Executive summary
chocolatey/ChocolateyGUI has a provisional result, because the code didn't build. It scores 54.7 out of 100, and the ratings may change once the code builds. 20 of its 29 critical findings are security problems.
Production Readiness, at 47.5, is the weakest lens and counts most in the score. The best first step is fixing the password or key in the code, worth about 5.9 points. Automating the release would lift Production Readiness itself, worth about 4.1 points. Raising Production Readiness to 70 would lift the score to about 60.4.
Ten pipeline tools are referenced by a changeable name, so the build pipeline can be tampered with. Four pipeline steps run downloads nobody checks, and three secrets can leak from the build pipeline. Pinning each tool to an exact version, checking each download against a checksum and limiting each secret to its own step would close these risks. Passing outside input through environment variables would fix the pipeline step that puts outside input straight into a shell command. The six data fields that are written but never read need removing.
The product code is 20,843 lines, about €29,000 to rebuild.
If Production Readiness rose from 47.5 to 70, the lowest score rated Strong, the score would rise from 54.7 to about 60.4.
Rebuild cost: about €29,000 · Estimate
| Cost to rebuild | €9,600 to €48,000, for 160 to 510 hours of work, about 0.2 person-years for one engineer |
|---|---|
| Difficulty of the problem | Standard, judged from the kind of software and how it is built. Code that solves a harder problem, such as payments or medical bookings, costs more per line to write. |
| Quality factor | ×0.8 at a score of 55. Better code takes more work to write, so the factor is ×1.0 at a score of 70, lower below it and higher above it. |
| Size | Medium: 20,843 lines of product code |
| Comment lines | The estimate prices 18,834 lines. Comment lines count towards the size of 20,843 lines but aren't priced as work. |
| What it is not | Not a quotation: nobody has offered to build it for that. Not a valuation: it says nothing about what the business is worth. Not a certified figure: no professional has signed it as one. |
Top priorities
Diagnosis: what the measurements show together
Architecture — module dependency graph
Architecture: which parts of the code depend on which
| uses → | 1 ChocolateyGui.Common | 2 ChocolateyGui.Common.Attributes | 3 ChocolateyGui.Common.Controls | 4 ChocolateyGui.Common.Enums | 5 ChocolateyGui.Common.Providers | 6 ChocolateyGui.Common.Startup | 7 ChocolateyGui.Common.Utilities | 8 ChocolateyGui.Common.ViewModels | 9 ChocolateyGui.Common.Windows.Commands | 10 ChocolateyGui.Common.Windows.Providers | 11 ChocolateyGui.Common.Windows.Startup | 12 ChocolateyGui.Common.Windows.Utilities.Converters | 13 ChocolateyGui.Common.Windows.Utilities.Extensions | 14 ChocolateyGuiCli.Startup | 15 ChocolateyGui | 16 ChocolateyGui.Common.Base | 17 ChocolateyGui.Common.ViewModels.Items | 18 ChocolateyGui.Common.Windows.Providers.PlatformProvider | 19 ChocolateyGui.Common.Models | 20 ChocolateyGui.Common.Windows.Utilities | 21 ChocolateyGui.Common.Models.Messages | 22 ChocolateyGui.Common.Services | 23 ChocolateyGui.Common.Windows.Controls | 24 ChocolateyGui.Common.Commands | 25 ChocolateyGui.Common.Windows.Controls.Dialogs | 26 ChocolateyGuiCli | 27 ChocolateyGui.Common.Windows.Views | 28 ChocolateyGui.Common.Windows.Services | 29 ChocolateyGui.Common.Windows | 30 ChocolateyGui.Common.Windows.Theming | 31 ChocolateyGui.Common.Windows.ViewModels.Items | 32 ChocolateyGui.Common.Windows.ViewModels |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 1 ChocolateyGui.Common | ||||||||||||||||||||||||||||||||
| 2 ChocolateyGui.Common.Attributes | ||||||||||||||||||||||||||||||||
| 3 ChocolateyGui.Common.Controls | ||||||||||||||||||||||||||||||||
| 4 ChocolateyGui.Common.Enums | ||||||||||||||||||||||||||||||||
| 5 ChocolateyGui.Common.Providers | ||||||||||||||||||||||||||||||||
| 6 ChocolateyGui.Common.Startup | ||||||||||||||||||||||||||||||||
| 7 ChocolateyGui.Common.Utilities | ||||||||||||||||||||||||||||||||
| 8 ChocolateyGui.Common.ViewModels | ||||||||||||||||||||||||||||||||
| 9 ChocolateyGui.Common.Windows.Commands | ||||||||||||||||||||||||||||||||
| 10 ChocolateyGui.Common.Windows.Providers | ||||||||||||||||||||||||||||||||
| 11 ChocolateyGui.Common.Windows.Startup | ||||||||||||||||||||||||||||||||
| 12 ChocolateyGui.Common.Windows.Utilities.Converters | ||||||||||||||||||||||||||||||||
| 13 ChocolateyGui.Common.Windows.Utilities.Extensions | ||||||||||||||||||||||||||||||||
| 14 ChocolateyGuiCli.Startup | ||||||||||||||||||||||||||||||||
| 15 ChocolateyGui | 1 | |||||||||||||||||||||||||||||||
| 16 ChocolateyGui.Common.Base | 1 | |||||||||||||||||||||||||||||||
| 17 ChocolateyGui.Common.ViewModels.Items | 1 | |||||||||||||||||||||||||||||||
| 18 ChocolateyGui.Common.Windows.Providers.PlatformProvider | 1 | |||||||||||||||||||||||||||||||
| 19 ChocolateyGui.Common.Models | 1 | |||||||||||||||||||||||||||||||
| 20 ChocolateyGui.Common.Windows.Utilities | 1 | 1 | ||||||||||||||||||||||||||||||
| 21 ChocolateyGui.Common.Models.Messages | 1 | 6 | ||||||||||||||||||||||||||||||
| 22 ChocolateyGui.Common.Services | 1 | 19 | ||||||||||||||||||||||||||||||
| 23 ChocolateyGui.Common.Windows.Controls | 1 | 2 | 1 | |||||||||||||||||||||||||||||
| 24 ChocolateyGui.Common.Commands | 1 | 5 | 3 | |||||||||||||||||||||||||||||
| 25 ChocolateyGui.Common.Windows.Controls.Dialogs | 1 | 1 | 1 | |||||||||||||||||||||||||||||
| 26 ChocolateyGuiCli | 1 | 1 | ||||||||||||||||||||||||||||||
| 27 ChocolateyGui.Common.Windows.Views | 1 | 2 | 1 | 1 | 3 | |||||||||||||||||||||||||||
| 28 ChocolateyGui.Common.Windows.Services | 2 | 2 | 1 | 2 | 14 | 4 | 1 | 4 | 1 | |||||||||||||||||||||||
| 29 ChocolateyGui.Common.Windows | 2 | 1 | ||||||||||||||||||||||||||||||
| 30 ChocolateyGui.Common.Windows.Theming | 1 | |||||||||||||||||||||||||||||||
| 31 ChocolateyGui.Common.Windows.ViewModels.Items | 2 | 1 | 2 | 7 | 5 | 3 | ||||||||||||||||||||||||||
| 32 ChocolateyGui.Common.Windows.ViewModels | 2 | 1 | 4 | 3 | 1 | 3 | 8 | 1 | 10 | 19 | 1 | 7 | 1 |
15→7 ChocolateyGui uses ChocolateyGui.Common.Utilities✕
- Connections
- 1 pair of types, where a type in ChocolateyGui uses a type in ChocolateyGui.Common.Utilities.
- The types involved
ChocolateyGui.App→ChocolateyGui.Common.Utilities.TranslationSource
- Direction
- ChocolateyGui uses ChocolateyGui.Common.Utilities, so a change to ChocolateyGui.Common.Utilities can break ChocolateyGui, while a change to ChocolateyGui can't break ChocolateyGui.Common.Utilities.
- Position
- Below the diagonal: ChocolateyGui uses a module listed above it, which is the healthy direction.
16→7 ChocolateyGui.Common.Base uses ChocolateyGui.Common.Utilities✕
- Connections
- 1 pair of types, where a type in ChocolateyGui.Common.Base uses a type in ChocolateyGui.Common.Utilities.
- The types involved
ChocolateyGui.Common.Base.ObservableBase→ChocolateyGui.Common.Utilities.TranslationSource
- Direction
- ChocolateyGui.Common.Base uses ChocolateyGui.Common.Utilities, so a change to ChocolateyGui.Common.Utilities can break ChocolateyGui.Common.Base, while a change to ChocolateyGui.Common.Base can't break ChocolateyGui.Common.Utilities.
- Position
- Below the diagonal: ChocolateyGui.Common.Base uses a module listed above it, which is the healthy direction.
17→19 ChocolateyGui.Common.ViewModels.Items uses ChocolateyGui.Common.Models part of a loop✕
- Connections
- 1 pair of types, where a type in ChocolateyGui.Common.ViewModels.Items uses a type in ChocolateyGui.Common.Models.
- The types involved
ChocolateyGui.Common.ViewModels.Items.IPackageViewModel→ChocolateyGui.Common.Models.ChocolateySource
- Direction
- ChocolateyGui.Common.ViewModels.Items uses ChocolateyGui.Common.Models, so a change to ChocolateyGui.Common.Models can break ChocolateyGui.Common.ViewModels.Items, while a change to ChocolateyGui.Common.ViewModels.Items can't break ChocolateyGui.Common.Models.
- 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→10 ChocolateyGui.Common.Windows.Providers.PlatformProvider uses ChocolateyGui.Common.Windows.Providers✕
- Connections
- 1 pair of types, where a type in ChocolateyGui.Common.Windows.Providers.PlatformProvider uses a type in ChocolateyGui.Common.Windows.Providers.
- The types involved
ChocolateyGui.Common.Windows.Providers.PlatformProvider.Windows7PlatformProvider→ChocolateyGui.Common.Windows.Providers.IPlatformProvider
- Direction
- ChocolateyGui.Common.Windows.Providers.PlatformProvider uses ChocolateyGui.Common.Windows.Providers, so a change to ChocolateyGui.Common.Windows.Providers can break ChocolateyGui.Common.Windows.Providers.PlatformProvider, while a change to ChocolateyGui.Common.Windows.Providers.PlatformProvider can't break ChocolateyGui.Common.Windows.Providers.
- Position
- Below the diagonal: ChocolateyGui.Common.Windows.Providers.PlatformProvider uses a module listed above it, which is the healthy direction.
19→17 ChocolateyGui.Common.Models uses ChocolateyGui.Common.ViewModels.Items✕
- Connections
- 1 pair of types, where a type in ChocolateyGui.Common.Models uses a type in ChocolateyGui.Common.ViewModels.Items.
- The types involved
ChocolateyGui.Common.Models.PackageSearchResults→ChocolateyGui.Common.ViewModels.Items.IPackageViewModel
- Direction
- ChocolateyGui.Common.Models uses ChocolateyGui.Common.ViewModels.Items, so a change to ChocolateyGui.Common.ViewModels.Items can break ChocolateyGui.Common.Models, while a change to ChocolateyGui.Common.Models can't break ChocolateyGui.Common.ViewModels.Items.
- Position
- Below the diagonal: ChocolateyGui.Common.Models uses a module listed above it, which is the healthy direction.
20→16 ChocolateyGui.Common.Windows.Utilities uses ChocolateyGui.Common.Base✕
- Connections
- 1 pair of types, where a type in ChocolateyGui.Common.Windows.Utilities uses a type in ChocolateyGui.Common.Base.
- The types involved
ChocolateyGui.Common.Windows.Utilities.NotifyTaskCompletion→ChocolateyGui.Common.Base.ObservableBase
- Direction
- ChocolateyGui.Common.Windows.Utilities uses ChocolateyGui.Common.Base, so a change to ChocolateyGui.Common.Base can break ChocolateyGui.Common.Windows.Utilities, while a change to ChocolateyGui.Common.Windows.Utilities can't break ChocolateyGui.Common.Base.
- Position
- Below the diagonal: ChocolateyGui.Common.Windows.Utilities uses a module listed above it, which is the healthy direction.
20→17 ChocolateyGui.Common.Windows.Utilities uses ChocolateyGui.Common.ViewModels.Items✕
- Connections
- 1 pair of types, where a type in ChocolateyGui.Common.Windows.Utilities uses a type in ChocolateyGui.Common.ViewModels.Items.
- The types involved
ChocolateyGui.Common.Windows.Utilities.PackageAuthorsComparer→ChocolateyGui.Common.ViewModels.Items.IPackageViewModel
- Direction
- ChocolateyGui.Common.Windows.Utilities uses ChocolateyGui.Common.ViewModels.Items, so a change to ChocolateyGui.Common.ViewModels.Items can break ChocolateyGui.Common.Windows.Utilities, while a change to ChocolateyGui.Common.Windows.Utilities can't break ChocolateyGui.Common.ViewModels.Items.
- Position
- Below the diagonal: ChocolateyGui.Common.Windows.Utilities uses a module listed above it, which is the healthy direction.
21→17 ChocolateyGui.Common.Models.Messages uses ChocolateyGui.Common.ViewModels.Items✕
- Connections
- 1 pair of types, where a type in ChocolateyGui.Common.Models.Messages uses a type in ChocolateyGui.Common.ViewModels.Items.
- The types involved
ChocolateyGui.Common.Models.Messages.ShowPackageDetailsMessage→ChocolateyGui.Common.ViewModels.Items.IPackageViewModel
- Direction
- ChocolateyGui.Common.Models.Messages uses ChocolateyGui.Common.ViewModels.Items, so a change to ChocolateyGui.Common.ViewModels.Items can break ChocolateyGui.Common.Models.Messages, while a change to ChocolateyGui.Common.Models.Messages can't break ChocolateyGui.Common.ViewModels.Items.
- Position
- Below the diagonal: ChocolateyGui.Common.Models.Messages uses a module listed above it, which is the healthy direction.
21→19 ChocolateyGui.Common.Models.Messages uses ChocolateyGui.Common.Models✕
- Connections
- 6 pairs of types, where a type in ChocolateyGui.Common.Models.Messages uses a type in ChocolateyGui.Common.Models.
- The types involved
ChocolateyGui.Common.Models.Messages.PackageInstalledMessage→ChocolateyGui.Common.Models.ChocolateySourceChocolateyGui.Common.Models.Messages.PackageOutdatedMessage→ChocolateyGui.Common.Models.ChocolateySourceChocolateyGui.Common.Models.Messages.PackagePinnedMessage→ChocolateyGui.Common.Models.ChocolateySourceChocolateyGui.Common.Models.Messages.PackageUninstalledMessage→ChocolateyGui.Common.Models.ChocolateySourceChocolateyGui.Common.Models.Messages.PackageUnpinnedMessage→ChocolateyGui.Common.Models.ChocolateySourceChocolateyGui.Common.Models.Messages.PackageUpgradedMessage→ChocolateyGui.Common.Models.ChocolateySource
- Direction
- ChocolateyGui.Common.Models.Messages uses ChocolateyGui.Common.Models, so a change to ChocolateyGui.Common.Models can break ChocolateyGui.Common.Models.Messages, while a change to ChocolateyGui.Common.Models.Messages can't break ChocolateyGui.Common.Models.
- Position
- Below the diagonal: ChocolateyGui.Common.Models.Messages uses a module listed above it, which is the healthy direction.
22→7 ChocolateyGui.Common.Services uses ChocolateyGui.Common.Utilities✕
- Connections
- 1 pair of types, where a type in ChocolateyGui.Common.Services uses a type in ChocolateyGui.Common.Utilities.
- The types involved
ChocolateyGui.Common.Services.ConfigService→ChocolateyGui.Common.Utilities.TranslationSource
- Direction
- ChocolateyGui.Common.Services uses ChocolateyGui.Common.Utilities, so a change to ChocolateyGui.Common.Utilities can break ChocolateyGui.Common.Services, while a change to ChocolateyGui.Common.Services can't break ChocolateyGui.Common.Utilities.
- Position
- Below the diagonal: ChocolateyGui.Common.Services uses a module listed above it, which is the healthy direction.
22→19 ChocolateyGui.Common.Services uses ChocolateyGui.Common.Models✕
- Connections
- 19 pairs of types, where a type in ChocolateyGui.Common.Services uses a type in ChocolateyGui.Common.Models.
- The types involved
ChocolateyGui.Common.Services.ChocolateyGuiCacheService→ChocolateyGui.Common.Models.ChocolateySourceChocolateyGui.Common.Services.ConfigService→ChocolateyGui.Common.Models.AppConfigurationChocolateyGui.Common.Services.ConfigService→ChocolateyGui.Common.Models.ChocolateyGuiConfigurationChocolateyGui.Common.Services.ConfigService→ChocolateyGui.Common.Models.ChocolateyGuiFeatureChocolateyGui.Common.Services.ConfigService→ChocolateyGui.Common.Models.ChocolateyGuiSettingChocolateyGui.Common.Services.IChocolateyGuiCacheService→ChocolateyGui.Common.Models.ChocolateySourceChocolateyGui.Common.Services.IChocolateyService→ChocolateyGui.Common.Models.AdvancedInstallChocolateyGui.Common.Services.IChocolateyService→ChocolateyGui.Common.Models.ChocolateyFeatureChocolateyGui.Common.Services.IChocolateyService→ChocolateyGui.Common.Models.ChocolateySettingChocolateyGui.Common.Services.IChocolateyService→ChocolateyGui.Common.Models.ChocolateySourceChocolateyGui.Common.Services.IChocolateyService→ChocolateyGui.Common.Models.OutdatedPackageChocolateyGui.Common.Services.IChocolateyService→ChocolateyGui.Common.Models.PackageChocolateyGui.Common.Services.IChocolateyService→ChocolateyGui.Common.Models.PackageOperationResultChocolateyGui.Common.Services.IChocolateyService→ChocolateyGui.Common.Models.PackageResultsChocolateyGui.Common.Services.IChocolateyService→ChocolateyGui.Common.Models.PackageSearchOptionsChocolateyGui.Common.Services.IConfigService→ChocolateyGui.Common.Models.AppConfigurationChocolateyGui.Common.Services.IConfigService→ChocolateyGui.Common.Models.ChocolateyGuiConfigurationChocolateyGui.Common.Services.IConfigService→ChocolateyGui.Common.Models.ChocolateyGuiFeatureChocolateyGui.Common.Services.IConfigService→ChocolateyGui.Common.Models.ChocolateyGuiSetting
- Direction
- ChocolateyGui.Common.Services uses ChocolateyGui.Common.Models, so a change to ChocolateyGui.Common.Models can break ChocolateyGui.Common.Services, while a change to ChocolateyGui.Common.Services can't break ChocolateyGui.Common.Models.
- Position
- Below the diagonal: ChocolateyGui.Common.Services uses a module listed above it, which is the healthy direction.
23→3 ChocolateyGui.Common.Windows.Controls uses ChocolateyGui.Common.Controls✕
- Connections
- 1 pair of types, where a type in ChocolateyGui.Common.Windows.Controls uses a type in ChocolateyGui.Common.Controls.
- The types involved
ChocolateyGui.Common.Windows.Controls.FauxPowerShellConsole→ChocolateyGui.Common.Controls.ObservableRingBufferCollection
- Direction
- ChocolateyGui.Common.Windows.Controls uses ChocolateyGui.Common.Controls, so a change to ChocolateyGui.Common.Controls can break ChocolateyGui.Common.Windows.Controls, while a change to ChocolateyGui.Common.Windows.Controls can't break ChocolateyGui.Common.Controls.
- Position
- Below the diagonal: ChocolateyGui.Common.Windows.Controls uses a module listed above it, which is the healthy direction.
23→19 ChocolateyGui.Common.Windows.Controls uses ChocolateyGui.Common.Models✕
- Connections
- 2 pairs of types, where a type in ChocolateyGui.Common.Windows.Controls uses a type in ChocolateyGui.Common.Models.
- The types involved
ChocolateyGui.Common.Windows.Controls.FauxPowerShellConsole→ChocolateyGui.Common.Models.PowerShellOutputLineChocolateyGui.Common.Windows.Controls.RunStringOnUI→ChocolateyGui.Common.Models.PowerShellOutputLine
- Direction
- ChocolateyGui.Common.Windows.Controls uses ChocolateyGui.Common.Models, so a change to ChocolateyGui.Common.Models can break ChocolateyGui.Common.Windows.Controls, while a change to ChocolateyGui.Common.Windows.Controls can't break ChocolateyGui.Common.Models.
- Position
- Below the diagonal: ChocolateyGui.Common.Windows.Controls uses a module listed above it, which is the healthy direction.
23→28 ChocolateyGui.Common.Windows.Controls uses ChocolateyGui.Common.Windows.Services part of a loop✕
- Connections
- 1 pair of types, where a type in ChocolateyGui.Common.Windows.Controls uses a type in ChocolateyGui.Common.Windows.Services.
- The types involved
ChocolateyGui.Common.Windows.Controls.InternetImage→ChocolateyGui.Common.Windows.Services.IPackageIconService
- Direction
- ChocolateyGui.Common.Windows.Controls uses ChocolateyGui.Common.Windows.Services, so a change to ChocolateyGui.Common.Windows.Services can break ChocolateyGui.Common.Windows.Controls, while a change to ChocolateyGui.Common.Windows.Controls can't break ChocolateyGui.Common.Windows.Services.
- 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→7 ChocolateyGui.Common.Commands uses ChocolateyGui.Common.Utilities✕
- Connections
- 1 pair of types, where a type in ChocolateyGui.Common.Commands uses a type in ChocolateyGui.Common.Utilities.
- The types involved
ChocolateyGui.Common.Commands.BaseCommand→ChocolateyGui.Common.Utilities.TranslationSource
- Direction
- ChocolateyGui.Common.Commands uses ChocolateyGui.Common.Utilities, so a change to ChocolateyGui.Common.Utilities can break ChocolateyGui.Common.Commands, while a change to ChocolateyGui.Common.Commands can't break ChocolateyGui.Common.Utilities.
- Position
- Below the diagonal: ChocolateyGui.Common.Commands uses a module listed above it, which is the healthy direction.
24→19 ChocolateyGui.Common.Commands uses ChocolateyGui.Common.Models✕
- Connections
- 5 pairs of types, where a type in ChocolateyGui.Common.Commands uses a type in ChocolateyGui.Common.Models.
- The types involved
ChocolateyGui.Common.Commands.ConfigCommand→ChocolateyGui.Common.Models.ChocolateyGuiConfigurationChocolateyGui.Common.Commands.FeatureCommand→ChocolateyGui.Common.Models.ChocolateyGuiConfigurationChocolateyGui.Common.Commands.GenericRunner→ChocolateyGui.Common.Models.ChocolateyGuiConfigurationChocolateyGui.Common.Commands.ICommand→ChocolateyGui.Common.Models.ChocolateyGuiConfigurationChocolateyGui.Common.Commands.PurgeCommand→ChocolateyGui.Common.Models.ChocolateyGuiConfiguration
- Direction
- ChocolateyGui.Common.Commands uses ChocolateyGui.Common.Models, so a change to ChocolateyGui.Common.Models can break ChocolateyGui.Common.Commands, while a change to ChocolateyGui.Common.Commands can't break ChocolateyGui.Common.Models.
- Position
- Below the diagonal: ChocolateyGui.Common.Commands uses a module listed above it, which is the healthy direction.
24→22 ChocolateyGui.Common.Commands uses ChocolateyGui.Common.Services✕
- Connections
- 3 pairs of types, where a type in ChocolateyGui.Common.Commands uses a type in ChocolateyGui.Common.Services.
- The types involved
ChocolateyGui.Common.Commands.ConfigCommand→ChocolateyGui.Common.Services.IConfigServiceChocolateyGui.Common.Commands.FeatureCommand→ChocolateyGui.Common.Services.IConfigServiceChocolateyGui.Common.Commands.PurgeCommand→ChocolateyGui.Common.Services.IChocolateyGuiCacheService
- Direction
- ChocolateyGui.Common.Commands uses ChocolateyGui.Common.Services, so a change to ChocolateyGui.Common.Services can break ChocolateyGui.Common.Commands, while a change to ChocolateyGui.Common.Commands can't break ChocolateyGui.Common.Services.
- Position
- Below the diagonal: ChocolateyGui.Common.Commands uses a module listed above it, which is the healthy direction.
25→3 ChocolateyGui.Common.Windows.Controls.Dialogs uses ChocolateyGui.Common.Controls✕
- Connections
- 1 pair of types, where a type in ChocolateyGui.Common.Windows.Controls.Dialogs uses a type in ChocolateyGui.Common.Controls.
- The types involved
ChocolateyGui.Common.Windows.Controls.Dialogs.ChocolateyDialog→ChocolateyGui.Common.Controls.ObservableRingBufferCollection
- Direction
- ChocolateyGui.Common.Windows.Controls.Dialogs uses ChocolateyGui.Common.Controls, so a change to ChocolateyGui.Common.Controls can break ChocolateyGui.Common.Windows.Controls.Dialogs, while a change to ChocolateyGui.Common.Windows.Controls.Dialogs can't break ChocolateyGui.Common.Controls.
- Position
- Below the diagonal: ChocolateyGui.Common.Windows.Controls.Dialogs uses a module listed above it, which is the healthy direction.
25→19 ChocolateyGui.Common.Windows.Controls.Dialogs uses ChocolateyGui.Common.Models✕
- Connections
- 1 pair of types, where a type in ChocolateyGui.Common.Windows.Controls.Dialogs uses a type in ChocolateyGui.Common.Models.
- The types involved
ChocolateyGui.Common.Windows.Controls.Dialogs.ChocolateyDialog→ChocolateyGui.Common.Models.PowerShellOutputLine
- Direction
- ChocolateyGui.Common.Windows.Controls.Dialogs uses ChocolateyGui.Common.Models, so a change to ChocolateyGui.Common.Models can break ChocolateyGui.Common.Windows.Controls.Dialogs, while a change to ChocolateyGui.Common.Windows.Controls.Dialogs can't break ChocolateyGui.Common.Models.
- Position
- Below the diagonal: ChocolateyGui.Common.Windows.Controls.Dialogs uses a module listed above it, which is the healthy direction.
25→23 ChocolateyGui.Common.Windows.Controls.Dialogs uses ChocolateyGui.Common.Windows.Controls✕
- Connections
- 1 pair of types, where a type in ChocolateyGui.Common.Windows.Controls.Dialogs uses a type in ChocolateyGui.Common.Windows.Controls.
- The types involved
ChocolateyGui.Common.Windows.Controls.Dialogs.ChocolateyDialog→ChocolateyGui.Common.Windows.Controls.FauxPowerShellConsole
- Direction
- ChocolateyGui.Common.Windows.Controls.Dialogs uses ChocolateyGui.Common.Windows.Controls, so a change to ChocolateyGui.Common.Windows.Controls can break ChocolateyGui.Common.Windows.Controls.Dialogs, while a change to ChocolateyGui.Common.Windows.Controls.Dialogs can't break ChocolateyGui.Common.Windows.Controls.
- Position
- Below the diagonal: ChocolateyGui.Common.Windows.Controls.Dialogs uses a module listed above it, which is the healthy direction.
26→19 ChocolateyGuiCli uses ChocolateyGui.Common.Models✕
- Connections
- 1 pair of types, where a type in ChocolateyGuiCli uses a type in ChocolateyGui.Common.Models.
- The types involved
ChocolateyGuiCli.Runner→ChocolateyGui.Common.Models.ChocolateyGuiConfiguration
- Direction
- ChocolateyGuiCli uses ChocolateyGui.Common.Models, so a change to ChocolateyGui.Common.Models can break ChocolateyGuiCli, while a change to ChocolateyGuiCli can't break ChocolateyGui.Common.Models.
- Position
- Below the diagonal: ChocolateyGuiCli uses a module listed above it, which is the healthy direction.
26→22 ChocolateyGuiCli uses ChocolateyGui.Common.Services✕
- Connections
- 1 pair of types, where a type in ChocolateyGuiCli uses a type in ChocolateyGui.Common.Services.
- The types involved
ChocolateyGuiCli.Runner→ChocolateyGui.Common.Services.IConfigService
- Direction
- ChocolateyGuiCli uses ChocolateyGui.Common.Services, so a change to ChocolateyGui.Common.Services can break ChocolateyGuiCli, while a change to ChocolateyGuiCli can't break ChocolateyGui.Common.Services.
- Position
- Below the diagonal: ChocolateyGuiCli uses a module listed above it, which is the healthy direction.
27→5 ChocolateyGui.Common.Windows.Views uses ChocolateyGui.Common.Providers✕
- Connections
- 1 pair of types, where a type in ChocolateyGui.Common.Windows.Views uses a type in ChocolateyGui.Common.Providers.
- The types involved
ChocolateyGui.Common.Windows.Views.ShellView→ChocolateyGui.Common.Providers.IChocolateyConfigurationProvider
- Direction
- ChocolateyGui.Common.Windows.Views uses ChocolateyGui.Common.Providers, so a change to ChocolateyGui.Common.Providers can break ChocolateyGui.Common.Windows.Views, while a change to ChocolateyGui.Common.Windows.Views can't break ChocolateyGui.Common.Providers.
- Position
- Below the diagonal: ChocolateyGui.Common.Windows.Views uses a module listed above it, which is the healthy direction.
27→21 ChocolateyGui.Common.Windows.Views uses ChocolateyGui.Common.Models.Messages✕
- Connections
- 2 pairs of types, where a type in ChocolateyGui.Common.Windows.Views uses a type in ChocolateyGui.Common.Models.Messages.
- The types involved
ChocolateyGui.Common.Windows.Views.RemoteSourceView→ChocolateyGui.Common.Models.Messages.ResetScrollPositionMessageChocolateyGui.Common.Windows.Views.SettingsView→ChocolateyGui.Common.Models.Messages.SourcesUpdatedMessage
- Direction
- ChocolateyGui.Common.Windows.Views uses ChocolateyGui.Common.Models.Messages, so a change to ChocolateyGui.Common.Models.Messages can break ChocolateyGui.Common.Windows.Views, while a change to ChocolateyGui.Common.Windows.Views can't break ChocolateyGui.Common.Models.Messages.
- Position
- Below the diagonal: ChocolateyGui.Common.Windows.Views uses a module listed above it, which is the healthy direction.
27→22 ChocolateyGui.Common.Windows.Views uses ChocolateyGui.Common.Services✕
- Connections
- 1 pair of types, where a type in ChocolateyGui.Common.Windows.Views uses a type in ChocolateyGui.Common.Services.
- The types involved
ChocolateyGui.Common.Windows.Views.ShellView→ChocolateyGui.Common.Services.IConfigService
- Direction
- ChocolateyGui.Common.Windows.Views uses ChocolateyGui.Common.Services, so a change to ChocolateyGui.Common.Services can break ChocolateyGui.Common.Windows.Views, while a change to ChocolateyGui.Common.Windows.Views can't break ChocolateyGui.Common.Services.
- Position
- Below the diagonal: ChocolateyGui.Common.Windows.Views uses a module listed above it, which is the healthy direction.
27→25 ChocolateyGui.Common.Windows.Views uses ChocolateyGui.Common.Windows.Controls.Dialogs✕
- Connections
- 1 pair of types, where a type in ChocolateyGui.Common.Windows.Views uses a type in ChocolateyGui.Common.Windows.Controls.Dialogs.
- The types involved
ChocolateyGui.Common.Windows.Views.ShellView→ChocolateyGui.Common.Windows.Controls.Dialogs.ChocolateyDialogController
- Direction
- ChocolateyGui.Common.Windows.Views uses ChocolateyGui.Common.Windows.Controls.Dialogs, so a change to ChocolateyGui.Common.Windows.Controls.Dialogs can break ChocolateyGui.Common.Windows.Views, while a change to ChocolateyGui.Common.Windows.Views can't break ChocolateyGui.Common.Windows.Controls.Dialogs.
- Position
- Below the diagonal: ChocolateyGui.Common.Windows.Views uses a module listed above it, which is the healthy direction.
27→28 ChocolateyGui.Common.Windows.Views uses ChocolateyGui.Common.Windows.Services part of a loop✕
- Connections
- 3 pairs of types, where a type in ChocolateyGui.Common.Windows.Views uses a type in ChocolateyGui.Common.Windows.Services.
- The types involved
ChocolateyGui.Common.Windows.Views.ShellView→ChocolateyGui.Common.Windows.Services.IDialogServiceChocolateyGui.Common.Windows.Views.ShellView→ChocolateyGui.Common.Windows.Services.IImageServiceChocolateyGui.Common.Windows.Views.ShellView→ChocolateyGui.Common.Windows.Services.IProgressService
- Direction
- ChocolateyGui.Common.Windows.Views uses ChocolateyGui.Common.Windows.Services, so a change to ChocolateyGui.Common.Windows.Services can break ChocolateyGui.Common.Windows.Views, while a change to ChocolateyGui.Common.Windows.Views can't break ChocolateyGui.Common.Windows.Services.
- 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→3 ChocolateyGui.Common.Windows.Services uses ChocolateyGui.Common.Controls✕
- Connections
- 2 pairs of types, where a type in ChocolateyGui.Common.Windows.Services uses a type in ChocolateyGui.Common.Controls.
- The types involved
ChocolateyGui.Common.Windows.Services.IProgressService→ChocolateyGui.Common.Controls.ObservableRingBufferCollectionChocolateyGui.Common.Windows.Services.ProgressService→ChocolateyGui.Common.Controls.ObservableRingBufferCollection
- Direction
- ChocolateyGui.Common.Windows.Services uses ChocolateyGui.Common.Controls, so a change to ChocolateyGui.Common.Controls can break ChocolateyGui.Common.Windows.Services, while a change to ChocolateyGui.Common.Windows.Services can't break ChocolateyGui.Common.Controls.
- Position
- Below the diagonal: ChocolateyGui.Common.Windows.Services uses a module listed above it, which is the healthy direction.
28→4 ChocolateyGui.Common.Windows.Services uses ChocolateyGui.Common.Enums✕
- Connections
- 2 pairs of types, where a type in ChocolateyGui.Common.Windows.Services uses a type in ChocolateyGui.Common.Enums.
- The types involved
ChocolateyGui.Common.Windows.Services.BundledThemeService→ChocolateyGui.Common.Enums.ThemeModeChocolateyGui.Common.Windows.Services.IBundledThemeService→ChocolateyGui.Common.Enums.ThemeMode
- Direction
- ChocolateyGui.Common.Windows.Services uses ChocolateyGui.Common.Enums, so a change to ChocolateyGui.Common.Enums can break ChocolateyGui.Common.Windows.Services, while a change to ChocolateyGui.Common.Windows.Services can't break ChocolateyGui.Common.Enums.
- Position
- Below the diagonal: ChocolateyGui.Common.Windows.Services uses a module listed above it, which is the healthy direction.
28→5 ChocolateyGui.Common.Windows.Services uses ChocolateyGui.Common.Providers✕
- Connections
- 1 pair of types, where a type in ChocolateyGui.Common.Windows.Services uses a type in ChocolateyGui.Common.Providers.
- The types involved
ChocolateyGui.Common.Windows.Services.PackageArgumentsService→ChocolateyGui.Common.Providers.IChocolateyConfigurationProvider
- Direction
- ChocolateyGui.Common.Windows.Services uses ChocolateyGui.Common.Providers, so a change to ChocolateyGui.Common.Providers can break ChocolateyGui.Common.Windows.Services, while a change to ChocolateyGui.Common.Windows.Services can't break ChocolateyGui.Common.Providers.
- Position
- Below the diagonal: ChocolateyGui.Common.Windows.Services uses a module listed above it, which is the healthy direction.
28→16 ChocolateyGui.Common.Windows.Services uses ChocolateyGui.Common.Base✕
- Connections
- 2 pairs of types, where a type in ChocolateyGui.Common.Windows.Services uses a type in ChocolateyGui.Common.Base.
- The types involved
ChocolateyGui.Common.Windows.Services.BundledThemeService→ChocolateyGui.Common.Base.ObservableBaseChocolateyGui.Common.Windows.Services.ProgressService→ChocolateyGui.Common.Base.ObservableBase
- Direction
- ChocolateyGui.Common.Windows.Services uses ChocolateyGui.Common.Base, so a change to ChocolateyGui.Common.Base can break ChocolateyGui.Common.Windows.Services, while a change to ChocolateyGui.Common.Windows.Services can't break ChocolateyGui.Common.Base.
- Position
- Below the diagonal: ChocolateyGui.Common.Windows.Services uses a module listed above it, which is the healthy direction.
28→19 ChocolateyGui.Common.Windows.Services uses ChocolateyGui.Common.Models✕
- Connections
- 14 pairs of types, where a type in ChocolateyGui.Common.Windows.Services uses a type in ChocolateyGui.Common.Models.
- The types involved
ChocolateyGui.Common.Windows.Services.ChocolateyService→ChocolateyGui.Common.Models.AdvancedInstallChocolateyGui.Common.Windows.Services.ChocolateyService→ChocolateyGui.Common.Models.ChocolateyFeatureChocolateyGui.Common.Windows.Services.ChocolateyService→ChocolateyGui.Common.Models.ChocolateySettingChocolateyGui.Common.Windows.Services.ChocolateyService→ChocolateyGui.Common.Models.ChocolateySourceChocolateyGui.Common.Windows.Services.ChocolateyService→ChocolateyGui.Common.Models.LogMessageChocolateyGui.Common.Windows.Services.ChocolateyService→ChocolateyGui.Common.Models.OutdatedPackageChocolateyGui.Common.Windows.Services.ChocolateyService→ChocolateyGui.Common.Models.PackageChocolateyGui.Common.Windows.Services.ChocolateyService→ChocolateyGui.Common.Models.PackageOperationResultChocolateyGui.Common.Windows.Services.ChocolateyService→ChocolateyGui.Common.Models.PackageResultsChocolateyGui.Common.Windows.Services.ChocolateyService→ChocolateyGui.Common.Models.PackageSearchOptionsChocolateyGui.Common.Windows.Services.IProgressService→ChocolateyGui.Common.Models.PowerShellLineTypeChocolateyGui.Common.Windows.Services.IProgressService→ChocolateyGui.Common.Models.PowerShellOutputLineChocolateyGui.Common.Windows.Services.ProgressService→ChocolateyGui.Common.Models.PowerShellLineTypeChocolateyGui.Common.Windows.Services.ProgressService→ChocolateyGui.Common.Models.PowerShellOutputLine
- Direction
- ChocolateyGui.Common.Windows.Services uses ChocolateyGui.Common.Models, so a change to ChocolateyGui.Common.Models can break ChocolateyGui.Common.Windows.Services, while a change to ChocolateyGui.Common.Windows.Services can't break ChocolateyGui.Common.Models.
- Position
- Below the diagonal: ChocolateyGui.Common.Windows.Services uses a module listed above it, which is the healthy direction.
28→22 ChocolateyGui.Common.Windows.Services uses ChocolateyGui.Common.Services✕
- Connections
- 4 pairs of types, where a type in ChocolateyGui.Common.Windows.Services uses a type in ChocolateyGui.Common.Services.
- The types involved
ChocolateyGui.Common.Windows.Services.ChocolateyService→ChocolateyGui.Common.Services.IChocolateyServiceChocolateyGui.Common.Windows.Services.ChocolateyService→ChocolateyGui.Common.Services.IConfigServiceChocolateyGui.Common.Windows.Services.PersistenceService→ChocolateyGui.Common.Services.IPersistenceServiceChocolateyGui.Common.Windows.Services.SplashScreenService→ChocolateyGui.Common.Services.ISplashScreenService
- Direction
- ChocolateyGui.Common.Windows.Services uses ChocolateyGui.Common.Services, so a change to ChocolateyGui.Common.Services can break ChocolateyGui.Common.Windows.Services, while a change to ChocolateyGui.Common.Windows.Services can't break ChocolateyGui.Common.Services.
- Position
- Below the diagonal: ChocolateyGui.Common.Windows.Services uses a module listed above it, which is the healthy direction.
28→25 ChocolateyGui.Common.Windows.Services uses ChocolateyGui.Common.Windows.Controls.Dialogs✕
- Connections
- 1 pair of types, where a type in ChocolateyGui.Common.Windows.Services uses a type in ChocolateyGui.Common.Windows.Controls.Dialogs.
- The types involved
ChocolateyGui.Common.Windows.Services.ProgressService→ChocolateyGui.Common.Windows.Controls.Dialogs.ChocolateyDialogController
- Direction
- ChocolateyGui.Common.Windows.Services uses ChocolateyGui.Common.Windows.Controls.Dialogs, so a change to ChocolateyGui.Common.Windows.Controls.Dialogs can break ChocolateyGui.Common.Windows.Services, while a change to ChocolateyGui.Common.Windows.Services can't break ChocolateyGui.Common.Windows.Controls.Dialogs.
- Position
- Below the diagonal: ChocolateyGui.Common.Windows.Services uses a module listed above it, which is the healthy direction.
28→27 ChocolateyGui.Common.Windows.Services uses ChocolateyGui.Common.Windows.Views✕
- Connections
- 4 pairs of types, where a type in ChocolateyGui.Common.Windows.Services uses a type in ChocolateyGui.Common.Windows.Views.
- The types involved
ChocolateyGui.Common.Windows.Services.DialogService→ChocolateyGui.Common.Windows.Views.ShellViewChocolateyGui.Common.Windows.Services.IDialogService→ChocolateyGui.Common.Windows.Views.ShellViewChocolateyGui.Common.Windows.Services.IProgressService→ChocolateyGui.Common.Windows.Views.ShellViewChocolateyGui.Common.Windows.Services.ProgressService→ChocolateyGui.Common.Windows.Views.ShellView
- Direction
- ChocolateyGui.Common.Windows.Services uses ChocolateyGui.Common.Windows.Views, so a change to ChocolateyGui.Common.Windows.Views can break ChocolateyGui.Common.Windows.Services, while a change to ChocolateyGui.Common.Windows.Services can't break ChocolateyGui.Common.Windows.Views.
- Position
- Below the diagonal: ChocolateyGui.Common.Windows.Services uses a module listed above it, which is the healthy direction.
28→29 ChocolateyGui.Common.Windows.Services uses ChocolateyGui.Common.Windows part of a loop✕
- Connections
- 1 pair of types, where a type in ChocolateyGui.Common.Windows.Services uses a type in ChocolateyGui.Common.Windows.
- The types involved
ChocolateyGui.Common.Windows.Services.ChocolateyService→ChocolateyGui.Common.Windows.SerilogLogger
- Direction
- ChocolateyGui.Common.Windows.Services uses ChocolateyGui.Common.Windows, so a change to ChocolateyGui.Common.Windows can break ChocolateyGui.Common.Windows.Services, while a change to ChocolateyGui.Common.Windows.Services can't break ChocolateyGui.Common.Windows.
- 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→19 ChocolateyGui.Common.Windows uses ChocolateyGui.Common.Models✕
- Connections
- 2 pairs of types, where a type in ChocolateyGui.Common.Windows uses a type in ChocolateyGui.Common.Models.
- The types involved
ChocolateyGui.Common.Windows.InterceptMessages→ChocolateyGui.Common.Models.LogMessageChocolateyGui.Common.Windows.SerilogLogger→ChocolateyGui.Common.Models.LogMessage
- Direction
- ChocolateyGui.Common.Windows uses ChocolateyGui.Common.Models, so a change to ChocolateyGui.Common.Models can break ChocolateyGui.Common.Windows, while a change to ChocolateyGui.Common.Windows can't break ChocolateyGui.Common.Models.
- Position
- Below the diagonal: ChocolateyGui.Common.Windows uses a module listed above it, which is the healthy direction.
29→28 ChocolateyGui.Common.Windows uses ChocolateyGui.Common.Windows.Services✕
- Connections
- 1 pair of types, where a type in ChocolateyGui.Common.Windows uses a type in ChocolateyGui.Common.Windows.Services.
- The types involved
ChocolateyGui.Common.Windows.SerilogLogger→ChocolateyGui.Common.Windows.Services.IProgressService
- Direction
- ChocolateyGui.Common.Windows uses ChocolateyGui.Common.Windows.Services, so a change to ChocolateyGui.Common.Windows.Services can break ChocolateyGui.Common.Windows, while a change to ChocolateyGui.Common.Windows can't break ChocolateyGui.Common.Windows.Services.
- Position
- Below the diagonal: ChocolateyGui.Common.Windows uses a module listed above it, which is the healthy direction.
30→28 ChocolateyGui.Common.Windows.Theming uses ChocolateyGui.Common.Windows.Services✕
- Connections
- 1 pair of types, where a type in ChocolateyGui.Common.Windows.Theming uses a type in ChocolateyGui.Common.Windows.Services.
- The types involved
ChocolateyGui.Common.Windows.Theming.ThemeAssist→ChocolateyGui.Common.Windows.Services.IBundledThemeService
- Direction
- ChocolateyGui.Common.Windows.Theming uses ChocolateyGui.Common.Windows.Services, so a change to ChocolateyGui.Common.Windows.Services can break ChocolateyGui.Common.Windows.Theming, while a change to ChocolateyGui.Common.Windows.Theming can't break ChocolateyGui.Common.Windows.Services.
- Position
- Below the diagonal: ChocolateyGui.Common.Windows.Theming uses a module listed above it, which is the healthy direction.
31→16 ChocolateyGui.Common.Windows.ViewModels.Items uses ChocolateyGui.Common.Base✕
- Connections
- 2 pairs of types, where a type in ChocolateyGui.Common.Windows.ViewModels.Items uses a type in ChocolateyGui.Common.Base.
- The types involved
ChocolateyGui.Common.Windows.ViewModels.Items.PackageViewModel→ChocolateyGui.Common.Base.ObservableBaseChocolateyGui.Common.Windows.ViewModels.Items.SourceViewModel→ChocolateyGui.Common.Base.ObservableBase
- Direction
- ChocolateyGui.Common.Windows.ViewModels.Items uses ChocolateyGui.Common.Base, so a change to ChocolateyGui.Common.Base can break ChocolateyGui.Common.Windows.ViewModels.Items, while a change to ChocolateyGui.Common.Windows.ViewModels.Items can't break ChocolateyGui.Common.Base.
- Position
- Below the diagonal: ChocolateyGui.Common.Windows.ViewModels.Items uses a module listed above it, which is the healthy direction.
31→17 ChocolateyGui.Common.Windows.ViewModels.Items uses ChocolateyGui.Common.ViewModels.Items✕
- Connections
- 1 pair of types, where a type in ChocolateyGui.Common.Windows.ViewModels.Items uses a type in ChocolateyGui.Common.ViewModels.Items.
- The types involved
ChocolateyGui.Common.Windows.ViewModels.Items.PackageViewModel→ChocolateyGui.Common.ViewModels.Items.IPackageViewModel
- Direction
- ChocolateyGui.Common.Windows.ViewModels.Items uses ChocolateyGui.Common.ViewModels.Items, so a change to ChocolateyGui.Common.ViewModels.Items can break ChocolateyGui.Common.Windows.ViewModels.Items, while a change to ChocolateyGui.Common.Windows.ViewModels.Items can't break ChocolateyGui.Common.ViewModels.Items.
- Position
- Below the diagonal: ChocolateyGui.Common.Windows.ViewModels.Items uses a module listed above it, which is the healthy direction.
31→19 ChocolateyGui.Common.Windows.ViewModels.Items uses ChocolateyGui.Common.Models✕
- Connections
- 2 pairs of types, where a type in ChocolateyGui.Common.Windows.ViewModels.Items uses a type in ChocolateyGui.Common.Models.
- The types involved
ChocolateyGui.Common.Windows.ViewModels.Items.PackageViewModel→ChocolateyGui.Common.Models.AdvancedInstallChocolateyGui.Common.Windows.ViewModels.Items.PackageViewModel→ChocolateyGui.Common.Models.ChocolateySource
- Direction
- ChocolateyGui.Common.Windows.ViewModels.Items uses ChocolateyGui.Common.Models, so a change to ChocolateyGui.Common.Models can break ChocolateyGui.Common.Windows.ViewModels.Items, while a change to ChocolateyGui.Common.Windows.ViewModels.Items can't break ChocolateyGui.Common.Models.
- Position
- Below the diagonal: ChocolateyGui.Common.Windows.ViewModels.Items uses a module listed above it, which is the healthy direction.
31→21 ChocolateyGui.Common.Windows.ViewModels.Items uses ChocolateyGui.Common.Models.Messages✕
- Connections
- 7 pairs of types, where a type in ChocolateyGui.Common.Windows.ViewModels.Items uses a type in ChocolateyGui.Common.Models.Messages.
- The types involved
ChocolateyGui.Common.Windows.ViewModels.Items.PackageViewModel→ChocolateyGui.Common.Models.Messages.FeatureModifiedMessageChocolateyGui.Common.Windows.ViewModels.Items.PackageViewModel→ChocolateyGui.Common.Models.Messages.PackageInstalledMessageChocolateyGui.Common.Windows.ViewModels.Items.PackageViewModel→ChocolateyGui.Common.Models.Messages.PackageOutdatedMessageChocolateyGui.Common.Windows.ViewModels.Items.PackageViewModel→ChocolateyGui.Common.Models.Messages.PackagePinnedMessageChocolateyGui.Common.Windows.ViewModels.Items.PackageViewModel→ChocolateyGui.Common.Models.Messages.PackageUninstalledMessageChocolateyGui.Common.Windows.ViewModels.Items.PackageViewModel→ChocolateyGui.Common.Models.Messages.PackageUnpinnedMessageChocolateyGui.Common.Windows.ViewModels.Items.PackageViewModel→ChocolateyGui.Common.Models.Messages.PackageUpgradedMessage
- Direction
- ChocolateyGui.Common.Windows.ViewModels.Items uses ChocolateyGui.Common.Models.Messages, so a change to ChocolateyGui.Common.Models.Messages can break ChocolateyGui.Common.Windows.ViewModels.Items, while a change to ChocolateyGui.Common.Windows.ViewModels.Items can't break ChocolateyGui.Common.Models.Messages.
- Position
- Below the diagonal: ChocolateyGui.Common.Windows.ViewModels.Items uses a module listed above it, which is the healthy direction.
31→22 ChocolateyGui.Common.Windows.ViewModels.Items uses ChocolateyGui.Common.Services✕
- Connections
- 5 pairs of types, where a type in ChocolateyGui.Common.Windows.ViewModels.Items uses a type in ChocolateyGui.Common.Services.
- The types involved
ChocolateyGui.Common.Windows.ViewModels.Items.PackageViewModel→ChocolateyGui.Common.Services.IAllowedCommandsServiceChocolateyGui.Common.Windows.ViewModels.Items.PackageViewModel→ChocolateyGui.Common.Services.IChocolateyGuiCacheServiceChocolateyGui.Common.Windows.ViewModels.Items.PackageViewModel→ChocolateyGui.Common.Services.IChocolateyServiceChocolateyGui.Common.Windows.ViewModels.Items.PackageViewModel→ChocolateyGui.Common.Services.IConfigServiceChocolateyGui.Common.Windows.ViewModels.Items.PackageViewModel→ChocolateyGui.Common.Services.IPersistenceService
- Direction
- ChocolateyGui.Common.Windows.ViewModels.Items uses ChocolateyGui.Common.Services, so a change to ChocolateyGui.Common.Services can break ChocolateyGui.Common.Windows.ViewModels.Items, while a change to ChocolateyGui.Common.Windows.ViewModels.Items can't break ChocolateyGui.Common.Services.
- Position
- Below the diagonal: ChocolateyGui.Common.Windows.ViewModels.Items uses a module listed above it, which is the healthy direction.
31→28 ChocolateyGui.Common.Windows.ViewModels.Items uses ChocolateyGui.Common.Windows.Services✕
- Connections
- 3 pairs of types, where a type in ChocolateyGui.Common.Windows.ViewModels.Items uses a type in ChocolateyGui.Common.Windows.Services.
- The types involved
ChocolateyGui.Common.Windows.ViewModels.Items.PackageViewModel→ChocolateyGui.Common.Windows.Services.IDialogServiceChocolateyGui.Common.Windows.ViewModels.Items.PackageViewModel→ChocolateyGui.Common.Windows.Services.IPackageArgumentsServiceChocolateyGui.Common.Windows.ViewModels.Items.PackageViewModel→ChocolateyGui.Common.Windows.Services.IProgressService
- Direction
- ChocolateyGui.Common.Windows.ViewModels.Items uses ChocolateyGui.Common.Windows.Services, so a change to ChocolateyGui.Common.Windows.Services can break ChocolateyGui.Common.Windows.ViewModels.Items, while a change to ChocolateyGui.Common.Windows.ViewModels.Items can't break ChocolateyGui.Common.Windows.Services.
- Position
- Below the diagonal: ChocolateyGui.Common.Windows.ViewModels.Items uses a module listed above it, which is the healthy direction.
32→4 ChocolateyGui.Common.Windows.ViewModels uses ChocolateyGui.Common.Enums✕
- Connections
- 2 pairs of types, where a type in ChocolateyGui.Common.Windows.ViewModels uses a type in ChocolateyGui.Common.Enums.
- The types involved
ChocolateyGui.Common.Windows.ViewModels.LocalSourceViewModel→ChocolateyGui.Common.Enums.ListViewModeChocolateyGui.Common.Windows.ViewModels.RemoteSourceViewModel→ChocolateyGui.Common.Enums.ListViewMode
- Direction
- ChocolateyGui.Common.Windows.ViewModels uses ChocolateyGui.Common.Enums, so a change to ChocolateyGui.Common.Enums can break ChocolateyGui.Common.Windows.ViewModels, while a change to ChocolateyGui.Common.Windows.ViewModels can't break ChocolateyGui.Common.Enums.
- Position
- Below the diagonal: ChocolateyGui.Common.Windows.ViewModels uses a module listed above it, which is the healthy direction.
32→5 ChocolateyGui.Common.Windows.ViewModels uses ChocolateyGui.Common.Providers✕
- Connections
- 1 pair of types, where a type in ChocolateyGui.Common.Windows.ViewModels uses a type in ChocolateyGui.Common.Providers.
- The types involved
ChocolateyGui.Common.Windows.ViewModels.ShellViewModel→ChocolateyGui.Common.Providers.IVersionNumberProvider
- Direction
- ChocolateyGui.Common.Windows.ViewModels uses ChocolateyGui.Common.Providers, so a change to ChocolateyGui.Common.Providers can break ChocolateyGui.Common.Windows.ViewModels, while a change to ChocolateyGui.Common.Windows.ViewModels can't break ChocolateyGui.Common.Providers.
- Position
- Below the diagonal: ChocolateyGui.Common.Windows.ViewModels uses a module listed above it, which is the healthy direction.
32→7 ChocolateyGui.Common.Windows.ViewModels uses ChocolateyGui.Common.Utilities✕
- Connections
- 4 pairs of types, where a type in ChocolateyGui.Common.Windows.ViewModels uses a type in ChocolateyGui.Common.Utilities.
- The types involved
ChocolateyGui.Common.Windows.ViewModels.LocalSourceViewModel→ChocolateyGui.Common.Utilities.TranslationSourceChocolateyGui.Common.Windows.ViewModels.RemoteSourceViewModel→ChocolateyGui.Common.Utilities.TranslationSourceChocolateyGui.Common.Windows.ViewModels.SettingsViewModel→ChocolateyGui.Common.Utilities.TranslationSourceChocolateyGui.Common.Windows.ViewModels.ViewModelScreen→ChocolateyGui.Common.Utilities.TranslationSource
- Direction
- ChocolateyGui.Common.Windows.ViewModels uses ChocolateyGui.Common.Utilities, so a change to ChocolateyGui.Common.Utilities can break ChocolateyGui.Common.Windows.ViewModels, while a change to ChocolateyGui.Common.Windows.ViewModels can't break ChocolateyGui.Common.Utilities.
- Position
- Below the diagonal: ChocolateyGui.Common.Windows.ViewModels uses a module listed above it, which is the healthy direction.
32→8 ChocolateyGui.Common.Windows.ViewModels uses ChocolateyGui.Common.ViewModels✕
- Connections
- 3 pairs of types, where a type in ChocolateyGui.Common.Windows.ViewModels uses a type in ChocolateyGui.Common.ViewModels.
- The types involved
ChocolateyGui.Common.Windows.ViewModels.LocalSourceViewModel→ChocolateyGui.Common.ViewModels.ISourceViewModelBaseChocolateyGui.Common.Windows.ViewModels.RemoteSourceViewModel→ChocolateyGui.Common.ViewModels.ISourceViewModelBaseChocolateyGui.Common.Windows.ViewModels.SourceSeparatorViewModel→ChocolateyGui.Common.ViewModels.ISourceViewModelBase
- Direction
- ChocolateyGui.Common.Windows.ViewModels uses ChocolateyGui.Common.ViewModels, so a change to ChocolateyGui.Common.ViewModels can break ChocolateyGui.Common.Windows.ViewModels, while a change to ChocolateyGui.Common.Windows.ViewModels can't break ChocolateyGui.Common.ViewModels.
- Position
- Below the diagonal: ChocolateyGui.Common.Windows.ViewModels uses a module listed above it, which is the healthy direction.
32→16 ChocolateyGui.Common.Windows.ViewModels uses ChocolateyGui.Common.Base✕
- Connections
- 1 pair of types, where a type in ChocolateyGui.Common.Windows.ViewModels uses a type in ChocolateyGui.Common.Base.
- The types involved
ChocolateyGui.Common.Windows.ViewModels.AdvancedInstallViewModel→ChocolateyGui.Common.Base.ObservableBase
- Direction
- ChocolateyGui.Common.Windows.ViewModels uses ChocolateyGui.Common.Base, so a change to ChocolateyGui.Common.Base can break ChocolateyGui.Common.Windows.ViewModels, while a change to ChocolateyGui.Common.Windows.ViewModels can't break ChocolateyGui.Common.Base.
- Position
- Below the diagonal: ChocolateyGui.Common.Windows.ViewModels uses a module listed above it, which is the healthy direction.
32→17 ChocolateyGui.Common.Windows.ViewModels uses ChocolateyGui.Common.ViewModels.Items✕
- Connections
- 3 pairs of types, where a type in ChocolateyGui.Common.Windows.ViewModels uses a type in ChocolateyGui.Common.ViewModels.Items.
- The types involved
ChocolateyGui.Common.Windows.ViewModels.LocalSourceViewModel→ChocolateyGui.Common.ViewModels.Items.IPackageViewModelChocolateyGui.Common.Windows.ViewModels.PackageViewModel→ChocolateyGui.Common.ViewModels.Items.IPackageViewModelChocolateyGui.Common.Windows.ViewModels.RemoteSourceViewModel→ChocolateyGui.Common.ViewModels.Items.IPackageViewModel
- Direction
- ChocolateyGui.Common.Windows.ViewModels uses ChocolateyGui.Common.ViewModels.Items, so a change to ChocolateyGui.Common.ViewModels.Items can break ChocolateyGui.Common.Windows.ViewModels, while a change to ChocolateyGui.Common.Windows.ViewModels can't break ChocolateyGui.Common.ViewModels.Items.
- Position
- Below the diagonal: ChocolateyGui.Common.Windows.ViewModels uses a module listed above it, which is the healthy direction.
32→19 ChocolateyGui.Common.Windows.ViewModels uses ChocolateyGui.Common.Models✕
- Connections
- 8 pairs of types, where a type in ChocolateyGui.Common.Windows.ViewModels uses a type in ChocolateyGui.Common.Models.
- The types involved
ChocolateyGui.Common.Windows.ViewModels.CreateRemove→ChocolateyGui.Common.Models.ChocolateySourceChocolateyGui.Common.Windows.ViewModels.RemoteSourceViewModel→ChocolateyGui.Common.Models.ChocolateySourceChocolateyGui.Common.Windows.ViewModels.SettingsViewModel→ChocolateyGui.Common.Models.AppConfigurationChocolateyGui.Common.Windows.ViewModels.SettingsViewModel→ChocolateyGui.Common.Models.ChocolateyFeatureChocolateyGui.Common.Windows.ViewModels.SettingsViewModel→ChocolateyGui.Common.Models.ChocolateyGuiFeatureChocolateyGui.Common.Windows.ViewModels.SettingsViewModel→ChocolateyGui.Common.Models.ChocolateyGuiSettingChocolateyGui.Common.Windows.ViewModels.SettingsViewModel→ChocolateyGui.Common.Models.ChocolateySettingChocolateyGui.Common.Windows.ViewModels.SettingsViewModel→ChocolateyGui.Common.Models.ChocolateySource
- Direction
- ChocolateyGui.Common.Windows.ViewModels uses ChocolateyGui.Common.Models, so a change to ChocolateyGui.Common.Models can break ChocolateyGui.Common.Windows.ViewModels, while a change to ChocolateyGui.Common.Windows.ViewModels can't break ChocolateyGui.Common.Models.
- Position
- Below the diagonal: ChocolateyGui.Common.Windows.ViewModels uses a module listed above it, which is the healthy direction.
32→20 ChocolateyGui.Common.Windows.ViewModels uses ChocolateyGui.Common.Windows.Utilities✕
- Connections
- 1 pair of types, where a type in ChocolateyGui.Common.Windows.ViewModels uses a type in ChocolateyGui.Common.Windows.Utilities.
- The types involved
ChocolateyGui.Common.Windows.ViewModels.AdvancedInstallViewModel→ChocolateyGui.Common.Windows.Utilities.NotifyTaskCompletion
- Direction
- ChocolateyGui.Common.Windows.ViewModels uses ChocolateyGui.Common.Windows.Utilities, so a change to ChocolateyGui.Common.Windows.Utilities can break ChocolateyGui.Common.Windows.ViewModels, while a change to ChocolateyGui.Common.Windows.ViewModels can't break ChocolateyGui.Common.Windows.Utilities.
- Position
- Below the diagonal: ChocolateyGui.Common.Windows.ViewModels uses a module listed above it, which is the healthy direction.
32→21 ChocolateyGui.Common.Windows.ViewModels uses ChocolateyGui.Common.Models.Messages✕
- Connections
- 10 pairs of types, where a type in ChocolateyGui.Common.Windows.ViewModels uses a type in ChocolateyGui.Common.Models.Messages.
- The types involved
ChocolateyGui.Common.Windows.ViewModels.LocalSourceViewModel→ChocolateyGui.Common.Models.Messages.PackageInstalledMessageChocolateyGui.Common.Windows.ViewModels.LocalSourceViewModel→ChocolateyGui.Common.Models.Messages.PackageUninstalledMessageChocolateyGui.Common.Windows.ViewModels.ShellViewModel→ChocolateyGui.Common.Models.Messages.AboutGoBackMessageChocolateyGui.Common.Windows.ViewModels.ShellViewModel→ChocolateyGui.Common.Models.Messages.FeatureModifiedMessageChocolateyGui.Common.Windows.ViewModels.ShellViewModel→ChocolateyGui.Common.Models.Messages.SettingsGoBackMessageChocolateyGui.Common.Windows.ViewModels.ShellViewModel→ChocolateyGui.Common.Models.Messages.ShowAboutMessageChocolateyGui.Common.Windows.ViewModels.ShellViewModel→ChocolateyGui.Common.Models.Messages.ShowPackageDetailsMessageChocolateyGui.Common.Windows.ViewModels.ShellViewModel→ChocolateyGui.Common.Models.Messages.ShowSettingsMessageChocolateyGui.Common.Windows.ViewModels.ShellViewModel→ChocolateyGui.Common.Models.Messages.ShowSourcesMessageChocolateyGui.Common.Windows.ViewModels.SourcesViewModel→ChocolateyGui.Common.Models.Messages.SourcesUpdatedMessage
- Direction
- ChocolateyGui.Common.Windows.ViewModels uses ChocolateyGui.Common.Models.Messages, so a change to ChocolateyGui.Common.Models.Messages can break ChocolateyGui.Common.Windows.ViewModels, while a change to ChocolateyGui.Common.Windows.ViewModels can't break ChocolateyGui.Common.Models.Messages.
- Position
- Below the diagonal: ChocolateyGui.Common.Windows.ViewModels uses a module listed above it, which is the healthy direction.
32→22 ChocolateyGui.Common.Windows.ViewModels uses ChocolateyGui.Common.Services✕
- Connections
- 19 pairs of types, where a type in ChocolateyGui.Common.Windows.ViewModels uses a type in ChocolateyGui.Common.Services.
- The types involved
ChocolateyGui.Common.Windows.ViewModels.AboutViewModel→ChocolateyGui.Common.Services.IVersionServiceChocolateyGui.Common.Windows.ViewModels.AdvancedInstallViewModel→ChocolateyGui.Common.Services.IChocolateyServiceChocolateyGui.Common.Windows.ViewModels.AdvancedInstallViewModel→ChocolateyGui.Common.Services.IPersistenceServiceChocolateyGui.Common.Windows.ViewModels.LocalSourceViewModel→ChocolateyGui.Common.Services.IAllowedCommandsServiceChocolateyGui.Common.Windows.ViewModels.LocalSourceViewModel→ChocolateyGui.Common.Services.IChocolateyGuiCacheServiceChocolateyGui.Common.Windows.ViewModels.LocalSourceViewModel→ChocolateyGui.Common.Services.IChocolateyServiceChocolateyGui.Common.Windows.ViewModels.LocalSourceViewModel→ChocolateyGui.Common.Services.IConfigServiceChocolateyGui.Common.Windows.ViewModels.LocalSourceViewModel→ChocolateyGui.Common.Services.IPersistenceServiceChocolateyGui.Common.Windows.ViewModels.RemoteSourceViewModel→ChocolateyGui.Common.Services.IChocolateyGuiCacheServiceChocolateyGui.Common.Windows.ViewModels.RemoteSourceViewModel→ChocolateyGui.Common.Services.IChocolateyServiceChocolateyGui.Common.Windows.ViewModels.RemoteSourceViewModel→ChocolateyGui.Common.Services.IConfigServiceChocolateyGui.Common.Windows.ViewModels.SettingsViewModel→ChocolateyGui.Common.Services.IChocolateyGuiCacheServiceChocolateyGui.Common.Windows.ViewModels.SettingsViewModel→ChocolateyGui.Common.Services.IChocolateyServiceChocolateyGui.Common.Windows.ViewModels.SettingsViewModel→ChocolateyGui.Common.Services.IConfigServiceChocolateyGui.Common.Windows.ViewModels.ShellViewModel→ChocolateyGui.Common.Services.IChocolateyServiceChocolateyGui.Common.Windows.ViewModels.ShellViewModel→ChocolateyGui.Common.Services.IConfigServiceChocolateyGui.Common.Windows.ViewModels.SourcesViewModel→ChocolateyGui.Common.Services.IChocolateyServiceChocolateyGui.Common.Windows.ViewModels.SourcesViewModel→ChocolateyGui.Common.Services.IConfigServiceChocolateyGui.Common.Windows.ViewModels.SourcesViewModel→ChocolateyGui.Common.Services.IVersionService
- Direction
- ChocolateyGui.Common.Windows.ViewModels uses ChocolateyGui.Common.Services, so a change to ChocolateyGui.Common.Services can break ChocolateyGui.Common.Windows.ViewModels, while a change to ChocolateyGui.Common.Windows.ViewModels can't break ChocolateyGui.Common.Services.
- Position
- Below the diagonal: ChocolateyGui.Common.Windows.ViewModels uses a module listed above it, which is the healthy direction.
32→25 ChocolateyGui.Common.Windows.ViewModels uses ChocolateyGui.Common.Windows.Controls.Dialogs✕
- Connections
- 1 pair of types, where a type in ChocolateyGui.Common.Windows.ViewModels uses a type in ChocolateyGui.Common.Windows.Controls.Dialogs.
- The types involved
ChocolateyGui.Common.Windows.ViewModels.AdvancedInstallViewModel→ChocolateyGui.Common.Windows.Controls.Dialogs.IClosableChildWindow
- Direction
- ChocolateyGui.Common.Windows.ViewModels uses ChocolateyGui.Common.Windows.Controls.Dialogs, so a change to ChocolateyGui.Common.Windows.Controls.Dialogs can break ChocolateyGui.Common.Windows.ViewModels, while a change to ChocolateyGui.Common.Windows.ViewModels can't break ChocolateyGui.Common.Windows.Controls.Dialogs.
- Position
- Below the diagonal: ChocolateyGui.Common.Windows.ViewModels uses a module listed above it, which is the healthy direction.
32→28 ChocolateyGui.Common.Windows.ViewModels uses ChocolateyGui.Common.Windows.Services✕
- Connections
- 7 pairs of types, where a type in ChocolateyGui.Common.Windows.ViewModels uses a type in ChocolateyGui.Common.Windows.Services.
- The types involved
ChocolateyGui.Common.Windows.ViewModels.LocalSourceViewModel→ChocolateyGui.Common.Windows.Services.IDialogServiceChocolateyGui.Common.Windows.ViewModels.LocalSourceViewModel→ChocolateyGui.Common.Windows.Services.IProgressServiceChocolateyGui.Common.Windows.ViewModels.RemoteSourceViewModel→ChocolateyGui.Common.Windows.Services.IDialogServiceChocolateyGui.Common.Windows.ViewModels.RemoteSourceViewModel→ChocolateyGui.Common.Windows.Services.IProgressServiceChocolateyGui.Common.Windows.ViewModels.SettingsViewModel→ChocolateyGui.Common.Windows.Services.IDialogServiceChocolateyGui.Common.Windows.ViewModels.SettingsViewModel→ChocolateyGui.Common.Windows.Services.IProgressServiceChocolateyGui.Common.Windows.ViewModels.SourcesViewModel→ChocolateyGui.Common.Windows.Services.IImageService
- Direction
- ChocolateyGui.Common.Windows.ViewModels uses ChocolateyGui.Common.Windows.Services, so a change to ChocolateyGui.Common.Windows.Services can break ChocolateyGui.Common.Windows.ViewModels, while a change to ChocolateyGui.Common.Windows.ViewModels can't break ChocolateyGui.Common.Windows.Services.
- Position
- Below the diagonal: ChocolateyGui.Common.Windows.ViewModels uses a module listed above it, which is the healthy direction.
32→31 ChocolateyGui.Common.Windows.ViewModels uses ChocolateyGui.Common.Windows.ViewModels.Items✕
- Connections
- 1 pair of types, where a type in ChocolateyGui.Common.Windows.ViewModels uses a type in ChocolateyGui.Common.Windows.ViewModels.Items.
- The types involved
ChocolateyGui.Common.Windows.ViewModels.ShellViewModel→ChocolateyGui.Common.Windows.ViewModels.Items.SourceViewModel
- Direction
- ChocolateyGui.Common.Windows.ViewModels uses ChocolateyGui.Common.Windows.ViewModels.Items, so a change to ChocolateyGui.Common.Windows.ViewModels.Items can break ChocolateyGui.Common.Windows.ViewModels, while a change to ChocolateyGui.Common.Windows.ViewModels can't break ChocolateyGui.Common.Windows.ViewModels.Items.
- Position
- Below the diagonal: ChocolateyGui.Common.Windows.ViewModels uses a module listed above it, which is the healthy direction.
At a glance — Code Health
At a glance — Architecture
At a glance — Maturity
At a glance — Readiness
At a glance — Security
At a glance — Performance
Security & Compliance — OWASP Top-10 mapping
| OWASP category | Findings | Severity |
|---|---|---|
| A05:2025 — Injection | 21 | High / Critical |
| A03:2025 — Software Supply Chain Failures | 8 | Medium |
| A07:2025 — Authentication Failures | 2 | High / Critical |
Roadmap
Top priorities: Resolve the 1 Leaked secret finding(s) in Secret Scanning — start with REDACTED; Resolve the 1 No ADRs found finding(s) in ADR Quality — start with ChocolateyGui.csproj; Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them.
| Do this | Helps | Effort | Dimension |
|---|---|---|---|
| Resolve the 1 Leaked secret finding(s) in Secret Scanning — start with REDACTED. | +5.9 pts | Low | Secret Scanning |
| Resolve the 1 No ADRs found finding(s) in ADR Quality — start with ChocolateyGui.csproj. | +4.2 pts | Low | ADR Quality |
| Resolve the 2 No assertions finding(s) in Test Quality — start with ChocolateyGuiTests.cs (2). | +3.2 pts | Low | Test Quality |
| Resolve the 5 redundant comment finding(s) in Comment Value — start with AssemblyInfo.cs (3), ChocolateyGuiModule.cs, DataGridCustomSortBehavior.cs. | +2.6 pts | Low | Comment Value |
| Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them. | +4.2 pts | Medium | Architecture documentation |
| Automate the release in CI — a deploy stage for a service (Helm/Kubernetes manifests or an equivalent rollout), or a tag-triggered publish job for an artifact — so releases are repeatable and reversible. | +4.1 pts | Medium | Deployment & Rollback |
| Add `AddStandardResilienceHandler()` (or a Polly policy and an explicit timeout) to each client registration flagged here, so a flaky dependency can't take the app down. | +3.4 pts | Medium | Outbound HTTP resilience |
| Resolve the 1 EmptyCatchBlock finding(s) in Explicit Debt — start with Internationalization.cs. | +1.5 pts | Low | Explicit Debt |
File quality
| File | Score | Band | Worst signal |
|---|---|---|---|
| REDACTED | 1.6 | Slop | Static Analysis (SAST): High: REDACTED |
| Source/ChocolateyGui.Common.Windows/ViewModels/RemoteSourceViewModel.cs | 1.9 | Slop | Explicit Debt: WriteOnlyPrivateField |
| REDACTED | 2.0 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 3.0 | Slop | Static Analysis (SAST): High: REDACTED |
| Source/ChocolateyGui.Common.Windows/ViewModels/Items/PackageViewModel.cs | 3.6 | Slop | Explicit Debt: WriteOnlyPrivateField |
| REDACTED | 3.7 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 4.4 | Mixed | Secret Scanning: Leaked secret: REDACTED |
| Source/ChocolateyGui.Common.Windows/ViewModels/SettingsViewModel.cs | 5.0 | Mixed | Explicit Debt: WriteOnlyPrivateField |
| REDACTED | 5.8 | Mixed | Static Analysis (SAST): High: REDACTED |
| REDACTED | 5.8 | Mixed | Static Analysis (SAST): High: REDACTED |
| Source/ChocolateyGui/App.xaml.cs | 6.0 | Mixed | Explicit Debt: TodoComment |
| Source/ChocolateyGui.Common.Windows/Bootstrapper.cs | 6.0 | Mixed | Explicit Debt: BarePragmaDisable |
| Source/ChocolateyGui.Common.Windows/Views/ShellView.xaml.cs | 6.0 | Mixed | Explicit Debt: BarePragmaDisable |
| Source/ChocolateyGui.Common.Windows/Services/PackageArgumentsService.cs | 6.1 | Mixed | Explicit Debt: WriteOnlyPrivateField |
| Source/ChocolateyGuiCli/Bootstrapper.cs | 6.7 | Mixed | Explicit Debt: BarePragmaDisable |
| Source/ChocolateyGui.Common.Windows/Startup/ChocolateyGuiModule.cs | 6.9 | Mixed | Code Duplication: Duplicated block (40 lines × 2) |
| Source/ChocolateyGui.Common.Windows/Services/ChocolateyService.cs | 7.1 | Mixed | Cognitive Complexity: ChocolateyService.GetOutdatedPackages (cognitive 19) |
| REDACTED | 7.2 | Mixed | Static Analysis (SAST): High: REDACTED |
| REDACTED | 7.2 | Mixed | Static Analysis (SAST): High: REDACTED |
| Source/ChocolateyGui.Common.Windows/Commands/CommandExecutionManager.cs | 7.3 | Mixed | Explicit Debt: CommentedOutCode |
How the grades work
A definite problem that already costs you something and drags the score down: a missing authorisation check, a dependency with a known exploit, a build that does not reproduce. Failure here tends to cause failures elsewhere.
Likely wrong, but not failing yet. It degrades the codebase over a longer horizon and can cause failures elsewhere — not urgent this week, not something to carry for two years either.
Recorded, with no effect on how the codebase functions. Present so the survey is complete, not because it needs doing.
Something this survey could not settle from the outside, and which could be critical or serious. Either a control was required and no positive evidence of it exists in the repository — a backup job that nothing shows was ever restored from proves nothing about restores — or our own analysis could not run over that part of the tree. This is not a clean result. These are excluded from the score rather than awarded a pass, so the number on the cover neither rewards nor penalises them: if you act on this survey without resolving them, you carry that risk yourself. Each one is named under Limitations.
Methodology & how to trust this report
This survey is a deep, periodic assessment — run each sprint, monthly, or quarterly, taking the time to go wider and deeper than a quick check and surfacing in one coherent report what you'd otherwise piece together from a dozen separate tools. It scores deterministically: the same commit yields the same score, every run. All 59 evaluated dimensions are computed by tools and static analysis; no language model sets or judges any of them. Overall confidence is 0.9, the weighted average across measured dimensions.
What we checked — 59 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, 212 of 229 do; the remainder are repo-wide signals — a dimension-level measurement, not a single line.
- Is there a tool behind the number? Every score below names the method that produced it: Roslyn, git or a scanner, not a narrative.
- Does re-running give the same result? Run it again on the same commit and the score — and this report, byte for byte — is identical. A report whose numbers move between runs is describing the run, not the code.
Tools & methods
| Method | Backs | Version | Evaluator |
|---|---|---|---|
| Roslyn static analysis | Complexity, cohesion, coupling, dead code, API surface, layering | 5.3.0 | ✓ deterministic |
| Native secret scanner | Hardcoded secrets / credentials | 1.0.0 | ✓ deterministic |
| Canine Code Analyzer duplication detector (in-process) | Code duplication | 1.0.0 | ✓ deterministic |
| Coverage (coverlet / dotnet-coverage) | Line & branch coverage | 10.0.400 | ✓ deterministic |
| NuGet / dotnet | Outdated, vulnerable & deprecated dependencies | 10.0.400 | ✓ deterministic |
| git / LibGit2Sharp | Churn hotspots, knowledge concentration, history | 2.43.0 · 0.31.0 | ✓ deterministic |
| gitleaks · semgrep · trivy | Secrets in history, SAST, CVEs, IaC & container, PII / GDPR | 1.86.0 · 0.69.3 | ✓ deterministic |
Run transparency — what happened this run
- D4 Code Duplication — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. The 9 duplicated block group(s) on this row were found in the languages this pass could tokenize, and they do NOT cover all of this repository's production source: .h (7,308 lines, 35% of production source) went unread, because no language model this pass could load exposed a clone-unit token stream for those file kinds. Duplication in that source is UNMEASURED — its absence from the count above is a gap in this analyzer's language coverage, not a finding that the code is free of duplication.
- D10 Test Quality — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. The 34 test(s) behind this row are the ones the C# collector could read, and this repository also carries test source in .ps1 that it cannot: it parses C# syntax and matches C# test attributes, so a vitest/jest/JUnit/pytest-style suite is invisible to it. Skipped tests, zero-assertion tests and the other quality signals on this row are UNMEASURED in that suite — their absence from the counts above is a gap in this analyzer's language coverage, not a finding that those tests are sound.
- D11 Test Reliability — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Test reliability not scored — the test tier(s) ran but surfaced none of this repository's 34 test method(s) to the runner, so flakiness couldn't be exercised. This is an analysis-environment limitation, not a finding about the tests.
- D12 Dependency Hygiene — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. `dotnet list package` did not return usable output (restore or query failed); no outdated/vulnerable/deprecated data to assess. The tool said: `dotnet list package` exited 1 with no output.
- D17 Explicit Debt — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. The C# workspace loaded this repository's projects but reported a load failure, and the dead-code reference search is unreliable over a graph that did not load cleanly, so it was skipped. The other debt markers on this row were read; dead symbols were not, and their absence from the score is not a finding that the code has none. First load diagnostic: Failure: Msbuild failed when processing the file 'Source/ChocolateyGui/ChocolateyGui.csproj' with message: Unknown build error, 'Could not find a part of the path 'Source/ChocolateyGui.Common.Windows/bin/Debug/net48/ChocolateyGui.Common.Windows.dll'. Line 18 Position 22.'.
- D17 Explicit Debt — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. The 29 deducted marker(s) and the 0.9/KLoC density on this row were taken over this repository's .NET projects ALONE: .h (7,308 lines, 35% of production source) went unread, because every marker collector on this path is reached through a C# workspace. D17's marker collectors need a compiler we do not have for that language, so none of its nine marker kinds were read there. The debt in that source is UNMEASURED — its absence from the score above is a gap in this analyzer's language coverage, not a finding that the code carries none.
- D19 Documentation Quality — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. Each ecosystem's manifests (what makes a folder runnable or a published package) need their own proof before D19 judges its units. Until then those folders' READMEs are judged only as documents (boilerplate, structure), never counted as complete.
- D19 Documentation Quality — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. This kind did not reach the 95 % precision gate in three adjudicated runs (docs/plans/deterministic-engine/adjudication/D19-sample3-v3.md), so by the pre-registered fallback it publishes no row until a re-measurement shows it does. The candidates are counted here, not reported as findings, and the score does not include them.
- D22 Internal API Consistency — 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. The loaded project set declares no packable project and no `.Contracts` project, so there is no intentionally-exposed surface for API consistency to be judged over.
- D27 Navigability — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. Tracing effort is measured over resolved call sites, and all 1382 sampled here came from .cs files. This repository's .h source is a material share of its production lines and contributed none, so the score above is a verdict about the part that was read. Not a finding that the unread half navigates well — it is unmeasured.
- D28 Secrets (history) — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. D28's config-credential rule (WD-SECRET-0002) parses each committed `.json` config as a document and reads credential-named values; `Source/stylecop.json` did not parse (JSON5, a template, several concatenated documents), so a credential bound there is UNMEASURED by that rule. gitleaks still scanned the same files as text.
- D30 Dependency Vulnerabilities — measured, with a gap in what it reached — 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. The solution did not restore on the analyzer's .NET SDK (an SDK/target-framework/restore mismatch, common for an older codebase), so there was no restored dependency graph to scan. 1 of 2 declared ecosystem(s) (osv) WERE scanned and every vulnerability they reported is included in this result; nuget was not, so this dimension's score covers less than the dependency surface this repository declares, and nothing here is evidence that nuget is free of known-vulnerable dependencies.
- D32 Data Compliance (PII/GDPR) — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. `Source/ChocolateyGui/GlobalSuppressions.cs` produced a parse error, so every rule in this engine's `gdpr.yml` was absent there. That absence is NOT a clean result: these rules detect personal data crossing a boundary into a log sink, a URL or browser storage, and a file that was never parsed cannot report any of the three. The rest of the tree analysed normally and its rows above stand; only these files are unaccounted for. You can widen what we reach: fix the syntax error (or exclude the file deliberately) and re-scan to cover it.
- AX6 Interface segregation — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. This check's reader does not cover every language in this repository. The score describes the part it read, which is most of the product; the rest is a gap in this analyzer's language reach.
- AXB1 Runtime evidence locked — no reproducible boot — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Subject: a native UI project (Source/ChocolateyGui.Common.Windows/Views/AboutView.xaml). The Runtime Evidence tier boots an app only via docker-compose, an Aspire AppHost, a Dockerfile, an npm dev script, a web service's own toolchain entry point (cargo, go, dotnet, Python, Spring Boot), or an Android app's own Gradle wrapper (run on an emulator); an Apple or Flutter app needs a host it lacks. None applied, so no live runtime a11y/egress/header evidence was collected. You can widen what we reach: add a docker-compose.yml (or an Aspire AppHost) that brings the app up with its dependencies. We then boot it in an isolated sandbox and gathers real runtime evidence — you change nothing in your pipeline (no CI step, no SDK).
- IC1 Incompleteness & stubs — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. This check's reader does not cover every language in this repository. The score describes the part it read, which is most of the product; the rest is a gap in this analyzer's language reach.
- X1 Async correctness — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. This check's reader does not cover every language in this repository. The score describes the part it read, which is most of the product; the rest is a gap in this analyzer's language reach.
- X12 Unreachable branch — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. This check's reader does not cover every language in this repository. The score describes the part it read, which is most of the product; the rest is a gap in this analyzer's language reach.
- X13 Undrained process stream — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. This check's reader does not cover every language in this repository. The score describes the part it read, which is most of the product; the rest is a gap in this analyzer's language reach.
- X16 Unfloored truncation loop — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. This check's reader does not cover every language in this repository. The score describes the part it read, which is most of the product; the rest is a gap in this analyzer's language reach.
- X18 Disposal-pattern correctness — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. This check's reader does not cover every language in this repository. The score describes the part it read, which is most of the product; the rest is a gap in this analyzer's language reach.
- X19 Unrestored process-global state — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. This check's reader does not cover every language in this repository. The score describes the part it read, which is most of the product; the rest is a gap in this analyzer's language reach.
- X2 Cancellation propagation — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. This check's reader does not cover every language in this repository. The score describes the part it read, which is most of the product; the rest is a gap in this analyzer's language reach.
- X2 Cancellation propagation — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. 33 further occurrence(s) are not listed individually; the score already reflects all 73.
- X23 Unguarded diagnostic materialisation — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. This check's reader does not cover every language in this repository. The score describes the part it read, which is most of the product; the rest is a gap in this analyzer's language reach.
- X27 Collection changed while being enumerated — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. This check's reader does not cover every language in this repository. The score describes the part it read, which is most of the product; the rest is a gap in this analyzer's language reach.
- X29 Per-element action decided by a fixed element — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. This check's reader does not cover every language in this repository. The score describes the part it read, which is most of the product; the rest is a gap in this analyzer's language reach.
- X3 Exception handling — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. This check's reader does not cover every language in this repository. The score describes the part it read, which is most of the product; the rest is a gap in this analyzer's language reach.
- X4 Structured logging — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. This check's reader does not cover every language in this repository. The score describes the part it read, which is most of the product; the rest is a gap in this analyzer's language reach.
Limitations & what we did not check
We assess the repository exactly as committed, and only the repository. By design we do not reach outside the source tree: the live cloud account, the running CI/CD pipeline, the host's branch-protection and approval rules, the production configuration, or a restore actually exercised against a backup are all out of scope. That boundary is a feature, not a gap — a repo-relative, deterministic scan re-runs identically on any commit and every finding opens at a real file and line, where a live audit can neither be reproduced nor traced. The visible consequence is that controls which leave no in-repo evidence are reported as "not evidenced" and excluded from the score rather than awarded a number a static scan cannot justify.
Per-dimension blind spots
- D1 Cyclomatic Complexity: Cyclomatic complexity counts branches statically — it cannot tell an essential decision tree from accidental tangle, nor see complexity that lives in data or configuration (large switch-case token tables, DSL lexers/parsers, data-as-code rule tables) rather than control flow: a tokenizer's many single-character cases read as high complexity though each branch is trivial.
- D2 Cognitive Complexity: Cognitive-complexity heuristics approximate how hard code is to follow; genuine domain difficulty and well-named intent that eases reading are not captured.
- D3 God Classes: "God class" is sized by members and responsibilities visible in the type — a deliberately broad facade over a coherent subsystem can read the same as an accidental grab-bag. For front-end JS the file-length check is cohesion-aware (a single-responsibility module — one class/IIFE — earns a 3× threshold), but cohesion is approximated from top-level declarations, not true dependency structure.
- D4 Code Duplication: Duplication is token-similarity — an in-process token-stream comparison over sliding windows, with type-aware normalization — so it finds copy-paste, not semantic duplication expressed differently. Committed machine-written code (scaffolded migrations, designer/codegen output, protobuf/OpenAPI stubs, model snapshots) is EXCLUDED — its repetition is the tool's, not the team's — so the score reflects hand-written duplication only.
- D5 Coupling: Coupling is measured between projects/assemblies — runtime coupling through DI, reflection, messaging or shared databases is invisible to a static reference graph.
- D6 Cohesion (LCOM4): LCOM4 cohesion is syntactic — it infers connectivity from which methods touch which fields/methods by name, not from real runtime behaviour or intent.
- D10 Test Quality: Assertion density is structural — it cannot tell a meaningful behavioural assertion from a trivial one, only that an assertion is present.
- D13 Secret Scanning: Secret detection is signature- and entropy-based on the current tree — a secret that does not match a known pattern, or one already rotated, will not be flagged (a clean scan is "nothing matched", not "no secrets exist").
- D14 License Compliance: License compatibility is checked against declared package metadata and a policy — mislabelled or missing license metadata, and obligations that depend on how you distribute, are not resolved here.
- D15 Churn × Complexity Hotspots: Churn hotspots come from git history — a freshly imported or squashed repository has no churn signal, and recent rewrites can mask a historically risky file.
- D16 Bus Factor: Bus-factor is a time-decayed model of commit attribution (who has recently, repeatedly worked a file), not comprehension — pairing, review and reading-without-committing spread knowledge it can't see; bot commits and shared accounts still distort it.
- D17 Explicit Debt: Acknowledged-debt signals (TODO/FIXME, suppressions, dead code) are textual — undocumented debt that nobody marked, and debt that lives in design rather than annotations, is invisible. Committed machine-written code (scaffolded migrations, designer/codegen output, generated stubs) is excluded — it is never the team's dead code to delete.
- D18 Solution Shape: Build integrity reflects whether the solution compiled in this environment — a build that needs a private feed, a specific SDK, or a generated file absent from the repo can read as broken when it is merely unreproducible here.
- D19 Documentation Quality: Documentation quality publishes two things only: a runnable or packaged unit with no example, and a multi-project root README that maps none of its parts. It does not judge clarity, and its other checks (overview, licence, boilerplate, structure, empty sections, XML-doc coverage) are withheld after adjudication: their candidates are counted in the card's gaps, not shown as rows. A false statement in a document is M4's; units are .NET projects only.
- D20 ADR Quality: ADR quality checks the structure of the decision records present: it cannot know about decisions made and never recorded, and it does not judge how well a record argues its case. Records in a language the section lexicon does not cover are not evaluated.
- D24 Comment Value: Comment value is measured as redundancy only: a comment that repeats its code's words is found, but a paraphrase in other words, a vague comment, or one the code contradicts is not, and whether a comment is valuable is not claimed. Comments in other scripts or languages, and outside C#, are not judged.
- 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.
- D27 Navigability: Indirection/navigability is structural — it measures hops to follow a call, not whether that indirection buys real flexibility or just ceremony.
- 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.
- D44 Platform End-of-Life: The support table is FROZEN, so it goes out of date by losing RECALL: a release that ended support after the table was written is missed until the table is refreshed, and this dimension reading 10 is not evidence that a platform is current. Only platforms the repository DECLARES in a place this pass reads are seen — a runtime named only in a Dockerfile (D31's subject), in a CI workflow (D29's), or in a file this pass does not parse (go.mod, a Gemfile ruby directive) is invisible here, which is why a repository declaring none of them abstains rather than scoring. Only frameworks with a PUBLISHED support policy are tracked: React, Flask and Express publish none, so their age cannot be judged and their absence from a report is not a statement that they are supported.
- AX10 Code composition: Role is inferred from namespace/folder convention, not semantics — a domain concept living in a folder named "Services" reads as application, and the split is lines-of-code, not business value. The business-logic-share score is a SOFT, FLOORED signal: it contributes to the Architecture lens but is floored at the Critical gate, so an infrastructure-heavy design (a gateway, an ETL, a driver) is legitimately low without being nuked to zero.
- P4 Deployment & Rollback: Approval/branch-protection rules live in repository settings the scan cannot see — only their in-repo evidence (config files, workflows) is checked, so a control enforced purely in the host's settings reads as "not evidenced".
- P6 Release Hygiene: Rollback/observability controls are inferred from repo artefacts (pipelines, dashboards-as-code) — controls configured in external tooling, with no in-repo trace, cannot be credited.
Dimensions
D1 · Cyclomatic Complexity
1 method(s) exceeded the cyclomatic complexity threshold of 15; the worst was RemoteSourceViewModel.LoadPackages at 16.
What to do
- Bring the 1 body over 15 down to 15 or less in Cyclomatic Complexity — start with RemoteSourceViewModel.LoadPackages (cyclomatic 16). — Refactoring it lifts Cyclomatic Complexity from 9.9 to about 10.0/10.
D2 · Cognitive Complexity
4 method(s) exceeded the cognitive complexity threshold of 15; the worst was RoutedCommandMonitor.TryExecuteRoutedCommandBinding at 19.
What to do
- Bring the 4 bodies over 15 down to 15 or less in Cognitive Complexity — start with RoutedCommandMonitor.TryExecuteRoutedCommandBinding (cognitive 19), ChocolateyService.GetOutdatedPackages (cognitive 19), RemoteSourceViewModel.LoadPackages (cognitive 19). — 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 4 together lifts Cognitive Complexity from 9.4 to about 10.0/10, projected with the scoring formula itself and assuming each lands exactly at 15.
D3 · God Classes
2 god class(es) detected.
What to do
- Resolve the 1 ClassTooLong finding(s) in God Classes — start with PackageViewModel.cs. — One of this dimension's main actionable groups (1 warning-level).
- Resolve the 1 TooManyMethods finding(s) in God Classes — start with ChocolateyService.cs. — One of this dimension's main actionable groups (1 warning-level).
D4 · Code Duplication
9 duplicated block group(s) detected. 6.6 % of the production lines (895 of 13,535) are in a reported copy. A further 13 rows report members as variants of one another; the share counts each copied line once, however many rows cite it. Measured on part of this repository only: .h (35% of production source) was not exposed to the token comparison, so duplication there is unmeasured and is not in this count.
What to do
- Resolve the 2 Edited copy of a member (18 corresponding lines) finding(s) in Code Duplication — start with ConfigService.cs, DialogService.cs. — One of this dimension's main actionable groups (2 warning-level).
- Resolve the 2 Edited copy of a member (4 corresponding lines) finding(s) in Code Duplication — start with BooleanToVisibility.cs (2). — One of this dimension's main actionable groups (2 warning-level).
- Resolve the 1 Edited copy of a member (51 corresponding lines) finding(s) in Code Duplication — start with App.xaml.cs. — One of this dimension's main actionable groups (1 warning-level).
D5 · Coupling
8 projects, 0 dependency cycle(s), 0 unstable depended-on project(s).
D6 · Cohesion (LCOM4)
1 of 26 classes have LCOM4 above 3.
What to do
- Resolve the 1 Low cohesion finding(s) in Cohesion (LCOM4) — start with ShellView.xaml.cs. — One of this dimension's main actionable groups (1 warning-level).
D10 · Test Quality
0 skipped, 2 zero-assertion, 3 mock references across 34 tests. Measured on the C# suite only — test source in .ps1 went unread, so its test quality is unmeasured and is not in these counts.
What to do
- Resolve the 2 No assertions finding(s) in Test Quality — start with ChocolateyGuiTests.cs (2). — One of this dimension's main actionable groups (2 warning-level).
D13 · Secret Scanning
1 secret(s) detected.
What to do
- Resolve the 1 Leaked secret finding(s) in Secret Scanning — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
D14 · License Compliance
0 of 274 packages use a banned license. ★ DEPTH: this repository's MSBuild projects declare 45 direct `PackageReference`(s), and 205 further package(s) were reached beyond them by closing the graph over nuget.org's own nuspec dependency graph — so a banned licence pulled in only by a dependency's OWN dependencies is inside this verdict. A package whose licence nuget.org could not be asked for is not graded, and version ranges are taken at their lower bound, so this is the closure as that graph states it rather than a restored consumer's exact resolution.
D15 · Churn × Complexity Hotspots
No churn × complexity hotspots in the window.
D16 · Bus Factor
3 source file(s) have their living knowledge concentrated in one author (≥90% of recent, decayed contribution). The largest is Source/ChocolateyGui.Common.Windows/ViewModels/RemoteSourceViewModel.cs. Counted over 44 of the 187 production source files in this repository: 129 are under the ~2,400-byte size floor this dimension measures over, and the remaining 14 have no attributable history left to measure.
D17 · Explicit Debt
29 deducted debt markers + unmeasured dead symbols across 13535 LoC in the .NET projects (0.9/KLoC) → score 8.2. Dead code not measured: the solution did not load cleanly, so the reference search was skipped. Measured on the .NET source only: .h (35% of production source) was not read, and carries at least 0 uncounted task marker(s) in 0 file(s).
What to do
- Resolve the 6 WriteOnlyPrivateField finding(s) in Explicit Debt — start with PackageArgumentsService.cs, AdvancedInstallViewModel.cs, PackageViewModel.cs. — One of this dimension's main actionable groups (6 issue-level).
- Resolve the 1 EmptyCatchBlock finding(s) in Explicit Debt — start with Internationalization.cs. — One of this dimension's main actionable groups (1 issue-level).
- Resolve the 9 BarePragmaDisable finding(s) in Explicit Debt — start with RemoteSourceViewModel.cs (5), Bootstrapper.cs (2), InternetImage.xaml.cs. — One of this dimension's main actionable groups (9 warning-level).
D18 · Solution Shape
8 projects, 218 source files, 15980 hand-written lines of code (13535 production / 2445 test — the split is derived per file: test is what its project, its own path, or a compile-guarded region marks as test, and a file carrying no test signal counts as production), plus 3278 generated (machine-written code — designer, scaffolded and tool-emitted files — excluded from quality), 8 inter-project edges (build failed).
What to do
- Resolve the 1 Build failed finding(s) in Solution Shape. — One of this dimension's main actionable groups (1 warning-level).
D19 · Documentation Quality
2 of 2 documentation facets pass in full. 2 document(s) read across 5 unit(s).
D20 · ADR Quality
No architecture decision records were found.
What to do
- Resolve the 1 No ADRs found finding(s) in ADR Quality — start with ChocolateyGui.csproj. — One of this dimension's main actionable groups (1 recommendation-level).
D24 · Comment Value
5 of 159 judged comments only repeat the code they sit on (3.1 %). 2 comment(s) in another language or script were not judged.
What to do
- Resolve the 5 redundant comment finding(s) in Comment Value — start with AssemblyInfo.cs (3), ChocolateyGuiModule.cs, DataGridCustomSortBehavior.cs. — One of this dimension's main actionable groups (5 recommendation-level).
D26 · Project Cohesion
1 of 8 projects flagged as possibly oversized/incoherent.
What to do
- Resolve the 1 Projects may be oversized for their cohesion finding(s) in Project Cohesion — start with ChocolateyGui.Common.Windows.csproj. — One of this dimension's main actionable groups (1 recommendation-level).
D27 · Navigability
85 % of calls cross a namespace and 22 % go through an interface, but 100 % of collaborators are co-located — so following a call takes several hops. Baseline: medium — clean/modular boundaries expected. Measured over the .cs source only — this repository's .h was not sampled for call sites, so this score covers part of the tree, not all of it.
D28 · Secrets (history)
1 finding(s): 0 critical, 1 high, 0 medium, 0 low.
What to do
- Resolve the 1 High secret finding(s) in Secrets (history) — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
D29 · Static Analysis (SAST)
21 finding(s): 0 critical, 18 high, 3 medium, 0 low. 10 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 10 file(s) — `Source/ChocolateyGui.Install/tools/wix/311/sdk/inc/IBootstrapperEngine.h` (line 101, line 105, line 106, …), `Source/ChocolateyGui.Install/tools/wix/311/sdk/inc/apputil.h` (line 15, line 16, line 19, …), `Source/ChocolateyGui.Install/tools/wix/311/sdk/inc/balutil.h` (lines 37–39, line 45, lines 51–54, …), `Source/ChocolateyGui.Install/tools/wix/311/sdk/inc/deputil.h` (lines 25–31, lines 39–48, lines 55–62, …), `Source/ChocolateyGui.Install/tools/wix/311/sdk/inc/dutil.h`, … (+5 more) — so no absence of findings in the named regions is evidence of anything; rows reported elsewhere in those files are real. Fix the syntax error (or exclude the file deliberately) and re-scan to cover them. Separately, one or more rules could not re-parse an embedded snippet in 1 file(s) (e.g. a workflow `run:` block read as shell). Those files WERE scanned and their other rows are unaffected; only those rules' view of those snippets is missing.
What to do
- Resolve the 4 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (2), REDACTED (2). — One of this dimension's main actionable groups (4 issue-level).
- Resolve the 3 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (2), REDACTED. — One of this dimension's main actionable groups (3 issue-level).
- No action in Static Analysis (SAST) — all 10 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 (10 issue-level, 0 of them charged here).
D30 · Dependency Vulnerabilities
No known-vulnerable dependencies in the 1 ecosystem(s) that were scanned (osv). Partial dependency scan: 1 of 2 declared ecosystem(s) were scanned (osv), and the findings above are real and complete for them. nuget was not scanned (nuget: the solution did not restore on the analyzer's .NET SDK (an SDK/target-framework/restore mismatch, common for an older codebase), so there was no restored dependency graph to scan), so this is not the whole dependency surface and the result is reported at reduced confidence.
D34 · Knowledge Freshness
14 of 58 significant source file(s) are orphaned — their living knowledge has decayed to nothing, so no one currently understands them. The largest is Source/ChocolateyGuiCli/Runner.cs. Counted over 58 of the 187 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.
What to do
- Resolve the 14 Orphaned file finding(s) in Knowledge Freshness — start with Runner.cs, DialogService.cs, BundledThemeService.cs. — One of this dimension's main actionable groups (14 recommendation-level).
- Resolve the 1 Orphaned files with no living knowledge finding(s) in Knowledge Freshness. — One of this dimension's main actionable groups (1 recommendation-level).
D35 · Change Coupling
No strong hidden change-coupling between production files.
D36 · Supply-chain Provenance & Signing
1/4 supply-chain integrity signals present (provenance, signing, SBOM, pinned actions).
What to do
- Resolve the 3 REDACTED finding(s) in Supply-chain Provenance & Signing — start with REDACTED, REDACTED, REDACTED. — One of this dimension's main actionable groups (3 warning-level).
- Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 warning-level).
- Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing — start with REDACTED. — One of this dimension's main actionable groups (1 warning-level).
D43 · Malicious Dependencies
No dependency in any ecosystem this repository declares is published as malicious.
D44 · Platform End-of-Life
0 end-of-life runtime(s) and 0 end-of-life framework(s), read from 8 platform declaration(s) and 2 dependency declaration(s). This dimension reads what the repository says about ITSELF — a pinned target framework, a version file, a capped requires-python, a Rust toolchain pin, a framework major a constraint cannot move off. A FLOOR is deliberately never charged: `requires-python = ">=3.8"` states what the package SUPPORTS, not what it runs on, and a well-maintained library declares exactly that while running its own CI on a current release. The end-of-life facts are FROZEN and dated, so this dimension needs no network and answers identically inside a closed scan fence; as the table ages it loses recall and never precision, because a statement about support that ended in the past cannot become false. The OS layer of a container image is D31's question and the toolchain a CI workflow installs is D29's; this row is neither.
Frontend & cross-cutting dimensions
AX10 · Code composition
AX2 · Stateful singletons
- `TranslationSource` keeps one instance of itself in the static `_instance`, so that one instance serves the whole process and is shared by every thread that reaches it — and it mutates instance state outside any lock (_currentCulture; e.g. `_currentCulture` at line 40). — Source/ChocolateyGui.Common/Utilities/TranslationSource.cs:17
- `CommandBindingsProvider` is not registered, but `RoutedCommandMonitor` creates it and keeps it in the static `UIElementCommandBindingsProvider`, so that one instance serves the whole process and is shared by every thread that reaches it — and it mutates instance state outside any lock (_getCommandBindings; e.g. `_getCommandBindings` at line 182). — Source/ChocolateyGui.Common.Windows/Commands/RoutedCommandMonitor.cs:161
- `Bootstrapper` keeps mutable `static` state — one slot for the whole process, shared by every thread that reaches the type however its instances are created — and mutates it outside any lock (Logger, Container; e.g. `Logger` at line 97). Concurrent callers lose updates, and a collection that is not built for concurrent writers can corrupt. — Source/ChocolateyGuiCli/Bootstrapper.cs:21
- `LogSetup` keeps mutable `static` state — one slot for the whole process, shared by every thread that reaches the type however its instances are created — and mutates it outside any lock (_logsFolderPath, _localAppDataPath, _appDataPath; e.g. `_logsFolderPath` at line 34). Concurrent callers lose updates, and a collection that is not built for concurrent writers can corrupt. — Source/ChocolateyGui.Common/Utilities/LogSetup.cs:13
- `Bootstrapper` keeps mutable `static` state — one slot for the whole process, shared by every thread that reaches the type however its instances are created — and mutates it outside any lock (IsExiting, Logger, Container; e.g. `IsExiting` at line 107). Concurrent callers lose updates, and a collection that is not built for concurrent writers can corrupt. — Source/ChocolateyGui.Common.Windows/Bootstrapper.cs:35
- `DesignMode` keeps mutable `static` state — one slot for the whole process, shared by every thread that reaches the type however its instances are created — and mutates it outside any lock (isInDesignMode; e.g. `isInDesignMode` at line 28). Concurrent callers lose updates, and a collection that is not built for concurrent writers can corrupt. — Source/ChocolateyGui.Common.Windows/DesignMode.cs:13
- `CommandExecutionManager` keeps mutable `static` state — one slot for the whole process, shared by every thread that reaches the type however its instances are created — and mutates it outside any lock (_isDisconnected, _disconnectedItemSentinelValue; e.g. `_isDisconnected` at line 87). Concurrent callers lose updates, and a collection that is not built for concurrent writers can corrupt. — Source/ChocolateyGui.Common.Windows/Commands/CommandExecutionManager.cs:25
- `Internationalization` keeps mutable `static` state — one slot for the whole process, shared by every thread that reaches the type however its instances are created — and mutates it outside any lock (_cachedCultures; e.g. `_cachedCultures` at line 32). Concurrent callers lose updates, and a collection that is not built for concurrent writers can corrupt. — Source/ChocolateyGui.Common.Windows/Startup/Internationalization.cs:18
What to do
- Keep singletons stateless or back their state with thread-safe types (Concurrent*/Immutable*); otherwise concurrent callers race.
- A `static` field is one slot for the whole process, however its type is created: back it with a thread-safe type (ConcurrentDictionary, Interlocked), take a lock around every write, or move it into a registered singleton that does.
AX3 · Project dependency cycles
- The namespaces ChocolateyGui.Common.Models ↔ ChocolateyGui.Common.ViewModels.Items depend on each other. The lightest dependency in the cycle is ChocolateyGui.Common.Models → ChocolateyGui.Common.ViewModels.Items (ChocolateyGui.Common.Models.PackageSearchResults → ChocolateyGui.Common.ViewModels.Items.IPackageViewModel, 1 type pair(s)); cut that one first, e.g. by moving the shared type to a namespace both can use or inverting it behind an interface. — Source/ChocolateyGui.Common/Models/PackageSearchResults.cs:9
- The namespaces ChocolateyGui.Common.Windows ↔ ChocolateyGui.Common.Windows.Controls ↔ ChocolateyGui.Common.Windows.Controls.Dialogs ↔ ChocolateyGui.Common.Windows.Services ↔ ChocolateyGui.Common.Windows.Views depend on each other. The lightest dependency in the cycle is ChocolateyGui.Common.Windows → ChocolateyGui.Common.Windows.Services (ChocolateyGui.Common.Windows.SerilogLogger → ChocolateyGui.Common.Windows.Services.IProgressService, 1 type pair(s)); cut that one first, e.g. by moving the shared type to a namespace both can use or inverting it behind an interface. — Source/ChocolateyGui.Common.Windows/SerilogLogger.cs:16
What to do
- Break namespace cycles inside a project by moving the shared type to a namespace both sides can use, or by inverting the back edge behind an interface.
AX4 · Dependency direction
AX5 · Architecture & structure
AX6 · Interface segregation
- `IChocolateyService` declares 24 members: `IsElevated`, `GetInstalledPackages`, `GetOutdatedPackages`, `GetOutdatedPackages`, `Search`, `GetByVersionAndIdAsync`, `GetAvailableVersionsForPackageIdAsync`, `InstallPackage`, `UninstallPackage`, `UpdatePackage`, `UpdatePackage`, `PinPackage`, `UnpinPackage`, `GetFeatures`, `SetFeature`, `GetSettings`, `SetSetting`, `GetSources`, `AddSource`, `UpdateSource`, `EnableSource`, `DisableSource`, `RemoveSource`, `ExportPackages`. Counted as the author wrote them — a property is ONE member and its get/set accessors are not counted separately, and an event counts once. Those 24 declarations carry 22 distinct name(s), so part of the width is overloading rather than separate responsibilities — but 22 operations clears the >15 bar on its own, so the row is about responsibilities, not signatures. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces. — Source/ChocolateyGui.Common/Services/IChocolateyService.cs:16
- `IPackageViewModel` declares 38 members: `Authors`, `CanUpdate`, `Copyright`, `Dependencies`, `Description`, `DownloadCount`, `GalleryDetailsUrl`, `IconUrl`, `Id`, `IsOutdated`, `IsInstalled`, `IsPinned`, `IsPrerelease`, `Language`, `LatestVersion`, `LicenseUrl`, `Owners`, `PackageHash`, `PackageHashAlgorithm`, `PackageSize`, `ProjectUrl`, `Published`, `ReleaseNotes`, `ReportAbuseUrl`, `RequireLicenseAcceptance`, `Source`, `ChocolateySource`, `Summary`, `Tags`, `Title`, `Version`, `RemoteVersion`, `VersionDownloadCount`, `Install`, `InstallAdvanced`, `Uninstall`, `Update`, `ViewDetails`. Counted as the author wrote them — a property is ONE member and its get/set accessors are not counted separately, and an event counts once. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces. — Source/ChocolateyGui.Common/ViewModels/Items/IPackageViewModel.cs:14
What to do
- Split fat interfaces into focused role-interfaces so clients depend only on what they use.
AX8 · Test isolation
GD1 · Unfinished & placeholder code
- A shipped member still throws NotImplementedException — generated scaffolding that was never completed. Implement it or remove the dead surface. (×13) — Source/ChocolateyGui.Common.Windows/Utilities/Converters/BooleanInverter.cs:33, Source/ChocolateyGui.Common.Windows/Utilities/Converters/BooleanInverter.cs:38, Source/ChocolateyGui.Common.Windows/Utilities/Converters/BooleanToVisibility.cs:31, …
What to do
- Finish or delete NotImplementedException stubs and replace placeholder literals before shipping.
IC1 · Incompleteness & stubs
- A line of code has been commented out rather than removed — dead weight that rots and confuses. Delete it (version control remembers). (×4) — Source/ChocolateyGui.Common.Windows/Commands/CommandExecutionManager.cs:193, Source/ChocolateyGui.Common.Windows/Commands/CommandExecutionManager.cs:196, Source/ChocolateyGui.Common.Windows/Commands/CommandExecutionManager.cs:200, …
What to do
- Clear the softer debt: remove commented-out code and dead branches, re-enable or delete skipped tests, and replace blanket warning suppressions with targeted ones.
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.
M2 · Architecture documentation
- No Architecture Decision Records found — no conventional ADR directory, no numbered `NNNN-title` documents in any markup this check reads, and nothing ADR-shaped by content. Design rationale recorded elsewhere (a design-notes tree, a mailing list, pull-request discussion) is not visible to this check and is not re-findable per decision, so a future maintainer cannot ask why one choice was made and get an answer.
- No C4/Structurizr/PlantUML/Mermaid/Graphviz/D2 diagram, no drawn diagram named for the architecture, no file named `architecture` or `design` in any markup this check reads, and nothing in the README, docs or contributor guides that announces the shape — no `## Architecture` heading, no "architecture overview"/"high-level design" phrasing, no "the architecture is …" introduction, no guided code tour. A shape laid out in prose that never names itself as the architecture is not visible to this check, and neither is one kept outside the repository, so this row reports the absence of a re-findable shape document — not evidence that nobody wrote the shape down.
What to do
- Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them.
- Add a C4 context/container diagram (Structurizr, PlantUML or Mermaid) or an architecture.md overview.
M3 · Folder & project structure
P1 · CI/CD gates
P2 · Observability
- `Source/ChocolateyGui.Common/Services/ConfigService.cs` reports through `Console.Write…` at line 187 although other files in its project log through a logger. Console lines carry no level, category or structured properties and never reach the log pipeline or its exporters. — Source/ChocolateyGui.Common/Services/ConfigService.cs:187
What to do
- Replace `Console.Write…` in service code with the project's injected `ILogger<T>` (message templates with named properties), so delivery outcomes and failures reach the log pipeline with a level and a category.
- Add a health-check endpoint (AddHealthChecks/MapHealthChecks) so orchestrators and load balancers can probe liveness/readiness.
P3 · Security & performance tooling
- `Source/ChocolateyGui.Common.Tests/ChocolateyGui.Common.Tests.csproj` declares packages, and nothing in the repository keeps them current: no Dependabot or Renovate configuration that schedules updates, and no dependency-review gate on pull requests. A pinned dependency stays at the version it was added at until someone notices — including after an advisory is published against it. Add a `.github/dependabot.yml` with one `package-ecosystem` entry per ecosystem the tree uses (or an enabled `renovate.json`), and gate pull requests with `actions/dependency-review-action`. — Source/ChocolateyGui.Common.Tests/ChocolateyGui.Common.Tests.csproj:12
What to do
- Enable Dependabot/Renovate or a dependency-review gate.
- Add gitleaks/trufflehog in CI to block PRs that introduce committed secrets.
P4 · Deployment & Rollback
- No release automation was found in CI — neither a deploy stage (Helm/Kubernetes/compose manifests, an orchestrated rollout) nor a publish job that ships the built artifact. Releases appear to be run by hand, which is slower, less repeatable and harder to reverse.
- This step syncs the release over the live copy with delete (`EndBug/label-sync` with `delete-other-labels: true`): files the new build lacks are removed in place and the rest are overwritten, so the previous release is gone and a half-finished sync serves a mix of both. There is no staged copy to switch back to. — REDACTED:27
What to do
- Automate the release in CI — a deploy stage for a service (Helm/Kubernetes manifests or an equivalent rollout), or a tag-triggered publish job for an artifact — so releases are repeatable and reversible.
- Upload each release beside the live one (a release-unique path) and switch to it, so the previous release stays one switch away; or drop the delete from the live sync.
P6 · Release Hygiene
P7 · Outbound HTTP resilience
- `new HttpClient()` builds an outbound HTTP client and nothing bounds it: no timeout is set on it and no retry or resilience policy wraps its calls in the type that owns it. A slow or failing dependency will hold this service's request, thread or connection — and cascade — until the call gives up on its own (100 s for HttpClient's default). — Source/ChocolateyGui.Common.Windows/Services/PackageIconService.cs:204
What to do
- Add `AddStandardResilienceHandler()` (or a Polly policy and an explicit timeout) to each client registration flagged here, so a flaky dependency can't take the app down.
PF3 · Async & latency hygiene
S1 · Cryptographic Hygiene
- MD5/SHA1 is constructed 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+ for content integrity, or a KDF (PBKDF2/Argon2/BCrypt) for password storage. If it only derives a non-security identifier (a cache key, a file or mutex name), collision resistance carries no security consequence here; make that intent explicit instead — a non-cryptographic hash such as `System.IO.Hashing.XxHash64`/`Crc32` says it in code — since the algorithm alone cannot distinguish the two uses. — Source/ChocolateyGui.Common.Windows/Controls/FauxPowerShellConsole.cs:57
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 (`System.IO.Hashing.XxHash64`/`Crc32`) where it only derives an identifier such as a cache key or a mutex name.
X1 · Async correctness
- `async void` can't be awaited and its exceptions crash the process instead of propagating. Return `Task` — or, where the delegate contract requires void (timer/event/callback registrations), make this a thin void shim that awaits a Task-returning inner method inside try/catch so exceptions are contained. (×13) — Source/ChocolateyGui.Common.Windows/ViewModels/Items/PackageViewModel.cs:722, Source/ChocolateyGui.Common.Windows/ViewModels/LocalSourceViewModel.cs:208, Source/ChocolateyGui.Common.Windows/ViewModels/LocalSourceViewModel.cs:255, …
What to do
- async void method: ViewDetails
X12 · Unreachable branch
X13 · Undrained process stream
X16 · Unfloored truncation loop
X18 · Disposal-pattern correctness
- `hashAlg` is a `MD5`, which implements `IDisposable`, and it is created here (line 57). Every use of it in `FauxPowerShellConsole` reads a member through it — it is never returned, never stored, never handed to anything else, and never disposed — so this method both creates the value and is the last thing that can release it, and does not. Nothing announces the leak: the object holds its resource until finalization if its type has a finalizer, and until the process ends if it does not, so the cost accumulates once per CALL rather than showing up as a failure. Declare it with `using` (`using var hashAlg = …;`), which releases it at the end of the scope on every path including a throw. — Source/ChocolateyGui.Common.Windows/Controls/FauxPowerShellConsole.cs:57
- `fd` is a `FolderBrowserDialog`, which implements `IDisposable`, and it is created here (line 38). Every use of it in `GetFolderPath` reads a member through it — it is never returned, never stored, never handed to anything else, and never disposed — so this method both creates the value and is the last thing that can release it, and does not. Nothing announces the leak: the object holds its resource until finalization if its type has a finalizer, and until the process ends if it does not, so the cost accumulates once per CALL rather than showing up as a failure. Declare it with `using` (`using var fd = …;`), which releases it at the end of the scope on every path including a throw. — Source/ChocolateyGui.Common.Windows/Services/PersistenceService.cs:38
What to do
- Each finding names the value and the span that decides who owns it — the `new` that created it, or the constructor parameter that handed it over. Confirm ownership from that span, then make the disposal match it: release what this type created, leave what it was injected with to whoever created THAT, and drop a finalizer whose type holds nothing unmanaged to release.
X19 · Unrestored process-global state
X2 · Cancellation propagation
- Only 0/72 async methods accept a CancellationToken, so in-flight work can't be stopped early when the caller gives up — whatever ends it in your host (shutdown signal, timeout, abandoned request, user cancel). Thread a token through the call chain and honour it at each await and loop; where a method genuinely cannot be interrupted, omitting it is a deliberate choice — judge against your hosting model.
- No CancellationToken parameter — this work can't be stopped early once started. (×38) — Source/ChocolateyGui.Common/ChocolateyExtensions.cs:18, Source/ChocolateyGui.Common/ChocolateyExtensions.cs:23, Source/ChocolateyGui.Common/ChocolateyExtensions.cs:28, …
- No CancellationToken parameter, and the token `settings.CancellationToken` carries reaches none of the calls here that take one — this work can't be stopped early once started. Pass `settings.CancellationToken` on, or take a CancellationToken. — Source/ChocolateyGui.Common.Windows/Services/DialogService.cs:103
What to do
- Thread a CancellationToken through async methods so work stops promptly on cancellation.
X20 · Mistyped argument guard
X23 · Unguarded diagnostic materialisation
X27 · Collection changed while being enumerated
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. — Source/ChocolateyGui.Common.Windows/Startup/Internationalization.cs:55
What to do
- Swallowed exception (empty catch)
X4 · Structured logging
Reference — by lens
| Lens | Score | Rating | Impact |
|---|---|---|---|
| Code Health | 62.7 | Adequate — gated by D18 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Architecture | 70.9 | Adequate — gated by AX2 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Maturity | 52.3 | Adequate — gated by M2 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Readiness | 47.5 | Weak — gated by P4, P7 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Security | 68.1 | Adequate — gated by D29, D36 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Performance | 100.0 | Exemplary | Strongest area. |
Unscored — 3 check(s) recorded observations but carry no score
- P12 CI test-gate honesty — 1 observation(s) recorded · Reported, not scored — this card publishes what the CI gate does with the test inventory rather than grading it. The findings above are its output.
- SC1 Supply-chain hygiene — 7 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
- X10 Duplicated predicate — 3 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
Not evidenced — 1 control(s) we could not find positive evidence for
- P5 DR & Backup — not evidenced — repo shows no backup/RTO/RPO controls; absence of evidence is not evidence of a working control
Not included — 54 check(s) not relevant to this codebase
- AC1 Text alternatives — No web markup found — accessibility is not applicable to this repository.
- AC2 Forms & labels — No web markup found — accessibility is not applicable to this repository.
- AC3 Page structure — No web markup found — accessibility is not applicable to this repository.
- AC4 Keyboard semantics — No web markup found — accessibility is not applicable to this repository.
- AC5 ARIA correctness — No web markup found — accessibility is not applicable to this repository.
- AC6 Visual & motion safety — No web markup found — accessibility is not applicable to this repository.
- AX1 Captive dependencies — no DI registrations detected
- AX7 Slice cohesion — not applicable — not a vertical-slice architecture
- AX9 CQS / query purity — no CQRS query handlers detected — query purity is not applicable to this codebase
- AXB1 Runtime evidence locked — no reproducible boot — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- AXB2 Runtime readiness — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- C1 Data Protection — No personal data detected in the analyzed source — no PII-typed entity/column names (Email, FirstName, DateOfBirth, …), no ASP.NET Identity / user-account model, and no stored user credentials. GDPR data-protection controls are therefore N/A here. If this is intentional, record the no-PII posture in an ADR; if the app does process personal data, name those fields conventionally so this dimension activates.
- C2 Access Controls — No access-control surface detected in the analyzed source — no web/app surface to authorize (no HTTP API or web-UI project) and no authorization code at all (no [Authorize]/policies, no imperative guard methods). Access control is therefore N/A here — this is a library/CLI, which is authorized by its CALLER, not by itself. If this codebase grows request handlers, the dimension reactivates and a default-deny posture is expected then.
- C3 Audit Trail — No personal data detected in the analyzed source — no PII-typed entity/column names (Email, FirstName, DateOfBirth, …), no ASP.NET Identity / user-account model, and no stored user credentials. GDPR data-protection controls are therefore N/A here. If this is intentional, record the no-PII posture in an ADR; if the app does process personal data, name those fields conventionally so this dimension activates.
- C4 Data Retention — No personal data detected in the analyzed source — no PII-typed entity/column names (Email, FirstName, DateOfBirth, …), no ASP.NET Identity / user-account model, and no stored user credentials. GDPR data-protection controls are therefore N/A here. If this is intentional, record the no-PII posture in an ADR; if the app does process personal data, name those fields conventionally so this dimension activates.
- C5 Data-Subject Rights — No personal data detected in the analyzed source — no PII-typed entity/column names (Email, FirstName, DateOfBirth, …), no ASP.NET Identity / user-account model, and no stored user credentials. GDPR data-protection controls are therefore N/A here. If this is intentional, record the no-PII posture in an ADR; if the app does process personal data, name those fields conventionally so this dimension activates.
- D11 Test Reliability — Test runner surfaced no tests
- D12 Dependency Hygiene — Dependency hygiene not measured
- D21 Naming Consistency — N/A — too few peers to establish a naming convention (2502 declarations, no unit with a dominant convention).
- D22 Internal API Consistency — No intentionally-exposed public API to evaluate for consistency.
- D23 Boundary Type-Coupling — small single-context codebase (13,535 production LoC in the .NET projects) — bounded contexts are not needed at this size No bounded-context organisation was detected either — neither a context-shaped layout, nor 2+ sibling source directories each declaring an aggregate root, nor 2+ sibling projects each declaring an entity of their own or taking another project's integration events. Declaring this codebase's bounded contexts (≥2) would let cross-boundary type coupling be assessed. Declare them in `.codehealth/config.yaml` at the repository root (create it if absent), mapping each context name to the module-path or namespace prefixes that belong to it — e.g. `architecture:` → `contexts:` → `Billing: ["src/billing", "Acme.Billing"]`, `Catalog: ["src/catalog", "Acme.Catalog"]`.
- D25 ADR Conformance — no ADRs to check
- 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) — 1 file(s) were not parsed by semgrep — the PII/GDPR ruleset never ran over them
- D37 Vulnerability-disclosure Policy — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed.
- D40 Network Egress Confinement — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here.
- D41 Kernel & Syscall Confinement — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here.
- D42 Runtime Threat Enforcement — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here.
- D7 Architectural Integrity — no checkable ADRs and no dependency cycles — architectural integrity not assessed
- D8 Code Coverage — Coverage NOT MEASURED: this repository did not build in our analyzer environment (a C#/MSBuild compiler error), so no coverage could be collected. It is excluded from the score rather than counted as a near-zero defect. We did not read WHERE the failing diagnostic is, so this does not claim the fault is in your test code — a repository written for an older SDK band can compile for you and not for us. Run `dotnet build` on this commit; if it succeeds, the gap is ours. Committing the Cobertura/OpenCover/lcov report your CI already produces also lets us measure real coverage without building anything.
- DM1 Domain Modelling — not scored — this repository shows none of the 3 signals this lens looks for
- ED1 Event-Driven — not scored — this repository shows none of the 3 signals this lens looks for
- ED5 Idempotency — no mutating command handlers or message consumers detected — idempotency check not applicable
- ES1 Event Sourcing — not scored — this repository shows none of the 3 signals this lens looks for
- M4 Documentation accuracy — Not applicable: the 2 current-state document(s) make no claim of a kind M4 checks. 3 claim(s) of kinds M4 does not check were not checked (path 1, command argument 2); M4 checks only links and versions and artefact counts.
- P8 Schema migrations — no EF Core usage detected
- P9 Domain vs controller coverage — coverage not measured: this check compares the coverage of the analyzer's own test run across the domain and web layers, and that run measured none here — Test coverage (D8) says why
- PF1 Benchmark discipline — Performance is assessed only for perf-relevant repos — a packaged library, one that ships benchmarks, or one already using allocation-aware APIs. This repo isn't one, so the Performance lens is not applicable and is excluded from the score.
- PF2 Allocation hygiene — Not scored: this check counted allocation-aware idioms (Span, pools, stackalloc) per line, which describes what kind of code a repository is rather than whether it has an allocation problem, so it was withdrawn. Nothing here is a finding about your code.
- X14 Bypassable address classification — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X15 Unvalidated length from an untrusted reader — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X17 Uncapped recursion over a caller-supplied document — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X21 Side-effecting pattern guard — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X22 Contradicted release guard — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X24 Document value interpolated into markup unescaped — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X25 Inert configuration knob — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X26 Unsynchronised callback handoff — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X28 Index access outside its own emptiness guard — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X30 Support guard that admits what it rejects — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X32 Type resolved by simple name across every loaded assembly — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X5 Nullable reference types — no NRT-eligible projects
- X6 Hand-rolled structured-format parsing — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- X7 Silent fallback defaults — 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 — 29 finding(s)
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- WriteOnlyPrivateField Source/ChocolateyGui.Common.Windows/Services/PackageArgumentsService.cs:27
- WriteOnlyPrivateField Source/ChocolateyGui.Common.Windows/ViewModels/AdvancedInstallViewModel.cs:27
- WriteOnlyPrivateField Source/ChocolateyGui.Common.Windows/ViewModels/Items/PackageViewModel.cs:44
- WriteOnlyPrivateField Source/ChocolateyGui.Common.Windows/ViewModels/LocalSourceViewModel.cs:52
- WriteOnlyPrivateField Source/ChocolateyGui.Common.Windows/ViewModels/RemoteSourceViewModel.cs:45
- WriteOnlyPrivateField Source/ChocolateyGui.Common.Windows/ViewModels/SettingsViewModel.cs:45
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Namespace dependency cycle Source/ChocolateyGui.Common/Models/PackageSearchResults.cs:9
- Namespace dependency cycle Source/ChocolateyGui.Common.Windows/SerilogLogger.cs:16
- REDACTED
- EmptyCatchBlock Source/ChocolateyGui.Common.Windows/Startup/Internationalization.cs:55
- REDACTED
- REDACTED
Serious — 147 finding(s)
- Async method without CancellationToken: RunAsync Source/ChocolateyGui.Common/ChocolateyExtensions.cs:18
- Async method without CancellationToken: ListAsync Source/ChocolateyGui.Common/ChocolateyExtensions.cs:23
- Async method without CancellationToken: ListPackagesAsync Source/ChocolateyGui.Common/ChocolateyExtensions.cs:28
- Async method without CancellationToken: SetImage Source/ChocolateyGui.Common.Windows/Controls/InternetImage.xaml.cs:48
- Async method without CancellationToken: GetInstalledPackages Source/ChocolateyGui.Common.Windows/Services/ChocolateyService.cs:72
- Async method without CancellationToken: GetOutdatedPackages Source/ChocolateyGui.Common.Windows/Services/ChocolateyService.cs:106
- Async method without CancellationToken: GetOutdatedPackages Source/ChocolateyGui.Common.Windows/Services/ChocolateyService.cs:111
- Async method without CancellationToken: InstallPackage Source/ChocolateyGui.Common.Windows/Services/ChocolateyService.cs:208
- Async method without CancellationToken: Search Source/ChocolateyGui.Common.Windows/Services/ChocolateyService.cs:307
- Async method without CancellationToken: GetByVersionAndIdAsync Source/ChocolateyGui.Common.Windows/Services/ChocolateyService.cs:348
- Async method without CancellationToken: GetAvailableVersionsForPackageIdAsync Source/ChocolateyGui.Common.Windows/Services/ChocolateyService.cs:381
- Async method without CancellationToken: UninstallPackage Source/ChocolateyGui.Common.Windows/Services/ChocolateyService.cs:407
- Async method without CancellationToken: UpdatePackage Source/ChocolateyGui.Common.Windows/Services/ChocolateyService.cs:430
- Async method without CancellationToken: UpdatePackage Source/ChocolateyGui.Common.Windows/Services/ChocolateyService.cs:435
- Async method without CancellationToken: PinPackage Source/ChocolateyGui.Common.Windows/Services/ChocolateyService.cs:458
- Async method without CancellationToken: UnpinPackage Source/ChocolateyGui.Common.Windows/Services/ChocolateyService.cs:485
- Async method without CancellationToken: GetFeatures Source/ChocolateyGui.Common.Windows/Services/ChocolateyService.cs:511
- Async method without CancellationToken: SetFeature Source/ChocolateyGui.Common.Windows/Services/ChocolateyService.cs:518
- Async method without CancellationToken: GetSettings Source/ChocolateyGui.Common.Windows/Services/ChocolateyService.cs:539
- Async method without CancellationToken: SetSetting Source/ChocolateyGui.Common.Windows/Services/ChocolateyService.cs:546
- Async method without CancellationToken: GetSources Source/ChocolateyGui.Common.Windows/Services/ChocolateyService.cs:563
- Async method without CancellationToken: AddSource Source/ChocolateyGui.Common.Windows/Services/ChocolateyService.cs:580
- Async method without CancellationToken: DisableSource Source/ChocolateyGui.Common.Windows/Services/ChocolateyService.cs:614
- Async method without CancellationToken: EnableSource Source/ChocolateyGui.Common.Windows/Services/ChocolateyService.cs:630
- Async method without CancellationToken: UpdateSource Source/ChocolateyGui.Common.Windows/Services/ChocolateyService.cs:646
- Unfinished stub — throws NotImplementedException Source/ChocolateyGui.Common.Windows/Utilities/Converters/BooleanInverter.cs:33
- Unfinished stub — throws NotImplementedException Source/ChocolateyGui.Common.Windows/Utilities/Converters/BooleanInverter.cs:38
- Unfinished stub — throws NotImplementedException Source/ChocolateyGui.Common.Windows/Utilities/Converters/BooleanToVisibility.cs:31
- Unfinished stub — throws NotImplementedException Source/ChocolateyGui.Common.Windows/Utilities/Converters/BooleanToVisibility.cs:36
- Unfinished stub — throws NotImplementedException Source/ChocolateyGui.Common.Windows/Utilities/Converters/BooleanToVisibilityHidden.cs:24
- Unfinished stub — throws NotImplementedException Source/ChocolateyGui.Common.Windows/Utilities/Converters/BooleanToVisibilityInverted.cs:32
- Unfinished stub — throws NotImplementedException Source/ChocolateyGui.Common.Windows/Utilities/Converters/BooleanToVisibilityInverted.cs:37
- Unfinished stub — throws NotImplementedException Source/ChocolateyGui.Common.Windows/Utilities/Converters/LocalizationConverter.cs:48
- Unfinished stub — throws NotImplementedException Source/ChocolateyGui.Common.Windows/Utilities/Converters/LongSizeToFileSizeString.cs:35
- Unfinished stub — throws NotImplementedException Source/ChocolateyGui.Common.Windows/Utilities/Converters/MultiBooleanAndToVisibility.cs:26
- Unfinished stub — throws NotImplementedException Source/ChocolateyGui.Common.Windows/Utilities/Converters/NullToValue.cs:30
- Unfinished stub — throws NotImplementedException Source/ChocolateyGui.Common.Windows/Utilities/Converters/PackageDependenciesToString.cs:58
- Unfinished stub — throws NotImplementedException Source/ChocolateyGui.Common.Windows/Utilities/Converters/StringListToString.cs:30
- async void method: ViewDetails Source/ChocolateyGui.Common.Windows/ViewModels/Items/PackageViewModel.cs:722
- async void method: UpdateAll Source/ChocolateyGui.Common.Windows/ViewModels/LocalSourceViewModel.cs:208
- async void method: ExportAll Source/ChocolateyGui.Common.Windows/ViewModels/LocalSourceViewModel.cs:255
- async void method: RefreshPackages Source/ChocolateyGui.Common.Windows/ViewModels/LocalSourceViewModel.cs:309
- async void method: OnInitialize Source/ChocolateyGui.Common.Windows/ViewModels/LocalSourceViewModel.cs:325
- async void method: CheckForOutdatedPackages Source/ChocolateyGui.Common.Windows/ViewModels/RemoteSourceViewModel.cs:410
- async void method: OnActivate Source/ChocolateyGui.Common.Windows/ViewModels/RemoteSourceViewModel.cs:416
- async void method: ChocolateySettingsRowEditEnding Source/ChocolateyGui.Common.Windows/ViewModels/SettingsViewModel.cs:279
- async void method: ChocolateyGuiSettingsRowEditEnding Source/ChocolateyGui.Common.Windows/ViewModels/SettingsViewModel.cs:285
- async void method: SetUserAndPassword Source/ChocolateyGui.Common.Windows/ViewModels/SettingsViewModel.cs:516
- async void method: SetCertificateAndPassword Source/ChocolateyGui.Common.Windows/ViewModels/SettingsViewModel.cs:544
- async void method: OnActivated Source/ChocolateyGui.Common.Windows/ViewModels/SettingsViewModel.cs:579
- async void method: GetSources Source/ChocolateyGui.Common.Windows/ViewModels/ShellViewModel.cs:202
- BarePragmaDisable Source/ChocolateyGui.Common.Windows/Bootstrapper.cs:39
- BarePragmaDisable Source/ChocolateyGuiCli/Bootstrapper.cs:25
- BarePragmaDisable Source/ChocolateyGui.Common.Windows/Controls/InternetImage.xaml.cs:35
- BarePragmaDisable Source/ChocolateyGui.Common.Windows/ViewModels/RemoteSourceViewModel.cs:261
- BarePragmaDisable Source/ChocolateyGui.Common.Windows/ViewModels/RemoteSourceViewModel.cs:273
- BarePragmaDisable Source/ChocolateyGui.Common.Windows/ViewModels/RemoteSourceViewModel.cs:465
- BarePragmaDisable Source/ChocolateyGui.Common.Windows/ViewModels/RemoteSourceViewModel.cs:474
- BarePragmaDisable Source/ChocolateyGui.Common.Windows/ViewModels/RemoteSourceViewModel.cs:542
- BarePragmaDisable Source/ChocolateyGui.Common.Windows/Views/ShellView.xaml.cs:137
- NuGet dependencies are not locked Source/ChocolateyGui.Common.Tests/ChocolateyGui.Common.Tests.csproj:12
- NuGet dependencies are not locked Source/ChocolateyGui.Common.Windows.Tests/ChocolateyGui.Common.Windows.Tests.csproj:12
- NuGet dependencies are not locked Source/ChocolateyGui.Common.Windows/ChocolateyGui.Common.Windows.csproj:74
- NuGet dependencies are not locked Source/ChocolateyGui.Common/ChocolateyGui.Common.csproj:87
- NuGet dependencies are not locked Source/ChocolateyGui.Tests/ChocolateyGui.Tests.csproj:12
- NuGet dependencies are not locked Source/ChocolateyGui.UITests/ChocolateyGui.UITests.csproj:9
- NuGet dependencies are not locked tools/packages.config:3
- Process-global static state: Bootstrapper Source/ChocolateyGuiCli/Bootstrapper.cs:21
- Process-global static state: LogSetup Source/ChocolateyGui.Common/Utilities/LogSetup.cs:13
- Process-global static state: Bootstrapper Source/ChocolateyGui.Common.Windows/Bootstrapper.cs:35
- Process-global static state: DesignMode Source/ChocolateyGui.Common.Windows/DesignMode.cs:13
- Process-global static state: CommandExecutionManager Source/ChocolateyGui.Common.Windows/Commands/CommandExecutionManager.cs:25
- Process-global static state: Internationalization Source/ChocolateyGui.Common.Windows/Startup/Internationalization.cs:18
- TodoComment Source/ChocolateyGui.Common.Windows/ViewModels/Items/PackageViewModel.cs:430
- TodoComment Source/ChocolateyGui.Common.Windows/Views/ShellView.xaml.cs:88
- TodoComment Source/ChocolateyGui.Common/Hacks.cs:19
- TodoComment Source/ChocolateyGui/App.xaml.cs:53
- TodoComment Source/ChocolateyGuiCli/Program.cs:46
- TodoComment Source/ChocolateyGui/App.xaml.cs:90
- REDACTED
- REDACTED
- REDACTED
- Stateful shared instance: TranslationSource Source/ChocolateyGui.Common/Utilities/TranslationSource.cs:17
- Stateful shared instance: CommandBindingsProvider Source/ChocolateyGui.Common.Windows/Commands/RoutedCommandMonitor.cs:161
- No assertions: AboutScreenTest Source/ChocolateyGui.UITests/ChocolateyGuiTests.cs:25
- No assertions: SettingsScreenTest Source/ChocolateyGui.UITests/ChocolateyGuiTests.cs:34
- CommentedOutCode Source/ChocolateyGui.Common.Windows/Commands/CommandExecutionManager.cs:193
- CommentedOutCode Source/ChocolateyGui.Common.Windows/Commands/CommandExecutionManager.cs:310
- ObsoleteWithCallers Source/ChocolateyGui.Common/ChocolateyConfigurationExtensions.cs:9
- ObsoleteWithCallers Source/ChocolateyGui.Common/ChocolateyConfigurationExtensions.cs:17
- REDACTED
- REDACTED
- Edited copy of a member (18 corresponding lines) Source/ChocolateyGui.Common/Services/ConfigService.cs:335
- Edited copy of a member (18 corresponding lines) Source/ChocolateyGui.Common.Windows/Services/DialogService.cs:44
- Edited copy of a member (4 corresponding lines) Source/ChocolateyGui.Common.Windows/Utilities/Converters/BooleanToVisibility.cs:42
- Edited copy of a member (4 corresponding lines) Source/ChocolateyGui.Common.Windows/Utilities/Converters/BooleanToVisibility.cs:26
- Disposable created and abandoned in the method that made it Source/ChocolateyGui.Common.Windows/Controls/FauxPowerShellConsole.cs:57
- Disposable created and abandoned in the method that made it Source/ChocolateyGui.Common.Windows/Services/PersistenceService.cs:38
- RemoteSourceViewModel.LoadPackages (cyclomatic 16) Source/ChocolateyGui.Common.Windows/ViewModels/RemoteSourceViewModel.cs:278
- Build failed
- RoutedCommandMonitor.TryExecuteRoutedCommandBinding (cognitive 19) Source/ChocolateyGui.Common.Windows/Commands/RoutedCommandMonitor.cs:94
- ChocolateyService.GetOutdatedPackages (cognitive 19) Source/ChocolateyGui.Common.Windows/Services/ChocolateyService.cs:111
- RemoteSourceViewModel.LoadPackages (cognitive 19) Source/ChocolateyGui.Common.Windows/ViewModels/RemoteSourceViewModel.cs:278
- PackageArgumentsService.DecryptPackageArgumentsFile (cognitive 16) Source/ChocolateyGui.Common.Windows/Services/PackageArgumentsService.cs:41
- REDACTED
- ClassTooLong: PackageViewModel Source/ChocolateyGui.Common.Windows/ViewModels/Items/PackageViewModel.cs
- TooManyMethods: ChocolateyService Source/ChocolateyGui.Common.Windows/Services/ChocolateyService.cs
- REDACTED
- REDACTED
- Edited copy of a member (51 corresponding lines) Source/ChocolateyGui/App.xaml.cs:34
- Edited copies of one member (5 members, 42+ corresponding lines) Source/ChocolateyGui.Common.Windows/ViewModels/Items/PackageViewModel.cs:530
- Edited copy of a member (21 corresponding lines) Source/ChocolateyGui.Common.Windows/Services/ChocolateyService.cs:408
- Edited copy of a member (19 corresponding lines) Source/ChocolateyGui.Common/Services/ConfigService.cs:201
- Edited copy of a member (22 corresponding lines) Source/ChocolateyGuiCli/Bootstrapper.cs:84
- Edited copies of one member (3 members, 17+ corresponding lines) Source/ChocolateyGui.Common/Commands/ConfigCommand.cs:103
- Edited copy of a member (24 corresponding lines) Source/ChocolateyGui.Common.Windows/Services/ChocolateyService.cs:459
- Edited copy of a member (26 corresponding lines) Source/ChocolateyGui.Common.Windows/ViewModels/SettingsViewModel.cs:517
- Edited copy of a member (14 corresponding lines) Source/ChocolateyGui.Common.Windows/ViewModels/SettingsViewModel.cs:367
- Duplicated block (49 lines × 2) Source/ChocolateyGui/App.xaml.cs:41
- Duplicated block (40 lines × 2) Source/ChocolateyGui.Common.Windows/Startup/ChocolateyGuiModule.cs:93
- Duplicated block (39 lines × 2) Source/ChocolateyGui.Common.Windows/Bootstrapper.cs:41
- Duplicated block (19 lines × 2) Source/ChocolateyGui.Common.Windows/ViewModels/SettingsViewModel.cs:651
- Duplicated block (14 lines × 2) Source/ChocolateyGui.Common.Windows/Bootstrapper.cs:123
- Duplicated block (10–11 lines × 2) Source/ChocolateyGui.Common.Windows/Startup/ChocolateyGuiModule.cs:136
- Duplicated block (7 lines × 3) Source/ChocolateyGui.Common.Windows/Services/ChocolateyService.cs:215
- Duplicated block (7–8 lines × 2) Source/ChocolateyGui.Common.Windows/Startup/ChocolateyGuiModule.cs:59
- Duplicated block (43 lines × 2) Source/ChocolateyGui.Common/Models/ChocolateyGuiSetting.cs:25
- Low cohesion: ShellView (LCOM4 5) Source/ChocolateyGui.Common.Windows/Views/ShellView.xaml.cs:33
- Coverage not measured — test suite did not build
- No deployment automation
- Outbound HTTP without resilience Source/ChocolateyGui.Common.Windows/Services/PackageIconService.cs:204
- Weak hash algorithm Source/ChocolateyGui.Common.Windows/Controls/FauxPowerShellConsole.cs:57
- Swallowed exception (empty catch) Source/ChocolateyGui.Common.Windows/Startup/Internationalization.cs:55
Minor — 46 finding(s)
- Orphaned file Source/ChocolateyGuiCli/Runner.cs:1
- Orphaned file Source/ChocolateyGui.Common.Windows/Services/DialogService.cs:1
- Orphaned file Source/ChocolateyGui.Common.Windows/Services/BundledThemeService.cs:1
- Orphaned file Source/ChocolateyGui.Common/Startup/AssemblyResolver.cs:1
- Orphaned file Source/ChocolateyGui.Common.Windows/Services/IDialogService.cs:1
- Orphaned file Source/ChocolateyGui.Common.Windows/Utilities/ChocolateyMessageBox.cs:1
- Orphaned file Source/ChocolateyGui.Common.Windows/Utilities/NotifyTaskCompletion.cs:1
- Orphaned file Source/ChocolateyGui.Common.Windows/Utilities/Extensions/MvvmExtensions.cs:1
- Orphaned file Source/ChocolateyGui.Common.Windows/Controls/InternetImage.xaml.cs:1
- Orphaned file Source/ChocolateyGui.Common.Windows/Theming/ThemeAssist.cs:1
- Orphaned file Source/ChocolateyGui.Common/Hacks.cs:1
- Orphaned file Source/ChocolateyGui.Common.Windows/Utilities/DataGridCustomSortBehavior.cs:1
- Orphaned file Source/ChocolateyGui.Common.Windows/Theming/ChocolateyBrushes.cs:1
- Orphaned file Source/ChocolateyGui.Common.Windows/Theming/ChocolateyColors.cs:1
- redundant comment Source/ChocolateyGui.Common.Windows/Properties/AssemblyInfo.cs:13
- redundant comment Source/ChocolateyGui.Common.Windows/Startup/ChocolateyGuiModule.cs:50
- redundant comment Source/ChocolateyGui.Common.Windows/Utilities/DataGridCustomSortBehavior.cs:64
- redundant comment Source/ChocolateyGui.Common/Properties/AssemblyInfo.cs:13
- redundant comment Source/ChocolateyGuiCli/Properties/AssemblyInfo.cs:13
- Commented-out code Source/ChocolateyGui.Common.Windows/Commands/CommandExecutionManager.cs:193
- Commented-out code Source/ChocolateyGui.Common.Windows/Commands/CommandExecutionManager.cs:196
- Commented-out code Source/ChocolateyGui.Common.Windows/Commands/CommandExecutionManager.cs:200
- Commented-out code Source/ChocolateyGui.Common.Windows/Controls/Dialogs/ChocolateyDialogController.cs:177
- ObsoleteWithoutCallers Source/ChocolateyGui.Common/Services/IChocolateyGuiCacheService.cs:17
- ObsoleteWithoutCallers Source/ChocolateyGui.Common/Services/IChocolateyService.cs:22
- ObsoleteWithoutCallers Source/ChocolateyGui.Common/Services/IChocolateyService.cs:42
- Duplicated predicate Source/ChocolateyGui.Common.Windows/Utilities/Converters/BooleanToVisibility.cs:43
- Duplicated predicate Source/ChocolateyGui/App.xaml.cs:70
- Duplicated predicate Source/ChocolateyGui/App.xaml.cs:79
- Fat interface: IChocolateyService (24 members) Source/ChocolateyGui.Common/Services/IChocolateyService.cs:16
- Fat interface: IPackageViewModel (38 members) Source/ChocolateyGui.Common/ViewModels/Items/IPackageViewModel.cs:14
- Off-boarding risk: anonymized user #1
- Further sole-owners (lower concentration)
- No ADRs found Source/ChocolateyGui/ChocolateyGui.csproj:4
- Projects may be oversized for their cohesion Source/ChocolateyGui.Common.Windows/ChocolateyGui.Common.Windows.csproj:1
- Orphaned files with no living knowledge
- REDACTED
- REDACTED
- REDACTED
- No ADRs
- No architecture diagram/doc
- Sleep-based test synchronization
- Console output used as the logging channel Source/ChocolateyGui.Common/Services/ConfigService.cs:187
- No dependency-update automation Source/ChocolateyGui.Common.Tests/ChocolateyGui.Common.Tests.csproj:12
- Irreversible deploy step: sync deletes the live copy REDACTED:27
- Not all async methods take a CancellationToken
Minor — 7 finding(s)
- Mock framework: Moq
- Mock framework: Moq
- Mock framework: Moq
- doc comments repeat the names Source/ChocolateyGui.Common/Commands/ICommand.cs:19
- doc comments repeat the names Source/ChocolateyGui.Common.Windows/Commands/DataContextCommandBinding.cs:34
- doc comments repeat the names Source/ChocolateyGui.UITests/Support/Feed/MockFeedPackage.cs:79
- Off the main sequence: ChocolateyGui.Common Source/ChocolateyGui.Common/ChocolateyGui.Common.csproj:1
Appendix B — Reproduction & audit trail
| Dimension | Tool | Version | Command | Findings | Raw output |
|---|---|---|---|---|---|
| D28 · Secrets (history) | gitleaks | — | gitleaks detect --no-banner --config /opt/gitleaks-rules/canine-gitleaks.toml --log-opts "--full-history --all --skip=0 --max-count=200" --report-format json --report-path /tmp/watchdog-gitleaks-3ce12a0dea294f899b0f785adaccaf02/history.json --exit-code 0 --source . | 0 | artifacts/raw/gitleaks-history.json |
| D28 · Secrets (history) | gitleaks | — | gitleaks detect --no-banner --config /opt/gitleaks-rules/canine-gitleaks.toml --log-opts "--full-history --all --skip=200 --max-count=800" --report-format json --report-path /tmp/watchdog-gitleaks-3ce12a0dea294f899b0f785adaccaf02/history-1.json --exit-code 0 --source . | 0 | artifacts/raw/gitleaks-history-1.json |
| D28 · Secrets (history) | gitleaks | — | gitleaks detect --no-banner --config /opt/gitleaks-rules/canine-gitleaks.toml --log-opts "--full-history --all --skip=1000 --max-count=955" --report-format json --report-path /tmp/watchdog-gitleaks-3ce12a0dea294f899b0f785adaccaf02/history-2.json --exit-code 0 --source . | 0 | artifacts/raw/gitleaks-history-2.json |
| D28 · Secrets (history) | gitleaks | — | gitleaks detect --no-git --no-banner --config /opt/gitleaks-rules/canine-gitleaks.toml --report-format json --report-path /tmp/watchdog-gitleaks-3ce12a0dea294f899b0f785adaccaf02/tree.json --exit-code 0 --source . | 0 | artifacts/raw/gitleaks-tree.json |
| D29 · Static Analysis (SAST) | semgrep | — | semgrep --config /opt/semgrep-rules/security-audit.yml --config /opt/semgrep-rules/owasp-top-ten.yml --config /opt/semgrep-rules/canine-sast.yml --json --quiet --timeout 10 --timeout-threshold 3 --metrics off --exclude *.arrow --exclude *.avro --exclude *.csv --exclude *.dat --exclude *.db --exclude *.feather --exclude *.geojson --exclude *.h5 --exclude *.hdf5 --exclude *.jsonl --exclude *.log --exclude *.ndjson --exclude *.npy --exclude *.npz --exclude *.orc --exclude *.parquet --exclude *.pickle --exclude *.pkl --exclude *.psv --exclude *.sqlite --exclude *.sqlite3 --exclude *.tfrecord --exclude *.tsv --exclude *.txt . | 21 | artifacts/raw/semgrep.json |
| D30 · Dependency Vulnerabilities | nuget | — | nuget: not applicable — nuget: the solution did not restore on the analyzer's .NET SDK (an SDK/target-framework/restore mismatch, common for an older codebase), so there was no restored dependency graph to scan | 0 | — |
| 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 . /tmp/codehealth-osv-sbom-3cfc9f9905b84c3699dd8a24e546bf40 | 0 | 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. semgrep could not parse 1 file(s) — `Source/ChocolateyGui/GlobalSuppressions.cs` — so the PII/GDPR sweep did not cover the unparsed regions of them; rows reported elsewhere in those files are real. | 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 . /tmp/codehealth-osv-sbom-3cfc9f9905b84c3699dd8a24e546bf40 | 0 | artifacts/raw/osv-scanner.json |
Appendix C — Personal-data map
Name — 1 field(s)
- InformationCommandConfiguration.FullName Source/ChocolateyGui.Common/Models/InformationCommandConfiguration.cs:21