Executive summary
mtkennerly/ludusavi meets our standard for a preview release, though we found no recorded design decisions and no architecture document or diagram. It scores 65 out of 100 and is rated Strong, and all 16 of its critical findings are security problems in the build pipeline and in the packages it uses.
Maturity, at 59, is the weakest lens and counts most in the score. The best first step is recording design decisions, worth about 6 points. Adding test instructions to the README is another step, worth about 3 points. Raising Maturity to 62 would lift the score to about 67.
Thirteen pipeline tools are referenced by a changeable name, so the build pipeline can be tampered with. Three known security holes in the packages the code depends on can be used by attackers. Pinning each tool to an exact version and updating the vulnerable packages would close both risks.
The product code is 37,618 lines, about €45,000 to rebuild.
If Maturity rose from 59 to 62, the lowest score rated Strong, the score would rise from 65 to about 67.
New since the last survey: 16 findings
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Supply-chain Provenance & Signing · REDACTED
- Web-Security Posture · Weak hash algorithm src/prelude.rs
Fixed since the last survey: 7 findings
- Churn × Complexity Hotspots · Hotspot: src/gui/app.rs src/gui/app.rs
- Churn × Complexity Hotspots · Hotspot: src/cli.rs src/cli.rs
- Churn × Complexity Hotspots · Hotspot: src/scan/layout.rs src/scan/layout.rs
- Churn × Complexity Hotspots · Hotspot: src/scan/semantic/convert.rs src/scan/semantic/convert.rs
- Churn × Complexity Hotspots · Hotspot: src/api.rs src/api.rs
- Change Coupling · Change coupling: app.rs ↔ game_list.rs src/gui/app.rs
- Supply-chain Provenance & Signing REDACTED
Rebuild cost: about €45,000 · Estimate
| Cost to rebuild | €15,000 to €75,000, for 247 to 784 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 65. 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: 37,618 lines of product code |
| What it is not | Not a quotation: nobody has offered to build it for that. Not a valuation: it says nothing about what the business is worth. Not a certified figure: no professional has signed it as one. |
Top priorities
Diagnosis: what the measurements show together
Architecture: which parts of the code depend on which
| uses → | 1 cli.api.response | 2 gui.style | 3 prelude | 4 scan.change | 5 gui.undoable | 6 scan.saves | 7 gui.shortcuts | 8 gui.modal | 9 scan.registry | 10 scan.layout | 11 scan.preview | 12 scan.backup | 13 scan.duplicate | 14 gui.file_tree | 15 scan.game_filter | 16 gui.search | 17 gui.game_list | 18 gui.screen | 19 resource.cache | 20 resource.manifest | 21 scan.title | 22 lang | 23 scan.launchers | 24 scan.launchers.lutris.spec | 25 scan | 26 gui.common | 27 gui.app | 28 gui.badge | 29 cloud | 30 resource.config | 31 gui.editor | 32 scan.semantic | 33 path | 34 api.parameters | 35 cli | 36 cli.api | 37 report | 38 resource.config.root | 39 api | 40 scan.launchers.lutris |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 1 cli.api.response | ||||||||||||||||||||||||||||||||||||||||
| 2 gui.style | 1 | |||||||||||||||||||||||||||||||||||||||
| 3 prelude | 1 | |||||||||||||||||||||||||||||||||||||||
| 4 scan.change | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 5 gui.undoable | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 6 scan.saves | 3 | 3 | 1 | |||||||||||||||||||||||||||||||||||||
| 7 gui.shortcuts | 1 | 1 | 1 | 2 | 2 | |||||||||||||||||||||||||||||||||||
| 8 gui.modal | 1 | 2 | 1 | 2 | 1 | 1 | ||||||||||||||||||||||||||||||||||
| 9 scan.registry | 1 | 1 | 1 | 2 | ||||||||||||||||||||||||||||||||||||
| 10 scan.layout | 2 | 2 | 4 | 1 | 3 | 2 | 8 | 3 | ||||||||||||||||||||||||||||||||
| 11 scan.preview | 2 | 1 | 1 | 1 | 1 | 1 | 2 | |||||||||||||||||||||||||||||||||
| 12 scan.backup | 1 | 2 | ||||||||||||||||||||||||||||||||||||||
| 13 scan.duplicate | 1 | 1 | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||
| 14 gui.file_tree | 2 | 1 | 1 | 2 | 3 | 3 | 1 | 3 | ||||||||||||||||||||||||||||||||
| 15 scan.game_filter | 2 | 1 | 2 | |||||||||||||||||||||||||||||||||||||
| 16 gui.search | 2 | 1 | 1 | 2 | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||
| 17 gui.game_list | 2 | 1 | 1 | 2 | 2 | 3 | 2 | 1 | 1 | 3 | 2 | 3 | 3 | |||||||||||||||||||||||||||
| 18 gui.screen | 4 | 1 | 3 | 1 | 2 | 6 | 1 | 3 | 4 | |||||||||||||||||||||||||||||||
| 19 resource.cache | 1 | 1 | 2 | 1 | ||||||||||||||||||||||||||||||||||||
| 20 resource.manifest | 1 | 2 | 3 | 2 | ||||||||||||||||||||||||||||||||||||
| 21 scan.title | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 22 lang | 1 | 1 | 1 | 1 | 3 | 4 | 1 | 5 | 1 | |||||||||||||||||||||||||||||||
| 23 scan.launchers | 1 | 1 | 1 | 1 | 2 | |||||||||||||||||||||||||||||||||||
| 24 scan.launchers.lutris.spec | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 25 scan | 1 | 2 | 1 | 1 | 4 | 1 | 6 | 1 | ||||||||||||||||||||||||||||||||
| 26 gui.common | 1 | 1 | 3 | 2 | 2 | |||||||||||||||||||||||||||||||||||
| 27 gui.app | 1 | 1 | 3 | 1 | 2 | 2 | 2 | 9 | 1 | 4 | 1 | 1 | ||||||||||||||||||||||||||||
| 28 gui.badge | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 29 cloud | 3 | 1 | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||
| 30 resource.config | 1 | 1 | 2 | 4 | 1 | 1 | 1 | 1 | 10 | |||||||||||||||||||||||||||||||
| 31 gui.editor | 1 | 1 | 1 | 2 | 1 | |||||||||||||||||||||||||||||||||||
| 32 scan.semantic | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 33 path | 2 | |||||||||||||||||||||||||||||||||||||||
| 34 api.parameters | 4 | 1 | ||||||||||||||||||||||||||||||||||||||
| 35 cli | 1 | 1 | 2 | 1 | 1 | 1 | 1 | 1 | ||||||||||||||||||||||||||||||||
| 36 cli.api | 1 | 1 | 1 | 1 | ||||||||||||||||||||||||||||||||||||
| 37 report | 4 | 1 | 4 | 1 | 1 | 1 | ||||||||||||||||||||||||||||||||||
| 38 resource.config.root | 19 | |||||||||||||||||||||||||||||||||||||||
| 39 api | 2 | 1 | 1 | 3 | 1 | 1 | 4 | |||||||||||||||||||||||||||||||||
| 40 scan.launchers.lutris | 1 | 1 | 2 | 2 | 1 |
2→32 gui.style uses scan.semantic part of a loop✕
- Connections
- 1 pair of types, where a type in gui.style uses a type in scan.semantic.
- The types involved
ludusavi.gui.style.Theme→ludusavi.scan.semantic.Base
- Direction
- gui.style uses scan.semantic, so a change to scan.semantic can break gui.style, while a change to gui.style can't break scan.semantic.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
3→33 prelude uses path part of a loop✕
- Connections
- 1 pair of types, where a type in prelude uses a type in path.
- The types involved
ludusavi.prelude.prelude$module→ludusavi.path.StrictPath
- Direction
- prelude uses path, so a change to path can break prelude, while a change to prelude can't break path.
- 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→25 scan.change uses scan part of a loop✕
- Connections
- 1 pair of types, where a type in scan.change uses a type in scan.
- The types involved
ludusavi.scan.change.ScanChange→ludusavi.scan.ScanKind
- Direction
- scan.change uses scan, so a change to scan can break scan.change, while a change to scan.change can't break scan.
- 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→33 scan.change uses path part of a loop✕
- Connections
- 1 pair of types, where a type in scan.change uses a type in path.
- The types involved
ludusavi.scan.change.ScanChange→ludusavi.path.StrictPath
- Direction
- scan.change uses path, so a change to path can break scan.change, while a change to scan.change can't break path.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
5→2 gui.undoable uses gui.style✕
- Connections
- 1 pair of types, where a type in gui.undoable uses a type in gui.style.
- The types involved
ludusavi.gui.undoable.Undoable→ludusavi.gui.style.Theme
- Direction
- gui.undoable uses gui.style, so a change to gui.style can break gui.undoable, while a change to gui.undoable can't break gui.style.
- Position
- Below the diagonal: gui.undoable uses a module listed above it, which is the healthy direction.
5→20 gui.undoable uses resource.manifest part of a loop✕
- Connections
- 1 pair of types, where a type in gui.undoable uses a type in resource.manifest.
- The types involved
ludusavi.gui.undoable.Undoable→ludusavi.resource.manifest.Tag
- Direction
- gui.undoable uses resource.manifest, so a change to resource.manifest can break gui.undoable, while a change to gui.undoable can't break resource.manifest.
- 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 scan.saves uses scan.change✕
- Connections
- 3 pairs of types, where a type in scan.saves uses a type in scan.change.
- The types involved
ludusavi.scan.saves.ScannedFile→ludusavi.scan.change.ScanChangeludusavi.scan.saves.ScannedRegistry→ludusavi.scan.change.ScanChangeludusavi.scan.saves.ScannedRegistryValue→ludusavi.scan.change.ScanChange
- Direction
- scan.saves uses scan.change, so a change to scan.change can break scan.saves, while a change to scan.saves can't break scan.change.
- Position
- Below the diagonal: scan.saves uses a module listed above it, which is the healthy direction.
6→25 scan.saves uses scan part of a loop✕
- Connections
- 3 pairs of types, where a type in scan.saves uses a type in scan.
- The types involved
ludusavi.scan.saves.ScannedFile→ludusavi.scan.ScanKindludusavi.scan.saves.ScannedRegistry→ludusavi.scan.ScanKindludusavi.scan.saves.ScannedRegistryValue→ludusavi.scan.ScanKind
- Direction
- scan.saves uses scan, so a change to scan can break scan.saves, while a change to scan.saves can't break scan.
- 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→33 scan.saves uses path part of a loop✕
- Connections
- 1 pair of types, where a type in scan.saves uses a type in path.
- The types involved
ludusavi.scan.saves.ScannedFile→ludusavi.path.StrictPath
- Direction
- scan.saves uses path, so a change to path can break scan.saves, while a change to scan.saves can't break path.
- 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→5 gui.shortcuts uses gui.undoable✕
- Connections
- 1 pair of types, where a type in gui.shortcuts uses a type in gui.undoable.
- The types involved
ludusavi.gui.shortcuts.Shortcut→ludusavi.gui.undoable.Action
- Direction
- gui.shortcuts uses gui.undoable, so a change to gui.undoable can break gui.shortcuts, while a change to gui.shortcuts can't break gui.undoable.
- Position
- Below the diagonal: gui.shortcuts uses a module listed above it, which is the healthy direction.
7→9 gui.shortcuts uses scan.registry part of a loop✕
- Connections
- 1 pair of types, where a type in gui.shortcuts uses a type in scan.registry.
- The types involved
ludusavi.gui.shortcuts.Shortcut→ludusavi.scan.registry.RegistryItem
- Direction
- gui.shortcuts uses scan.registry, so a change to scan.registry can break gui.shortcuts, while a change to gui.shortcuts can't break scan.registry.
- 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→26 gui.shortcuts uses gui.common part of a loop✕
- Connections
- 1 pair of types, where a type in gui.shortcuts uses a type in gui.common.
- The types involved
ludusavi.gui.shortcuts.TextHistories→ludusavi.gui.common.UndoSubject
- Direction
- gui.shortcuts uses gui.common, so a change to gui.common can break gui.shortcuts, while a change to gui.shortcuts can't break gui.common.
- 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→30 gui.shortcuts uses resource.config part of a loop✕
- Connections
- 2 pairs of types, where a type in gui.shortcuts uses a type in resource.config.
- The types involved
ludusavi.gui.shortcuts.TextHistories→ludusavi.resource.config.Configludusavi.gui.shortcuts.TextHistories→ludusavi.resource.config.CustomGame
- Direction
- gui.shortcuts uses resource.config, so a change to resource.config can break gui.shortcuts, while a change to gui.shortcuts can't break resource.config.
- 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→33 gui.shortcuts uses path part of a loop✕
- Connections
- 2 pairs of types, where a type in gui.shortcuts uses a type in path.
- The types involved
ludusavi.gui.shortcuts.Shortcut→ludusavi.path.StrictPathludusavi.gui.shortcuts.TextHistory→ludusavi.path.StrictPath
- Direction
- gui.shortcuts uses path, so a change to path can break gui.shortcuts, while a change to gui.shortcuts can't break path.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
8→2 gui.modal uses gui.style✕
- Connections
- 1 pair of types, where a type in gui.modal uses a type in gui.style.
- The types involved
ludusavi.gui.modal.Modal→ludusavi.gui.style.Container
- Direction
- gui.modal uses gui.style, so a change to gui.style can break gui.modal, while a change to gui.modal can't break gui.style.
- Position
- Below the diagonal: gui.modal uses a module listed above it, which is the healthy direction.
8→7 gui.modal uses gui.shortcuts✕
- Connections
- 2 pairs of types, where a type in gui.modal uses a type in gui.shortcuts.
- The types involved
ludusavi.gui.modal.Modal→ludusavi.gui.shortcuts.TextHistoriesludusavi.gui.modal.ModalField→ludusavi.gui.shortcuts.TextHistories
- Direction
- gui.modal uses gui.shortcuts, so a change to gui.shortcuts can break gui.modal, while a change to gui.modal can't break gui.shortcuts.
- Position
- Below the diagonal: gui.modal uses a module listed above it, which is the healthy direction.
8→9 gui.modal uses scan.registry part of a loop✕
- Connections
- 1 pair of types, where a type in gui.modal uses a type in scan.registry.
- The types involved
ludusavi.gui.modal.Kind→ludusavi.scan.registry.RegistryKind
- Direction
- gui.modal uses scan.registry, so a change to scan.registry can break gui.modal, while a change to gui.modal can't break scan.registry.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
8→26 gui.modal uses gui.common part of a loop✕
- Connections
- 2 pairs of types, where a type in gui.modal uses a type in gui.common.
- The types involved
ludusavi.gui.modal.Modal→ludusavi.gui.common.Messageludusavi.gui.modal.Modal→ludusavi.gui.common.Operation
- Direction
- gui.modal uses gui.common, so a change to gui.common can break gui.modal, while a change to gui.modal can't break gui.common.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
8→29 gui.modal uses cloud part of a loop✕
- Connections
- 1 pair of types, where a type in gui.modal uses a type in cloud.
- The types involved
ludusavi.gui.modal.Modal→ludusavi.cloud.CloudChange
- Direction
- gui.modal uses cloud, so a change to cloud can break gui.modal, while a change to gui.modal can't break cloud.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
8→30 gui.modal uses resource.config part of a loop✕
- Connections
- 1 pair of types, where a type in gui.modal uses a type in resource.config.
- The types involved
ludusavi.gui.modal.Modal→ludusavi.resource.config.Config
- Direction
- gui.modal uses resource.config, so a change to resource.config can break gui.modal, while a change to gui.modal can't break resource.config.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
9→6 scan.registry uses scan.saves✕
- Connections
- 1 pair of types, where a type in scan.registry uses a type in scan.saves.
- The types involved
ludusavi.scan.registry.Hives→ludusavi.scan.saves.ScannedRegistry
- Direction
- scan.registry uses scan.saves, so a change to scan.saves can break scan.registry, while a change to scan.registry can't break scan.saves.
- Position
- Below the diagonal: scan.registry uses a module listed above it, which is the healthy direction.
9→8 scan.registry uses gui.modal✕
- Connections
- 1 pair of types, where a type in scan.registry uses a type in gui.modal.
- The types involved
ludusavi.scan.registry.RegistryKind→ludusavi.gui.modal.Kind
- Direction
- scan.registry uses gui.modal, so a change to gui.modal can break scan.registry, while a change to scan.registry can't break gui.modal.
- Position
- Below the diagonal: scan.registry uses a module listed above it, which is the healthy direction.
9→30 scan.registry uses resource.config part of a loop✕
- Connections
- 1 pair of types, where a type in scan.registry uses a type in resource.config.
- The types involved
ludusavi.scan.registry.Hives→ludusavi.resource.config.ToggledRegistry
- Direction
- scan.registry uses resource.config, so a change to resource.config can break scan.registry, while a change to scan.registry can't break resource.config.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
9→33 scan.registry uses path part of a loop✕
- Connections
- 2 pairs of types, where a type in scan.registry uses a type in path.
- The types involved
ludusavi.scan.registry.Format→ludusavi.path.StrictPathludusavi.scan.registry.Hives→ludusavi.path.StrictPath
- Direction
- scan.registry uses path, so a change to path can break scan.registry, while a change to scan.registry can't break path.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
10→9 scan.layout uses scan.registry✕
- Connections
- 2 pairs of types, where a type in scan.layout uses a type in scan.registry.
- The types involved
ludusavi.scan.layout.GameLayout→ludusavi.scan.registry.Hivesludusavi.scan.layout.LatestBackup→ludusavi.scan.registry.Hives
- Direction
- scan.layout uses scan.registry, so a change to scan.registry can break scan.layout, while a change to scan.layout can't break scan.registry.
- Position
- Below the diagonal: scan.layout uses a module listed above it, which is the healthy direction.
10→11 scan.layout uses scan.preview part of a loop✕
- Connections
- 2 pairs of types, where a type in scan.layout uses a type in scan.preview.
- The types involved
ludusavi.scan.layout.GameLayout→ludusavi.scan.preview.ScanInfoludusavi.scan.layout.LatestBackup→ludusavi.scan.preview.ScanInfo
- Direction
- scan.layout uses scan.preview, so a change to scan.preview can break scan.layout, while a change to scan.layout can't break scan.preview.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
10→12 scan.layout uses scan.backup part of a loop✕
- Connections
- 4 pairs of types, where a type in scan.layout uses a type in scan.backup.
- The types involved
ludusavi.scan.layout.Backup→ludusavi.scan.backup.BackupIdludusavi.scan.layout.Backup→ludusavi.scan.backup.BackupInfoludusavi.scan.layout.GameLayout→ludusavi.scan.backup.BackupIdludusavi.scan.layout.GameLayout→ludusavi.scan.backup.BackupInfo
- Direction
- scan.layout uses scan.backup, so a change to scan.backup can break scan.layout, while a change to scan.layout can't break scan.backup.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
10→18 scan.layout uses gui.screen part of a loop✕
- Connections
- 1 pair of types, where a type in scan.layout uses a type in gui.screen.
- The types involved
ludusavi.scan.layout.GameLayout→ludusavi.gui.screen.Backup
- Direction
- scan.layout uses gui.screen, so a change to gui.screen can break scan.layout, while a change to scan.layout can't break gui.screen.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
10→20 scan.layout uses resource.manifest part of a loop✕
- Connections
- 3 pairs of types, where a type in scan.layout uses a type in resource.manifest.
- The types involved
ludusavi.scan.layout.Backup→ludusavi.resource.manifest.Osludusavi.scan.layout.DifferentialBackup→ludusavi.resource.manifest.Osludusavi.scan.layout.FullBackup→ludusavi.resource.manifest.Os
- Direction
- scan.layout uses resource.manifest, so a change to resource.manifest can break scan.layout, while a change to scan.layout can't break resource.manifest.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
10→25 scan.layout uses scan part of a loop✕
- Connections
- 2 pairs of types, where a type in scan.layout uses a type in scan.
- The types involved
ludusavi.scan.layout.BackupLayout→ludusavi.scan.ScanKindludusavi.scan.layout.GameLayout→ludusavi.scan.ScanKind
- Direction
- scan.layout uses scan, so a change to scan can break scan.layout, while a change to scan.layout can't break scan.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
10→30 scan.layout uses resource.config part of a loop✕
- Connections
- 8 pairs of types, where a type in scan.layout uses a type in resource.config.
- The types involved
ludusavi.scan.layout.BackupLayout→ludusavi.resource.config.ToggledPathsludusavi.scan.layout.DifferentialBackup→ludusavi.resource.config.BackupFormatludusavi.scan.layout.FullBackup→ludusavi.resource.config.BackupFormatludusavi.scan.layout.GameLayout→ludusavi.resource.config.BackupFormatludusavi.scan.layout.GameLayout→ludusavi.resource.config.BackupFormatsludusavi.scan.layout.GameLayout→ludusavi.resource.config.Retentionludusavi.scan.layout.GameLayout→ludusavi.resource.config.ToggledPathsludusavi.scan.layout.GameLayout→ludusavi.resource.config.ToggledRegistry
- Direction
- scan.layout uses resource.config, so a change to resource.config can break scan.layout, while a change to scan.layout can't break resource.config.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
10→33 scan.layout uses path part of a loop✕
- Connections
- 3 pairs of types, where a type in scan.layout uses a type in path.
- The types involved
ludusavi.scan.layout.BackupLayout→ludusavi.path.StrictPathludusavi.scan.layout.GameLayout→ludusavi.path.StrictPathludusavi.scan.layout.IndividualMapping→ludusavi.path.StrictPath
- Direction
- scan.layout uses path, so a change to path can break scan.layout, while a change to scan.layout can't break path.
- 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.
11→4 scan.preview uses scan.change✕
- Connections
- 2 pairs of types, where a type in scan.preview uses a type in scan.change.
- The types involved
ludusavi.scan.preview.ScanInfo→ludusavi.scan.change.ScanChangeludusavi.scan.preview.ScanInfo→ludusavi.scan.change.ScanChangeCount
- Direction
- scan.preview uses scan.change, so a change to scan.change can break scan.preview, while a change to scan.preview can't break scan.change.
- Position
- Below the diagonal: scan.preview uses a module listed above it, which is the healthy direction.
11→9 scan.preview uses scan.registry✕
- Connections
- 1 pair of types, where a type in scan.preview uses a type in scan.registry.
- The types involved
ludusavi.scan.preview.ScanInfo→ludusavi.scan.registry.Hives
- Direction
- scan.preview uses scan.registry, so a change to scan.registry can break scan.preview, while a change to scan.preview can't break scan.registry.
- Position
- Below the diagonal: scan.preview uses a module listed above it, which is the healthy direction.
11→10 scan.preview uses scan.layout✕
- Connections
- 1 pair of types, where a type in scan.preview uses a type in scan.layout.
- The types involved
ludusavi.scan.preview.ScanInfo→ludusavi.scan.layout.BackupSemantics
- Direction
- scan.preview uses scan.layout, so a change to scan.layout can break scan.preview, while a change to scan.preview can't break scan.layout.
- Position
- Below the diagonal: scan.preview uses a module listed above it, which is the healthy direction.
11→12 scan.preview uses scan.backup part of a loop✕
- Connections
- 1 pair of types, where a type in scan.preview uses a type in scan.backup.
- The types involved
ludusavi.scan.preview.ScanInfo→ludusavi.scan.backup.BackupInfo
- Direction
- scan.preview uses scan.backup, so a change to scan.backup can break scan.preview, while a change to scan.preview can't break scan.backup.
- 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.
11→18 scan.preview uses gui.screen part of a loop✕
- Connections
- 1 pair of types, where a type in scan.preview uses a type in gui.screen.
- The types involved
ludusavi.scan.preview.ScanInfo→ludusavi.gui.screen.Backup
- Direction
- scan.preview uses gui.screen, so a change to gui.screen can break scan.preview, while a change to scan.preview can't break gui.screen.
- 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.
11→25 scan.preview uses scan part of a loop✕
- Connections
- 1 pair of types, where a type in scan.preview uses a type in scan.
- The types involved
ludusavi.scan.preview.ScanInfo→ludusavi.scan.ScanKind
- Direction
- scan.preview uses scan, so a change to scan can break scan.preview, while a change to scan.preview can't break scan.
- 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.
11→30 scan.preview uses resource.config part of a loop✕
- Connections
- 2 pairs of types, where a type in scan.preview uses a type in resource.config.
- The types involved
ludusavi.scan.preview.ScanInfo→ludusavi.resource.config.ToggledPathsludusavi.scan.preview.ScanInfo→ludusavi.resource.config.ToggledRegistry
- Direction
- scan.preview uses resource.config, so a change to resource.config can break scan.preview, while a change to scan.preview can't break resource.config.
- 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.
12→4 scan.backup uses scan.change✕
- Connections
- 1 pair of types, where a type in scan.backup uses a type in scan.change.
- The types involved
ludusavi.scan.backup.OperationStatus→ludusavi.scan.change.ScanChangeCount
- Direction
- scan.backup uses scan.change, so a change to scan.change can break scan.backup, while a change to scan.backup can't break scan.change.
- Position
- Below the diagonal: scan.backup uses a module listed above it, which is the healthy direction.
12→11 scan.backup uses scan.preview✕
- Connections
- 2 pairs of types, where a type in scan.backup uses a type in scan.preview.
- The types involved
ludusavi.scan.backup.BackupInfo→ludusavi.scan.preview.ScanInfoludusavi.scan.backup.OperationStatus→ludusavi.scan.preview.ScanInfo
- Direction
- scan.backup uses scan.preview, so a change to scan.preview can break scan.backup, while a change to scan.backup can't break scan.preview.
- Position
- Below the diagonal: scan.backup uses a module listed above it, which is the healthy direction.
13→4 scan.duplicate uses scan.change✕
- Connections
- 1 pair of types, where a type in scan.duplicate uses a type in scan.change.
- The types involved
ludusavi.scan.duplicate.DuplicateDetectorEntry→ludusavi.scan.change.ScanChange
- Direction
- scan.duplicate uses scan.change, so a change to scan.change can break scan.duplicate, while a change to scan.duplicate can't break scan.change.
- Position
- Below the diagonal: scan.duplicate uses a module listed above it, which is the healthy direction.
13→6 scan.duplicate uses scan.saves✕
- Connections
- 1 pair of types, where a type in scan.duplicate uses a type in scan.saves.
- The types involved
ludusavi.scan.duplicate.DuplicateDetector→ludusavi.scan.saves.ScannedFile
- Direction
- scan.duplicate uses scan.saves, so a change to scan.saves can break scan.duplicate, while a change to scan.duplicate can't break scan.saves.
- Position
- Below the diagonal: scan.duplicate uses a module listed above it, which is the healthy direction.
13→9 scan.duplicate uses scan.registry✕
- Connections
- 1 pair of types, where a type in scan.duplicate uses a type in scan.registry.
- The types involved
ludusavi.scan.duplicate.DuplicateDetector→ludusavi.scan.registry.RegistryItem
- Direction
- scan.duplicate uses scan.registry, so a change to scan.registry can break scan.duplicate, while a change to scan.duplicate can't break scan.registry.
- Position
- Below the diagonal: scan.duplicate uses a module listed above it, which is the healthy direction.
13→11 scan.duplicate uses scan.preview✕
- Connections
- 1 pair of types, where a type in scan.duplicate uses a type in scan.preview.
- The types involved
ludusavi.scan.duplicate.DuplicateDetector→ludusavi.scan.preview.ScanInfo
- Direction
- scan.duplicate uses scan.preview, so a change to scan.preview can break scan.duplicate, while a change to scan.duplicate can't break scan.preview.
- Position
- Below the diagonal: scan.duplicate uses a module listed above it, which is the healthy direction.
13→33 scan.duplicate uses path part of a loop✕
- Connections
- 1 pair of types, where a type in scan.duplicate uses a type in path.
- The types involved
ludusavi.scan.duplicate.DuplicateDetector→ludusavi.path.StrictPath
- Direction
- scan.duplicate uses path, so a change to path can break scan.duplicate, while a change to scan.duplicate can't break path.
- 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.
14→2 gui.file_tree uses gui.style✕
- Connections
- 2 pairs of types, where a type in gui.file_tree uses a type in gui.style.
- The types involved
ludusavi.gui.file_tree.FileTree→ludusavi.gui.style.Containerludusavi.gui.file_tree.FileTreeNode→ludusavi.gui.style.Container
- Direction
- gui.file_tree uses gui.style, so a change to gui.style can break gui.file_tree, while a change to gui.file_tree can't break gui.style.
- Position
- Below the diagonal: gui.file_tree uses a module listed above it, which is the healthy direction.
14→4 gui.file_tree uses scan.change✕
- Connections
- 1 pair of types, where a type in gui.file_tree uses a type in scan.change.
- The types involved
ludusavi.gui.file_tree.FileTreeNode→ludusavi.scan.change.ScanChange
- Direction
- gui.file_tree uses scan.change, so a change to scan.change can break gui.file_tree, while a change to gui.file_tree can't break scan.change.
- Position
- Below the diagonal: gui.file_tree uses a module listed above it, which is the healthy direction.
14→11 gui.file_tree uses scan.preview✕
- Connections
- 1 pair of types, where a type in gui.file_tree uses a type in scan.preview.
- The types involved
ludusavi.gui.file_tree.FileTree→ludusavi.scan.preview.ScanInfo
- Direction
- gui.file_tree uses scan.preview, so a change to scan.preview can break gui.file_tree, while a change to gui.file_tree can't break scan.preview.
- Position
- Below the diagonal: gui.file_tree uses a module listed above it, which is the healthy direction.
14→12 gui.file_tree uses scan.backup✕
- Connections
- 2 pairs of types, where a type in gui.file_tree uses a type in scan.backup.
- The types involved
ludusavi.gui.file_tree.FileTree→ludusavi.scan.backup.BackupInfoludusavi.gui.file_tree.FileTreeNode→ludusavi.scan.backup.BackupError
- Direction
- gui.file_tree uses scan.backup, so a change to scan.backup can break gui.file_tree, while a change to gui.file_tree can't break scan.backup.
- Position
- Below the diagonal: gui.file_tree uses a module listed above it, which is the healthy direction.
14→13 gui.file_tree uses scan.duplicate✕
- Connections
- 3 pairs of types, where a type in gui.file_tree uses a type in scan.duplicate.
- The types involved
ludusavi.gui.file_tree.FileTree→ludusavi.scan.duplicate.DuplicateDetectorludusavi.gui.file_tree.FileTreeNode→ludusavi.scan.duplicate.DuplicateDetectorludusavi.gui.file_tree.FileTreeNode→ludusavi.scan.duplicate.Duplication
- Direction
- gui.file_tree uses scan.duplicate, so a change to scan.duplicate can break gui.file_tree, while a change to gui.file_tree can't break scan.duplicate.
- Position
- Below the diagonal: gui.file_tree uses a module listed above it, which is the healthy direction.
14→25 gui.file_tree uses scan part of a loop✕
- Connections
- 3 pairs of types, where a type in gui.file_tree uses a type in scan.
- The types involved
ludusavi.gui.file_tree.FileTree→ludusavi.scan.ScanKindludusavi.gui.file_tree.FileTreeNode→ludusavi.scan.ScanKindludusavi.gui.file_tree.file_tree$module→ludusavi.scan.ScanKind
- Direction
- gui.file_tree uses scan, so a change to scan can break gui.file_tree, while a change to gui.file_tree can't break scan.
- 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.
14→26 gui.file_tree uses gui.common part of a loop✕
- Connections
- 1 pair of types, where a type in gui.file_tree uses a type in gui.common.
- The types involved
ludusavi.gui.file_tree.FileTreeNode→ludusavi.gui.common.TreeNodeKey
- Direction
- gui.file_tree uses gui.common, so a change to gui.common can break gui.file_tree, while a change to gui.file_tree can't break gui.common.
- 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.
14→30 gui.file_tree uses resource.config part of a loop✕
- Connections
- 3 pairs of types, where a type in gui.file_tree uses a type in resource.config.
- The types involved
ludusavi.gui.file_tree.FileTree→ludusavi.resource.config.Configludusavi.gui.file_tree.FileTreeNode→ludusavi.resource.config.Configludusavi.gui.file_tree.file_tree$module→ludusavi.resource.config.Config
- Direction
- gui.file_tree uses resource.config, so a change to resource.config can break gui.file_tree, while a change to gui.file_tree can't break resource.config.
- 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.
15→11 scan.game_filter uses scan.preview✕
- Connections
- 2 pairs of types, where a type in scan.game_filter uses a type in scan.preview.
- The types involved
ludusavi.scan.game_filter.Change→ludusavi.scan.preview.ScanInfoludusavi.scan.game_filter.Completeness→ludusavi.scan.preview.ScanInfo
- Direction
- scan.game_filter uses scan.preview, so a change to scan.preview can break scan.game_filter, while a change to scan.game_filter can't break scan.preview.
- Position
- Below the diagonal: scan.game_filter uses a module listed above it, which is the healthy direction.
15→13 scan.game_filter uses scan.duplicate✕
- Connections
- 1 pair of types, where a type in scan.game_filter uses a type in scan.duplicate.
- The types involved
ludusavi.scan.game_filter.Uniqueness→ludusavi.scan.duplicate.Duplication
- Direction
- scan.game_filter uses scan.duplicate, so a change to scan.duplicate can break scan.game_filter, while a change to scan.game_filter can't break scan.duplicate.
- Position
- Below the diagonal: scan.game_filter uses a module listed above it, which is the healthy direction.
15→20 scan.game_filter uses resource.manifest part of a loop✕
- Connections
- 2 pairs of types, where a type in scan.game_filter uses a type in resource.manifest.
- The types involved
ludusavi.scan.game_filter.Manifest→ludusavi.resource.manifest.Gameludusavi.scan.game_filter.Manifest→ludusavi.resource.manifest.Source
- Direction
- scan.game_filter uses resource.manifest, so a change to resource.manifest can break scan.game_filter, while a change to scan.game_filter can't break resource.manifest.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
16→7 gui.search uses gui.shortcuts✕
- Connections
- 2 pairs of types, where a type in gui.search uses a type in gui.shortcuts.
- The types involved
ludusavi.gui.search.CustomGamesFilter→ludusavi.gui.shortcuts.TextHistoriesludusavi.gui.search.FilterComponent→ludusavi.gui.shortcuts.TextHistories
- Direction
- gui.search uses gui.shortcuts, so a change to gui.shortcuts can break gui.search, while a change to gui.search can't break gui.shortcuts.
- Position
- Below the diagonal: gui.search uses a module listed above it, which is the healthy direction.
16→11 gui.search uses scan.preview✕
- Connections
- 1 pair of types, where a type in gui.search uses a type in scan.preview.
- The types involved
ludusavi.gui.search.FilterComponent→ludusavi.scan.preview.ScanInfo
- Direction
- gui.search uses scan.preview, so a change to scan.preview can break gui.search, while a change to gui.search can't break scan.preview.
- Position
- Below the diagonal: gui.search uses a module listed above it, which is the healthy direction.
16→13 gui.search uses scan.duplicate✕
- Connections
- 1 pair of types, where a type in gui.search uses a type in scan.duplicate.
- The types involved
ludusavi.gui.search.FilterComponent→ludusavi.scan.duplicate.Duplication
- Direction
- gui.search uses scan.duplicate, so a change to scan.duplicate can break gui.search, while a change to gui.search can't break scan.duplicate.
- Position
- Below the diagonal: gui.search uses a module listed above it, which is the healthy direction.
16→15 gui.search uses scan.game_filter✕
- Connections
- 2 pairs of types, where a type in gui.search uses a type in scan.game_filter.
- The types involved
ludusavi.gui.search.FilterComponent→ludusavi.scan.game_filter.FilterKindludusavi.gui.search.search$module→ludusavi.scan.game_filter.FilterKind
- Direction
- gui.search uses scan.game_filter, so a change to scan.game_filter can break gui.search, while a change to gui.search can't break scan.game_filter.
- Position
- Below the diagonal: gui.search uses a module listed above it, which is the healthy direction.
16→19 gui.search uses resource.cache part of a loop✕
- Connections
- 1 pair of types, where a type in gui.search uses a type in resource.cache.
- The types involved
ludusavi.gui.search.FilterComponent→ludusavi.resource.cache.Manifest
- Direction
- gui.search uses resource.cache, so a change to resource.cache can break gui.search, while a change to gui.search can't break resource.cache.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
16→26 gui.search uses gui.common part of a loop✕
- Connections
- 1 pair of types, where a type in gui.search uses a type in gui.common.
- The types involved
ludusavi.gui.search.FilterComponent→ludusavi.gui.common.Screen
- Direction
- gui.search uses gui.common, so a change to gui.common can break gui.search, while a change to gui.search can't break gui.common.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
16→30 gui.search uses resource.config part of a loop✕
- Connections
- 1 pair of types, where a type in gui.search uses a type in resource.config.
- The types involved
ludusavi.gui.search.CustomGamesFilter→ludusavi.resource.config.CustomGame
- Direction
- gui.search uses resource.config, so a change to resource.config can break gui.search, while a change to gui.search can't break resource.config.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
17→2 gui.game_list uses gui.style✕
- Connections
- 2 pairs of types, where a type in gui.game_list uses a type in gui.style.
- The types involved
ludusavi.gui.game_list.GameList→ludusavi.gui.style.Containerludusavi.gui.game_list.GameListEntry→ludusavi.gui.style.Container
- Direction
- gui.game_list uses gui.style, so a change to gui.style can break gui.game_list, while a change to gui.game_list can't break gui.style.
- Position
- Below the diagonal: gui.game_list uses a module listed above it, which is the healthy direction.
17→5 gui.game_list uses gui.undoable✕
- Connections
- 1 pair of types, where a type in gui.game_list uses a type in gui.undoable.
- The types involved
ludusavi.gui.game_list.GameList→ludusavi.gui.undoable.Action
- Direction
- gui.game_list uses gui.undoable, so a change to gui.undoable can break gui.game_list, while a change to gui.game_list can't break gui.undoable.
- Position
- Below the diagonal: gui.game_list uses a module listed above it, which is the healthy direction.
17→7 gui.game_list uses gui.shortcuts✕
- Connections
- 1 pair of types, where a type in gui.game_list uses a type in gui.shortcuts.
- The types involved
ludusavi.gui.game_list.GameList→ludusavi.gui.shortcuts.TextHistories
- Direction
- gui.game_list uses gui.shortcuts, so a change to gui.shortcuts can break gui.game_list, while a change to gui.game_list can't break gui.shortcuts.
- Position
- Below the diagonal: gui.game_list uses a module listed above it, which is the healthy direction.
17→10 gui.game_list uses scan.layout✕
- Connections
- 2 pairs of types, where a type in gui.game_list uses a type in scan.layout.
- The types involved
ludusavi.gui.game_list.GameList→ludusavi.scan.layout.GameLayoutludusavi.gui.game_list.GameListEntry→ludusavi.scan.layout.GameLayout
- Direction
- gui.game_list uses scan.layout, so a change to scan.layout can break gui.game_list, while a change to gui.game_list can't break scan.layout.
- Position
- Below the diagonal: gui.game_list uses a module listed above it, which is the healthy direction.
17→11 gui.game_list uses scan.preview✕
- Connections
- 2 pairs of types, where a type in gui.game_list uses a type in scan.preview.
- The types involved
ludusavi.gui.game_list.GameList→ludusavi.scan.preview.ScanInfoludusavi.gui.game_list.GameListEntry→ludusavi.scan.preview.ScanInfo
- Direction
- gui.game_list uses scan.preview, so a change to scan.preview can break gui.game_list, while a change to gui.game_list can't break scan.preview.
- Position
- Below the diagonal: gui.game_list uses a module listed above it, which is the healthy direction.
17→12 gui.game_list uses scan.backup✕
- Connections
- 3 pairs of types, where a type in gui.game_list uses a type in scan.backup.
- The types involved
ludusavi.gui.game_list.GameList→ludusavi.scan.backup.BackupInfoludusavi.gui.game_list.GameList→ludusavi.scan.backup.OperationStatusludusavi.gui.game_list.GameListEntry→ludusavi.scan.backup.BackupInfo
- Direction
- gui.game_list uses scan.backup, so a change to scan.backup can break gui.game_list, while a change to gui.game_list can't break scan.backup.
- Position
- Below the diagonal: gui.game_list uses a module listed above it, which is the healthy direction.
17→13 gui.game_list uses scan.duplicate✕
- Connections
- 2 pairs of types, where a type in gui.game_list uses a type in scan.duplicate.
- The types involved
ludusavi.gui.game_list.GameList→ludusavi.scan.duplicate.DuplicateDetectorludusavi.gui.game_list.GameListEntry→ludusavi.scan.duplicate.DuplicateDetector
- Direction
- gui.game_list uses scan.duplicate, so a change to scan.duplicate can break gui.game_list, while a change to gui.game_list can't break scan.duplicate.
- Position
- Below the diagonal: gui.game_list uses a module listed above it, which is the healthy direction.
17→14 gui.game_list uses gui.file_tree✕
- Connections
- 1 pair of types, where a type in gui.game_list uses a type in gui.file_tree.
- The types involved
ludusavi.gui.game_list.GameListEntry→ludusavi.gui.file_tree.FileTree
- Direction
- gui.game_list uses gui.file_tree, so a change to gui.file_tree can break gui.game_list, while a change to gui.game_list can't break gui.file_tree.
- Position
- Below the diagonal: gui.game_list uses a module listed above it, which is the healthy direction.
17→16 gui.game_list uses gui.search✕
- Connections
- 1 pair of types, where a type in gui.game_list uses a type in gui.search.
- The types involved
ludusavi.gui.game_list.GameList→ludusavi.gui.search.FilterComponent
- Direction
- gui.game_list uses gui.search, so a change to gui.search can break gui.game_list, while a change to gui.game_list can't break gui.search.
- Position
- Below the diagonal: gui.game_list uses a module listed above it, which is the healthy direction.
17→19 gui.game_list uses resource.cache part of a loop✕
- Connections
- 3 pairs of types, where a type in gui.game_list uses a type in resource.cache.
- The types involved
ludusavi.gui.game_list.GameList→ludusavi.resource.cache.Cacheludusavi.gui.game_list.GameList→ludusavi.resource.cache.Manifestludusavi.gui.game_list.GameListEntry→ludusavi.resource.cache.Manifest
- Direction
- gui.game_list uses resource.cache, so a change to resource.cache can break gui.game_list, while a change to gui.game_list can't break resource.cache.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
17→25 gui.game_list uses scan part of a loop✕
- Connections
- 2 pairs of types, where a type in gui.game_list uses a type in scan.
- The types involved
ludusavi.gui.game_list.GameList→ludusavi.scan.ScanKindludusavi.gui.game_list.GameListEntry→ludusavi.scan.ScanKind
- Direction
- gui.game_list uses scan, so a change to scan can break gui.game_list, while a change to gui.game_list can't break scan.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
17→26 gui.game_list uses gui.common part of a loop✕
- Connections
- 3 pairs of types, where a type in gui.game_list uses a type in gui.common.
- The types involved
ludusavi.gui.game_list.GameList→ludusavi.gui.common.GameSelectionludusavi.gui.game_list.GameList→ludusavi.gui.common.Operationludusavi.gui.game_list.GameListEntry→ludusavi.gui.common.Operation
- Direction
- gui.game_list uses gui.common, so a change to gui.common can break gui.game_list, while a change to gui.game_list can't break gui.common.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
17→30 gui.game_list uses resource.config part of a loop✕
- Connections
- 3 pairs of types, where a type in gui.game_list uses a type in resource.config.
- The types involved
ludusavi.gui.game_list.GameList→ludusavi.resource.config.Configludusavi.gui.game_list.GameList→ludusavi.resource.config.Sortludusavi.gui.game_list.GameListEntry→ludusavi.resource.config.Config
- Direction
- gui.game_list uses resource.config, so a change to resource.config can break gui.game_list, while a change to gui.game_list can't break resource.config.
- 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.
18→7 gui.screen uses gui.shortcuts✕
- Connections
- 4 pairs of types, where a type in gui.screen uses a type in gui.shortcuts.
- The types involved
ludusavi.gui.screen.Backup→ludusavi.gui.shortcuts.TextHistoriesludusavi.gui.screen.CustomGames→ludusavi.gui.shortcuts.TextHistoriesludusavi.gui.screen.Restore→ludusavi.gui.shortcuts.TextHistoriesludusavi.gui.screen.screen$module→ludusavi.gui.shortcuts.TextHistories
- Direction
- gui.screen uses gui.shortcuts, so a change to gui.shortcuts can break gui.screen, while a change to gui.screen can't break gui.shortcuts.
- Position
- Below the diagonal: gui.screen uses a module listed above it, which is the healthy direction.
18→12 gui.screen uses scan.backup✕
- Connections
- 1 pair of types, where a type in gui.screen uses a type in scan.backup.
- The types involved
ludusavi.gui.screen.screen$module→ludusavi.scan.backup.OperationStatus
- Direction
- gui.screen uses scan.backup, so a change to scan.backup can break gui.screen, while a change to gui.screen can't break scan.backup.
- Position
- Below the diagonal: gui.screen uses a module listed above it, which is the healthy direction.
18→13 gui.screen uses scan.duplicate✕
- Connections
- 3 pairs of types, where a type in gui.screen uses a type in scan.duplicate.
- The types involved
ludusavi.gui.screen.Backup→ludusavi.scan.duplicate.DuplicateDetectorludusavi.gui.screen.Restore→ludusavi.scan.duplicate.DuplicateDetectorludusavi.gui.screen.screen$module→ludusavi.scan.duplicate.Duplication
- Direction
- gui.screen uses scan.duplicate, so a change to scan.duplicate can break gui.screen, while a change to gui.screen can't break scan.duplicate.
- Position
- Below the diagonal: gui.screen uses a module listed above it, which is the healthy direction.
18→16 gui.screen uses gui.search✕
- Connections
- 1 pair of types, where a type in gui.screen uses a type in gui.search.
- The types involved
ludusavi.gui.screen.CustomGames→ludusavi.gui.search.CustomGamesFilter
- Direction
- gui.screen uses gui.search, so a change to gui.search can break gui.screen, while a change to gui.screen can't break gui.search.
- Position
- Below the diagonal: gui.screen uses a module listed above it, which is the healthy direction.
18→17 gui.screen uses gui.game_list✕
- Connections
- 2 pairs of types, where a type in gui.screen uses a type in gui.game_list.
- The types involved
ludusavi.gui.screen.Backup→ludusavi.gui.game_list.GameListludusavi.gui.screen.Restore→ludusavi.gui.game_list.GameList
- Direction
- gui.screen uses gui.game_list, so a change to gui.game_list can break gui.screen, while a change to gui.screen can't break gui.game_list.
- Position
- Below the diagonal: gui.screen uses a module listed above it, which is the healthy direction.
18→19 gui.screen uses resource.cache part of a loop✕
- Connections
- 6 pairs of types, where a type in gui.screen uses a type in resource.cache.
- The types involved
ludusavi.gui.screen.Backup→ludusavi.resource.cache.Cacheludusavi.gui.screen.Backup→ludusavi.resource.cache.Manifestludusavi.gui.screen.CustomGames→ludusavi.resource.cache.Manifestludusavi.gui.screen.Restore→ludusavi.resource.cache.Cacheludusavi.gui.screen.Restore→ludusavi.resource.cache.Manifestludusavi.gui.screen.screen$module→ludusavi.resource.cache.Cache
- Direction
- gui.screen uses resource.cache, so a change to resource.cache can break gui.screen, while a change to gui.screen can't break resource.cache.
- 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.
18→25 gui.screen uses scan part of a loop✕
- Connections
- 1 pair of types, where a type in gui.screen uses a type in scan.
- The types involved
ludusavi.gui.screen.screen$module→ludusavi.scan.ScanKind
- Direction
- gui.screen uses scan, so a change to scan can break gui.screen, while a change to gui.screen can't break scan.
- 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.
18→26 gui.screen uses gui.common part of a loop✕
- Connections
- 3 pairs of types, where a type in gui.screen uses a type in gui.common.
- The types involved
ludusavi.gui.screen.Backup→ludusavi.gui.common.Operationludusavi.gui.screen.Restore→ludusavi.gui.common.Operationludusavi.gui.screen.screen$module→ludusavi.gui.common.Operation
- Direction
- gui.screen uses gui.common, so a change to gui.common can break gui.screen, while a change to gui.screen can't break gui.common.
- 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.
18→30 gui.screen uses resource.config part of a loop✕
- Connections
- 4 pairs of types, where a type in gui.screen uses a type in resource.config.
- The types involved
ludusavi.gui.screen.Backup→ludusavi.resource.config.Configludusavi.gui.screen.CustomGames→ludusavi.resource.config.Configludusavi.gui.screen.Restore→ludusavi.resource.config.Configludusavi.gui.screen.screen$module→ludusavi.resource.config.Config
- Direction
- gui.screen uses resource.config, so a change to resource.config can break gui.screen, while a change to gui.screen can't break resource.config.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
19→18 resource.cache uses gui.screen✕
- Connections
- 1 pair of types, where a type in resource.cache uses a type in gui.screen.
- The types involved
ludusavi.resource.cache.Cache→ludusavi.gui.screen.Backup
- Direction
- resource.cache uses gui.screen, so a change to gui.screen can break resource.cache, while a change to resource.cache can't break gui.screen.
- Position
- Below the diagonal: resource.cache uses a module listed above it, which is the healthy direction.
19→20 resource.cache uses resource.manifest part of a loop✕
- Connections
- 1 pair of types, where a type in resource.cache uses a type in resource.manifest.
- The types involved
ludusavi.resource.cache.Cache→ludusavi.resource.manifest.ManifestUpdate
- Direction
- resource.cache uses resource.manifest, so a change to resource.manifest can break resource.cache, while a change to resource.cache can't break resource.manifest.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
19→30 resource.cache uses resource.config part of a loop✕
- Connections
- 2 pairs of types, where a type in resource.cache uses a type in resource.config.
- The types involved
ludusavi.resource.cache.Cache→ludusavi.resource.config.Configludusavi.resource.cache.Cache→ludusavi.resource.config.Root
- Direction
- resource.cache uses resource.config, so a change to resource.config can break resource.cache, while a change to resource.cache can't break resource.config.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
19→34 resource.cache uses api.parameters part of a loop✕
- Connections
- 1 pair of types, where a type in resource.cache uses a type in api.parameters.
- The types involved
ludusavi.resource.cache.Cache→ludusavi.api.parameters.Restore
- Direction
- resource.cache uses api.parameters, so a change to api.parameters can break resource.cache, while a change to resource.cache can't break api.parameters.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
20→3 resource.manifest uses prelude✕
- Connections
- 1 pair of types, where a type in resource.manifest uses a type in prelude.
- The types involved
ludusavi.resource.manifest.Manifest→ludusavi.prelude.Security
- Direction
- resource.manifest uses prelude, so a change to prelude can break resource.manifest, while a change to resource.manifest can't break prelude.
- Position
- Below the diagonal: resource.manifest uses a module listed above it, which is the healthy direction.
20→19 resource.manifest uses resource.cache✕
- Connections
- 2 pairs of types, where a type in resource.manifest uses a type in resource.cache.
- The types involved
ludusavi.resource.manifest.Manifest→ludusavi.resource.cache.Cacheludusavi.resource.manifest.Secondary→ludusavi.resource.cache.Manifest
- Direction
- resource.manifest uses resource.cache, so a change to resource.cache can break resource.manifest, while a change to resource.manifest can't break resource.cache.
- Position
- Below the diagonal: resource.manifest uses a module listed above it, which is the healthy direction.
20→30 resource.manifest uses resource.config part of a loop✕
- Connections
- 3 pairs of types, where a type in resource.manifest uses a type in resource.config.
- The types involved
ludusavi.resource.manifest.Manifest→ludusavi.resource.config.Configludusavi.resource.manifest.Manifest→ludusavi.resource.config.CustomGameludusavi.resource.manifest.Manifest→ludusavi.resource.config.ManifestConfig
- Direction
- resource.manifest uses resource.config, so a change to resource.config can break resource.manifest, while a change to resource.manifest can't break resource.config.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
20→33 resource.manifest uses path part of a loop✕
- Connections
- 2 pairs of types, where a type in resource.manifest uses a type in path.
- The types involved
ludusavi.resource.manifest.Manifest→ludusavi.path.StrictPathludusavi.resource.manifest.Secondary→ludusavi.path.StrictPath
- Direction
- resource.manifest uses path, so a change to path can break resource.manifest, while a change to resource.manifest can't break path.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
21→19 scan.title uses resource.cache✕
- Connections
- 1 pair of types, where a type in scan.title uses a type in resource.cache.
- The types involved
ludusavi.scan.title.TitleFinder→ludusavi.resource.cache.Manifest
- Direction
- scan.title uses resource.cache, so a change to resource.cache can break scan.title, while a change to scan.title can't break resource.cache.
- Position
- Below the diagonal: scan.title uses a module listed above it, which is the healthy direction.
21→30 scan.title uses resource.config part of a loop✕
- Connections
- 1 pair of types, where a type in scan.title uses a type in resource.config.
- The types involved
ludusavi.scan.title.TitleFinder→ludusavi.resource.config.Config
- Direction
- scan.title uses resource.config, so a change to resource.config can break scan.title, while a change to scan.title can't break resource.config.
- 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.
22→1 lang uses cli.api.response✕
- Connections
- 1 pair of types, where a type in lang uses a type in cli.api.response.
- The types involved
ludusavi.lang.Translator→ludusavi.cli.api.response.Error
- Direction
- lang uses cli.api.response, so a change to cli.api.response can break lang, while a change to lang can't break cli.api.response.
- Position
- Below the diagonal: lang uses a module listed above it, which is the healthy direction.
22→2 lang uses gui.style✕
- Connections
- 1 pair of types, where a type in lang uses a type in gui.style.
- The types involved
ludusavi.lang.Translator→ludusavi.gui.style.Theme
- Direction
- lang uses gui.style, so a change to gui.style can break lang, while a change to lang can't break gui.style.
- Position
- Below the diagonal: lang uses a module listed above it, which is the healthy direction.
22→3 lang uses prelude✕
- Connections
- 1 pair of types, where a type in lang uses a type in prelude.
- The types involved
ludusavi.lang.Translator→ludusavi.prelude.CommandError
- Direction
- lang uses prelude, so a change to prelude can break lang, while a change to lang can't break prelude.
- Position
- Below the diagonal: lang uses a module listed above it, which is the healthy direction.
22→4 lang uses scan.change✕
- Connections
- 1 pair of types, where a type in lang uses a type in scan.change.
- The types involved
ludusavi.lang.Translator→ludusavi.scan.change.ScanChange
- Direction
- lang uses scan.change, so a change to scan.change can break lang, while a change to lang can't break scan.change.
- Position
- Below the diagonal: lang uses a module listed above it, which is the healthy direction.
22→12 lang uses scan.backup✕
- Connections
- 3 pairs of types, where a type in lang uses a type in scan.backup.
- The types involved
ludusavi.lang.Translator→ludusavi.scan.backup.BackupErrorludusavi.lang.Translator→ludusavi.scan.backup.OperationStatusludusavi.lang.Translator→ludusavi.scan.backup.OperationStepDecision
- Direction
- lang uses scan.backup, so a change to scan.backup can break lang, while a change to lang can't break scan.backup.
- Position
- Below the diagonal: lang uses a module listed above it, which is the healthy direction.
22→15 lang uses scan.game_filter✕
- Connections
- 4 pairs of types, where a type in lang uses a type in scan.game_filter.
- The types involved
ludusavi.lang.Translator→ludusavi.scan.game_filter.Changeludusavi.lang.Translator→ludusavi.scan.game_filter.Completenessludusavi.lang.Translator→ludusavi.scan.game_filter.Enablementludusavi.lang.Translator→ludusavi.scan.game_filter.Uniqueness
- Direction
- lang uses scan.game_filter, so a change to scan.game_filter can break lang, while a change to lang can't break scan.game_filter.
- Position
- Below the diagonal: lang uses a module listed above it, which is the healthy direction.
22→20 lang uses resource.manifest✕
- Connections
- 1 pair of types, where a type in lang uses a type in resource.manifest.
- The types involved
ludusavi.lang.Translator→ludusavi.resource.manifest.Store
- Direction
- lang uses resource.manifest, so a change to resource.manifest can break lang, while a change to lang can't break resource.manifest.
- Position
- Below the diagonal: lang uses a module listed above it, which is the healthy direction.
22→30 lang uses resource.config part of a loop✕
- Connections
- 5 pairs of types, where a type in lang uses a type in resource.config.
- The types involved
ludusavi.lang.Translator→ludusavi.resource.config.BackupFormatludusavi.lang.Translator→ludusavi.resource.config.CustomGameKindludusavi.lang.Translator→ludusavi.resource.config.RedirectKindludusavi.lang.Translator→ludusavi.resource.config.SortKeyludusavi.lang.Translator→ludusavi.resource.config.ZipCompression
- Direction
- lang uses resource.config, so a change to resource.config can break lang, while a change to lang can't break resource.config.
- 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.
22→33 lang uses path part of a loop✕
- Connections
- 1 pair of types, where a type in lang uses a type in path.
- The types involved
ludusavi.lang.Translator→ludusavi.path.StrictPath
- Direction
- lang uses path, so a change to path can break lang, while a change to lang can't break path.
- 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→19 scan.launchers uses resource.cache✕
- Connections
- 1 pair of types, where a type in scan.launchers uses a type in resource.cache.
- The types involved
ludusavi.scan.launchers.Launchers→ludusavi.resource.cache.Manifest
- Direction
- scan.launchers uses resource.cache, so a change to resource.cache can break scan.launchers, while a change to scan.launchers can't break resource.cache.
- Position
- Below the diagonal: scan.launchers uses a module listed above it, which is the healthy direction.
23→20 scan.launchers uses resource.manifest✕
- Connections
- 1 pair of types, where a type in scan.launchers uses a type in resource.manifest.
- The types involved
ludusavi.scan.launchers.LauncherGame→ludusavi.resource.manifest.Os
- Direction
- scan.launchers uses resource.manifest, so a change to resource.manifest can break scan.launchers, while a change to scan.launchers can't break resource.manifest.
- Position
- Below the diagonal: scan.launchers uses a module listed above it, which is the healthy direction.
23→21 scan.launchers uses scan.title✕
- Connections
- 1 pair of types, where a type in scan.launchers uses a type in scan.title.
- The types involved
ludusavi.scan.launchers.Launchers→ludusavi.scan.title.TitleFinder
- Direction
- scan.launchers uses scan.title, so a change to scan.title can break scan.launchers, while a change to scan.launchers can't break scan.title.
- Position
- Below the diagonal: scan.launchers uses a module listed above it, which is the healthy direction.
23→30 scan.launchers uses resource.config part of a loop✕
- Connections
- 1 pair of types, where a type in scan.launchers uses a type in resource.config.
- The types involved
ludusavi.scan.launchers.Launchers→ludusavi.resource.config.Root
- Direction
- scan.launchers uses resource.config, so a change to resource.config can break scan.launchers, while a change to scan.launchers can't break resource.config.
- 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→33 scan.launchers uses path part of a loop✕
- Connections
- 2 pairs of types, where a type in scan.launchers uses a type in path.
- The types involved
ludusavi.scan.launchers.LauncherGame→ludusavi.path.StrictPathludusavi.scan.launchers.Launchers→ludusavi.path.StrictPath
- Direction
- scan.launchers uses path, so a change to path can break scan.launchers, while a change to scan.launchers can't break path.
- 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.
24→20 scan.launchers.lutris.spec uses resource.manifest✕
- Connections
- 1 pair of types, where a type in scan.launchers.lutris.spec uses a type in resource.manifest.
- The types involved
ludusavi.scan.launchers.lutris.spec.Data→ludusavi.resource.manifest.Game
- Direction
- scan.launchers.lutris.spec uses resource.manifest, so a change to resource.manifest can break scan.launchers.lutris.spec, while a change to scan.launchers.lutris.spec can't break resource.manifest.
- Position
- Below the diagonal: scan.launchers.lutris.spec uses a module listed above it, which is the healthy direction.
24→33 scan.launchers.lutris.spec uses path part of a loop✕
- Connections
- 1 pair of types, where a type in scan.launchers.lutris.spec uses a type in path.
- The types involved
ludusavi.scan.launchers.lutris.spec.Game→ludusavi.path.StrictPath
- Direction
- scan.launchers.lutris.spec uses path, so a change to path can break scan.launchers.lutris.spec, while a change to scan.launchers.lutris.spec can't break path.
- 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→6 scan uses scan.saves✕
- Connections
- 1 pair of types, where a type in scan uses a type in scan.saves.
- The types involved
ludusavi.scan.scan$module→ludusavi.scan.saves.ScannedFile
- Direction
- scan uses scan.saves, so a change to scan.saves can break scan, while a change to scan can't break scan.saves.
- Position
- Below the diagonal: scan uses a module listed above it, which is the healthy direction.
25→10 scan uses scan.layout✕
- Connections
- 2 pairs of types, where a type in scan uses a type in scan.layout.
- The types involved
ludusavi.scan.scan$module→ludusavi.scan.layout.BackupSemanticsludusavi.scan.scan$module→ludusavi.scan.layout.LatestBackup
- Direction
- scan uses scan.layout, so a change to scan.layout can break scan, while a change to scan can't break scan.layout.
- Position
- Below the diagonal: scan uses a module listed above it, which is the healthy direction.
25→11 scan uses scan.preview✕
- Connections
- 1 pair of types, where a type in scan uses a type in scan.preview.
- The types involved
ludusavi.scan.scan$module→ludusavi.scan.preview.ScanInfo
- Direction
- scan uses scan.preview, so a change to scan.preview can break scan, while a change to scan can't break scan.preview.
- Position
- Below the diagonal: scan uses a module listed above it, which is the healthy direction.
25→12 scan uses scan.backup✕
- Connections
- 1 pair of types, where a type in scan uses a type in scan.backup.
- The types involved
ludusavi.scan.scan$module→ludusavi.scan.backup.BackupInfo
- Direction
- scan uses scan.backup, so a change to scan.backup can break scan, while a change to scan can't break scan.backup.
- Position
- Below the diagonal: scan uses a module listed above it, which is the healthy direction.
25→20 scan uses resource.manifest✕
- Connections
- 4 pairs of types, where a type in scan uses a type in resource.manifest.
- The types involved
ludusavi.scan.scan$module→ludusavi.resource.manifest.Gameludusavi.scan.scan$module→ludusavi.resource.manifest.GameFileEntryludusavi.scan.scan$module→ludusavi.resource.manifest.IdSetludusavi.scan.scan$module→ludusavi.resource.manifest.Os
- Direction
- scan uses resource.manifest, so a change to resource.manifest can break scan, while a change to scan can't break resource.manifest.
- Position
- Below the diagonal: scan uses a module listed above it, which is the healthy direction.
25→23 scan uses scan.launchers✕
- Connections
- 1 pair of types, where a type in scan uses a type in scan.launchers.
- The types involved
ludusavi.scan.scan$module→ludusavi.scan.launchers.Launchers
- Direction
- scan uses scan.launchers, so a change to scan.launchers can break scan, while a change to scan can't break scan.launchers.
- Position
- Below the diagonal: scan uses a module listed above it, which is the healthy direction.
25→30 scan uses resource.config part of a loop✕
- Connections
- 6 pairs of types, where a type in scan uses a type in resource.config.
- The types involved
ludusavi.scan.scan$module→ludusavi.resource.config.BackupFilterludusavi.scan.scan$module→ludusavi.resource.config.Configludusavi.scan.scan$module→ludusavi.resource.config.Rootludusavi.scan.scan$module→ludusavi.resource.config.SortKeyludusavi.scan.scan$module→ludusavi.resource.config.ToggledPathsludusavi.scan.scan$module→ludusavi.resource.config.ToggledRegistry
- Direction
- scan uses resource.config, so a change to resource.config can break scan, while a change to scan can't break resource.config.
- 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→33 scan uses path part of a loop✕
- Connections
- 1 pair of types, where a type in scan uses a type in path.
- The types involved
ludusavi.scan.scan$module→ludusavi.path.StrictPath
- Direction
- scan uses path, so a change to path can break scan, while a change to scan can't break path.
- 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.
26→1 gui.common uses cli.api.response✕
- Connections
- 1 pair of types, where a type in gui.common uses a type in cli.api.response.
- The types involved
ludusavi.gui.common.Operation→ludusavi.cli.api.response.Error
- Direction
- gui.common uses cli.api.response, so a change to cli.api.response can break gui.common, while a change to gui.common can't break cli.api.response.
- Position
- Below the diagonal: gui.common uses a module listed above it, which is the healthy direction.
26→2 gui.common uses gui.style✕
- Connections
- 1 pair of types, where a type in gui.common uses a type in gui.style.
- The types involved
ludusavi.gui.common.ScrollSubject→ludusavi.gui.style.Scrollable
- Direction
- gui.common uses gui.style, so a change to gui.style can break gui.common, while a change to gui.common can't break gui.style.
- Position
- Below the diagonal: gui.common uses a module listed above it, which is the healthy direction.
26→3 gui.common uses prelude✕
- Connections
- 3 pairs of types, where a type in gui.common uses a type in prelude.
- The types involved
ludusavi.gui.common.Operation→ludusavi.prelude.Finalityludusavi.gui.common.Operation→ludusavi.prelude.SyncDirectionludusavi.gui.common.UndoSubject→ludusavi.prelude.Privacy
- Direction
- gui.common uses prelude, so a change to prelude can break gui.common, while a change to gui.common can't break prelude.
- Position
- Below the diagonal: gui.common uses a module listed above it, which is the healthy direction.
26→24 gui.common uses scan.launchers.lutris.spec✕
- Connections
- 2 pairs of types, where a type in gui.common uses a type in scan.launchers.lutris.spec.
- The types involved
ludusavi.gui.common.ScrollSubject→ludusavi.scan.launchers.lutris.spec.Idludusavi.gui.common.UndoSubject→ludusavi.scan.launchers.lutris.spec.Id
- Direction
- gui.common uses scan.launchers.lutris.spec, so a change to scan.launchers.lutris.spec can break gui.common, while a change to gui.common can't break scan.launchers.lutris.spec.
- Position
- Below the diagonal: gui.common uses a module listed above it, which is the healthy direction.
26→25 gui.common uses scan✕
- Connections
- 2 pairs of types, where a type in gui.common uses a type in scan.
- The types involved
ludusavi.gui.common.GameAction→ludusavi.scan.ScanKindludusavi.gui.common.ScrollSubject→ludusavi.scan.ScanKind
- Direction
- gui.common uses scan, so a change to scan can break gui.common, while a change to gui.common can't break scan.
- Position
- Below the diagonal: gui.common uses a module listed above it, which is the healthy direction.
27→1 gui.app uses cli.api.response✕
- Connections
- 1 pair of types, where a type in gui.app uses a type in cli.api.response.
- The types involved
ludusavi.gui.app.App→ludusavi.cli.api.response.Error
- Direction
- gui.app uses cli.api.response, so a change to cli.api.response can break gui.app, while a change to gui.app can't break cli.api.response.
- Position
- Below the diagonal: gui.app uses a module listed above it, which is the healthy direction.
27→2 gui.app uses gui.style✕
- Connections
- 1 pair of types, where a type in gui.app uses a type in gui.style.
- The types involved
ludusavi.gui.app.App→ludusavi.gui.style.Theme
- Direction
- gui.app uses gui.style, so a change to gui.style can break gui.app, while a change to gui.app can't break gui.style.
- Position
- Below the diagonal: gui.app uses a module listed above it, which is the healthy direction.
27→3 gui.app uses prelude✕
- Connections
- 3 pairs of types, where a type in gui.app uses a type in prelude.
- The types involved
ludusavi.gui.app.App→ludusavi.prelude.Finalityludusavi.gui.app.App→ludusavi.prelude.Securityludusavi.gui.app.App→ludusavi.prelude.SyncDirection
- Direction
- gui.app uses prelude, so a change to prelude can break gui.app, while a change to gui.app can't break prelude.
- Position
- Below the diagonal: gui.app uses a module listed above it, which is the healthy direction.
27→7 gui.app uses gui.shortcuts✕
- Connections
- 1 pair of types, where a type in gui.app uses a type in gui.shortcuts.
- The types involved
ludusavi.gui.app.App→ludusavi.gui.shortcuts.TextHistories
- Direction
- gui.app uses gui.shortcuts, so a change to gui.shortcuts can break gui.app, while a change to gui.app can't break gui.shortcuts.
- Position
- Below the diagonal: gui.app uses a module listed above it, which is the healthy direction.
27→8 gui.app uses gui.modal✕
- Connections
- 2 pairs of types, where a type in gui.app uses a type in gui.modal.
- The types involved
ludusavi.gui.app.App→ludusavi.gui.modal.Kindludusavi.gui.app.App→ludusavi.gui.modal.Modal
- Direction
- gui.app uses gui.modal, so a change to gui.modal can break gui.app, while a change to gui.app can't break gui.modal.
- Position
- Below the diagonal: gui.app uses a module listed above it, which is the healthy direction.
27→18 gui.app uses gui.screen✕
- Connections
- 2 pairs of types, where a type in gui.app uses a type in gui.screen.
- The types involved
ludusavi.gui.app.App→ludusavi.gui.screen.Backupludusavi.gui.app.App→ludusavi.gui.screen.CustomGames
- Direction
- gui.app uses gui.screen, so a change to gui.screen can break gui.app, while a change to gui.app can't break gui.screen.
- Position
- Below the diagonal: gui.app uses a module listed above it, which is the healthy direction.
27→19 gui.app uses resource.cache✕
- Connections
- 2 pairs of types, where a type in gui.app uses a type in resource.cache.
- The types involved
ludusavi.gui.app.App→ludusavi.resource.cache.Cacheludusavi.gui.app.LoadedManifest→ludusavi.resource.cache.Manifest
- Direction
- gui.app uses resource.cache, so a change to resource.cache can break gui.app, while a change to gui.app can't break resource.cache.
- Position
- Below the diagonal: gui.app uses a module listed above it, which is the healthy direction.
27→26 gui.app uses gui.common✕
- Connections
- 9 pairs of types, where a type in gui.app uses a type in gui.common.
- The types involved
ludusavi.gui.app.App→ludusavi.gui.common.BackupPhaseludusavi.gui.app.App→ludusavi.gui.common.Flagsludusavi.gui.app.App→ludusavi.gui.common.GameSelectionludusavi.gui.app.App→ludusavi.gui.common.Messageludusavi.gui.app.App→ludusavi.gui.common.Operationludusavi.gui.app.App→ludusavi.gui.common.RestorePhaseludusavi.gui.app.App→ludusavi.gui.common.Screenludusavi.gui.app.App→ludusavi.gui.common.ScrollSubjectludusavi.gui.app.App→ludusavi.gui.common.ValidatePhase
- Direction
- gui.app uses gui.common, so a change to gui.common can break gui.app, while a change to gui.app can't break gui.common.
- Position
- Below the diagonal: gui.app uses a module listed above it, which is the healthy direction.
27→29 gui.app uses cloud part of a loop✕
- Connections
- 1 pair of types, where a type in gui.app uses a type in cloud.
- The types involved
ludusavi.gui.app.App→ludusavi.cloud.Remote
- Direction
- gui.app uses cloud, so a change to cloud can break gui.app, while a change to gui.app can't break cloud.
- 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.
27→30 gui.app uses resource.config part of a loop✕
- Connections
- 4 pairs of types, where a type in gui.app uses a type in resource.config.
- The types involved
ludusavi.gui.app.App→ludusavi.resource.config.Configludusavi.gui.app.App→ludusavi.resource.config.CustomGameludusavi.gui.app.App→ludusavi.resource.config.ManifestConfigludusavi.gui.app.Executor→ludusavi.resource.config.Runtime
- Direction
- gui.app uses resource.config, so a change to resource.config can break gui.app, while a change to gui.app can't break resource.config.
- 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.
27→33 gui.app uses path part of a loop✕
- Connections
- 1 pair of types, where a type in gui.app uses a type in path.
- The types involved
ludusavi.gui.app.App→ludusavi.path.StrictPath
- Direction
- gui.app uses path, so a change to path can break gui.app, while a change to gui.app can't break path.
- 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.
27→34 gui.app uses api.parameters part of a loop✕
- Connections
- 1 pair of types, where a type in gui.app uses a type in api.parameters.
- The types involved
ludusavi.gui.app.App→ludusavi.api.parameters.Restore
- Direction
- gui.app uses api.parameters, so a change to api.parameters can break gui.app, while a change to gui.app can't break api.parameters.
- 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→2 gui.badge uses gui.style✕
- Connections
- 1 pair of types, where a type in gui.badge uses a type in gui.style.
- The types involved
ludusavi.gui.badge.Badge→ludusavi.gui.style.Container
- Direction
- gui.badge uses gui.style, so a change to gui.style can break gui.badge, while a change to gui.badge can't break gui.style.
- Position
- Below the diagonal: gui.badge uses a module listed above it, which is the healthy direction.
28→4 gui.badge uses scan.change✕
- Connections
- 1 pair of types, where a type in gui.badge uses a type in scan.change.
- The types involved
ludusavi.gui.badge.Badge→ludusavi.scan.change.ScanChange
- Direction
- gui.badge uses scan.change, so a change to scan.change can break gui.badge, while a change to gui.badge can't break scan.change.
- Position
- Below the diagonal: gui.badge uses a module listed above it, which is the healthy direction.
28→26 gui.badge uses gui.common✕
- Connections
- 1 pair of types, where a type in gui.badge uses a type in gui.common.
- The types involved
ludusavi.gui.badge.Badge→ludusavi.gui.common.Message
- Direction
- gui.badge uses gui.common, so a change to gui.common can break gui.badge, while a change to gui.badge can't break gui.common.
- Position
- Below the diagonal: gui.badge uses a module listed above it, which is the healthy direction.
29→3 cloud uses prelude✕
- Connections
- 3 pairs of types, where a type in cloud uses a type in prelude.
- The types involved
ludusavi.cloud.Rclone→ludusavi.prelude.Finalityludusavi.cloud.Rclone→ludusavi.prelude.Privacyludusavi.cloud.Rclone→ludusavi.prelude.SyncDirection
- Direction
- cloud uses prelude, so a change to prelude can break cloud, while a change to cloud can't break prelude.
- Position
- Below the diagonal: cloud uses a module listed above it, which is the healthy direction.
29→4 cloud uses scan.change✕
- Connections
- 1 pair of types, where a type in cloud uses a type in scan.change.
- The types involved
ludusavi.cloud.CloudChange→ludusavi.scan.change.ScanChange
- Direction
- cloud uses scan.change, so a change to scan.change can break cloud, while a change to cloud can't break scan.change.
- Position
- Below the diagonal: cloud uses a module listed above it, which is the healthy direction.
29→27 cloud uses gui.app✕
- Connections
- 1 pair of types, where a type in cloud uses a type in gui.app.
- The types involved
ludusavi.cloud.Rclone→ludusavi.gui.app.App
- Direction
- cloud uses gui.app, so a change to gui.app can break cloud, while a change to cloud can't break gui.app.
- Position
- Below the diagonal: cloud uses a module listed above it, which is the healthy direction.
29→30 cloud uses resource.config part of a loop✕
- Connections
- 1 pair of types, where a type in cloud uses a type in resource.config.
- The types involved
ludusavi.cloud.cloud$module→ludusavi.resource.config.Config
- Direction
- cloud uses resource.config, so a change to resource.config can break cloud, while a change to cloud can't break resource.config.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
29→33 cloud uses path part of a loop✕
- Connections
- 1 pair of types, where a type in cloud uses a type in path.
- The types involved
ludusavi.cloud.Rclone→ludusavi.path.StrictPath
- Direction
- cloud uses path, so a change to path can break cloud, while a change to cloud can't break path.
- 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.
30→2 resource.config uses gui.style✕
- Connections
- 1 pair of types, where a type in resource.config uses a type in gui.style.
- The types involved
ludusavi.resource.config.Config→ludusavi.gui.style.Theme
- Direction
- resource.config uses gui.style, so a change to gui.style can break resource.config, while a change to resource.config can't break gui.style.
- Position
- Below the diagonal: resource.config uses a module listed above it, which is the healthy direction.
30→3 resource.config uses prelude✕
- Connections
- 1 pair of types, where a type in resource.config uses a type in prelude.
- The types involved
ludusavi.resource.config.Runtime→ludusavi.prelude.Security
- Direction
- resource.config uses prelude, so a change to prelude can break resource.config, while a change to resource.config can't break prelude.
- Position
- Below the diagonal: resource.config uses a module listed above it, which is the healthy direction.
30→9 resource.config uses scan.registry✕
- Connections
- 2 pairs of types, where a type in resource.config uses a type in scan.registry.
- The types involved
ludusavi.resource.config.BackupFilter→ludusavi.scan.registry.RegistryItemludusavi.resource.config.ToggledRegistry→ludusavi.scan.registry.RegistryItem
- Direction
- resource.config uses scan.registry, so a change to scan.registry can break resource.config, while a change to resource.config can't break scan.registry.
- Position
- Below the diagonal: resource.config uses a module listed above it, which is the healthy direction.
30→20 resource.config uses resource.manifest✕
- Connections
- 4 pairs of types, where a type in resource.config uses a type in resource.manifest.
- The types involved
ludusavi.resource.config.BackupFilter→ludusavi.resource.manifest.CloudMetadataludusavi.resource.config.CloudFilter→ludusavi.resource.manifest.CloudMetadataludusavi.resource.config.ManifestConfig→ludusavi.resource.manifest.Secondaryludusavi.resource.config.Root→ludusavi.resource.manifest.Store
- Direction
- resource.config uses resource.manifest, so a change to resource.manifest can break resource.config, while a change to resource.config can't break resource.manifest.
- Position
- Below the diagonal: resource.config uses a module listed above it, which is the healthy direction.
30→22 resource.config uses lang✕
- Connections
- 1 pair of types, where a type in resource.config uses a type in lang.
- The types involved
ludusavi.resource.config.Config→ludusavi.lang.Language
- Direction
- resource.config uses lang, so a change to lang can break resource.config, while a change to resource.config can't break lang.
- Position
- Below the diagonal: resource.config uses a module listed above it, which is the healthy direction.
30→25 resource.config uses scan✕
- Connections
- 1 pair of types, where a type in resource.config uses a type in scan.
- The types involved
ludusavi.resource.config.Config→ludusavi.scan.ScanKind
- Direction
- resource.config uses scan, so a change to scan can break resource.config, while a change to resource.config can't break scan.
- Position
- Below the diagonal: resource.config uses a module listed above it, which is the healthy direction.
30→27 resource.config uses gui.app✕
- Connections
- 1 pair of types, where a type in resource.config uses a type in gui.app.
- The types involved
ludusavi.resource.config.Apps→ludusavi.gui.app.App
- Direction
- resource.config uses gui.app, so a change to gui.app can break resource.config, while a change to resource.config can't break gui.app.
- Position
- Below the diagonal: resource.config uses a module listed above it, which is the healthy direction.
30→29 resource.config uses cloud✕
- Connections
- 1 pair of types, where a type in resource.config uses a type in cloud.
- The types involved
ludusavi.resource.config.Cloud→ludusavi.cloud.Remote
- Direction
- resource.config uses cloud, so a change to cloud can break resource.config, while a change to resource.config can't break cloud.
- Position
- Below the diagonal: resource.config uses a module listed above it, which is the healthy direction.
30→33 resource.config uses path part of a loop✕
- Connections
- 10 pairs of types, where a type in resource.config uses a type in path.
- The types involved
ludusavi.resource.config.App→ludusavi.path.StrictPathludusavi.resource.config.BackupConfig→ludusavi.path.StrictPathludusavi.resource.config.BackupFilter→ludusavi.path.StrictPathludusavi.resource.config.Config→ludusavi.path.StrictPathludusavi.resource.config.RedirectConfig→ludusavi.path.StrictPathludusavi.resource.config.RestoreConfig→ludusavi.path.StrictPathludusavi.resource.config.Root→ludusavi.path.StrictPathludusavi.resource.config.SecondaryManifestConfig→ludusavi.path.StrictPathludusavi.resource.config.ToggledPaths→ludusavi.path.StrictPathludusavi.resource.config.config$module→ludusavi.path.StrictPath
- Direction
- resource.config uses path, so a change to path can break resource.config, while a change to resource.config can't break path.
- 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.
31→2 gui.editor uses gui.style✕
- Connections
- 1 pair of types, where a type in gui.editor uses a type in gui.style.
- The types involved
ludusavi.gui.editor.editor$module→ludusavi.gui.style.Container
- Direction
- gui.editor uses gui.style, so a change to gui.style can break gui.editor, while a change to gui.editor can't break gui.style.
- Position
- Below the diagonal: gui.editor uses a module listed above it, which is the healthy direction.
31→7 gui.editor uses gui.shortcuts✕
- Connections
- 1 pair of types, where a type in gui.editor uses a type in gui.shortcuts.
- The types involved
ludusavi.gui.editor.editor$module→ludusavi.gui.shortcuts.TextHistories
- Direction
- gui.editor uses gui.shortcuts, so a change to gui.shortcuts can break gui.editor, while a change to gui.editor can't break gui.shortcuts.
- Position
- Below the diagonal: gui.editor uses a module listed above it, which is the healthy direction.
31→16 gui.editor uses gui.search✕
- Connections
- 1 pair of types, where a type in gui.editor uses a type in gui.search.
- The types involved
ludusavi.gui.editor.editor$module→ludusavi.gui.search.CustomGamesFilter
- Direction
- gui.editor uses gui.search, so a change to gui.search can break gui.editor, while a change to gui.editor can't break gui.search.
- Position
- Below the diagonal: gui.editor uses a module listed above it, which is the healthy direction.
31→19 gui.editor uses resource.cache✕
- Connections
- 2 pairs of types, where a type in gui.editor uses a type in resource.cache.
- The types involved
ludusavi.gui.editor.editor$module→ludusavi.resource.cache.Cacheludusavi.gui.editor.editor$module→ludusavi.resource.cache.Manifest
- Direction
- gui.editor uses resource.cache, so a change to resource.cache can break gui.editor, while a change to gui.editor can't break resource.cache.
- Position
- Below the diagonal: gui.editor uses a module listed above it, which is the healthy direction.
31→30 gui.editor uses resource.config✕
- Connections
- 1 pair of types, where a type in gui.editor uses a type in resource.config.
- The types involved
ludusavi.gui.editor.editor$module→ludusavi.resource.config.Config
- Direction
- gui.editor uses resource.config, so a change to resource.config can break gui.editor, while a change to gui.editor can't break resource.config.
- Position
- Below the diagonal: gui.editor uses a module listed above it, which is the healthy direction.
32→10 scan.semantic uses scan.layout✕
- Connections
- 1 pair of types, where a type in scan.semantic uses a type in scan.layout.
- The types involved
ludusavi.scan.semantic.semantic$module→ludusavi.scan.layout.BackupSemantics
- Direction
- scan.semantic uses scan.layout, so a change to scan.layout can break scan.semantic, while a change to scan.semantic can't break scan.layout.
- Position
- Below the diagonal: scan.semantic uses a module listed above it, which is the healthy direction.
32→30 scan.semantic uses resource.config✕
- Connections
- 1 pair of types, where a type in scan.semantic uses a type in resource.config.
- The types involved
ludusavi.scan.semantic.Wine→ludusavi.resource.config.Config
- Direction
- scan.semantic uses resource.config, so a change to resource.config can break scan.semantic, while a change to scan.semantic can't break resource.config.
- Position
- Below the diagonal: scan.semantic uses a module listed above it, which is the healthy direction.
32→33 scan.semantic uses path part of a loop✕
- Connections
- 1 pair of types, where a type in scan.semantic uses a type in path.
- The types involved
ludusavi.scan.semantic.semantic$module→ludusavi.path.StrictPath
- Direction
- scan.semantic uses path, so a change to path can break scan.semantic, while a change to scan.semantic can't break path.
- 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.
33→32 path uses scan.semantic✕
- Connections
- 2 pairs of types, where a type in path uses a type in scan.semantic.
- The types involved
ludusavi.path.StrictPath→ludusavi.scan.semantic.Pathludusavi.path.path$module→ludusavi.scan.semantic.Path
- Direction
- path uses scan.semantic, so a change to scan.semantic can break path, while a change to path can't break scan.semantic.
- Position
- Below the diagonal: path uses a module listed above it, which is the healthy direction.
34→3 api.parameters uses prelude✕
- Connections
- 4 pairs of types, where a type in api.parameters uses a type in prelude.
- The types involved
ludusavi.api.parameters.BackUp→ludusavi.prelude.Finalityludusavi.api.parameters.BackUp→ludusavi.prelude.SyncDirectionludusavi.api.parameters.Restore→ludusavi.prelude.Finalityludusavi.api.parameters.Restore→ludusavi.prelude.SyncDirection
- Direction
- api.parameters uses prelude, so a change to prelude can break api.parameters, while a change to api.parameters can't break prelude.
- Position
- Below the diagonal: api.parameters uses a module listed above it, which is the healthy direction.
34→33 api.parameters uses path✕
- Connections
- 1 pair of types, where a type in api.parameters uses a type in path.
- The types involved
ludusavi.api.parameters.BackUp→ludusavi.path.StrictPath
- Direction
- api.parameters uses path, so a change to path can break api.parameters, while a change to api.parameters can't break path.
- Position
- Below the diagonal: api.parameters uses a module listed above it, which is the healthy direction.
35→1 cli uses cli.api.response✕
- Connections
- 1 pair of types, where a type in cli uses a type in cli.api.response.
- The types involved
ludusavi.cli.cli$module→ludusavi.cli.api.response.Error
- Direction
- cli uses cli.api.response, so a change to cli.api.response can break cli, while a change to cli can't break cli.api.response.
- Position
- Below the diagonal: cli uses a module listed above it, which is the healthy direction.
35→2 cli uses gui.style✕
- Connections
- 1 pair of types, where a type in cli uses a type in gui.style.
- The types involved
ludusavi.cli.cli$module→ludusavi.gui.style.ProgressBar
- Direction
- cli uses gui.style, so a change to gui.style can break cli, while a change to cli can't break gui.style.
- Position
- Below the diagonal: cli uses a module listed above it, which is the healthy direction.
35→3 cli uses prelude✕
- Connections
- 2 pairs of types, where a type in cli uses a type in prelude.
- The types involved
ludusavi.cli.cli$module→ludusavi.prelude.Finalityludusavi.cli.cli$module→ludusavi.prelude.SyncDirection
- Direction
- cli uses prelude, so a change to prelude can break cli, while a change to cli can't break prelude.
- Position
- Below the diagonal: cli uses a module listed above it, which is the healthy direction.
35→19 cli uses resource.cache✕
- Connections
- 1 pair of types, where a type in cli uses a type in resource.cache.
- The types involved
ludusavi.cli.cli$module→ludusavi.resource.cache.Cache
- Direction
- cli uses resource.cache, so a change to resource.cache can break cli, while a change to cli can't break resource.cache.
- Position
- Below the diagonal: cli uses a module listed above it, which is the healthy direction.
35→21 cli uses scan.title✕
- Connections
- 1 pair of types, where a type in cli uses a type in scan.title.
- The types involved
ludusavi.cli.cli$module→ludusavi.scan.title.TitleFinder
- Direction
- cli uses scan.title, so a change to scan.title can break cli, while a change to cli can't break scan.title.
- Position
- Below the diagonal: cli uses a module listed above it, which is the healthy direction.
35→29 cli uses cloud✕
- Connections
- 1 pair of types, where a type in cli uses a type in cloud.
- The types involved
ludusavi.cli.cli$module→ludusavi.cloud.Remote
- Direction
- cli uses cloud, so a change to cloud can break cli, while a change to cli can't break cloud.
- Position
- Below the diagonal: cli uses a module listed above it, which is the healthy direction.
35→30 cli uses resource.config✕
- Connections
- 1 pair of types, where a type in cli uses a type in resource.config.
- The types involved
ludusavi.cli.cli$module→ludusavi.resource.config.Config
- Direction
- cli uses resource.config, so a change to resource.config can break cli, while a change to cli can't break resource.config.
- Position
- Below the diagonal: cli uses a module listed above it, which is the healthy direction.
35→33 cli uses path✕
- Connections
- 1 pair of types, where a type in cli uses a type in path.
- The types involved
ludusavi.cli.cli$module→ludusavi.path.StrictPath
- Direction
- cli uses path, so a change to path can break cli, while a change to cli can't break path.
- Position
- Below the diagonal: cli uses a module listed above it, which is the healthy direction.
36→1 cli.api uses cli.api.response✕
- Connections
- 1 pair of types, where a type in cli.api uses a type in cli.api.response.
- The types involved
ludusavi.cli.api.api$module→ludusavi.cli.api.response.Error
- Direction
- cli.api uses cli.api.response, so a change to cli.api.response can break cli.api, while a change to cli.api can't break cli.api.response.
- Position
- Below the diagonal: cli.api uses a module listed above it, which is the healthy direction.
36→19 cli.api uses resource.cache✕
- Connections
- 1 pair of types, where a type in cli.api uses a type in resource.cache.
- The types involved
ludusavi.cli.api.api$module→ludusavi.resource.cache.Manifest
- Direction
- cli.api uses resource.cache, so a change to resource.cache can break cli.api, while a change to cli.api can't break resource.cache.
- Position
- Below the diagonal: cli.api uses a module listed above it, which is the healthy direction.
36→30 cli.api uses resource.config✕
- Connections
- 1 pair of types, where a type in cli.api uses a type in resource.config.
- The types involved
ludusavi.cli.api.api$module→ludusavi.resource.config.Config
- Direction
- cli.api uses resource.config, so a change to resource.config can break cli.api, while a change to cli.api can't break resource.config.
- Position
- Below the diagonal: cli.api uses a module listed above it, which is the healthy direction.
36→33 cli.api uses path✕
- Connections
- 1 pair of types, where a type in cli.api uses a type in path.
- The types involved
ludusavi.cli.api.ConfigOverride→ludusavi.path.StrictPath
- Direction
- cli.api uses path, so a change to path can break cli.api, while a change to cli.api can't break path.
- Position
- Below the diagonal: cli.api uses a module listed above it, which is the healthy direction.
37→4 report uses scan.change✕
- Connections
- 4 pairs of types, where a type in report uses a type in scan.change.
- The types involved
ludusavi.report.ApiFile→ludusavi.scan.change.ScanChangeludusavi.report.ApiRegistry→ludusavi.scan.change.ScanChangeludusavi.report.ApiRegistryValue→ludusavi.scan.change.ScanChangeludusavi.report.CloudEntry→ludusavi.scan.change.ScanChange
- Direction
- report uses scan.change, so a change to scan.change can break report, while a change to report can't break scan.change.
- Position
- Below the diagonal: report uses a module listed above it, which is the healthy direction.
37→11 report uses scan.preview✕
- Connections
- 1 pair of types, where a type in report uses a type in scan.preview.
- The types involved
ludusavi.report.Reporter→ludusavi.scan.preview.ScanInfo
- Direction
- report uses scan.preview, so a change to scan.preview can break report, while a change to report can't break scan.preview.
- Position
- Below the diagonal: report uses a module listed above it, which is the healthy direction.
37→12 report uses scan.backup✕
- Connections
- 4 pairs of types, where a type in report uses a type in scan.backup.
- The types involved
ludusavi.report.ApiOutput→ludusavi.scan.backup.OperationStatusludusavi.report.Reporter→ludusavi.scan.backup.BackupInfoludusavi.report.Reporter→ludusavi.scan.backup.OperationStepDecisionludusavi.report.SaveError→ludusavi.scan.backup.BackupError
- Direction
- report uses scan.backup, so a change to scan.backup can break report, while a change to report can't break scan.backup.
- Position
- Below the diagonal: report uses a module listed above it, which is the healthy direction.
37→13 report uses scan.duplicate✕
- Connections
- 1 pair of types, where a type in report uses a type in scan.duplicate.
- The types involved
ludusavi.report.Reporter→ludusavi.scan.duplicate.DuplicateDetector
- Direction
- report uses scan.duplicate, so a change to scan.duplicate can break report, while a change to report can't break scan.duplicate.
- Position
- Below the diagonal: report uses a module listed above it, which is the healthy direction.
37→20 report uses resource.manifest✕
- Connections
- 1 pair of types, where a type in report uses a type in resource.manifest.
- The types involved
ludusavi.report.ApiBackup→ludusavi.resource.manifest.Os
- Direction
- report uses resource.manifest, so a change to resource.manifest can break report, while a change to report can't break resource.manifest.
- Position
- Below the diagonal: report uses a module listed above it, which is the healthy direction.
37→33 report uses path✕
- Connections
- 1 pair of types, where a type in report uses a type in path.
- The types involved
ludusavi.report.Reporter→ludusavi.path.StrictPath
- Direction
- report uses path, so a change to path can break report, while a change to report can't break path.
- Position
- Below the diagonal: report uses a module listed above it, which is the healthy direction.
38→33 resource.config.root uses path✕
- Connections
- 19 pairs of types, where a type in resource.config.root uses a type in path.
- The types involved
ludusavi.resource.config.root.Ea→ludusavi.path.StrictPathludusavi.resource.config.root.Epic→ludusavi.path.StrictPathludusavi.resource.config.root.Faugus→ludusavi.path.StrictPathludusavi.resource.config.root.Gog→ludusavi.path.StrictPathludusavi.resource.config.root.GogGalaxy→ludusavi.path.StrictPathludusavi.resource.config.root.Heroic→ludusavi.path.StrictPathludusavi.resource.config.root.Legendary→ludusavi.path.StrictPathludusavi.resource.config.root.Lutris→ludusavi.path.StrictPathludusavi.resource.config.root.Microsoft→ludusavi.path.StrictPathludusavi.resource.config.root.Origin→ludusavi.path.StrictPathludusavi.resource.config.root.Other→ludusavi.path.StrictPathludusavi.resource.config.root.OtherHome→ludusavi.path.StrictPathludusavi.resource.config.root.OtherLinux→ludusavi.path.StrictPathludusavi.resource.config.root.OtherMac→ludusavi.path.StrictPathludusavi.resource.config.root.OtherWindows→ludusavi.path.StrictPathludusavi.resource.config.root.OtherWine→ludusavi.path.StrictPathludusavi.resource.config.root.Prime→ludusavi.path.StrictPathludusavi.resource.config.root.Steam→ludusavi.path.StrictPathludusavi.resource.config.root.Uplay→ludusavi.path.StrictPath
- Direction
- resource.config.root uses path, so a change to path can break resource.config.root, while a change to resource.config.root can't break path.
- Position
- Below the diagonal: resource.config.root uses a module listed above it, which is the healthy direction.
39→3 api uses prelude✕
- Connections
- 2 pairs of types, where a type in api uses a type in prelude.
- The types involved
ludusavi.api.Ludusavi→ludusavi.prelude.Finalityludusavi.api.Ludusavi→ludusavi.prelude.SyncDirection
- Direction
- api uses prelude, so a change to prelude can break api, while a change to api can't break prelude.
- Position
- Below the diagonal: api uses a module listed above it, which is the healthy direction.
39→10 api uses scan.layout✕
- Connections
- 1 pair of types, where a type in api uses a type in scan.layout.
- The types involved
ludusavi.api.Ludusavi→ludusavi.scan.layout.BackupLayout
- Direction
- api uses scan.layout, so a change to scan.layout can break api, while a change to api can't break scan.layout.
- Position
- Below the diagonal: api uses a module listed above it, which is the healthy direction.
39→19 api uses resource.cache✕
- Connections
- 1 pair of types, where a type in api uses a type in resource.cache.
- The types involved
ludusavi.api.Ludusavi→ludusavi.resource.cache.Manifest
- Direction
- api uses resource.cache, so a change to resource.cache can break api, while a change to api can't break resource.cache.
- Position
- Below the diagonal: api uses a module listed above it, which is the healthy direction.
39→21 api uses scan.title✕
- Connections
- 3 pairs of types, where a type in api uses a type in scan.title.
- The types involved
ludusavi.api.Ludusavi→ludusavi.scan.title.TitleFinderludusavi.api.Ludusavi→ludusavi.scan.title.TitleQueryludusavi.api.api$module→ludusavi.scan.title.TitleFinder
- Direction
- api uses scan.title, so a change to scan.title can break api, while a change to api can't break scan.title.
- Position
- Below the diagonal: api uses a module listed above it, which is the healthy direction.
39→30 api uses resource.config✕
- Connections
- 1 pair of types, where a type in api uses a type in resource.config.
- The types involved
ludusavi.api.Ludusavi→ludusavi.resource.config.Config
- Direction
- api uses resource.config, so a change to resource.config can break api, while a change to api can't break resource.config.
- Position
- Below the diagonal: api uses a module listed above it, which is the healthy direction.
39→33 api uses path✕
- Connections
- 1 pair of types, where a type in api uses a type in path.
- The types involved
ludusavi.api.Ludusavi→ludusavi.path.StrictPath
- Direction
- api uses path, so a change to path can break api, while a change to api can't break path.
- Position
- Below the diagonal: api uses a module listed above it, which is the healthy direction.
39→34 api uses api.parameters✕
- Connections
- 4 pairs of types, where a type in api uses a type in api.parameters.
- The types involved
ludusavi.api.Ludusavi→ludusavi.api.parameters.BackUpludusavi.api.Ludusavi→ludusavi.api.parameters.EditBackupludusavi.api.Ludusavi→ludusavi.api.parameters.ListBackupsludusavi.api.Ludusavi→ludusavi.api.parameters.Restore
- Direction
- api uses api.parameters, so a change to api.parameters can break api, while a change to api can't break api.parameters.
- Position
- Below the diagonal: api uses a module listed above it, which is the healthy direction.
40→1 scan.launchers.lutris uses cli.api.response✕
- Connections
- 1 pair of types, where a type in scan.launchers.lutris uses a type in cli.api.response.
- The types involved
ludusavi.scan.launchers.lutris.Error→ludusavi.cli.api.response.Error
- Direction
- scan.launchers.lutris uses cli.api.response, so a change to cli.api.response can break scan.launchers.lutris, while a change to scan.launchers.lutris can't break cli.api.response.
- Position
- Below the diagonal: scan.launchers.lutris uses a module listed above it, which is the healthy direction.
40→20 scan.launchers.lutris uses resource.manifest✕
- Connections
- 1 pair of types, where a type in scan.launchers.lutris uses a type in resource.manifest.
- The types involved
ludusavi.scan.launchers.lutris.Pending→ludusavi.resource.manifest.Os
- Direction
- scan.launchers.lutris uses resource.manifest, so a change to resource.manifest can break scan.launchers.lutris, while a change to scan.launchers.lutris can't break resource.manifest.
- Position
- Below the diagonal: scan.launchers.lutris uses a module listed above it, which is the healthy direction.
40→21 scan.launchers.lutris uses scan.title✕
- Connections
- 2 pairs of types, where a type in scan.launchers.lutris uses a type in scan.title.
- The types involved
ludusavi.scan.launchers.lutris.Pending→ludusavi.scan.title.TitleFinderludusavi.scan.launchers.lutris.lutris$module→ludusavi.scan.title.TitleFinder
- Direction
- scan.launchers.lutris uses scan.title, so a change to scan.title can break scan.launchers.lutris, while a change to scan.launchers.lutris can't break scan.title.
- Position
- Below the diagonal: scan.launchers.lutris uses a module listed above it, which is the healthy direction.
40→33 scan.launchers.lutris uses path✕
- Connections
- 2 pairs of types, where a type in scan.launchers.lutris uses a type in path.
- The types involved
ludusavi.scan.launchers.lutris.Pending→ludusavi.path.StrictPathludusavi.scan.launchers.lutris.lutris$module→ludusavi.path.StrictPath
- Direction
- scan.launchers.lutris uses path, so a change to path can break scan.launchers.lutris, while a change to scan.launchers.lutris can't break path.
- Position
- Below the diagonal: scan.launchers.lutris uses a module listed above it, which is the healthy direction.
40→38 scan.launchers.lutris uses resource.config.root✕
- Connections
- 1 pair of types, where a type in scan.launchers.lutris uses a type in resource.config.root.
- The types involved
ludusavi.scan.launchers.lutris.lutris$module→ludusavi.resource.config.root.Lutris
- Direction
- scan.launchers.lutris uses resource.config.root, so a change to resource.config.root can break scan.launchers.lutris, while a change to scan.launchers.lutris can't break resource.config.root.
- Position
- Below the diagonal: scan.launchers.lutris 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
At a glance — Performance
Security & Compliance — OWASP Top-10 mapping
| OWASP category | Findings | Severity |
|---|---|---|
| A03:2025 — Software Supply Chain Failures | 39 | High / Critical |
| A05:2025 — Injection | 13 | High / Critical |
Roadmap
First, address the single missing architecture decision record by documenting the significant design choice with its context and consequences in the designated ADR folder. Next, update the README to clearly explain how to run the test suite, and fix the swallowed exception to ensure errors are properly handled. Finally, enable automated dependency review tools to maintain security and performance standards.
| Do this | Helps | Effort | Dimension |
|---|---|---|---|
| Resolve the 1 No ADRs found finding(s) in ADR Quality. | +6.0 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. | +5.5 pts | Medium | Architecture documentation |
| Explain in the README how to run the tests. Add a section called Testing to the README in the repository's top folder, saying how to run the test suite. | +3.2 pts | Medium | Documentation (README) |
| Swallowed exception (empty catch) | +2.5 pts | Medium | Exception handling |
| Resolve the 2 Hotspot finding(s) in Churn × Complexity Hotspots — start with scan.rs, report.rs. | +1.0 pts | Medium | Churn × Complexity Hotspots |
| Enable Dependabot/Renovate or a dependency-review gate. | +1.4 pts | Medium | Security & performance tooling |
| Document RTO/RPO and a tested restore procedure (a backup config alone isn't disaster recovery). | +1.4 pts | Medium | DR & Backup |
| Resolve the 1 Projects may be oversized for their cohesion finding(s) in Project Cohesion. | +0.6 pts | Low | Project Cohesion |
File quality
| File | Score | Band | Worst signal |
|---|---|---|---|
| REDACTED | 0.9 | Slop | Dependency Vulnerabilities: High CVE: REDACTED |
| REDACTED | 2.3 | Slop | Static Analysis (SAST): High: REDACTED |
| src/gui/app.rs | 6.0 | Mixed | Explicit Debt: TodoComment |
| src/cli.rs | 6.0 | Mixed | Explicit Debt: TodoComment |
| src/gui/shortcuts.rs | 6.0 | Mixed | Explicit Debt: TodoComment |
| src/scan.rs | 6.0 | Mixed | Explicit Debt: TodoComment |
| src/path.rs | 6.0 | Mixed | Explicit Debt: TodoComment |
| src/scan/layout.rs | 6.0 | Mixed | Explicit Debt: TodoComment |
| src/scan/registry/win.rs | 6.0 | Mixed | Explicit Debt: TodoComment |
| src/lang.rs | 6.0 | Mixed | Explicit Debt: TodoComment |
| src/resource/config.rs | 7.0 | Near-clean | Cyclomatic Complexity: Config::find_missing_roots (cyclomatic 23) |
| src/gui/modal.rs | 7.0 | Near-clean | Cyclomatic Complexity: Modal::message (cyclomatic 20) |
| src/scan/duplicate.rs | 7.0 | Near-clean | Cyclomatic Complexity: DuplicateDetector::duplicate_games (cyclomatic 17) |
| src/api.rs | 7.0 | Near-clean | Cyclomatic Complexity: Ludusavi::back_up (cyclomatic 26) |
| src/gui/style.rs | 7.1 | Near-clean | Cyclomatic Complexity: Theme::style (cyclomatic 30) |
| src/gui/game_list.rs | 7.1 | Near-clean | Cyclomatic Complexity: GameListEntry::view (cyclomatic 26) |
| src/scan/semantic/convert.rs | 7.1 | Near-clean | Cyclomatic Complexity: ludusavi::scan::semantic::convert::windows_physical_to_semantic (cyclomatic 23) |
| src/scan/title.rs | 7.2 | Near-clean | Cyclomatic Complexity: TitleFinder::find (cyclomatic 52) |
| src/gui/screen.rs | 7.2 | Near-clean | God Classes: FunctionTooLong: ludusavi::gui::screen::other |
| src/cli/ui.rs | 7.3 | Near-clean | Explicit Debt: TodoComment |
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. 56 of 56 evaluated dimensions are computed purely by tools and static analysis (confidence 1.0); none rely on LLM judgement. Overall confidence is 0.8 — 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 — 56 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, 269 of 294 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 | Secrets in history, SAST, CVEs, IaC & container, PII / GDPR | 1.86.0 · 0.69.3 | ✓ 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.
- D11 Test Reliability — 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. Test source is present (.rs) and this repository declares a Cargo test suite (repository root, 28 test files), but it was not re-run: no test result was produced. Not scored — this is a gap in the analyzer's language coverage, not a finding about this repository.
- 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 (28 contributor(s) across 1168 commit(s) sampled, automation and bot accounts excluded). One of them holds 91% of the history; the other 27 hold 0.3% 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.
- 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.
- C1 Data Protection — 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. 'rusqlite' is imported (src/scan/launchers/lutris.rs:14), but no entity, schema, table or model declaration this check reads was found beside it, so whether personal data is stored could not be decided.
- C3 Audit Trail — 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. 'rusqlite' is imported (src/scan/launchers/lutris.rs:14), but no entity, schema, table or model declaration this check reads was found beside it, so whether personal data is stored could not be decided.
- C4 Data Retention — 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. 'rusqlite' is imported (src/scan/launchers/lutris.rs:14), but no entity, schema, table or model declaration this check reads was found beside it, so whether personal data is stored could not be decided.
- C5 Data-Subject Rights — 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. 'rusqlite' is imported (src/scan/launchers/lutris.rs:14), but no entity, schema, table or model declaration this check reads was found beside it, so whether personal data is stored could not be decided.
- 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 Python, 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 Python, Rust is not read yet, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- M4 Documentation accuracy — measured, with a gap in what it reached — Watchdog measured this, but not all of it. What it did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. M4 checks only the claim kinds adjudicated at or above 95 % precision: links and versions (PREREGISTRATION version 9). Paths, command arguments, installs, environment variables, settings, projects, packages, routes, cd targets, infrastructure products and removed modules are read but not checked, and none of them is reported or counted.
- 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.
- 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.
- 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 Python, Rust is not read yet, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
Limitations & what we did not check
Watchdog assesses the repository exactly as committed, and only the repository. By design it does not reach outside the source tree: the live cloud account, the running CI/CD pipeline, the host's branch-protection and approval rules, the production configuration, or a restore actually exercised against a backup are all out of scope. That boundary is a feature, not a gap — a repo-relative, deterministic scan re-runs identically on any commit and every finding opens at a real file and line, where a live audit can neither be reproduced nor traced. The visible consequence is that controls which leave no in-repo evidence are reported as "not evidenced" and excluded from the score rather than awarded a number a static scan cannot justify.
Per-dimension blind spots
- D1 Cyclomatic Complexity: Cyclomatic complexity counts branches statically — it cannot tell an essential decision tree from accidental tangle, nor see complexity that lives in data or configuration (large switch-case token tables, DSL lexers/parsers, data-as-code rule tables) rather than control flow: a tokenizer's many single-character cases read as high complexity though each branch is trivial.
- D2 Cognitive Complexity: Cognitive-complexity heuristics approximate how hard code is to follow; genuine domain difficulty and well-named intent that eases reading are not captured.
- D3 God Classes: "God class" is sized by members and responsibilities visible in the type — a deliberately broad facade over a coherent subsystem can read the same as an accidental grab-bag. For front-end JS the file-length check is cohesion-aware (a single-responsibility module — one class/IIFE — earns a 3× threshold), but cohesion is approximated from top-level declarations, not true dependency structure.
- D4 Code Duplication: Duplication is token-similarity — an in-process token-stream comparison over sliding windows, with type-aware normalization — so it finds copy-paste, not semantic duplication expressed differently. Committed machine-written code (scaffolded migrations, designer/codegen output, protobuf/OpenAPI stubs, model snapshots) is EXCLUDED — its repetition is the tool's, not the team's — so the score reflects hand-written duplication only.
- D6 Cohesion (LCOM4): LCOM4 cohesion is syntactic — it infers connectivity from which methods touch which fields/methods by name, not from real runtime behaviour or intent.
- D9 Test Distribution: The test-pyramid shape is inferred from project/folder naming and references, with a single test host bucketed per-file by its path tier and content signals — a suite that names tiers unconventionally and gives no per-file signal can still be mis-bucketed.
- 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.
- 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.
- M4 Documentation accuracy: Onboarding quality is an LLM read of the docs/setup present — it cannot run the onboarding or measure how long a real new joiner takes; the verdict is sampled and advisory.
- P5 DR & Backup: Backup/restore and disaster-recovery readiness is judged from in-repo evidence — a config that exists is not a tested restore, so the absence of positive evidence is reported as "not evidenced", never scored as present.
- 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
29 method(s) exceeded the cyclomatic complexity threshold of 15; the worst was App::update at 332. A further 13 method(s) were over the threshold but excluded as flat dispatchers (a long switch/match over independent cases: many branches, almost no nesting), the largest being Icon::as_char at 35 — 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/gui/icon.rs (Icon::as_char at 35), src/lang.rs (Language::id at 24). 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 3 bodies over 60 down to 60 or less in Cyclomatic Complexity — start with App::update (cyclomatic 332), ludusavi::cli::run (cyclomatic 157), TextHistories::input (cyclomatic 85). — This score is capped by its worst body, so a finding fixed alone moves it by almost nothing — the next one down takes its place. Refactoring these 3 together lifts Cyclomatic Complexity from 4.8 to about 6.5/10, projected with the scoring formula itself and assuming each lands exactly at 60; a cleaner split scores higher.
- 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
50 method(s) exceeded the cognitive complexity threshold of 15; the worst was ludusavi::cli::run at 311.
What to do
- Bring the 3 bodies over 120 down to 120 or less in Cognitive Complexity — start with ludusavi::cli::run (cognitive 311), App::update (cognitive 283), ludusavi::scan::scan_game_for_backup (cognitive 131). — This score is capped by its worst body, so a finding fixed alone moves it by almost nothing — the next one down takes its place. Refactoring these 3 together lifts Cognitive Complexity from 2.7 to about 4.4/10, projected with the scoring formula itself and assuming each lands exactly at 120; 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
41 god class(es) detected.
What to do
- Resolve the 15 FileTooLong finding(s) in God Classes — start with app.rs, layout.rs, config.rs. — One of this dimension's main actionable groups (15 warning-level).
- Resolve the 10 MethodTooLong finding(s) in God Classes — start with app.rs (3), game_list.rs, shortcuts.rs. — One of this dimension's main actionable groups (10 warning-level).
- Resolve the 6 ClassTooLong finding(s) in God Classes — start with app.rs, layout.rs, lang.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
68 duplicated block group(s) detected. One further row reports members as variants of one another; it aggregates block groups already counted above and is not itself counted.
What to do
- Resolve the 7 Duplicated block (9 lines × 2) finding(s) in Code Duplication — start with app.rs (2), icon.rs, config.rs. — One of this dimension's main actionable groups (7 warning-level).
- Resolve the 6 Duplicated block (8 lines × 2) finding(s) in Code Duplication — start with cli.rs (2), modal.rs, screen.rs. — One of this dimension's main actionable groups (6 warning-level).
- Resolve the 5 Duplicated block (12 lines × 2) finding(s) in Code Duplication — start with cli.rs (2), parse.rs, main.rs. — One of this dimension's main actionable groups (5 warning-level).
- Enforce Code Duplication in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Verified — provenance only; does not change the score.
D6 · Cohesion (LCOM4)
0 of 49 classes have LCOM4 above 3.
D9 · Test Distribution
285 test methods: 285 unit, 0 integration, 0 BDD, 0 e2e. The Rust suite contributes 285 `#[test]` function(s) across 28 file(s) declaring at least one; its unit/integration split is Cargo's own — 0 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.
D12 · Dependency Hygiene
20 outdated, 0 yanked direct Cargo dependencies. Only DIRECT edges are graded: a transitive crate cannot be moved past what its parent's requirement admits, so reporting one would be advice its owner cannot take. A newer release is reported only where this repository's OWN requirement already admits it, so the remedy is `cargo update` and never a manifest edit — which means a release outside the declared range is deliberately NOT charged, because a written-down constraint is a decision rather than a defect. Note that a bare requirement is a CARET, and for a 0.x crate its ceiling is the minor. Whether any crate is UNMAINTAINED is not graded — crates.io publishes no maintenance status, and release age does not stand in for one. Known CVEs in this dependency graph are D30's question, read from REDACTED there.
D13 · Secret Scanning
Secret scan ran and found no leaked secrets.
D14 · License Compliance
0 of 661 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/scan.rs (3×50=150); src/report.rs (2×25=50)
What to do
- Resolve the 2 Hotspot finding(s) in Churn × Complexity Hotspots — start with scan.rs, report.rs. — One of this dimension's main actionable groups (2 warning-level).
D17 · Explicit Debt
15 deducted task-comment markers across 37618 LoC (0.0/KLoC) → score 9.9. 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 15 TodoComment finding(s) in Explicit Debt — start with win.rs (3), cli.rs (2), app.rs (2). — One of this dimension's main actionable groups (15 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. 25 document(s) read across 1 unit(s).
D20 · ADR Quality
No architecture decision records were found.
What to do
- Resolve the 1 No ADRs found finding(s) in ADR Quality. — One of this dimension's main actionable groups (1 recommendation-level).
D26 · Project Cohesion
1 of 1 build units (Cargo) flagged as possibly oversized/incoherent.
What to do
- Resolve the 1 Projects may be oversized for their cohesion finding(s) in Project Cohesion. — One of this dimension's main actionable groups (1 recommendation-level).
D28 · Secrets (history)
gitleaks scanned the full history AND the current working tree and found no secrets.
D29 · Static Analysis (SAST)
13 finding(s): 0 critical, 13 high, 0 medium, 0 low. 13 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) — `src/path.rs` (line 807) — 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
- No action in Static Analysis (SAST) — all 13 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 (13 issue-level, 0 of them charged here).
D30 · Dependency Vulnerabilities
39 finding(s): 0 critical, 3 high, 36 medium, 0 low.
What to do
- Resolve the 15 Medium advisory (unsound) finding(s) in Dependency Vulnerabilities — start with REDACTED (15). — One of this dimension's main actionable groups (15 warning-level).
- Resolve the 2 High CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (2). — One of this dimension's main actionable groups (2 issue-level).
- Resolve the 1 High vulnerability finding(s) in Dependency Vulnerabilities — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
D34 · Knowledge Freshness
Every significant source file has living knowledge — recently and meaningfully worked. Counted over 59 of the 68 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.
D35 · Change Coupling
Strongest change-coupling: app.rs↔icon.rs 60%
What to do
- Resolve the 1 Change coupling finding(s) in Change Coupling — start with app.rs. — 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
- Explain in the README how to run the tests. Add a section called Testing to the README in the repository's top folder, saying how to run the test suite.
- Add an 'Architecture' / 'How it works' section to the root README — the high-level shape.
M2 · Architecture documentation
- No Architecture Decision Records found — no conventional ADR directory, no numbered `NNNN-title` documents in any markup this check reads, and nothing ADR-shaped by content. Design rationale recorded elsewhere (a design-notes tree, a mailing list, pull-request discussion) is not visible to this check and is not re-findable per decision, so a future maintainer cannot ask why one choice was made and get an answer.
- No C4/Structurizr/PlantUML/Mermaid/Graphviz/D2 diagram, no drawn diagram named for the architecture, no file named `architecture` or `design` in any markup this check reads, and nothing in the README, docs or contributor guides that announces the shape — no `## Architecture` heading, no "architecture overview"/"high-level design" phrasing, no "the architecture is …" introduction, no guided code tour. A shape laid out in prose that never names itself as the architecture is not visible to this check, and neither is one kept outside the repository, so this row reports the absence of a re-findable shape document — not evidence that nobody wrote the shape down.
What to do
- Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them.
- Add a C4 context/container diagram (Structurizr, PlantUML or Mermaid) or an architecture.md overview.
M3 · Folder & project structure
M4 · Documentation accuracy
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.
P5 · DR & Backup
What to do
- Document RTO/RPO and a tested restore procedure (a backup config alone isn't disaster recovery).
P6 · Release Hygiene
PF3 · Async & latency hygiene
S1 · Web-Security Posture
- MD5/SHA1 is computed here, and both are collision-broken. If this digest protects anything — a signature, an integrity or tamper check, a credential, or any value an attacker can influence — that is a real weakness: use SHA-256+ (`sha2::Sha256::digest(…)`) for content integrity, or a KDF (bcrypt/Argon2/scrypt) for password storage. If it only derives a non-security identifier (a cache key, an avatar URL, an ETag), collision resistance carries no security consequence here; make that intent explicit instead — a non-cryptographic hash such as xxhash or murmurhash says it in code — since the algorithm alone cannot distinguish the two uses. Where a protocol this code does not own fixes the digest (a k-anonymity range query, a legacy signature format), the protocol decides; say so beside the call. (×2) — src/path.rs:1189, src/prelude.rs:191
What to do
- Review each MD5/SHA1 use by what it protects: replace it with SHA-256+ (or a KDF for passwords) where the digest is security-relevant, and switch it to a non-cryptographic hash (xxhash, murmurhash) where it only derives an identifier such as a cache key. This repository constructs a collision-broken hash (MD5/SHA1) at 2 sites, not one: `src/path.rs:1189` (`Sha1::new`), `src/prelude.rs:191` (`Sha1::new`). Each is a separate decision — fixing only the line this row cites leaves the others in place.
X1 · Async correctness
X12 · Unreachable branch
X13 · Undrained process stream
X14 · Bypassable address classification
X15 · Unvalidated length from an untrusted reader
X17 · Uncapped recursion over a caller-supplied document
X19 · Unrestored process-global state
X21 · Side-effecting pattern guard
X22 · Contradicted release guard
X23 · Unguarded diagnostic materialisation
X24 · Document value interpolated into markup unescaped
X25 · Inert configuration knob
X26 · Unsynchronised callback handoff
X27 · Collection changed while being enumerated
X28 · Index access outside its own emptiness guard
X29 · Per-element action decided by a fixed element
X3 · Exception handling
- An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it. — tasks.py:48
What to do
- Swallowed exception (empty catch)
X30 · Support guard that admits what it rejects
Reference — by lens
| Lens | Score | Rating | Impact |
|---|---|---|---|
| Code Health | 65% | Adequate — gated by D2, X3 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Architecture | 85% | Adequate — gated by D26 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Maturity | 59% | Adequate — gated by M2 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Readiness | 66% | Strong | Solid. |
| Security | 79% | Adequate — gated by D30 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Event Sourcing | 100% | Exemplary | Strongest area. |
| Performance | 100% | Exemplary | Solid. |
Unscored — 3 check(s) recorded observations but carry no score
- D36 Supply-chain Provenance & Signing — 1 observation(s) recorded · The CI pipeline builds and tests but publishes no released artifact — no package publish, container push, GitHub release or deployment step. Supply-chain provenance, signing and SBOM attest RELEASED artifacts, so there is nothing to attest here. Add them to the release pipeline when this repo starts shipping artifacts (a published package, a container image, a deployed service or a tagged release). Build integrity and workflow-token hygiene are reported below: they describe what the CI runs and the token it runs with, neither of which is affected by whether the pipeline ships an artifact.
- X10 Duplicated predicate — 2 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
- X7 Silent fallback defaults — 4 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
Not evidenced — 4 control(s) we could not find positive evidence for
- C3 Audit Trail — Not assessed: this repository stores data through 'rusqlite' (src/scan/launchers/lutris.rs:14) but declares no persisted model this check reads (Diesel table! columns, SeaORM entity / Diesel model / sqlx FromRow struct fields, CREATE TABLE and ALTER TABLE … ADD columns in SQL migrations and SQL string literals). Personal data may be written through raw SQL or a hosted backend, so whether its changes need an audit trail could not be established, and the trail's absence is not scored.
- C4 Data Retention — Not assessed: this repository stores data through 'rusqlite' (src/scan/launchers/lutris.rs:14) but declares no persisted model this check reads (Diesel table! columns, SeaORM entity / Diesel model / sqlx FromRow struct fields, CREATE TABLE and ALTER TABLE … ADD columns in SQL migrations and SQL string literals). Personal data may be written through raw SQL or a hosted backend, so whether a retention limit applies here could not be established, and its absence is not scored.
- C5 Data-Subject Rights — Not assessed: this repository stores data through 'rusqlite' (src/scan/launchers/lutris.rs:14) but declares no persisted model this check reads (Diesel table! columns, SeaORM entity / Diesel model / sqlx FromRow struct fields, CREATE TABLE and ALTER TABLE … ADD columns in SQL migrations and SQL string literals). Personal data may be written through raw SQL or a hosted backend, so whether data-subject rights apply here could not be established, and their absence is not scored.
- P4 Deployment & Rollback — not evidenced — no deploy/rollback/approval signal in the repo; absence of evidence is not evidence of a manual release
Not included — 57 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: this repository's Python imports no dependency-injection container and defines no container of its own — nothing that both registers and resolves bindings, and nothing that names two lifetimes — so nothing holds one lifetime's instance while handing out another's; Rust with no dependency-injection crate has no container to hand one lifetime's instance to another — every value is owned by the code that builds it, and the borrow checker rejects a longer-lived value keeping a borrow of a shorter-lived one.
- AX2 Stateful singletons — No container singleton was found, so there is no shared instance for concurrent requests to race on. No function in this Python code is served by a threaded web framework (a Flask, Bottle or FastAPI route, a Django or Pyramid view), so no module is shared between request threads. 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
- AXB1 Runtime evidence locked — no reproducible boot — This repository has nothing the runtime tiers could boot or serve — no markup, no UI framework or web-server dependency, no UI component source, no native UI project and no API definition — nothing here is a surface to boot — so runtime a11y/egress/header evidence has no subject here. Not applicable: this is neither a gap in the scan nor a finding about your code.
- C1 Data Protection — Not assessed: this repository stores data through 'rusqlite' (src/scan/launchers/lutris.rs:14) but declares no persisted model this check reads (Diesel table! columns, SeaORM entity / Diesel model / sqlx FromRow struct fields, CREATE TABLE and ALTER TABLE … ADD columns in SQL migrations and SQL string literals). Personal data may be written through raw SQL or a hosted backend, so the absence of a personal-data field here is not evidence that none is stored, and encryption at rest is not scored over a subject that could not be established.
- 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.
- D10 Test Quality — ~29 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.
- D11 Test Reliability — Test reliability not included — the .rs suite was found but not re-run
- 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; Python, 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 (gui), 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 .py, .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.
- D31 IaC & Container Security — No Infrastructure-as-Code or container manifests found (Dockerfile, Docker Compose, Terraform, Kubernetes/Helm, CloudFormation, ARM, Bicep, Ansible); nothing to scan.
- D32 Data Compliance (PII/GDPR) — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that.
- D37 Vulnerability-disclosure Policy — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed.
- 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
- D5 Coupling — Not applicable — this Cargo build ships 1 production module(s), so there is no coupling BETWEEN modules to measure. (Its test and non-production modules are not part of the shipped graph.)
- D7 Architectural Integrity — no checkable ADRs, and no project-reference graph for the cycle pass to read — so this dimension makes no claim about dependency cycles in either direction (where this repository's language has an import-cycle lens, cycles are reported there). Architectural integrity not assessed
- D8 Code Coverage — Coverage not included — suite not readable by the collector
- DM1 Domain Modelling — applicable but not scored (3 signals for this style, 3 needed — the count is met but a required primary signal is absent): 1 aggregate root(s) (types guarding their own state behind command methods — this language has no AggregateRoot base to inherit); 9 value object(s); 3 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
- 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 Python, 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.
- 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
- 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
- X2 Cancellation propagation — no C# was loaded; this repository's Python and Rust were read, and no request in it can be cancelled by a caller — a Python request takes no token: asyncio cancels the task and trio or anyio the scope that made it, from outside the call, and requests, httpx, aiohttp and gRPC take a timeout, not a cancellation; 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.
- 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 — 16 finding(s)
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
Serious — 247 finding(s)
- TodoComment src/cli.rs:1147
- TodoComment src/cli.rs:1216
- TodoComment src/lang.rs:48
- TodoComment src/path.rs:1854
- TodoComment src/scan.rs:797
- TodoComment src/wrap.rs:44
- TodoComment src/scan/layout.rs:197
- TodoComment src/scan/registry/win.rs:187
- TodoComment src/scan/registry/win.rs:217
- TodoComment src/scan/registry/win.rs:347
- TodoComment src/gui/app.rs:1107
- TodoComment src/gui/app.rs:1650
- TodoComment src/gui/shortcuts.rs:446
- TodoComment src/cli/ui.rs:29
- TodoComment src/cli/ui.rs:69
- FileTooLong: gui/app.rs src/gui/app.rs
- FileTooLong: scan/layout.rs src/scan/layout.rs
- FileTooLong: resource/config.rs src/resource/config.rs
- FileTooLong: src/cli.rs src/cli.rs
- FileTooLong: src/lang.rs src/lang.rs
- FileTooLong: src/path.rs src/path.rs
- FileTooLong: src/scan.rs src/scan.rs
- FileTooLong: gui/common.rs src/gui/common.rs
- FileTooLong: gui/game_list.rs src/gui/game_list.rs
- FileTooLong: resource/manifest.rs src/resource/manifest.rs
- FileTooLong: gui/modal.rs src/gui/modal.rs
- FileTooLong: src/cloud.rs src/cloud.rs
- FileTooLong: gui/screen.rs src/gui/screen.rs
- FileTooLong: gui/editor.rs src/gui/editor.rs
- FileTooLong: gui/style.rs src/gui/style.rs
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- ludusavi::cli::run (cognitive 311) src/cli.rs:142
- ludusavi::scan::scan_game_for_backup (cognitive 131) src/scan.rs:544
- ludusavi::scan::parse_paths (cognitive 62) src/scan.rs:139
- ludusavi::scan::launchers::generic::scan (cognitive 39) src/scan/launchers/generic.rs:52
- ludusavi::cloud::rclone_monitor::run (cognitive 34) src/cloud.rs:766
- ludusavi::scan::semantic::convert::wine_physical_to_semantic (cognitive 33) src/scan/semantic/convert.rs:184
- ludusavi::scan::game_file_target (cognitive 27) src/scan.rs:65
- ludusavi::scan::semantic::convert::windows_physical_to_semantic (cognitive 22) src/scan/semantic/convert.rs:63
- ludusavi::scan::launchers::lutris::scan_db (cognitive 21) src/scan/launchers/lutris.rs:199
- ludusavi::cli::api::process (cognitive 18) src/cli/api.rs:205
- ludusavi::cli::sync_cloud (cognitive 17) src/cli.rs:1369
- ludusavi::scan::wine_prefixes_with_included_files (cognitive 17) src/scan.rs:986
- ludusavi::scan::registry::win::scan_registry_key (cognitive 17) src/scan/registry/win.rs:129
- ludusavi::scan::launchers::faugus::scan_spec (cognitive 16) src/scan/launchers/faugus.rs:87
- MethodTooLong: App.update src/gui/app.rs:1491
- MethodTooLong: App.handle_backup src/gui/app.rs:296
- MethodTooLong: GameListEntry.view src/gui/game_list.rs:49
- MethodTooLong: App.handle_restore src/gui/app.rs:731
- MethodTooLong: TextHistories.input src/gui/shortcuts.rs:316
- MethodTooLong: Reporter.add_game src/report.rs:311
- MethodTooLong: FileTreeNode.view src/gui/file_tree.rs:103
- MethodTooLong: Config.find_missing_roots src/resource/config.rs:1444
- MethodTooLong: TitleFinder.find src/scan/title.rs:169
- MethodTooLong: GameLayout.execute_backup_as_zip src/scan/layout.rs:1258
- GameLayout::validate (cognitive 64) src/scan/layout.rs:2105
- GameLayout::execute_backup_as_zip (cognitive 31) src/scan/layout.rs:1258
- GameLayout::restore (cognitive 29) src/scan/layout.rs:1763
- GameLayout::scan_for_restoration (cognitive 22) src/scan/layout.rs:1654
- GameLayout::forget_excess_backups (cognitive 19) src/scan/layout.rs:1421
- GameLayout::modify_backup (cognitive 19) src/scan/layout.rs:2055
- GameLayout::plan_differential_backup (cognitive 18) src/scan/layout.rs:1131
- GameLayout::find_irrelevant_backup_files (cognitive 16) src/scan/layout.rs:1964
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- ludusavi::cli::run (cyclomatic 157) src/cli.rs:142
- ludusavi::scan::scan_game_for_backup (cyclomatic 50) src/scan.rs:544
- ludusavi::scan::parse_paths (cyclomatic 40) src/scan.rs:139
- ludusavi::scan::semantic::convert::windows_physical_to_semantic (cyclomatic 23) src/scan/semantic/convert.rs:63
- ludusavi::scan::semantic::convert::wine_physical_to_semantic (cyclomatic 23) src/scan/semantic/convert.rs:184
- ludusavi::scan::launchers::generic::scan (cyclomatic 18) src/scan/launchers/generic.rs:52
- ludusavi::scan::game_file_target (cyclomatic 16) src/scan.rs:65
- Duplicated block (9 lines × 2) src/gui/app.rs:361
- Duplicated block (9 lines × 2) src/gui/app.rs:802
- Duplicated block (9 lines × 2) src/gui/icon.rs:89
- Duplicated block (9 lines × 2) src/resource/config.rs:1935
- Duplicated block (9 lines × 2) src/scan/duplicate.rs:184
- Duplicated block (9 lines × 2) src/scan/launchers/heroic/nile.rs:37
- Duplicated block (9 lines × 2) src/api.rs:263
- ClassTooLong: App src/gui/app.rs:91
- ClassTooLong: GameLayout src/scan/layout.rs:560
- ClassTooLong: Translator src/lang.rs:255
- ClassTooLong: StrictPath src/path.rs:185
- ClassTooLong: Modal src/gui/modal.rs:139
- ClassTooLong: Theme src/gui/style.rs:25
- Duplicated block (8 lines × 2) src/cli.rs:509
- Duplicated block (8 lines × 2) src/cli.rs:723
- Duplicated block (8 lines × 2) src/gui/modal.rs:337
- Duplicated block (8 lines × 2) src/gui/screen.rs:97
- Duplicated block (8 lines × 2) src/gui/search.rs:43
- Duplicated block (8 lines × 2) src/scan/layout.rs:1812
- App::update (cognitive 283) src/gui/app.rs:1491
- App::handle_backup (cognitive 118) src/gui/app.rs:296
- App::handle_restore (cognitive 78) src/gui/app.rs:731
- App::handle_validation (cognitive 31) src/gui/app.rs:1037
- App::new (cognitive 20) src/gui/app.rs:1364
- FunctionTooLong: ludusavi::cli::run src/cli.rs:142
- FunctionTooLong: ludusavi::gui::screen::other src/gui/screen.rs:317
- FunctionTooLong: ludusavi::scan::scan_game_for_backup src/scan.rs:544
- FunctionTooLong: ludusavi::scan::parse_paths src/scan.rs:139
- FunctionTooLong: ludusavi::gui::editor::custom_games src/gui/editor.rs:272
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Duplicated block (12 lines × 2) src/cli.rs:388
- Duplicated block (12 lines × 2) src/cli.rs:977
- Duplicated block (12 lines × 2) src/cli/parse.rs:569
- Duplicated block (12 lines × 2) src/main.rs:29
- Duplicated block (12 lines × 2) src/scan/launchers/heroic/legendary.rs:108
- Duplicated block (7 lines × 2) src/gui/app.rs:862
- Duplicated block (7 lines × 2) src/path.rs:92
- Duplicated block (7 lines × 2) src/scan.rs:486
- Duplicated block (7 lines × 2) src/scan/layout.rs:923
- Duplicated block (7 lines × 2) src/scan/layout.rs:1981
- App::update (cyclomatic 332) src/gui/app.rs:1491
- App::handle_backup (cyclomatic 60) src/gui/app.rs:296
- App::handle_restore (cyclomatic 40) src/gui/app.rs:731
- App::handle_validation (cyclomatic 18) src/gui/app.rs:1037
- DuplicateDetector::duplicate_games (cognitive 48) src/scan/duplicate.rs:326
- DuplicateDetector::remove_game_and_refresh (cognitive 38) src/scan/duplicate.rs:178
- DuplicateDetector::count_duplicated_items_for (cognitive 25) src/scan/duplicate.rs:291
- DuplicateDetector::add_game (cognitive 16) src/scan/duplicate.rs:97
- TooManyMethods: Translator src/lang.rs:255
- TooManyMethods: StrictPath src/path.rs:185
- TooManyMethods: GameLayout src/scan/layout.rs:560
- TooManyMethods: App src/gui/app.rs:91
- Duplicated block (6 lines × 2) src/path.rs:85
- Duplicated block (6 lines × 2) src/resource/config.rs:446
- Duplicated block (6 lines × 2) src/scan.rs:305
- Duplicated block (6 lines × 2) src/scan/launchers/heroic/gog.rs:97
- Duplicated block (18 lines × 2) src/cli.rs:161
- Duplicated block (18 lines × 2) src/gui/button.rs:267
- Duplicated block (18 lines × 2) src/scan/layout.rs:2110
- Duplicated block (15 lines × 2) src/gui/style.rs:428
- Duplicated block (15 lines × 2) src/path.rs:1041
- Duplicated block (15 lines × 2) src/scan/launchers/heroic/nile.rs:47
- Duplicated block (14 lines × 2) src/gui/app.rs:688
- Duplicated block (14 lines × 2) src/scan/launchers/faugus.rs:45
- Duplicated block (14 lines × 2) src/cli.rs:249
- Duplicated block (10 lines × 2) src/gui/app.rs:1233
- Duplicated block (10 lines × 2) src/gui/editor.rs:110
- Duplicated block (10 lines × 2) src/scan/layout.rs:2130
- Theme::style (cyclomatic 30) src/gui/style.rs:184
- Theme::style (cyclomatic 29) src/gui/style.rs:326
- Ludusavi::back_up (cyclomatic 26) src/api.rs:119
- Ludusavi::restore (cyclomatic 22) src/api.rs:312
- Modal::message (cyclomatic 20) src/gui/modal.rs:303
- Modal::text (cyclomatic 19) src/gui/modal.rs:259
- GameLayout::execute_backup_as_zip (cyclomatic 20) src/scan/layout.rs:1258
- GameLayout::validate (cyclomatic 19) src/scan/layout.rs:2105
- DuplicateDetector::duplicate_games (cyclomatic 17) src/scan/duplicate.rs:326
- DuplicateDetector::remove_game_and_refresh (cyclomatic 16) src/scan/duplicate.rs:178
- Hotspot: src/scan.rs src/scan.rs:544
- Hotspot: src/report.rs src/report.rs:311
- Ludusavi::back_up (cognitive 47) src/api.rs:119
- Ludusavi::restore (cognitive 42) src/api.rs:312
- Hives::restore (cognitive 34) src/scan/registry/win.rs:302
- Hives::from (cognitive 18) src/scan/registry.rs:170
- Duplicated block (21 lines × 2) src/api.rs:173
- Duplicated block (21 lines × 2) src/cli.rs:427
- Duplicated block (13–15 lines × 2) src/gui/app.rs:570
- Duplicated block (13–15 lines × 2) src/scan.rs:774
- Duplicated block (13 lines × 2) src/cli.rs:232
- Duplicated block (13 lines × 2) src/scan/layout.rs:814
- Duplicated block (11 lines × 2) src/metadata.rs:27
- Duplicated block (11 lines × 2) src/scan/duplicate.rs:330
- Duplicated block (8 lines × 3) src/scan/semantic/convert.rs:205
- Duplicated block (8 lines × 3) src/scan/launchers/heroic/legendary.rs:104
- Weak hash algorithm src/path.rs:1189
- Weak hash algorithm src/prelude.rs:191
- TextHistories::input (cyclomatic 85) src/gui/shortcuts.rs:316
- TitleFinder::find (cyclomatic 52) src/scan/title.rs:169
- StrictPath::analyze_with_mode (cyclomatic 36) src/path.rs:289
- GameListEntry::view (cyclomatic 26) src/gui/game_list.rs:49
- Reporter::add_game (cyclomatic 25) src/report.rs:311
- Config::find_missing_roots (cyclomatic 23) src/resource/config.rs:1444
- FileTreeNode::view (cyclomatic 20) src/gui/file_tree.rs:103
- Progress::view (cyclomatic 17) src/gui/widget.rs:231
- TitleFinder::find (cognitive 116) src/scan/title.rs:169
- Reporter::add_game (cognitive 59) src/report.rs:311
- StrictPath::analyze_with_mode (cognitive 52) src/path.rs:289
- Config::find_missing_roots (cognitive 36) src/resource/config.rs:1444
- GameListEntry::view (cognitive 31) src/gui/game_list.rs:49
- Manifest::incorporate_secondary_manifest (cognitive 25) src/resource/manifest.rs:802
- Progress::view (cognitive 22) src/gui/widget.rs:231
- FileTreeNode::view (cognitive 21) src/gui/file_tree.rs:103
- GameList::update_game (cognitive 20) src/gui/game_list.rs:692
- Modal::message (cognitive 20) src/gui/modal.rs:303
- RcloneProcess::events (cognitive 19) src/cloud.rs:84
- Backup::prune_failures (cognitive 19) src/scan/layout.rs:184
- ScanInfo::count_changes (cognitive 19) src/scan/preview.rs:194
- Theme::style (cognitive 17) src/gui/style.rs:184
- ToggledRegistryEntry::prune (cognitive 17) src/resource/config.rs:742
- TooManyFunctions: ludusavi::gui::button src/gui/button.rs:20
- Change coupling: app.rs ↔ icon.rs src/gui/app.rs:1
- REDACTED
- Members sharing a duplicated core (5 members, 50+ identical tokens) src/gui/modal.rs:608
- Duplicated block (49 lines × 2) src/scan/layout.rs:764
- Duplicated block (19–21 lines × 2) src/scan.rs:754
- Duplicated block (19 lines × 2) src/api.rs:602
- Duplicated block (17 lines × 3) src/gui/modal.rs:614
- Duplicated block (17 lines × 2) src/cli.rs:995
- Duplicated block (16–17 lines × 2) src/gui/app.rs:616
- Duplicated block (16 lines × 2) src/gui/screen.rs:144
- Duplicated block (14 lines × 5) src/gui/modal.rs:614
- Duplicated block (14 lines × 3) src/scan.rs:217
- Duplicated block (11–13 lines × 2) src/scan/layout.rs:187
- Duplicated block (12 lines × 3) src/gui/app.rs:557
- Duplicated block (10–12 lines × 2) src/gui/search.rs:233
- Duplicated block (11–12 lines × 2) src/path.rs:404
- Duplicated block (10–11 lines × 2) src/gui/app.rs:463
- Duplicated block (9 lines × 3) src/gui/app.rs:2731
- Duplicated block (8–9 lines × 3) src/scan/title.rs:202
- Duplicated block (7 lines × 3) src/scan/duplicate.rs:294
- Duplicated block (5 lines × 3) src/cli.rs:765
- Duplicated block (5 lines × 2) src/resource/config.rs:430
- Swallowed exception (empty catch) tasks.py:48
Minor — 11 finding(s)
- Silent fallback default on Err src/scan/layout.rs:535
- Silent fallback default on Err src/scan/layout.rs:908
- Silent fallback default on Err src/scan/layout.rs:1968
- Silent fallback default on Err src/lang.rs:324
- Duplicated predicate src/api.rs:280
- Duplicated predicate src/scan/layout.rs:462
- No ADRs found
- Projects may be oversized for their cohesion
- REDACTED
- No ADRs
- No architecture diagram/doc
Minor — 20 finding(s)
- Outdated: byte-unit
- Outdated: chrono
- Outdated: clap
- Outdated: clap_complete
- Outdated: embed-resource
- Outdated: filetime
- Outdated: globset
- Outdated: image
- Outdated: intl-memoizer
- Outdated: known-folders
- Outdated: log
- Outdated: rayon
- Outdated: regex
- Outdated: schemars
- Outdated: semver
- Outdated: serde
- Outdated: serde_json
- Outdated: steamlocate
- Outdated: tokio
- Outdated: unic-langid
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-63a23542b62b40768a5bf34a624c6483/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-63a23542b62b40768a5bf34a624c6483/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 . | 13 | 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 . | 39 | artifacts/raw/osv-scanner.json |
| D31 · IaC & Container Security | trivy | — | trivy: not applicable — No Infrastructure-as-Code or container manifests found (Dockerfile, Docker Compose, Terraform, Kubernetes/Helm, CloudFormation, ARM, Bicep, Ansible); nothing to scan. | 0 | — |
| D32 · Data Compliance (PII/GDPR) | semgrep | — | semgrep: not applicable — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that. | 0 | — |
| D37 · Vulnerability-disclosure Policy | disclosure | — | disclosure: not applicable — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed. | 0 | — |
| D40 · Network Egress Confinement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here. | 0 | — |
| D41 · Kernel & Syscall Confinement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here. | 0 | — |
| D42 · Runtime Threat Enforcement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here. | 0 | — |
| D43 · Malicious Dependencies | osv-scanner | — | osv-scanner --format json --recursive --experimental-disable-plugins transitivedependency/requirements --experimental-disable-plugins dotnet/csproj --experimental-disable-plugins dotnet/nugetcpm . | 0 | artifacts/raw/osv-scanner.json |