Public report of Devolutions/UniGetUI, published 23 October 2026. It has the same score, grades and number of
findings as the full report. The details of security findings (where they are in the code, which known
vulnerabilities and which passwords or keys were found) are left out, so nobody can use them against the project.
Public
Executive reportMeasured under the Code Assurance Index, an open standard for code quality, using its published scoring rules (rubric version 2026.10.5). Watchdog signed this survey and filed it in the standard's public register, where anyone can look it up by its survey ID. Check this survey →
Signed and filed in the standard's public register, 23 October 2026, 07:44 UTC · Survey ID cd_bae84c4ed7d6495ca6ee84b231cf64bf
Devolutions/UniGetUI
Measured 23 October 2026, 07:29 UTC, at code version 2f1659f
A regression is a drop of 0.5 points or more in the score, or of 2.5 or more out of 10 in a dimension, since the last survey.
Boundary Type-Coupling is not measured: Bounded contexts not declared.
CAI scoreWeak
CriticalWeakAdequateStrongExemplary
No change since the last survey
The score is built from these lenses. Each lens grades one area of the code, such as how easy it is to change or how well it is protected. The weakest lens counts most, so one weak area pulls the score down instead of being averaged away.
A large codebase: 112,148 lines of product code in 91 projects, tests not counted · Estimated rebuild effort: about 2.2 person-years · Weakest lens: Security and Compliance, 24
Findings by how serious they are
120 critical794 serious162 minor
7 dimensions are left out of the score. For each one, Watchdog either couldn't measure it in this code, or found no evidence of the safeguard it looks for, such as a tested backup restore. They count neither for nor against the score, and Limitations lists each one with its reason.
This survey was produced by
Watchdog
Producer
Canine Development
Analyzer
Watchdog engine 1.0.0
Measured
23 October 2026, 07:29 UTC
A measurement, not a certificate. The Code Assurance Index records a number
together with the evidence it was worked out from, so anyone can recalculate it, but it doesn't certify or guarantee
the code. The standard was written by Canine Development, which also builds Watchdog. It is open to any tool that
implements it, and today Watchdog is the only one that does.
The score is deterministic, which means the same code always gets the same score. Watchdog works it out with tools that follow published rules, and an AI model never decides it, so anyone who applies the same rules to the same code gets the same number. How it is done is explained under Methodology ▸
75of 79 dimensions measured by tools. The other 4 are advisory notes from an AI model, which explain the code but don't count towards the score.
1047of 1076 findings point to an exact file and line, so you can open each one in the code. The other 29 concern the repository as a whole, such as missing documentation.
79dimensions across 6 lenses, read from 112,148 lines of product code in 91 projects.
Devolutions/UniGetUI scores 41 out of 100 and is rated Weak, while five of its six lenses score higher still: Architecture at 96, rated Exemplary, and Maturity at 64, Performance at 60, Production Readiness at 52 and Code Health at 51, all rated Adequate.
The score is lower than those five because the weakest lens counts most, and here that is Security and Compliance, which scores 24 and is rated Critical. Its Access Controls dimension scores 0 out of 10, and until that reaches 4, Security and Compliance can't be rated higher than Adequate. The first actions are to protect endpoints by default-deny: [Authorize] + role/policy authorization, or imperative guard methods (throw-on-violation) called from every handler and to resolve the 5 REDACTED finding(s) in Secrets (history), and if Security and Compliance rose to 70, the score would rise from 41 to about 56.
120 findings are critical: 52 in Static Analysis (SAST), 51 in Explicit Debt, five in Coupling, five in Secrets (history), four in Project dependency cycles, one in Change Coupling, one in Incompleteness & stubs and one in Web-Security Posture.
Watchdog couldn't measure 5 dimensions in this code, among them Code Coverage, Test Reliability and Dependency Hygiene, so they are left out of the score. The product code is 112,148 lines, which would take an estimated 2.2 person-years, around €330,000, to rebuild.
A lens is capped at Adequate while one of its dimensions scores below 4 out of 10, however well the rest of the lens does. That way a serious problem in one place always shows in the lens's rating.
How the score is built: what each lens counts forThe lenses don't count equally. The weakest lens counts most, the next weakest a little less, and so on, so a weak area pulls the score down instead of being averaged away. In the bar below, each part's width shows how much that lens counts and its colour shows its rating. Improving the widest part moves the score most, and as that lens improves, it counts for less, because another lens becomes the weakest.
If Security and Compliance rose from 24 to 70, the lowest score rated Strong, the score would rise from 41 to about 56.
Code composition: what the lines of code are
Business logic 38%Supporting code 28%Tests 35%
New since the last survey: 247 findings
These 247 critical or serious findings weren't in the previous survey, on 9 October 2026. The first 100 are listed here, and the findings file in the download package lists them all.
Watchdog compares every finding with the previous survey's. A finding that has only moved to another line in the same file counts as the same finding, so only new findings appear here. Advisory notes from the AI model are left out, because the model words them afresh in every survey.
Fixed since the last survey: 640 findings
These 640 critical or serious findings were in the previous survey, on 9 October 2026, and are gone from this one. The first 100 are listed here.
Cancellation propagation · Async method without CancellationToken: NavigateThenLoadBundleAsync src/UniGetUI.Avalonia/ViewModels/MainWindowViewModel.cs
Cancellation propagation · Async method without CancellationToken: ShowAboutDialog src/UniGetUI.Avalonia/ViewModels/MainWindowViewModel.cs
Cancellation propagation · Async method without CancellationToken: HandleNotificationActivation src/UniGetUI.Avalonia/ViewModels/MainWindowViewModel.cs
Cancellation propagation · Async method without CancellationToken: LoadPictureAsync src/UniGetUI.Avalonia/ViewModels/Pages/AboutPages/ContributorsViewModel.cs
Cancellation propagation · Async method without CancellationToken: LoadPictureAsync src/UniGetUI.Avalonia/ViewModels/Pages/AboutPages/TranslatorsViewModel.cs
Cancellation propagation · Async method without CancellationToken: Revert src/UniGetUI.Avalonia/ViewModels/Pages/LogPages/OperationHistoryRowViewModel.cs
Cancellation propagation · Async method without CancellationToken: ReRun src/UniGetUI.Avalonia/ViewModels/Pages/LogPages/OperationHistoryRowViewModel.cs
Cancellation propagation · Async method without CancellationToken: ViewLog src/UniGetUI.Avalonia/ViewModels/Pages/LogPages/OperationHistoryRowViewModel.cs
Cancellation propagation · Async method without CancellationToken: RetryAsAdmin src/UniGetUI.Avalonia/ViewModels/Pages/LogPages/OperationHistoryRowViewModel.cs
Cancellation propagation · Async method without CancellationToken: RetryInteractive src/UniGetUI.Avalonia/ViewModels/Pages/LogPages/OperationHistoryRowViewModel.cs
Cancellation propagation · Async method without CancellationToken: RetrySkipHash src/UniGetUI.Avalonia/ViewModels/Pages/LogPages/OperationHistoryRowViewModel.cs
Cancellation propagation · Async method without CancellationToken: PickBackupDirectory src/UniGetUI.Avalonia/ViewModels/Pages/SettingsPages/BackupViewModel.cs
Cancellation propagation · Async method without CancellationToken: DoLocalBackupStatic src/UniGetUI.Avalonia/ViewModels/Pages/SettingsPages/BackupViewModel.cs
Cancellation propagation · Async method without CancellationToken: UpdateGitHubLoginStatus src/UniGetUI.Avalonia/ViewModels/Pages/SettingsPages/BackupViewModel.cs
Cancellation propagation · Async method without CancellationToken: Login src/UniGetUI.Avalonia/ViewModels/Pages/SettingsPages/BackupViewModel.cs
Cancellation propagation · Async method without CancellationToken: DoCloudBackup src/UniGetUI.Avalonia/ViewModels/Pages/SettingsPages/BackupViewModel.cs
Cancellation propagation · Async method without CancellationToken: DoCloudBackupStatic src/UniGetUI.Avalonia/ViewModels/Pages/SettingsPages/BackupViewModel.cs
Cancellation propagation · Async method without CancellationToken: RestoreFromCloud src/UniGetUI.Avalonia/ViewModels/Pages/SettingsPages/BackupViewModel.cs
Cancellation propagation · Async method without CancellationToken: AskForBackupSelectionAsync src/UniGetUI.Avalonia/ViewModels/Pages/SettingsPages/BackupViewModel.cs
Cancellation propagation · Async method without CancellationToken: ShowTelemetryDialog src/UniGetUI.Avalonia/ViewModels/Pages/SettingsPages/GeneralViewModel.cs
Cancellation propagation · Async method without CancellationToken: ImportSettings src/UniGetUI.Avalonia/ViewModels/Pages/SettingsPages/GeneralViewModel.cs
Cancellation propagation · Async method without CancellationToken: ExportSettings src/UniGetUI.Avalonia/ViewModels/Pages/SettingsPages/GeneralViewModel.cs
Cancellation propagation · Async method without CancellationToken: ResetSettings src/UniGetUI.Avalonia/ViewModels/Pages/SettingsPages/GeneralViewModel.cs
Cancellation propagation · Async method without CancellationToken: SaveOptions src/UniGetUI.Avalonia/ViewModels/Pages/SettingsPages/InstallOptionsPanelViewModel.cs
Cancellation propagation · Async method without CancellationToken: ResetOptions src/UniGetUI.Avalonia/ViewModels/Pages/SettingsPages/InstallOptionsPanelViewModel.cs
Cancellation propagation · Async method without CancellationToken: DoLoadOptions src/UniGetUI.Avalonia/ViewModels/Pages/SettingsPages/InstallOptionsPanelViewModel.cs
Cancellation propagation · Async method without CancellationToken: SelectLocation src/UniGetUI.Avalonia/ViewModels/Pages/SettingsPages/InstallOptionsPanelViewModel.cs
Cancellation propagation · Async method without CancellationToken: ResetIconCache src/UniGetUI.Avalonia/ViewModels/Pages/SettingsPages/Interface_PViewModel.cs
Cancellation propagation · Async method without CancellationToken: LoadIconCacheSize src/UniGetUI.Avalonia/ViewModels/Pages/SettingsPages/Interface_PViewModel.cs
Cancellation propagation · Async method without CancellationToken: SaveCredentialsAsync src/UniGetUI.Avalonia/ViewModels/Pages/SettingsPages/InternetViewModel.cs
Cancellation propagation · Async method without CancellationToken: PickDownloadDirectory src/UniGetUI.Avalonia/ViewModels/Pages/SettingsPages/OperationsViewModel.cs
Cancellation propagation · Async method without CancellationToken: ReloadManager src/UniGetUI.Avalonia/ViewModels/Pages/SettingsPages/PackageManagerViewModel.cs
Cancellation propagation · Async method without CancellationToken: PickVcpkgRoot src/UniGetUI.Avalonia/ViewModels/Pages/SettingsPages/PackageManagerViewModel.cs
Cancellation propagation · Async method without CancellationToken: RunNow src/UniGetUI.Avalonia/ViewModels/Pages/SettingsPages/ScheduledTaskViewModel.cs
Cancellation propagation · Async method without CancellationToken: DoLoadSources src/UniGetUI.Avalonia/ViewModels/Pages/SettingsPages/SourceManagerCardViewModel.cs
Cancellation propagation · Async method without CancellationToken: ConfirmAddSource src/UniGetUI.Avalonia/ViewModels/Pages/SettingsPages/SourceManagerCardViewModel.cs
Cancellation propagation · Async method without CancellationToken: ShowInfoDialog src/UniGetUI.Avalonia/ViewModels/SoftwarePages/PackagesPageViewModel.cs
Cancellation propagation · Async method without CancellationToken: LoadPackages src/UniGetUI.Avalonia/ViewModels/SoftwarePages/PackagesPageViewModel.cs
Cancellation propagation · Async method without CancellationToken: Reload src/UniGetUI.Avalonia/ViewModels/SoftwarePages/PackagesPageViewModel.cs
Cancellation propagation · Async method without CancellationToken: LaunchInstall src/UniGetUI.Avalonia/ViewModels/SoftwarePages/PackagesPageViewModel.cs
Cancellation propagation · Async method without CancellationToken: _checkbox_Toggled src/UniGetUI.Avalonia/Views/Controls/Settings/SecureCheckboxCard.cs
Cancellation propagation · Async method without CancellationToken: SendReport_Click src/UniGetUI.Avalonia/Views/DialogPages/CrashReportWindow.axaml.cs
Cancellation propagation · Async method without CancellationToken: ShowAndLogFailureAsync src/UniGetUI.Avalonia/Views/DialogPages/ImmersiveDialog.cs
Cancellation propagation · Async method without CancellationToken: SelectDir_Click src/UniGetUI.Avalonia/Views/DialogPages/InstallOptionsControl.axaml.cs
Cancellation propagation · Async method without CancellationToken: Manual_Click src/UniGetUI.Avalonia/Views/DialogPages/InstallOptionsControl.axaml.cs
Cancellation propagation · Async method without CancellationToken: OnInstallClickedAsync src/UniGetUI.Avalonia/Views/DialogPages/MissingDependencyDialog.axaml.cs
Cancellation propagation · Async method without CancellationToken: RunInstallAsync src/UniGetUI.Avalonia/Views/DialogPages/MissingDependencyDialog.axaml.cs
Rebuild cost: about €330,000 · Estimate
Cost to rebuild
€110,000 to €550,000, for 1,777 to 5,781 hours of work, about 2.2 person-years for 1 to 5 engineers
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.7 at a score of 41. 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
Large: 112,148 lines of product code
Comment lines
The estimate prices 105,992 lines. Comment lines count towards the size of 112,148 lines but aren't priced as work.
How the estimate is made: Watchdog prices the hours a team would need to write this code again, at €60 to €95 an hour. Declarations and boilerplate are priced at a fast rate and logic at a slower one, and the logic is then multiplied by the difficulty of the problem and by the quality factor. The estimate can be about 30% off either way, and it moves most with the hourly rate and the difficulty.
Top priorities
The three actions that raise the score most for the work they take. The full ranked list is in the Roadmap.
1
Protect endpoints by default-deny: [Authorize] + role/policy authorization, or imperative guard methods (throw-on-violation) called from every handler.
Raises the score by about 9 points · Medium effort · Access Controls
2
Resolve the 5 REDACTED finding(s) in Secrets (history) — start with REDACTED (4), REDACTED.
Each conclusion below combines several dimensions into one point that no single dimension shows, and lists the measurements it rests on.
Where the investment is most exposed · Value at risk
This code would cost about €330,000 to build again, about 2.2 person-years of work. Its weakest lens is Security and Compliance, at 24 (Critical). Security and Compliance is about how well the product is protected, and how it handles personal data. Because the weakest lens counts most in the score, work on Security and Compliance also moves the score most.
Based on: the rebuild estimate · the Security and Compliance grade · how much each lens counts
What to do: Start with the Security and Compliance actions in Top priorities.
If you do one thing first · First action
Protect endpoints by default-deny: [Authorize] + role/policy authorization, or imperative guard methods (throw-on-violation) called from every handler. Of all the actions in this report, it raises the score most for the work it takes: about 9 points for medium effort. The next survey will show the change in the score.
Based on: the ranked actions in Top priorities, by score gain and effort
Architecture — module dependency graph
Project dependencies, layered top-to-bottom; arrows show direction. Any dashed red edge points upward or sideways — a layering smell or cycle. A clean layered graph has none.
Architecture: which parts of the code depend on which
The code is divided into modules, groups of code that each handle one part of the product, and a module depends on another when it uses code from it. The table lists the modules both down the side and across the top, in an order where each module should only use modules listed above it. A number in a cell means the module on that row uses the module in that column, and it counts the pairs of building blocks (types) that connect them. The one thing to look for is a mark above the diagonal line. It means two or more modules use each other in a loop (a dependency cycle), so none of them can be changed, tested or released on its own.
104 modules, with 405 dependencies between them. 4 loops run through 34 of the modules, marked above the diagonal.
The table shows the 40 modules with the most connections; 64 more are left out to keep it readable.
Which modules use which. The module on each row uses the module in each column, and the number counts the pairs of types that connect them. A cell above the diagonal is part of a loop.
Avalonia.ViewModels.Pages.LogPages uses Avalonia.Views.Controls, so a change to Avalonia.Views.Controls can break Avalonia.ViewModels.Pages.LogPages, while a change to Avalonia.ViewModels.Pages.LogPages can't break Avalonia.Views.Controls.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
6→15 Avalonia.ViewModels.Pages.LogPages uses PackageEngine.Interfacespart of a loop✕
Connections
1 pair of types, where a type in Avalonia.ViewModels.Pages.LogPages uses a type in PackageEngine.Interfaces.
Avalonia.ViewModels.Pages.LogPages uses PackageEngine.Interfaces, so a change to PackageEngine.Interfaces can break Avalonia.ViewModels.Pages.LogPages, while a change to Avalonia.ViewModels.Pages.LogPages can't break PackageEngine.Interfaces.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
6→39 Avalonia.ViewModels.Pages.LogPages uses Avalonia.ViewModelspart of a loop✕
Connections
3 pairs of types, where a type in Avalonia.ViewModels.Pages.LogPages uses a type in Avalonia.ViewModels.
Avalonia.ViewModels.Pages.LogPages uses Avalonia.ViewModels, so a change to Avalonia.ViewModels can break Avalonia.ViewModels.Pages.LogPages, while a change to Avalonia.ViewModels.Pages.LogPages can't break Avalonia.ViewModels.
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.
PackageEngine.Classes.Manager.Classes uses Interface.Enums, so a change to Interface.Enums can break PackageEngine.Classes.Manager.Classes, while a change to PackageEngine.Classes.Manager.Classes can't break Interface.Enums.
Position
Below the diagonal: PackageEngine.Classes.Manager.Classes uses a module listed above it, which is the healthy direction.
PackageEngine.Classes.Manager.Classes uses PackageEngine.Serializable, so a change to PackageEngine.Serializable can break PackageEngine.Classes.Manager.Classes, while a change to PackageEngine.Classes.Manager.Classes can't break PackageEngine.Serializable.
Position
Below the diagonal: PackageEngine.Classes.Manager.Classes uses a module listed above it, which is the healthy direction.
7→15 PackageEngine.Classes.Manager.Classes uses PackageEngine.Interfacespart of a loop✕
Connections
1 pair of types, where a type in PackageEngine.Classes.Manager.Classes uses a type in PackageEngine.Interfaces.
PackageEngine.Classes.Manager.Classes uses PackageEngine.Interfaces, so a change to PackageEngine.Interfaces can break PackageEngine.Classes.Manager.Classes, while a change to PackageEngine.Classes.Manager.Classes can't break PackageEngine.Interfaces.
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.
PackageEngine.Interfaces.ManagerProviders uses Core.IconEngine, so a change to Core.IconEngine can break PackageEngine.Interfaces.ManagerProviders, while a change to PackageEngine.Interfaces.ManagerProviders can't break Core.IconEngine.
Position
Below the diagonal: PackageEngine.Interfaces.ManagerProviders uses a module listed above it, which is the healthy direction.
PackageEngine.Interfaces.ManagerProviders uses PackageEngine.Enums, so a change to PackageEngine.Enums can break PackageEngine.Interfaces.ManagerProviders, while a change to PackageEngine.Interfaces.ManagerProviders can't break PackageEngine.Enums.
Position
Below the diagonal: PackageEngine.Interfaces.ManagerProviders uses a module listed above it, which is the healthy direction.
PackageEngine.Interfaces.ManagerProviders uses PackageEngine.Serializable, so a change to PackageEngine.Serializable can break PackageEngine.Interfaces.ManagerProviders, while a change to PackageEngine.Interfaces.ManagerProviders can't break PackageEngine.Serializable.
Position
Below the diagonal: PackageEngine.Interfaces.ManagerProviders uses a module listed above it, which is the healthy direction.
8→15 PackageEngine.Interfaces.ManagerProviders uses PackageEngine.Interfacespart of a loop✕
Connections
6 pairs of types, where a type in PackageEngine.Interfaces.ManagerProviders uses a type in PackageEngine.Interfaces.
PackageEngine.Interfaces.ManagerProviders uses PackageEngine.Interfaces, so a change to PackageEngine.Interfaces can break PackageEngine.Interfaces.ManagerProviders, while a change to PackageEngine.Interfaces.ManagerProviders can't break PackageEngine.Interfaces.
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.
PackageEngine.ManagerClasses.Classes uses PackageEngine.Enums, so a change to PackageEngine.Enums can break PackageEngine.ManagerClasses.Classes, while a change to PackageEngine.ManagerClasses.Classes can't break PackageEngine.Enums.
Position
Below the diagonal: PackageEngine.ManagerClasses.Classes uses a module listed above it, which is the healthy direction.
9→15 PackageEngine.ManagerClasses.Classes uses PackageEngine.Interfacespart of a loop✕
Connections
3 pairs of types, where a type in PackageEngine.ManagerClasses.Classes uses a type in PackageEngine.Interfaces.
PackageEngine.ManagerClasses.Classes uses PackageEngine.Interfaces, so a change to PackageEngine.Interfaces can break PackageEngine.ManagerClasses.Classes, while a change to PackageEngine.ManagerClasses.Classes can't break PackageEngine.Interfaces.
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.
PackageOperations uses PackageEngine.Enums, so a change to PackageEngine.Enums can break PackageOperations, while a change to PackageOperations can't break PackageEngine.Enums.
Position
Below the diagonal: PackageOperations uses a module listed above it, which is the healthy direction.
Avalonia.Views.Controls uses Avalonia.ViewModels.Pages.LogPages, so a change to Avalonia.ViewModels.Pages.LogPages can break Avalonia.Views.Controls, while a change to Avalonia.Views.Controls can't break Avalonia.ViewModels.Pages.LogPages.
Position
Below the diagonal: Avalonia.Views.Controls uses a module listed above it, which is the healthy direction.
11→39 Avalonia.Views.Controls uses Avalonia.ViewModelspart of a loop✕
Connections
4 pairs of types, where a type in Avalonia.Views.Controls uses a type in Avalonia.ViewModels.
Avalonia.Views.Controls uses Avalonia.ViewModels, so a change to Avalonia.ViewModels can break Avalonia.Views.Controls, while a change to Avalonia.Views.Controls can't break Avalonia.ViewModels.
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.
Avalonia.Views.DialogPages uses Interface.Enums, so a change to Interface.Enums can break Avalonia.Views.DialogPages, while a change to Avalonia.Views.DialogPages can't break Interface.Enums.
Position
Below the diagonal: Avalonia.Views.DialogPages uses a module listed above it, which is the healthy direction.
Avalonia.Views.DialogPages uses PackageEngine.Classes.Manager.Classes, so a change to PackageEngine.Classes.Manager.Classes can break Avalonia.Views.DialogPages, while a change to Avalonia.Views.DialogPages can't break PackageEngine.Classes.Manager.Classes.
Position
Below the diagonal: Avalonia.Views.DialogPages uses a module listed above it, which is the healthy direction.
Avalonia.Views.DialogPages uses PackageOperations, so a change to PackageOperations can break Avalonia.Views.DialogPages, while a change to Avalonia.Views.DialogPages can't break PackageOperations.
Position
Below the diagonal: Avalonia.Views.DialogPages uses a module listed above it, which is the healthy direction.
Avalonia.Views.DialogPages uses Avalonia.Views.Controls, so a change to Avalonia.Views.Controls can break Avalonia.Views.DialogPages, while a change to Avalonia.Views.DialogPages can't break Avalonia.Views.Controls.
Position
Below the diagonal: Avalonia.Views.DialogPages uses a module listed above it, which is the healthy direction.
12→39 Avalonia.Views.DialogPages uses Avalonia.ViewModelspart of a loop✕
Connections
1 pair of types, where a type in Avalonia.Views.DialogPages uses a type in Avalonia.ViewModels.
Avalonia.Views.DialogPages uses Avalonia.ViewModels, so a change to Avalonia.ViewModels can break Avalonia.Views.DialogPages, while a change to Avalonia.Views.DialogPages can't break Avalonia.ViewModels.
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.
PackageEngine.PackageClasses uses Core.Tools, so a change to Core.Tools can break PackageEngine.PackageClasses, while a change to PackageEngine.PackageClasses can't break Core.Tools.
Position
Below the diagonal: PackageEngine.PackageClasses uses a module listed above it, which is the healthy direction.
PackageEngine.PackageClasses uses Interface.Enums, so a change to Interface.Enums can break PackageEngine.PackageClasses, while a change to PackageEngine.PackageClasses can't break Interface.Enums.
Position
Below the diagonal: PackageEngine.PackageClasses uses a module listed above it, which is the healthy direction.
PackageEngine.PackageClasses uses PackageEngine.Serializable, so a change to PackageEngine.Serializable can break PackageEngine.PackageClasses, while a change to PackageEngine.PackageClasses can't break PackageEngine.Serializable.
Position
Below the diagonal: PackageEngine.PackageClasses uses a module listed above it, which is the healthy direction.
PackageEngine.PackageClasses uses Avalonia.Views.Controls, so a change to Avalonia.Views.Controls can break PackageEngine.PackageClasses, while a change to PackageEngine.PackageClasses can't break Avalonia.Views.Controls.
Position
Below the diagonal: PackageEngine.PackageClasses uses a module listed above it, which is the healthy direction.
13→15 PackageEngine.PackageClasses uses PackageEngine.Interfacespart of a loop✕
Connections
22 pairs of types, where a type in PackageEngine.PackageClasses uses a type in PackageEngine.Interfaces.
PackageEngine.PackageClasses uses PackageEngine.Interfaces, so a change to PackageEngine.Interfaces can break PackageEngine.PackageClasses, while a change to PackageEngine.PackageClasses can't break PackageEngine.Interfaces.
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.
13→16 PackageEngine.PackageClasses uses Avalonia.ViewModels.Pagespart of a loop✕
Connections
1 pair of types, where a type in PackageEngine.PackageClasses uses a type in Avalonia.ViewModels.Pages.
PackageEngine.PackageClasses uses Avalonia.ViewModels.Pages, so a change to Avalonia.ViewModels.Pages can break PackageEngine.PackageClasses, while a change to PackageEngine.PackageClasses can't break Avalonia.ViewModels.Pages.
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.
PackageEngine.ManagerClasses.Manager uses Interface.Enums, so a change to Interface.Enums can break PackageEngine.ManagerClasses.Manager, while a change to PackageEngine.ManagerClasses.Manager can't break Interface.Enums.
Position
Below the diagonal: PackageEngine.ManagerClasses.Manager uses a module listed above it, which is the healthy direction.
PackageEngine.ManagerClasses.Manager uses PackageEngine.Classes.Manager.Classes, so a change to PackageEngine.Classes.Manager.Classes can break PackageEngine.ManagerClasses.Manager, while a change to PackageEngine.ManagerClasses.Manager can't break PackageEngine.Classes.Manager.Classes.
Position
Below the diagonal: PackageEngine.ManagerClasses.Manager uses a module listed above it, which is the healthy direction.
PackageEngine.ManagerClasses.Manager uses PackageEngine.Interfaces.ManagerProviders, so a change to PackageEngine.Interfaces.ManagerProviders can break PackageEngine.ManagerClasses.Manager, while a change to PackageEngine.ManagerClasses.Manager can't break PackageEngine.Interfaces.ManagerProviders.
Position
Below the diagonal: PackageEngine.ManagerClasses.Manager uses a module listed above it, which is the healthy direction.
PackageEngine.ManagerClasses.Manager uses PackageEngine.ManagerClasses.Classes, so a change to PackageEngine.ManagerClasses.Classes can break PackageEngine.ManagerClasses.Manager, while a change to PackageEngine.ManagerClasses.Manager can't break PackageEngine.ManagerClasses.Classes.
Position
Below the diagonal: PackageEngine.ManagerClasses.Manager uses a module listed above it, which is the healthy direction.
PackageEngine.ManagerClasses.Manager uses PackageEngine.PackageClasses, so a change to PackageEngine.PackageClasses can break PackageEngine.ManagerClasses.Manager, while a change to PackageEngine.ManagerClasses.Manager can't break PackageEngine.PackageClasses.
Position
Below the diagonal: PackageEngine.ManagerClasses.Manager uses a module listed above it, which is the healthy direction.
14→15 PackageEngine.ManagerClasses.Manager uses PackageEngine.Interfacespart of a loop✕
Connections
4 pairs of types, where a type in PackageEngine.ManagerClasses.Manager uses a type in PackageEngine.Interfaces.
PackageEngine.ManagerClasses.Manager uses PackageEngine.Interfaces, so a change to PackageEngine.Interfaces can break PackageEngine.ManagerClasses.Manager, while a change to PackageEngine.ManagerClasses.Manager can't break PackageEngine.Interfaces.
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.
PackageEngine.Interfaces uses Core.Tools, so a change to Core.Tools can break PackageEngine.Interfaces, while a change to PackageEngine.Interfaces can't break Core.Tools.
Position
Below the diagonal: PackageEngine.Interfaces uses a module listed above it, which is the healthy direction.
PackageEngine.Interfaces uses Interface.Enums, so a change to Interface.Enums can break PackageEngine.Interfaces, while a change to PackageEngine.Interfaces can't break Interface.Enums.
Position
Below the diagonal: PackageEngine.Interfaces uses a module listed above it, which is the healthy direction.
PackageEngine.Interfaces uses PackageEngine.Serializable, so a change to PackageEngine.Serializable can break PackageEngine.Interfaces, while a change to PackageEngine.Interfaces can't break PackageEngine.Serializable.
Position
Below the diagonal: PackageEngine.Interfaces uses a module listed above it, which is the healthy direction.
PackageEngine.Interfaces uses PackageEngine.Classes.Manager.Classes, so a change to PackageEngine.Classes.Manager.Classes can break PackageEngine.Interfaces, while a change to PackageEngine.Interfaces can't break PackageEngine.Classes.Manager.Classes.
Position
Below the diagonal: PackageEngine.Interfaces uses a module listed above it, which is the healthy direction.
PackageEngine.Interfaces uses PackageEngine.Interfaces.ManagerProviders, so a change to PackageEngine.Interfaces.ManagerProviders can break PackageEngine.Interfaces, while a change to PackageEngine.Interfaces can't break PackageEngine.Interfaces.ManagerProviders.
Position
Below the diagonal: PackageEngine.Interfaces uses a module listed above it, which is the healthy direction.
PackageEngine.Interfaces uses PackageEngine.ManagerClasses.Classes, so a change to PackageEngine.ManagerClasses.Classes can break PackageEngine.Interfaces, while a change to PackageEngine.Interfaces can't break PackageEngine.ManagerClasses.Classes.
Position
Below the diagonal: PackageEngine.Interfaces uses a module listed above it, which is the healthy direction.
PackageEngine.Interfaces uses PackageEngine.ManagerClasses.Manager, so a change to PackageEngine.ManagerClasses.Manager can break PackageEngine.Interfaces, while a change to PackageEngine.Interfaces can't break PackageEngine.ManagerClasses.Manager.
Position
Below the diagonal: PackageEngine.Interfaces uses a module listed above it, which is the healthy direction.
Avalonia.ViewModels.Pages uses PackageEngine.Enums, so a change to PackageEngine.Enums can break Avalonia.ViewModels.Pages, while a change to Avalonia.ViewModels.Pages can't break PackageEngine.Enums.
Position
Below the diagonal: Avalonia.ViewModels.Pages uses a module listed above it, which is the healthy direction.
Avalonia.ViewModels.Pages uses PackageEngine.PackageClasses, so a change to PackageEngine.PackageClasses can break Avalonia.ViewModels.Pages, while a change to Avalonia.ViewModels.Pages can't break PackageEngine.PackageClasses.
Position
Below the diagonal: Avalonia.ViewModels.Pages uses a module listed above it, which is the healthy direction.
Avalonia.ViewModels.Pages uses PackageEngine.Interfaces, so a change to PackageEngine.Interfaces can break Avalonia.ViewModels.Pages, while a change to Avalonia.ViewModels.Pages can't break PackageEngine.Interfaces.
Position
Below the diagonal: Avalonia.ViewModels.Pages uses a module listed above it, which is the healthy direction.
16→39 Avalonia.ViewModels.Pages uses Avalonia.ViewModelspart of a loop✕
Connections
5 pairs of types, where a type in Avalonia.ViewModels.Pages uses a type in Avalonia.ViewModels.
Avalonia.ViewModels.Pages uses Avalonia.ViewModels, so a change to Avalonia.ViewModels can break Avalonia.ViewModels.Pages, while a change to Avalonia.ViewModels.Pages can't break Avalonia.ViewModels.
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.
Avalonia.ViewModels.Pages.SettingsPages uses PackageEngine.Interfaces, so a change to PackageEngine.Interfaces can break Avalonia.ViewModels.Pages.SettingsPages, while a change to Avalonia.ViewModels.Pages.SettingsPages can't break PackageEngine.Interfaces.
Position
Below the diagonal: Avalonia.ViewModels.Pages.SettingsPages uses a module listed above it, which is the healthy direction.
17→39 Avalonia.ViewModels.Pages.SettingsPages uses Avalonia.ViewModelspart of a loop✕
Connections
21 pairs of types, where a type in Avalonia.ViewModels.Pages.SettingsPages uses a type in Avalonia.ViewModels.
Avalonia.ViewModels.Pages.SettingsPages uses Avalonia.ViewModels, so a change to Avalonia.ViewModels can break Avalonia.ViewModels.Pages.SettingsPages, while a change to Avalonia.ViewModels.Pages.SettingsPages can't break Avalonia.ViewModels.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
17→40 Avalonia.ViewModels.Pages.SettingsPages uses Avalonia.Infrastructurepart of a loop✕
Connections
2 pairs of types, where a type in Avalonia.ViewModels.Pages.SettingsPages uses a type in Avalonia.Infrastructure.
Avalonia.ViewModels.Pages.SettingsPages uses Avalonia.Infrastructure, so a change to Avalonia.Infrastructure can break Avalonia.ViewModels.Pages.SettingsPages, while a change to Avalonia.ViewModels.Pages.SettingsPages can't break Avalonia.Infrastructure.
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.
Interface uses PackageEngine.Enums, so a change to PackageEngine.Enums can break Interface, while a change to Interface can't break PackageEngine.Enums.
Position
Below the diagonal: Interface uses a module listed above it, which is the healthy direction.
Interface uses PackageEngine.Serializable, so a change to PackageEngine.Serializable can break Interface, while a change to Interface can't break PackageEngine.Serializable.
Position
Below the diagonal: Interface uses a module listed above it, which is the healthy direction.
Interface uses PackageEngine.Interfaces, so a change to PackageEngine.Interfaces can break Interface, while a change to Interface can't break PackageEngine.Interfaces.
Position
Below the diagonal: Interface uses a module listed above it, which is the healthy direction.
PackageEngine.Classes.Manager uses Core.IconEngine, so a change to Core.IconEngine can break PackageEngine.Classes.Manager, while a change to PackageEngine.Classes.Manager can't break Core.IconEngine.
Position
Below the diagonal: PackageEngine.Classes.Manager uses a module listed above it, which is the healthy direction.
PackageEngine.Classes.Manager uses Interface.Enums, so a change to Interface.Enums can break PackageEngine.Classes.Manager, while a change to PackageEngine.Classes.Manager can't break Interface.Enums.
Position
Below the diagonal: PackageEngine.Classes.Manager uses a module listed above it, which is the healthy direction.
PackageEngine.Classes.Manager uses PackageEngine.Enums, so a change to PackageEngine.Enums can break PackageEngine.Classes.Manager, while a change to PackageEngine.Classes.Manager can't break PackageEngine.Enums.
Position
Below the diagonal: PackageEngine.Classes.Manager uses a module listed above it, which is the healthy direction.
PackageEngine.Classes.Manager uses PackageEngine.Serializable, so a change to PackageEngine.Serializable can break PackageEngine.Classes.Manager, while a change to PackageEngine.Classes.Manager can't break PackageEngine.Serializable.
Position
Below the diagonal: PackageEngine.Classes.Manager uses a module listed above it, which is the healthy direction.
PackageEngine.Classes.Manager uses PackageEngine.Classes.Manager.Classes, so a change to PackageEngine.Classes.Manager.Classes can break PackageEngine.Classes.Manager, while a change to PackageEngine.Classes.Manager can't break PackageEngine.Classes.Manager.Classes.
Position
Below the diagonal: PackageEngine.Classes.Manager uses a module listed above it, which is the healthy direction.
PackageEngine.Classes.Manager uses PackageEngine.Interfaces.ManagerProviders, so a change to PackageEngine.Interfaces.ManagerProviders can break PackageEngine.Classes.Manager, while a change to PackageEngine.Classes.Manager can't break PackageEngine.Interfaces.ManagerProviders.
Position
Below the diagonal: PackageEngine.Classes.Manager uses a module listed above it, which is the healthy direction.
PackageEngine.Classes.Manager uses PackageEngine.ManagerClasses.Classes, so a change to PackageEngine.ManagerClasses.Classes can break PackageEngine.Classes.Manager, while a change to PackageEngine.Classes.Manager can't break PackageEngine.ManagerClasses.Classes.
Position
Below the diagonal: PackageEngine.Classes.Manager uses a module listed above it, which is the healthy direction.
PackageEngine.Classes.Manager uses PackageEngine.ManagerClasses.Manager, so a change to PackageEngine.ManagerClasses.Manager can break PackageEngine.Classes.Manager, while a change to PackageEngine.Classes.Manager can't break PackageEngine.ManagerClasses.Manager.
Position
Below the diagonal: PackageEngine.Classes.Manager uses a module listed above it, which is the healthy direction.
PackageEngine.Classes.Manager uses PackageEngine.Interfaces, so a change to PackageEngine.Interfaces can break PackageEngine.Classes.Manager, while a change to PackageEngine.Classes.Manager can't break PackageEngine.Interfaces.
Position
Below the diagonal: PackageEngine.Classes.Manager uses a module listed above it, which is the healthy direction.
PackageEngine.Classes.Manager.BaseProviders uses Core.IconEngine, so a change to Core.IconEngine can break PackageEngine.Classes.Manager.BaseProviders, while a change to PackageEngine.Classes.Manager.BaseProviders can't break Core.IconEngine.
Position
Below the diagonal: PackageEngine.Classes.Manager.BaseProviders uses a module listed above it, which is the healthy direction.
PackageEngine.Classes.Manager.BaseProviders uses PackageEngine.Enums, so a change to PackageEngine.Enums can break PackageEngine.Classes.Manager.BaseProviders, while a change to PackageEngine.Classes.Manager.BaseProviders can't break PackageEngine.Enums.
Position
Below the diagonal: PackageEngine.Classes.Manager.BaseProviders uses a module listed above it, which is the healthy direction.
PackageEngine.Classes.Manager.BaseProviders uses PackageEngine.Serializable, so a change to PackageEngine.Serializable can break PackageEngine.Classes.Manager.BaseProviders, while a change to PackageEngine.Classes.Manager.BaseProviders can't break PackageEngine.Serializable.
Position
Below the diagonal: PackageEngine.Classes.Manager.BaseProviders uses a module listed above it, which is the healthy direction.
PackageEngine.Classes.Manager.BaseProviders uses PackageEngine.Interfaces.ManagerProviders, so a change to PackageEngine.Interfaces.ManagerProviders can break PackageEngine.Classes.Manager.BaseProviders, while a change to PackageEngine.Classes.Manager.BaseProviders can't break PackageEngine.Interfaces.ManagerProviders.
Position
Below the diagonal: PackageEngine.Classes.Manager.BaseProviders uses a module listed above it, which is the healthy direction.
PackageEngine.Classes.Manager.BaseProviders uses PackageEngine.Interfaces, so a change to PackageEngine.Interfaces can break PackageEngine.Classes.Manager.BaseProviders, while a change to PackageEngine.Classes.Manager.BaseProviders can't break PackageEngine.Interfaces.
Position
Below the diagonal: PackageEngine.Classes.Manager.BaseProviders uses a module listed above it, which is the healthy direction.
PackageEngine.Classes.Manager.Providers uses PackageEngine.Enums, so a change to PackageEngine.Enums can break PackageEngine.Classes.Manager.Providers, while a change to PackageEngine.Classes.Manager.Providers can't break PackageEngine.Enums.
Position
Below the diagonal: PackageEngine.Classes.Manager.Providers uses a module listed above it, which is the healthy direction.
PackageEngine.Classes.Manager.Providers uses PackageEngine.Interfaces.ManagerProviders, so a change to PackageEngine.Interfaces.ManagerProviders can break PackageEngine.Classes.Manager.Providers, while a change to PackageEngine.Classes.Manager.Providers can't break PackageEngine.Interfaces.ManagerProviders.
Position
Below the diagonal: PackageEngine.Classes.Manager.Providers uses a module listed above it, which is the healthy direction.
PackageEngine.Classes.Manager.Providers uses PackageEngine.Interfaces, so a change to PackageEngine.Interfaces can break PackageEngine.Classes.Manager.Providers, while a change to PackageEngine.Classes.Manager.Providers can't break PackageEngine.Interfaces.
Position
Below the diagonal: PackageEngine.Classes.Manager.Providers uses a module listed above it, which is the healthy direction.
Avalonia.Views.Pages uses Interface.Enums, so a change to Interface.Enums can break Avalonia.Views.Pages, while a change to Avalonia.Views.Pages can't break Interface.Enums.
Position
Below the diagonal: Avalonia.Views.Pages uses a module listed above it, which is the healthy direction.
Avalonia.Views.Pages uses PackageEngine.Enums, so a change to PackageEngine.Enums can break Avalonia.Views.Pages, while a change to Avalonia.Views.Pages can't break PackageEngine.Enums.
Position
Below the diagonal: Avalonia.Views.Pages uses a module listed above it, which is the healthy direction.
Avalonia.Views.Pages uses Avalonia.ViewModels.Pages.LogPages, so a change to Avalonia.ViewModels.Pages.LogPages can break Avalonia.Views.Pages, while a change to Avalonia.Views.Pages can't break Avalonia.ViewModels.Pages.LogPages.
Position
Below the diagonal: Avalonia.Views.Pages uses a module listed above it, which is the healthy direction.
Avalonia.Views.Pages uses Avalonia.Views.Controls, so a change to Avalonia.Views.Controls can break Avalonia.Views.Pages, while a change to Avalonia.Views.Pages can't break Avalonia.Views.Controls.
Position
Below the diagonal: Avalonia.Views.Pages uses a module listed above it, which is the healthy direction.
Avalonia.Views.Pages uses PackageEngine.Interfaces, so a change to PackageEngine.Interfaces can break Avalonia.Views.Pages, while a change to Avalonia.Views.Pages can't break PackageEngine.Interfaces.
Position
Below the diagonal: Avalonia.Views.Pages uses a module listed above it, which is the healthy direction.
Avalonia.Views.Pages uses Avalonia.ViewModels.Pages, so a change to Avalonia.ViewModels.Pages can break Avalonia.Views.Pages, while a change to Avalonia.Views.Pages can't break Avalonia.ViewModels.Pages.
Position
Below the diagonal: Avalonia.Views.Pages uses a module listed above it, which is the healthy direction.
Avalonia.Views.Pages uses PackageEngine.Classes.Manager, so a change to PackageEngine.Classes.Manager can break Avalonia.Views.Pages, while a change to Avalonia.Views.Pages can't break PackageEngine.Classes.Manager.
Position
Below the diagonal: Avalonia.Views.Pages uses a module listed above it, which is the healthy direction.
22→35 Avalonia.Views.Pages uses Avalonia.Viewspart of a loop✕
Connections
1 pair of types, where a type in Avalonia.Views.Pages uses a type in Avalonia.Views.
Avalonia.Views.Pages uses Avalonia.Views, so a change to Avalonia.Views can break Avalonia.Views.Pages, while a change to Avalonia.Views.Pages can't break Avalonia.Views.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
22→39 Avalonia.Views.Pages uses Avalonia.ViewModelspart of a loop✕
Connections
5 pairs of types, where a type in Avalonia.Views.Pages uses a type in Avalonia.ViewModels.
Avalonia.Views.Pages uses Avalonia.ViewModels, so a change to Avalonia.ViewModels can break Avalonia.Views.Pages, while a change to Avalonia.Views.Pages can't break Avalonia.ViewModels.
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.
PackageEngine.Managers.BunManager uses Core.IconEngine, so a change to Core.IconEngine can break PackageEngine.Managers.BunManager, while a change to PackageEngine.Managers.BunManager can't break Core.IconEngine.
Position
Below the diagonal: PackageEngine.Managers.BunManager uses a module listed above it, which is the healthy direction.
PackageEngine.Managers.BunManager uses PackageEngine.Enums, so a change to PackageEngine.Enums can break PackageEngine.Managers.BunManager, while a change to PackageEngine.Managers.BunManager can't break PackageEngine.Enums.
Position
Below the diagonal: PackageEngine.Managers.BunManager uses a module listed above it, which is the healthy direction.
PackageEngine.Managers.BunManager uses PackageEngine.Serializable, so a change to PackageEngine.Serializable can break PackageEngine.Managers.BunManager, while a change to PackageEngine.Managers.BunManager can't break PackageEngine.Serializable.
Position
Below the diagonal: PackageEngine.Managers.BunManager uses a module listed above it, which is the healthy direction.
PackageEngine.Managers.BunManager uses PackageEngine.PackageClasses, so a change to PackageEngine.PackageClasses can break PackageEngine.Managers.BunManager, while a change to PackageEngine.Managers.BunManager can't break PackageEngine.PackageClasses.
Position
Below the diagonal: PackageEngine.Managers.BunManager uses a module listed above it, which is the healthy direction.
PackageEngine.Managers.BunManager uses PackageEngine.ManagerClasses.Manager, so a change to PackageEngine.ManagerClasses.Manager can break PackageEngine.Managers.BunManager, while a change to PackageEngine.Managers.BunManager can't break PackageEngine.ManagerClasses.Manager.
Position
Below the diagonal: PackageEngine.Managers.BunManager uses a module listed above it, which is the healthy direction.
PackageEngine.Managers.BunManager uses PackageEngine.Interfaces, so a change to PackageEngine.Interfaces can break PackageEngine.Managers.BunManager, while a change to PackageEngine.Managers.BunManager can't break PackageEngine.Interfaces.
Position
Below the diagonal: PackageEngine.Managers.BunManager uses a module listed above it, which is the healthy direction.
PackageEngine.Managers.BunManager uses PackageEngine.Classes.Manager.BaseProviders, so a change to PackageEngine.Classes.Manager.BaseProviders can break PackageEngine.Managers.BunManager, while a change to PackageEngine.Managers.BunManager can't break PackageEngine.Classes.Manager.BaseProviders.
Position
Below the diagonal: PackageEngine.Managers.BunManager uses a module listed above it, which is the healthy direction.
PackageEngine.Managers.CargoManager uses Core.IconEngine, so a change to Core.IconEngine can break PackageEngine.Managers.CargoManager, while a change to PackageEngine.Managers.CargoManager can't break Core.IconEngine.
Position
Below the diagonal: PackageEngine.Managers.CargoManager uses a module listed above it, which is the healthy direction.
PackageEngine.Managers.CargoManager uses PackageEngine.Enums, so a change to PackageEngine.Enums can break PackageEngine.Managers.CargoManager, while a change to PackageEngine.Managers.CargoManager can't break PackageEngine.Enums.
Position
Below the diagonal: PackageEngine.Managers.CargoManager uses a module listed above it, which is the healthy direction.
PackageEngine.Managers.CargoManager uses PackageEngine.Serializable, so a change to PackageEngine.Serializable can break PackageEngine.Managers.CargoManager, while a change to PackageEngine.Managers.CargoManager can't break PackageEngine.Serializable.
Position
Below the diagonal: PackageEngine.Managers.CargoManager uses a module listed above it, which is the healthy direction.
PackageEngine.Managers.CargoManager uses PackageEngine.Interfaces.ManagerProviders, so a change to PackageEngine.Interfaces.ManagerProviders can break PackageEngine.Managers.CargoManager, while a change to PackageEngine.Managers.CargoManager can't break PackageEngine.Interfaces.ManagerProviders.
Position
Below the diagonal: PackageEngine.Managers.CargoManager uses a module listed above it, which is the healthy direction.
PackageEngine.Managers.CargoManager uses PackageEngine.PackageClasses, so a change to PackageEngine.PackageClasses can break PackageEngine.Managers.CargoManager, while a change to PackageEngine.Managers.CargoManager can't break PackageEngine.PackageClasses.
Position
Below the diagonal: PackageEngine.Managers.CargoManager uses a module listed above it, which is the healthy direction.
PackageEngine.Managers.CargoManager uses PackageEngine.ManagerClasses.Manager, so a change to PackageEngine.ManagerClasses.Manager can break PackageEngine.Managers.CargoManager, while a change to PackageEngine.Managers.CargoManager can't break PackageEngine.ManagerClasses.Manager.
Position
Below the diagonal: PackageEngine.Managers.CargoManager uses a module listed above it, which is the healthy direction.
PackageEngine.Managers.CargoManager uses PackageEngine.Interfaces, so a change to PackageEngine.Interfaces can break PackageEngine.Managers.CargoManager, while a change to PackageEngine.Managers.CargoManager can't break PackageEngine.Interfaces.
Position
Below the diagonal: PackageEngine.Managers.CargoManager uses a module listed above it, which is the healthy direction.
PackageEngine.Managers.CargoManager uses PackageEngine.Classes.Manager.BaseProviders, so a change to PackageEngine.Classes.Manager.BaseProviders can break PackageEngine.Managers.CargoManager, while a change to PackageEngine.Managers.CargoManager can't break PackageEngine.Classes.Manager.BaseProviders.
Position
Below the diagonal: PackageEngine.Managers.CargoManager uses a module listed above it, which is the healthy direction.
PackageEngine.Managers.FlatpakManager uses Core.IconEngine, so a change to Core.IconEngine can break PackageEngine.Managers.FlatpakManager, while a change to PackageEngine.Managers.FlatpakManager can't break Core.IconEngine.
Position
Below the diagonal: PackageEngine.Managers.FlatpakManager uses a module listed above it, which is the healthy direction.
PackageEngine.Managers.FlatpakManager uses PackageEngine.Enums, so a change to PackageEngine.Enums can break PackageEngine.Managers.FlatpakManager, while a change to PackageEngine.Managers.FlatpakManager can't break PackageEngine.Enums.
Position
Below the diagonal: PackageEngine.Managers.FlatpakManager uses a module listed above it, which is the healthy direction.
PackageEngine.Managers.FlatpakManager uses PackageEngine.Serializable, so a change to PackageEngine.Serializable can break PackageEngine.Managers.FlatpakManager, while a change to PackageEngine.Managers.FlatpakManager can't break PackageEngine.Serializable.
Position
Below the diagonal: PackageEngine.Managers.FlatpakManager uses a module listed above it, which is the healthy direction.
PackageEngine.Managers.FlatpakManager uses PackageEngine.PackageClasses, so a change to PackageEngine.PackageClasses can break PackageEngine.Managers.FlatpakManager, while a change to PackageEngine.Managers.FlatpakManager can't break PackageEngine.PackageClasses.
Position
Below the diagonal: PackageEngine.Managers.FlatpakManager uses a module listed above it, which is the healthy direction.
PackageEngine.Managers.FlatpakManager uses PackageEngine.ManagerClasses.Manager, so a change to PackageEngine.ManagerClasses.Manager can break PackageEngine.Managers.FlatpakManager, while a change to PackageEngine.Managers.FlatpakManager can't break PackageEngine.ManagerClasses.Manager.
Position
Below the diagonal: PackageEngine.Managers.FlatpakManager uses a module listed above it, which is the healthy direction.
PackageEngine.Managers.FlatpakManager uses PackageEngine.Interfaces, so a change to PackageEngine.Interfaces can break PackageEngine.Managers.FlatpakManager, while a change to PackageEngine.Managers.FlatpakManager can't break PackageEngine.Interfaces.
Position
Below the diagonal: PackageEngine.Managers.FlatpakManager uses a module listed above it, which is the healthy direction.
PackageEngine.Managers.FlatpakManager uses PackageEngine.Classes.Manager.BaseProviders, so a change to PackageEngine.Classes.Manager.BaseProviders can break PackageEngine.Managers.FlatpakManager, while a change to PackageEngine.Managers.FlatpakManager can't break PackageEngine.Classes.Manager.BaseProviders.
Position
Below the diagonal: PackageEngine.Managers.FlatpakManager uses a module listed above it, which is the healthy direction.
PackageEngine.Managers.FlatpakManager uses PackageEngine.Classes.Manager.Providers, so a change to PackageEngine.Classes.Manager.Providers can break PackageEngine.Managers.FlatpakManager, while a change to PackageEngine.Managers.FlatpakManager can't break PackageEngine.Classes.Manager.Providers.
Position
Below the diagonal: PackageEngine.Managers.FlatpakManager uses a module listed above it, which is the healthy direction.
PackageEngine.Managers.HomebrewManager uses Core.IconEngine, so a change to Core.IconEngine can break PackageEngine.Managers.HomebrewManager, while a change to PackageEngine.Managers.HomebrewManager can't break Core.IconEngine.
Position
Below the diagonal: PackageEngine.Managers.HomebrewManager uses a module listed above it, which is the healthy direction.
PackageEngine.Managers.HomebrewManager uses PackageEngine.Enums, so a change to PackageEngine.Enums can break PackageEngine.Managers.HomebrewManager, while a change to PackageEngine.Managers.HomebrewManager can't break PackageEngine.Enums.
Position
Below the diagonal: PackageEngine.Managers.HomebrewManager uses a module listed above it, which is the healthy direction.
PackageEngine.Managers.HomebrewManager uses PackageEngine.Serializable, so a change to PackageEngine.Serializable can break PackageEngine.Managers.HomebrewManager, while a change to PackageEngine.Managers.HomebrewManager can't break PackageEngine.Serializable.
Position
Below the diagonal: PackageEngine.Managers.HomebrewManager uses a module listed above it, which is the healthy direction.
PackageEngine.Managers.HomebrewManager uses PackageEngine.PackageClasses, so a change to PackageEngine.PackageClasses can break PackageEngine.Managers.HomebrewManager, while a change to PackageEngine.Managers.HomebrewManager can't break PackageEngine.PackageClasses.
Position
Below the diagonal: PackageEngine.Managers.HomebrewManager uses a module listed above it, which is the healthy direction.
PackageEngine.Managers.HomebrewManager uses PackageEngine.ManagerClasses.Manager, so a change to PackageEngine.ManagerClasses.Manager can break PackageEngine.Managers.HomebrewManager, while a change to PackageEngine.Managers.HomebrewManager can't break PackageEngine.ManagerClasses.Manager.
Position
Below the diagonal: PackageEngine.Managers.HomebrewManager uses a module listed above it, which is the healthy direction.
PackageEngine.Managers.HomebrewManager uses PackageEngine.Interfaces, so a change to PackageEngine.Interfaces can break PackageEngine.Managers.HomebrewManager, while a change to PackageEngine.Managers.HomebrewManager can't break PackageEngine.Interfaces.
Position
Below the diagonal: PackageEngine.Managers.HomebrewManager uses a module listed above it, which is the healthy direction.
PackageEngine.Managers.HomebrewManager uses PackageEngine.Classes.Manager, so a change to PackageEngine.Classes.Manager can break PackageEngine.Managers.HomebrewManager, while a change to PackageEngine.Managers.HomebrewManager can't break PackageEngine.Classes.Manager.
Position
Below the diagonal: PackageEngine.Managers.HomebrewManager uses a module listed above it, which is the healthy direction.
PackageEngine.Managers.HomebrewManager uses PackageEngine.Classes.Manager.BaseProviders, so a change to PackageEngine.Classes.Manager.BaseProviders can break PackageEngine.Managers.HomebrewManager, while a change to PackageEngine.Managers.HomebrewManager can't break PackageEngine.Classes.Manager.BaseProviders.
Position
Below the diagonal: PackageEngine.Managers.HomebrewManager uses a module listed above it, which is the healthy direction.
PackageEngine.Managers.HomebrewManager uses PackageEngine.Classes.Manager.Providers, so a change to PackageEngine.Classes.Manager.Providers can break PackageEngine.Managers.HomebrewManager, while a change to PackageEngine.Managers.HomebrewManager can't break PackageEngine.Classes.Manager.Providers.
Position
Below the diagonal: PackageEngine.Managers.HomebrewManager uses a module listed above it, which is the healthy direction.
PackageEngine.Managers.NpmManager uses Core.IconEngine, so a change to Core.IconEngine can break PackageEngine.Managers.NpmManager, while a change to PackageEngine.Managers.NpmManager can't break Core.IconEngine.
Position
Below the diagonal: PackageEngine.Managers.NpmManager uses a module listed above it, which is the healthy direction.
PackageEngine.Managers.NpmManager uses PackageEngine.Enums, so a change to PackageEngine.Enums can break PackageEngine.Managers.NpmManager, while a change to PackageEngine.Managers.NpmManager can't break PackageEngine.Enums.
Position
Below the diagonal: PackageEngine.Managers.NpmManager uses a module listed above it, which is the healthy direction.
PackageEngine.Managers.NpmManager uses PackageEngine.Serializable, so a change to PackageEngine.Serializable can break PackageEngine.Managers.NpmManager, while a change to PackageEngine.Managers.NpmManager can't break PackageEngine.Serializable.
Position
Below the diagonal: PackageEngine.Managers.NpmManager uses a module listed above it, which is the healthy direction.
PackageEngine.Managers.NpmManager uses PackageEngine.PackageClasses, so a change to PackageEngine.PackageClasses can break PackageEngine.Managers.NpmManager, while a change to PackageEngine.Managers.NpmManager can't break PackageEngine.PackageClasses.
Position
Below the diagonal: PackageEngine.Managers.NpmManager uses a module listed above it, which is the healthy direction.
PackageEngine.Managers.NpmManager uses PackageEngine.ManagerClasses.Manager, so a change to PackageEngine.ManagerClasses.Manager can break PackageEngine.Managers.NpmManager, while a change to PackageEngine.Managers.NpmManager can't break PackageEngine.ManagerClasses.Manager.
Position
Below the diagonal: PackageEngine.Managers.NpmManager uses a module listed above it, which is the healthy direction.
PackageEngine.Managers.NpmManager uses PackageEngine.Interfaces, so a change to PackageEngine.Interfaces can break PackageEngine.Managers.NpmManager, while a change to PackageEngine.Managers.NpmManager can't break PackageEngine.Interfaces.
Position
Below the diagonal: PackageEngine.Managers.NpmManager uses a module listed above it, which is the healthy direction.
PackageEngine.Managers.NpmManager uses PackageEngine.Classes.Manager.BaseProviders, so a change to PackageEngine.Classes.Manager.BaseProviders can break PackageEngine.Managers.NpmManager, while a change to PackageEngine.Managers.NpmManager can't break PackageEngine.Classes.Manager.BaseProviders.
Position
Below the diagonal: PackageEngine.Managers.NpmManager uses a module listed above it, which is the healthy direction.
PackageEngine.Managers.PipManager uses Core.IconEngine, so a change to Core.IconEngine can break PackageEngine.Managers.PipManager, while a change to PackageEngine.Managers.PipManager can't break Core.IconEngine.
Position
Below the diagonal: PackageEngine.Managers.PipManager uses a module listed above it, which is the healthy direction.
PackageEngine.Managers.PipManager uses Core.Tools, so a change to Core.Tools can break PackageEngine.Managers.PipManager, while a change to PackageEngine.Managers.PipManager can't break Core.Tools.
Position
Below the diagonal: PackageEngine.Managers.PipManager uses a module listed above it, which is the healthy direction.
PackageEngine.Managers.PipManager uses PackageEngine.Enums, so a change to PackageEngine.Enums can break PackageEngine.Managers.PipManager, while a change to PackageEngine.Managers.PipManager can't break PackageEngine.Enums.
Position
Below the diagonal: PackageEngine.Managers.PipManager uses a module listed above it, which is the healthy direction.
PackageEngine.Managers.PipManager uses PackageEngine.Serializable, so a change to PackageEngine.Serializable can break PackageEngine.Managers.PipManager, while a change to PackageEngine.Managers.PipManager can't break PackageEngine.Serializable.
Position
Below the diagonal: PackageEngine.Managers.PipManager uses a module listed above it, which is the healthy direction.
PackageEngine.Managers.PipManager uses PackageEngine.ManagerClasses.Classes, so a change to PackageEngine.ManagerClasses.Classes can break PackageEngine.Managers.PipManager, while a change to PackageEngine.Managers.PipManager can't break PackageEngine.ManagerClasses.Classes.
Position
Below the diagonal: PackageEngine.Managers.PipManager uses a module listed above it, which is the healthy direction.
PackageEngine.Managers.PipManager uses PackageEngine.PackageClasses, so a change to PackageEngine.PackageClasses can break PackageEngine.Managers.PipManager, while a change to PackageEngine.Managers.PipManager can't break PackageEngine.PackageClasses.
Position
Below the diagonal: PackageEngine.Managers.PipManager uses a module listed above it, which is the healthy direction.
PackageEngine.Managers.PipManager uses PackageEngine.ManagerClasses.Manager, so a change to PackageEngine.ManagerClasses.Manager can break PackageEngine.Managers.PipManager, while a change to PackageEngine.Managers.PipManager can't break PackageEngine.ManagerClasses.Manager.
Position
Below the diagonal: PackageEngine.Managers.PipManager uses a module listed above it, which is the healthy direction.
PackageEngine.Managers.PipManager uses PackageEngine.Interfaces, so a change to PackageEngine.Interfaces can break PackageEngine.Managers.PipManager, while a change to PackageEngine.Managers.PipManager can't break PackageEngine.Interfaces.
Position
Below the diagonal: PackageEngine.Managers.PipManager uses a module listed above it, which is the healthy direction.
PackageEngine.Managers.PipManager uses PackageEngine.Classes.Manager.BaseProviders, so a change to PackageEngine.Classes.Manager.BaseProviders can break PackageEngine.Managers.PipManager, while a change to PackageEngine.Managers.PipManager can't break PackageEngine.Classes.Manager.BaseProviders.
Position
Below the diagonal: PackageEngine.Managers.PipManager uses a module listed above it, which is the healthy direction.
PackageEngine.Managers.PowerShellManager uses Core.IconEngine, so a change to Core.IconEngine can break PackageEngine.Managers.PowerShellManager, while a change to PackageEngine.Managers.PowerShellManager can't break Core.IconEngine.
Position
Below the diagonal: PackageEngine.Managers.PowerShellManager uses a module listed above it, which is the healthy direction.
PackageEngine.Managers.PowerShellManager uses Core.Tools, so a change to Core.Tools can break PackageEngine.Managers.PowerShellManager, while a change to PackageEngine.Managers.PowerShellManager can't break Core.Tools.
Position
Below the diagonal: PackageEngine.Managers.PowerShellManager uses a module listed above it, which is the healthy direction.
PackageEngine.Managers.PowerShellManager uses PackageEngine.Enums, so a change to PackageEngine.Enums can break PackageEngine.Managers.PowerShellManager, while a change to PackageEngine.Managers.PowerShellManager can't break PackageEngine.Enums.
Position
Below the diagonal: PackageEngine.Managers.PowerShellManager uses a module listed above it, which is the healthy direction.
PackageEngine.Managers.PowerShellManager uses PackageEngine.Serializable, so a change to PackageEngine.Serializable can break PackageEngine.Managers.PowerShellManager, while a change to PackageEngine.Managers.PowerShellManager can't break PackageEngine.Serializable.
Position
Below the diagonal: PackageEngine.Managers.PowerShellManager uses a module listed above it, which is the healthy direction.
PackageEngine.Managers.PowerShellManager uses PackageEngine.ManagerClasses.Classes, so a change to PackageEngine.ManagerClasses.Classes can break PackageEngine.Managers.PowerShellManager, while a change to PackageEngine.Managers.PowerShellManager can't break PackageEngine.ManagerClasses.Classes.
Position
Below the diagonal: PackageEngine.Managers.PowerShellManager uses a module listed above it, which is the healthy direction.
PackageEngine.Managers.PowerShellManager uses PackageEngine.PackageClasses, so a change to PackageEngine.PackageClasses can break PackageEngine.Managers.PowerShellManager, while a change to PackageEngine.Managers.PowerShellManager can't break PackageEngine.PackageClasses.
Position
Below the diagonal: PackageEngine.Managers.PowerShellManager uses a module listed above it, which is the healthy direction.
PackageEngine.Managers.PowerShellManager uses PackageEngine.ManagerClasses.Manager, so a change to PackageEngine.ManagerClasses.Manager can break PackageEngine.Managers.PowerShellManager, while a change to PackageEngine.Managers.PowerShellManager can't break PackageEngine.ManagerClasses.Manager.
Position
Below the diagonal: PackageEngine.Managers.PowerShellManager uses a module listed above it, which is the healthy direction.
PackageEngine.Managers.PowerShellManager uses PackageEngine.Interfaces, so a change to PackageEngine.Interfaces can break PackageEngine.Managers.PowerShellManager, while a change to PackageEngine.Managers.PowerShellManager can't break PackageEngine.Interfaces.
Position
Below the diagonal: PackageEngine.Managers.PowerShellManager uses a module listed above it, which is the healthy direction.
PackageEngine.Managers.PowerShellManager uses PackageEngine.Classes.Manager.BaseProviders, so a change to PackageEngine.Classes.Manager.BaseProviders can break PackageEngine.Managers.PowerShellManager, while a change to PackageEngine.Managers.PowerShellManager can't break PackageEngine.Classes.Manager.BaseProviders.
Position
Below the diagonal: PackageEngine.Managers.PowerShellManager uses a module listed above it, which is the healthy direction.
PackageEngine.Managers.PowerShellManager uses PackageEngine.Classes.Manager.Providers, so a change to PackageEngine.Classes.Manager.Providers can break PackageEngine.Managers.PowerShellManager, while a change to PackageEngine.Managers.PowerShellManager can't break PackageEngine.Classes.Manager.Providers.
Position
Below the diagonal: PackageEngine.Managers.PowerShellManager uses a module listed above it, which is the healthy direction.
PackageEngine.Managers.ScoopManager uses Core.IconEngine, so a change to Core.IconEngine can break PackageEngine.Managers.ScoopManager, while a change to PackageEngine.Managers.ScoopManager can't break Core.IconEngine.
Position
Below the diagonal: PackageEngine.Managers.ScoopManager uses a module listed above it, which is the healthy direction.
PackageEngine.Managers.ScoopManager uses PackageEngine.Enums, so a change to PackageEngine.Enums can break PackageEngine.Managers.ScoopManager, while a change to PackageEngine.Managers.ScoopManager can't break PackageEngine.Enums.
Position
Below the diagonal: PackageEngine.Managers.ScoopManager uses a module listed above it, which is the healthy direction.
PackageEngine.Managers.ScoopManager uses PackageEngine.Serializable, so a change to PackageEngine.Serializable can break PackageEngine.Managers.ScoopManager, while a change to PackageEngine.Managers.ScoopManager can't break PackageEngine.Serializable.
Position
Below the diagonal: PackageEngine.Managers.ScoopManager uses a module listed above it, which is the healthy direction.
PackageEngine.Managers.ScoopManager uses PackageEngine.ManagerClasses.Classes, so a change to PackageEngine.ManagerClasses.Classes can break PackageEngine.Managers.ScoopManager, while a change to PackageEngine.Managers.ScoopManager can't break PackageEngine.ManagerClasses.Classes.
Position
Below the diagonal: PackageEngine.Managers.ScoopManager uses a module listed above it, which is the healthy direction.
PackageEngine.Managers.ScoopManager uses PackageEngine.PackageClasses, so a change to PackageEngine.PackageClasses can break PackageEngine.Managers.ScoopManager, while a change to PackageEngine.Managers.ScoopManager can't break PackageEngine.PackageClasses.
Position
Below the diagonal: PackageEngine.Managers.ScoopManager uses a module listed above it, which is the healthy direction.
PackageEngine.Managers.ScoopManager uses PackageEngine.ManagerClasses.Manager, so a change to PackageEngine.ManagerClasses.Manager can break PackageEngine.Managers.ScoopManager, while a change to PackageEngine.Managers.ScoopManager can't break PackageEngine.ManagerClasses.Manager.
Position
Below the diagonal: PackageEngine.Managers.ScoopManager uses a module listed above it, which is the healthy direction.
PackageEngine.Managers.ScoopManager uses PackageEngine.Interfaces, so a change to PackageEngine.Interfaces can break PackageEngine.Managers.ScoopManager, while a change to PackageEngine.Managers.ScoopManager can't break PackageEngine.Interfaces.
Position
Below the diagonal: PackageEngine.Managers.ScoopManager uses a module listed above it, which is the healthy direction.
PackageEngine.Managers.ScoopManager uses PackageEngine.Classes.Manager.BaseProviders, so a change to PackageEngine.Classes.Manager.BaseProviders can break PackageEngine.Managers.ScoopManager, while a change to PackageEngine.Managers.ScoopManager can't break PackageEngine.Classes.Manager.BaseProviders.
Position
Below the diagonal: PackageEngine.Managers.ScoopManager uses a module listed above it, which is the healthy direction.
PackageEngine.Managers.ScoopManager uses PackageEngine.Classes.Manager.Providers, so a change to PackageEngine.Classes.Manager.Providers can break PackageEngine.Managers.ScoopManager, while a change to PackageEngine.Managers.ScoopManager can't break PackageEngine.Classes.Manager.Providers.
Position
Below the diagonal: PackageEngine.Managers.ScoopManager uses a module listed above it, which is the healthy direction.
PackageEngine.Managers.VcpkgManager uses Core.IconEngine, so a change to Core.IconEngine can break PackageEngine.Managers.VcpkgManager, while a change to PackageEngine.Managers.VcpkgManager can't break Core.IconEngine.
Position
Below the diagonal: PackageEngine.Managers.VcpkgManager uses a module listed above it, which is the healthy direction.
PackageEngine.Managers.VcpkgManager uses PackageEngine.Enums, so a change to PackageEngine.Enums can break PackageEngine.Managers.VcpkgManager, while a change to PackageEngine.Managers.VcpkgManager can't break PackageEngine.Enums.
Position
Below the diagonal: PackageEngine.Managers.VcpkgManager uses a module listed above it, which is the healthy direction.
PackageEngine.Managers.VcpkgManager uses PackageEngine.Serializable, so a change to PackageEngine.Serializable can break PackageEngine.Managers.VcpkgManager, while a change to PackageEngine.Managers.VcpkgManager can't break PackageEngine.Serializable.
Position
Below the diagonal: PackageEngine.Managers.VcpkgManager uses a module listed above it, which is the healthy direction.
PackageEngine.Managers.VcpkgManager uses PackageEngine.Classes.Manager.Classes, so a change to PackageEngine.Classes.Manager.Classes can break PackageEngine.Managers.VcpkgManager, while a change to PackageEngine.Managers.VcpkgManager can't break PackageEngine.Classes.Manager.Classes.
Position
Below the diagonal: PackageEngine.Managers.VcpkgManager uses a module listed above it, which is the healthy direction.
PackageEngine.Managers.VcpkgManager uses PackageEngine.PackageClasses, so a change to PackageEngine.PackageClasses can break PackageEngine.Managers.VcpkgManager, while a change to PackageEngine.Managers.VcpkgManager can't break PackageEngine.PackageClasses.
Position
Below the diagonal: PackageEngine.Managers.VcpkgManager uses a module listed above it, which is the healthy direction.
PackageEngine.Managers.VcpkgManager uses PackageEngine.ManagerClasses.Manager, so a change to PackageEngine.ManagerClasses.Manager can break PackageEngine.Managers.VcpkgManager, while a change to PackageEngine.Managers.VcpkgManager can't break PackageEngine.ManagerClasses.Manager.
Position
Below the diagonal: PackageEngine.Managers.VcpkgManager uses a module listed above it, which is the healthy direction.
PackageEngine.Managers.VcpkgManager uses PackageEngine.Interfaces, so a change to PackageEngine.Interfaces can break PackageEngine.Managers.VcpkgManager, while a change to PackageEngine.Managers.VcpkgManager can't break PackageEngine.Interfaces.
Position
Below the diagonal: PackageEngine.Managers.VcpkgManager uses a module listed above it, which is the healthy direction.
PackageEngine.Managers.VcpkgManager uses PackageEngine.Classes.Manager, so a change to PackageEngine.Classes.Manager can break PackageEngine.Managers.VcpkgManager, while a change to PackageEngine.Managers.VcpkgManager can't break PackageEngine.Classes.Manager.
Position
Below the diagonal: PackageEngine.Managers.VcpkgManager uses a module listed above it, which is the healthy direction.
PackageEngine.Managers.VcpkgManager uses PackageEngine.Classes.Manager.BaseProviders, so a change to PackageEngine.Classes.Manager.BaseProviders can break PackageEngine.Managers.VcpkgManager, while a change to PackageEngine.Managers.VcpkgManager can't break PackageEngine.Classes.Manager.BaseProviders.
Position
Below the diagonal: PackageEngine.Managers.VcpkgManager uses a module listed above it, which is the healthy direction.
PackageEngine.Managers.VcpkgManager uses PackageEngine.Classes.Manager.Providers, so a change to PackageEngine.Classes.Manager.Providers can break PackageEngine.Managers.VcpkgManager, while a change to PackageEngine.Managers.VcpkgManager can't break PackageEngine.Classes.Manager.Providers.
Position
Below the diagonal: PackageEngine.Managers.VcpkgManager uses a module listed above it, which is the healthy direction.
PackageEngine.Managers.WingetManager uses Core.IconEngine, so a change to Core.IconEngine can break PackageEngine.Managers.WingetManager, while a change to PackageEngine.Managers.WingetManager can't break Core.IconEngine.
Position
Below the diagonal: PackageEngine.Managers.WingetManager uses a module listed above it, which is the healthy direction.
PackageEngine.Managers.WingetManager uses Interface.Enums, so a change to Interface.Enums can break PackageEngine.Managers.WingetManager, while a change to PackageEngine.Managers.WingetManager can't break Interface.Enums.
Position
Below the diagonal: PackageEngine.Managers.WingetManager uses a module listed above it, which is the healthy direction.
PackageEngine.Managers.WingetManager uses PackageEngine.Enums, so a change to PackageEngine.Enums can break PackageEngine.Managers.WingetManager, while a change to PackageEngine.Managers.WingetManager can't break PackageEngine.Enums.
Position
Below the diagonal: PackageEngine.Managers.WingetManager uses a module listed above it, which is the healthy direction.
PackageEngine.Managers.WingetManager uses PackageEngine.Serializable, so a change to PackageEngine.Serializable can break PackageEngine.Managers.WingetManager, while a change to PackageEngine.Managers.WingetManager can't break PackageEngine.Serializable.
Position
Below the diagonal: PackageEngine.Managers.WingetManager uses a module listed above it, which is the healthy direction.
PackageEngine.Managers.WingetManager uses PackageEngine.ManagerClasses.Classes, so a change to PackageEngine.ManagerClasses.Classes can break PackageEngine.Managers.WingetManager, while a change to PackageEngine.Managers.WingetManager can't break PackageEngine.ManagerClasses.Classes.
Position
Below the diagonal: PackageEngine.Managers.WingetManager uses a module listed above it, which is the healthy direction.
PackageEngine.Managers.WingetManager uses PackageEngine.PackageClasses, so a change to PackageEngine.PackageClasses can break PackageEngine.Managers.WingetManager, while a change to PackageEngine.Managers.WingetManager can't break PackageEngine.PackageClasses.
Position
Below the diagonal: PackageEngine.Managers.WingetManager uses a module listed above it, which is the healthy direction.
PackageEngine.Managers.WingetManager uses PackageEngine.ManagerClasses.Manager, so a change to PackageEngine.ManagerClasses.Manager can break PackageEngine.Managers.WingetManager, while a change to PackageEngine.Managers.WingetManager can't break PackageEngine.ManagerClasses.Manager.
Position
Below the diagonal: PackageEngine.Managers.WingetManager uses a module listed above it, which is the healthy direction.
PackageEngine.Managers.WingetManager uses PackageEngine.Interfaces, so a change to PackageEngine.Interfaces can break PackageEngine.Managers.WingetManager, while a change to PackageEngine.Managers.WingetManager can't break PackageEngine.Interfaces.
Position
Below the diagonal: PackageEngine.Managers.WingetManager uses a module listed above it, which is the healthy direction.
PackageEngine.Managers.WingetManager uses PackageEngine.Classes.Manager, so a change to PackageEngine.Classes.Manager can break PackageEngine.Managers.WingetManager, while a change to PackageEngine.Managers.WingetManager can't break PackageEngine.Classes.Manager.
Position
Below the diagonal: PackageEngine.Managers.WingetManager uses a module listed above it, which is the healthy direction.
PackageEngine.Managers.WingetManager uses PackageEngine.Classes.Manager.BaseProviders, so a change to PackageEngine.Classes.Manager.BaseProviders can break PackageEngine.Managers.WingetManager, while a change to PackageEngine.Managers.WingetManager can't break PackageEngine.Classes.Manager.BaseProviders.
Position
Below the diagonal: PackageEngine.Managers.WingetManager uses a module listed above it, which is the healthy direction.
PackageEngine.Managers.WingetManager uses PackageEngine.Classes.Manager.Providers, so a change to PackageEngine.Classes.Manager.Providers can break PackageEngine.Managers.WingetManager, while a change to PackageEngine.Managers.WingetManager can't break PackageEngine.Classes.Manager.Providers.
Position
Below the diagonal: PackageEngine.Managers.WingetManager uses a module listed above it, which is the healthy direction.
Tui.FakeData uses PackageEngine.Enums, so a change to PackageEngine.Enums can break Tui.FakeData, while a change to Tui.FakeData can't break PackageEngine.Enums.
Position
Below the diagonal: Tui.FakeData uses a module listed above it, which is the healthy direction.
Tui.FakeData uses PackageEngine.Serializable, so a change to PackageEngine.Serializable can break Tui.FakeData, while a change to Tui.FakeData can't break PackageEngine.Serializable.
Position
Below the diagonal: Tui.FakeData uses a module listed above it, which is the healthy direction.
Tui.FakeData uses PackageEngine.PackageClasses, so a change to PackageEngine.PackageClasses can break Tui.FakeData, while a change to Tui.FakeData can't break PackageEngine.PackageClasses.
Position
Below the diagonal: Tui.FakeData uses a module listed above it, which is the healthy direction.
Tui.FakeData uses PackageEngine.ManagerClasses.Manager, so a change to PackageEngine.ManagerClasses.Manager can break Tui.FakeData, while a change to Tui.FakeData can't break PackageEngine.ManagerClasses.Manager.
Position
Below the diagonal: Tui.FakeData uses a module listed above it, which is the healthy direction.
Tui.FakeData uses PackageEngine.Interfaces, so a change to PackageEngine.Interfaces can break Tui.FakeData, while a change to Tui.FakeData can't break PackageEngine.Interfaces.
Position
Below the diagonal: Tui.FakeData uses a module listed above it, which is the healthy direction.
Tui.FakeData uses PackageEngine.Classes.Manager.BaseProviders, so a change to PackageEngine.Classes.Manager.BaseProviders can break Tui.FakeData, while a change to Tui.FakeData can't break PackageEngine.Classes.Manager.BaseProviders.
Position
Below the diagonal: Tui.FakeData uses a module listed above it, which is the healthy direction.
Tui.FakeData uses PackageEngine.Classes.Manager.Providers, so a change to PackageEngine.Classes.Manager.Providers can break Tui.FakeData, while a change to Tui.FakeData can't break PackageEngine.Classes.Manager.Providers.
Position
Below the diagonal: Tui.FakeData uses a module listed above it, which is the healthy direction.
Tui.Infrastructure uses Interface.Enums, so a change to Interface.Enums can break Tui.Infrastructure, while a change to Tui.Infrastructure can't break Interface.Enums.
Position
Below the diagonal: Tui.Infrastructure uses a module listed above it, which is the healthy direction.
Tui.Infrastructure uses PackageEngine.Enums, so a change to PackageEngine.Enums can break Tui.Infrastructure, while a change to Tui.Infrastructure can't break PackageEngine.Enums.
Position
Below the diagonal: Tui.Infrastructure uses a module listed above it, which is the healthy direction.
Tui.Infrastructure uses PackageEngine.Serializable, so a change to PackageEngine.Serializable can break Tui.Infrastructure, while a change to Tui.Infrastructure can't break PackageEngine.Serializable.
Position
Below the diagonal: Tui.Infrastructure uses a module listed above it, which is the healthy direction.
Tui.Infrastructure uses PackageOperations, so a change to PackageOperations can break Tui.Infrastructure, while a change to Tui.Infrastructure can't break PackageOperations.
Position
Below the diagonal: Tui.Infrastructure uses a module listed above it, which is the healthy direction.
Tui.Infrastructure uses PackageEngine.Interfaces, so a change to PackageEngine.Interfaces can break Tui.Infrastructure, while a change to Tui.Infrastructure can't break PackageEngine.Interfaces.
Position
Below the diagonal: Tui.Infrastructure uses a module listed above it, which is the healthy direction.
Avalonia.Views uses PackageEngine.Enums, so a change to PackageEngine.Enums can break Avalonia.Views, while a change to Avalonia.Views can't break PackageEngine.Enums.
Position
Below the diagonal: Avalonia.Views uses a module listed above it, which is the healthy direction.
Avalonia.Views uses PackageEngine.Serializable, so a change to PackageEngine.Serializable can break Avalonia.Views, while a change to Avalonia.Views can't break PackageEngine.Serializable.
Position
Below the diagonal: Avalonia.Views uses a module listed above it, which is the healthy direction.
Avalonia.Views uses Avalonia.Views.Controls, so a change to Avalonia.Views.Controls can break Avalonia.Views, while a change to Avalonia.Views can't break Avalonia.Views.Controls.
Position
Below the diagonal: Avalonia.Views uses a module listed above it, which is the healthy direction.
Avalonia.Views uses Avalonia.Views.DialogPages, so a change to Avalonia.Views.DialogPages can break Avalonia.Views, while a change to Avalonia.Views can't break Avalonia.Views.DialogPages.
Position
Below the diagonal: Avalonia.Views uses a module listed above it, which is the healthy direction.
Avalonia.Views uses PackageEngine.Interfaces, so a change to PackageEngine.Interfaces can break Avalonia.Views, while a change to Avalonia.Views can't break PackageEngine.Interfaces.
Position
Below the diagonal: Avalonia.Views uses a module listed above it, which is the healthy direction.
Avalonia.Views uses Avalonia.Views.Pages, so a change to Avalonia.Views.Pages can break Avalonia.Views, while a change to Avalonia.Views can't break Avalonia.Views.Pages.
Position
Below the diagonal: Avalonia.Views uses a module listed above it, which is the healthy direction.
35→39 Avalonia.Views uses Avalonia.ViewModelspart of a loop✕
Connections
6 pairs of types, where a type in Avalonia.Views uses a type in Avalonia.ViewModels.
Avalonia.Views uses Avalonia.ViewModels, so a change to Avalonia.ViewModels can break Avalonia.Views, while a change to Avalonia.Views can't break Avalonia.ViewModels.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
35→40 Avalonia.Views uses Avalonia.Infrastructurepart of a loop✕
Connections
1 pair of types, where a type in Avalonia.Views uses a type in Avalonia.Infrastructure.
Avalonia.Views uses Avalonia.Infrastructure, so a change to Avalonia.Infrastructure can break Avalonia.Views, while a change to Avalonia.Views can't break Avalonia.Infrastructure.
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.
Avalonia.Views.Pages.SettingsPages uses Avalonia.Views.Controls, so a change to Avalonia.Views.Controls can break Avalonia.Views.Pages.SettingsPages, while a change to Avalonia.Views.Pages.SettingsPages can't break Avalonia.Views.Controls.
Position
Below the diagonal: Avalonia.Views.Pages.SettingsPages uses a module listed above it, which is the healthy direction.
Avalonia.Views.Pages.SettingsPages uses PackageEngine.Interfaces, so a change to PackageEngine.Interfaces can break Avalonia.Views.Pages.SettingsPages, while a change to Avalonia.Views.Pages.SettingsPages can't break PackageEngine.Interfaces.
Position
Below the diagonal: Avalonia.Views.Pages.SettingsPages uses a module listed above it, which is the healthy direction.
Avalonia.Views.Pages.SettingsPages uses Avalonia.ViewModels.Pages.SettingsPages, so a change to Avalonia.ViewModels.Pages.SettingsPages can break Avalonia.Views.Pages.SettingsPages, while a change to Avalonia.Views.Pages.SettingsPages can't break Avalonia.ViewModels.Pages.SettingsPages.
Position
Below the diagonal: Avalonia.Views.Pages.SettingsPages uses a module listed above it, which is the healthy direction.
Avalonia.Views.Pages.SettingsPages uses Avalonia.Views.Pages, so a change to Avalonia.Views.Pages can break Avalonia.Views.Pages.SettingsPages, while a change to Avalonia.Views.Pages.SettingsPages can't break Avalonia.Views.Pages.
Position
Below the diagonal: Avalonia.Views.Pages.SettingsPages uses a module listed above it, which is the healthy direction.
36→39 Avalonia.Views.Pages.SettingsPages uses Avalonia.ViewModelspart of a loop✕
Connections
1 pair of types, where a type in Avalonia.Views.Pages.SettingsPages uses a type in Avalonia.ViewModels.
Avalonia.Views.Pages.SettingsPages uses Avalonia.ViewModels, so a change to Avalonia.ViewModels can break Avalonia.Views.Pages.SettingsPages, while a change to Avalonia.Views.Pages.SettingsPages can't break Avalonia.ViewModels.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
36→40 Avalonia.Views.Pages.SettingsPages uses Avalonia.Infrastructurepart of a loop✕
Connections
1 pair of types, where a type in Avalonia.Views.Pages.SettingsPages uses a type in Avalonia.Infrastructure.
Avalonia.Views.Pages.SettingsPages uses Avalonia.Infrastructure, so a change to Avalonia.Infrastructure can break Avalonia.Views.Pages.SettingsPages, while a change to Avalonia.Views.Pages.SettingsPages can't break Avalonia.Infrastructure.
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.
PackageEngine uses PackageEngine.Interfaces, so a change to PackageEngine.Interfaces can break PackageEngine, while a change to PackageEngine can't break PackageEngine.Interfaces.
Position
Below the diagonal: PackageEngine uses a module listed above it, which is the healthy direction.
PackageEngine uses PackageEngine.Managers.BunManager, so a change to PackageEngine.Managers.BunManager can break PackageEngine, while a change to PackageEngine can't break PackageEngine.Managers.BunManager.
Position
Below the diagonal: PackageEngine uses a module listed above it, which is the healthy direction.
PackageEngine uses PackageEngine.Managers.CargoManager, so a change to PackageEngine.Managers.CargoManager can break PackageEngine, while a change to PackageEngine can't break PackageEngine.Managers.CargoManager.
Position
Below the diagonal: PackageEngine uses a module listed above it, which is the healthy direction.
PackageEngine uses PackageEngine.Managers.FlatpakManager, so a change to PackageEngine.Managers.FlatpakManager can break PackageEngine, while a change to PackageEngine can't break PackageEngine.Managers.FlatpakManager.
Position
Below the diagonal: PackageEngine uses a module listed above it, which is the healthy direction.
PackageEngine uses PackageEngine.Managers.HomebrewManager, so a change to PackageEngine.Managers.HomebrewManager can break PackageEngine, while a change to PackageEngine can't break PackageEngine.Managers.HomebrewManager.
Position
Below the diagonal: PackageEngine uses a module listed above it, which is the healthy direction.
PackageEngine uses PackageEngine.Managers.NpmManager, so a change to PackageEngine.Managers.NpmManager can break PackageEngine, while a change to PackageEngine can't break PackageEngine.Managers.NpmManager.
Position
Below the diagonal: PackageEngine uses a module listed above it, which is the healthy direction.
PackageEngine uses PackageEngine.Managers.PipManager, so a change to PackageEngine.Managers.PipManager can break PackageEngine, while a change to PackageEngine can't break PackageEngine.Managers.PipManager.
Position
Below the diagonal: PackageEngine uses a module listed above it, which is the healthy direction.
PackageEngine uses PackageEngine.Managers.VcpkgManager, so a change to PackageEngine.Managers.VcpkgManager can break PackageEngine, while a change to PackageEngine can't break PackageEngine.Managers.VcpkgManager.
Position
Below the diagonal: PackageEngine uses a module listed above it, which is the healthy direction.
Tui.Views.Pages uses PackageEngine.Enums, so a change to PackageEngine.Enums can break Tui.Views.Pages, while a change to Tui.Views.Pages can't break PackageEngine.Enums.
Position
Below the diagonal: Tui.Views.Pages uses a module listed above it, which is the healthy direction.
Tui.Views.Pages uses PackageOperations, so a change to PackageOperations can break Tui.Views.Pages, while a change to Tui.Views.Pages can't break PackageOperations.
Position
Below the diagonal: Tui.Views.Pages uses a module listed above it, which is the healthy direction.
Tui.Views.Pages uses PackageEngine.Interfaces, so a change to PackageEngine.Interfaces can break Tui.Views.Pages, while a change to Tui.Views.Pages can't break PackageEngine.Interfaces.
Position
Below the diagonal: Tui.Views.Pages uses a module listed above it, which is the healthy direction.
Tui.Views.Pages uses Tui.Infrastructure, so a change to Tui.Infrastructure can break Tui.Views.Pages, while a change to Tui.Views.Pages can't break Tui.Infrastructure.
Position
Below the diagonal: Tui.Views.Pages uses a module listed above it, which is the healthy direction.
Avalonia.ViewModels uses PackageEngine.Enums, so a change to PackageEngine.Enums can break Avalonia.ViewModels, while a change to Avalonia.ViewModels can't break PackageEngine.Enums.
Position
Below the diagonal: Avalonia.ViewModels uses a module listed above it, which is the healthy direction.
Avalonia.ViewModels uses PackageEngine.Serializable, so a change to PackageEngine.Serializable can break Avalonia.ViewModels, while a change to Avalonia.ViewModels can't break PackageEngine.Serializable.
Position
Below the diagonal: Avalonia.ViewModels uses a module listed above it, which is the healthy direction.
Avalonia.ViewModels uses PackageOperations, so a change to PackageOperations can break Avalonia.ViewModels, while a change to Avalonia.ViewModels can't break PackageOperations.
Position
Below the diagonal: Avalonia.ViewModels uses a module listed above it, which is the healthy direction.
Avalonia.ViewModels uses Avalonia.Views.Controls, so a change to Avalonia.Views.Controls can break Avalonia.ViewModels, while a change to Avalonia.ViewModels can't break Avalonia.Views.Controls.
Position
Below the diagonal: Avalonia.ViewModels uses a module listed above it, which is the healthy direction.
Avalonia.ViewModels uses PackageEngine.Interfaces, so a change to PackageEngine.Interfaces can break Avalonia.ViewModels, while a change to Avalonia.ViewModels can't break PackageEngine.Interfaces.
Position
Below the diagonal: Avalonia.ViewModels uses a module listed above it, which is the healthy direction.
Avalonia.ViewModels uses Avalonia.ViewModels.Pages, so a change to Avalonia.ViewModels.Pages can break Avalonia.ViewModels, while a change to Avalonia.ViewModels can't break Avalonia.ViewModels.Pages.
Position
Below the diagonal: Avalonia.ViewModels uses a module listed above it, which is the healthy direction.
Avalonia.ViewModels uses Avalonia.Views.Pages, so a change to Avalonia.Views.Pages can break Avalonia.ViewModels, while a change to Avalonia.ViewModels can't break Avalonia.Views.Pages.
Position
Below the diagonal: Avalonia.ViewModels uses a module listed above it, which is the healthy direction.
Avalonia.ViewModels uses Avalonia.Views, so a change to Avalonia.Views can break Avalonia.ViewModels, while a change to Avalonia.ViewModels can't break Avalonia.Views.
Position
Below the diagonal: Avalonia.ViewModels uses a module listed above it, which is the healthy direction.
Avalonia.ViewModels uses Avalonia.Views.Pages.SettingsPages, so a change to Avalonia.Views.Pages.SettingsPages can break Avalonia.ViewModels, while a change to Avalonia.ViewModels can't break Avalonia.Views.Pages.SettingsPages.
Position
Below the diagonal: Avalonia.ViewModels uses a module listed above it, which is the healthy direction.
39→40 Avalonia.ViewModels uses Avalonia.Infrastructurepart of a loop✕
Connections
1 pair of types, where a type in Avalonia.ViewModels uses a type in Avalonia.Infrastructure.
Avalonia.ViewModels uses Avalonia.Infrastructure, so a change to Avalonia.Infrastructure can break Avalonia.ViewModels, while a change to Avalonia.ViewModels can't break Avalonia.Infrastructure.
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.
Avalonia.Infrastructure uses Core.Tools, so a change to Core.Tools can break Avalonia.Infrastructure, while a change to Avalonia.Infrastructure can't break Core.Tools.
Position
Below the diagonal: Avalonia.Infrastructure uses a module listed above it, which is the healthy direction.
Avalonia.Infrastructure uses PackageEngine.Enums, so a change to PackageEngine.Enums can break Avalonia.Infrastructure, while a change to Avalonia.Infrastructure can't break PackageEngine.Enums.
Position
Below the diagonal: Avalonia.Infrastructure uses a module listed above it, which is the healthy direction.
Avalonia.Infrastructure uses PackageEngine.Classes.Manager.Classes, so a change to PackageEngine.Classes.Manager.Classes can break Avalonia.Infrastructure, while a change to Avalonia.Infrastructure can't break PackageEngine.Classes.Manager.Classes.
Position
Below the diagonal: Avalonia.Infrastructure uses a module listed above it, which is the healthy direction.
Avalonia.Infrastructure uses PackageOperations, so a change to PackageOperations can break Avalonia.Infrastructure, while a change to Avalonia.Infrastructure can't break PackageOperations.
Position
Below the diagonal: Avalonia.Infrastructure uses a module listed above it, which is the healthy direction.
Avalonia.Infrastructure uses PackageEngine.Interfaces, so a change to PackageEngine.Interfaces can break Avalonia.Infrastructure, while a change to Avalonia.Infrastructure can't break PackageEngine.Interfaces.
Position
Below the diagonal: Avalonia.Infrastructure uses a module listed above it, which is the healthy direction.
Avalonia.Infrastructure uses Interface, so a change to Interface can break Avalonia.Infrastructure, while a change to Avalonia.Infrastructure can't break Interface.
Position
Below the diagonal: Avalonia.Infrastructure uses a module listed above it, which is the healthy direction.
Avalonia.Infrastructure uses Avalonia.Views, so a change to Avalonia.Views can break Avalonia.Infrastructure, while a change to Avalonia.Infrastructure can't break Avalonia.Views.
Position
Below the diagonal: Avalonia.Infrastructure uses a module listed above it, which is the healthy direction.
Avalonia.Infrastructure uses Avalonia.ViewModels, so a change to Avalonia.ViewModels can break Avalonia.Infrastructure, while a change to Avalonia.Infrastructure can't break Avalonia.ViewModels.
Position
Below the diagonal: Avalonia.Infrastructure uses a module listed above it, which is the healthy direction.
At a glance — Code Health · 51% · Adequate · gated by X4 ·
Findings mapped to OWASP categories; the specific CVEs/secrets are in the Security dimension cards below and findings.md (redacted only on the public version of this report).
OWASP category
Findings
Severity
A05:2025 — Injection
59
High / Critical
A03:2025 — Software Supply Chain Failures
9
Medium
A07:2025 — Authentication Failures
6
High / Critical
Roadmap
First, enforce strict access controls by applying default-deny authorization policies or imperative guards to all endpoints. Next, secure sensitive data at rest using encryption and manage keys in a vault, while simultaneously removing permissive TLS certificate validation to ensure proper chain verification. Finally, resolve the identified secrets in historical files and address supply-chain workflow permissions to harden the development pipeline.
Ranked by impact ÷ effort. "Helps" is the estimated gain on the 0–100 health score.
Do this
Helps
Effort
Dimension
Protect endpoints by default-deny: [Authorize] + role/policy authorization, or imperative guard methods (throw-on-violation) called from every handler.
Encrypt sensitive data at rest (ASP.NET Core Data Protection / column encryption) and manage keys in a vault. Skip if delegated to infra (Postgres TDE, KMS, etc.).
Stop accepting every TLS certificate: remove the always-true validation callback so the platform verifies the chain, hostname and expiry. If one self-signed certificate must be trusted, pin it by public key or thumbprint on the single handler that needs it and reject all others — never process-wide.
Resolve the 6 REDACTED finding(s) charged to Static Analysis (SAST) — the other 36 are reported here at file:line but scored by D36 (supply-chain provenance), which charges them once.
Every finding carries one of four grades. Three say how serious it is. The fourth says this
survey could not settle it — and it is a grade, not a gap.
Critical — 120
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.
Serious — 794
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.
Minor — 162
Recorded, with no effect on how the codebase functions.
Present so the survey is complete, not because it needs doing.
Could not be resolved — 7
Something this survey could not settle
from the outside, and which could be critical or serious. Either a control was required and no
positive evidence of it exists in the repository — a backup job that nothing shows was ever restored from proves
nothing about restores — or our own analysis could not run over that part of the tree. This is not a clean
result. These are excluded from the score rather than awarded a pass, so the number on the cover neither
rewards nor penalises them: if you act on this survey without resolving them, you carry that risk yourself. Each
one is named under Limitations.
Methodology & how to trust this report
Watchdog is a deep, periodic assessment — run each sprint, monthly, or quarterly, taking the time to go wider and deeper than a quick check and surfacing in one coherent report what you'd otherwise piece together from a dozen separate tools. It scores deterministically: the same commit yields the same score, every run. 75 of 79 evaluated dimensions are computed purely by tools and static analysis (confidence 1.0); 4 documentation/naming judgement(s) are LLM-assisted and labelled advisory. Overall confidence is 0.9 — the weighted average across measured dimensions; it falls as more of the score leans on LLM-assisted judgement and rises when it's fully tool-backed.
Every figure here is one of three kinds, and we label which: ✓ Measured — a deterministic fact (LoC, complexity, coverage); ~ Modeled — an estimate from a stated model (cost, effort, value-at-risk), always a range with its assumptions, never a precise fact; ◐ Advisory — an LLM prose judgement. We never present a modelled estimate as if it were measured. Perfect or absent scores carry their provenance too (ADR-0011): ✓ Tool-verified means the property itself was measured across the surface; ○ Nothing flagged means the probes came back clean — a claim bounded by what a repository can show; ⊘ Not evidenced means a working control (a tested restore, an automated rollback) showed no positive evidence — absence of evidence is not evidence of a control, so it's excluded from the score rather than awarded a spurious 10; ◐ Sampled · advisory marks an LLM verdict over a bounded sample — advisory, never a deterministic measurement.
What we checked — 79 dimensions across the health lenses
Each chip is a dimension scored from real signals across architecture, testing, dependencies, security & compliance, documentation, git-history and code quality — in one coherent pass. A surface report typically covers a handful.
How to trust any code-health report — three questions
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, 1047 of 1076 do; the remainder are repo-wide signals — a dimension-level measurement, not a single line. (Every path in this report is repo-relative by construction: paths are normalized at the producer and the report is rejected if any rooted path leaks through.)
Is there a tool behind the number? Every score below names the method that produced it — Roslyn, git, a scanner, or (for a handful of documentation/naming dimensions) an LLM labelled sampled · advisory — not a narrative.
Does re-running give the same result? Run it again on the same commit and the score — and this report, byte for byte — is identical. A report whose numbers move between runs is describing the run, not the code.
This report answers yes to all three. That's the bar to hold any assessment to.
Tools & methods
The actual versions used this run (captured at analysis time) — re-run on the same commit for the identical score.
Method
Backs
Version
Evaluator
Roslyn static analysis
Complexity, cohesion, coupling, dead code, API surface, layering
What ran differently this time — a tool absent, degraded, or that fell back to an estimate. Named openly, not folded silently into the scores. A degraded run also records its exact cause in diagnostics.md.
D8 Code Coverage — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Coverage NOT MEASURED: the analyzer environment could not build/run the test suite (a target framework / SDK band or targeting pack the analyzer image doesn't carry). This is OUR limitation, not a defect in the repo — coverage is excluded from the score rather than counted as a near-zero. We track the analyzer-image gap so it can be closed; in the meantime, no coverage collector was found in your CI either, so there is no existing report to hand us — add a collector to your test run and commit (or publish into the working tree) its Cobertura/OpenCover/lcov output, and real coverage will be read. You can widen what we reach: optional: add a coverage collector to your test run and commit (or publish into the working tree) its Cobertura/OpenCover/lcov output, and the real number is read on the next scan.
D11 Test Reliability — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Test reliability not included — no test tier completed within its budget.
D12 Dependency Hygiene — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. `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 — Watchdog measured this, but not all of it. What it did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. 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 'src/UniGetUI.Core.Data/UniGetUI.Core.Data.csproj' with message: PackageReference System.Text.Encoding.CodePages will not be pruned. This package is automatically available and does not need to be referenced explicitly. Remove the PackageReference item.
D18 Solution Shape — measured, with a gap in what it reached — Watchdog measured this, but not all of it. What it did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. `dotnet build` reported 1 error(s), and the diagnostics it printed were: MSB3073: The command ""/root/.nuget/packages/microsoft.windows.cswinrt/2.2.0/cswinrt.exe" @"src/WindowsPackageManager.Interop/obj/arm64/Debug/net10.0-windows10.0.26100.0/Generated Files/CsWinRT/cswinrt.rsp"" exited with code 126.. None of them is a .NET compiler diagnostic, which is the only signal this check reads as "the code does not compile", so the failure is recorded as a build-environment gap rather than a code defect. The usual causes are a project that targets a platform this run cannot build (a Windows-only target framework on a Linux worker) or a build step that shells out to a tool the image does not carry. Solution Shape is scored on structure and is NOT capped. Semantic analysis is independent of this build and covers every project that loaded — but a project whose restore did not complete has no resolved references, so treat its results as absent rather than clean. ★ The reach of that test, stated so this classification can be checked rather than taken on trust: it reads the C# (CS), Visual Basic (BC) and F# (FS) compiler series, and treats SDK, NuGet-restore and MSBuild codes (NETSDK, NU, MSB) as evidence that the build did not run rather than that the code is broken — read the diagnostics named above and judge for yourself. You can widen what we reach: if this build is meant to run off its own platform, without host tooling we do not carry, the diagnostics named above are what stopped it. If it is deliberately platform-bound — a Windows-only desktop product, say — there is nothing to do here: the note records our reach, not a defect in your build.
D18 Solution Shape — measured, with a gap in what it reached — Watchdog measured this, but not all of it. What it did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. A scan loads every live solution in the repository into one workspace. Every score, lens, and finding here reflects the projects of `src/UniGetUI.Windows.slnx`; 1 further solution(s) found in this tree (`InstallerExtras/MsiCreator/MsiInstallerWrapper.sln`) could not be added to it — their project list could not be read, or none of their projects opened — so their code is not represented in the headline. (This is a count of the solutions discovery found and could not show to be covered by the analyzed ones — not a claim about how many solution files the repository contains.) If one of them is an archived or vendored tree, declaring it — `.gitattributes` (`path/** linguist-vendored`) or `.editorconfig` (`[path/**] generated_code = true`) — excludes it from discovery the same way generated code is. You can widen what we reach: if one of these solutions is live code, check that it opens on its own (`dotnet build <solution>`); if it is archived or vendored, declare it so.
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.
D23 Boundary Type-Coupling — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Large codebase (112,046 production LoC in the .NET projects) with no declared bounded contexts — cross-boundary type coupling is unassessed Bounded contexts cannot be inferred from a codebase that is not physically organised by them (D-321), so with none declared there are no boundaries for the coupling pass to measure across. You can widen what we reach: name this codebase's bounded contexts (≥2 module groups, e.g. per subsystem) so cross-boundary type coupling can 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"]`.
D32 Data Compliance (PII/GDPR) — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. `scripts/CargoSmoke/Program.cs`, `src/Shared/SharedPreUiCommandDispatcher.cs`, `src/Shared/StartupBundleArguments.cs`, `src/UniGetUI.Avalonia/App.axaml.cs`, `src/UniGetUI.Avalonia/CrashHandler.cs`, … (+91 more) 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.
D39 IL Efficiency — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. IL NOT MEASURED: the analyzer's own build of this repository failed for an ENVIRONMENT reason (exit 1) — MSBuild's engine or the CLR gave up, or our image does not carry the SDK band/targeting pack this repository needs. This is OUR limitation, not a defect in the repo, and it is not a statement that this repository fails to build. D18 owns the question of whether this repository builds; it was not answered here.
AXB1 Runtime evidence locked — no reproducible boot — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Subject: a native UI project (src/UniGetUI.Avalonia/App.axaml). 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. Watchdog then boots it in an isolated sandbox and gathers real runtime evidence — you change nothing in your pipeline (no CI step, no SDK).
C2 Access Controls — measured, with a gap in what it reached — Watchdog measured this, but not all of it. What it did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. 127 further occurrence(s) are not listed individually; the score already reflects all 167.
GD1 Unfinished & placeholder code — measured, with a gap in what it reached — Watchdog measured this, but not all of it. What it did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. 13 further occurrence(s) are not listed individually; the score already reflects all 53.
IC1 Incompleteness & stubs — measured, with a gap in what it reached — Watchdog measured this, but not all of it. What it did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. 34 further occurrence(s) are not listed individually; the score already reflects all 74.
PF3 Async & latency hygiene — measured, with a gap in what it reached — Watchdog measured this, but not all of it. What it did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. 6 further occurrence(s) are not listed individually; the score already reflects all 46.
X1 Async correctness — measured, with a gap in what it reached — Watchdog measured this, but not all of it. What it did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. 48 further occurrence(s) are not listed individually; the score already reflects all 88.
X2 Cancellation propagation — measured, with a gap in what it reached — Watchdog measured this, but not all of it. What it did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. 570 further occurrence(s) are not listed individually; the score already reflects all 610.
X3 Exception handling — measured, with a gap in what it reached — Watchdog measured this, but not all of it. What it did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. 17 further occurrence(s) are not listed individually; the score already reflects all 57.
X7 Silent fallback defaults — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. 10 further occurrence(s) are not listed individually; the score already reflects all 50.
Repo exclusion declarations: 2 pattern(s) declared (.gitattributes linguist-generated/vendored, .editorconfig generated_code) excluded 0 source file(s) from code-quality scoring. Declarations are the repo's own visible statement that a tree is machine-written or vendored — auditable in any diff, honored by GitHub the same way.
Limitations & what we did not check
Watchdog assesses the repository exactly as committed, and only the repository. By design it does not reach outside the source tree: the live cloud account, the running CI/CD pipeline, the host's branch-protection and approval rules, the production configuration, or a restore actually exercised against a backup are all out of scope. That boundary is a feature, not a gap — a repo-relative, deterministic scan re-runs identically on any commit and every finding opens at a real file and line, where a live audit can neither be reproduced nor traced. The visible consequence is that controls which leave no in-repo evidence are reported as "not evidenced" and excluded from the score rather than awarded a number a static scan cannot justify.
Per-dimension blind spots
For each dimension that was measured, what a static, repo-only scan structurally cannot see — the honest edge of the measurement, not a failure of it.
D1 Cyclomatic Complexity: Cyclomatic complexity counts branches statically — it cannot tell an essential decision tree from accidental tangle, nor see complexity that lives in data or configuration (large switch-case token tables, DSL lexers/parsers, data-as-code rule tables) rather than control flow: a tokenizer's many single-character cases read as high complexity though each branch is trivial.
D2 Cognitive Complexity: Cognitive-complexity heuristics approximate how hard code is to follow; genuine domain difficulty and well-named intent that eases reading are not captured.
D3 God Classes: "God class" is sized by members and responsibilities visible in the type — a deliberately broad facade over a coherent subsystem can read the same as an accidental grab-bag. For front-end JS the file-length check is cohesion-aware (a single-responsibility module — one class/IIFE — earns a 3× threshold), but cohesion is approximated from top-level declarations, not true dependency structure.
D4 Code Duplication: Duplication is token-similarity — an in-process token-stream comparison over sliding windows, with type-aware normalization — so it finds copy-paste, not semantic duplication expressed differently. Committed machine-written code (scaffolded migrations, designer/codegen output, protobuf/OpenAPI stubs, model snapshots) is EXCLUDED — its repetition is the tool's, not the team's — so the score reflects hand-written duplication only.
D5 Coupling: Coupling is measured between projects/assemblies — runtime coupling through DI, reflection, messaging or shared databases is invisible to a static reference graph.
D6 Cohesion (LCOM4): LCOM4 cohesion is syntactic — it infers connectivity from which methods touch which fields/methods by name, not from real runtime behaviour or intent.
D9 Test Distribution: The test-pyramid shape is inferred from project/folder naming and references, with a single test host bucketed per-file by its path tier and content signals — a suite that names tiers unconventionally and gives no per-file signal can still be mis-bucketed.
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 REDACTED Scanning: REDACTED 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 is judged by an LLM over a bounded sample of docs — it reads what is written, not whether the docs match the running system, and it is advisory, not a measurement. Its critique rows are drawn from a closed category vocabulary and each row means the same thing in every run, so two scans can be compared row by row; the SET that fires is still a sample, and does not repeat exactly. Measured on one frozen input, six scans at one engine SHA: 2-5 critique rows per scan, 8 distinct rows across the six, 3 of those 8 seen in only one scan. So a D19 row is evidence about the documentation, but a COUNT of D19 rows is not a quantity — never read a change in it as an improvement or a regression.
D20 ADR Quality: ADR quality is an LLM read of the decision records present — it cannot know about decisions made and never recorded, and its verdict is sampled and advisory.
D21 Naming Consistency: Naming quality is an LLM judgement over a bounded sample — it assesses clarity/consistency of the names it sees, not domain-correctness, and is advisory.
D24 Comment Value: Comment value (WHY vs WHAT) is an LLM judgement over a bounded sample — it is advisory and cannot weigh a comment against the precise code change it was written to explain.
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").
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.
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.
C4 Data Retention: This control is scored from in-repo evidence only — its real-world effectiveness, exercised only at runtime, is outside a static scan.
M4 Documentation accuracy: Onboarding quality is an LLM read of the docs/setup present — it cannot run the onboarding or measure how long a real new joiner takes; the verdict is sampled and advisory.
P4 Deployment & Rollback: Approval/branch-protection rules live in repository settings the scan cannot see — only their in-repo evidence (config files, workflows) is checked, so a control enforced purely in the host's settings reads as "not evidenced".
P5 DR & Backup: Backup/restore and disaster-recovery readiness is judged from in-repo evidence — a config that exists is not a tested restore, so the absence of positive evidence is reported as "not evidenced", never scored as present.
P6 Release Hygiene: Rollback/observability controls are inferred from repo artefacts (pipelines, dashboards-as-code) — controls configured in external tooling, with no in-repo trace, cannot be credited.
The LLM boundary
LLM-set scores this run (4): D19, D21, D24, M4 (model: Local LLM). For these, a model reads a bounded sample and sets the numeric score; each names its own sample and method on its card. They are sampled and advisory by design: they vary at the margins between runs and are never a deterministic measurement. Every other score in this report is tool-computed at confidence 1.0.
What it measures: How tangled the control flow is — methods with many branches are hard to test and change.
Method: Cyclomatic complexity per method (1 + decision points), computed exhaustively across production source; test projects separated by convention. Deterministic.
78 method(s) exceeded the cyclomatic complexity threshold of 15; the worst was PolicyEditorSessionViewModel.SaveCoreAsync at 53. A further 25 method(s) were over the threshold but excluded as flat dispatchers (a long switch/match over independent cases: many branches, almost no nesting), the largest being Settings.ResolveKey at 136 — they are counted neither in the figure above nor in this dimension's score. 16 files carry no cyclomatic complexity row at all for this reason — every one of their over-threshold methods was excluded, so the exclusion is disclosed nowhere in the file itself: src/UniGetUI.Core.Settings/SettingsEngine_Names.cs (Settings.ResolveKey at 136), src/UniGetUI.Interface.IpcApi/IpcCliCommandRunner.cs (IpcCliCommandRunner.RunAsync at 92), src/UniGetUI.Interface.IpcApi/IpcCliSyntax.cs (IpcCliSyntax.TryMapCommand at 85), src/UniGetUI.PackageEngine.Managers.Dotnet/Helpers/DotNetPkgOperationHelper.cs (DotNetPkgOperationHelper._getOperationParameters at 20), src/UniGetUI.PackageEngine.AgentBroker/BrokerRequestBuilder.cs (BrokerRequestBuilder.TryMapManagerName at 19), and 11 more not listed here. They are named here because the per-file figures other dimensions report are taken BEFORE this exclusion, so such a file can show a high maximum complexity elsewhere in this report and nothing here, with nothing to reconcile the two.
+ 73 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Bring the 8 bodies over 30 down to 30 or less in Cyclomatic Complexity — start with PolicyEditorSessionViewModel.SaveCoreAsync (cyclomatic 53), MainWindow.OnWindowsWndProc (cyclomatic 48), CargoBinaryResolver.ResolveAsync (cyclomatic 48). — 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 8 together lifts Cyclomatic Complexity from 6.7 to about 7.3/10, projected with the scoring formula itself and assuming each lands exactly at 30; a cleaner split scores higher.
Enforce Cyclomatic Complexity in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
Detailed fixes: d1_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: How hard the code is for a person to follow, beyond raw branching.
Method: Cognitive complexity per method (Sonar-style nesting-penalized score), computed exhaustively over production code, excluding test projects. Deterministic.
+ 122 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Bring the 2 bodies over 60 down to 60 or less in Cognitive Complexity — start with MainWindow.OnWindowsWndProc (cognitive 91), CargoBinaryResolver.ResolveAsync (cognitive 74). — 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 2 together lifts Cognitive Complexity from 6.1 to about 6.5/10, projected with the scoring formula itself and assuming each lands exactly at 60; a cleaner split scores higher.
Enforce Cognitive Complexity in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
Detailed fixes: d2_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D3 · God Classes7.7 / 10Strong✓ Tool-verified
What it measures: Over-large classes that try to do too much ("god classes").
Method: God-class detection by line and method-count thresholds per logical type (partial classes unified), filtered for generated code and registration/contract false positives. Deterministic.
Resolve the 34 TooManyMethods finding(s) in God Classes — start with MainWindow.axaml.cs, IpcClient.cs, IpcServer.cs. — One of this dimension's main actionable groups (34 warning-level).
Resolve the 30 FileTooLong finding(s) in God Classes — start with MainWindow.axaml.cs, IpcServer.cs, REDACTED. — One of this dimension's main actionable groups (30 warning-level).
Resolve the 18 MethodTooLong finding(s) in God Classes — start with PackageManagerPage.axaml.cs (2), AbstractOperation.cs (2), IpcCliCommandRunner.cs. — One of this dimension's main actionable groups (18 warning-level).
Enforce God Classes in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
Detailed fixes: d3_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Copy-pasted code that should be shared instead.
Method: Code duplication via token-stream sliding windows with type-aware normalization (locals masked, type names preserved), density-scored per KLoC of production code. Deterministic.
119 duplicated block group(s) detected. A further 5 rows report members as variants of one another; they aggregate block groups already counted above and are not themselves counted.
+ 57 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Resolve the 9 Duplicated block (6 lines × 2) finding(s) in Code Duplication — start with AbstractPackageLoader.cs, IpcBundleApi.cs, IpcPackageApi.cs. — One of this dimension's main actionable groups (9 warning-level).
Resolve the 9 Duplicated block (8 lines × 2) finding(s) in Code Duplication — start with MaintenanceScheduler.cs (2), StartMenuShortcutsDatabase.cs, Apt.cs. — One of this dimension's main actionable groups (9 warning-level).
Resolve the 7 Duplicated block (5 lines × 2) finding(s) in Code Duplication — start with InstallOptionsViewModel.cs, OperationOutputViewModel.cs, PackagesPageViewModel.cs. — One of this dimension's main actionable groups (7 warning-level).
Enforce Code Duplication in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Verified — provenance only; does not change the score.
Detailed fixes: d4_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D5 · Coupling8.8 / 10Adequategated by 5 critical findings✓ Tool-verified
What it measures: Whether volatile projects sit underneath others that depend on them (so their churn ripples upward), and whether project dependencies form cycles. A widely-depended-on but stable shared/kernel project is healthy, not penalised.
Method: Dependency cycles via elementary-DFS over real .csproj references, plus Martin instability (afferent/efferent) per project. Exhaustive over the reference graph, deterministic.
Coverage: Exhaustive · type-level: afferent/efferent coupling + cycles computed over every production type — the population is all types, not a name convention.
+ 1 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Resolve the 5 Layer violation finding(s) in Coupling — start with UniGetUI.Core.IconEngine.csproj, UniGetUI.Core.LanguageEngine.csproj, UniGetUI.Core.SecureSettings.csproj. — One of this dimension's main actionable groups (5 issue-level).
Resolve the 9 Off the main sequence finding(s) in Coupling — start with UniGetUI.Core.Logging.csproj, UniGetUI.Interface.Enums.csproj, UniGetUI.PackageEngine.Structs.csproj. — One of this dimension's main actionable groups (9 warning-level).
Resolve the 1 Unstable project UniGetUI.PackageEngine.Managers.Chocolatey finding(s) in Coupling — start with UniGetUI.PackageEngine.Managers.Chocolatey.csproj. — One of this dimension's main actionable groups (1 warning-level).
Enforce Coupling in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
Detailed fixes: d5_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether a class's methods are focused on a single responsibility.
Method: LCOM4 cohesion per production class with at least two methods: connected components of methods sharing state or calls, computed syntactically. Deterministic, not a proxy.
Coverage: Exhaustive · type-level: LCOM4 cohesion computed over every production class — the population is all types, not a name convention.
Resolve the 2 Low cohesion finding(s) in Cohesion (LCOM4) — start with MainWindow.axaml.cs, AbstractPackagesPage.axaml.cs. — One of this dimension's main actionable groups (2 warning-level).
Enforce Cohesion (LCOM4) in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Verified — provenance only; does not change the score.
Detailed fixes: d6_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D9 · Test Distribution10.0 / 10Exemplary✓ Tool-verified
What it measures: Whether the test suite has a healthy mix of unit / integration / end-to-end tests.
Method: Test projects classified (Unit/Integration/BDD/E2E) from compiled metadata; test methods counted exhaustively across projects with placement-agnostic disk fallback. Deterministic.
3499 test methods: 3499 unit, 0 integration, 0 BDD, 0 e2e.
✓ On the Gold path — maintain.
Detailed fixes: d9_recommendation.md.
Do you agree with this assessment?
D10 · Test Quality10.0 / 10Exemplary✓ Tool-verified
What it measures: Whether the tests truly assert behaviour rather than just running the code.
Method: Per-test assertions, skips, and mock references analyzed via Roslyn; structured skip-reason tags (BUG:/ENV:) separate documented deferrals from debt. Deterministic.
What it measures: Whether any secrets (keys, tokens, passwords) have leaked into the code.
Method: In-process native secret scanner (entropy plus signature patterns) across all tracked files; no external tool. A clean result is a measured 10, not no-data zero. Deterministic.
What it measures: Whether the licenses of third-party packages are compatible with your policy.
Method: Third-party package licenses resolved from declared package metadata and checked against the configured policy (allow/deny/copyleft). Deterministic; clean = no incompatible license found at metadata depth.
0 of 322 packages use a banned license. ★ DEPTH: this repository's MSBuild projects declare 44 direct `PackageReference`(s), and 210 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.
What it measures: Files that change often and are also complex — the riskiest hotspots.
Method: Per production file churn times cyclomatic complexity over a rolling window, computed from git and Roslyn/JS/Razor analysis. Exhaustive, deterministic per commit date.
Resolve the 25 Hotspot finding(s) in Churn × Complexity Hotspots — start with MainWindow.axaml.cs, AbstractPackagesPage.axaml.cs, WinGetPkgOperationHelper.cs. — One of this dimension's main actionable groups (25 warning-level).
Detailed fixes: d15_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D16 · Bus Factor8.4 / 10Strong✓ Tool-verified
What it measures: Whether knowledge is concentrated in too few people (the "bus factor").
Method: Living knowledge per author via time-decayed commit attribution (6-month half-life, focus weighting) across largest source files. Deterministic, avoids blame's mechanical-refactor false positives.
61 source file(s) have their living knowledge concentrated in one author (≥90% of recent, decayed contribution). The largest is src/UniGetUI.Avalonia/ViewModels/Pages/SettingsPages/PolicyEditor/PolicyEditorSessionViewModel.cs. Counted over 382 of the 592 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.
Off-boarding risk: anonymized user #1 · ×2
Further sole-owners (lower concentration)
What to do
Resolve the 2 Off-boarding risk finding(s) in Bus Factor. — One of this dimension's main actionable groups (2 recommendation-level).
Resolve the 1 Further sole-owners (lower concentration) finding(s) in Bus Factor. — One of this dimension's main actionable groups (1 recommendation-level).
Detailed fixes: d16_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Acknowledged debt left in the code — TODOs, dead code, suppressed warnings.
Method: Roslyn syntactic debt markers (suppressions/TODO/FIXME/HACK/empty-catch/commented-code/Obsolete) plus SymbolFinder dead-code analysis; weighted-debt-per-KLoC density deducted 2.0x per unit. Deterministic, exhaustive.
72 deducted debt markers + unmeasured dead symbols across 112046 LoC in the .NET projects (0.5/KLoC) → score 9.0. Dead code not measured: the solution did not load cleanly, so the reference search was skipped.
+ 2 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Resolve the 46 EmptyCatchBlock finding(s) in Explicit Debt — start with AutoUpdater.Helpers.cs (3), CrashHandler.cs (3), AvaloniaAutoUpdater.cs (3). — One of this dimension's main actionable groups (46 issue-level).
Resolve the 3 NoWarnInCsproj finding(s) in Explicit Debt — start with UniGetUI.Avalonia.csproj (2), Directory.Build.props. — One of this dimension's main actionable groups (3 issue-level).
Resolve the 2 FileScopedPragmaDisable finding(s) in Explicit Debt — start with SortableObservableCollectionTests.cs, LoggerTests.cs. — One of this dimension's main actionable groups (2 issue-level).
Enforce Explicit Debt in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
Detailed fixes: d17_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether the solution is laid out in a sensible, conventional structure.
Method: Solution structure: project count, decomposition, shell-project detection, build success (confirmed failures cap the score); traced to actual .sln files and binaries. Deterministic.
90 projects, 1324 source files, 168222 hand-written lines of code (111885 production / 56337 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 11 generated (machine-written code — designer, scaffolded and tool-emitted files — excluded from quality), 637 inter-project edges (build NOT measured — `dotnet build` did not complete in the analyzer, so the build half of this dimension is unmeasured rather than failed: the score above rests on structure alone and is not capped. The diagnostics that stopped it are named under Limitations.)
What it measures: Whether the project's documentation is clear, complete, and useful.
Method: Judged by language model at low temperature (0.0-0.1) on a deterministic doc sample (READMEs plus first 25 architecture docs), with two-pass stability filtering. Advisory, sampled.
The repository's root README is excellent: it announces the project (Devolutions UniGetUI), its major announcement, and a third-party warning, then documents what the directory does (a Windows-first GUI for common CLI package managers on Windows 10/11 plus cross-platform builds) with links to releases, issues, and a table of contents. The github-actions README is an internal composite-action guide that documents only the actions directory, not the repository, so it is not judged here. The CLI docs are complete: they document the public command-line surface (uniget console launcher, Windows PATH add-on), show usage examples for every command in a PowerShell script block, and cover transport options, authentication, error modeling, and query-string endpoints with an outline that all sections exist in.
Detailed fixes: d19_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D20 · ADR Quality0.0 / 10Critical✓ Tool-verified
What it measures: Whether architecture decisions are recorded well (context, decision, consequences).
Method: Per-ADR judgment by language model at low temperature with two-pass stability; confidence is share of ADRs evaluated; enforcement-field presence detected deterministically. Advisory.
What it measures: Whether names — types, methods, variables — are clear and consistent.
Method: Judged by language model at low temperature (0.0-0.1) on a deterministic random symbol sample (fixed size, not exhaustive), with disclosed confidence band. Advisory, sampled.
1 naming inconsistencies across 200 sampled symbols.
Typo in field name: 'DWMThreadAdress' uses 'ss' instead of the standard 'ss' -> 'ss' wait, 'Adress' is a typo for 'Address'. The field is named 'DWMThreadAdress' which is a misspelling of 'Address'.
✓ On the Gold path — maintain.
Detailed fixes: d21_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D24 · Comment ValueExemplary◐ Sampled · advisory
What it measures: Whether comments are worth it — explaining WHY (valuable) rather than WHAT (redundant).
Method: Judged by language model at low temperature (0.0-0.1) on deterministically sampled inline comments with surrounding code; findings verified back to sampled comments by substring match. Advisory, sampled.
What it measures: How far you must trace to follow a call — low indirection and co-located slices read easier.
Method: Call indirection (interface hops, cross-namespace calls, slice-locality scaled) over a sampled set of method invocations, size-aware baseline. Sampled; confidence discounted by symbol-resolution gaps. C# also names each pass-through layer (a class whose every public method only forwards its own parameters to one collaborator) as a located finding; the score is not affected.
Coverage: Slice locality from the first namespace segments, SAMPLED (≤400 methods) — not exhaustive.
84 % of calls cross a namespace and 5 % go through an interface, but 99 % of collaborators are co-located — so a call's collaborators sit together and tracing stays easy. Baseline: large — vertical-slice locality expected.
What it measures: Whether any secrets were ever committed — scanned across the full git history, not just now.
Method: REDACTED scan via TWO gitleaks detect passes in an isolated checkout — the full git history, then a second --no-git pass over the working tree as it stands — merged and de-duplicated by (rule, file, line); each match flagged High. Both invocations are recorded in the audit trail. Exhaustive; when the tool is absent, or when its output cannot be parsed into the expected shape, the dimension is WITHHELD as an explicit measurement gap on our side — unscored and excluded from the lens, never a hedged middling score.
5 finding(s): 0 critical, 5 high, 0 medium, 0 low. Remediation for historically-committed secrets is credential rotation — they remain in history regardless of later deletion.
REDACTED
REDACTED
What to do
Resolve the 5 REDACTED finding(s) in Secrets (history) — start with REDACTED (4), REDACTED. — One of this dimension's main actionable groups (5 issue-level).
Resolve the 1 Rotate the exposed credentials finding(s) in Secrets (history). — One of this dimension's main actionable groups (1 recommendation-level).
Detailed fixes: d28_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Real static-analysis (SAST) findings — likely security bugs in the code, any language.
Method: Polyglot static analysis via semgrep across the repo using the pinned, image-baked p/security-audit + p/owasp-top-ten rulesets (no scan-time registry fetch); severity rules (ERROR/WARNING/INFO) map to a full-band severity-weighted score. Exhaustive, deterministic; degrades on parse failure.
Coverage: semgrep pattern rules over all files — exhaustive for the rule set, blind to classes of bug without a rule (clean = no rule matched).
59 finding(s): 0 critical, 52 high, 7 medium, 0 low. 36 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 153 file(s) — `scripts/CargoSmoke/Program.cs` (lines 148–149, line 164), `src/Shared/SharedPreUiCommandDispatcher.cs` (lines 356–372, line 374, lines 410–412, …), `src/Shared/StartupBundleArguments.cs` (lines 9–106), `src/UniGetUI.Avalonia/App.axaml.cs`, `src/UniGetUI.Avalonia/CrashHandler.cs` (line 212, line 244), … (+148 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. In 50 of those file(s) — `scripts/CargoSmoke/Program.cs`, `src/UniGetUI.Avalonia/Extensions/ObservableSubscriptionExtensions.cs`, `src/UniGetUI.Avalonia/Infrastructure/AvaloniaAutoUpdater.cs`, `src/UniGetUI.Avalonia/Infrastructure/MacGlassWindowHelper.cs`, `src/UniGetUI.Avalonia/ViewModels/DialogPages/InstallOptionsViewModel.cs`, … (+45 more) — the break is a C# primary constructor, which semgrep's grammar cannot parse and which hides the type from every rule scoped to it; those files were re-scanned from a shadow copy with the constructor's parameter list blanked (line and column preserving), which restores the type to the rules, and 0 additional row(s) came from that pass. Only the header's own parameter list is unread in them. In 19 of those file(s) — `src/Shared/SharedPreUiCommandDispatcher.cs`, `src/Shared/StartupBundleArguments.cs`, `src/UniGetUI.Avalonia/App.axaml.cs`, `src/UniGetUI.Avalonia/Infrastructure/DirectionalSlideTransition.cs`, `src/UniGetUI.Avalonia/Infrastructure/EntrancePageTransition.cs`, … (+14 more) — the break is at a TYPE DECLARATION (a C# primary constructor semgrep's grammar cannot parse), so the loss is wider than the named lines: rules scoped to that type see no type to scope to and are blind over its whole body, while rules matching statements keep working there. Absence of a type-scoped finding in those types is not evidence of anything. Separately, one or more rules could not re-parse an embedded snippet in 7 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.
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
+ 6 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Resolve the 6 REDACTED finding(s) charged to Static Analysis (SAST) — the other 36 are reported here at file:line but scored by D36 (supply-chain provenance), which charges them once. — One of this dimension's main actionable groups (42 issue-level, 6 of them charged here).
Resolve the 3 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED, REDACTED, REDACTED. — One of this dimension's main actionable groups (3 issue-level).
Resolve the 2 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED, REDACTED. — One of this dimension's main actionable groups (2 issue-level).
Detailed fixes: d29_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether anyone still has living knowledge of each file, or it has been orphaned — last understood long ago by someone now gone quiet. The sibling of the bus factor: D16 asks who owns it, D34 asks whether anyone still knows it.
Method: File orphaning as total living-knowledge decay below one focused-commit's worth within a year, computed per-file from the D16 decay model. Exhaustive, deterministic over fixed history.
14 of 382 significant source file(s) are orphaned — their living knowledge has decayed to nothing, so no one currently understands them. The largest is src/UniGetUI.PackageEngine.PackageManagerClasses/Packages/Classes/IgnoredUpdatesDatabase.cs. Counted over 382 of the 592 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.
What it measures: Whether files that change together actually belong together — pairs that repeatedly co-change in git history despite having no explicit code dependency, surfacing the hidden/logical coupling (and boundaries in the wrong place) a static scan can't see.
Method: Pairwise co-occurrence over the per-commit file sets in git history (production source only — tests and generated dropped): Degree-of-Coupling = shared ÷ min individual revisions, reported above noise floors (each file ≥10 revisions, ≥5 shared commits, ≥50% strength); sweeping commits excluded. Deterministic over fixed history.
Coverage: Population: PRODUCTION source files only — test and generated files are dropped before pairing, so a class co-changing with its own test (trivially ~100%) can't drown the real production↔production coupling. Pairs ranked by Degree-of-Coupling. A non-source file is never a coupling PARTICIPANT either: documentation, schemas, config and data files are dropped with the rest, so a code↔docs pair — a command and the reference page that restates it — is not reported however strongly the two co-change; nor is coupling that runs THROUGH a build step or config file.
Resolve the 1 Boundary-crossing change coupling finding(s) in Change Coupling — start with ChocolateyDetailsHelper.cs. — One of this dimension's main actionable groups (1 issue-level).
Resolve the 3 Change coupling finding(s) in Change Coupling — start with InvalidImportedPackage.cs, BaseSourceHelper.cs, ImportedPackage.cs. — One of this dimension's main actionable groups (3 warning-level).
Resolve the 1 Change coupling clique finding(s) in Change Coupling — start with InstalledPackagesPage.cs. — One of this dimension's main actionable groups (1 warning-level).
Detailed fixes: d35_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether the build pipeline provides supply-chain integrity — generated provenance/attestation, signed artifacts (cosign/sigstore), an SBOM, and pinned build actions. Presence of the configuration, not a runtime guarantee.
Method: Supply-chain provenance/signing read deterministically from CI/build config (.github/workflows, .gitlab-ci.yml, azure-pipelines, Jenkinsfile, .circleci) + the release surface: four signals — generated provenance/attestation (SLSA/in-toto/actions-attest), artifact signing (cosign/sigstore/gitsign), an SBOM (syft/sbom-action/*.spdx.json/*.cdx.json), and SHA-pinned build actions — scored 10·present/denom. NotApplicable without a build pipeline. Detects configuration presence, not runtime enforcement.
+ 2 more group(s) — more in Appendix A; the complete list is findings.md.
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).
Detailed fixes: d36_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether the repository publishes a coordinated-vulnerability-disclosure policy (SECURITY.md or security.txt) with a reporting contact, so finders know how to report a vulnerability. Presence of a policy file with a contact, not whether the policy is adequate or honoured.
Method: Vulnerability-disclosure policy read deterministically from the repo: a SECURITY.md (root/.github/docs) or .well-known/security.txt / security.txt, regex-checked for a reporting contact (email / URL / mailto). Present + contact → 10; present without a contact → 4; NotApplicable when no policy file exists (it may live off-repo). Detects the policy file's presence + contact, not its adequacy.
What it measures: Whether anyone still ships security patches for the platform this repository RUNS ON — the runtime it pins and the framework majors its own constraints hold it to. Separate from D12 because the question differs: a current Django on an end-of-life Python is perfectly up to date and completely unsupported, and the fix is a migration rather than a version bump. What the repository says it merely SUPPORTS is never charged.
Method: End-of-life PLATFORM read from the repository's own declarations and graded against a FROZEN, dated table of vendor support dates — no network, no feed, no API, so this dimension answers identically inside a closed scan fence. Two subjects: a RUNTIME the project pins (a single or all-end-of-life TargetFramework, a .nvmrc or .python-version, a requires-python CAP) and a FRAMEWORK major a dependency constraint cannot move off (a caret, tilde or exact version; `vue@^2.7.16` pins Vue 2). A FLOOR is deliberately never charged — `requires-python = ">=3.8"` states what a package SUPPORTS, not what it runs on — and a multi-target project is charged only when EVERY target is out of support. Runtime 4.0/product capped 8.0, framework 1.5 capped 4.5. The table is safe to freeze because a statement about support that ended in the past cannot become false: it loses recall as it ages, never precision, and a test asserts every entry predates the freeze date. Disjoint from D31 (a container image's OS layer) and D29 (the toolchain a CI workflow installs). Abstains when the repository declares no platform this pass reads — never scores it clean.
0 end-of-life runtime(s) and 0 end-of-life framework(s), read from 53 platform declaration(s) and 0 dependency declaration(s). This dimension reads what the repository says about ITSELF — a pinned target framework, a version file, a capped requires-python, a Rust toolchain pin, a framework major a constraint cannot move off. A FLOOR is deliberately never charged: `requires-python = ">=3.8"` states what the package SUPPORTS, not what it runs on, and a well-maintained library declares exactly that while running its own CI on a current release. The end-of-life facts are FROZEN and dated, so this dimension needs no network and answers identically inside a closed scan fence; as the table ages it loses recall and never precision, because a statement about support that ended in the past cannot become false. The OS layer of a container image is D31's question and the toolchain a CI workflow installs is D29's; this row is neither.
Other · Architecture — Whether any singleton service captures a scoped/transient dependency — a silent lifetime/threading bug.
Method: Roslyn scan: DI registrations parsed from AddSingleton/Scoped/Transient; each singleton checked for captured shorter-lifetime dependencies. Exhaustive, deterministic.
Other · Architecture — How the codebase splits by code ROLE — domain, application, infrastructure, test, generated. The significance map behind the knowledge/coupling weighting, and a DDD signal in its own right: a thin domain core under fat infrastructure is the anemic-domain smell, quantified. How each file's role is decided, because the split is only as good as that: a generated name or a build-output tree makes it Generated, a test project makes it Test, and otherwise the file's NAMESPACE and PATH words are matched against fixed vocabularies in a fixed ORDER — domain, then infrastructure, then application — so a file whose words hit two layers is counted under the earlier one. A production file matching none of them counts as application, so that share reads 'application or unclassified' rather than a measured application layer. Roles come from naming convention, never from what the code does.
Method: Roslyn line-count by code ROLE: every source file classified Domain/Application/Infrastructure/Test/Generated by namespace + path convention (the shared CodeRoleClassifier), then significant lines summed per role. Deterministic; the advisory score is the business-logic (domain+application) share of production code.
Coverage: Population: ALL source files, each bucketed into ONE of five roles (Domain/Application/Infrastructure/Test/Generated) by namespace + path convention — a file whose layer isn't named in the convention falls to Application (the neutral default), and the split is line-count, not semantic depth or business value.
What to do
The domain core is a small share of production code, but most of the rest matched no layer vocabulary at all — so this is not yet an anemic-domain finding. The namespace/path convention could not place that code, which makes the composition above a statement about the naming, not about the design. Name the layers (or check that the repository's conventions differ from the ones this check knows) before reading a thin domain into it.
Other · Architecture — Whether singleton services avoid mutable shared instance state that concurrent callers would race on.
Method: Roslyn scan: singleton field mutations unguarded by lock or Interlocked, per type; syntax-based guard detection. Deterministic, traceable per field.
Other · Architecture — Whether the project-reference graph is acyclic (cycles block independent build/deploy and signal eroding boundaries).
Method: Project reference cycles via elementary-DFS over real .csproj references, using the engine shared with D5/D7; cyclic versus acyclic. Exhaustive, deterministic.
The namespaces UniGetUI.PackageEngine.AgentBroker.PolicyWriteElevation ↔ UniGetUI.PackageEngine.AgentBroker.PolicyWriteElevation.Interop depend on each other. The lightest dependency in the cycle is UniGetUI.PackageEngine.AgentBroker.PolicyWriteElevation.Interop → UniGetUI.PackageEngine.AgentBroker.PolicyWriteElevation (UniGetUI.PackageEngine.AgentBroker.PolicyWriteElevation.Interop.WindowsAuthenticodeTrustVerifier → UniGetUI.PackageEngine.AgentBroker.PolicyWriteElevation.IPolicyElevationTrustVerifier, 3 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. — src/UniGetUI.PackageEngine.AgentBroker/PolicyWriteElevation/Interop/WindowsAuthenticodeTrustVerifier.cs:37
The namespaces UniGetUI.Avalonia.Infrastructure ↔ UniGetUI.Avalonia.Models ↔ UniGetUI.Avalonia.ViewModels ↔ UniGetUI.Avalonia.ViewModels.Controls ↔ UniGetUI.Avalonia.ViewModels.Pages ↔ UniGetUI.Avalonia.ViewModels.Pages.LogPages ↔ UniGetUI.Avalonia.ViewModels.Pages.SettingsPages ↔ UniGetUI.Avalonia.ViewModels.Pages.SettingsPages.PolicyEditor ↔ UniGetUI.Avalonia.Views ↔ UniGetUI.Avalonia.Views.Controls ↔ UniGetUI.Avalonia.Views.Controls.Settings ↔ UniGetUI.Avalonia.Views.DialogPages ↔ UniGetUI.Avalonia.Views.Pages ↔ UniGetUI.Avalonia.Views.Pages.LogPages ↔ UniGetUI.Avalonia.Views.Pages.SettingsPages ↔ UniGetUI.Avalonia.Views.Pages.SettingsPages.PolicyEditor ↔ UniGetUI.Interface ↔ UniGetUI.Interface.Telemetry ↔ UniGetUI.PackageEngine.AgentBroker ↔ UniGetUI.PackageEngine.Classes.Manager ↔ UniGetUI.PackageEngine.Classes.Manager.Classes ↔ UniGetUI.PackageEngine.Interfaces ↔ UniGetUI.PackageEngine.Interfaces.ManagerProviders ↔ UniGetUI.PackageEngine.ManagerClasses.Classes ↔ UniGetUI.PackageEngine.ManagerClasses.Manager ↔ UniGetUI.PackageEngine.Operations ↔ UniGetUI.PackageEngine.PackageClasses ↔ UniGetUI.PackageEngine.PackageLoader depend on each other. The lightest dependency in the cycle is UniGetUI.Avalonia.Infrastructure → UniGetUI.Interface.Telemetry (UniGetUI.Avalonia.Infrastructure.AvaloniaPackageOperationHelper → UniGetUI.Interface.Telemetry.TEL_InstallReferral, 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. — src/UniGetUI.Avalonia/Infrastructure/AvaloniaPackageOperationHelper.cs:13
The namespaces UniGetUI.Tui.Infrastructure ↔ UniGetUI.Tui.Views.Controls depend on each other. The lightest dependency in the cycle is UniGetUI.Tui.Infrastructure → UniGetUI.Tui.Views.Controls (UniGetUI.Tui.Infrastructure.TuiChrome → UniGetUI.Tui.Views.Controls.TuiPanel, 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. — src/UniGetUI.Tui/Infrastructure/TuiChrome.cs:4
The namespaces UniGetUI.Tui.Views.Dialogs ↔ UniGetUI.Tui.Views.Pages depend on each other. The lightest dependency in the cycle is UniGetUI.Tui.Views.Dialogs → UniGetUI.Tui.Views.Pages (UniGetUI.Tui.Views.Dialogs.SearchOptionsDialog → UniGetUI.Tui.Views.Pages.PackageListPage, 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. — src/UniGetUI.Tui/Views/Dialogs/PackageListDialogs.cs:3
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.
Other · Architecture — Whether the codebase has a recognisable, scale-appropriate structure (a named architectural style, or modular enough for its size) rather than being an ad-hoc ball of mud.
Method: Roslyn plus csproj analysis: architecture style detection (DDD, clean, vertical-slice, CQRS) and structure fitness for repo size. Deterministic.
Other · Architecture — Whether interfaces stay focused rather than fat — the Interface-Segregation principle (SOLID 'I').
Method: Roslyn scan: public interface declared-member counts (accessors fold into their property/event); fat-interface threshold (over 15 declared members) flagged per type. Each finding also reports the distinct-OPERATION count — members counted by name, so an overload group counts once — which decides whether it states the caller-side ISP harm or the implementer-side burden of an overload set. TypeScript: exported interfaces that declare behaviour, counted over their REQUIRED operations (method signatures and function-typed properties with no `?`, once per signature) — data-shape interfaces and ambient .d.ts declarations are outside the population; JavaScript declares no interfaces and is not applicable. Deterministic, type-level.
`IPackage` declares 38 members: `Details`, `Tag`, `IsChecked`, `Name`, `Id`, `VersionString`, `HasConcreteVersion`, `InstalledVersionIsUnverified`, `NormalizedVersion`, `NormalizedNewVersion`, `Source`, `Manager`, `NewVersionString`, `IsUpgradable`, `OverridenOptions`, `AutomationName`, `GetHash`, `GetVersionedHash`, `Equals`, `IsEquivalentTo`, `GetIconId`, `GetIconUrl`, `GetIconUrlIfAny`, `GetScreenshots`, `AddToIgnoredUpdatesAsync`, `RemoveFromIgnoredUpdatesAsync`, `HasUpdatesIgnoredAsync`, `GetIgnoredUpdatesVersionAsync`, `GetInstalledPackages`, `GetAvailablePackage`, `GetUpgradablePackage`, `SetTag`, `NewerVersionIsInstalled`, `GetInstallerFileName`, `IsUpdateMinor`, `GetInstallOptions`, `AsSerializableAsync`, `AsSerializable_Incompatible`. 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. — src/UniGetUI.PackageEngine.Interfaces/IPackage.cs:10
`IPackageDetails` declares 20 members: `Package`, `IsPopulated`, `Description`, `Publisher`, `Author`, `HomepageUrl`, `License`, `LicenseUrl`, `Version`, `InstallerUrl`, `InstallerHash`, `InstallerType`, `InstallerSize`, `ManifestUrl`, `UpdateDate`, `ReleaseNotes`, `ReleaseNotesUrl`, `Tags`, `Load`, `Dependencies`. 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. — src/UniGetUI.PackageEngine.Interfaces/IPackageDetails.cs:3
`IPackageManager` declares 29 members: `Properties`, `Capabilities`, `Status`, `Id`, `Name`, `DisplayName`, `DefaultSource`, `TaskLogger`, `SourcesHelper`, `DetailsHelper`, `OperationHelper`, `Dependencies`, `OutputEncoding`, `InstallerUrlFollowsPackageVersion`, `CommandLineIsShellInterpreted`, `IdentifiersAreQuotedOnCommandLine`, `CompareVersions`, `Initialize`, `IsEnabled`, `IsReady`, `FindPackages`, `GetAvailableUpdates`, `LastUpdatesListingFailed`, `LastInstalledListingFailed`, `GetInstalledPackages`, `RefreshPackageIndexes`, `AttemptFastRepair`, `FindCandidateExecutableFiles`, `GetExecutableFile`. 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. — src/UniGetUI.PackageEngine.Interfaces/IPackageManager.cs:10
What to do
Split fat interfaces into focused role-interfaces so clients depend only on what they use.
Do you agree with this assessment?
AX8 · Test isolation10.0 / 10Exemplary✓ Tool-verified
Other · Architecture — Whether production projects stay free of references to test projects — tests may depend on production, never the reverse.
Method: Csproj graph: each production project checked for references to test projects (identified by test-framework presence, not name). Zero violations is clean. Deterministic.
Do you agree with this assessment?
C1 · Data Protection2.0 / 10Critical✓ Tool-verified
Other · Security — Whether sensitive data is encrypted at rest and in transit and keys are vaulted.
Method: Roslyn plus filesystem scan: encryption presence (EF ColumnEncryption, key-vault references, HTTPS enforcement) and key-derivation KDF detection. Deterministic.
No data-protection or encryption usage (ASP.NET Data Protection, AES, column encryption, PBKDF2) was found — sensitive data at rest may be unprotected. If TDE/KMS/vault is delegated to infrastructure, ignore.
What to do
Encrypt sensitive data at rest (ASP.NET Core Data Protection / column encryption) and manage keys in a vault. Skip if delegated to infra (Postgres TDE, KMS, etc.).
Enforce HTTPS (UseHttpsRedirection / RequireHttpsMetadata) so data in transit is always encrypted.
Other · Security — Whether access is authorized by default — a framework authorization attribute/decorator or policy, or imperative guard methods (throw-on-violation) called from handlers.
Method: Roslyn scan: [Authorize] usage and authorization policies, plus imperative throw-on-violation guard methods detected via syntax. Deterministic.
No [Authorize]/policies and no imperative guard methods (throw-on-violation) were found — endpoints may be unprotected.
`MapGet(IpcHttpRoutes.Path("/status"))` serves requests and nothing authorizes it: no [Authorize] or RequireAuthorization on it or its controller/group, no fallback policy, no auth-gate middleware and no imperative guard in this codebase. (×2) — src/UniGetUI.Interface.IpcApi/IpcServer.cs:88, src/UniGetUI.Interface.IpcApi/IpcServer.cs:88
`MapGet(IpcHttpRoutes.Path("/app"))` serves requests and nothing authorizes it: no [Authorize] or RequireAuthorization on it or its controller/group, no fallback policy, no auth-gate middleware and no imperative guard in this codebase. (×2) — src/UniGetUI.Interface.IpcApi/IpcServer.cs:89, src/UniGetUI.Interface.IpcApi/IpcServer.cs:89
`MapPost(IpcHttpRoutes.Path("/app/show"))` serves requests and nothing authorizes it: no [Authorize] or RequireAuthorization on it or its controller/group, no fallback policy, no auth-gate middleware and no imperative guard in this codebase. (×2) — src/UniGetUI.Interface.IpcApi/IpcServer.cs:90, src/UniGetUI.Interface.IpcApi/IpcServer.cs:90
`MapPost(IpcHttpRoutes.Path("/app/navigate"))` serves requests and nothing authorizes it: no [Authorize] or RequireAuthorization on it or its controller/group, no fallback policy, no auth-gate middleware and no imperative guard in this codebase. (×2) — src/UniGetUI.Interface.IpcApi/IpcServer.cs:91, src/UniGetUI.Interface.IpcApi/IpcServer.cs:91
`MapPost(IpcHttpRoutes.Path("/app/quit"))` serves requests and nothing authorizes it: no [Authorize] or RequireAuthorization on it or its controller/group, no fallback policy, no auth-gate middleware and no imperative guard in this codebase. (×2) — src/UniGetUI.Interface.IpcApi/IpcServer.cs:92, src/UniGetUI.Interface.IpcApi/IpcServer.cs:92
`MapGet(IpcHttpRoutes.Path("/operations"))` serves requests and nothing authorizes it: no [Authorize] or RequireAuthorization on it or its controller/group, no fallback policy, no auth-gate middleware and no imperative guard in this codebase. (×2) — src/UniGetUI.Interface.IpcApi/IpcServer.cs:93, src/UniGetUI.Interface.IpcApi/IpcServer.cs:93
`MapGet(IpcHttpRoutes.Path("/operations/{operationId}"))` serves requests and nothing authorizes it: no [Authorize] or RequireAuthorization on it or its controller/group, no fallback policy, no auth-gate middleware and no imperative guard in this codebase. (×2) — src/UniGetUI.Interface.IpcApi/IpcServer.cs:94, src/UniGetUI.Interface.IpcApi/IpcServer.cs:94
`MapGet(IpcHttpRoutes.Path("/operations/{operationId}/output"))` serves requests and nothing authorizes it: no [Authorize] or RequireAuthorization on it or its controller/group, no fallback policy, no auth-gate middleware and no imperative guard in this codebase. (×2) — src/UniGetUI.Interface.IpcApi/IpcServer.cs:98, src/UniGetUI.Interface.IpcApi/IpcServer.cs:98
`MapPost(IpcHttpRoutes.Path("/operations/{operationId}/cancel"))` serves requests and nothing authorizes it: no [Authorize] or RequireAuthorization on it or its controller/group, no fallback policy, no auth-gate middleware and no imperative guard in this codebase. (×2) — src/UniGetUI.Interface.IpcApi/IpcServer.cs:102, src/UniGetUI.Interface.IpcApi/IpcServer.cs:102
`MapPost(IpcHttpRoutes.Path("/operations/{operationId}/retry"))` serves requests and nothing authorizes it: no [Authorize] or RequireAuthorization on it or its controller/group, no fallback policy, no auth-gate middleware and no imperative guard in this codebase. (×2) — src/UniGetUI.Interface.IpcApi/IpcServer.cs:106, src/UniGetUI.Interface.IpcApi/IpcServer.cs:106
`MapPost(IpcHttpRoutes.Path("/operations/{operationId}/reorder"))` serves requests and nothing authorizes it: no [Authorize] or RequireAuthorization on it or its controller/group, no fallback policy, no auth-gate middleware and no imperative guard in this codebase. (×2) — src/UniGetUI.Interface.IpcApi/IpcServer.cs:110, src/UniGetUI.Interface.IpcApi/IpcServer.cs:110
`MapPost(IpcHttpRoutes.Path("/operations/{operationId}/forget"))` serves requests and nothing authorizes it: no [Authorize] or RequireAuthorization on it or its controller/group, no fallback policy, no auth-gate middleware and no imperative guard in this codebase. (×2) — src/UniGetUI.Interface.IpcApi/IpcServer.cs:114, src/UniGetUI.Interface.IpcApi/IpcServer.cs:114
`MapGet(IpcHttpRoutes.Path("/managers"))` serves requests and nothing authorizes it: no [Authorize] or RequireAuthorization on it or its controller/group, no fallback policy, no auth-gate middleware and no imperative guard in this codebase. (×2) — src/UniGetUI.Interface.IpcApi/IpcServer.cs:118, src/UniGetUI.Interface.IpcApi/IpcServer.cs:118
`MapGet(IpcHttpRoutes.Path("/managers/maintenance"))` serves requests and nothing authorizes it: no [Authorize] or RequireAuthorization on it or its controller/group, no fallback policy, no auth-gate middleware and no imperative guard in this codebase. (×2) — src/UniGetUI.Interface.IpcApi/IpcServer.cs:119, src/UniGetUI.Interface.IpcApi/IpcServer.cs:119
`MapPost(IpcHttpRoutes.Path("/managers/maintenance/reload"))` serves requests and nothing authorizes it: no [Authorize] or RequireAuthorization on it or its controller/group, no fallback policy, no auth-gate middleware and no imperative guard in this codebase. (×2) — src/UniGetUI.Interface.IpcApi/IpcServer.cs:123, src/UniGetUI.Interface.IpcApi/IpcServer.cs:123
`MapPost(IpcHttpRoutes.Path("/managers/maintenance/executable/set"))` serves requests and nothing authorizes it: no [Authorize] or RequireAuthorization on it or its controller/group, no fallback policy, no auth-gate middleware and no imperative guard in this codebase. (×2) — src/UniGetUI.Interface.IpcApi/IpcServer.cs:127, src/UniGetUI.Interface.IpcApi/IpcServer.cs:127
`MapPost(IpcHttpRoutes.Path("/managers/maintenance/executable/clear"))` serves requests and nothing authorizes it: no [Authorize] or RequireAuthorization on it or its controller/group, no fallback policy, no auth-gate middleware and no imperative guard in this codebase. (×2) — src/UniGetUI.Interface.IpcApi/IpcServer.cs:131, src/UniGetUI.Interface.IpcApi/IpcServer.cs:131
`MapPost(IpcHttpRoutes.Path("/managers/maintenance/action"))` serves requests and nothing authorizes it: no [Authorize] or RequireAuthorization on it or its controller/group, no fallback policy, no auth-gate middleware and no imperative guard in this codebase. (×2) — src/UniGetUI.Interface.IpcApi/IpcServer.cs:135, src/UniGetUI.Interface.IpcApi/IpcServer.cs:135
`MapGet(IpcHttpRoutes.Path("/sources"))` serves requests and nothing authorizes it: no [Authorize] or RequireAuthorization on it or its controller/group, no fallback policy, no auth-gate middleware and no imperative guard in this codebase. (×2) — src/UniGetUI.Interface.IpcApi/IpcServer.cs:139, src/UniGetUI.Interface.IpcApi/IpcServer.cs:139
`MapPost(IpcHttpRoutes.Path("/sources/add"))` serves requests and nothing authorizes it: no [Authorize] or RequireAuthorization on it or its controller/group, no fallback policy, no auth-gate middleware and no imperative guard in this codebase. — src/UniGetUI.Interface.IpcApi/IpcServer.cs:140
What to do
Protect endpoints by default-deny: [Authorize] + role/policy authorization, or imperative guard methods (throw-on-violation) called from every handler.
Do you agree with this assessment?
C4 · Data Retention7.5 / 10Strong✓ Tool-verified
Other · Security — Whether data has a defined lifetime — retention periods, TTLs, cleanup jobs (storage limitation).
Method: Roslyn scan: retention/TTL configuration presence in schema; CascadeDelete detected but not scored as retention control. Deterministic, gated by PII presence.
A retention mechanism is present, but the data-lifecycle is not yet complete — missing: a scheduled purge / cleanup job (PurgeOlderThan / CleanupJob).
What to do
Complete the data-lifecycle story: an expiry limit (a declared maximum age for the stored data — a retention-age setting, or a store-level TTL where your storage offers one), a scheduled purge/cleanup job that enforces it, and a documented retention period covering the personal data.
Other · Code Health — Unreviewed-generation residue: shipped members still throwing NotImplementedException, and placeholder string literals left in non-test, non-generated code. Scored as a quality signature, never as a claim about authorship.
Method: Roslyn syntax scan: NotImplementedException throws and placeholder string literals in non-test, non-generated shipped code. Deterministic, code-shape signature.
A shipped member still throws NotImplementedException — generated scaffolding that was never completed. Implement it or remove the dead surface. (×40) — src/UniGetUI.PackageEngine.Managers.Homebrew/Helpers/HomebrewPkgDetailsHelper.cs:99, src/UniGetUI.PackageEngine.Managers.Homebrew/Helpers/HomebrewPkgDetailsHelper.cs:102, src/UniGetUI.PackageEngine.PackageManagerClasses/Manager/Classes/NullPackageManager.cs:103, …
What to do
Finish or delete NotImplementedException stubs and replace placeholder literals before shipping.
Other · Code Health — Unfinished work detected by code SHAPE, not keywords: members that only throw a "not implemented" exception, methods that take inputs and return a constant, async methods that never await, dead `if (false)` / `#if false` branches, and skeleton types most of whose members are holes. A real, objective slice of technical debt.
Method: Roslyn syntax scan: incompleteness by code shape (constant-returning methods, async-never-await, #if false branches, guards that return what the code already falls through to, tests an earlier guard already decided, comparisons against NaN, skeleton types), not keyword-gated. Deterministic, code-shape heuristic.
`GetParameters` is a shipped member whose body only throws — and it is REACHED: src/UniGetUI.PackageEngine.PackageManagerClasses/Manager/Classes/NullPackageManager.cs:173 references it. This is not dead surface that can be deleted — anything taking that path throws at runtime. Implement the member, or remove the code that reaches it. — src/UniGetUI.PackageEngine.PackageManagerClasses/Manager/Classes/NullPackageManager.cs:175
`ConfirmAddSource` is declared `async` but never awaits anything, so it runs synchronously while pretending to be asynchronous. Drop `async` or do the real async work. — src/UniGetUI.Avalonia/ViewModels/Pages/SettingsPages/SourceManagerCardViewModel.cs:109
The first 2 statements of the `if` and of the `else` are identical, so they run on both paths regardless of the condition. Lift them above the `if` — leaving them duplicated inside makes the branches read as though they handled this differently. — src/UniGetUI.Avalonia/Views/DialogPages/PackageDetailsWindow.axaml.cs:1077
`GetIcon_UnSafe` is a shipped member whose whole body throws NotImplementedException — scaffolding that was never completed. Implement it or remove the dead surface. (×11) — src/UniGetUI.PackageEngine.Managers.Apt/Helpers/AptPkgDetailsHelper.cs:119, src/UniGetUI.PackageEngine.Managers.Cargo/Helpers/CargoPkgDetailsHelper.cs:74, src/UniGetUI.PackageEngine.Managers.Dnf/Helpers/DnfPkgDetailsHelper.cs:102, …
`GetScreenshots_UnSafe` is a shipped member whose whole body throws NotImplementedException — scaffolding that was never completed. Implement it or remove the dead surface. (×10) — src/UniGetUI.PackageEngine.Managers.Apt/Helpers/AptPkgDetailsHelper.cs:122, src/UniGetUI.PackageEngine.Managers.Cargo/Helpers/CargoPkgDetailsHelper.cs:79, src/UniGetUI.PackageEngine.Managers.Dnf/Helpers/DnfPkgDetailsHelper.cs:105, …
`VcpkgPkgDetailsHelper` has 3 unfinished members out of 5 declared members (methods, properties, indexers and events, whether or not each carries a body) — a scaffolded type that was never implemented. — src/UniGetUI.PackageEngine.Managers.Vcpkg/Helpers/VcpkgPkgDetailsHelper.cs:13
`GetInstallableVersions_UnSafe` is a shipped member whose whole body throws NotImplementedException — scaffolding that was never completed. Implement it or remove the dead surface. — src/UniGetUI.PackageEngine.Managers.Vcpkg/Helpers/VcpkgPkgDetailsHelper.cs:123
`VcpkgSourceHelper` has 4 unfinished members out of 5 declared members (methods, properties, indexers and events, whether or not each carries a body) — a scaffolded type that was never implemented. — src/UniGetUI.PackageEngine.Managers.Vcpkg/Helpers/VcpkgSourceHelper.cs:8
`GetAddSourceParameters` is a shipped member whose whole body throws NotImplementedException — scaffolding that was never completed. Implement it or remove the dead surface. — src/UniGetUI.PackageEngine.Managers.Vcpkg/Helpers/VcpkgSourceHelper.cs:13
`GetRemoveSourceParameters` is a shipped member whose whole body throws NotImplementedException — scaffolding that was never completed. Implement it or remove the dead surface. — src/UniGetUI.PackageEngine.Managers.Vcpkg/Helpers/VcpkgSourceHelper.cs:16
`_getAddSourceOperationVeredict` is a shipped member whose whole body throws NotImplementedException — scaffolding that was never completed. Implement it or remove the dead surface. — src/UniGetUI.PackageEngine.Managers.Vcpkg/Helpers/VcpkgSourceHelper.cs:19
`_getRemoveSourceOperationVeredict` is a shipped member whose whole body throws NotImplementedException — scaffolding that was never completed. Implement it or remove the dead surface. — src/UniGetUI.PackageEngine.Managers.Vcpkg/Helpers/VcpkgSourceHelper.cs:25
`IsWinGetManager` looks like it should compute a result but its body just returns a constant — a placeholder return that was never filled in. (×2) — src/UniGetUI.PackageEngine.Operations/PackageOperations.cs:1320, src/UniGetUI.PackageEngine.Operations/SourceOperations.cs:144
`FindPackages` is a shipped member whose whole body throws NotImplementedException — scaffolding that was never completed. Implement it or remove the dead surface. — src/UniGetUI.PackageEngine.PackageManagerClasses/Manager/Classes/NullPackageManager.cs:103
`GetAvailableUpdates` is a shipped member whose whole body throws NotImplementedException — scaffolding that was never completed. Implement it or remove the dead surface. — src/UniGetUI.PackageEngine.PackageManagerClasses/Manager/Classes/NullPackageManager.cs:106
`GetInstalledPackages` is a shipped member whose whole body throws NotImplementedException — scaffolding that was never completed. Implement it or remove the dead surface. — src/UniGetUI.PackageEngine.PackageManagerClasses/Manager/Classes/NullPackageManager.cs:108
`Initialize` is a shipped member whose whole body throws NotImplementedException — scaffolding that was never completed. Implement it or remove the dead surface. — src/UniGetUI.PackageEngine.PackageManagerClasses/Manager/Classes/NullPackageManager.cs:111
`IsEnabled` is a shipped member whose whole body throws NotImplementedException — scaffolding that was never completed. Implement it or remove the dead surface. — src/UniGetUI.PackageEngine.PackageManagerClasses/Manager/Classes/NullPackageManager.cs:113
`IsReady` is a shipped member whose whole body throws NotImplementedException — scaffolding that was never completed. Implement it or remove the dead surface. — src/UniGetUI.PackageEngine.PackageManagerClasses/Manager/Classes/NullPackageManager.cs:115
`RefreshPackageIndexes` is a shipped member whose whole body throws NotImplementedException — scaffolding that was never completed. Implement it or remove the dead surface. — src/UniGetUI.PackageEngine.PackageManagerClasses/Manager/Classes/NullPackageManager.cs:117
What to do
Finish or delete the unfinished stubs (NotImplementedException / empty / constant-returning bodies) — they are dead surface that looks live.
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.
Maturity · Maturity — Whether the repo and its projects have a README, and whether it's substantive and current.
Method: Filesystem scan: README presence, word count, and headings for depth; git history for staleness. Exhaustive across root and project dirs, deterministic.
What to do
Explain in the README how to run the tests. Add a section called Testing to the README in the repository's top folder, saying how to run the test suite.
Add an 'Architecture' / 'How it works' section to the root README — the high-level shape.
Add a README to the 57 of 57 project(s) that lack one — worth up to 2 pts.
Maturity · Maturity — Whether key decisions (ADRs) and the high-level shape (C4/diagrams) are written down.
Method: Filesystem scan: ADR folder/naming conventions or content, plus Mermaid/PlantUML/C4/architecture.md discovery. Exhaustive, deterministic.
No Architecture Decision Records found — no conventional ADR directory, no numbered `NNNN-title` documents in any markup this check reads, and nothing ADR-shaped by content. Design rationale recorded elsewhere (a design-notes tree, a mailing list, pull-request discussion) is not visible to this check and is not re-findable per decision, so a future maintainer cannot ask why one choice was made and get an answer.
What to do
Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them.
Maturity · Maturity — Whether the README actually describes the code that exists (LLM-judged, advisory).
Method: Judged by language model at low temperature: README accuracy versus actual projects, within a disclosed tolerance. Advisory, not a measured number.
docs/CLI.md links to `src/UniGetUI.Core.Settings/SettingsEngine_Names.cs`, but `docs/src/UniGetUI.Core.Settings/SettingsEngine_Names.cs` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — docs/CLI.md:225
docs/CLI.md links to `src/UniGetUI.Core.SecureSettings/SecureSettings.cs`, but `docs/src/UniGetUI.Core.SecureSettings/SecureSettings.cs` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — docs/CLI.md:226
docs/IPC.md names the project `UniGetUI.IPC`, but no project, folder or namespace of that name exists. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — docs/IPC.md:26
What to do
Reconcile the README with reality: docs/CLI.md links to `src/UniGetUI.Core.Settings/SettingsEngine_Names.cs`, but `docs/src/UniGetUI.Core.Settings/SettingsEngine_Names.cs` does not exist; docs/CLI.md links to `src/UniGetUI.Core.SecureSettings/SecureSettings.cs`, but `docs/src/UniGetUI.Core.SecureSettings/SecureSettings.cs` does not exist; docs/IPC.md names the project `UniGetUI.IPC`, but no project, folder or namespace of that name exists.
Only 29/30 service-like projects use logging (pure contract/DTO projects are excluded — they have nothing to log). Of those 30, 2 ship a process this repository operates; the rest are libraries their consumer hosts, where the logging decision belongs to the host.
`src/UniGetUI.Avalonia/CrashHandler.cs` reports through `Console.Write…` at line 270 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. — src/UniGetUI.Avalonia/CrashHandler.cs:270
What to do
Extend structured logging across the projects you operate, and give the library ones a diagnostics seam instead — an `EventSource`/`ActivitySource` the host can subscribe to, or an optional logger on your options object — rather than taking a logging dependency on your consumers' behalf.
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.
Consider OpenTelemetry tracing/metrics and a health-check endpoint for operability.
Readiness · Readiness — Whether SAST, secret/dependency scanning and performance benchmarking are wired in (presence, not runtime).
Method: Filesystem scan: SAST configuration, dependency-update automation, secret scanning, and a benchmark harness or benchmark step — in this repository's own ecosystem. Exhaustive, deterministic.
`REDACTED` run(s) a static-analysis scan, but no workflow that runs one is triggered by a pull request (or a merge queue, or an unfiltered push) — the scan fires on a schedule or a manual dispatch only. A vulnerable change therefore merges clean and is reported on the next scheduled run, by which time it is on the default branch and the only remedy is a follow-up fix. Add the pull-request trigger to the workflow that runs the scan so the finding arrives before the merge rather than after it.
What to do
Trigger your SAST workflow on pull requests — a scan that only runs on a cron reports history, it does not gate.
Add gitleaks/trufflehog in CI to block PRs that introduce committed secrets.
Readiness · Readiness — Whether releases are automated and safely reversible (probes, rolling updates, approval gates) — from manifests/pipeline files, not the live environment.
Method: Filesystem scan: deployment manifests/IaC (K8s YAML, Helm, Terraform) for rolling updates, probes, approval gates, migration hooks. Exhaustive, deterministic.
Do you agree with this assessment?
P5 · DR & Backup4.0 / 10Weak✓ Tool-verified
Readiness · Readiness — Whether disaster recovery is planned and codified — backups, geo-recovery, RTO/RPO, persistence guarantees — from IaC + container manifests + docs, never the live cloud.
Method: Filesystem scan: disaster recovery, backup, geo-recovery, RTO/RPO, persistence guarantees from IaC, manifests, and docs. Exhaustive, deterministic, never a live environment.
What to do
Document RTO/RPO and a tested restore procedure (a backup config alone isn't disaster recovery).
Readiness · Readiness — Whether releases are traceable — a maintained changelog and explicit version stamping.
Method: Filesystem scan: changelog file presence and version tags in csproj or git tags. Exhaustive, deterministic.
No CHANGELOG/HISTORY/RELEASES file — what shipped when isn't easy to reconstruct for support or audit. (Versioning/tagging makes releases traceable, but a changelog records the what.)
What to do
Keep a changelog (e.g. Keep-a-Changelog) recording what shipped in each release.
Readiness · Readiness — Whether outbound HTTP calls are wrapped in resilience (retry/timeout/circuit-breaker) so a failing dependency doesn't cascade.
Method: Source scan: outbound HTTP clients and what bounds them — resilience handlers (Polly, AddStandardResilienceHandler) on .NET; on Go, the JVM, Python, JavaScript/TypeScript, Ruby, PHP, Rust, Elixir, Swift, Dart and Erlang, a timeout, deadline, retry or breaker beside each call, or a process-wide client default (a framework-wide deadline such as Drupal core's, Laravel's or actix's awc counts). Exhaustive, deterministic.
`new HttpClient(CoreTools.GenericHttpClientParameters)` 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). (×8) — src/UniGetUI.Avalonia/ViewModels/Controls/UserAvatarViewModel.cs:94, src/UniGetUI.Avalonia/ViewModels/DialogPages/OperationViewModel.cs:167, src/UniGetUI.Avalonia/ViewModels/DialogPages/PackageDetailsViewModel.cs:319, …
`new(CoreTools.GenericHttpClientParameters)` 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). (×14) — src/UniGetUI.Avalonia/ViewModels/DialogPages/InstallOptionsViewModel.cs:653, src/UniGetUI.Core.IconStore/IconCacheEngine.cs:236, src/UniGetUI.Core.IconStore/IconDatabase.cs:75, …
`new(handler)` 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). — REDACTED:500
`new HttpClient(CoreTools.GenericHttpClientParameters) { BaseAddress = GitHubA...` 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). — src/UniGetUI.Interface.IpcApi/GitHubApiClient.cs:18
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.
Readiness · Performance — Whether the code protects its performance with benchmarks — a benchmark suite, allocation/memory measurement, and (ideally) a CI gate. Presence is credited as a bonus, never a deduction.
Method: Repo + source scan: BenchmarkDotNet referenced (csproj/source), [Benchmark]/[MemoryDiagnoser] attribute counts, and a benchmark step in CI; off .NET, the same ladder over Go testing.B, Rust criterion/#[bench]/divan, JMH/kotlinx-benchmark, pytest-benchmark/asv/pyperf, tinybench/mitata/vitest bench/benchmark.js and Swift package-benchmark — scored as a bonus ladder (absence is neutral, never a deduction). Deterministic, presence detection.
No benchmark suite was found by the two searches this check runs. FIRST, a BenchmarkDotNet package reference in any project file — every project the workspace loaded, plus a walk of project files on disk that never loaded, because a benchmark suite is exactly the project a partial load drops. SECOND, a script harness: a file whose name contains `benchmark` and ends `.py`, `.sh`, `.ps1`, `.bash`, `.rb`, `.js` or `.mjs`, credited ONLY when this repository's CI text also mentions benchmarks — a harness no pipeline runs is read as a fixture, deliberately. Neither search can see a benchmark suite in another ecosystem's idiom (a Go `testing.B` file, a JMH or criterion project, a pytest-benchmark run), so this is 'no benchmark found by those two searches', not a verdict that the repository has none. Where code is performance-sensitive, a benchmark guards against silent regressions — but it's a bonus here, not a deduction.
What to do
Add a benchmarking harness for the hot paths and run it in CI to catch regressions (for .NET, a BenchmarkDotNet project with [MemoryDiagnoser] to track allocations).
Readiness · Performance — Whether the code is written to minimise allocations so it doesn't pressure its host's memory manager — buffer/slice views over copies, object pooling, stack or value-type allocation, and buffer writers. Reward-only: credited where present, never penalised where a simpler style is fine.
Method: Production-source scan: density (per 1k LoC) of allocation-aware APIs — in .NET Span/Memory, ArrayPool/ObjectPool, stackalloc, ValueTask, value-type structs, IBufferWriter, string.Create, SkipLocalsInit; off .NET, with comments and strings blanked, Go's sync.Pool, preallocated slices/maps, Grow, strconv.Append* and buf[:0] reuse; the JVM's NIO buffer views, MemorySegment, primitive collections, pools and literal presizes (plus Kotlin primitive arrays and value classes, Scala AnyVal and @specialized); Swift's reserveCapacity, ContiguousArray, withUnsafe* access and ~Copyable. Activated off .NET on the same floor (400 lines, and benchmarks or 8 uses); Rust and garbage-collected scripting languages are not applicable. Reward-only. Deterministic, syntax/text detection.
What to do
Raise allocation-aware density on the hot paths — currently 20 use(s) across 112,396 production line(s) (~0.2/1k). More Span/Memory, pooling (ArrayPool/ObjectPool), stackalloc and ValueTask on the allocation-heavy paths climbs this toward 10.
Readiness · Performance — Whether asynchronous code stays responsive — it avoids sync-over-async blocking (a .NET .Wait()/.GetAwaiter().GetResult(), a time.sleep or blocking HTTP call inside a Python coroutine, a *Sync call inside an async JavaScript function, block_on inside a Rust async fn, runBlocking inside a Kotlin suspend function, block() inside a Reactor publisher) that stalls a thread or event loop and risks deadlock, and, where the code is a reusable library on .NET, awaits with ConfigureAwait(false) so it never captures and stalls its caller's context.
Method: Production-source scan: sync-over-async blocking counted everywhere — .Wait()/.GetAwaiter().GetResult() in .NET; off .NET, read from the language model, a blocking call inside an async function (Python, TS/JS, Rust, Kotlin, Swift, Dart) or inside a Java method returning a Reactor Mono/Flux or a Scala method returning a Future or effect — and, for a .NET library with ≥5 awaits, the share of awaits using ConfigureAwait(false). Deterministic, syntax/text detection.
46 blocking call(s) on async work (.Wait()/.GetAwaiter().GetResult()) — these waste a thread and can deadlock wherever a synchronization context is in play (a UI thread, or a caller that has one).
`.GetAwaiter().GetResult()` blocks this thread until the async work completes — it wastes a thread-pool thread for as long as the work runs and can deadlock wherever a synchronization context is in play (a UI thread, or a caller that has one). (×36) — src/UniGetUI.Avalonia/Views/DialogPages/CrashReportWindow.axaml.cs:58, src/Shared/SharedPreUiCommandDispatcher.cs:256, src/Shared/SharedPreUiCommandDispatcher.cs:274, …
`.Wait()` blocks this thread until the async work completes — it wastes a thread-pool thread for as long as the work runs and can deadlock wherever a synchronization context is in play (a UI thread, or a caller that has one). — src/UniGetUI.Core.Data/CoreData.cs:517
`task.Wait()` blocks this thread until the async work completes — it wastes a thread-pool thread for as long as the work runs and can deadlock wherever a synchronization context is in play (a UI thread, or a caller that has one). (×2) — src/UniGetUI.PackageEngine.PackageManagerClasses/Manager/Helpers/BaseSourceHelper.cs:102, src/UniGetUI.PackageEngine.PackageManagerClasses/Manager/PackageManager.cs:433
What to do
Make the call chain async end-to-end and await it — never block on a Task with .Wait()/.GetAwaiter().GetResult().
Other · Security — Transport security, security headers, secure cookies, input validation, middleware order and crypto hygiene (presence, not runtime).
Method: Roslyn plus filesystem scan: HSTS/security headers, secure cookies, input validation, middleware order, weak crypto (MD5/SHA1/DES); HTTPS-metadata context-aware. On a repository with no .NET source it reads JavaScript/TypeScript, Dart, Ruby, Scala, Rust or Elixir source itself (test, vendored, generated and minified paths not) for the arms that hold whether or not the code serves HTTP: a weak hash or cipher, key material fixed in the source, a TLS client that accepts any certificate, and (JavaScript/TypeScript, Ruby, Scala, Rust and Elixir) an obsolete TLS version; the server controls are not assessed there, and a Dart, Ruby, Scala, Rust or Elixir repository that serves no HTTP of its own is N/A on them. Deterministic.
`ServerCertificateCustomValidationCallback` is assigned a callback that returns `true` unconditionally, so every TLS peer certificate is accepted — including one an attacker presents. Chain, expiry, revocation and hostname are all skipped, so an attacker on the network path can present any certificate and read or rewrite the traffic — the connection is encrypted to the attacker, not to the intended host. Delete the override and let the platform validate. If a specific self-signed or internally-issued certificate genuinely has to be trusted, pin THAT one — compare the presented certificate's public key or thumbprint against the expected value and return `false` for everything else — and scope it to the single handler that talks to that host rather than to the whole process. If the override exists only to get past a development certificate, gate it on a build configuration or an explicit opt-in setting so it cannot ship. — src/UniGetUI.Avalonia/Infrastructure/AvaloniaAutoUpdater.cs:1652
None of the 11 security response headers the OWASP Secure Headers Project recommends (Content-Security-Policy, Strict-Transport-Security, X-Content-Type-Options, X-Frame-Options, …) is configured — defense in depth, even when a reverse proxy could set them. (−2.0 on this card.)
This web host's pipeline is composed here and adds no security response header (Content-Security-Policy, Strict-Transport-Security, X-Content-Type-Options, a frame policy) to what it serves. — src/UniGetUI.Interface.IpcApi/IpcServer.cs:71
No UseHttpsRedirection/UseHsts and no reverse-proxy signal — transport security is unverified at the app layer. (−2.0 on this card.)
This web host's pipeline is composed here with no UseHttpsRedirection/UseHsts, and nothing says a reverse proxy terminates TLS in front of it. — src/UniGetUI.Interface.IpcApi/IpcServer.cs:71
What to do
Stop accepting every TLS certificate: remove the always-true validation callback so the platform verifies the chain, hostname and expiry. If one self-signed certificate must be trusted, pin it by public key or thumbprint on the single handler that needs it and reject all others — never process-wide.
Add security response headers (Content-Security-Policy first, then Strict-Transport-Security, X-Content-Type-Options and a frame policy) — defense in depth, even when a reverse proxy could set them.
Enforce HTTPS at the app layer (UseHttpsRedirection / UseHsts) — only skip this if a reverse proxy demonstrably terminates TLS.
Other · Code Health — Whether the code avoids sync-over-async (deadlock-prone blocking on tasks) and async void.
Method: Roslyn syntax scan: async methods scanned for .Wait()/.GetAwaiter().GetResult() and async-void outside event handlers. Deterministic, hard fact per invocation.
`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. (×17) — src/UniGetUI.Avalonia/App.axaml.cs:148, src/UniGetUI.Avalonia/ViewModels/MainWindowViewModel.cs:980, src/UniGetUI.Avalonia/Views/DialogPages/CrashReportWindow.axaml.cs:24, …
`File.ReadAllText` blocks the thread on I/O while `File.ReadAllTextAsync` exists to wait without one — inside a method that is already `async`, await the twin. — src/UniGetUI.Avalonia/App.axaml.cs:296
`.Wait(…)` blocks this thread until the task completes or the bound expires — sync-over-async: it can deadlock under a synchronization context and it parks a thread while it waits. `await` the task (with `.WaitAsync(timeout, token)` where the bound matters). (×2) — src/UniGetUI.Avalonia/CrashHandler.cs:197, src/UniGetUI.Core.Tools/ShortcutFileRemover.cs:202
Reading `.Result` of a task that has not completed blocks this thread until it does — the same block as `.Wait()`: under a synchronization context (Blazor, a UI thread, classic ASP.NET) it deadlocks, and on the thread pool it parks a thread for as long as the work runs. `await` the task instead (make the caller `async`); where a synchronous entry point must stay, keep the block in ONE documented bridge with a timeout. (×4) — src/UniGetUI.Avalonia/CrashHandler.cs:199, src/UniGetUI.Avalonia/ViewModels/DialogPages/CatalogEditorViewModel.cs:109, REDACTED:1145, …
Blocking on a Task with `.Wait()`/`.GetAwaiter().GetResult()` can deadlock (and wastes a thread). Prefer awaiting it: make the caller `async` and `await` instead. Where a synchronous entry point must stay — a public sync API you cannot break, or a process entry point that must not return until the work finishes — the block belongs in ONE documented bridge and never inside code that is already async; and where it already is that bridge, give the wait a TIMEOUT so a hung task fails the call instead of hanging the process. (×16) — src/UniGetUI.Avalonia/Views/DialogPages/CrashReportWindow.axaml.cs:56, src/Shared/SharedPreUiCommandDispatcher.cs:256, src/Shared/SharedPreUiCommandDispatcher.cs:274, …
Other · Code Health — Whether any branch is dead by construction — a switch arm whose label can never equal a case-normalised subject, or an `else if` whose predicate the arm above has already swallowed.
Method: Roslyn syntax + semantics: switch labels compared against the subject's own case normaliser, and if/else-if chains checked for a literal an earlier arm's containment test already swallows. Deterministic, provable per finding. Advisory.
Do you agree with this assessment?
X13 · Undrained process stream7.5 / 10Strong✓ Tool-verified
Other · Code Health — Whether a child process that has BOTH standard streams redirected drains both — reading one to the end while the other is never read deadlocks once the child fills the unread pipe.
Method: Roslyn syntax + semantics: ProcessStartInfo launches with both streams redirected, checked for a drain of each stream across the enclosing type. On a repository with no .NET source it reads JavaScript/TypeScript off the engine’s own token stream (test, vendored and minified paths not) with the same rule: a `spawn` imported from `child_process` whose stdout and stderr are both pipes (no options, no `stdio`, or `stdio` of `'pipe'`), bound to a local that never leaves its scope, where exactly one of the two streams is read, the other never, and the child’s `close`/`exit` (or the read stream’s end) is awaited; a shell redirect in the call’s arguments or a `kill` of the child suppresses it. The same rule reads Python’s `subprocess.Popen`, Dart’s `Process.start`, Ruby’s `Open3.popen3`, and Scala’s JDK process starts (`new ProcessBuilder(…).start()` with no `redirectErrorStream`/`redirectError`/`redirectOutput`/`inheritIO`, `Runtime.getRuntime.exec`) where one of `getInputStream`/`getErrorStream` is read and the other never while `waitFor()` is called or the read stream is read to its end. Deterministic, provable per finding. Advisory.
`RedirectStandardError` is set here, but nothing in this type ever reads `StandardError` — while `StandardOutput` is read to the end. The child blocks as soon as it fills the StandardError pipe (~4 KB, never more than 64 KB), and it can then never finish writing StandardOutput, so the read-to-end above never returns and the `WaitForExit` timeout beside it does not help: the timeout bounds the WAIT, not the read that precedes it. Drain both — read one stream on a background thread (`BeginErrorReadLine()` with an `ErrorDataReceived` handler, or a `Task` running the second `ReadToEndAsync()`) and await both before `WaitForExit()` — or stop redirecting the stream you do not consume. — src/UniGetUI.PackageEngine.Managers.Scoop/Helpers/ScoopPkgDetailsHelper.cs:57
What to do
Each finding names the span that makes the branch dead and the span it is dead because of. Confirm from the two, then delete the dead arm or fix the predicate that was meant to be reachable.
Other · Security — Whether a hand-rolled public/private IP check can be walked past — a method that unwraps IPv4-mapped IPv6 but returns the opposite verdict for the same host written as IPv4-compatible, 6to4 or NAT64.
Method: Roslyn syntax + semantics: methods that unwrap IPv4-mapped IPv6 and hand-roll IPv4 range carve-outs, checked for whether the IPv6 branch also accounts for the IPv4-compatible, 6to4 and NAT64 embeddings. Deterministic, provable per finding. Advisory.
Do you agree with this assessment?
X15 · Unvalidated length from an untrusted reader10.0 / 10Exemplary○ Nothing flagged
Other · Security — Whether a length read out of the stream being parsed is bounded before it is allocated or read — an unchecked count taken from the input lets the input choose the allocation.
Method: Roslyn syntax + semantics: integer lengths read from a BinaryReader and spent on a bulk read or an array allocation, checked for any comparison or bounding call on the value anywhere in the method. Deterministic, provable per finding. Advisory.
Other · Code Health — Whether a loop that shortens a string until it fits a length budget has a floor — one with none grinds the value down to the empty string, or past it into a negative-length `Substring`.
Method: Roslyn syntax + semantics: while/do loops whose body's only effect on a string is to drop its last character, checked for whether anything — a direct comparison on the length, a body guard, a break — bounds that length below. On a repository with no .NET source it reads JavaScript/TypeScript off the engine’s own token stream (test, vendored and minified paths not) with the same rule: a `while`/`do` loop whose body’s one assignment to a value is `x = x.slice(0, -1)` or `x = x.slice|substring|substr(0, x.length - 1)`, driven by a condition that reads `x.length` only as a term of a larger expression — never compared directly, never tested for truthiness, and with no other read of `x` — and whose body has no `break`, `return`, `throw` or `if` naming `x`. Deterministic, provable per finding. Advisory.
Do you agree with this assessment?
X17 · Uncapped recursion over a caller-supplied document10.0 / 10Exemplary○ Nothing flagged
Other · Security — Whether a walk that recurses through a JSON/XML tree handed in by its caller bounds how deep it will go — an uncapped walk lets the document's nesting choose the stack depth, and the resulting StackOverflowException cannot be caught.
Method: Roslyn syntax + semantics: methods that take a JSON/XML document node and call themselves with a child of it, reachable from an externally-callable member of the same type that accepts a document, checked for any depth parameter, descent counter or threaded arithmetic anywhere in the walk. On a repository with no .NET source it reads TypeScript off the engine’s own token stream (test, vendored, generated and minified paths and `.d.ts` not) with the same rule: a function or method with a parameter typed as a document value — `unknown`, `any`, `object`, `Record<string, unknown|any>`, a JSON alias (`JsonValue`, `JSONObject`, …) or a DOM node global the file does not rebind — that calls itself (bare, or through `this` for a method, or hands itself to a call over the value as in `value.map(walk)`) with something it took out of that value and never through an ancestor accessor such as `closest()` or `parentElement`, that is exported or reached from an exported function (a public method of the same exported class) taking such a value, and that names no depth, level, nesting, recursion, remaining or budget anywhere and threads no `+`/`-` arithmetic through a self-call. Plain JavaScript is not read: with no annotation nothing tells a parsed document from a tree the code built itself. Deterministic, provable per finding. Advisory.
Other · Code Health — Whether a type's disposal matches what it OWNS — releasing what it created, leaving alone what it was handed, and not declaring a finalizer for state that has nothing unmanaged to finalize.
Method: Roslyn syntax + semantics: every assignment to a disposable field is read to decide whether the type CREATED the value or was handed it, and the type's disposal is checked against that answer — an injected interface it disposes, a value it constructed and never releases, a finalizer on a type holding nothing unmanaged, and a disposable local whose every reference is a plain member read. A value handed to a container that disposes its contents (a parent control's `Controls` collection, a component `IContainer`) is released by that container and is not reported; generated code is out of population. On a repository with no .NET source the same ownership questions are read in JavaScript/TypeScript off the engine’s own token stream (test, vendored, generated and minified paths not): a class declaring `dispose()`, `[Symbol.dispose]()` or `[Symbol.asyncDispose]()` that disposes a field it was handed through a constructor parameter typed as a repository interface or resolved by a dependency-injection container; that assigns a field only ever from `new X(…)` of a disposable class and neither releases it anywhere in the class nor names it in its disposal member or a method that member calls, nor hands it to anything else; and a `const`/`let` local built from literals only whose every reference opens a statement operating on a non-release member of it. A class is disposable when every repository declaration of its name declares or inherits a disposal member, or when it is a documented library disposable (`vscode` EventEmitter, CancellationTokenSource and Disposable; three.js geometries, materials, textures, render targets, renderers, controls and composers). The finalizer arm has no JavaScript counterpart: a class cannot declare one. Dart is read for the owned-and-never-released arm: a Flutter `State` (or a class declaring `dispose()`/`close()`) whose library-private field is written only with direct creations of a framework controller, `FocusNode`, `StreamController` or periodic `Timer` (or a `.listen(…)` into a field declared `StreamSubscription`), which nothing in the class or its library releases (`dispose`/`close`/`cancel`) and which is never handed on except as a named argument. Ruby is read for the owned-and-never-released arm and the abandoned-local arm: a class declaring an instance `close`, `dispose`, `shutdown`, `stop`, `disconnect` or `terminate` whose instance variable is written only with a blockless core descriptor creation (`File.open`/`new`, `Tempfile`, `Dir.open`, `IO.popen`, the `socket` and `openssl` socket classes) that no method of the class closes and that is never handed on (passed, returned, stored, exposed by `attr_reader`, delegated) — a class whose superclass or mixin lies outside the repository is not judged — and a blockless creation read through and dropped (`File.open(path).read`) or held in a local that is never closed, returned, passed or stored (a `&:read` block-pass, an `autoclose: false` borrow and a `fileno` hand-over are not abandonment). PHP is read for the same two arms: a class (not a trait, and not one using a trait) declaring an instance `close`, `dispose`, `shutdown`, `stop`, `disconnect` or `terminate` whose `private` property (or a `final` class's `protected` one) is written only with a direct core `fopen`, `tmpfile`, `popen`, `proc_open`, `fsockopen`, `stream_socket_client`/`server` or `opendir` that nothing in the class closes (`fclose`, `pclose`, `closedir`, `unset`, a reset to `null`) and that is never handed on, and a handle held in a function's local, or read through as the argument of a reader, that is never closed, returned, passed, captured or stored; a `php://` stream, `curl_init`, `SplFileObject`, `PDO` and a function the repository declares under the core name are not read. Deterministic, provable per finding. Advisory.
`GHAuthApiRunner` implements `IDisposable` — so it has told every caller it holds something worth releasing — and it constructs `_listener` itself (line 20), which makes that instance its own. But `_listener` is named in none of the methods the disposal search covered: `Dispose` (line 144) — that is `Dispose` plus every method `Dispose` calls BY NAME, so a release reached through an interface, a delegate or a base class is not followed and is worth checking before acting. On what was read, the type's disposal releases everything except the one thing it owns. A disposable the owner never disposes is held until finalization if its type has a finalizer, and forever if it does not — which for a synchronisation primitive, a timer, a stream or a handle means the resource accumulates once per instance for the life of the process. Release it in `Dispose` (`_listener?.Dispose();`), or, if it truly does not need releasing, drop `IDisposable` from the type so the claim and the behaviour agree. — src/UniGetUI.Avalonia/Infrastructure/GHAuthApiRunner.cs:20
`process` is a `Process`, which implements `IDisposable`, and it is created here (line 151). Every use of it in `_loadManagerExecutableFile` 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 process = …;`), which releases it at the end of the scope on every path including a throw. — src/UniGetUI.PackageEngine.Managers.Dotnet/DotNet.cs:151
`process` is a `Process`, which implements `IDisposable`, and it is created here (line 171). Every use of it in `_loadManagerVersion` 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 process = …;`), which releases it at the end of the scope on every path including a throw. — src/UniGetUI.PackageEngine.Managers.Dotnet/DotNet.cs:171
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.
Other · Code Health — Whether a method that temporarily changes state belonging to the whole process — the working directory, an environment variable — puts it back on EVERY path: a restore reached only when nothing throws leaks the change to the rest of the process.
Method: Roslyn syntax + semantics: method bodies that write the process working directory or an environment variable and write it back in the same body, checked for whether that restore sits in a `finally`/`catch` or only on the straight-line path. On a repository with no .NET source the same rule reads production JavaScript/TypeScript off the engine’s own token stream (test, vendored and minified paths not): `process.chdir`, `process.env.NAME =`/`["NAME"] =` and `delete process.env.NAME`, and Deno’s `Deno.chdir`/`Deno.env.set`/`Deno.env.delete`, paired per function body (a nested function or arrow is its own body, and module top-level code is none), where the last write puts back a local the body captured from the same global or deletes a variable the first write set, with at least one statement between them; a write in a `catch`/`finally` of that body silences it. Deterministic, provable per finding. Advisory.
Other · Code Health — Whether async methods accept a CancellationToken so work can be cancelled (adoption curve).
Method: Roslyn scan: every async method (excluding framework-fixed overrides/Blazor handlers) checked for CancellationToken parameter presence. Deterministic, adoption percentage. On a repository with no .NET source it reads JavaScript/TypeScript off the engine’s own token stream (test, vendored and minified paths not) with the same question: every named async function that itself makes a request an AbortSignal can cancel (global `fetch`, axios and its file-local instances, ky, ofetch) counts, and it is compliant when its parameters or body name a signal or it hands one of its own parameters to the request as options; signatures a framework fixes (JSX event handlers, route and lifecycle exports, request-first handlers, `override`, `'use server'` modules, TanStack `mutationFn`) are exempt unless they take a signal. Deterministic, adoption percentage.
Only 78/685 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. (×35) — src/UniGetUI.Avalonia/App.axaml.cs:148, src/UniGetUI.Avalonia/App.axaml.cs:288, src/UniGetUI.Avalonia/Models/PackageCollections.cs:719, …
No CancellationToken parameter — the body observes an ambient token instead (a field or a context object), so the work does stop on cancellation, but a caller cannot cancel this call independently of the owner that created that token. (×4) — src/UniGetUI.Avalonia/Models/PackageCollections.cs:299, src/UniGetUI.Avalonia/Models/PackageCollections.cs:477, src/UniGetUI.Avalonia/Models/PackageCollections.cs:657, …
What to do
Thread a CancellationToken through async methods so work stops promptly on cancellation.
Other · Code Health — Whether an argument guard throws the exception its own condition describes — a guard that rejects a value for being EMPTY and reports it as `ArgumentNullException` tells the caller a parameter was null when it provably was not.
Method: Roslyn syntax: `throw new ArgumentNullException(nameof(p))` statements controlled by an `if`, whose condition is read for a test that is true of a NON-null `p` — an emptiness test that dereferences it (`p.Count == 0`, `!p.Any()`) or a BCL predicate documented true of the empty value (`string.IsNullOrEmpty(p)`). Deterministic, provable per finding. Advisory.
Other · Code Health — Whether a `when` guard is free of side effects — a guard that increments a counter or assigns while deciding whether its arm matches applies that change during PATTERN MATCHING, on an arm that may not be selected, and skips it entirely when a short-circuit to its left answers first.
Method: Roslyn syntax: `when` guards on case labels and switch-expression arms, read for a mutation (`++`/`--`/assignment) sitting in a position the guard's own `&&`/`||`/`??`/`?:`/`?.` can skip. Deterministic, provable per finding. Advisory.
Other · Code Health — Whether a method that TAKES a lock or semaphore and gives it back from a flag-guarded `finally` returns the value that flag implies — reporting success while the guard hands the primitive back admits a second caller the exclusion was there to keep out, and reporting failure while the guard keeps it leaves nothing to ever give it back.
Method: Roslyn syntax: `try` statements whose `finally` releases a synchronisation primitive under a bare local-bool guard, where the method also TOOK that same primitive before the `try`, checked for a `return` of a bool literal whose value disagrees with the flag state the method's own straight-line assignments put it in. Deterministic, provable per finding. Advisory.
Other · Code Health — Whether the work a diagnostic log line costs is paid only when that line is wanted — C# evaluates a call's arguments BEFORE the call, so a trace/debug message joined or projected out of a collection is built in full on every pass, and then discarded by a sink the shipped configuration leaves switched off.
Method: Roslyn syntax: log calls at a diagnostic level (a `Log`-prefixed method naming Trace/Debug/Verbose, or a bare `Debug`/`Trace`/`Verbose` on a receiver named for a logger), whose argument list is read for a call whose cost scales with a sequence — a LINQ operator, a materialisation, `string.Join`, a serializer — with no enclosing level check or conditional-compilation region. On a repository with no .NET source it reads JavaScript/TypeScript off the engine’s own token stream (test, vendored and minified paths not) with the same rule: a `debug`/`trace`/`verbose` call on a receiver named for a logger, or a `log`-prefixed method naming the level, whose argument calls an array operator (`map`/`filter`/`reduce`/`sort`/…), `Array.from`, `Object.keys/values/entries`, `JSON.stringify`/`util.inspect` over anything but a literal, or an array `join` — outside any arrow or function passed as an argument, which the logger calls only when the level is on — with no enclosing `if`, `&&` or `?:` whose condition names a level, a level string, or the `NODE_ENV`/`__DEV__`/`DEV` build switch. Deterministic, provable per finding. Advisory.
Do you agree with this assessment?
X24 · Document value interpolated into markup unescaped10.0 / 10Exemplary○ Nothing flagged
Other · Security — Whether text read out of the document being converted is escaped before it is written into generated markup — a value the document's author chose, interpolated into an attribute the surrounding literal delimits, can close that attribute and open another.
Method: Roslyn semantic model over the whole compilation: a string-typed `Value`/`InnerText`/`InnerXml`/`Text` member declared inside `DocumentFormat.OpenXml` or `System.Xml` is a taint SOURCE, propagated through assignments, returns, arguments, tuple elements and string composition to its transitive closure, then read at interpolated-string holes that sit in a markup position the surrounding literal itself delimits. Escaper/encoder calls and enclosing validator conditions cut the flow. Flow- and container-insensitive by construction. A second arm needs no provenance at all and reports a type that CONTRADICTS ITSELF — the same expression escaped at one delimited markup hole and interpolated raw at another hole in the same markup position of the same type, which the type's own escaping proves is a defect without knowing where the value came from. On a repository with no .NET source it reads JavaScript/TypeScript off the token stream with the same rule: a DOM read of raw document text (`getAttribute`, `textContent`, `innerText`, `nodeValue`) is the source, propagated through local bindings and string composition, and judged at template-literal and concatenation holes in the same two delimited markup positions; escapers and validating conditions cut it, and documentation-site, test, vendored and minified scripts are not read. Deterministic, provable per finding. Advisory.
Other · Code Health — Whether a value the caller is invited to supply is the value the type actually uses — a constructor parameter stored in a private field that nothing ever reads while the default it was given is spelled out a second time at the site that should have read it, a keyed lookup that falls back to a different setting than the one its key names while the same type falls back to the matching one for that same key, or a culture-sensitive parse given no format provider by a type that feeds its own settable culture to the same kind of parse elsewhere, or a number an entry point writes to standard output under the host's culture while the same entry point formats with the invariant culture elsewhere. Either way, every caller who supplies a value silently gets something else.
Method: Roslyn syntax: private instance fields of a non-partial type assigned in a constructor from one of its own parameters with a `??` fallback, checked for whether anything in the type body reads the field and whether that same fallback expression is spelled out again outside the constructor; and `??` fallbacks onto a member access from a lookup call carrying exactly one string literal, grouped by that key across the type and checked for a fallback member whose folded name disagrees with the key while a sibling site for the same key agrees with it. On a repository with no .NET source the first two arms read JavaScript/TypeScript off the engine’s own token stream (tests included, bundles and vendored paths not): a `#x`, `private` or `private` parameter-property instance field filled in the constructor from a parameter (or one member of one) through `??`/`||` or a parameter default, never read anywhere in the file by name, whose constructed default is spelled again in the class body; and `lookup("key") ?? s.member` grouped by key per class, or per module outside every class. The culture arm has no JavaScript counterpart: its parses take no locale. Deterministic, provable per finding. Advisory.
Other · Code Health — Whether a value handed from a callback to the body that waits on it crosses on something built to be crossed — a `Queue<T>`/`List<T>`/`Dictionary<K,V>` written inside an event handler and read back outside it is mutated by two flows at once, and the semaphore or completion source beside it orders how MANY items exist while leaving the collection's own head, tail and backing array unprotected.
Method: Roslyn syntax: method, accessor, local-function and lambda bodies that declare BOTH a non-thread-safe generic collection (`Queue`/`Stack`/`List`/`Dictionary`/`HashSet`/`Sorted*`/`LinkedList`) and a synchronisation primitive (`SemaphoreSlim`/`TaskCompletionSource`/`ManualResetEvent(Slim)`/`AutoResetEvent`/`CountdownEvent`) as locals, then read for a `+=`-registered lambda that raises that primitive while the body outside every lambda waits on it — and, in that scope, a mutating call on the collection inside the lambda paired with a mention of it outside. Any `lock` in the scope abstains it. On a repository with no .NET source the same handoff is read in Java off the engine’s own token stream (test source sets, vendored and demonstration paths not): an `ArrayList`/`LinkedList`/`ArrayDeque`/`PriorityQueue`/`Hash*`/`LinkedHash*`/`Tree*` local and a `CountDownLatch`/`Semaphore`/`CompletableFuture` local, a lambda or anonymous class that raises the primitive and mutates the collection, and a wait outside it; any `synchronized` or `lock()` abstains the body. Because each of those primitives orders what the callback wrote before raising it, only a touch that provably overlaps the callback is convicted: one after the registration and before the next wait, or one in a loop registered-before, waiting on every pass and not declaring the collection. Deterministic, provable per finding. Advisory.
Do you agree with this assessment?
X27 · Collection changed while being enumerated10.0 / 10Exemplary○ Nothing flagged
Other · Code Health — Whether a `foreach` leaves the collection it is walking alone — a body that adds to or removes from the very collection the loop is enumerating invalidates the enumerator it is holding, so the next `MoveNext` throws `InvalidOperationException` and the remaining items are never seen.
Method: Roslyn syntax + semantics: `foreach` statements whose body calls a structural mutator (`Add`/`Remove`/`Clear`/`Insert`/…) on the very expression the loop is enumerating. Two arms. ARM A — the source is a concrete fragile BCL collection, or a live `Keys`/`Values` view over one, and the mutator resolves to that same collection's own member; concurrent and immutable collections and arrays are outside the population by construction, since their enumerators survive a structural change. ARM B — the source is an argument-less accessor CALL on a receiver whose body is in source: the accessor must return a stored field VERBATIM and a sibling member must structurally change that same field, both read off the implementations rather than from the members' names. A mutation the loop provably exits immediately after (`break`/`return`/`throw`/`goto`), or one written inside a nested loop or a lambda, is counted and never reported. Deterministic, provable per finding. Advisory.
Do you agree with this assessment?
X28 · Index access outside its own emptiness guard10.0 / 10Exemplary○ Nothing flagged
Other · Code Health — Whether a condition that tests a value for emptiness indexes that same value only where the test holds — an `||` written one parenthesis too far to the left leaves an index access outside the guard beside it, so the empty case the guard exists to anticipate reaches the index and throws.
Method: Roslyn syntax only, no semantic model: the OUTERMOST `&&`/`||` of every boolean condition, read for a symbol the condition tests for emptiness (`string.IsNullOrEmpty`/`IsNullOrWhiteSpace`, a `Length`/`Count` comparison against a literal, `Any()`, a `Length`/`Count` pattern, or a comparison against `""`) and ALSO indexes. Each `symbol[...]` access is placed by a boolean-reachability walk from the access up to the outermost connective: an access is COVERED when some enclosing step has it in the right operand and the left operand, under the truth value that step forces, proves the symbol non-empty — a recursion over `&&`/`||` whose true- and false-directions are asymmetric. A finding needs BOTH an uncovered access and a covered one on the same symbol in the same condition, which is the agreeing twin that separates a misplaced parenthesis from an unrelated length test. Bare index accesses with no emptiness test in the condition are neither counted nor reported; a non-identifier receiver and a lambda nested inside the condition are outside the population. Deterministic, provable per finding. Advisory.
Do you agree with this assessment?
X29 · Per-element action decided by a fixed element10.0 / 10Exemplary○ Nothing flagged
Other · Code Health — Whether a decision taken once per element is taken ABOUT that element — a test inside a counted loop that reads a fixed subscript of the very collection its guarded statement indexes by the loop variable applies element zero's answer to all of them, so the elements that differ from it are all handled wrongly, and in the same direction.
Method: Roslyn syntax only, no semantic model: every `for` statement declaring exactly ONE loop variable, and every `if` inside its body that is not under a nested loop or a lambda. A site enters the population when the `if`’s condition never mentions the loop variable while the statement it guards indexes some collection by that variable ALONE (`c[i]`; `c[i + 1]` and `c[i, j]` are outside it). A finding additionally needs the AGREEING TWIN at the same-collection grain: the condition must read THAT SAME collection at a subscript that does not move — written into the condition, or reached through a local declared BEFORE the loop, so an alias bound inside the body is not followed. Both collection expressions must be simple identifiers. On a repository with no .NET source the same rule reads JavaScript/TypeScript off the engine’s own token stream (tests included, bundles and vendored paths not): a `for (let|var|const x = …; …; …)` with one declarator and a braced body, an alias followed only when it is declared before the loop in a block that encloses it and never assigned inside the loop. Deterministic, provable per finding. Advisory.
Other · Code Health — Whether exceptions are handled rather than silently swallowed or rethrown with lost stack traces.
Method: Roslyn syntax scan: every catch clause counted; empty catches and bare rethrows flagged. Population is all catch clauses, not estimated. Deterministic, hard fact.
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. (×32) — src/UniGetUI.Avalonia/App.axaml.cs:304, src/UniGetUI.Avalonia/CrashHandler.cs:168, src/UniGetUI.Avalonia/CrashHandler.cs:263, …
`catch` does nothing with the exception it caught — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch. Log it through whatever this codebase already uses to report problems, or let it propagate; if one specific failure genuinely cannot matter, catch exactly that exception type and say why in a comment on the catch. (×2) — src/UniGetUI.Avalonia/CrashHandler.cs:88, src/UniGetUI.Avalonia/Views/Controls/Settings/ComboboxCard.cs:70
`catch (JsonException)` does nothing with the exception it caught — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch. Log it through whatever this codebase already uses to report problems, or let it propagate; if one specific failure genuinely cannot matter, catch exactly that exception type and say why in a comment on the catch. — src/UniGetUI.Avalonia/ViewModels/Pages/SettingsPages/PolicyEditor/PolicyEditorSessionViewModel.cs:1302
`catch (InvalidOperationException)` does nothing with the exception it caught — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch. Log it through whatever this codebase already uses to report problems, or let it propagate; if one specific failure genuinely cannot matter, catch exactly that exception type and say why in a comment on the catch. — src/UniGetUI.Avalonia/ViewModels/Pages/SettingsPages/PolicyEditor/PolicyValidationFinding.cs:286
`catch (Exception)` does nothing with the exception it caught — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch. Log it through whatever this codebase already uses to report problems, or let it propagate; if one specific failure genuinely cannot matter, catch exactly that exception type and say why in a comment on the catch. (×2) — src/UniGetUI.Avalonia/Infrastructure/GHAuthApiRunner.cs:39, src/UniGetUI.Core.Tools/ShortcutFileRemover.cs:584
`catch (IOException) when (…)` does nothing with the exception it caught — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch. Log it through whatever this codebase already uses to report problems, or let it propagate; if one specific failure genuinely cannot matter, catch exactly that exception type and say why in a comment on the catch. — src/UniGetUI.Core.Tools/LocalBackupManager.cs:95
`catch (ObjectDisposedException)` does nothing with the exception it caught — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch. Log it through whatever this codebase already uses to report problems, or let it propagate; if one specific failure genuinely cannot matter, catch exactly that exception type and say why in a comment on the catch. — src/UniGetUI.PackageEngine.Operations/AbstractOperation_Progress.cs:307
What to do
Swallowed exception (empty catch)
Do you agree with this assessment?
X30 · Support guard that admits what it rejects10.0 / 10Exemplary○ Nothing flagged
Other · Code Health — Whether a guard written as a NEGATED `||` says what its author meant — `!(a || b || x != k)` is `!a && !b && x == k` by De Morgan, so a bail-out that mixes capabilities the code needs with a fault it refuses turns inside out: it fires only where the capabilities are ABSENT, and lets every value the fault term names walk straight into the body that cannot handle it.
Method: Roslyn syntax only, no semantic model: every logical-not whose operand is a parenthesised `||` chain of two or more disjuncts, flattened (a left-nested `a || b || c` read once would see `(a || b)` as one disjunct). A site enters the population on that shape alone. A finding additionally needs the disjuncts to DISAGREE in polarity: at least one bare boolean read — an identifier or member access, never an invocation, which is a predicate rather than a capability flag — and at least one `x != <constant>`, the only form that negates into an exact-value pin (`== null` negates into a looser requirement and is outside the fault set). Consistently-polarised disjunctions, all-fault or all-capability, are counted and never reported; a negated `&&` is outside the population entirely. No same-receiver gate: it was measured to cost a real defect and remove no false positive. Deterministic, provable per finding. Advisory.
Do you agree with this assessment?
X32 · Type resolved by simple name across every loaded assembly10.0 / 10Exemplary○ Nothing flagged
Other · Code Health — Whether a plugin lookup names the type it means — searching every assembly loaded into the process for a candidate whose SIMPLE name equals a string supplied at runtime, and taking the first one found, is decided by assembly LOAD ORDER rather than by this source, so the same name can resolve to a different type on the next run.
Method: Roslyn syntax only, no semantic model: every invocation of `First`/`FirstOrDefault`/`Single`/`SingleOrDefault` whose OWN expression subtree contains both a `GetAssemblies()` call and a `GetTypes()`/`GetExportedTypes()` call — a single-element pick out of every type loaded into the process. A nested selector in the same chain sees no `GetAssemblies()` in its own subtree and is outside the population, so one lookup counts once however many links its chain has. A finding additionally needs both remaining halves: the selector must be `First`/`FirstOrDefault` (`Single`/`SingleOrDefault` reports the ambiguity rather than resolving it, and is counted and never reported), and the chain must carry an `==` comparison of `<lambda parameter>.Name` against something that is not a literal. The receiver must be a plain identifier bound by one of the chain’s own lambdas, which places `assembly.GetName().Name == "X"` outside the rule by construction. One exemption: a `.Name` test joined by `&&` to a `FullName`/`AssemblyQualifiedName` test on the same identifier is spared; joined by `||` it is not. Deterministic, provable per finding. Advisory.
Other · Code Health — Whether log calls use message templates (queryable) rather than interpolated strings.
Method: Roslyn syntax scan: every log call-site counted; interpolated-string first-argument violations flagged. Population is all log calls, not estimated. On a repository with no .NET source it reads JavaScript/TypeScript off the engine’s own token stream (test, vendored and minified paths not) with the same rule: a `trace`/`debug`/`info`/`warn`/`error`/`fatal`/`verbose`/`silly`/`http`/`log` call on a receiver named for a logger, in a package whose own or an enclosing `package.json` declares a logger that carries values as fields (pino, pino-http, nestjs-pino, Fastify, winston, bunyan, tslog, LogTape, roarr), whose first deciding argument is a template literal with substitutions; an object-literal fields argument is stepped over, a plain string message clears the call. Python is read the same way: a `debug`/`info`/`warning`/`error`/`exception`/`critical`/`log` call on a logger in a file that imports the standard library’s `logging` or structlog (loguru, which formats at the call, is not judged), whose message is a whole f-string with a non-constant field; a `%`-formatted, `.format()`-ed or concatenated message is not convicted, as in C#. PHP is read the same way: a PSR-3 level call (`emergency`…`debug`, `log`) on a logger (`$logger`, `$this->logger`, Laravel’s `Log::`, `logger()`, `\Drupal::logger()`) in a package whose `composer.json` requires a PSR-3 logger or a framework that hands one out (psr/log, Monolog, Laravel, Symfony, Drupal, CakePHP), or a file that imports one, whose message is a double-quoted string interpolating a variable; a single-quoted message clears the call, and `sprintf` or `.` concatenation is not convicted, as in C#. Dart is read the same way: a `trace`/`debug`/`info`/`warn`/`error`/`fatal` call on Sentry’s structured logger (`Sentry.logger`) whose message is a whole string literal interpolating a value (`$name`, `${…}`); the `Sentry.logger.fmt` template API clears the call. Dart that logs only through loggers with one message and no fields (package:logging, package:logger, talker, dart:developer) is not applicable rather than a reach gap. Ruby is read the same way: a `trace`/`debug`/`info`/`warn`/`error`/`fatal` call on the console gem’s `Console` (declared by a Gemfile, gemspec or Gemfile.lock, or required) or, where SemanticLogger, Ougai or dry-logger is declared or required, on a receiver named for a logger (`logger`, `@logger`, `Rails.logger`, `log`), whose first deciding argument is, as the whole argument, a double-quoted string interpolating a non-constant value (`#{…}`, `#@ivar`); a plain literal clears the call, keyword arguments are the fields, and a block, `%`-format or `+` concatenation is not convicted. Ruby that logs only through the standard Logger (Rails.logger) is not applicable rather than a reach gap. Deterministic.
Logging an interpolated string (`$"..."`) collapses the event to plain text — you lose the named, queryable properties structured logging exists for. Use a message template with placeholders: `LogInformation("User {UserId} did {Action}", id, action)`. If these calls go through a logging wrapper that only accepts a pre-formatted string, give the wrapper a template+args overload that forwards to the underlying logger, then migrate call sites to it. (×5) — src/UniGetUI.Tui/FakeData/FakePackageManager.cs:105, src/UniGetUI.Tui/FakeData/FakePackageManager.cs:114, src/UniGetUI.Tui/FakeData/FakePackageManager.cs:131, …
Other · Code Health — Whether nullable reference types are enabled and not undermined by heavy `!` suppression.
Method: Roslyn compiler-options scan: NullableContextOptions per project; null-forgiving (!) suppression density per 1k syntax nodes. Deterministic, adoption plus suppression penalty.
This method contradicts itself about `info`: line 81 writes `info?.`, which says `info` can be null, but line 38 then dereferences it directly with no null test between them and no guard around it. If the `?.` is right, that dereference throws NullReferenceException on the input it was written for; if `info` truly cannot be null here, the `?.` is misleading. Settle it one way — test `info` once before the first use and handle the null case, or drop the `?.` — rather than leaving the two readings side by side. — src/UniGetUI.PackageEngine.Managers.Pip/Helpers/PipPkgDetailsHelper.cs:38
~0.3 `!` suppressions per 1k syntax nodes — 183 suppression(s) across the 563871 syntax node(s) in code where nullable warnings are ENABLED, which is the only code a `!` can suppress anything in (a `!` under `#nullable disable` is inert and is not counted, and its file's nodes are not in the denominator). Each one tells the compiler to trust you about null, suppressing the very safety NRTs provide.
What to do
Where a method uses `?.` on a symbol and then dereferences it directly, settle the question once: test it before the first use and handle null, or drop the `?.`.
Enable <Nullable>enable</Nullable> across all projects and resolve warnings rather than suppressing with `!`.
Do you agree with this assessment?
Reference — by lens
The score is the rank-weighted fold of these lenses (worst-heaviest), each including its meta-dimensions; a lens with a Critical contributor is capped at Fair (its band reads "gated by …") and is never the strongest area however high its average.
Unscored — 5 check(s) recorded observations but carry no score
These checks ran and found something, but they do not carry a score — either by design (an advisory check reports evidence rather than grading it) or because they could not be scored here. They are excluded from the score for that reason, not because there was nothing to see.
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 — 1 observation(s) recorded · Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
X10 Duplicated predicate — 25 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
X6 Hand-rolled structured-format parsing — 4 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
X7 Silent fallback defaults — 40 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
Not evidenced — 2 control(s) we could not find positive evidence for
These checks grade a working control, and the repository shows no evidence of one. That is deliberately not scored as a zero: a repository cannot show an ops runbook, a database TTL or an infrastructure-side audit log, so absence of evidence here is not evidence the control is missing. It is also not a statement that the check is irrelevant to this codebase — the thing it grades applies; we just could not see it. Excluded from the score either way.
C3 Audit Trail — Repo shows no audit-logging mechanism (IAuditable, an immutable audit log, an EF SaveChanges interceptor) for sensitive changes — absence of evidence is not evidence of a working control. Record an audit trail in code (or document where it lives) so this dimension can be scored.
C5 Data-Subject Rights — Repo shows no corroborated data-subject-rights mechanism (erasure / export-portability / consent) tied to a subject id or GDPR vocabulary — absence of evidence is not evidence of a working control. Implement erasure, data export/portability and consent tracking over the subject's records.
Not included — 34 check(s) not relevant to this codebase
These checks had nothing to measure here (no tests, no git history, the codebase is small, or the architecture style doesn't apply), so they're omitted above rather than scored low.
AC1 Text alternatives — No web markup found — accessibility is not applicable to this repository.
AC2 Forms & labels — No web markup found — accessibility is not applicable to this repository.
AC3 Page structure — No web markup found — accessibility is not applicable to this repository.
AC4 Keyboard semantics — No web markup found — accessibility is not applicable to this repository.
AC5 ARIA correctness — No web markup found — accessibility is not applicable to this repository.
AC6 Visual & motion safety — No web markup found — accessibility is not applicable to this repository.
AC7 A11y enforcement — No web markup found — accessibility is not applicable to this repository.
AX4 Dependency direction — not applicable to a transaction-script/CRUD architecture (the inward-dependency rule is for layered/clean styles)
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.
D11 Test Reliability — Test reliability not included
D12 Dependency Hygiene — Dependency hygiene not measured
D22 Internal API Consistency — No intentionally-exposed public API to evaluate for consistency.
D23 Boundary Type-Coupling — Cross-context type coupling could not be assessed — this codebase's bounded contexts are neither declared nor inferable.
D25 ADR Conformance — no ADRs to check
D30 Dependency Vulnerabilities — 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
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) — 96 file(s) were not parsed by semgrep — the PII/GDPR ruleset never ran over them
D39 IL Efficiency — IL not measured — the analyzer's build of the target did not succeed
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.
D43 Malicious Dependencies — Not scored — no dependency manifest in a supported ecosystem was read for this repository. A gap in the analyzer's language coverage, NOT a finding that the repository is free of vulnerable dependencies (a Python pyproject.toml/requirements.txt (pip/uv/Poetry), a Swift Package.swift/Package.resolved, a Cargo manifest, a Go module (go.mod/go.sum), a Gradle version catalogue, a Maven POM, an sbt build (build.sbt), composer.json, package.json, a Dart pubspec.yaml, an Elixir mix.exs/mix.lock (Hex), a rebar.config / erlang.mk DEPS (Hex), a Ruby Gemfile/Gemfile.lock or .gemspec (Bundler/RubyGems) — not scanned yet).
D7 Architectural Integrity — no checkable ADRs and no dependency cycles — architectural integrity not assessed
D8 Code Coverage — Coverage not measured — analyzer environment
DM1 Domain Modelling — not scored — this repository shows only 1 of the 3 signals this lens looks for (21 value object(s))
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
P8 Schema migrations — no EF Core usage detected
P9 Domain vs controller coverage — no coverage report found on disk — produce a coverage report in a standard format (Cobertura — `dotnet test --collect:"XPlat Code Coverage"` with a `coverlet.collector` PackageReference) and commit it — a hosted scan measures a clone of the repository, so a report that exists only in a working tree, a CI runner's or your own, never reaches it; the artefact is commonly gitignored, so `git add -f` that one file (or un-ignore its path) and commit it alongside the code it measures, or wire coverage collection into CI, to enable this cross-layer check
X9 Subsumed condition operand — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
Appendix A — Findings (grouped)
The findings behind the scores, grouped by severity, then by dimension and kind. The high-severity issues are enumerated in full below; items per group are capped at 25 with any overflow stated explicitly per group, never silently truncated. The complete machine-readable list of every finding (all severities) is the companion findings.md in this report's bundle.
EmptyCatchBlock src/Shared/AutoUpdater.Helpers.cs:478— empty catch block — the error is discarded with nothing recorded, so a failure here leaves no trace anywhere. Record it through whatever this codebase already uses to report problems, or let it propagate. Where swallowing one specific failure really is correct — as it often is on a teardown/dispose path where throwing would mask the original failure — catch exactly that exception type and write down WHY in a comment on the catch. Both are needed: a comment on a catch-all still swallows every failure nobody anticipated, and a note that only restates the swallow ("ignored", "do nothing") is read as no explanation at all.
EmptyCatchBlock src/Shared/AutoUpdater.Helpers.cs:513— empty catch block — the error is discarded with nothing recorded, so a failure here leaves no trace anywhere. Record it through whatever this codebase already uses to report problems, or let it propagate. Where swallowing one specific failure really is correct — as it often is on a teardown/dispose path where throwing would mask the original failure — catch exactly that exception type and write down WHY in a comment on the catch. Both are needed: a comment on a catch-all still swallows every failure nobody anticipated, and a note that only restates the swallow ("ignored", "do nothing") is read as no explanation at all.
EmptyCatchBlock src/Shared/AutoUpdater.Helpers.cs:665— empty catch block — the error is discarded with nothing recorded, so a failure here leaves no trace anywhere. Record it through whatever this codebase already uses to report problems, or let it propagate. Where swallowing one specific failure really is correct — as it often is on a teardown/dispose path where throwing would mask the original failure — catch exactly that exception type and write down WHY in a comment on the catch. Both are needed: a comment on a catch-all still swallows every failure nobody anticipated, and a note that only restates the swallow ("ignored", "do nothing") is read as no explanation at all.
EmptyCatchBlock src/UniGetUI.Avalonia/App.axaml.cs:304— empty catch block — the error is discarded with nothing recorded, so a failure here leaves no trace anywhere. Record it through whatever this codebase already uses to report problems, or let it propagate. Where swallowing one specific failure really is correct — as it often is on a teardown/dispose path where throwing would mask the original failure — catch exactly that exception type and write down WHY in a comment on the catch. Both are needed: a comment on a catch-all still swallows every failure nobody anticipated, and a note that only restates the swallow ("ignored", "do nothing") is read as no explanation at all.
EmptyCatchBlock src/UniGetUI.Avalonia/CrashHandler.cs:168— empty catch block — the error is discarded with nothing recorded, so a failure here leaves no trace anywhere. Record it through whatever this codebase already uses to report problems, or let it propagate. Where swallowing one specific failure really is correct — as it often is on a teardown/dispose path where throwing would mask the original failure — catch exactly that exception type and write down WHY in a comment on the catch. Both are needed: a comment on a catch-all still swallows every failure nobody anticipated, and a note that only restates the swallow ("ignored", "do nothing") is read as no explanation at all.
EmptyCatchBlock src/UniGetUI.Avalonia/CrashHandler.cs:263— empty catch block — the error is discarded with nothing recorded, so a failure here leaves no trace anywhere. Record it through whatever this codebase already uses to report problems, or let it propagate. Where swallowing one specific failure really is correct — as it often is on a teardown/dispose path where throwing would mask the original failure — catch exactly that exception type and write down WHY in a comment on the catch. Both are needed: a comment on a catch-all still swallows every failure nobody anticipated, and a note that only restates the swallow ("ignored", "do nothing") is read as no explanation at all.
EmptyCatchBlock src/UniGetUI.Avalonia/CrashHandler.cs:278— empty catch block — the error is discarded with nothing recorded, so a failure here leaves no trace anywhere. Record it through whatever this codebase already uses to report problems, or let it propagate. Where swallowing one specific failure really is correct — as it often is on a teardown/dispose path where throwing would mask the original failure — catch exactly that exception type and write down WHY in a comment on the catch. Both are needed: a comment on a catch-all still swallows every failure nobody anticipated, and a note that only restates the swallow ("ignored", "do nothing") is read as no explanation at all.
EmptyCatchBlock src/UniGetUI.Avalonia/Infrastructure/AvaloniaAutoUpdater.cs:157— empty catch block — the error is discarded with nothing recorded, so a failure here leaves no trace anywhere. Record it through whatever this codebase already uses to report problems, or let it propagate. Where swallowing one specific failure really is correct — as it often is on a teardown/dispose path where throwing would mask the original failure — catch exactly that exception type and write down WHY in a comment on the catch. Both are needed: a comment on a catch-all still swallows every failure nobody anticipated, and a note that only restates the swallow ("ignored", "do nothing") is read as no explanation at all.
EmptyCatchBlock src/UniGetUI.Avalonia/Infrastructure/AvaloniaAutoUpdater.cs:241— empty catch block — the error is discarded with nothing recorded, so a failure here leaves no trace anywhere. Record it through whatever this codebase already uses to report problems, or let it propagate. Where swallowing one specific failure really is correct — as it often is on a teardown/dispose path where throwing would mask the original failure — catch exactly that exception type and write down WHY in a comment on the catch. Both are needed: a comment on a catch-all still swallows every failure nobody anticipated, and a note that only restates the swallow ("ignored", "do nothing") is read as no explanation at all.
EmptyCatchBlock src/UniGetUI.Avalonia/Infrastructure/AvaloniaAutoUpdater.cs:1322— empty catch block — the error is discarded with nothing recorded, so a failure here leaves no trace anywhere. Record it through whatever this codebase already uses to report problems, or let it propagate. Where swallowing one specific failure really is correct — as it often is on a teardown/dispose path where throwing would mask the original failure — catch exactly that exception type and write down WHY in a comment on the catch. Both are needed: a comment on a catch-all still swallows every failure nobody anticipated, and a note that only restates the swallow ("ignored", "do nothing") is read as no explanation at all.
EmptyCatchBlock src/UniGetUI.Avalonia/Infrastructure/MicaWindowHelper.cs:187— empty catch block — the error is discarded with nothing recorded, so a failure here leaves no trace anywhere. Record it through whatever this codebase already uses to report problems, or let it propagate. Where swallowing one specific failure really is correct — as it often is on a teardown/dispose path where throwing would mask the original failure — catch exactly that exception type and write down WHY in a comment on the catch. Both are needed: a comment on a catch-all still swallows every failure nobody anticipated, and a note that only restates the swallow ("ignored", "do nothing") is read as no explanation at all.
EmptyCatchBlock src/UniGetUI.Avalonia/Models/PackageRowModel.cs:184— empty catch block — the error is discarded with nothing recorded, so a failure here leaves no trace anywhere. Record it through whatever this codebase already uses to report problems, or let it propagate. Where swallowing one specific failure really is correct — as it often is on a teardown/dispose path where throwing would mask the original failure — catch exactly that exception type and write down WHY in a comment on the catch. Both are needed: a comment on a catch-all still swallows every failure nobody anticipated, and a note that only restates the swallow ("ignored", "do nothing") is read as no explanation at all.
EmptyCatchBlock src/UniGetUI.Avalonia/Program.cs:26— empty catch block — the error is discarded with nothing recorded, so a failure here leaves no trace anywhere. Record it through whatever this codebase already uses to report problems, or let it propagate. Where swallowing one specific failure really is correct — as it often is on a teardown/dispose path where throwing would mask the original failure — catch exactly that exception type and write down WHY in a comment on the catch. Both are needed: a comment on a catch-all still swallows every failure nobody anticipated, and a note that only restates the swallow ("ignored", "do nothing") is read as no explanation at all.
EmptyCatchBlock src/UniGetUI.Avalonia/ViewModels/DialogPages/OperationViewModel.cs:184— empty catch block — the error is discarded with nothing recorded, so a failure here leaves no trace anywhere. Record it through whatever this codebase already uses to report problems, or let it propagate. Where swallowing one specific failure really is correct — as it often is on a teardown/dispose path where throwing would mask the original failure — catch exactly that exception type and write down WHY in a comment on the catch. Both are needed: a comment on a catch-all still swallows every failure nobody anticipated, and a note that only restates the swallow ("ignored", "do nothing") is read as no explanation at all.
EmptyCatchBlock src/UniGetUI.Avalonia/ViewModels/DialogPages/OperationViewModel.cs:192— empty catch block — the error is discarded with nothing recorded, so a failure here leaves no trace anywhere. Record it through whatever this codebase already uses to report problems, or let it propagate. Where swallowing one specific failure really is correct — as it often is on a teardown/dispose path where throwing would mask the original failure — catch exactly that exception type and write down WHY in a comment on the catch. Both are needed: a comment on a catch-all still swallows every failure nobody anticipated, and a note that only restates the swallow ("ignored", "do nothing") is read as no explanation at all.
EmptyCatchBlock src/UniGetUI.Avalonia/ViewModels/DialogPages/PackageDetailsViewModel.cs:343— empty catch block — the error is discarded with nothing recorded, so a failure here leaves no trace anywhere. Record it through whatever this codebase already uses to report problems, or let it propagate. Where swallowing one specific failure really is correct — as it often is on a teardown/dispose path where throwing would mask the original failure — catch exactly that exception type and write down WHY in a comment on the catch. Both are needed: a comment on a catch-all still swallows every failure nobody anticipated, and a note that only restates the swallow ("ignored", "do nothing") is read as no explanation at all.
EmptyCatchBlock src/UniGetUI.Avalonia/ViewModels/DialogPages/PackageDetailsViewModel.cs:367— empty catch block — the error is discarded with nothing recorded, so a failure here leaves no trace anywhere. Record it through whatever this codebase already uses to report problems, or let it propagate. Where swallowing one specific failure really is correct — as it often is on a teardown/dispose path where throwing would mask the original failure — catch exactly that exception type and write down WHY in a comment on the catch. Both are needed: a comment on a catch-all still swallows every failure nobody anticipated, and a note that only restates the swallow ("ignored", "do nothing") is read as no explanation at all.
EmptyCatchBlock src/UniGetUI.Avalonia/ViewModels/DialogPages/PackageDetailsViewModel.cs:382— empty catch block — the error is discarded with nothing recorded, so a failure here leaves no trace anywhere. Record it through whatever this codebase already uses to report problems, or let it propagate. Where swallowing one specific failure really is correct — as it often is on a teardown/dispose path where throwing would mask the original failure — catch exactly that exception type and write down WHY in a comment on the catch. Both are needed: a comment on a catch-all still swallows every failure nobody anticipated, and a note that only restates the swallow ("ignored", "do nothing") is read as no explanation at all.
EmptyCatchBlock src/UniGetUI.Avalonia/ViewModels/Pages/AboutPages/ContributorsViewModel.cs:36— empty catch block — the error is discarded with nothing recorded, so a failure here leaves no trace anywhere. Record it through whatever this codebase already uses to report problems, or let it propagate. Where swallowing one specific failure really is correct — as it often is on a teardown/dispose path where throwing would mask the original failure — catch exactly that exception type and write down WHY in a comment on the catch. Both are needed: a comment on a catch-all still swallows every failure nobody anticipated, and a note that only restates the swallow ("ignored", "do nothing") is read as no explanation at all.
EmptyCatchBlock src/UniGetUI.Avalonia/ViewModels/Pages/AboutPages/TranslatorsViewModel.cs:38— empty catch block — the error is discarded with nothing recorded, so a failure here leaves no trace anywhere. Record it through whatever this codebase already uses to report problems, or let it propagate. Where swallowing one specific failure really is correct — as it often is on a teardown/dispose path where throwing would mask the original failure — catch exactly that exception type and write down WHY in a comment on the catch. Both are needed: a comment on a catch-all still swallows every failure nobody anticipated, and a note that only restates the swallow ("ignored", "do nothing") is read as no explanation at all.
EmptyCatchBlock src/UniGetUI.Avalonia/ViewModels/Pages/SettingsPages/PolicyEditor/PolicyEditorSessionViewModel.cs:1136— empty catch block — the error is discarded with nothing recorded, so a failure here leaves no trace anywhere. Record it through whatever this codebase already uses to report problems, or let it propagate. Where swallowing one specific failure really is correct — as it often is on a teardown/dispose path where throwing would mask the original failure — catch exactly that exception type and write down WHY in a comment on the catch. Both are needed: a comment on a catch-all still swallows every failure nobody anticipated, and a note that only restates the swallow ("ignored", "do nothing") is read as no explanation at all.
EmptyCatchBlock src/UniGetUI.Avalonia/Views/Controls/SvgIcon.cs:157— empty catch block — the error is discarded with nothing recorded, so a failure here leaves no trace anywhere. Record it through whatever this codebase already uses to report problems, or let it propagate. Where swallowing one specific failure really is correct — as it often is on a teardown/dispose path where throwing would mask the original failure — catch exactly that exception type and write down WHY in a comment on the catch. Both are needed: a comment on a catch-all still swallows every failure nobody anticipated, and a note that only restates the swallow ("ignored", "do nothing") is read as no explanation at all.
EmptyCatchBlock src/UniGetUI.Avalonia/Views/Controls/SvgIcon.cs:175— empty catch block — the error is discarded with nothing recorded, so a failure here leaves no trace anywhere. Record it through whatever this codebase already uses to report problems, or let it propagate. Where swallowing one specific failure really is correct — as it often is on a teardown/dispose path where throwing would mask the original failure — catch exactly that exception type and write down WHY in a comment on the catch. Both are needed: a comment on a catch-all still swallows every failure nobody anticipated, and a note that only restates the swallow ("ignored", "do nothing") is read as no explanation at all.
EmptyCatchBlock src/UniGetUI.Avalonia/Views/DialogPages/CrashReportWindow.axaml.cs:60— empty catch block — the error is discarded with nothing recorded, so a failure here leaves no trace anywhere. Record it through whatever this codebase already uses to report problems, or let it propagate. Where swallowing one specific failure really is correct — as it often is on a teardown/dispose path where throwing would mask the original failure — catch exactly that exception type and write down WHY in a comment on the catch. Both are needed: a comment on a catch-all still swallows every failure nobody anticipated, and a note that only restates the swallow ("ignored", "do nothing") is read as no explanation at all.
EmptyCatchBlock src/UniGetUI.Avalonia/Views/MainWindow.axaml.cs:1447— empty catch block — the error is discarded with nothing recorded, so a failure here leaves no trace anywhere. Record it through whatever this codebase already uses to report problems, or let it propagate. Where swallowing one specific failure really is correct — as it often is on a teardown/dispose path where throwing would mask the original failure — catch exactly that exception type and write down WHY in a comment on the catch. Both are needed: a comment on a catch-all still swallows every failure nobody anticipated, and a note that only restates the swallow ("ignored", "do nothing") is read as no explanation at all.
Namespace dependency cycle src/UniGetUI.PackageEngine.AgentBroker/PolicyWriteElevation/Interop/WindowsAuthenticodeTrustVerifier.cs:37— The namespaces UniGetUI.PackageEngine.AgentBroker.PolicyWriteElevation ↔ UniGetUI.PackageEngine.AgentBroker.PolicyWriteElevation.Interop depend on each other. The lightest dependency in the cycle is UniGetUI.PackageEngine.AgentBroker.PolicyWriteElevation.Interop → UniGetUI.PackageEngine.AgentBroker.PolicyWriteElevation (UniGetUI.PackageEngine.AgentBroker.PolicyWriteElevation.Interop.WindowsAuthenticodeTrustVerifier → UniGetUI.PackageEngine.AgentBroker.PolicyWriteElevation.IPolicyElevationTrustVerifier, 3 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.
Namespace dependency cycle src/UniGetUI.Avalonia/Infrastructure/AvaloniaPackageOperationHelper.cs:13— The namespaces UniGetUI.Avalonia.Infrastructure ↔ UniGetUI.Avalonia.Models ↔ UniGetUI.Avalonia.ViewModels ↔ UniGetUI.Avalonia.ViewModels.Controls ↔ UniGetUI.Avalonia.ViewModels.Pages ↔ UniGetUI.Avalonia.ViewModels.Pages.LogPages ↔ UniGetUI.Avalonia.ViewModels.Pages.SettingsPages ↔ UniGetUI.Avalonia.ViewModels.Pages.SettingsPages.PolicyEditor ↔ UniGetUI.Avalonia.Views ↔ UniGetUI.Avalonia.Views.Controls ↔ UniGetUI.Avalonia.Views.Controls.Settings ↔ UniGetUI.Avalonia.Views.DialogPages ↔ UniGetUI.Avalonia.Views.Pages ↔ UniGetUI.Avalonia.Views.Pages.LogPages ↔ UniGetUI.Avalonia.Views.Pages.SettingsPages ↔ UniGetUI.Avalonia.Views.Pages.SettingsPages.PolicyEditor ↔ UniGetUI.Interface ↔ UniGetUI.Interface.Telemetry ↔ UniGetUI.PackageEngine.AgentBroker ↔ UniGetUI.PackageEngine.Classes.Manager ↔ UniGetUI.PackageEngine.Classes.Manager.Classes ↔ UniGetUI.PackageEngine.Interfaces ↔ UniGetUI.PackageEngine.Interfaces.ManagerProviders ↔ UniGetUI.PackageEngine.ManagerClasses.Classes ↔ UniGetUI.PackageEngine.ManagerClasses.Manager ↔ UniGetUI.PackageEngine.Operations ↔ UniGetUI.PackageEngine.PackageClasses ↔ UniGetUI.PackageEngine.PackageLoader depend on each other. The lightest dependency in the cycle is UniGetUI.Avalonia.Infrastructure → UniGetUI.Interface.Telemetry (UniGetUI.Avalonia.Infrastructure.AvaloniaPackageOperationHelper → UniGetUI.Interface.Telemetry.TEL_InstallReferral, 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.
Namespace dependency cycle src/UniGetUI.Tui/Infrastructure/TuiChrome.cs:4— The namespaces UniGetUI.Tui.Infrastructure ↔ UniGetUI.Tui.Views.Controls depend on each other. The lightest dependency in the cycle is UniGetUI.Tui.Infrastructure → UniGetUI.Tui.Views.Controls (UniGetUI.Tui.Infrastructure.TuiChrome → UniGetUI.Tui.Views.Controls.TuiPanel, 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.
Namespace dependency cycle src/UniGetUI.Tui/Views/Dialogs/PackageListDialogs.cs:3— The namespaces UniGetUI.Tui.Views.Dialogs ↔ UniGetUI.Tui.Views.Pages depend on each other. The lightest dependency in the cycle is UniGetUI.Tui.Views.Dialogs → UniGetUI.Tui.Views.Pages (UniGetUI.Tui.Views.Dialogs.SearchOptionsDialog → UniGetUI.Tui.Views.Pages.PackageListPage, 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.
NoWarnInCsproj src/UniGetUI.Avalonia/UniGetUI.Avalonia.csproj:45— MVVMTK0045 — this warning is switched off for the WHOLE project, in every file it builds, including code written years from now: nothing at the call site records that the rule was ever silenced, so the next reader has no reason to look here. Fix what the rule is reporting and drop the code from the list, or — if some occurrences really are legitimate — narrow the suppression to those sites and give each one its reason, so the rule keeps protecting the rest of the project.
NoWarnInCsproj src/UniGetUI.Avalonia/UniGetUI.Avalonia.csproj:45— AVLN3001 — this warning is switched off for the WHOLE project, in every file it builds, including code written years from now: nothing at the call site records that the rule was ever silenced, so the next reader has no reason to look here. Fix what the rule is reporting and drop the code from the list, or — if some occurrences really are legitimate — narrow the suppression to those sites and give each one its reason, so the rule keeps protecting the rest of the project.
NoWarnInCsproj src/Directory.Build.props:65— EnableGenerateDocumentationFile — this warning is switched off for the WHOLE project, in every file it builds, including code written years from now: nothing at the call site records that the rule was ever silenced, so the next reader has no reason to look here. Fix what the rule is reporting and drop the code from the list, or — if some occurrences really are legitimate — narrow the suppression to those sites and give each one its reason, so the rule keeps protecting the rest of the project.
FileScopedPragmaDisable src/UniGetUI.Core.Classes.Tests/SortableObservableCollectionTests.cs:1— #pragma warning disable CA1852 — the disable has no matching restore anywhere in this file, so it does not end with the construct that needed it: it runs to the end of the file and silences the rule for everything written below, including code added years later that nobody weighed against it. Close it with the matching restore directive immediately after the construct it covers — that alone turns a standing exemption into a scoped one — or fix the cause and drop the directive entirely.
FileScopedPragmaDisable src/UniGetUI.Core.Logging.Tests/LoggerTests.cs:1— #pragma warning disable CA2201 — the disable has no matching restore anywhere in this file, so it does not end with the construct that needed it: it runs to the end of the file and silences the rule for everything written below, including code added years later that nobody weighed against it. Close it with the matching restore directive immediately after the construct it covers — that alone turns a standing exemption into a scoped one — or fix the cause and drop the directive entirely.
Boundary-crossing change coupling: ChocolateyDetailsHelper.cs ↔ WinGetCliHelper.cs src/UniGetUI.PackageEngine.Managers.Chocolatey/Helpers/ChocolateyDetailsHelper.cs:1— `src/UniGetUI.PackageEngine.Managers.Chocolatey/Helpers/ChocolateyDetailsHelper.cs` (context UniGetUI.PackageEngine.Managers.Chocolatey) and `src/UniGetUI.PackageEngine.Managers.WinGet/ClientHelpers/WinGetCliHelper.cs` (context UniGetUI.PackageEngine.Managers.WinGet) sit in DIFFERENT parts of the tree yet change together 58% of the time (7 of the 12 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) — the bounded-context boundary may be in the wrong place, or one context is leaking into the other. This is the behavioural boundary violation a static scan can't see. You can check this without leaving the row: of the 7 shared commits counted here, the most recent 3 are `a7d04106` Migrate Manager.Properties.ExecutableCallArguments to Manager.Status.… (at that commit the file was still `src/UniGetUI.PackageEngine.Managers.WinGet/ClientHelpers/BundledWinGetHelper.cs`); `d7bee713` Add proxy to Chocolatey and WinGet (at that commit the file was still `src/UniGetUI.PackageEngine.Managers.WinGet/ClientHelpers/BundledWinGetHelper.cs`); `20cd3ac7` Properly dispose Process instances (fix #3366) (at that commit the file was still `src/UniGetUI.PackageEngine.Managers.WinGet/ClientHelpers/BundledWinGetHelper.cs`) — run `git show` on any of them.
Unfinished stub — throws NotImplementedException src/UniGetUI.PackageEngine.PackageManagerClasses/Manager/Classes/NullPackageManager.cs:175— `GetParameters` is a shipped member whose body only throws — and it is REACHED: src/UniGetUI.PackageEngine.PackageManagerClasses/Manager/Classes/NullPackageManager.cs:173 references it. This is not dead surface that can be deleted — anything taking that path throws at runtime. Implement the member, or remove the code that reaches it.
TLS certificate validation disabled src/UniGetUI.Avalonia/Infrastructure/AvaloniaAutoUpdater.cs:1652— `ServerCertificateCustomValidationCallback` is assigned a callback that returns `true` unconditionally, so every TLS peer certificate is accepted — including one an attacker presents. Chain, expiry, revocation and hostname are all skipped, so an attacker on the network path can present any certificate and read or rewrite the traffic — the connection is encrypted to the attacker, not to the intended host. Delete the override and let the platform validate. If a specific self-signed or internally-issued certificate genuinely has to be trusted, pin THAT one — compare the presented certificate's public key or thumbprint against the expected value and return `false` for everything else — and scope it to the single handler that talks to that host rather than to the whole process. If the override exists only to get past a development certificate, gate it on a build configuration or an explicit opt-in setting so it cannot ship.
No authorization — No [Authorize]/policies and no imperative guard methods (throw-on-violation) were found — endpoints may be unprotected.
No authorization src/UniGetUI.Interface.IpcApi/IpcServer.cs:88— `MapGet(IpcHttpRoutes.Path("/status"))` serves requests and nothing authorizes it: no [Authorize] or RequireAuthorization on it or its controller/group, no fallback policy, no auth-gate middleware and no imperative guard in this codebase.
No authorization src/UniGetUI.Interface.IpcApi/IpcServer.cs:88— `MapGet(IpcHttpRoutes.Path("/status"))` serves requests and nothing authorizes it: no [Authorize] or RequireAuthorization on it or its controller/group, no fallback policy, no auth-gate middleware and no imperative guard in this codebase.
No authorization src/UniGetUI.Interface.IpcApi/IpcServer.cs:89— `MapGet(IpcHttpRoutes.Path("/app"))` serves requests and nothing authorizes it: no [Authorize] or RequireAuthorization on it or its controller/group, no fallback policy, no auth-gate middleware and no imperative guard in this codebase.
No authorization src/UniGetUI.Interface.IpcApi/IpcServer.cs:89— `MapGet(IpcHttpRoutes.Path("/app"))` serves requests and nothing authorizes it: no [Authorize] or RequireAuthorization on it or its controller/group, no fallback policy, no auth-gate middleware and no imperative guard in this codebase.
No authorization src/UniGetUI.Interface.IpcApi/IpcServer.cs:90— `MapPost(IpcHttpRoutes.Path("/app/show"))` serves requests and nothing authorizes it: no [Authorize] or RequireAuthorization on it or its controller/group, no fallback policy, no auth-gate middleware and no imperative guard in this codebase.
No authorization src/UniGetUI.Interface.IpcApi/IpcServer.cs:90— `MapPost(IpcHttpRoutes.Path("/app/show"))` serves requests and nothing authorizes it: no [Authorize] or RequireAuthorization on it or its controller/group, no fallback policy, no auth-gate middleware and no imperative guard in this codebase.
No authorization src/UniGetUI.Interface.IpcApi/IpcServer.cs:91— `MapPost(IpcHttpRoutes.Path("/app/navigate"))` serves requests and nothing authorizes it: no [Authorize] or RequireAuthorization on it or its controller/group, no fallback policy, no auth-gate middleware and no imperative guard in this codebase.
No authorization src/UniGetUI.Interface.IpcApi/IpcServer.cs:91— `MapPost(IpcHttpRoutes.Path("/app/navigate"))` serves requests and nothing authorizes it: no [Authorize] or RequireAuthorization on it or its controller/group, no fallback policy, no auth-gate middleware and no imperative guard in this codebase.
No authorization src/UniGetUI.Interface.IpcApi/IpcServer.cs:92— `MapPost(IpcHttpRoutes.Path("/app/quit"))` serves requests and nothing authorizes it: no [Authorize] or RequireAuthorization on it or its controller/group, no fallback policy, no auth-gate middleware and no imperative guard in this codebase.
No authorization src/UniGetUI.Interface.IpcApi/IpcServer.cs:92— `MapPost(IpcHttpRoutes.Path("/app/quit"))` serves requests and nothing authorizes it: no [Authorize] or RequireAuthorization on it or its controller/group, no fallback policy, no auth-gate middleware and no imperative guard in this codebase.
No authorization src/UniGetUI.Interface.IpcApi/IpcServer.cs:93— `MapGet(IpcHttpRoutes.Path("/operations"))` serves requests and nothing authorizes it: no [Authorize] or RequireAuthorization on it or its controller/group, no fallback policy, no auth-gate middleware and no imperative guard in this codebase.
No authorization src/UniGetUI.Interface.IpcApi/IpcServer.cs:93— `MapGet(IpcHttpRoutes.Path("/operations"))` serves requests and nothing authorizes it: no [Authorize] or RequireAuthorization on it or its controller/group, no fallback policy, no auth-gate middleware and no imperative guard in this codebase.
No authorization src/UniGetUI.Interface.IpcApi/IpcServer.cs:94— `MapGet(IpcHttpRoutes.Path("/operations/{operationId}"))` serves requests and nothing authorizes it: no [Authorize] or RequireAuthorization on it or its controller/group, no fallback policy, no auth-gate middleware and no imperative guard in this codebase.
No authorization src/UniGetUI.Interface.IpcApi/IpcServer.cs:94— `MapGet(IpcHttpRoutes.Path("/operations/{operationId}"))` serves requests and nothing authorizes it: no [Authorize] or RequireAuthorization on it or its controller/group, no fallback policy, no auth-gate middleware and no imperative guard in this codebase.
No authorization src/UniGetUI.Interface.IpcApi/IpcServer.cs:98— `MapGet(IpcHttpRoutes.Path("/operations/{operationId}/output"))` serves requests and nothing authorizes it: no [Authorize] or RequireAuthorization on it or its controller/group, no fallback policy, no auth-gate middleware and no imperative guard in this codebase.
No authorization src/UniGetUI.Interface.IpcApi/IpcServer.cs:98— `MapGet(IpcHttpRoutes.Path("/operations/{operationId}/output"))` serves requests and nothing authorizes it: no [Authorize] or RequireAuthorization on it or its controller/group, no fallback policy, no auth-gate middleware and no imperative guard in this codebase.
No authorization src/UniGetUI.Interface.IpcApi/IpcServer.cs:102— `MapPost(IpcHttpRoutes.Path("/operations/{operationId}/cancel"))` serves requests and nothing authorizes it: no [Authorize] or RequireAuthorization on it or its controller/group, no fallback policy, no auth-gate middleware and no imperative guard in this codebase.
No authorization src/UniGetUI.Interface.IpcApi/IpcServer.cs:102— `MapPost(IpcHttpRoutes.Path("/operations/{operationId}/cancel"))` serves requests and nothing authorizes it: no [Authorize] or RequireAuthorization on it or its controller/group, no fallback policy, no auth-gate middleware and no imperative guard in this codebase.
No authorization src/UniGetUI.Interface.IpcApi/IpcServer.cs:106— `MapPost(IpcHttpRoutes.Path("/operations/{operationId}/retry"))` serves requests and nothing authorizes it: no [Authorize] or RequireAuthorization on it or its controller/group, no fallback policy, no auth-gate middleware and no imperative guard in this codebase.
No authorization src/UniGetUI.Interface.IpcApi/IpcServer.cs:106— `MapPost(IpcHttpRoutes.Path("/operations/{operationId}/retry"))` serves requests and nothing authorizes it: no [Authorize] or RequireAuthorization on it or its controller/group, no fallback policy, no auth-gate middleware and no imperative guard in this codebase.
No authorization src/UniGetUI.Interface.IpcApi/IpcServer.cs:110— `MapPost(IpcHttpRoutes.Path("/operations/{operationId}/reorder"))` serves requests and nothing authorizes it: no [Authorize] or RequireAuthorization on it or its controller/group, no fallback policy, no auth-gate middleware and no imperative guard in this codebase.
No authorization src/UniGetUI.Interface.IpcApi/IpcServer.cs:110— `MapPost(IpcHttpRoutes.Path("/operations/{operationId}/reorder"))` serves requests and nothing authorizes it: no [Authorize] or RequireAuthorization on it or its controller/group, no fallback policy, no auth-gate middleware and no imperative guard in this codebase.
No authorization src/UniGetUI.Interface.IpcApi/IpcServer.cs:114— `MapPost(IpcHttpRoutes.Path("/operations/{operationId}/forget"))` serves requests and nothing authorizes it: no [Authorize] or RequireAuthorization on it or its controller/group, no fallback policy, no auth-gate middleware and no imperative guard in this codebase.
No authorization src/UniGetUI.Interface.IpcApi/IpcServer.cs:114— `MapPost(IpcHttpRoutes.Path("/operations/{operationId}/forget"))` serves requests and nothing authorizes it: no [Authorize] or RequireAuthorization on it or its controller/group, no fallback policy, no auth-gate middleware and no imperative guard in this codebase.
Unfinished stub — throws NotImplementedException src/UniGetUI.PackageEngine.Managers.Homebrew/Helpers/HomebrewPkgDetailsHelper.cs:99— A shipped member still throws NotImplementedException — generated scaffolding that was never completed. Implement it or remove the dead surface.
Unfinished stub — throws NotImplementedException src/UniGetUI.PackageEngine.Managers.Homebrew/Helpers/HomebrewPkgDetailsHelper.cs:102— A shipped member still throws NotImplementedException — generated scaffolding that was never completed. Implement it or remove the dead surface.
Unfinished stub — throws NotImplementedException src/UniGetUI.PackageEngine.PackageManagerClasses/Manager/Classes/NullPackageManager.cs:103— A shipped member still throws NotImplementedException — generated scaffolding that was never completed. Implement it or remove the dead surface.
Unfinished stub — throws NotImplementedException src/UniGetUI.PackageEngine.PackageManagerClasses/Manager/Classes/NullPackageManager.cs:106— A shipped member still throws NotImplementedException — generated scaffolding that was never completed. Implement it or remove the dead surface.
Unfinished stub — throws NotImplementedException src/UniGetUI.PackageEngine.PackageManagerClasses/Manager/Classes/NullPackageManager.cs:108— A shipped member still throws NotImplementedException — generated scaffolding that was never completed. Implement it or remove the dead surface.
Unfinished stub — throws NotImplementedException src/UniGetUI.PackageEngine.PackageManagerClasses/Manager/Classes/NullPackageManager.cs:111— A shipped member still throws NotImplementedException — generated scaffolding that was never completed. Implement it or remove the dead surface.
Unfinished stub — throws NotImplementedException src/UniGetUI.PackageEngine.PackageManagerClasses/Manager/Classes/NullPackageManager.cs:113— A shipped member still throws NotImplementedException — generated scaffolding that was never completed. Implement it or remove the dead surface.
Unfinished stub — throws NotImplementedException src/UniGetUI.PackageEngine.PackageManagerClasses/Manager/Classes/NullPackageManager.cs:115— A shipped member still throws NotImplementedException — generated scaffolding that was never completed. Implement it or remove the dead surface.
Unfinished stub — throws NotImplementedException src/UniGetUI.PackageEngine.PackageManagerClasses/Manager/Classes/NullPackageManager.cs:117— A shipped member still throws NotImplementedException — generated scaffolding that was never completed. Implement it or remove the dead surface.
Unfinished stub — throws NotImplementedException src/UniGetUI.PackageEngine.PackageManagerClasses/Manager/Classes/NullPackageManager.cs:119— A shipped member still throws NotImplementedException — generated scaffolding that was never completed. Implement it or remove the dead surface.
Unfinished stub — throws NotImplementedException src/UniGetUI.PackageEngine.PackageManagerClasses/Manager/Classes/NullPackageManager.cs:121— A shipped member still throws NotImplementedException — generated scaffolding that was never completed. Implement it or remove the dead surface.
Unfinished stub — throws NotImplementedException src/UniGetUI.PackageEngine.PackageManagerClasses/Manager/Classes/NullPackageManager.cs:124— A shipped member still throws NotImplementedException — generated scaffolding that was never completed. Implement it or remove the dead surface.
Unfinished stub — throws NotImplementedException src/UniGetUI.PackageEngine.PackageManagerClasses/Manager/Classes/NullPackageManager.cs:129— A shipped member still throws NotImplementedException — generated scaffolding that was never completed. Implement it or remove the dead surface.
Unfinished stub — throws NotImplementedException src/UniGetUI.PackageEngine.PackageManagerClasses/Manager/Classes/NullPackageManager.cs:131— A shipped member still throws NotImplementedException — generated scaffolding that was never completed. Implement it or remove the dead surface.
Unfinished stub — throws NotImplementedException src/UniGetUI.PackageEngine.PackageManagerClasses/Manager/Classes/NullPackageManager.cs:134— A shipped member still throws NotImplementedException — generated scaffolding that was never completed. Implement it or remove the dead surface.
Unfinished stub — throws NotImplementedException src/UniGetUI.PackageEngine.PackageManagerClasses/Manager/Classes/NullPackageManager.cs:137— A shipped member still throws NotImplementedException — generated scaffolding that was never completed. Implement it or remove the dead surface.
Unfinished stub — throws NotImplementedException src/UniGetUI.PackageEngine.PackageManagerClasses/Manager/Classes/NullPackageManager.cs:143— A shipped member still throws NotImplementedException — generated scaffolding that was never completed. Implement it or remove the dead surface.
Unfinished stub — throws NotImplementedException src/UniGetUI.PackageEngine.PackageManagerClasses/Manager/Classes/NullPackageManager.cs:149— A shipped member still throws NotImplementedException — generated scaffolding that was never completed. Implement it or remove the dead surface.
Unfinished stub — throws NotImplementedException src/UniGetUI.PackageEngine.PackageManagerClasses/Manager/Classes/NullPackageManager.cs:154— A shipped member still throws NotImplementedException — generated scaffolding that was never completed. Implement it or remove the dead surface.
Unfinished stub — throws NotImplementedException src/UniGetUI.PackageEngine.PackageManagerClasses/Manager/Classes/NullPackageManager.cs:156— A shipped member still throws NotImplementedException — generated scaffolding that was never completed. Implement it or remove the dead surface.
Unfinished stub — throws NotImplementedException src/UniGetUI.PackageEngine.PackageManagerClasses/Manager/Classes/NullPackageManager.cs:159— A shipped member still throws NotImplementedException — generated scaffolding that was never completed. Implement it or remove the dead surface.
Unfinished stub — throws NotImplementedException src/UniGetUI.PackageEngine.PackageManagerClasses/Manager/Classes/NullPackageManager.cs:161— A shipped member still throws NotImplementedException — generated scaffolding that was never completed. Implement it or remove the dead surface.
Unfinished stub — throws NotImplementedException src/UniGetUI.PackageEngine.PackageManagerClasses/Manager/Classes/NullPackageManager.cs:164— A shipped member still throws NotImplementedException — generated scaffolding that was never completed. Implement it or remove the dead surface.
Unfinished stub — throws NotImplementedException src/UniGetUI.PackageEngine.PackageManagerClasses/Manager/Classes/NullPackageManager.cs:175— A shipped member still throws NotImplementedException — generated scaffolding that was never completed. Implement it or remove the dead surface.
Unfinished stub — throws NotImplementedException src/UniGetUI.PackageEngine.PackageManagerClasses/Manager/Classes/NullPackageManager.cs:181— A shipped member still throws NotImplementedException — generated scaffolding that was never completed. Implement it or remove the dead surface.
Sync-over-async blocking — 46 blocking call(s) on async work (.Wait()/.GetAwaiter().GetResult()) — these waste a thread and can deadlock wherever a synchronization context is in play (a UI thread, or a caller that has one).
Sync-over-async blocking src/UniGetUI.Avalonia/Views/DialogPages/CrashReportWindow.axaml.cs:58— `.GetAwaiter().GetResult()` blocks this thread until the async work completes — it wastes a thread-pool thread for as long as the work runs and can deadlock wherever a synchronization context is in play (a UI thread, or a caller that has one).
Sync-over-async blocking src/Shared/SharedPreUiCommandDispatcher.cs:256— `.GetAwaiter().GetResult()` blocks this thread until the async work completes — it wastes a thread-pool thread for as long as the work runs and can deadlock wherever a synchronization context is in play (a UI thread, or a caller that has one).
Sync-over-async blocking src/Shared/SharedPreUiCommandDispatcher.cs:274— `.GetAwaiter().GetResult()` blocks this thread until the async work completes — it wastes a thread-pool thread for as long as the work runs and can deadlock wherever a synchronization context is in play (a UI thread, or a caller that has one).
Sync-over-async blocking src/UniGetUI.Avalonia/Infrastructure/AvaloniaAutoUpdater.cs:1573— `.GetAwaiter().GetResult()` blocks this thread until the async work completes — it wastes a thread-pool thread for as long as the work runs and can deadlock wherever a synchronization context is in play (a UI thread, or a caller that has one).
Sync-over-async blocking src/UniGetUI.Avalonia/Infrastructure/AvaloniaBootstrapper.cs:210— `.GetAwaiter().GetResult()` blocks this thread until the async work completes — it wastes a thread-pool thread for as long as the work runs and can deadlock wherever a synchronization context is in play (a UI thread, or a caller that has one).
Sync-over-async blocking src/UniGetUI.Avalonia/Infrastructure/AvaloniaBootstrapper.cs:212— `.GetAwaiter().GetResult()` blocks this thread until the async work completes — it wastes a thread-pool thread for as long as the work runs and can deadlock wherever a synchronization context is in play (a UI thread, or a caller that has one).
Sync-over-async blocking src/UniGetUI.Avalonia/Infrastructure/AvaloniaBootstrapper.cs:214— `.GetAwaiter().GetResult()` blocks this thread until the async work completes — it wastes a thread-pool thread for as long as the work runs and can deadlock wherever a synchronization context is in play (a UI thread, or a caller that has one).
Sync-over-async blocking src/UniGetUI.Avalonia/Infrastructure/AvaloniaBootstrapper.cs:216— `.GetAwaiter().GetResult()` blocks this thread until the async work completes — it wastes a thread-pool thread for as long as the work runs and can deadlock wherever a synchronization context is in play (a UI thread, or a caller that has one).
Sync-over-async blocking src/UniGetUI.Avalonia/Infrastructure/AvaloniaBootstrapper.cs:218— `.GetAwaiter().GetResult()` blocks this thread until the async work completes — it wastes a thread-pool thread for as long as the work runs and can deadlock wherever a synchronization context is in play (a UI thread, or a caller that has one).
Sync-over-async blocking src/UniGetUI.Avalonia/Infrastructure/SingleInstanceRedirector.cs:117— `.GetAwaiter().GetResult()` blocks this thread until the async work completes — it wastes a thread-pool thread for as long as the work runs and can deadlock wherever a synchronization context is in play (a UI thread, or a caller that has one).
Sync-over-async blocking src/UniGetUI.Core.Classes/TaskRecycler.cs:78— `.GetAwaiter().GetResult()` blocks this thread until the async work completes — it wastes a thread-pool thread for as long as the work runs and can deadlock wherever a synchronization context is in play (a UI thread, or a caller that has one).
Sync-over-async blocking src/UniGetUI.Core.Classes/TaskRecycler.cs:84— `.GetAwaiter().GetResult()` blocks this thread until the async work completes — it wastes a thread-pool thread for as long as the work runs and can deadlock wherever a synchronization context is in play (a UI thread, or a caller that has one).
Sync-over-async blocking src/UniGetUI.Core.Classes/TaskRecycler.cs:91— `.GetAwaiter().GetResult()` blocks this thread until the async work completes — it wastes a thread-pool thread for as long as the work runs and can deadlock wherever a synchronization context is in play (a UI thread, or a caller that has one).
Sync-over-async blocking src/UniGetUI.Core.Classes/TaskRecycler.cs:99— `.GetAwaiter().GetResult()` blocks this thread until the async work completes — it wastes a thread-pool thread for as long as the work runs and can deadlock wherever a synchronization context is in play (a UI thread, or a caller that has one).
Sync-over-async blocking src/UniGetUI.Core.Data/CoreData.cs:517— `.Wait()` blocks this thread until the async work completes — it wastes a thread-pool thread for as long as the work runs and can deadlock wherever a synchronization context is in play (a UI thread, or a caller that has one).
Sync-over-async blocking src/UniGetUI.Core.Tools/IntegrityTester.cs:41— `.GetAwaiter().GetResult()` blocks this thread until the async work completes — it wastes a thread-pool thread for as long as the work runs and can deadlock wherever a synchronization context is in play (a UI thread, or a caller that has one).
Sync-over-async blocking src/UniGetUI.Core.Tools/ShortcutFileRemover.cs:203— `.GetAwaiter().GetResult()` blocks this thread until the async work completes — it wastes a thread-pool thread for as long as the work runs and can deadlock wherever a synchronization context is in play (a UI thread, or a caller that has one).
Sync-over-async blocking REDACTED:1521— `.GetAwaiter().GetResult()` blocks this thread until the async work completes — it wastes a thread-pool thread for as long as the work runs and can deadlock wherever a synchronization context is in play (a UI thread, or a caller that has one).
Sync-over-async blocking src/UniGetUI.Interface.IpcApi/IpcClient.cs:1573— `.GetAwaiter().GetResult()` blocks this thread until the async work completes — it wastes a thread-pool thread for as long as the work runs and can deadlock wherever a synchronization context is in play (a UI thread, or a caller that has one).
Sync-over-async blocking src/UniGetUI.Interface.IpcApi/IpcPackageApi.cs:754— `.GetAwaiter().GetResult()` blocks this thread until the async work completes — it wastes a thread-pool thread for as long as the work runs and can deadlock wherever a synchronization context is in play (a UI thread, or a caller that has one).
Sync-over-async blocking src/UniGetUI.PackageEngine.PackageManagerClasses/Manager/Helpers/BaseSourceHelper.cs:102— `task.Wait()` blocks this thread until the async work completes — it wastes a thread-pool thread for as long as the work runs and can deadlock wherever a synchronization context is in play (a UI thread, or a caller that has one).
Sync-over-async blocking src/UniGetUI.PackageEngine.PackageManagerClasses/Manager/PackageManager.cs:436— `.GetAwaiter().GetResult()` blocks this thread until the async work completes — it wastes a thread-pool thread for as long as the work runs and can deadlock wherever a synchronization context is in play (a UI thread, or a caller that has one).
Sync-over-async blocking src/UniGetUI.PackageEngine.PackageManagerClasses/Manager/PackageManager.cs:433— `task.Wait()` blocks this thread until the async work completes — it wastes a thread-pool thread for as long as the work runs and can deadlock wherever a synchronization context is in play (a UI thread, or a caller that has one).
Sync-over-async blocking src/UniGetUI.PackageEngine.Managers.Bun/Bun.cs:67— `.GetAwaiter().GetResult()` blocks this thread until the async work completes — it wastes a thread-pool thread for as long as the work runs and can deadlock wherever a synchronization context is in play (a UI thread, or a caller that has one).
+ 15 more in this group — see findings.md.
X2 · Cancellation propagation· Async method without CancellationToken · ×35
Async method without CancellationToken: ResumeStartupAfterMacOSEnvironment src/UniGetUI.Avalonia/App.axaml.cs:148— No CancellationToken parameter — this work can't be stopped early once started.
Async method without CancellationToken: StartupAsync src/UniGetUI.Avalonia/App.axaml.cs:288— No CancellationToken parameter — this work can't be stopped early once started.
Async method without CancellationToken: LoadAndCacheIconAsync src/UniGetUI.Avalonia/Models/PackageCollections.cs:719— No CancellationToken parameter — this work can't be stopped early once started.
Async method without CancellationToken: LoadIconAsync src/UniGetUI.Avalonia/Models/PackageRowModel.cs:162— No CancellationToken parameter — this work can't be stopped early once started.
Async method without CancellationToken: SaveWithAdminRightsAsync src/UniGetUI.Avalonia/Models/SoftwareCatalog.cs:95— No CancellationToken parameter — this work can't be stopped early once started.
Async method without CancellationToken: SaveAsync src/UniGetUI.Avalonia/Models/SoftwareCatalog.cs:109— No CancellationToken parameter — this work can't be stopped early once started.
Async method without CancellationToken: LoadAsync src/UniGetUI.Avalonia/Models/SoftwareCatalog.cs:149— No CancellationToken parameter — this work can't be stopped early once started.
Async method without CancellationToken: LoginAsync src/UniGetUI.Avalonia/ViewModels/Controls/UserAvatarViewModel.cs:138— No CancellationToken parameter — this work can't be stopped early once started.
Async method without CancellationToken: LoadAsync src/UniGetUI.Avalonia/ViewModels/DialogPages/CatalogEditorViewModel.cs:253— No CancellationToken parameter — this work can't be stopped early once started.
Async method without CancellationToken: SaveAsync src/UniGetUI.Avalonia/ViewModels/DialogPages/CatalogEditorViewModel.cs:293— No CancellationToken parameter — this work can't be stopped early once started.
Async method without CancellationToken: LoadIgnoredUpdatesAsync src/UniGetUI.Avalonia/ViewModels/DialogPages/InstallOptionsViewModel.cs:464— No CancellationToken parameter — this work can't be stopped early once started.
Async method without CancellationToken: ApplyIgnoredUpdatesAsync src/UniGetUI.Avalonia/ViewModels/DialogPages/InstallOptionsViewModel.cs:470— No CancellationToken parameter — this work can't be stopped early once started.
Async method without CancellationToken: RefreshCommandPreviewAsync src/UniGetUI.Avalonia/ViewModels/DialogPages/InstallOptionsViewModel.cs:527— No CancellationToken parameter — this work can't be stopped early once started.
Async method without CancellationToken: RefreshBrokerNoticesAsync src/UniGetUI.Avalonia/ViewModels/DialogPages/InstallOptionsViewModel.cs:545— No CancellationToken parameter — this work can't be stopped early once started.
Async method without CancellationToken: BuildCurrentCommandAsync src/UniGetUI.Avalonia/ViewModels/DialogPages/InstallOptionsViewModel.cs:632— No CancellationToken parameter — this work can't be stopped early once started.
Async method without CancellationToken: LoadIconAsync src/UniGetUI.Avalonia/ViewModels/DialogPages/InstallOptionsViewModel.cs:658— No CancellationToken parameter — this work can't be stopped early once started.
Async method without CancellationToken: LoadVersionsAsync src/UniGetUI.Avalonia/ViewModels/DialogPages/InstallOptionsViewModel.cs:682— No CancellationToken parameter — this work can't be stopped early once started.
Async method without CancellationToken: InitializeAsync src/UniGetUI.Avalonia/ViewModels/DialogPages/ManageAutoUpdatesViewModel.cs:71— No CancellationToken parameter — this work can't be stopped early once started.
Async method without CancellationToken: LoadIconAsync src/UniGetUI.Avalonia/ViewModels/DialogPages/ManageAutoUpdatesViewModel.cs:317— No CancellationToken parameter — this work can't be stopped early once started.
Async method without CancellationToken: ResetAll src/UniGetUI.Avalonia/ViewModels/DialogPages/ManageIgnoredUpdatesViewModel.cs:103— No CancellationToken parameter — this work can't be stopped early once started.
Async method without CancellationToken: Remove src/UniGetUI.Avalonia/ViewModels/DialogPages/ManageIgnoredUpdatesViewModel.cs:172— No CancellationToken parameter — this work can't be stopped early once started.
Async method without CancellationToken: RemoveAsync src/UniGetUI.Avalonia/ViewModels/DialogPages/ManageIgnoredUpdatesViewModel.cs:174— No CancellationToken parameter — this work can't be stopped early once started.
Async method without CancellationToken: RestoreToUpdatesAsync src/UniGetUI.Avalonia/ViewModels/DialogPages/ManageIgnoredUpdatesViewModel.cs:181— No CancellationToken parameter — this work can't be stopped early once started.
Async method without CancellationToken: LoadIconAsync src/UniGetUI.Avalonia/ViewModels/DialogPages/OperationViewModel.cs:159— No CancellationToken parameter — this work can't be stopped early once started.
Async method without CancellationToken: ShowInstallOptionsAsync src/UniGetUI.Avalonia/ViewModels/DialogPages/OperationViewModel.cs:350— No CancellationToken parameter — this work can't be stopped early once started.
TooManyMethods: MainWindow src/UniGetUI.Avalonia/Views/MainWindow.axaml.cs— TooManyMethods — 1412 significant lines (blank, comment-only and punctuation-only lines excluded), 111 methods, declared across 2 files: Views/MainWindow.axaml.cs (99), Views/MainWindow.MacMenu.cs (12). The bar is 30 methods; this is 81 over it, 3.70× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: IpcClient src/UniGetUI.Interface.IpcApi/IpcClient.cs— TooManyMethods — 874 significant lines (blank, comment-only and punctuation-only lines excluded), 107 methods. The bar is 30 methods; this is 77 over it, 3.57× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: IpcServer src/UniGetUI.Interface.IpcApi/IpcServer.cs— TooManyMethods — 1198 significant lines (blank, comment-only and punctuation-only lines excluded), 105 methods. The bar is 30 methods; this is 75 over it, 3.50× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: CoreTools REDACTED— TooManyMethods — 1085 significant lines (blank, comment-only and punctuation-only lines excluded), 86 methods. The bar is 30 methods; this is 56 over it, 2.87× the bar. The type holds no instance state, so there is no shared data to group its members by. To reduce it, split it by area instead: give each cohesive family of members its own smaller type, so no one type has to be read whole to change one of them.
TooManyMethods: PackageListPage src/UniGetUI.Tui/Views/Pages/PackageListPage.cs— TooManyMethods — 964 significant lines (blank, comment-only and punctuation-only lines excluded), 85 methods. The bar is 30 methods; this is 55 over it, 2.83× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: StartMenuShortcutsDatabase src/UniGetUI.PackageEngine.PackageManagerClasses/Packages/Classes/StartMenuShortcutsDatabase.cs— TooManyMethods — 740 significant lines (blank, comment-only and punctuation-only lines excluded), 68 methods. The bar is 30 methods; this is 38 over it, 2.27× the bar. The type holds no instance state, so there is no shared data to group its members by. To reduce it, split it by area instead: give each cohesive family of members its own smaller type, so no one type has to be read whole to change one of them.
TooManyMethods: PolicyEditorSessionViewModel src/UniGetUI.Avalonia/ViewModels/Pages/SettingsPages/PolicyEditor/PolicyEditorSessionViewModel.cs— TooManyMethods — 986 significant lines (blank, comment-only and punctuation-only lines excluded), 64 methods. The bar is 30 methods; this is 34 over it, 2.13× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: PackagesPageViewModel src/UniGetUI.Avalonia/ViewModels/SoftwarePages/PackagesPageViewModel.cs— TooManyMethods — 694 significant lines (blank, comment-only and punctuation-only lines excluded), 63 methods. The bar is 30 methods; this is 33 over it, 2.10× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: MainWindowViewModel src/UniGetUI.Avalonia/ViewModels/MainWindowViewModel.cs— TooManyMethods — 596 significant lines (blank, comment-only and punctuation-only lines excluded), 60 methods. The bar is 30 methods; this is 30 over it, 2.00× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: AvaloniaAutoUpdater src/UniGetUI.Avalonia/Infrastructure/AvaloniaAutoUpdater.cs— TooManyMethods — 979 significant lines (blank, comment-only and punctuation-only lines excluded), 55 methods. The bar is 30 methods; this is 25 over it, 1.83× the bar. The type holds no instance state, so there is no shared data to group its members by. To reduce it, split it by area instead: give each cohesive family of members its own smaller type, so no one type has to be read whole to change one of them.
TooManyMethods: AbstractPackagesPage src/UniGetUI.Avalonia/Views/SoftwarePages/AbstractPackagesPage.axaml.cs— TooManyMethods — 498 significant lines (blank, comment-only and punctuation-only lines excluded), 54 methods. The bar is 30 methods; this is 24 over it, 1.80× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: PackageOperation src/UniGetUI.PackageEngine.Operations/PackageOperations.cs— TooManyMethods — 741 significant lines (blank, comment-only and punctuation-only lines excluded), 53 methods. The bar is 30 methods; this is 23 over it, 1.77× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: SoftwareCatalogViewModel src/UniGetUI.Avalonia/ViewModels/SoftwarePages/SoftwareCatalogViewModel.cs— TooManyMethods — 494 significant lines (blank, comment-only and punctuation-only lines excluded), 52 methods. The bar is 30 methods; this is 22 over it, 1.73× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: MainWindow src/UniGetUI.Tui/Views/MainWindow.cs— TooManyMethods — 619 significant lines (blank, comment-only and punctuation-only lines excluded), 50 methods. The bar is 30 methods; this is 20 over it, 1.67× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: PackageDetailsWindow src/UniGetUI.Avalonia/Views/DialogPages/PackageDetailsWindow.axaml.cs— TooManyMethods — 716 significant lines (blank, comment-only and punctuation-only lines excluded), 49 methods. The bar is 30 methods; this is 19 over it, 1.63× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: WinGet src/UniGetUI.PackageEngine.Managers.WinGet/WinGet.cs— TooManyMethods — 601 significant lines (blank, comment-only and punctuation-only lines excluded), 48 methods. The bar is 30 methods; this is 18 over it, 1.60× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: AbstractOperation src/UniGetUI.PackageEngine.Operations/AbstractOperation.cs— TooManyMethods — 707 significant lines (blank, comment-only and punctuation-only lines excluded), 47 methods, declared across 2 files: UniGetUI.PackageEngine.Operations/AbstractOperation.cs (35), UniGetUI.PackageEngine.Operations/AbstractOperation_Progress.cs (12). The bar is 30 methods; this is 17 over it, 1.57× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: InstallOptionsViewModel src/UniGetUI.Avalonia/ViewModels/DialogPages/InstallOptionsViewModel.cs— TooManyMethods — 505 significant lines (blank, comment-only and punctuation-only lines excluded), 47 methods. The bar is 30 methods; this is 17 over it, 1.57× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: PolicyEditorSession src/UniGetUI.Avalonia/ViewModels/Pages/SettingsPages/PolicyEditor/PolicyEditorSession.cs— TooManyMethods — 486 significant lines (blank, comment-only and punctuation-only lines excluded), 43 methods. The bar is 30 methods; this is 13 over it, 1.43× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: AgentPolicyInspectorViewModel src/UniGetUI.Avalonia/ViewModels/Pages/SettingsPages/AgentPolicyInspectorViewModel.cs— TooManyMethods — 606 significant lines (blank, comment-only and punctuation-only lines excluded), 42 methods. The bar is 30 methods; this is 12 over it, 1.40× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: PackageWrapper src/UniGetUI.Avalonia/Models/PackageCollections.cs— TooManyMethods — 427 significant lines (blank, comment-only and punctuation-only lines excluded), 40 methods. The bar is 30 methods; this is 10 over it, 1.33× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: SidebarView src/UniGetUI.Avalonia/Views/SidebarView.axaml.cs— TooManyMethods — 446 significant lines (blank, comment-only and punctuation-only lines excluded), 39 methods. The bar is 30 methods; this is 9 over it, 1.30× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: IpcPackageApi src/UniGetUI.Interface.IpcApi/IpcPackageApi.cs— TooManyMethods — 413 significant lines (blank, comment-only and punctuation-only lines excluded), 39 methods. The bar is 30 methods; this is 9 over it, 1.30× the bar. The type holds no instance state, so there is no shared data to group its members by. To reduce it, split it by area instead: give each cohesive family of members its own smaller type, so no one type has to be read whole to change one of them.
TooManyMethods: Pip src/UniGetUI.PackageEngine.Managers.Pip/Pip.cs— TooManyMethods — 612 significant lines (blank, comment-only and punctuation-only lines excluded), 38 methods. The bar is 30 methods; this is 8 over it, 1.27× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: Settings src/UniGetUI.Core.Settings/SettingsEngine_Dictionaries.cs— TooManyMethods — 711 significant lines (blank, comment-only and punctuation-only lines excluded), 37 methods, declared across 6 files: UniGetUI.Core.Settings/SettingsEngine_Dictionaries.cs (10), UniGetUI.Core.Settings/SettingsEngine_Extras.cs (8), UniGetUI.Core.Settings/SettingsEngine_Lists.cs (8), UniGetUI.Core.Settings/SettingsEngine_ImportExport.cs (6), +2 more file(s). The bar is 30 methods; this is 7 over it, 1.23× the bar. The type holds no instance state, so there is no shared data to group its members by. To reduce it, split it by area instead: give each cohesive family of members its own smaller type, so no one type has to be read whole to change one of them.
Unfinished stub — throws NotImplementedException src/UniGetUI.PackageEngine.Managers.Apt/Helpers/AptPkgDetailsHelper.cs:119— `GetIcon_UnSafe` is a shipped member whose whole body throws NotImplementedException — scaffolding that was never completed. Implement it or remove the dead surface.
Unfinished stub — throws NotImplementedException src/UniGetUI.PackageEngine.Managers.Apt/Helpers/AptPkgDetailsHelper.cs:122— `GetScreenshots_UnSafe` is a shipped member whose whole body throws NotImplementedException — scaffolding that was never completed. Implement it or remove the dead surface.
Unfinished stub — throws NotImplementedException src/UniGetUI.PackageEngine.Managers.Cargo/Helpers/CargoPkgDetailsHelper.cs:74— `GetIcon_UnSafe` is a shipped member whose whole body throws NotImplementedException — scaffolding that was never completed. Implement it or remove the dead surface.
Unfinished stub — throws NotImplementedException src/UniGetUI.PackageEngine.Managers.Cargo/Helpers/CargoPkgDetailsHelper.cs:79— `GetScreenshots_UnSafe` is a shipped member whose whole body throws NotImplementedException — scaffolding that was never completed. Implement it or remove the dead surface.
Unfinished stub — throws NotImplementedException src/UniGetUI.PackageEngine.Managers.Dnf/Helpers/DnfPkgDetailsHelper.cs:102— `GetIcon_UnSafe` is a shipped member whose whole body throws NotImplementedException — scaffolding that was never completed. Implement it or remove the dead surface.
Unfinished stub — throws NotImplementedException src/UniGetUI.PackageEngine.Managers.Dnf/Helpers/DnfPkgDetailsHelper.cs:105— `GetScreenshots_UnSafe` is a shipped member whose whole body throws NotImplementedException — scaffolding that was never completed. Implement it or remove the dead surface.
Unfinished stub — throws NotImplementedException src/UniGetUI.PackageEngine.Managers.Flatpak/Helpers/FlatpakPkgDetailsHelper.cs:75— `GetIcon_UnSafe` is a shipped member whose whole body throws NotImplementedException — scaffolding that was never completed. Implement it or remove the dead surface.
Unfinished stub — throws NotImplementedException src/UniGetUI.PackageEngine.Managers.Generic.NuGet/BaseNuGetDetailsHelper.cs:567— `GetScreenshots_UnSafe` is a shipped member whose whole body throws NotImplementedException — scaffolding that was never completed. Implement it or remove the dead surface.
Unfinished stub — throws NotImplementedException src/UniGetUI.PackageEngine.Managers.Homebrew/Helpers/HomebrewPkgDetailsHelper.cs:99— `GetIcon_UnSafe` is a shipped member whose whole body throws NotImplementedException — scaffolding that was never completed. Implement it or remove the dead surface.
Unfinished stub — throws NotImplementedException src/UniGetUI.PackageEngine.Managers.Homebrew/Helpers/HomebrewPkgDetailsHelper.cs:102— `GetScreenshots_UnSafe` is a shipped member whose whole body throws NotImplementedException — scaffolding that was never completed. Implement it or remove the dead surface.
Unfinished stub — throws NotImplementedException src/UniGetUI.PackageEngine.Managers.Npm/Helpers/NpmPkgDetailsHelper.cs:165— `GetIcon_UnSafe` is a shipped member whose whole body throws NotImplementedException — scaffolding that was never completed. Implement it or remove the dead surface.
Unfinished stub — throws NotImplementedException src/UniGetUI.PackageEngine.Managers.Npm/Helpers/NpmPkgDetailsHelper.cs:170— `GetScreenshots_UnSafe` is a shipped member whose whole body throws NotImplementedException — scaffolding that was never completed. Implement it or remove the dead surface.
Unfinished stub — throws NotImplementedException src/UniGetUI.PackageEngine.Managers.Pacman/Helpers/PacmanPkgDetailsHelper.cs:123— `GetIcon_UnSafe` is a shipped member whose whole body throws NotImplementedException — scaffolding that was never completed. Implement it or remove the dead surface.
Unfinished stub — throws NotImplementedException src/UniGetUI.PackageEngine.Managers.Pacman/Helpers/PacmanPkgDetailsHelper.cs:126— `GetScreenshots_UnSafe` is a shipped member whose whole body throws NotImplementedException — scaffolding that was never completed. Implement it or remove the dead surface.
Unfinished stub — throws NotImplementedException src/UniGetUI.PackageEngine.Managers.Pip/Helpers/PipPkgDetailsHelper.cs:126— `GetIcon_UnSafe` is a shipped member whose whole body throws NotImplementedException — scaffolding that was never completed. Implement it or remove the dead surface.
Unfinished stub — throws NotImplementedException src/UniGetUI.PackageEngine.Managers.Pip/Helpers/PipPkgDetailsHelper.cs:131— `GetScreenshots_UnSafe` is a shipped member whose whole body throws NotImplementedException — scaffolding that was never completed. Implement it or remove the dead surface.
Unfinished stub — throws NotImplementedException src/UniGetUI.PackageEngine.Managers.Scoop/Helpers/ScoopPkgDetailsHelper.cs:285— `GetIcon_UnSafe` is a shipped member whose whole body throws NotImplementedException — scaffolding that was never completed. Implement it or remove the dead surface.
Unfinished stub — throws NotImplementedException src/UniGetUI.PackageEngine.Managers.Scoop/Helpers/ScoopPkgDetailsHelper.cs:290— `GetScreenshots_UnSafe` is a shipped member whose whole body throws NotImplementedException — scaffolding that was never completed. Implement it or remove the dead surface.
Unfinished stub — throws NotImplementedException src/UniGetUI.PackageEngine.Managers.Snap/Helpers/SnapPkgDetailsHelper.cs:118— `GetIcon_UnSafe` is a shipped member whose whole body throws NotImplementedException — scaffolding that was never completed. Implement it or remove the dead surface.
Unfinished stub — throws NotImplementedException src/UniGetUI.PackageEngine.Managers.Vcpkg/Helpers/VcpkgPkgDetailsHelper.cs:95— `GetIcon_UnSafe` is a shipped member whose whole body throws NotImplementedException — scaffolding that was never completed. Implement it or remove the dead surface.
Unfinished stub — throws NotImplementedException src/UniGetUI.PackageEngine.Managers.Vcpkg/Helpers/VcpkgPkgDetailsHelper.cs:100— `GetScreenshots_UnSafe` is a shipped member whose whole body throws NotImplementedException — scaffolding that was never completed. Implement it or remove the dead surface.
Unfinished stub — throws NotImplementedException src/UniGetUI.PackageEngine.Managers.Vcpkg/Helpers/VcpkgPkgDetailsHelper.cs:123— `GetInstallableVersions_UnSafe` is a shipped member whose whole body throws NotImplementedException — scaffolding that was never completed. Implement it or remove the dead surface.
Unfinished stub — throws NotImplementedException src/UniGetUI.PackageEngine.Managers.Vcpkg/Helpers/VcpkgSourceHelper.cs:13— `GetAddSourceParameters` is a shipped member whose whole body throws NotImplementedException — scaffolding that was never completed. Implement it or remove the dead surface.
Unfinished stub — throws NotImplementedException src/UniGetUI.PackageEngine.Managers.Vcpkg/Helpers/VcpkgSourceHelper.cs:16— `GetRemoveSourceParameters` is a shipped member whose whole body throws NotImplementedException — scaffolding that was never completed. Implement it or remove the dead surface.
Unfinished stub — throws NotImplementedException src/UniGetUI.PackageEngine.Managers.Vcpkg/Helpers/VcpkgSourceHelper.cs:19— `_getAddSourceOperationVeredict` is a shipped member whose whole body throws NotImplementedException — scaffolding that was never completed. Implement it or remove the dead surface.
Swallowed exception (empty catch) src/UniGetUI.Avalonia/App.axaml.cs:304— 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.
Swallowed exception (empty catch) src/UniGetUI.Avalonia/CrashHandler.cs:168— 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.
Swallowed exception (empty catch) src/UniGetUI.Avalonia/CrashHandler.cs:263— 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.
Swallowed exception (empty catch) src/UniGetUI.Avalonia/CrashHandler.cs:278— 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.
Swallowed exception (empty catch) src/UniGetUI.Avalonia/Models/PackageRowModel.cs:184— 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.
Swallowed exception (empty catch) src/UniGetUI.Avalonia/Program.cs:26— 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.
Swallowed exception (empty catch) src/UniGetUI.Avalonia/ViewModels/DialogPages/OperationViewModel.cs:184— 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.
Swallowed exception (empty catch) src/UniGetUI.Avalonia/ViewModels/DialogPages/OperationViewModel.cs:192— 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.
Swallowed exception (empty catch) src/UniGetUI.Avalonia/ViewModels/DialogPages/PackageDetailsViewModel.cs:343— 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.
Swallowed exception (empty catch) src/UniGetUI.Avalonia/ViewModels/DialogPages/PackageDetailsViewModel.cs:367— 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.
Swallowed exception (empty catch) src/UniGetUI.Avalonia/ViewModels/DialogPages/PackageDetailsViewModel.cs:382— 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.
Swallowed exception (empty catch) src/UniGetUI.Avalonia/ViewModels/Pages/AboutPages/ContributorsViewModel.cs:36— 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.
Swallowed exception (empty catch) src/UniGetUI.Avalonia/ViewModels/Pages/AboutPages/TranslatorsViewModel.cs:38— 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.
Swallowed exception (empty catch) src/UniGetUI.Avalonia/ViewModels/Pages/SettingsPages/PolicyEditor/PolicyEditorSessionViewModel.cs:1136— 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.
Swallowed exception (empty catch) src/UniGetUI.Avalonia/Views/Controls/SvgIcon.cs:157— 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.
Swallowed exception (empty catch) src/UniGetUI.Avalonia/Views/Controls/SvgIcon.cs:175— 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.
Swallowed exception (empty catch) src/UniGetUI.Avalonia/Views/DialogPages/CrashReportWindow.axaml.cs:60— 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.
Swallowed exception (empty catch) src/UniGetUI.Avalonia/Views/MainWindow.axaml.cs:1447— 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.
Swallowed exception (empty catch) src/Shared/AutoUpdater.Helpers.cs:478— 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.
Swallowed exception (empty catch) src/Shared/AutoUpdater.Helpers.cs:513— 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.
Swallowed exception (empty catch) src/Shared/AutoUpdater.Helpers.cs:665— 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.
Swallowed exception (empty catch) src/UniGetUI.Avalonia/Infrastructure/MicaWindowHelper.cs:187— 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.
Swallowed exception (empty catch) src/UniGetUI.Avalonia/Infrastructure/AvaloniaAutoUpdater.cs:157— 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.
Swallowed exception (empty catch) src/UniGetUI.Avalonia/Infrastructure/AvaloniaAutoUpdater.cs:241— 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.
Swallowed exception (empty catch) src/UniGetUI.Avalonia/Infrastructure/AvaloniaAutoUpdater.cs:1322— 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.
FileTooLong: Views/MainWindow.axaml.cs src/UniGetUI.Avalonia/Views/MainWindow.axaml.cs— FileTooLong — 1390 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 890 over it, 2.78× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: UniGetUI.Interface.IpcApi/IpcServer.cs src/UniGetUI.Interface.IpcApi/IpcServer.cs— FileTooLong — 1222 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 722 over it, 2.44× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: REDACTED REDACTED— FileTooLong — 1200 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 700 over it, 2.40× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: Pages/PackageListPage.cs src/UniGetUI.Tui/Views/Pages/PackageListPage.cs— FileTooLong — 1054 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 554 over it, 2.11× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: Infrastructure/AvaloniaAutoUpdater.cs src/UniGetUI.Avalonia/Infrastructure/AvaloniaAutoUpdater.cs— FileTooLong — 1033 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 533 over it, 2.07× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: PolicyEditor/PolicyEditorSessionViewModel.cs src/UniGetUI.Avalonia/ViewModels/Pages/SettingsPages/PolicyEditor/PolicyEditorSessionViewModel.cs— FileTooLong — 1005 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 505 over it, 2.01× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: UniGetUI.PackageEngine.Operations/PackageOperations.cs src/UniGetUI.PackageEngine.Operations/PackageOperations.cs— FileTooLong — 977 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 477 over it, 1.95× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: UniGetUI.Interface.IpcApi/IpcClient.cs src/UniGetUI.Interface.IpcApi/IpcClient.cs— FileTooLong — 888 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 388 over it, 1.78× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: PolicyEditor/PolicyEditorStructuredUi.cs src/UniGetUI.Avalonia/ViewModels/Pages/SettingsPages/PolicyEditor/PolicyEditorStructuredUi.cs— FileTooLong — 868 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 368 over it, 1.74× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: SoftwarePages/PackagesPageViewModel.cs src/UniGetUI.Avalonia/ViewModels/SoftwarePages/PackagesPageViewModel.cs— FileTooLong — 793 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 293 over it, 1.59× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: Classes/StartMenuShortcutsDatabase.cs src/UniGetUI.PackageEngine.PackageManagerClasses/Packages/Classes/StartMenuShortcutsDatabase.cs— FileTooLong — 749 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 249 over it, 1.50× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: DialogPages/PackageDetailsWindow.axaml.cs src/UniGetUI.Avalonia/Views/DialogPages/PackageDetailsWindow.axaml.cs— FileTooLong — 743 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 243 over it, 1.49× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: UniGetUI.PackageEngine.Managers.WinGet/WinGet.cs src/UniGetUI.PackageEngine.Managers.WinGet/WinGet.cs— FileTooLong — 649 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 149 over it, 1.30× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: SettingsPages/AgentPolicyInspectorViewModel.cs src/UniGetUI.Avalonia/ViewModels/Pages/SettingsPages/AgentPolicyInspectorViewModel.cs— FileTooLong — 644 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 144 over it, 1.29× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: Views/MainWindow.cs src/UniGetUI.Tui/Views/MainWindow.cs— FileTooLong — 642 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 142 over it, 1.28× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: UniGetUI.PackageEngine.Managers.Pip/Pip.cs src/UniGetUI.PackageEngine.Managers.Pip/Pip.cs— FileTooLong — 633 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 133 over it, 1.27× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: UniGetUI.Interface.IpcApi/IpcCliCommandRunner.cs src/UniGetUI.Interface.IpcApi/IpcCliCommandRunner.cs— FileTooLong — 628 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 128 over it, 1.26× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: ViewModels/MainWindowViewModel.cs src/UniGetUI.Avalonia/ViewModels/MainWindowViewModel.cs— FileTooLong — 624 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 124 over it, 1.25× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: SoftwarePages/SoftwareCatalogViewModel.cs src/UniGetUI.Avalonia/ViewModels/SoftwarePages/SoftwareCatalogViewModel.cs— FileTooLong — 605 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 105 over it, 1.21× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: ClientHelpers/PingetPackageDetailsProvider.cs src/UniGetUI.PackageEngine.Managers.WinGet/ClientHelpers/PingetPackageDetailsProvider.cs— FileTooLong — 570 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 70 over it, 1.14× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: PolicyEditor/PolicyValidationFinding.cs src/UniGetUI.Avalonia/ViewModels/Pages/SettingsPages/PolicyEditor/PolicyValidationFinding.cs— FileTooLong — 561 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 61 over it, 1.12× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: Internal/NuGetV3Client.cs src/UniGetUI.PackageEngine.Managers.Generic.NuGet/Internal/NuGetV3Client.cs— FileTooLong — 551 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 51 over it, 1.10× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: DialogPages/InstallOptionsViewModel.cs src/UniGetUI.Avalonia/ViewModels/DialogPages/InstallOptionsViewModel.cs— FileTooLong — 538 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 38 over it, 1.08× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: Models/PackageCollections.cs src/UniGetUI.Avalonia/Models/PackageCollections.cs— FileTooLong — 527 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 27 over it, 1.05× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: SoftwarePages/AbstractPackagesPage.axaml.cs src/UniGetUI.Avalonia/Views/SoftwarePages/AbstractPackagesPage.axaml.cs— FileTooLong — 527 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 27 over it, 1.05× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
Hotspot: src/UniGetUI.Avalonia/Views/MainWindow.axaml.cs src/UniGetUI.Avalonia/Views/MainWindow.axaml.cs:1451— src/UniGetUI.Avalonia/Views/MainWindow.axaml.cs changed 28 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 48 in MainWindow.OnWindowsWndProc at line 1451. 6 of those changes were fix/bug commits, and the other 22 changed it for other reasons — this file is under both repair and feature pressure. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-07-24..2026-10-22, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-24 15:53:23 -04:00' --until='2026-10-22 15:53:23 -04:00' --full-history --no-merges -- src/UniGetUI.Avalonia/Views/MainWindow.axaml.cs`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: src/UniGetUI.Avalonia/Views/SoftwarePages/AbstractPackagesPage.axaml.cs src/UniGetUI.Avalonia/Views/SoftwarePages/AbstractPackagesPage.axaml.cs:47— src/UniGetUI.Avalonia/Views/SoftwarePages/AbstractPackagesPage.axaml.cs changed 14 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 29 in AbstractPackagesPage.AbstractPackagesPage.ctor at line 47. 4 of those changes were fix/bug commits, and the other 10 changed it for other reasons — this file is under both repair and feature pressure. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-07-24..2026-10-22, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-24 15:53:23 -04:00' --until='2026-10-22 15:53:23 -04:00' --full-history --no-merges -- src/UniGetUI.Avalonia/Views/SoftwarePages/AbstractPackagesPage.axaml.cs`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: src/UniGetUI.PackageEngine.Managers.WinGet/Helpers/WinGetPkgOperationHelper.cs src/UniGetUI.PackageEngine.Managers.WinGet/Helpers/WinGetPkgOperationHelper.cs:331— src/UniGetUI.PackageEngine.Managers.WinGet/Helpers/WinGetPkgOperationHelper.cs changed 13 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 31 in WinGetPkgOperationHelper._getOperationResult at line 331. 1 of those changes was a fix/bug commit, and the other 12 changed it for other reasons — this file is under both repair and feature pressure. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-07-24..2026-10-22, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-24 15:53:23 -04:00' --until='2026-10-22 15:53:23 -04:00' --full-history --no-merges -- src/UniGetUI.PackageEngine.Managers.WinGet/Helpers/WinGetPkgOperationHelper.cs`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: src/UniGetUI.PackageEngine.Operations/PackageOperations.cs src/UniGetUI.PackageEngine.Operations/PackageOperations.cs:1469— src/UniGetUI.PackageEngine.Operations/PackageOperations.cs changed 18 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 19 in PackageOperation._getPostInstallOps at line 1469. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-07-24..2026-10-22, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-24 15:53:23 -04:00' --until='2026-10-22 15:53:23 -04:00' --full-history --no-merges -- src/UniGetUI.PackageEngine.Operations/PackageOperations.cs`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: src/UniGetUI.Avalonia/ViewModels/SoftwarePages/PackagesPageViewModel.cs src/UniGetUI.Avalonia/ViewModels/SoftwarePages/PackagesPageViewModel.cs:713— src/UniGetUI.Avalonia/ViewModels/SoftwarePages/PackagesPageViewModel.cs changed 17 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 16 in PackagesPageViewModel.BuildPackageFilter at line 713. 3 of those changes were fix/bug commits, and the other 14 changed it for other reasons — this file is under both repair and feature pressure. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-07-24..2026-10-22, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-24 15:53:23 -04:00' --until='2026-10-22 15:53:23 -04:00' --full-history --no-merges -- src/UniGetUI.Avalonia/ViewModels/SoftwarePages/PackagesPageViewModel.cs`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: src/UniGetUI.PackageEngine.Operations/AbstractOperation.cs src/UniGetUI.PackageEngine.Operations/AbstractOperation.cs:257— src/UniGetUI.PackageEngine.Operations/AbstractOperation.cs changed 8 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 30 in AbstractOperation.MainThreadCore at line 257. 1 of those changes was a fix/bug commit, and the other 7 changed it for other reasons — this file is under both repair and feature pressure. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-07-24..2026-10-22, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-24 15:53:23 -04:00' --until='2026-10-22 15:53:23 -04:00' --full-history --no-merges -- src/UniGetUI.PackageEngine.Operations/AbstractOperation.cs`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: REDACTED REDACTED:697— REDACTED changed 14 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 16 in CoreTools.VersionStringToStruct at line 697. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-07-24..2026-10-22, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-24 15:53:23 -04:00' --until='2026-10-22 15:53:23 -04:00' --full-history --no-merges -- REDACTED`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: src/UniGetUI.Avalonia/ViewModels/MainWindowViewModel.cs src/UniGetUI.Avalonia/ViewModels/MainWindowViewModel.cs:426— src/UniGetUI.Avalonia/ViewModels/MainWindowViewModel.cs changed 14 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 15 in MainWindowViewModel.MainWindowViewModel.ctor at line 426. 2 of those changes were fix/bug commits, and the other 12 changed it for other reasons — this file is under both repair and feature pressure. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-07-24..2026-10-22, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-24 15:53:23 -04:00' --until='2026-10-22 15:53:23 -04:00' --full-history --no-merges -- src/UniGetUI.Avalonia/ViewModels/MainWindowViewModel.cs`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: src/UniGetUI.PackageEngine.Operations/AbstractProcessOperation.cs src/UniGetUI.PackageEngine.Operations/AbstractProcessOperation.cs:96— src/UniGetUI.PackageEngine.Operations/AbstractProcessOperation.cs changed 5 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 29 in AbstractProcessOperation.PerformOperation at line 96. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-07-24..2026-10-22, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-24 15:53:23 -04:00' --until='2026-10-22 15:53:23 -04:00' --full-history --no-merges -- src/UniGetUI.PackageEngine.Operations/AbstractProcessOperation.cs`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: src/UniGetUI.PackageEngine.PackageLoader/AbstractPackageLoader.cs src/UniGetUI.PackageEngine.PackageLoader/AbstractPackageLoader.cs:159— src/UniGetUI.PackageEngine.PackageLoader/AbstractPackageLoader.cs changed 5 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 28 in AbstractPackageLoader.ReloadPackages at line 159. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-07-24..2026-10-22, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-24 15:53:23 -04:00' --until='2026-10-22 15:53:23 -04:00' --full-history --no-merges -- src/UniGetUI.PackageEngine.PackageLoader/AbstractPackageLoader.cs`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: src/UniGetUI.Avalonia/Infrastructure/AvaloniaAutoUpdater.cs src/UniGetUI.Avalonia/Infrastructure/AvaloniaAutoUpdater.cs:459— src/UniGetUI.Avalonia/Infrastructure/AvaloniaAutoUpdater.cs changed 6 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 23 in AvaloniaAutoUpdater.CheckAndInstallUpdatesCoreAsync at line 459. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-07-24..2026-10-22, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-24 15:53:23 -04:00' --until='2026-10-22 15:53:23 -04:00' --full-history --no-merges -- src/UniGetUI.Avalonia/Infrastructure/AvaloniaAutoUpdater.cs`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: src/UniGetUI.PackageEngine.Managers.PowerShell/Helpers/PowerShellPkgOperationHelper.cs src/UniGetUI.PackageEngine.Managers.PowerShell/Helpers/PowerShellPkgOperationHelper.cs:21— src/UniGetUI.PackageEngine.Managers.PowerShell/Helpers/PowerShellPkgOperationHelper.cs changed 4 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 34 in PowerShellPkgOperationHelper._getOperationParameters at line 21. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-07-24..2026-10-22, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-24 15:53:23 -04:00' --until='2026-10-22 15:53:23 -04:00' --full-history --no-merges -- src/UniGetUI.PackageEngine.Managers.PowerShell/Helpers/PowerShellPkgOperationHelper.cs`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: src/UniGetUI.Avalonia/ViewModels/DialogPages/InstallOptionsViewModel.cs src/UniGetUI.Avalonia/ViewModels/DialogPages/InstallOptionsViewModel.cs:268— src/UniGetUI.Avalonia/ViewModels/DialogPages/InstallOptionsViewModel.cs changed 6 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 17 in InstallOptionsViewModel.InstallOptionsViewModel.ctor at line 268. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-07-24..2026-10-22, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-24 15:53:23 -04:00' --until='2026-10-22 15:53:23 -04:00' --full-history --no-merges -- src/UniGetUI.Avalonia/ViewModels/DialogPages/InstallOptionsViewModel.cs`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: src/UniGetUI.PackageEngine.AgentBroker/BrokerRequestBuilder.cs src/UniGetUI.PackageEngine.AgentBroker/BrokerRequestBuilder.cs:201— src/UniGetUI.PackageEngine.AgentBroker/BrokerRequestBuilder.cs changed 5 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 19 in BrokerRequestBuilder.TryMapManagerName at line 201. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-07-24..2026-10-22, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-24 15:53:23 -04:00' --until='2026-10-22 15:53:23 -04:00' --full-history --no-merges -- src/UniGetUI.PackageEngine.AgentBroker/BrokerRequestBuilder.cs`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: src/UniGetUI.PackageEngine.Managers.Generic.NuGet/BaseNuGet.cs src/UniGetUI.PackageEngine.Managers.Generic.NuGet/BaseNuGet.cs:99— src/UniGetUI.PackageEngine.Managers.Generic.NuGet/BaseNuGet.cs changed 5 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 17 in BaseNuGet.FindPackages_UnSafe at line 99. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-07-24..2026-10-22, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-24 15:53:23 -04:00' --until='2026-10-22 15:53:23 -04:00' --full-history --no-merges -- src/UniGetUI.PackageEngine.Managers.Generic.NuGet/BaseNuGet.cs`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: src/UniGetUI.PackageEngine.Managers.Scoop/Helpers/ScoopPkgDetailsHelper.cs src/UniGetUI.PackageEngine.Managers.Scoop/Helpers/ScoopPkgDetailsHelper.cs:17— src/UniGetUI.PackageEngine.Managers.Scoop/Helpers/ScoopPkgDetailsHelper.cs changed 3 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 28 in ScoopPkgDetailsHelper.GetDetails_UnSafe at line 17. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-07-24..2026-10-22, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-24 15:53:23 -04:00' --until='2026-10-22 15:53:23 -04:00' --full-history --no-merges -- src/UniGetUI.PackageEngine.Managers.Scoop/Helpers/ScoopPkgDetailsHelper.cs`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: src/UniGetUI.PackageEngine.Managers.Generic.NuGet/BaseNuGetDetailsHelper.cs src/UniGetUI.PackageEngine.Managers.Generic.NuGet/BaseNuGetDetailsHelper.cs:20— src/UniGetUI.PackageEngine.Managers.Generic.NuGet/BaseNuGetDetailsHelper.cs changed 3 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 23 in BaseNuGetDetailsHelper.GetDetails_UnSafe at line 20. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-07-24..2026-10-22, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-24 15:53:23 -04:00' --until='2026-10-22 15:53:23 -04:00' --full-history --no-merges -- src/UniGetUI.PackageEngine.Managers.Generic.NuGet/BaseNuGetDetailsHelper.cs`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: src/UniGetUI.PackageEngine.Operations/DownloadOperation.cs src/UniGetUI.PackageEngine.Operations/DownloadOperation.cs:114— src/UniGetUI.PackageEngine.Operations/DownloadOperation.cs changed 3 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 20 in DownloadOperation.PerformOperation at line 114. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-07-24..2026-10-22, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-24 15:53:23 -04:00' --until='2026-10-22 15:53:23 -04:00' --full-history --no-merges -- src/UniGetUI.PackageEngine.Operations/DownloadOperation.cs`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: src/UniGetUI.PackageEngine.Managers.Dotnet/Helpers/DotNetPkgOperationHelper.cs src/UniGetUI.PackageEngine.Managers.Dotnet/Helpers/DotNetPkgOperationHelper.cs:15— src/UniGetUI.PackageEngine.Managers.Dotnet/Helpers/DotNetPkgOperationHelper.cs changed 3 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 20 in DotNetPkgOperationHelper._getOperationParameters at line 15. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-07-24..2026-10-22, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-24 15:53:23 -04:00' --until='2026-10-22 15:53:23 -04:00' --full-history --no-merges -- src/UniGetUI.PackageEngine.Managers.Dotnet/Helpers/DotNetPkgOperationHelper.cs`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: src/UniGetUI.Avalonia/CrashHandler.cs src/UniGetUI.Avalonia/CrashHandler.cs:142— src/UniGetUI.Avalonia/CrashHandler.cs changed 3 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 17 in CrashHandler.ReportFatalException at line 142. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-07-24..2026-10-22, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-24 15:53:23 -04:00' --until='2026-10-22 15:53:23 -04:00' --full-history --no-merges -- src/UniGetUI.Avalonia/CrashHandler.cs`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: src/UniGetUI.Avalonia/ViewModels/SoftwarePages/SoftwareCatalogViewModel.cs src/UniGetUI.Avalonia/ViewModels/SoftwarePages/SoftwareCatalogViewModel.cs:325— src/UniGetUI.Avalonia/ViewModels/SoftwarePages/SoftwareCatalogViewModel.cs changed 3 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 15 in SoftwareCatalogViewModel.RefreshAsync at line 325. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-07-24..2026-10-22, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-24 15:53:23 -04:00' --until='2026-10-22 15:53:23 -04:00' --full-history --no-merges -- src/UniGetUI.Avalonia/ViewModels/SoftwarePages/SoftwareCatalogViewModel.cs`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: src/Shared/SharedPreUiCommandDispatcher.cs src/Shared/SharedPreUiCommandDispatcher.cs:72— src/Shared/SharedPreUiCommandDispatcher.cs changed 3 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 15 in SharedPreUiCommandDispatcher.TryHandle at line 72. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-07-24..2026-10-22, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-24 15:53:23 -04:00' --until='2026-10-22 15:53:23 -04:00' --full-history --no-merges -- src/Shared/SharedPreUiCommandDispatcher.cs`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: src/UniGetUI.PackageEngine.PackageLoader/UpgradablePackagesLoader.cs src/UniGetUI.PackageEngine.PackageLoader/UpgradablePackagesLoader.cs:32— src/UniGetUI.PackageEngine.PackageLoader/UpgradablePackagesLoader.cs changed 3 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 15 in UpgradablePackagesLoader.IsPackageValid at line 32. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-07-24..2026-10-22, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-24 15:53:23 -04:00' --until='2026-10-22 15:53:23 -04:00' --full-history --no-merges -- src/UniGetUI.PackageEngine.PackageLoader/UpgradablePackagesLoader.cs`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: src/UniGetUI.PackageEngine.Managers.PowerShell7/Helpers/PowerShell7PkgOperationHelper.cs src/UniGetUI.PackageEngine.Managers.PowerShell7/Helpers/PowerShell7PkgOperationHelper.cs:15— src/UniGetUI.PackageEngine.Managers.PowerShell7/Helpers/PowerShell7PkgOperationHelper.cs changed 2 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 19 in PowerShell7PkgOperationHelper._getOperationParameters at line 15. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-07-24..2026-10-22, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-24 15:53:23 -04:00' --until='2026-10-22 15:53:23 -04:00' --full-history --no-merges -- src/UniGetUI.PackageEngine.Managers.PowerShell7/Helpers/PowerShell7PkgOperationHelper.cs`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: src/UniGetUI.Avalonia/ViewModels/Pages/LogPages/OperationHistoryPageViewModel.cs src/UniGetUI.Avalonia/ViewModels/Pages/LogPages/OperationHistoryPageViewModel.cs:49— src/UniGetUI.Avalonia/ViewModels/Pages/LogPages/OperationHistoryPageViewModel.cs changed 2 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 18 in OperationHistoryPageViewModel.BuildHeader at line 49. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-07-24..2026-10-22, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-24 15:53:23 -04:00' --until='2026-10-22 15:53:23 -04:00' --full-history --no-merges -- src/UniGetUI.Avalonia/ViewModels/Pages/LogPages/OperationHistoryPageViewModel.cs`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Outbound HTTP without resilience src/UniGetUI.Avalonia/ViewModels/Controls/UserAvatarViewModel.cs:94— `new HttpClient(CoreTools.GenericHttpClientParameters)` 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).
Outbound HTTP without resilience src/UniGetUI.Avalonia/ViewModels/DialogPages/InstallOptionsViewModel.cs:653— `new(CoreTools.GenericHttpClientParameters)` 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).
Outbound HTTP without resilience src/UniGetUI.Avalonia/ViewModels/DialogPages/OperationViewModel.cs:167— `new HttpClient(CoreTools.GenericHttpClientParameters)` 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).
Outbound HTTP without resilience src/UniGetUI.Avalonia/ViewModels/DialogPages/PackageDetailsViewModel.cs:319— `new HttpClient(CoreTools.GenericHttpClientParameters)` 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).
Outbound HTTP without resilience src/UniGetUI.Avalonia/ViewModels/DialogPages/PackageDetailsViewModel.cs:353— `new HttpClient(CoreTools.GenericHttpClientParameters)` 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).
Outbound HTTP without resilience src/UniGetUI.Avalonia/ViewModels/Pages/AboutPages/ContributorsViewModel.cs:31— `new HttpClient(CoreTools.GenericHttpClientParameters)` 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).
Outbound HTTP without resilience src/UniGetUI.Avalonia/ViewModels/Pages/AboutPages/TranslatorsViewModel.cs:33— `new HttpClient(CoreTools.GenericHttpClientParameters)` 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).
Outbound HTTP without resilience src/UniGetUI.Avalonia/ViewModels/Pages/SettingsPages/BackupViewModel.cs:236— `new HttpClient(CoreTools.GenericHttpClientParameters)` 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).
Outbound HTTP without resilience src/UniGetUI.Core.IconStore/IconCacheEngine.cs:236— `new(CoreTools.GenericHttpClientParameters)` 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).
Outbound HTTP without resilience src/UniGetUI.Core.IconStore/IconDatabase.cs:75— `new(CoreTools.GenericHttpClientParameters)` 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).
Outbound HTTP without resilience REDACTED:477— `new(CoreTools.GenericHttpClientParameters)` 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).
Outbound HTTP without resilience REDACTED:500— `new(handler)` 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).
Outbound HTTP without resilience src/UniGetUI.Interface.IpcApi/GitHubApiClient.cs:18— `new HttpClient(CoreTools.GenericHttpClientParameters) { BaseAddress = GitHubA...` 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).
Outbound HTTP without resilience src/UniGetUI.PackageEngine.Managers.Bun/Bun.cs:65— `new(CoreTools.GenericHttpClientParameters)` 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).
Outbound HTTP without resilience REDACTED:132— `new(CoreTools.GenericHttpClientParameters)` 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).
Outbound HTTP without resilience src/UniGetUI.PackageEngine.Managers.Generic.NuGet/BaseNuGet.cs:157— `new(CoreTools.GenericHttpClientParameters)` 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).
Outbound HTTP without resilience src/UniGetUI.PackageEngine.Managers.Generic.NuGet/BaseNuGet.cs:501— `new(CoreTools.GenericHttpClientParameters)` 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).
Outbound HTTP without resilience src/UniGetUI.PackageEngine.Managers.Generic.NuGet/BaseNuGetDetailsHelper.cs:613— `new(CoreTools.GenericHttpClientParameters)` 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).
Outbound HTTP without resilience src/UniGetUI.PackageEngine.Managers.Generic.NuGet/Internal/NuGetManifestLoader.cs:91— `new(CoreTools.GenericHttpClientParameters)` 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).
Outbound HTTP without resilience src/UniGetUI.PackageEngine.Managers.Generic.NuGet/Internal/NuGetV3Client.cs:48— `new(CoreTools.GenericHttpClientParameters)` 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).
Outbound HTTP without resilience src/UniGetUI.PackageEngine.Managers.Pip/Helpers/PipPkgDetailsHelper.cs:24— `new(CoreTools.GenericHttpClientParameters)` 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).
Outbound HTTP without resilience src/UniGetUI.PackageEngine.Managers.Pip/Pip.cs:127— `new HttpClient(CoreTools.GenericHttpClientParameters)` 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).
Outbound HTTP without resilience src/UniGetUI.PackageEngine.Managers.Pip/Pip.cs:199— `new(CoreTools.GenericHttpClientParameters)` 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).
Outbound HTTP without resilience src/UniGetUI.PackageEngine.Managers.Vcpkg/Helpers/VcpkgPkgDetailsHelper.cs:30— `new(CoreTools.GenericHttpClientParameters)` 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).
MethodTooLong: IpcCliCommandRunner.RunAsync src/UniGetUI.Interface.IpcApi/IpcCliCommandRunner.cs:19— MethodTooLong — RunAsync runs 408 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 308 over it, 4.08× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: PackageManagerPage.BuildPage src/UniGetUI.Avalonia/Views/Pages/SettingsPages/PackageManagerPage.axaml.cs:56— MethodTooLong — BuildPage runs 232 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 132 over it, 2.32× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: IpcServer.Start src/UniGetUI.Interface.IpcApi/IpcServer.cs:63— MethodTooLong — Start runs 223 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 123 over it, 2.23× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: PolicyEditorSessionViewModel.SaveCoreAsync src/UniGetUI.Avalonia/ViewModels/Pages/SettingsPages/PolicyEditor/PolicyEditorSessionViewModel.cs:509— MethodTooLong — SaveCoreAsync runs 218 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 118 over it, 2.18× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: AvaloniaAutoUpdater.CheckAndInstallUpdatesCoreAsync src/UniGetUI.Avalonia/Infrastructure/AvaloniaAutoUpdater.cs:459— MethodTooLong — CheckAndInstallUpdatesCoreAsync runs 159 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 59 over it, 1.59× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: PackageManagerPage.BuildExtraControls src/UniGetUI.Avalonia/Views/Pages/SettingsPages/PackageManagerPage.axaml.cs:424— MethodTooLong — BuildExtraControls runs 135 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 35 over it, 1.35× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: BaseNuGetDetailsHelper.GetDetails_UnSafe src/UniGetUI.PackageEngine.Managers.Generic.NuGet/BaseNuGetDetailsHelper.cs:20— MethodTooLong — GetDetails_UnSafe runs 129 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 29 over it, 1.29× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: ScoopPkgDetailsHelper.GetDetails_UnSafe src/UniGetUI.PackageEngine.Managers.Scoop/Helpers/ScoopPkgDetailsHelper.cs:17— MethodTooLong — GetDetails_UnSafe runs 124 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 24 over it, 1.24× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: DownloadOperation.PerformOperation src/UniGetUI.PackageEngine.Operations/DownloadOperation.cs:114— MethodTooLong — PerformOperation runs 122 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 22 over it, 1.22× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: AbstractOperation.MainThreadCore src/UniGetUI.PackageEngine.Operations/AbstractOperation.cs:257— MethodTooLong — MainThreadCore runs 120 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 20 over it, 1.20× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: CargoInstallTracker.InstallAsync src/UniGetUI.PackageEngine.Managers.Cargo/CargoInstallTracker.cs:85— MethodTooLong — InstallAsync runs 119 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 19 over it, 1.19× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: BundleImportFilter.Apply src/UniGetUI.PackageEngine.PackageManagerClasses/Manager/Classes/BundleImportFilter.cs:21— MethodTooLong — Apply runs 118 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 18 over it, 1.18× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: UpdaterDownloadEngine.DownloadInstallerPartAsync src/UniGetUI.Core.Tools/UpdaterDownloadEngine.cs:102— MethodTooLong — DownloadInstallerPartAsync runs 114 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 14 over it, 1.14× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: InstallOptionsDialog.Build src/UniGetUI.Tui/Views/Dialogs/InstallOptionsDialog.cs:128— MethodTooLong — Build runs 114 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 14 over it, 1.14× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: SoftwareUpdatesPage.GenerateContextMenu src/UniGetUI.Avalonia/Views/SoftwarePages/SoftwareUpdatesPage.cs:121— MethodTooLong — GenerateContextMenu runs 110 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 10 over it, 1.10× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: MainWindow.OnWindowsWndProc src/UniGetUI.Avalonia/Views/MainWindow.axaml.cs:1451— MethodTooLong — OnWindowsWndProc runs 105 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 5 over it, 1.05× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: AbstractOperation._runOperation src/UniGetUI.PackageEngine.Operations/AbstractOperation.cs:471— MethodTooLong — _runOperation runs 103 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 3 over it, 1.03× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: CargoBinaryResolver.ResolveAsync src/UniGetUI.PackageEngine.Managers.Cargo/CargoBinaryResolver.cs:36— MethodTooLong — ResolveAsync runs 101 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 1 over it, 1.01× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
async void method: ResumeStartupAfterMacOSEnvironment src/UniGetUI.Avalonia/App.axaml.cs:148— `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.
async void method: HandleNotificationActivation src/UniGetUI.Avalonia/ViewModels/MainWindowViewModel.cs:980— `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.
async void method: SendReport_Click src/UniGetUI.Avalonia/Views/DialogPages/CrashReportWindow.axaml.cs:24— `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.
async void method: SelectDir_Click src/UniGetUI.Avalonia/Views/DialogPages/InstallOptionsControl.axaml.cs:118— `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.
async void method: Manual_Click src/UniGetUI.Avalonia/Views/DialogPages/InstallOptionsControl.axaml.cs:135— `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.
async void method: OnCopyTextRequested src/UniGetUI.Avalonia/Views/Pages/LogPages/BaseLogPage.axaml.cs:46— `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.
async void method: OnExportTextRequested src/UniGetUI.Avalonia/Views/Pages/LogPages/BaseLogPage.axaml.cs:53— `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.
async void method: OnClearRequested src/UniGetUI.Avalonia/Views/Pages/LogPages/OperationHistoryPage.axaml.cs:199— `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.
async void method: OnCopyTextRequested src/UniGetUI.Avalonia/Views/Pages/SettingsPages/AgentPolicyInspector.axaml.cs:36— `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.
async void method: OnOpenPolicyEditorRequested src/UniGetUI.Avalonia/Views/Pages/SettingsPages/AgentPolicyInspector.axaml.cs:58— `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.
async void method: StructuredModeButton_Click src/UniGetUI.Avalonia/Views/Pages/SettingsPages/PolicyEditor/PolicyEditorDialog.axaml.cs:68— `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.
async void method: RuleDecision_SelectionChanged src/UniGetUI.Avalonia/Views/Pages/SettingsPages/PolicyEditor/PolicyEditorDialog.axaml.cs:148— `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.
async void method: Page_NavigationRequested src/UniGetUI.Avalonia/Views/Pages/SettingsPages/SettingsBasePage.axaml.cs:109— `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.
async void method: AnimateOverlayFilterPane src/UniGetUI.Avalonia/Views/SoftwarePages/AbstractPackagesPage.axaml.cs:593— `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.
async void method: AnimateInlineFilterPane src/UniGetUI.Avalonia/Views/SoftwarePages/AbstractPackagesPage.axaml.cs:713— `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.
async void method: OnEnter src/UniGetUI.Avalonia/Views/SoftwarePages/DiscoverSoftwarePage.cs:81— `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.
async void method: Execute src/UniGetUI.Avalonia/Infrastructure/AsyncCommand.cs:24— `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.
Sync-over-async (deadlock risk) src/UniGetUI.Avalonia/Views/DialogPages/CrashReportWindow.axaml.cs:56— Blocking on a Task with `.Wait()`/`.GetAwaiter().GetResult()` can deadlock (and wastes a thread). Prefer awaiting it: make the caller `async` and `await` instead. Where a synchronous entry point must stay — a public sync API you cannot break, or a process entry point that must not return until the work finishes — the block belongs in ONE documented bridge and never inside code that is already async; and where it already is that bridge, give the wait a TIMEOUT so a hung task fails the call instead of hanging the process.
Sync-over-async (deadlock risk) src/Shared/SharedPreUiCommandDispatcher.cs:256— Blocking on a Task with `.Wait()`/`.GetAwaiter().GetResult()` can deadlock (and wastes a thread). Prefer awaiting it: make the caller `async` and `await` instead. Where a synchronous entry point must stay — a public sync API you cannot break, or a process entry point that must not return until the work finishes — the block belongs in ONE documented bridge and never inside code that is already async; and where it already is that bridge, give the wait a TIMEOUT so a hung task fails the call instead of hanging the process.
Sync-over-async (deadlock risk) src/Shared/SharedPreUiCommandDispatcher.cs:274— Blocking on a Task with `.Wait()`/`.GetAwaiter().GetResult()` can deadlock (and wastes a thread). Prefer awaiting it: make the caller `async` and `await` instead. Where a synchronous entry point must stay — a public sync API you cannot break, or a process entry point that must not return until the work finishes — the block belongs in ONE documented bridge and never inside code that is already async; and where it already is that bridge, give the wait a TIMEOUT so a hung task fails the call instead of hanging the process.
Sync-over-async (deadlock risk) src/UniGetUI.Avalonia/Infrastructure/AvaloniaAutoUpdater.cs:1573— Blocking on a Task with `.Wait()`/`.GetAwaiter().GetResult()` can deadlock (and wastes a thread). Prefer awaiting it: make the caller `async` and `await` instead. Where a synchronous entry point must stay — a public sync API you cannot break, or a process entry point that must not return until the work finishes — the block belongs in ONE documented bridge and never inside code that is already async; and where it already is that bridge, give the wait a TIMEOUT so a hung task fails the call instead of hanging the process.
Sync-over-async (deadlock risk) src/UniGetUI.Avalonia/Infrastructure/AvaloniaBootstrapper.cs:210— Blocking on a Task with `.Wait()`/`.GetAwaiter().GetResult()` can deadlock (and wastes a thread). Prefer awaiting it: make the caller `async` and `await` instead. Where a synchronous entry point must stay — a public sync API you cannot break, or a process entry point that must not return until the work finishes — the block belongs in ONE documented bridge and never inside code that is already async; and where it already is that bridge, give the wait a TIMEOUT so a hung task fails the call instead of hanging the process.
Sync-over-async (deadlock risk) src/UniGetUI.Avalonia/Infrastructure/AvaloniaBootstrapper.cs:212— Blocking on a Task with `.Wait()`/`.GetAwaiter().GetResult()` can deadlock (and wastes a thread). Prefer awaiting it: make the caller `async` and `await` instead. Where a synchronous entry point must stay — a public sync API you cannot break, or a process entry point that must not return until the work finishes — the block belongs in ONE documented bridge and never inside code that is already async; and where it already is that bridge, give the wait a TIMEOUT so a hung task fails the call instead of hanging the process.
Sync-over-async (deadlock risk) src/UniGetUI.Avalonia/Infrastructure/AvaloniaBootstrapper.cs:214— Blocking on a Task with `.Wait()`/`.GetAwaiter().GetResult()` can deadlock (and wastes a thread). Prefer awaiting it: make the caller `async` and `await` instead. Where a synchronous entry point must stay — a public sync API you cannot break, or a process entry point that must not return until the work finishes — the block belongs in ONE documented bridge and never inside code that is already async; and where it already is that bridge, give the wait a TIMEOUT so a hung task fails the call instead of hanging the process.
Sync-over-async (deadlock risk) src/UniGetUI.Avalonia/Infrastructure/AvaloniaBootstrapper.cs:216— Blocking on a Task with `.Wait()`/`.GetAwaiter().GetResult()` can deadlock (and wastes a thread). Prefer awaiting it: make the caller `async` and `await` instead. Where a synchronous entry point must stay — a public sync API you cannot break, or a process entry point that must not return until the work finishes — the block belongs in ONE documented bridge and never inside code that is already async; and where it already is that bridge, give the wait a TIMEOUT so a hung task fails the call instead of hanging the process.
Sync-over-async (deadlock risk) src/UniGetUI.Avalonia/Infrastructure/AvaloniaBootstrapper.cs:218— Blocking on a Task with `.Wait()`/`.GetAwaiter().GetResult()` can deadlock (and wastes a thread). Prefer awaiting it: make the caller `async` and `await` instead. Where a synchronous entry point must stay — a public sync API you cannot break, or a process entry point that must not return until the work finishes — the block belongs in ONE documented bridge and never inside code that is already async; and where it already is that bridge, give the wait a TIMEOUT so a hung task fails the call instead of hanging the process.
Sync-over-async (deadlock risk) src/UniGetUI.Avalonia/Infrastructure/SingleInstanceRedirector.cs:117— Blocking on a Task with `.Wait()`/`.GetAwaiter().GetResult()` can deadlock (and wastes a thread). Prefer awaiting it: make the caller `async` and `await` instead. Where a synchronous entry point must stay — a public sync API you cannot break, or a process entry point that must not return until the work finishes — the block belongs in ONE documented bridge and never inside code that is already async; and where it already is that bridge, give the wait a TIMEOUT so a hung task fails the call instead of hanging the process.
Sync-over-async (deadlock risk) src/UniGetUI.Core.Classes/TaskRecycler.cs:78— Blocking on a Task with `.Wait()`/`.GetAwaiter().GetResult()` can deadlock (and wastes a thread). Prefer awaiting it: make the caller `async` and `await` instead. Where a synchronous entry point must stay — a public sync API you cannot break, or a process entry point that must not return until the work finishes — the block belongs in ONE documented bridge and never inside code that is already async; and where it already is that bridge, give the wait a TIMEOUT so a hung task fails the call instead of hanging the process.
Sync-over-async (deadlock risk) src/UniGetUI.Core.Classes/TaskRecycler.cs:84— Blocking on a Task with `.Wait()`/`.GetAwaiter().GetResult()` can deadlock (and wastes a thread). Prefer awaiting it: make the caller `async` and `await` instead. Where a synchronous entry point must stay — a public sync API you cannot break, or a process entry point that must not return until the work finishes — the block belongs in ONE documented bridge and never inside code that is already async; and where it already is that bridge, give the wait a TIMEOUT so a hung task fails the call instead of hanging the process.
Sync-over-async (deadlock risk) src/UniGetUI.Core.Classes/TaskRecycler.cs:91— Blocking on a Task with `.Wait()`/`.GetAwaiter().GetResult()` can deadlock (and wastes a thread). Prefer awaiting it: make the caller `async` and `await` instead. Where a synchronous entry point must stay — a public sync API you cannot break, or a process entry point that must not return until the work finishes — the block belongs in ONE documented bridge and never inside code that is already async; and where it already is that bridge, give the wait a TIMEOUT so a hung task fails the call instead of hanging the process.
Sync-over-async (deadlock risk) src/UniGetUI.Core.Classes/TaskRecycler.cs:99— Blocking on a Task with `.Wait()`/`.GetAwaiter().GetResult()` can deadlock (and wastes a thread). Prefer awaiting it: make the caller `async` and `await` instead. Where a synchronous entry point must stay — a public sync API you cannot break, or a process entry point that must not return until the work finishes — the block belongs in ONE documented bridge and never inside code that is already async; and where it already is that bridge, give the wait a TIMEOUT so a hung task fails the call instead of hanging the process.
Sync-over-async (deadlock risk) src/UniGetUI.Core.Data/CoreData.cs:517— Blocking on a Task with `.Wait()`/`.GetAwaiter().GetResult()` can deadlock (and wastes a thread). Prefer awaiting it: make the caller `async` and `await` instead. Where a synchronous entry point must stay — a public sync API you cannot break, or a process entry point that must not return until the work finishes — the block belongs in ONE documented bridge and never inside code that is already async; and where it already is that bridge, give the wait a TIMEOUT so a hung task fails the call instead of hanging the process.
Sync-over-async (deadlock risk) src/UniGetUI.Core.Tools/ShortcutFileRemover.cs:203— Blocking on a Task with `.Wait()`/`.GetAwaiter().GetResult()` can deadlock (and wastes a thread). Prefer awaiting it: make the caller `async` and `await` instead. Where a synchronous entry point must stay — a public sync API you cannot break, or a process entry point that must not return until the work finishes — the block belongs in ONE documented bridge and never inside code that is already async; and where it already is that bridge, give the wait a TIMEOUT so a hung task fails the call instead of hanging the process.
Duplicated block (6 lines × 2) src/UniGetUI.PackageEngine.PackageLoader/AbstractPackageLoader.cs:214— src/UniGetUI.PackageEngine.PackageLoader/AbstractPackageLoader.cs:214-219 | src/UniGetUI.PackageEngine.PackageLoader/InstalledPackagesLoader.cs:77-82 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `src/UniGetUI.PackageEngine.PackageLoader/AbstractPackageLoader.cs:214` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (6 lines × 2) src/UniGetUI.Interface.IpcApi/IpcBundleApi.cs:56— src/UniGetUI.Interface.IpcApi/IpcBundleApi.cs:56-61 | src/UniGetUI.Interface.IpcApi/IpcPackageApi.cs:30-35 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (6 lines × 2) src/UniGetUI.Interface.IpcApi/IpcPackageApi.cs:18— src/UniGetUI.Interface.IpcApi/IpcPackageApi.cs:18-23 | src/UniGetUI.Interface.IpcApi/IpcPackageApi.cs:68-73 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (6 lines × 2) src/UniGetUI.PackageEngine.Managers.Cargo/CargoInstallTracker.cs:271— src/UniGetUI.PackageEngine.Managers.Cargo/CargoInstallTracker.cs:271-276 | src/UniGetUI.PackageEngine.Managers.Cargo/CargoInstallTracker.cs:288-293 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/UniGetUI.PackageEngine.Managers.Cargo/CargoInstallTracker.cs:271` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (6 lines × 2) src/UniGetUI.Avalonia/ViewModels/Pages/SettingsPages/PolicyEditor/PolicyEditorMapper.cs:119— src/UniGetUI.Avalonia/ViewModels/Pages/SettingsPages/PolicyEditor/PolicyEditorMapper.cs:119-124 | src/UniGetUI.Avalonia/ViewModels/Pages/SettingsPages/PolicyEditor/PolicyEditorMapper.cs:284-289 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Note first that the copies are not typed on the same thing: the declarations holding them bind `rules` to `List<PolicyEditorDraftRule>` in one and `IEnumerable<PolicyRule>` in another, and the duplicated lines use it. The extracted unit therefore needs a parameter type that fits BOTH — their common supertype where they have one, or a new abstraction over them where they do not — and settling that is the step that comes BEFORE the extraction above. Where the two types are deliberately unrelated, the duplication is the price of that separation and the honest resolution is to record the decision rather than to extract.
Duplicated block (6 lines × 2) src/UniGetUI.Avalonia/Views/SoftwarePages/PackageBundlesPage.cs:587— src/UniGetUI.Avalonia/Views/SoftwarePages/PackageBundlesPage.cs:587-595 | src/UniGetUI.Tui/Infrastructure/TuiBundleService.cs:264-269 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `src/UniGetUI.Avalonia/Views/SoftwarePages/PackageBundlesPage.cs:587` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (6 lines × 2) src/Shared/AutoUpdater.Helpers.cs:406— src/Shared/AutoUpdater.Helpers.cs:406-411 | src/UniGetUI.Avalonia/Infrastructure/AvaloniaAutoUpdater.cs:1896-1901 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `src/Shared/AutoUpdater.Helpers.cs:406` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (6 lines × 2) REDACTED:211— REDACTED:211-216 | REDACTED:274-287 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `REDACTED:209` calls `StartsWith`, `Substring` and `REDACTED:274` does not — after which the two agree again for 3 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (6 lines × 2) src/UniGetUI.Avalonia/ViewModels/Pages/SettingsPages/PolicyEditor/PolicyEditorSessionViewModel.cs:1028— src/UniGetUI.Avalonia/ViewModels/Pages/SettingsPages/PolicyEditor/PolicyEditorSessionViewModel.cs:1028-1033 | src/UniGetUI.Avalonia/Views/Pages/SettingsPages/PolicyEditor/PolicyEditorDialog.axaml.cs:357-362 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (8 lines × 2) src/UniGetUI.Avalonia/Infrastructure/MaintenanceScheduler.cs:11— src/UniGetUI.Avalonia/Infrastructure/MaintenanceScheduler.cs:11-18 | src/UniGetUI.Tui/Infrastructure/TuiMaintenance.cs:18-25 — before extracting anything, compare `src/UniGetUI.Avalonia/Infrastructure/MaintenanceScheduler.cs` and `src/UniGetUI.Tui/Infrastructure/TuiMaintenance.cs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 35 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (8 lines × 2) src/UniGetUI.PackageEngine.PackageManagerClasses/Packages/Classes/StartMenuShortcutsDatabase.cs:241— src/UniGetUI.PackageEngine.PackageManagerClasses/Packages/Classes/StartMenuShortcutsDatabase.cs:241-248 | src/UniGetUI.PackageEngine.PackageManagerClasses/Packages/Classes/StartMenuShortcutsDatabase.cs:1065-1072 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/UniGetUI.PackageEngine.PackageManagerClasses/Packages/Classes/StartMenuShortcutsDatabase.cs:241` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (8 lines × 2) src/UniGetUI.PackageEngine.Managers.Apt/Apt.cs:189— src/UniGetUI.PackageEngine.Managers.Apt/Apt.cs:189-196 | src/UniGetUI.PackageEngine.Managers.Apt/Apt.cs:238-245 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/UniGetUI.PackageEngine.Managers.Apt/Apt.cs:189` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (8 lines × 2) src/UniGetUI.PackageEngine.Managers.Pacman/Pacman.cs:191— src/UniGetUI.PackageEngine.Managers.Pacman/Pacman.cs:191-198 | src/UniGetUI.PackageEngine.Managers.Pacman/Pacman.cs:232-239 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/UniGetUI.PackageEngine.Managers.Pacman/Pacman.cs:191` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (8 lines × 2) src/UniGetUI.Avalonia/Views/SoftwarePages/InstalledPackagesPage.cs:418— src/UniGetUI.Avalonia/Views/SoftwarePages/InstalledPackagesPage.cs:418-425 | src/UniGetUI.Avalonia/Views/SoftwarePages/SoftwareUpdatesPage.cs:423-430 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `src/UniGetUI.Avalonia/Views/SoftwarePages/InstalledPackagesPage.cs:418` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (8 lines × 2) src/UniGetUI.Avalonia/Infrastructure/MaintenanceScheduler.cs:127— src/UniGetUI.Avalonia/Infrastructure/MaintenanceScheduler.cs:127-134 | src/UniGetUI.Tui/Infrastructure/TuiMaintenance.cs:102-109 — before extracting anything, compare `src/UniGetUI.Avalonia/Infrastructure/MaintenanceScheduler.cs` and `src/UniGetUI.Tui/Infrastructure/TuiMaintenance.cs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 35 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/UniGetUI.Avalonia/Infrastructure/MaintenanceScheduler.cs:127` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `src/UniGetUI.Tui/Infrastructure/TuiMaintenance.cs:110` calls `Error`, `Translate` and `src/UniGetUI.Avalonia/Infrastructure/MaintenanceScheduler.cs:135` does not — after which the two agree again for 3 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (8 lines × 2) src/UniGetUI.PackageEngine.Managers.Flatpak/Helpers/FlatpakPkgDetailsHelper.cs:40— src/UniGetUI.PackageEngine.Managers.Flatpak/Helpers/FlatpakPkgDetailsHelper.cs:40-47 | src/UniGetUI.PackageEngine.Managers.Snap/Helpers/SnapPkgDetailsHelper.cs:71-78 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `src/UniGetUI.PackageEngine.Managers.Flatpak/Helpers/FlatpakPkgDetailsHelper.cs:40` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (8 lines × 2) src/UniGetUI.Avalonia/ViewModels/DialogPages/InstallOptionsViewModel.cs:483— src/UniGetUI.Avalonia/ViewModels/DialogPages/InstallOptionsViewModel.cs:483-493 | src/UniGetUI.Tui/Views/Dialogs/InstallOptionsDialog.cs:280-287 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (8 lines × 2) src/UniGetUI.PackageEngine.PackageManagerClasses/Manager/Classes/NullPackageManager.cs:36— src/UniGetUI.PackageEngine.PackageManagerClasses/Manager/Classes/NullPackageManager.cs:36-43 | src/UniGetUI.PackageEngine.PackageManagerClasses/Manager/PackageManager.cs:55-62 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Off the main sequence: UniGetUI.Core.Logging(net10.0) src/UniGetUI.Core.Logger/UniGetUI.Core.Logging.csproj:1— UniGetUI.Core.Logging(net10.0): abstractness 0.00, instability 0.00, distance 1.00 — zone of pain — concrete and depended on by 27 project(s), so it's rigid to change.
Off the main sequence: UniGetUI.Interface.Enums(net10.0) src/UniGetUI.Interface.Enums/UniGetUI.Interface.Enums.csproj:1— UniGetUI.Interface.Enums(net10.0): abstractness 0.00, instability 0.00, distance 1.00 — zone of pain — concrete and depended on by 16 project(s), so it's rigid to change.
Off the main sequence: UniGetUI.PackageEngine.Structs(net10.0) src/UniGetUI.PackageEngine.Enums/UniGetUI.PackageEngine.Structs.csproj:1— UniGetUI.PackageEngine.Structs(net10.0): abstractness 0.00, instability 0.00, distance 1.00 — zone of pain — concrete and depended on by 22 project(s), so it's rigid to change.
Off the main sequence: UniGetUI.Core.Data(net10.0) src/UniGetUI.Core.Data/UniGetUI.Core.Data.csproj:1— UniGetUI.Core.Data(net10.0): abstractness 0.00, instability 0.04, distance 0.96 — zone of pain — concrete and depended on by 26 project(s), so it's rigid to change.
Off the main sequence: UniGetUI.Core.Settings(net10.0) src/UniGetUI.Core.Settings/UniGetUI.Core.Settings.csproj:1— UniGetUI.Core.Settings(net10.0): abstractness 0.00, instability 0.07, distance 0.93 — zone of pain — concrete and depended on by 25 project(s), so it's rigid to change.
Off the main sequence: UniGetUI.Core.Tools(net10.0) src/UniGetUI.Core.Tools/UniGetUI.Core.Tools.csproj:1— UniGetUI.Core.Tools(net10.0): abstractness 0.00, instability 0.17, distance 0.83 — zone of pain — concrete and depended on by 24 project(s), so it's rigid to change.
Off the main sequence: UniGetUI.Core.IconEngine(net10.0) src/UniGetUI.Core.IconStore/UniGetUI.Core.IconEngine.csproj:1— UniGetUI.Core.IconEngine(net10.0): abstractness 0.00, instability 0.20, distance 0.80 — zone of pain — concrete and depended on by 16 project(s), so it's rigid to change.
Off the main sequence: UniGetUI.Core.LanguageEngine(net10.0) src/UniGetUI.Core.LanguageEngine/UniGetUI.Core.LanguageEngine.csproj:1— UniGetUI.Core.LanguageEngine(net10.0): abstractness 0.00, instability 0.20, distance 0.80 — zone of pain — concrete and depended on by 19 project(s), so it's rigid to change.
Off the main sequence: UniGetUI.Core.Classes(net10.0) src/UniGetUI.Core.Classes/UniGetUI.Core.Classes.csproj:1— UniGetUI.Core.Classes(net10.0): abstractness 0.17, instability 0.05, distance 0.79 — zone of pain — concrete and depended on by 20 project(s), so it's rigid to change.
ClassTooLong: IpcCliCommandRunner src/UniGetUI.Interface.IpcApi/IpcCliCommandRunner.cs— ClassTooLong — 617 significant lines (blank, comment-only and punctuation-only lines excluded), 24 methods. The bar is 400 significant lines; this is 217 over it, 1.54× the bar. The type holds no instance state, so there is no shared data to group its members by. To reduce it, split it by area instead: give each cohesive family of members its own smaller type, so no one type has to be read whole to change one of them.
ClassTooLong: NuGetV3Client src/UniGetUI.PackageEngine.Managers.Generic.NuGet/Internal/NuGetV3Client.cs— ClassTooLong — 538 significant lines (blank, comment-only and punctuation-only lines excluded), 28 methods. The bar is 400 significant lines; this is 138 over it, 1.35× the bar. The type holds no instance state, so there is no shared data to group its members by. To reduce it, split it by area instead: give each cohesive family of members its own smaller type, so no one type has to be read whole to change one of them.
ClassTooLong: BaseNuGet src/UniGetUI.PackageEngine.Managers.Generic.NuGet/BaseNuGet.cs— ClassTooLong — 499 significant lines (blank, comment-only and punctuation-only lines excluded), 17 methods. The bar is 400 significant lines; this is 99 over it, 1.25× the bar. The type holds no instance state, so there is no shared data to group its members by. To reduce it, split it by area instead: give each cohesive family of members its own smaller type, so no one type has to be read whole to change one of them.
ClassTooLong: NativeWinGetHelper src/UniGetUI.PackageEngine.Managers.WinGet/ClientHelpers/NativeWinGetHelper.cs— ClassTooLong — 495 significant lines (blank, comment-only and punctuation-only lines excluded), 25 methods. The bar is 400 significant lines; this is 95 over it, 1.24× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
ClassTooLong: PackageManagerPage src/UniGetUI.Avalonia/Views/Pages/SettingsPages/PackageManagerPage.axaml.cs— ClassTooLong — 453 significant lines (blank, comment-only and punctuation-only lines excluded), 8 methods. The bar is 400 significant lines; this is 53 over it, 1.13× the bar. The type holds no instance state, so there is no shared data to group its members by. To reduce it, split it by area instead: give each cohesive family of members its own smaller type, so no one type has to be read whole to change one of them.
ClassTooLong: TuiThemes src/UniGetUI.Tui/Theme/TuiTheme.cs— ClassTooLong — 431 significant lines (blank, comment-only and punctuation-only lines excluded), 2 methods. The bar is 400 significant lines; this is 31 over it, 1.08× the bar. The type holds no instance state, so there is no shared data to group its members by. To reduce it, split it by area instead: give each cohesive family of members its own smaller type, so no one type has to be read whole to change one of them.
ClassTooLong: PolicyEditorRuleUi src/UniGetUI.Avalonia/ViewModels/Pages/SettingsPages/PolicyEditor/PolicyEditorStructuredUi.cs— ClassTooLong — 430 significant lines (blank, comment-only and punctuation-only lines excluded), 17 methods. The bar is 400 significant lines; this is 30 over it, 1.08× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
ClassTooLong: PolicyFindingPresentation src/UniGetUI.Avalonia/ViewModels/Pages/SettingsPages/PolicyEditor/PolicyValidationFinding.cs— ClassTooLong — 404 significant lines (blank, comment-only and punctuation-only lines excluded), 21 methods. The bar is 400 significant lines; this is 4 over it, 1.01× the bar. The type holds no instance state, so there is no shared data to group its members by. To reduce it, split it by area instead: give each cohesive family of members its own smaller type, so no one type has to be read whole to change one of them.
Swallowed exception (caught, then discarded) src/UniGetUI.Avalonia/CrashHandler.cs:88— `catch` does nothing with the exception it caught — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch. Log it through whatever this codebase already uses to report problems, or let it propagate; if one specific failure genuinely cannot matter, catch exactly that exception type and say why in a comment on the catch.
Swallowed exception (caught, then discarded) src/UniGetUI.Avalonia/ViewModels/Pages/SettingsPages/PolicyEditor/PolicyEditorSessionViewModel.cs:1302— `catch (JsonException)` does nothing with the exception it caught — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch. Log it through whatever this codebase already uses to report problems, or let it propagate; if one specific failure genuinely cannot matter, catch exactly that exception type and say why in a comment on the catch.
Swallowed exception (caught, then discarded) src/UniGetUI.Avalonia/ViewModels/Pages/SettingsPages/PolicyEditor/PolicyValidationFinding.cs:286— `catch (InvalidOperationException)` does nothing with the exception it caught — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch. Log it through whatever this codebase already uses to report problems, or let it propagate; if one specific failure genuinely cannot matter, catch exactly that exception type and say why in a comment on the catch.
Swallowed exception (caught, then discarded) src/UniGetUI.Avalonia/Views/Controls/Settings/ComboboxCard.cs:70— `catch` does nothing with the exception it caught — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch. Log it through whatever this codebase already uses to report problems, or let it propagate; if one specific failure genuinely cannot matter, catch exactly that exception type and say why in a comment on the catch.
Swallowed exception (caught, then discarded) src/UniGetUI.Avalonia/Infrastructure/GHAuthApiRunner.cs:39— `catch (Exception)` does nothing with the exception it caught — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch. Log it through whatever this codebase already uses to report problems, or let it propagate; if one specific failure genuinely cannot matter, catch exactly that exception type and say why in a comment on the catch.
Swallowed exception (caught, then discarded) src/UniGetUI.Core.Tools/LocalBackupManager.cs:95— `catch (IOException) when (…)` does nothing with the exception it caught — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch. Log it through whatever this codebase already uses to report problems, or let it propagate; if one specific failure genuinely cannot matter, catch exactly that exception type and say why in a comment on the catch.
Swallowed exception (caught, then discarded) src/UniGetUI.Core.Tools/ShortcutFileRemover.cs:584— `catch (Exception)` does nothing with the exception it caught — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch. Log it through whatever this codebase already uses to report problems, or let it propagate; if one specific failure genuinely cannot matter, catch exactly that exception type and say why in a comment on the catch.
Swallowed exception (caught, then discarded) src/UniGetUI.PackageEngine.Operations/AbstractOperation_Progress.cs:307— `catch (ObjectDisposedException)` does nothing with the exception it caught — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch. Log it through whatever this codebase already uses to report problems, or let it propagate; if one specific failure genuinely cannot matter, catch exactly that exception type and say why in a comment on the catch.
Duplicated block (5 lines × 2) src/UniGetUI.Avalonia/ViewModels/DialogPages/InstallOptionsViewModel.cs:45— src/UniGetUI.Avalonia/ViewModels/DialogPages/InstallOptionsViewModel.cs:45-49 | src/UniGetUI.Avalonia/ViewModels/Pages/SettingsPages/InstallOptionsPanelViewModel.cs:77-81 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (5 lines × 2) src/UniGetUI.Avalonia/ViewModels/DialogPages/OperationOutputViewModel.cs:63— src/UniGetUI.Avalonia/ViewModels/DialogPages/OperationOutputViewModel.cs:63-67 | src/UniGetUI.Avalonia/Views/DialogPages/OperationFailedDialog.axaml.cs:76-80 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (5 lines × 2) src/UniGetUI.Avalonia/ViewModels/SoftwarePages/PackagesPageViewModel.cs:120— src/UniGetUI.Avalonia/ViewModels/SoftwarePages/PackagesPageViewModel.cs:120-124 | src/UniGetUI.Avalonia/ViewModels/SoftwarePages/SoftwareCatalogViewModel.cs:60-64 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (5 lines × 2) src/UniGetUI.Avalonia/Views/Controls/Settings/CheckboxCard.cs:82— src/UniGetUI.Avalonia/Views/Controls/Settings/CheckboxCard.cs:82-86 | src/UniGetUI.Avalonia/Views/Controls/Settings/SecureCheckboxCard.cs:71-75 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (5 lines × 2) src/UniGetUI.Avalonia/Views/SoftwarePages/DiscoverSoftwarePage.cs:343— src/UniGetUI.Avalonia/Views/SoftwarePages/DiscoverSoftwarePage.cs:343-347 | src/UniGetUI.Avalonia/Views/SoftwarePages/InstalledPackagesPage.cs:383-387 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (5 lines × 2) src/UniGetUI.Avalonia/Views/SoftwarePages/InstalledPackagesPage.cs:375— src/UniGetUI.Avalonia/Views/SoftwarePages/InstalledPackagesPage.cs:375-379 | src/UniGetUI.Avalonia/Views/SoftwarePages/SoftwareUpdatesPage.cs:373-377 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (5 lines × 2) src/UniGetUI.Avalonia/Views/DialogPages/PackageDetailsWindow.axaml.cs:1078— src/UniGetUI.Avalonia/Views/DialogPages/PackageDetailsWindow.axaml.cs:1078-1082 | src/UniGetUI.Avalonia/Views/DialogPages/PackageDetailsWindow.axaml.cs:1084-1088 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
TodoComment src/UniGetUI.PackageEngine.Managers.Bun/Bun.cs:374— // TODO: Replace table parsing with JSON deserialization when bun outdated adds --json flag.
TodoComment src/UniGetUI.PackageEngine.Managers.Cargo/Helpers/CargoPkgDetailsHelper.cs:67— // TODO: most packages are hosted on Github; see if there's a way to use the repository — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment src/UniGetUI.PackageEngine.Managers.Vcpkg/Helpers/VcpkgPkgDetailsHelper.cs:57— // TODO: since each change results in a new commit to the file, you could determine the `UpdateDate` via figuring out the date of the last commit that changed the file was.
TodoComment src/UniGetUI.PackageEngine.Managers.Vcpkg/Helpers/VcpkgPkgDetailsHelper.cs:62— // TODO: the "features" and "dependencies" keys could also be good candidates for tags, however their type specifications are all over -
TodoComment REDACTED:99— // TODO: Perhaps use --x-json when it is fixed — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment REDACTED:253— // TODO: Once --x-json is stable migrate to --x-json — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
Duplicated block (13 lines × 2) src/UniGetUI.PackageEngine.Managers.Dnf/Dnf.cs:198— src/UniGetUI.PackageEngine.Managers.Dnf/Dnf.cs:198-210 | src/UniGetUI.PackageEngine.Managers.Dnf/Dnf.cs:249-261 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/UniGetUI.PackageEngine.Managers.Dnf/Dnf.cs:198` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `src/UniGetUI.PackageEngine.Managers.Dnf/Dnf.cs:263` calls `TryGetValue` and `src/UniGetUI.PackageEngine.Managers.Dnf/Dnf.cs:212` does not — after which the two agree again for 3 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (13 lines × 2) src/UniGetUI.Avalonia/Infrastructure/WindowsAvaloniaRenderingPolicy.cs:154— src/UniGetUI.Avalonia/Infrastructure/WindowsAvaloniaRenderingPolicy.cs:154-166 | src/UniGetUI.Avalonia/Infrastructure/WindowsAvaloniaRenderingPolicy.cs:193-205 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (13 lines × 2) src/UniGetUI.PackageEngine.Managers.Bun/Helpers/BunPkgDetailsHelper.cs:177— src/UniGetUI.PackageEngine.Managers.Bun/Helpers/BunPkgDetailsHelper.cs:177-189 | src/UniGetUI.PackageEngine.Managers.Npm/Helpers/NpmPkgDetailsHelper.cs:230-242 — before extracting anything, compare `src/UniGetUI.PackageEngine.Managers.Bun/Helpers/BunPkgDetailsHelper.cs` and `src/UniGetUI.PackageEngine.Managers.Npm/Helpers/NpmPkgDetailsHelper.cs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 106 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/UniGetUI.PackageEngine.Managers.Bun/Helpers/BunPkgDetailsHelper.cs:177` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The `return` at the foot of the matched lines is the enclosing body's own terminal exit, not an early one: it moves with them unchanged, and each site calls the extracted unit from the position that `return` occupied — no decision has to be handed back and re-acted on.
Duplicated block (13 lines × 2) src/UniGetUI.PackageEngine.Managers.Apt/Apt.cs:198— src/UniGetUI.PackageEngine.Managers.Apt/Apt.cs:198-210 | src/UniGetUI.PackageEngine.Managers.Dnf/Dnf.cs:212-224 — `src/UniGetUI.PackageEngine.Managers.Apt/Apt.cs` and `src/UniGetUI.PackageEngine.Managers.Dnf/Dnf.cs` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 3 separate duplicated blocks between them, totalling at least 47 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own. Read the line range as the matched WINDOW rather than a finished unit: at `src/UniGetUI.PackageEngine.Managers.Apt/Apt.cs:198` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The `return` at the foot of the matched lines is the enclosing body's own terminal exit, not an early one: it moves with them unchanged, and each site calls the extracted unit from the position that `return` occupied — no decision has to be handed back and re-acted on.
Duplicated block (13 lines × 2) src/UniGetUI.Avalonia/ViewModels/Pages/SettingsPages/InternetViewModel.cs:89— src/UniGetUI.Avalonia/ViewModels/Pages/SettingsPages/InternetViewModel.cs:89-104 | src/UniGetUI.Avalonia/ViewModels/Pages/SettingsPages/UpdatesViewModel.cs:46-58 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (13 lines × 2) src/UniGetUI.PackageEngine.Managers.Scoop/Scoop.cs:253— src/UniGetUI.PackageEngine.Managers.Scoop/Scoop.cs:253-265 | src/UniGetUI.PackageEngine.Managers.Scoop/Scoop.cs:315-327 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/UniGetUI.PackageEngine.Managers.Scoop/Scoop.cs:253` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (11 lines × 2) src/UniGetUI.PackageEngine.Managers.Generic.NuGet/Internal/NuGetV3Json.cs:33— src/UniGetUI.PackageEngine.Managers.Generic.NuGet/Internal/NuGetV3Json.cs:33-43 | src/UniGetUI.PackageEngine.Managers.Generic.NuGet/Internal/NuGetV3Json.cs:90-100 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (11 lines × 2) src/UniGetUI.PackageEngine.Managers.WinGet/ClientHelpers/WinGetCliHelper.cs:241— src/UniGetUI.PackageEngine.Managers.WinGet/ClientHelpers/WinGetCliHelper.cs:241-251 | src/UniGetUI.PackageEngine.Managers.WinGet/ClientHelpers/WinGetCliHelper.cs:409-419 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (11 lines × 2) src/UniGetUI.Avalonia/Views/SoftwarePages/InstalledPackagesPage.cs:115— src/UniGetUI.Avalonia/Views/SoftwarePages/InstalledPackagesPage.cs:115-125 | src/UniGetUI.Avalonia/Views/SoftwarePages/SoftwareUpdatesPage.cs:97-107 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `src/UniGetUI.Avalonia/Views/SoftwarePages/InstalledPackagesPage.cs:115` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (11 lines × 2) src/UniGetUI.PackageEngine.Managers.Homebrew/Homebrew.cs:172— src/UniGetUI.PackageEngine.Managers.Homebrew/Homebrew.cs:172-182 | src/UniGetUI.PackageEngine.Managers.Pacman/Pacman.cs:126-149 — `src/UniGetUI.PackageEngine.Managers.Homebrew/Homebrew.cs` and `src/UniGetUI.PackageEngine.Managers.Pacman/Pacman.cs` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 4 separate duplicated blocks between them, totalling at least 79 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own. Read the line range as the matched WINDOW rather than a finished unit: at `src/UniGetUI.PackageEngine.Managers.Homebrew/Homebrew.cs:172` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `src/UniGetUI.PackageEngine.Managers.Homebrew/Homebrew.cs:170` calls `GetSourceOrDefault` and `src/UniGetUI.PackageEngine.Managers.Pacman/Pacman.cs:126` does not — after which the two agree again for 3 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (11 lines × 2) src/UniGetUI.PackageEngine.Managers.Apt/Helpers/AptPkgDetailsHelper.cs:107— src/UniGetUI.PackageEngine.Managers.Apt/Helpers/AptPkgDetailsHelper.cs:107-117 | src/UniGetUI.PackageEngine.Managers.Snap/Helpers/SnapPkgDetailsHelper.cs:106-116 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `src/UniGetUI.PackageEngine.Managers.Apt/Helpers/AptPkgDetailsHelper.cs:107` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (11 lines × 2) src/UniGetUI.PackageEngine.Managers.Generic.NuGet/BaseNuGetDetailsHelper.cs:279— src/UniGetUI.PackageEngine.Managers.Generic.NuGet/BaseNuGetDetailsHelper.cs:279-289 | src/UniGetUI.PackageEngine.Managers.Generic.NuGet/BaseNuGetDetailsHelper.cs:349-359 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (15 lines × 2) src/UniGetUI.Avalonia/ViewModels/Pages/SettingsPages/PolicyEditor/PolicyValidationFinding.cs:26— src/UniGetUI.Avalonia/ViewModels/Pages/SettingsPages/PolicyEditor/PolicyValidationFinding.cs:26-40 | src/UniGetUI.Avalonia/ViewModels/Pages/SettingsPages/PolicyEditor/PolicyValidationFinding.cs:44-58 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit. Note first that the copies are not typed on the same thing: the declarations holding them bind `finding` to `PolicyFinding` in one and `BrokerPolicySanitizedFinding` in another, and the duplicated lines use it. The extracted unit therefore needs a parameter type that fits BOTH — their common supertype where they have one, or a new abstraction over them where they do not — and settling that is the step that comes BEFORE the extraction above. Where the two types are deliberately unrelated, the duplication is the price of that separation and the honest resolution is to record the decision rather than to extract.
Duplicated block (15 lines × 2) src/UniGetUI.Avalonia/Views/Controls/PackageIconLoader.cs:24— src/UniGetUI.Avalonia/Views/Controls/PackageIconLoader.cs:24-38 | src/UniGetUI.Avalonia/Views/Controls/PackageRowValueLoader.cs:18-32 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (15 lines × 2) src/UniGetUI.Avalonia/Infrastructure/AvaloniaAutoUpdater.cs:955— src/UniGetUI.Avalonia/Infrastructure/AvaloniaAutoUpdater.cs:955-969 | src/UniGetUI.Avalonia/Infrastructure/AvaloniaAutoUpdater.cs:1115-1130 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/UniGetUI.Avalonia/Infrastructure/AvaloniaAutoUpdater.cs:955` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (15 lines × 2) src/UniGetUI.Avalonia/Infrastructure/AvaloniaAutoUpdater.cs:1053— src/UniGetUI.Avalonia/Infrastructure/AvaloniaAutoUpdater.cs:1053-1071 | src/UniGetUI.Avalonia/Infrastructure/AvaloniaAutoUpdater.cs:1174-1188 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/UniGetUI.Avalonia/Infrastructure/AvaloniaAutoUpdater.cs:1053` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (15 lines × 2) src/UniGetUI.PackageEngine.Managers.Flatpak/FlatpakParsing.cs:30— src/UniGetUI.PackageEngine.Managers.Flatpak/FlatpakParsing.cs:30-44 | src/UniGetUI.PackageEngine.Managers.Flatpak/FlatpakParsing.cs:78-92 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/UniGetUI.PackageEngine.Managers.Flatpak/FlatpakParsing.cs:30` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (7 lines × 2) src/UniGetUI.Avalonia/Views/DialogPages/PackageDetailsWindow.axaml.cs:572— src/UniGetUI.Avalonia/Views/DialogPages/PackageDetailsWindow.axaml.cs:572-578 | src/UniGetUI.Avalonia/Views/DialogPages/PackageDetailsWindow.axaml.cs:605-611 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (7 lines × 2) src/UniGetUI.Avalonia/Views/MainWindow.axaml.cs:1109— src/UniGetUI.Avalonia/Views/MainWindow.axaml.cs:1109-1115 | src/UniGetUI.Avalonia/Views/MainWindow.axaml.cs:1117-1123 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (7 lines × 2) src/UniGetUI.Tui/Infrastructure/TuiFocus.cs:33— src/UniGetUI.Tui/Infrastructure/TuiFocus.cs:33-45 | src/UniGetUI.Tui/Infrastructure/TuiFocus.cs:65-71 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/UniGetUI.Tui/Infrastructure/TuiFocus.cs:33` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (7 lines × 2) src/UniGetUI.Avalonia/ViewModels/Controls/UserAvatarViewModel.cs:169— src/UniGetUI.Avalonia/ViewModels/Controls/UserAvatarViewModel.cs:169-175 | src/UniGetUI.Avalonia/ViewModels/Pages/SettingsPages/BackupViewModel.cs:431-437 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (7 lines × 2) src/UniGetUI.Avalonia/Views/Pages/HelpPage.axaml.cs:127— src/UniGetUI.Avalonia/Views/Pages/HelpPage.axaml.cs:127-133 | src/UniGetUI.Avalonia/Views/Pages/ReleaseNotesPage.axaml.cs:94-100 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Sync-over-async (deadlock risk) through `.Result` src/UniGetUI.Avalonia/CrashHandler.cs:199— Reading `.Result` of a task that has not completed blocks this thread until it does — the same block as `.Wait()`: under a synchronization context (Blazor, a UI thread, classic ASP.NET) it deadlocks, and on the thread pool it parks a thread for as long as the work runs. `await` the task instead (make the caller `async`); where a synchronous entry point must stay, keep the block in ONE documented bridge with a timeout.
Sync-over-async (deadlock risk) through `.Result` src/UniGetUI.Avalonia/ViewModels/DialogPages/CatalogEditorViewModel.cs:109— Reading `.Result` of a task that has not completed blocks this thread until it does — the same block as `.Wait()`: under a synchronization context (Blazor, a UI thread, classic ASP.NET) it deadlocks, and on the thread pool it parks a thread for as long as the work runs. `await` the task instead (make the caller `async`); where a synchronous entry point must stay, keep the block in ONE documented bridge with a timeout.
Sync-over-async (deadlock risk) through `.Result` REDACTED:1145— Reading `.Result` of a task that has not completed blocks this thread until it does — the same block as `.Wait()`: under a synchronization context (Blazor, a UI thread, classic ASP.NET) it deadlocks, and on the thread pool it parks a thread for as long as the work runs. `await` the task instead (make the caller `async`); where a synchronous entry point must stay, keep the block in ONE documented bridge with a timeout.
Sync-over-async (deadlock risk) through `.Result` REDACTED:1150— Reading `.Result` of a task that has not completed blocks this thread until it does — the same block as `.Wait()`: under a synchronization context (Blazor, a UI thread, classic ASP.NET) it deadlocks, and on the thread pool it parks a thread for as long as the work runs. `await` the task instead (make the caller `async`); where a synchronous entry point must stay, keep the block in ONE documented bridge with a timeout.
Change coupling: InvalidImportedPackage.cs ↔ Package.cs src/UniGetUI.PackageEngine.PackageManagerClasses/Packages/InvalidImportedPackage.cs:1— `src/UniGetUI.PackageEngine.PackageManagerClasses/Packages/InvalidImportedPackage.cs` and `src/UniGetUI.PackageEngine.PackageManagerClasses/Packages/Package.cs` change together 95% of the time (19 of the 20 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets). They sit in the same directory, and in this ecosystem sibling files there normally share one namespace/package — so a direct reference between them needs no import and this pass cannot see whether one exists. Read the pair before acting: if one file only DECLARES what the other consumes (a constants/types file beside its user), the co-change is definitional and the question is whether the split earns its keep; if they duplicate structure, extract the common part into a shared function or type they both call; if neither holds, the coupling is hidden and worth breaking. You can check this without leaving the row: of the 19 shared commits counted here, the most recent 3 are `fe5a6f94` Fix MSIX installer manifests and mark unverified versions (#5369); `ce4f25c0` Add configurable skip level for minor updates (#5113); `a653e410` Better handle installed packages tags — run `git show` on any of them.
Change coupling: BaseSourceHelper.cs ↔ PackageManager.cs src/UniGetUI.PackageEngine.PackageManagerClasses/Manager/Helpers/BaseSourceHelper.cs:1— `src/UniGetUI.PackageEngine.PackageManagerClasses/Manager/Helpers/BaseSourceHelper.cs` and `src/UniGetUI.PackageEngine.PackageManagerClasses/Manager/PackageManager.cs` change together 60% of the time (6 of the 10 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets). They sit in different directories, but in this ecosystem the namespace is declared in the FILE, not by the folder — so the two may well share one namespace and reference each other with no import for this pass to see. Read the pair before acting: if one derives from or overrides the other, the dependency is explicit in the type declaration and the co-change is definitional; if one registers itself into the other through a hook or an initialiser, the missing dependency is DELIBERATE and the thing to add is a comment saying so; if they simply belong together, co-locate them; if none of these holds, the coupling is hidden and worth breaking. You can check this without leaving the row: of the 6 shared commits counted here, the most recent 3 are `8a788eba` Improve error handling of tasks that are not waited anymore due to a …; `0cb3180b` improvements to package manager initialization process, separe steps …; `85432e5a` Scoop will also take advantage of the TaskRecycler to fetch installed… (at that commit the file was still `src/UniGetUI.PackageEngine.PackageManagerClasses/Manager/BaseProviders/BaseSourceProvider.cs`) — run `git show` on any of them.
Change coupling: ImportedPackage.cs ↔ InvalidImportedPackage.cs src/UniGetUI.PackageEngine.PackageManagerClasses/Packages/ImportedPackage.cs:1— `src/UniGetUI.PackageEngine.PackageManagerClasses/Packages/ImportedPackage.cs` and `src/UniGetUI.PackageEngine.PackageManagerClasses/Packages/InvalidImportedPackage.cs` change together 53% of the time (8 of the 15 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets). They sit in the same directory, and in this ecosystem sibling files there normally share one namespace/package — so a direct reference between them needs no import and this pass cannot see whether one exists. Read the pair before acting: if one file only DECLARES what the other consumes (a constants/types file beside its user), the co-change is definitional and the question is whether the split earns its keep; if they duplicate structure, extract the common part into a shared function or type they both call; if neither holds, the coupling is hidden and worth breaking. You can check this without leaving the row: of the 8 shared commits counted here, the most recent 3 are `b736458b` fix import tree; `04cf96fa` Migrate SerializablePackage; `9c92fb38` Revame Version to VersionString — run `git show` on any of them.
D4 · Code Duplication· Members sharing a duplicated core (5 members, 50+ identical tokens) · ×3
Members sharing a duplicated core (5 members, 50+ identical tokens) src/UniGetUI.Avalonia/Infrastructure/AvaloniaPackageOperationHelper.cs:34— src/UniGetUI.Avalonia/Infrastructure/AvaloniaPackageOperationHelper.cs:34-45 | src/UniGetUI.Avalonia/Infrastructure/AvaloniaPackageOperationHelper.cs:48-61 | src/UniGetUI.Avalonia/Infrastructure/AvaloniaPackageOperationHelper.cs:64-79 | src/UniGetUI.Avalonia/Views/SoftwarePages/InstalledPackagesPage.cs:428-439 | src/UniGetUI.Avalonia/Views/SoftwarePages/SoftwareUpdatesPage.cs:399-411 — These 5 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 5 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 5 times.
Members sharing a duplicated core (5 members, 50+ identical tokens) src/UniGetUI.Interface.IpcApi/IpcServer.cs:1615— src/UniGetUI.Interface.IpcApi/IpcServer.cs:1615-1644 | src/UniGetUI.Interface.IpcApi/IpcServer.cs:1647-1674 | src/UniGetUI.Interface.IpcApi/IpcServer.cs:1749-1779 | src/UniGetUI.Interface.IpcApi/IpcServer.cs:1824-1853 | src/UniGetUI.Interface.IpcApi/IpcServer.cs:1906-1933 — These 5 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 5 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 5 times.
Members sharing a duplicated core (5 members, 50+ identical tokens) src/UniGetUI.PackageEngine.Managers.Dnf/Dnf.cs:182— src/UniGetUI.PackageEngine.Managers.Dnf/Dnf.cs:182-224 | src/UniGetUI.PackageEngine.Managers.Dnf/Dnf.cs:227-277 | src/UniGetUI.PackageEngine.Managers.Homebrew/Homebrew.cs:213-236 | src/UniGetUI.PackageEngine.Managers.Pacman/Pacman.cs:175-213 | src/UniGetUI.PackageEngine.Managers.Pacman/Pacman.cs:216-256 — These 5 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 5 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 5 times.
Duplicated block (19 lines × 2) src/UniGetUI.Avalonia/Views/SoftwarePages/PackageBundlesPage.cs:408— src/UniGetUI.Avalonia/Views/SoftwarePages/PackageBundlesPage.cs:408-426 | src/UniGetUI.Tui/Infrastructure/TuiBundleService.cs:53-71 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (19 lines × 2) src/UniGetUI.Interface.IpcApi/IpcServer.cs:1857— src/UniGetUI.Interface.IpcApi/IpcServer.cs:1857-1875 | src/UniGetUI.Interface.IpcApi/IpcServer.cs:1882-1900 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit. Note first that the copies are not typed on the same thing: the declarations holding them bind `action` to `Func<IpcPackageActionRequest, Task<IpcPackageOperationResult>>` in one and `Func<IpcCommandResult>` in another, and the duplicated lines use it. The extracted unit therefore needs a parameter type that fits BOTH — their common supertype where they have one, or a new abstraction over them where they do not — and settling that is the step that comes BEFORE the extraction above. Where the two types are deliberately unrelated, the duplication is the price of that separation and the honest resolution is to record the decision rather than to extract.
Duplicated block (19 lines × 2) src/UniGetUI.PackageEngine.PackageManagerClasses/Manager/Classes/ManagerLogger.cs:225— src/UniGetUI.PackageEngine.PackageManagerClasses/Manager/Classes/ManagerLogger.cs:225-245 | src/UniGetUI.PackageEngine.PackageManagerClasses/Manager/Classes/ManagerLogger.cs:399-417 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/UniGetUI.PackageEngine.PackageManagerClasses/Manager/Classes/ManagerLogger.cs:225` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (14 lines × 2) src/UniGetUI.Avalonia/Infrastructure/WindowsAppNotificationBridge.cs:110— src/UniGetUI.Avalonia/Infrastructure/WindowsAppNotificationBridge.cs:110-123 | src/UniGetUI.Avalonia/Infrastructure/WindowsAppNotificationBridge.cs:150-163 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/UniGetUI.Avalonia/Infrastructure/WindowsAppNotificationBridge.cs:110` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (14 lines × 2) src/UniGetUI.PackageEngine.Managers.Dnf/Dnf.cs:166— src/UniGetUI.PackageEngine.Managers.Dnf/Dnf.cs:166-179 | src/UniGetUI.PackageEngine.Managers.Pacman/Pacman.cs:159-172 — `src/UniGetUI.PackageEngine.Managers.Dnf/Dnf.cs` and `src/UniGetUI.PackageEngine.Managers.Pacman/Pacman.cs` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 5 separate duplicated blocks between them, totalling at least 99 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own. Read the line range as the matched WINDOW rather than a finished unit: at `src/UniGetUI.PackageEngine.Managers.Dnf/Dnf.cs:166` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The `return` at the foot of the matched lines is the enclosing body's own terminal exit, not an early one: it moves with them unchanged, and each site calls the extracted unit from the position that `return` occupied — no decision has to be handed back and re-acted on.
Duplicated block (14 lines × 2) src/UniGetUI.PackageEngine.Managers.PowerShell/PowerShell.cs:154— src/UniGetUI.PackageEngine.Managers.PowerShell/PowerShell.cs:154-167 | src/UniGetUI.PackageEngine.Managers.PowerShell7/PowerShell7.cs:194-207 — `src/UniGetUI.PackageEngine.Managers.PowerShell/PowerShell.cs` and `src/UniGetUI.PackageEngine.Managers.PowerShell7/PowerShell7.cs` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 4 separate duplicated blocks between them, totalling at least 85 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (10 lines × 2) src/UniGetUI.PackageEngine.Managers.Scoop/Helpers/ScoopTable.cs:40— src/UniGetUI.PackageEngine.Managers.Scoop/Helpers/ScoopTable.cs:40-49 | src/UniGetUI.PackageEngine.PackageManagerClasses/Manager/Classes/ManagerTable.cs:39-48 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `src/UniGetUI.PackageEngine.PackageManagerClasses/Manager/Classes/ManagerTable.cs:39` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (10 lines × 2) src/UniGetUI.Avalonia/ViewModels/Pages/AboutPages/ContributorsViewModel.cs:28— src/UniGetUI.Avalonia/ViewModels/Pages/AboutPages/ContributorsViewModel.cs:28-37 | src/UniGetUI.Avalonia/ViewModels/Pages/AboutPages/TranslatorsViewModel.cs:30-39 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (10 lines × 2) src/UniGetUI.PackageEngine.AgentBroker/BrokerPolicyDocumentValidator.cs:55— src/UniGetUI.PackageEngine.AgentBroker/BrokerPolicyDocumentValidator.cs:55-64 | src/UniGetUI.PackageEngine.AgentBroker/BrokerPolicyInspector.cs:140-149 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (8 lines × 3) src/UniGetUI.Avalonia/Infrastructure/AvaloniaPackageOperationHelper.cs:38— src/UniGetUI.Avalonia/Infrastructure/AvaloniaPackageOperationHelper.cs:38-45 | src/UniGetUI.Avalonia/Infrastructure/AvaloniaPackageOperationHelper.cs:54-61 | src/UniGetUI.Avalonia/Views/SoftwarePages/SoftwareUpdatesPage.cs:404-411 — there are 3 copies across 2 file(s) — more copies than files, so at least one file holds the block twice. Extract it once into a single shared function every call site can reach and call it from all 3 sites; resolving a subset leaves the remainder to drift apart. Read the line range as the matched WINDOW rather than a finished unit: at `src/UniGetUI.Avalonia/Infrastructure/AvaloniaPackageOperationHelper.cs:38` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (8 lines × 3) src/UniGetUI.PackageEngine.AgentBroker/BrokerPolicyDocumentValidator.cs:44— src/UniGetUI.PackageEngine.AgentBroker/BrokerPolicyDocumentValidator.cs:44-51 | src/UniGetUI.PackageEngine.AgentBroker/BrokerPolicyInspector.cs:129-136 | src/UniGetUI.PackageEngine.AgentBroker/PolicyManagement/BrokerPolicyManagementService.cs:156-163 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 3 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 3 times. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (8 lines × 3) src/UniGetUI.PackageEngine.Managers.Bun/Bun.cs:242— src/UniGetUI.PackageEngine.Managers.Bun/Bun.cs:242-249 | src/UniGetUI.PackageEngine.Managers.Cargo/Cargo.cs:196-203 | src/UniGetUI.PackageEngine.Managers.Npm/Npm.cs:444-451 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 3 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 3 times. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
BarePragmaDisable src/UniGetUI.Avalonia/Infrastructure/AvaloniaAutoUpdater.cs:1503— #pragma warning disable SYSLIB0057 — the disable is closed again below, so its scope is not the problem; what it records is no reason: there is nothing on the directive line, and no ordinary comment attached to it either side. A suppression is a decision somebody made, and without the reason the next reader cannot tell a considered exception from an unexamined one, so it is never revisited and it outlives the code it was written for. Put the reason on the directive line — what makes this site legitimately different — or fix what the rule is pointing at and delete the pair. A rationale in the member's documentation comment does not clear this row and is not meant to: it explains the member to its callers, and the next person to touch the suppression is not reading it for that.
BarePragmaDisable src/UniGetUI.PackageEngine.Managers.WinGet/ClientHelpers/WinGetIconsHelper.cs:29— #pragma warning disable SYSLIB0014 — the disable is closed again below, so its scope is not the problem; what it records is no reason: there is nothing on the directive line, and no ordinary comment attached to it either side. A suppression is a decision somebody made, and without the reason the next reader cannot tell a considered exception from an unexamined one, so it is never revisited and it outlives the code it was written for. Put the reason on the directive line — what makes this site legitimately different — or fix what the rule is pointing at and delete the pair. A rationale in the member's documentation comment does not clear this row and is not meant to: it explains the member to its callers, and the next person to touch the suppression is not reading it for that.
Duplicated block (30 lines × 2) src/UniGetUI.PackageEngine.Managers.Flatpak/Flatpak.cs:128— src/UniGetUI.PackageEngine.Managers.Flatpak/Flatpak.cs:128-157 | src/UniGetUI.PackageEngine.Managers.Snap/Snap.cs:127-156 — `src/UniGetUI.PackageEngine.Managers.Flatpak/Flatpak.cs` and `src/UniGetUI.PackageEngine.Managers.Snap/Snap.cs` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 4 separate duplicated blocks between them, totalling at least 112 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (30 lines × 2) src/UniGetUI.PackageEngine.Managers.Flatpak/Flatpak.cs:161— src/UniGetUI.PackageEngine.Managers.Flatpak/Flatpak.cs:161-190 | src/UniGetUI.PackageEngine.Managers.Snap/Snap.cs:160-189 — `src/UniGetUI.PackageEngine.Managers.Flatpak/Flatpak.cs` and `src/UniGetUI.PackageEngine.Managers.Snap/Snap.cs` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 4 separate duplicated blocks between them, totalling at least 112 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (20 lines × 2) src/UniGetUI.PackageEngine.AgentBroker/PolicyWriteElevation/Interop/WindowsProtectedLocationVerifier.cs:185— src/UniGetUI.PackageEngine.AgentBroker/PolicyWriteElevation/Interop/WindowsProtectedLocationVerifier.cs:185-204 | src/UniGetUI.PackageEngine.AgentBroker/PolicyWriteElevation/Interop/WindowsProtectedLocationVerifier.cs:238-257 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/UniGetUI.PackageEngine.AgentBroker/PolicyWriteElevation/Interop/WindowsProtectedLocationVerifier.cs:185` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (20 lines × 2) src/UniGetUI.PackageEngine.Managers.Bun/Bun.cs:252— src/UniGetUI.PackageEngine.Managers.Bun/Bun.cs:252-271 | src/UniGetUI.PackageEngine.Managers.Pip/Pip.cs:994-1018 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (22 lines × 2) src/UniGetUI.PackageEngine.Managers.Scoop/Helpers/ScoopTable.cs:15— src/UniGetUI.PackageEngine.Managers.Scoop/Helpers/ScoopTable.cs:15-36 | src/UniGetUI.PackageEngine.PackageManagerClasses/Manager/Classes/ManagerTable.cs:9-30 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (22 lines × 2) src/UniGetUI.PackageEngine.Managers.Chocolatey/Chocolatey.cs:360— src/UniGetUI.PackageEngine.Managers.Chocolatey/Chocolatey.cs:360-381 | src/UniGetUI.PackageEngine.Managers.Chocolatey/Chocolatey.cs:405-426 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/UniGetUI.PackageEngine.Managers.Chocolatey/Chocolatey.cs:360` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (18–19 lines × 2) src/UniGetUI.Avalonia/Infrastructure/MaintenanceScheduler.cs:63— src/UniGetUI.Avalonia/Infrastructure/MaintenanceScheduler.cs:63-81 | src/UniGetUI.Tui/Infrastructure/TuiMaintenance.cs:58-75 — before extracting anything, compare `src/UniGetUI.Avalonia/Infrastructure/MaintenanceScheduler.cs` and `src/UniGetUI.Tui/Infrastructure/TuiMaintenance.cs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 35 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `src/UniGetUI.Avalonia/Infrastructure/MaintenanceScheduler.cs:59` calls `ImportantInfo` and `src/UniGetUI.Tui/Infrastructure/TuiMaintenance.cs:54` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (18–19 lines × 2) src/UniGetUI.PackageEngine.Operations/AbstractOperation.cs:490— src/UniGetUI.PackageEngine.Operations/AbstractOperation.cs:490-507 | src/UniGetUI.PackageEngine.Operations/AbstractOperation.cs:587-605 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/UniGetUI.PackageEngine.Operations/AbstractOperation.cs:490` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (17–19 lines × 2) src/UniGetUI.Avalonia/Infrastructure/GitHubCloudBackupService.cs:80— src/UniGetUI.Avalonia/Infrastructure/GitHubCloudBackupService.cs:80-96 | src/UniGetUI.Interface.IpcApi/IpcBackupApi.cs:469-487 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `src/UniGetUI.Avalonia/Infrastructure/GitHubCloudBackupService.cs:80` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (17–19 lines × 2) src/UniGetUI.PackageEngine.Managers.Apt/Helpers/AptPkgDetailsHelper.cs:28— src/UniGetUI.PackageEngine.Managers.Apt/Helpers/AptPkgDetailsHelper.cs:28-44 | src/UniGetUI.PackageEngine.Managers.Dnf/Helpers/DnfPkgDetailsHelper.cs:31-49 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `src/UniGetUI.PackageEngine.Managers.Apt/Helpers/AptPkgDetailsHelper.cs:28` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (17 lines × 2) src/UniGetUI.Interface.IpcApi/IpcServer.cs:741— src/UniGetUI.Interface.IpcApi/IpcServer.cs:741-757 | src/UniGetUI.Interface.IpcApi/IpcServer.cs:802-818 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/UniGetUI.Interface.IpcApi/IpcServer.cs:741` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (17 lines × 2) src/UniGetUI.PackageEngine.Managers.Dotnet/DotNet.cs:217— src/UniGetUI.PackageEngine.Managers.Dotnet/DotNet.cs:217-233 | src/UniGetUI.PackageEngine.Managers.Scoop/Scoop.cs:211-227 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `src/UniGetUI.PackageEngine.Managers.Dotnet/DotNet.cs:217` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (17 lines × 3) src/UniGetUI.Interface.IpcApi/IpcServer.cs:1616— src/UniGetUI.Interface.IpcApi/IpcServer.cs:1616-1632 | src/UniGetUI.Interface.IpcApi/IpcServer.cs:1648-1664 | src/UniGetUI.Interface.IpcApi/IpcServer.cs:1750-1766 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/UniGetUI.Interface.IpcApi/IpcServer.cs:1616` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (17 lines × 3) src/UniGetUI.PackageEngine.Managers.Chocolatey/Chocolatey.cs:555— src/UniGetUI.PackageEngine.Managers.Chocolatey/Chocolatey.cs:555-572 | src/UniGetUI.PackageEngine.Managers.PowerShell/PowerShell.cs:170-186 | src/UniGetUI.PackageEngine.Managers.PowerShell7/PowerShell7.cs:210-226 — `src/UniGetUI.PackageEngine.Managers.PowerShell/PowerShell.cs` and `src/UniGetUI.PackageEngine.Managers.PowerShell7/PowerShell7.cs` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 4 separate duplicated blocks between them, totalling at least 85 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own.
Duplicated block (16 lines × 2) src/UniGetUI.Avalonia/ViewModels/Pages/SettingsPages/PolicyEditor/PolicyEditorSessionViewModel.cs:628— src/UniGetUI.Avalonia/ViewModels/Pages/SettingsPages/PolicyEditor/PolicyEditorSessionViewModel.cs:628-643 | src/UniGetUI.Avalonia/ViewModels/Pages/SettingsPages/PolicyEditor/PolicyEditorSessionViewModel.cs:655-670 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/UniGetUI.Avalonia/ViewModels/Pages/SettingsPages/PolicyEditor/PolicyEditorSessionViewModel.cs:628` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (16 lines × 2) src/UniGetUI.PackageEngine.Managers.Pacman/Helpers/PacmanPkgDetailsHelper.cs:60— src/UniGetUI.PackageEngine.Managers.Pacman/Helpers/PacmanPkgDetailsHelper.cs:60-75 | src/UniGetUI.PackageEngine.Managers.Pacman/Helpers/PacmanPkgDetailsHelper.cs:100-115 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/UniGetUI.PackageEngine.Managers.Pacman/Helpers/PacmanPkgDetailsHelper.cs:60` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (12 lines × 2) src/UniGetUI.PackageEngine.Managers.Chocolatey/Chocolatey.cs:152— src/UniGetUI.PackageEngine.Managers.Chocolatey/Chocolatey.cs:152-163 | src/UniGetUI.PackageEngine.Managers.Pip/Pip.cs:97-108 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (12 lines × 2) src/UniGetUI.PackageEngine.Managers.PowerShell/PowerShell.cs:201— src/UniGetUI.PackageEngine.Managers.PowerShell/PowerShell.cs:201-212 | src/UniGetUI.PackageEngine.Managers.PowerShell7/PowerShell7.cs:151-162 — `src/UniGetUI.PackageEngine.Managers.PowerShell/PowerShell.cs` and `src/UniGetUI.PackageEngine.Managers.PowerShell7/PowerShell7.cs` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 4 separate duplicated blocks between them, totalling at least 85 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own. Read the line range as the matched WINDOW rather than a finished unit: at `src/UniGetUI.PackageEngine.Managers.PowerShell/PowerShell.cs:201` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it. Note first that the copies are not typed on the same thing: the declarations holding them bind `manager` to `PowerShell` in one and `PowerShell7` in another, and the duplicated lines use it. The extracted unit therefore needs a parameter type that fits BOTH — their common supertype where they have one, or a new abstraction over them where they do not — and settling that is the step that comes BEFORE the extraction above. Where the two types are deliberately unrelated, the duplication is the price of that separation and the honest resolution is to record the decision rather than to extract.
Duplicated block (9–11 lines × 2) src/UniGetUI.Avalonia/ViewModels/SoftwarePages/PackagesPageViewModel.cs:1224— src/UniGetUI.Avalonia/ViewModels/SoftwarePages/PackagesPageViewModel.cs:1224-1234 | src/UniGetUI.Tui/Views/Pages/PackageListPage.cs:905-913 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (9–11 lines × 2) src/UniGetUI.Avalonia/Views/Controls/Settings/CheckboxCard.cs:161— src/UniGetUI.Avalonia/Views/Controls/Settings/CheckboxCard.cs:161-169 | src/UniGetUI.Avalonia/Views/Controls/Settings/CheckboxCard.cs:233-243 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/UniGetUI.Avalonia/Views/Controls/Settings/CheckboxCard.cs:233` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
Duplicated block (6 lines × 3) src/UniGetUI.Avalonia/Views/SoftwarePages/DiscoverSoftwarePage.cs:280— src/UniGetUI.Avalonia/Views/SoftwarePages/DiscoverSoftwarePage.cs:280-285 | src/UniGetUI.Avalonia/Views/SoftwarePages/PackageBundlesPage.cs:177-182 | src/UniGetUI.Avalonia/Views/SoftwarePages/SoftwareUpdatesPage.cs:270-275 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from all 3 call sites, so a change lands once. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `src/UniGetUI.Avalonia/Views/SoftwarePages/SoftwareUpdatesPage.cs:267` calls `Add` and `src/UniGetUI.Avalonia/Views/SoftwarePages/DiscoverSoftwarePage.cs:277` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (6 lines × 3) src/UniGetUI.Avalonia/ViewModels/Pages/LogPages/UniGetUILogPageViewModel.cs:73— src/UniGetUI.Avalonia/ViewModels/Pages/LogPages/UniGetUILogPageViewModel.cs:73-81 | src/UniGetUI.Interface.IpcApi/IpcLogsApi.cs:177-184 | src/UniGetUI.Tui/Views/Pages/LogsPage.cs:267-272 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 3 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 3 times. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (6–7 lines × 2) src/UniGetUI.Avalonia/Views/SoftwarePages/InstalledPackagesPage.cs:458— src/UniGetUI.Avalonia/Views/SoftwarePages/InstalledPackagesPage.cs:458-463 | src/UniGetUI.Avalonia/Views/SoftwarePages/SoftwareUpdatesPage.cs:437-443 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (6–7 lines × 2) src/UniGetUI.Avalonia/Infrastructure/AvaloniaPackageOperationHelper.cs:158— src/UniGetUI.Avalonia/Infrastructure/AvaloniaPackageOperationHelper.cs:158-163 | src/UniGetUI.Avalonia/Infrastructure/AvaloniaPackageOperationHelper.cs:214-220 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/UniGetUI.Avalonia/Infrastructure/AvaloniaPackageOperationHelper.cs:158` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Low cohesion: MainWindow (LCOM4 9) src/UniGetUI.Avalonia/Views/MainWindow.axaml.cs:50— MainWindow's methods fall into 9 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 9 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
Low cohesion: AbstractPackagesPage (LCOM4 6) src/UniGetUI.Avalonia/Views/SoftwarePages/AbstractPackagesPage.axaml.cs:32— AbstractPackagesPage's methods fall into 6 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 6 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
Skeleton type — most members are unfinished src/UniGetUI.PackageEngine.Managers.Vcpkg/Helpers/VcpkgPkgDetailsHelper.cs:13— `VcpkgPkgDetailsHelper` has 3 unfinished members out of 5 declared members (methods, properties, indexers and events, whether or not each carries a body) — a scaffolded type that was never implemented.
Skeleton type — most members are unfinished src/UniGetUI.PackageEngine.Managers.Vcpkg/Helpers/VcpkgSourceHelper.cs:8— `VcpkgSourceHelper` has 4 unfinished members out of 5 declared members (methods, properties, indexers and events, whether or not each carries a body) — a scaffolded type that was never implemented.
Hollow method — returns a constant without doing the work src/UniGetUI.PackageEngine.Operations/PackageOperations.cs:1320— `IsWinGetManager` looks like it should compute a result but its body just returns a constant — a placeholder return that was never filled in.
Hollow method — returns a constant without doing the work src/UniGetUI.PackageEngine.Operations/SourceOperations.cs:144— `IsWinGetManager` looks like it should compute a result but its body just returns a constant — a placeholder return that was never filled in.
Sync-over-async (deadlock risk) through `.Wait(…)` src/UniGetUI.Avalonia/CrashHandler.cs:197— `.Wait(…)` blocks this thread until the task completes or the bound expires — sync-over-async: it can deadlock under a synchronization context and it parks a thread while it waits. `await` the task (with `.WaitAsync(timeout, token)` where the bound matters).
Sync-over-async (deadlock risk) through `.Wait(…)` src/UniGetUI.Core.Tools/ShortcutFileRemover.cs:202— `.Wait(…)` blocks this thread until the task completes or the bound expires — sync-over-async: it can deadlock under a synchronization context and it parks a thread while it waits. `await` the task (with `.WaitAsync(timeout, token)` where the bound matters).
X18 · Disposal-pattern correctness· Disposable created and abandoned in the method that made it · ×2
Disposable created and abandoned in the method that made it src/UniGetUI.PackageEngine.Managers.Dotnet/DotNet.cs:151— `process` is a `Process`, which implements `IDisposable`, and it is created here (line 151). Every use of it in `_loadManagerExecutableFile` 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 process = …;`), which releases it at the end of the scope on every path including a throw.
Disposable created and abandoned in the method that made it src/UniGetUI.PackageEngine.Managers.Dotnet/DotNet.cs:171— `process` is a `Process`, which implements `IDisposable`, and it is created here (line 171). Every use of it in `_loadManagerVersion` 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 process = …;`), which releases it at the end of the scope on every path including a throw.
C1 · Data Protection· No data-protection/encryption · ×1
No data-protection/encryption — No data-protection or encryption usage (ASP.NET Data Protection, AES, column encryption, PBKDF2) was found — sensitive data at rest may be unprotected. If TDE/KMS/vault is delegated to infrastructure, ignore.
PolicyEditorSessionViewModel.SaveCoreAsync (cyclomatic 53) src/UniGetUI.Avalonia/ViewModels/Pages/SettingsPages/PolicyEditor/PolicyEditorSessionViewModel.cs:509— PolicyEditorSessionViewModel.SaveCoreAsync has cyclomatic complexity 53 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
MainWindow.OnWindowsWndProc (cyclomatic 48) src/UniGetUI.Avalonia/Views/MainWindow.axaml.cs:1451— MainWindow.OnWindowsWndProc has cyclomatic complexity 48 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
CargoBinaryResolver.ResolveAsync (cyclomatic 48) src/UniGetUI.PackageEngine.Managers.Cargo/CargoBinaryResolver.cs:36— CargoBinaryResolver.ResolveAsync has cyclomatic complexity 48 (threshold 15). Of this number, 44 points are the body's own statements and 4 belong to one function literal inside it that branches. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
CargoInstallTracker.InstallAsync (cyclomatic 35) src/UniGetUI.PackageEngine.Managers.Cargo/CargoInstallTracker.cs:85— CargoInstallTracker.InstallAsync has cyclomatic complexity 35 (threshold 15). Of this number, 31 points are the body's own statements and 4 belong to 2 function literals inside it that branch. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
Bun.ParseBunOutdatedTable (cyclomatic 34) src/UniGetUI.PackageEngine.Managers.Bun/Bun.cs:377— Bun.ParseBunOutdatedTable has cyclomatic complexity 34 (threshold 15). Most of this is not in the body itself: 14 of the 34 points are its own statements and the rest belongs to 2 function literals inside it that branch (lines 407, 408). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
PowerShellPkgOperationHelper._getOperationParameters (cyclomatic 34) src/UniGetUI.PackageEngine.Managers.PowerShell/Helpers/PowerShellPkgOperationHelper.cs:21— PowerShellPkgOperationHelper._getOperationParameters has cyclomatic complexity 34 (threshold 15). Of this number, 33 points are the body's own statements and 1 belongs to one function literal inside it that branches. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
InstallOptionsDialog.Build (cyclomatic 34) src/UniGetUI.Tui/Views/Dialogs/InstallOptionsDialog.cs:128— InstallOptionsDialog.Build has cyclomatic complexity 34 (threshold 15). Most of this is not in the body itself: 10 of the 34 points are its own statements and the rest belongs to 16 function literals inside it that branch (lines 219, 204, 168, …). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
WinGetPkgOperationHelper._getOperationResult (cyclomatic 31) src/UniGetUI.PackageEngine.Managers.WinGet/Helpers/WinGetPkgOperationHelper.cs:331— WinGetPkgOperationHelper._getOperationResult has cyclomatic complexity 31 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
AbstractOperation.MainThreadCore (cyclomatic 30) src/UniGetUI.PackageEngine.Operations/AbstractOperation.cs:257— AbstractOperation.MainThreadCore has cyclomatic complexity 30 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
WinGetPkgOperationHelper._getOperationParameters (cyclomatic 30) src/UniGetUI.PackageEngine.Managers.WinGet/Helpers/WinGetPkgOperationHelper.cs:115— WinGetPkgOperationHelper._getOperationParameters has cyclomatic complexity 30 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
AbstractPackagesPage.AbstractPackagesPage.ctor (cyclomatic 29) src/UniGetUI.Avalonia/Views/SoftwarePages/AbstractPackagesPage.axaml.cs:47— AbstractPackagesPage.AbstractPackagesPage.ctor has cyclomatic complexity 29 (threshold 15). Most of this is not in the body itself: 12 of the 29 points are its own statements and the rest belongs to 6 function literals inside it that branch (lines 160, 113, 75, …). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
AbstractOperation._runOperation (cyclomatic 29) src/UniGetUI.PackageEngine.Operations/AbstractOperation.cs:471— AbstractOperation._runOperation has cyclomatic complexity 29 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
AbstractProcessOperation.PerformOperation (cyclomatic 29) src/UniGetUI.PackageEngine.Operations/AbstractProcessOperation.cs:96— AbstractProcessOperation.PerformOperation has cyclomatic complexity 29 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
AbstractPackageLoader.ReloadPackages (cyclomatic 28) src/UniGetUI.PackageEngine.PackageLoader/AbstractPackageLoader.cs:159— AbstractPackageLoader.ReloadPackages has cyclomatic complexity 28 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
CargoArchive.Read (cyclomatic 28) src/UniGetUI.PackageEngine.Managers.Cargo/CargoArchive.cs:18— CargoArchive.Read has cyclomatic complexity 28 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
CargoPkgOperationHelper._getOperationParameters (cyclomatic 28) src/UniGetUI.PackageEngine.Managers.Cargo/Helpers/CargoPkgOperationHelper.cs:18— CargoPkgOperationHelper._getOperationParameters has cyclomatic complexity 28 (threshold 15). Of this number, 23 points are the body's own statements and 5 belong to one function literal inside it that branches. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
ScoopPkgDetailsHelper.GetDetails_UnSafe (cyclomatic 28) src/UniGetUI.PackageEngine.Managers.Scoop/Helpers/ScoopPkgDetailsHelper.cs:17— ScoopPkgDetailsHelper.GetDetails_UnSafe has cyclomatic complexity 28 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
MainWindow.Window_KeyDown (cyclomatic 27) src/UniGetUI.Avalonia/Views/MainWindow.axaml.cs:338— MainWindow.Window_KeyDown has cyclomatic complexity 27 (threshold 15). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
PackageManagerPage.BuildPage (cyclomatic 27) src/UniGetUI.Avalonia/Views/Pages/SettingsPages/PackageManagerPage.axaml.cs:56— PackageManagerPage.BuildPage has cyclomatic complexity 27 (threshold 15). Of this number, 15 points are the body's own statements and 12 belong to 6 function literals inside it that branch. To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
BrokerRequestValidator.Validate (cyclomatic 27) src/UniGetUI.PackageEngine.AgentBroker/BrokerRequestValidator.cs:50— BrokerRequestValidator.Validate has cyclomatic complexity 27 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
CargoManagedInstaller.TryPerformAsync (cyclomatic 27) REDACTED:18— CargoManagedInstaller.TryPerformAsync has cyclomatic complexity 27 (threshold 15). Of this number, 23 points are the body's own statements and 4 belong to 2 function literals inside it that branch. To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
MainWindow.HitTestResizeBorder (cyclomatic 25) src/UniGetUI.Avalonia/Views/MainWindow.axaml.cs:1267— MainWindow.HitTestResizeBorder has cyclomatic complexity 25 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
WindowsPeerAuthenticator.Authenticate (cyclomatic 25) src/UniGetUI.PackageEngine.AgentBroker/PolicyWriteElevation/Interop/WindowsPeerAuthenticator.cs:72— WindowsPeerAuthenticator.Authenticate has cyclomatic complexity 25 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
BrokerRequestValidator.FindUnsupportedOptions (cyclomatic 25) src/UniGetUI.PackageEngine.AgentBroker/BrokerRequestValidator.cs:192— BrokerRequestValidator.FindUnsupportedOptions has cyclomatic complexity 25 (threshold 15). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
PacmanPkgDetailsHelper.GetDetails_UnSafe (cyclomatic 25) src/UniGetUI.PackageEngine.Managers.Pacman/Helpers/PacmanPkgDetailsHelper.cs:15— PacmanPkgDetailsHelper.GetDetails_UnSafe has cyclomatic complexity 25 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
AptPkgDetailsHelper.GetDetails_UnSafe (cyclomatic 24) src/UniGetUI.PackageEngine.Managers.Apt/Helpers/AptPkgDetailsHelper.cs:15— AptPkgDetailsHelper.GetDetails_UnSafe has cyclomatic complexity 24 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
AgentPolicyInspectorViewModel.ApplyManagementSnapshot (cyclomatic 23) src/UniGetUI.Avalonia/ViewModels/Pages/SettingsPages/AgentPolicyInspectorViewModel.cs:669— AgentPolicyInspectorViewModel.ApplyManagementSnapshot has cyclomatic complexity 23 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top. This is NOT this file's highest cyclomatic complexity: AgentPolicyInspectorViewModel.HelpForRow (cyclomatic 46) is higher and carries no row of its own — it was excluded as a flat dispatcher (a long switch/match over independent cases: many branches, almost no nesting), which this dimension does not treat as a refactor obligation. It is named here so the ranking you see in this file is not mistaken for the whole of it; the excluded method is counted neither in this dimension's figures nor in its score.
AvaloniaAutoUpdater.CheckAndInstallUpdatesCoreAsync (cyclomatic 23) src/UniGetUI.Avalonia/Infrastructure/AvaloniaAutoUpdater.cs:459— AvaloniaAutoUpdater.CheckAndInstallUpdatesCoreAsync has cyclomatic complexity 23 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
BaseNuGetDetailsHelper.GetDetails_UnSafe (cyclomatic 23) src/UniGetUI.PackageEngine.Managers.Generic.NuGet/BaseNuGetDetailsHelper.cs:20— BaseNuGetDetailsHelper.GetDetails_UnSafe has cyclomatic complexity 23 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
UpdaterDownloadEngine.DownloadInstallerPartAsync (cyclomatic 22) src/UniGetUI.Core.Tools/UpdaterDownloadEngine.cs:102— UpdaterDownloadEngine.DownloadInstallerPartAsync has cyclomatic complexity 22 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
CargoInstallTracker.Recover (cyclomatic 22) src/UniGetUI.PackageEngine.Managers.Cargo/CargoInstallTracker.cs:242— CargoInstallTracker.Recover has cyclomatic complexity 22 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
ScoopPkgOperationHelper._getOperationParameters (cyclomatic 22) src/UniGetUI.PackageEngine.Managers.Scoop/Helpers/ScoopPkgOperationHelper.cs:15— ScoopPkgOperationHelper._getOperationParameters has cyclomatic complexity 22 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
ManageShortcutsViewModel.SaveChanges (cyclomatic 21) src/UniGetUI.Avalonia/ViewModels/DialogPages/ManageShortcutsViewModel.cs:275— ManageShortcutsViewModel.SaveChanges has cyclomatic complexity 21 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
WindowsPolicyWriteElevator.ExchangeAsync (cyclomatic 21) src/UniGetUI.PackageEngine.AgentBroker/PolicyWriteElevation/WindowsPolicyWriteElevator.cs:302— WindowsPolicyWriteElevator.ExchangeAsync has cyclomatic complexity 21 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
ProcessTaskLogger.AsColoredString (cyclomatic 21) src/UniGetUI.PackageEngine.PackageManagerClasses/Manager/Classes/ManagerLogger.cs:224— ProcessTaskLogger.AsColoredString has cyclomatic complexity 21 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
CargoInstallTracker.GetBuildArgumentsAsync (cyclomatic 21) src/UniGetUI.PackageEngine.Managers.Cargo/CargoInstallTracker.cs:19— CargoInstallTracker.GetBuildArgumentsAsync has cyclomatic complexity 21 (threshold 15). Of this number, 19 points are the body's own statements and 2 belong to one function literal inside it that branches. To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
SnapPkgDetailsHelper.GetDetails_UnSafe (cyclomatic 21) src/UniGetUI.PackageEngine.Managers.Snap/Helpers/SnapPkgDetailsHelper.cs:15— SnapPkgDetailsHelper.GetDetails_UnSafe has cyclomatic complexity 21 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
CatalogEditorPage.PinVersionAsync (cyclomatic 20) src/UniGetUI.Avalonia/Views/SoftwarePages/CatalogEditorPage.cs:248— CatalogEditorPage.PinVersionAsync has cyclomatic complexity 20 (threshold 15). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
IpcClient.BuildPackageQueryParameters (cyclomatic 20) src/UniGetUI.Interface.IpcApi/IpcClient.cs:1322— IpcClient.BuildPackageQueryParameters has cyclomatic complexity 20 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
IpcClient.GetRequestTimeout (cyclomatic 20) src/UniGetUI.Interface.IpcApi/IpcClient.cs:1466— IpcClient.GetRequestTimeout has cyclomatic complexity 20 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
BrokerRequestValidator.CheckVersion (cyclomatic 20) src/UniGetUI.PackageEngine.AgentBroker/BrokerRequestValidator.cs:355— BrokerRequestValidator.CheckVersion has cyclomatic complexity 20 (threshold 15). Of this number, 18 points are the body's own statements and 2 belong to one function literal inside it that branches. To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
DownloadOperation.PerformOperation (cyclomatic 20) src/UniGetUI.PackageEngine.Operations/DownloadOperation.cs:114— DownloadOperation.PerformOperation has cyclomatic complexity 20 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
FakePackageManagerProcess.RunPackageVerb (cyclomatic 20) src/UniGetUI.Tui/FakeData/FakePackageManagerProcess.cs:100— FakePackageManagerProcess.RunPackageVerb has cyclomatic complexity 20 (threshold 15). Of this number, 17 points are the body's own statements and 3 belong to 3 function literals inside it that branch. To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
BoundedNamedPipeBrokerTransport.ReadResponseAsync (cyclomatic 19) src/UniGetUI.PackageEngine.AgentBroker/PolicyWriteElevation/Shared/BoundedNamedPipeBrokerTransport.cs:124— BoundedNamedPipeBrokerTransport.ReadResponseAsync has cyclomatic complexity 19 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
PackageOperation._getPostInstallOps (cyclomatic 19) src/UniGetUI.PackageEngine.Operations/PackageOperations.cs:1469— PackageOperation._getPostInstallOps has cyclomatic complexity 19 (threshold 15). Of this number, 14 points are the body's own statements and 5 belong to 2 function items inside it that branch. To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
StartMenuShortcutsDatabase.HandleNewShortcuts (cyclomatic 19) src/UniGetUI.PackageEngine.PackageManagerClasses/Packages/Classes/StartMenuShortcutsDatabase.cs:611— StartMenuShortcutsDatabase.HandleNewShortcuts has cyclomatic complexity 19 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
PowerShell7PkgOperationHelper._getOperationParameters (cyclomatic 19) src/UniGetUI.PackageEngine.Managers.PowerShell7/Helpers/PowerShell7PkgOperationHelper.cs:15— PowerShell7PkgOperationHelper._getOperationParameters has cyclomatic complexity 19 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
TuiCommandLine.Parse (cyclomatic 19) src/UniGetUI.Tui/Infrastructure/TuiCommandLine.cs:71— TuiCommandLine.Parse has cyclomatic complexity 19 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
PackageListPage.BuildActions (cyclomatic 19) src/UniGetUI.Tui/Views/Pages/PackageListPage.cs:1083— PackageListPage.BuildActions has cyclomatic complexity 19 (threshold 15). Of this number, 13 points are the body's own statements and 6 belong to 6 function literals inside it that branch. To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
PolicyEditorDialogViewModel.OnSessionPropertyChanged (cyclomatic 18) src/UniGetUI.Avalonia/ViewModels/Pages/SettingsPages/PolicyEditor/PolicyEditorDialogViewModel.cs:139— PolicyEditorDialogViewModel.OnSessionPropertyChanged has cyclomatic complexity 18 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
PolicyFindingPresentation.DescribeLocation (cyclomatic 18) src/UniGetUI.Avalonia/ViewModels/Pages/SettingsPages/PolicyEditor/PolicyValidationFinding.cs:211— PolicyFindingPresentation.DescribeLocation has cyclomatic complexity 18 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top. This is NOT this file's highest cyclomatic complexity: PolicyFindingPresentation.FieldLabel (cyclomatic 51) is higher and carries no row of its own — it was excluded as a flat dispatcher (a long switch/match over independent cases: many branches, almost no nesting), which this dimension does not treat as a refactor obligation. It is named here so the ranking you see in this file is not mistaken for the whole of it; the excluded method is counted neither in this dimension's figures nor in its score.
SoftwareCatalogViewModel.UpdateStates (cyclomatic 18) src/UniGetUI.Avalonia/ViewModels/SoftwarePages/SoftwareCatalogViewModel.cs:489— SoftwareCatalogViewModel.UpdateStates has cyclomatic complexity 18 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
PolicyElevationLaunchArguments.TryParse (cyclomatic 18) src/UniGetUI.PackageEngine.AgentBroker/PolicyWriteElevation/Protocol/PolicyElevationArguments.cs:44— PolicyElevationLaunchArguments.TryParse has cyclomatic complexity 18 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
CoreData.GetNewDataDirectoryOrMoveOld (cyclomatic 18) src/UniGetUI.Core.Data/CoreData.cs:422— CoreData.GetNewDataDirectoryOrMoveOld has cyclomatic complexity 18 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
PackageOperation.PerformBrokerOperation (cyclomatic 18) src/UniGetUI.PackageEngine.Operations/PackageOperations.cs:451— PackageOperation.PerformBrokerOperation has cyclomatic complexity 18 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
PEInterface.CreateManagers (cyclomatic 18) src/UniGetUI.PackageEngine.PackageEngine/PEInterface.cs:85— PEInterface.CreateManagers has cyclomatic complexity 18 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
NativeTaskLogger.AsColoredString (cyclomatic 18) src/UniGetUI.PackageEngine.PackageManagerClasses/Manager/Classes/ManagerLogger.cs:398— NativeTaskLogger.AsColoredString has cyclomatic complexity 18 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
Pip.ResolveLatestCompatibleVersion (cyclomatic 18) src/UniGetUI.PackageEngine.Managers.Pip/Pip.cs:611— Pip.ResolveLatestCompatibleVersion has cyclomatic complexity 18 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
FakeOperationHelper._getOperationParameters (cyclomatic 18) src/UniGetUI.Tui/FakeData/FakePackageManager.cs:230— FakeOperationHelper._getOperationParameters has cyclomatic complexity 18 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
MainWindow.OnWindowKeyDown (cyclomatic 18) src/UniGetUI.Tui/Views/MainWindow.cs:477— MainWindow.OnWindowKeyDown has cyclomatic complexity 18 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
CrashHandler.ReportFatalException (cyclomatic 17) src/UniGetUI.Avalonia/CrashHandler.cs:142— CrashHandler.ReportFatalException has cyclomatic complexity 17 (threshold 15). Of this number, 14 points are the body's own statements and 3 belong to one function item inside it that branches. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
InstallOptionsViewModel.InstallOptionsViewModel.ctor (cyclomatic 17) src/UniGetUI.Avalonia/ViewModels/DialogPages/InstallOptionsViewModel.cs:268— InstallOptionsViewModel.InstallOptionsViewModel.ctor has cyclomatic complexity 17 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
OperationViewModel.RebuildMenu (cyclomatic 17) src/UniGetUI.Avalonia/ViewModels/DialogPages/OperationViewModel.cs:242— OperationViewModel.RebuildMenu has cyclomatic complexity 17 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
PolicyJsonEditor.TryFindProperty (cyclomatic 17) src/UniGetUI.Avalonia/Views/Controls/PolicyJsonEditor.cs:106— PolicyJsonEditor.TryFindProperty has cyclomatic complexity 17 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
SvgIcon.ParseSvg (cyclomatic 17) src/UniGetUI.Avalonia/Views/Controls/SvgIcon.cs:114— SvgIcon.ParseSvg has cyclomatic complexity 17 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
TrayService.UpdateStatus (cyclomatic 17) src/UniGetUI.Avalonia/Infrastructure/TrayService.cs:62— TrayService.UpdateStatus has cyclomatic complexity 17 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
WinGet.GetLocalSource (cyclomatic 17) src/UniGetUI.PackageEngine.Managers.WinGet/WinGet.cs:301— WinGet.GetLocalSource has cyclomatic complexity 17 (threshold 15). Of this number, 11 points are the body's own statements and 6 belong to 2 function literals inside it that branch. To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
BaseNuGet.FindPackages_UnSafe (cyclomatic 17) src/UniGetUI.PackageEngine.Managers.Generic.NuGet/BaseNuGet.cs:99— BaseNuGet.FindPackages_UnSafe has cyclomatic complexity 17 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
MainWindow.RenderMenu (cyclomatic 17) src/UniGetUI.Tui/Views/MainWindow.cs:961— MainWindow.RenderMenu has cyclomatic complexity 17 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
SoftwareCatalog.Parse (cyclomatic 16) src/UniGetUI.Avalonia/Models/SoftwareCatalog.cs:156— SoftwareCatalog.Parse has cyclomatic complexity 16 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
PolicyEditorSessionViewModel.AnalyzeRawSyntaxAsync (cyclomatic 16) src/UniGetUI.Avalonia/ViewModels/Pages/SettingsPages/PolicyEditor/PolicyEditorSessionViewModel.cs:1182— PolicyEditorSessionViewModel.AnalyzeRawSyntaxAsync has cyclomatic complexity 16 (threshold 15). Of this number, 10 points are the body's own statements and 6 belong to one function literal inside it that branches. To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
PackagesPageViewModel.BuildPackageFilter (cyclomatic 16) src/UniGetUI.Avalonia/ViewModels/SoftwarePages/PackagesPageViewModel.cs:713— PackagesPageViewModel.BuildPackageFilter has cyclomatic complexity 16 (threshold 15). Of this number, 13 points are the body's own statements and 3 belong to 2 function literals inside it that branch. To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
PythonVersion.TryParse (cyclomatic 16) src/UniGetUI.Core.Tools/PythonVersion.cs:74— PythonVersion.TryParse has cyclomatic complexity 16 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
CoreTools.VersionStringToStruct (cyclomatic 16) REDACTED:697— CoreTools.VersionStringToStruct has cyclomatic complexity 16 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
WindowsConsoleHost.PrepareInteractiveIO (cyclomatic 16) src/UniGetUI.Interface.IpcApi/WindowsConsoleHost.cs:53— WindowsConsoleHost.PrepareInteractiveIO has cyclomatic complexity 16 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
NuGetV3Client.ParseNuspec (cyclomatic 16) src/UniGetUI.PackageEngine.Managers.Generic.NuGet/Internal/NuGetV3Client.cs:635— NuGetV3Client.ParseNuspec has cyclomatic complexity 16 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
MainWindow.RunStartupTasksAsync (cyclomatic 16) src/UniGetUI.Tui/Views/MainWindow.cs:224— MainWindow.RunStartupTasksAsync has cyclomatic complexity 16 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
MainWindow.HandleGlobalShortcut (cyclomatic 16) src/UniGetUI.Tui/Views/MainWindow.cs:564— MainWindow.HandleGlobalShortcut has cyclomatic complexity 16 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D17 · Explicit Debt· BarePragmaDisable repeated 11 times in 4 files · ×1
BarePragmaDisable repeated 11 times in 4 files src/ExternalLibraries.FilePickers/Classes/Helper.cs:46— The identical BarePragmaDisable (`#pragma warning disable CA1416`) appears 11 times in 4 files — one decision applied repeatedly (e.g. the same rule silenced on every overload of a fluent API), not 11 independent debts. Decide it once — at the type or project level, or by fixing the underlying pattern — rather than occurrence-by-occurrence. (Every occurrence still counts toward the score and metrics.)
MainWindow.OnWindowsWndProc (cognitive 91) src/UniGetUI.Avalonia/Views/MainWindow.axaml.cs:1451— MainWindow.OnWindowsWndProc has cognitive complexity 91 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
CargoBinaryResolver.ResolveAsync (cognitive 74) src/UniGetUI.PackageEngine.Managers.Cargo/CargoBinaryResolver.cs:36— CargoBinaryResolver.ResolveAsync has cognitive complexity 74 (threshold 15). Of this number, 73 points are the body's own statements and 1 belongs to one function literal inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
PolicyEditorSessionViewModel.SaveCoreAsync (cognitive 59) src/UniGetUI.Avalonia/ViewModels/Pages/SettingsPages/PolicyEditor/PolicyEditorSessionViewModel.cs:509— PolicyEditorSessionViewModel.SaveCoreAsync has cognitive complexity 59 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
AbstractPackageLoader.ReloadPackages (cognitive 51) src/UniGetUI.PackageEngine.PackageLoader/AbstractPackageLoader.cs:159— AbstractPackageLoader.ReloadPackages has cognitive complexity 51 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
PacmanPkgDetailsHelper.GetDetails_UnSafe (cognitive 50) src/UniGetUI.PackageEngine.Managers.Pacman/Helpers/PacmanPkgDetailsHelper.cs:15— PacmanPkgDetailsHelper.GetDetails_UnSafe has cognitive complexity 50 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
AbstractOperation._runOperation (cognitive 47) src/UniGetUI.PackageEngine.Operations/AbstractOperation.cs:471— AbstractOperation._runOperation has cognitive complexity 47 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
AbstractOperation.MainThreadCore (cognitive 44) src/UniGetUI.PackageEngine.Operations/AbstractOperation.cs:257— AbstractOperation.MainThreadCore has cognitive complexity 44 (threshold 15). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
CargoInstallTracker.InstallAsync (cognitive 43) src/UniGetUI.PackageEngine.Managers.Cargo/CargoInstallTracker.cs:85— CargoInstallTracker.InstallAsync has cognitive complexity 43 (threshold 15). Of this number, 39 points are the body's own statements and 4 belong to 2 function literals inside it that branch. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
ScoopPkgDetailsHelper.GetDetails_UnSafe (cognitive 43) src/UniGetUI.PackageEngine.Managers.Scoop/Helpers/ScoopPkgDetailsHelper.cs:17— ScoopPkgDetailsHelper.GetDetails_UnSafe has cognitive complexity 43 (threshold 15). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
PowerShellPkgOperationHelper._getOperationParameters (cognitive 42) src/UniGetUI.PackageEngine.Managers.PowerShell/Helpers/PowerShellPkgOperationHelper.cs:21— PowerShellPkgOperationHelper._getOperationParameters has cognitive complexity 42 (threshold 15). Of this number, 41 points are the body's own statements and 1 belongs to one function literal inside it that branches. To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
CargoInstallTracker.Recover (cognitive 41) src/UniGetUI.PackageEngine.Managers.Cargo/CargoInstallTracker.cs:242— CargoInstallTracker.Recover has cognitive complexity 41 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
AbstractProcessOperation.PerformOperation (cognitive 39) src/UniGetUI.PackageEngine.Operations/AbstractProcessOperation.cs:96— AbstractProcessOperation.PerformOperation has cognitive complexity 39 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
TuiCommandLine.Parse (cognitive 39) src/UniGetUI.Tui/Infrastructure/TuiCommandLine.cs:71— TuiCommandLine.Parse has cognitive complexity 39 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
AptPkgDetailsHelper.GetDetails_UnSafe (cognitive 37) src/UniGetUI.PackageEngine.Managers.Apt/Helpers/AptPkgDetailsHelper.cs:15— AptPkgDetailsHelper.GetDetails_UnSafe has cognitive complexity 37 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
CargoArchive.Read (cognitive 36) src/UniGetUI.PackageEngine.Managers.Cargo/CargoArchive.cs:18— CargoArchive.Read has cognitive complexity 36 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
InstallOptionsDialog.Build (cognitive 36) src/UniGetUI.Tui/Views/Dialogs/InstallOptionsDialog.cs:128— InstallOptionsDialog.Build has cognitive complexity 36 (threshold 15). Most of this is not in the body itself: 14 of the 36 points are its own statements and the rest belongs to 16 function literals inside it that branch (lines 204, 155, 164, …). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
PolicyJsonEditor.TryFindProperty (cognitive 35) src/UniGetUI.Avalonia/Views/Controls/PolicyJsonEditor.cs:106— PolicyJsonEditor.TryFindProperty has cognitive complexity 35 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
BaseNuGet.FindPackages_UnSafe (cognitive 35) src/UniGetUI.PackageEngine.Managers.Generic.NuGet/BaseNuGet.cs:99— BaseNuGet.FindPackages_UnSafe has cognitive complexity 35 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
ManageShortcutsViewModel.SaveChanges (cognitive 34) src/UniGetUI.Avalonia/ViewModels/DialogPages/ManageShortcutsViewModel.cs:275— ManageShortcutsViewModel.SaveChanges has cognitive complexity 34 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
SnapPkgDetailsHelper.GetDetails_UnSafe (cognitive 34) src/UniGetUI.PackageEngine.Managers.Snap/Helpers/SnapPkgDetailsHelper.cs:15— SnapPkgDetailsHelper.GetDetails_UnSafe has cognitive complexity 34 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
BoundedNamedPipeBrokerTransport.ReadResponseAsync (cognitive 33) src/UniGetUI.PackageEngine.AgentBroker/PolicyWriteElevation/Shared/BoundedNamedPipeBrokerTransport.cs:124— BoundedNamedPipeBrokerTransport.ReadResponseAsync has cognitive complexity 33 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
SoftwareCatalogViewModel.UpdateStates (cognitive 31) src/UniGetUI.Avalonia/ViewModels/SoftwarePages/SoftwareCatalogViewModel.cs:489— SoftwareCatalogViewModel.UpdateStates has cognitive complexity 31 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
CoreData.GetNewDataDirectoryOrMoveOld (cognitive 31) src/UniGetUI.Core.Data/CoreData.cs:422— CoreData.GetNewDataDirectoryOrMoveOld has cognitive complexity 31 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
InstalledPackagesLoader.ReloadPackagesSilently (cognitive 31) src/UniGetUI.PackageEngine.PackageLoader/InstalledPackagesLoader.cs:51— InstalledPackagesLoader.ReloadPackagesSilently has cognitive complexity 31 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
Pip.ResolveLatestCompatibleVersion (cognitive 31) src/UniGetUI.PackageEngine.Managers.Pip/Pip.cs:611— Pip.ResolveLatestCompatibleVersion has cognitive complexity 31 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
WinGetPkgOperationHelper._getOperationResult (cognitive 31) src/UniGetUI.PackageEngine.Managers.WinGet/Helpers/WinGetPkgOperationHelper.cs:331— WinGetPkgOperationHelper._getOperationResult has cognitive complexity 31 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
StartMenuShortcutsDatabase.HandleNewShortcuts (cognitive 30) src/UniGetUI.PackageEngine.PackageManagerClasses/Packages/Classes/StartMenuShortcutsDatabase.cs:611— StartMenuShortcutsDatabase.HandleNewShortcuts has cognitive complexity 30 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
WinGetPkgOperationHelper._getOperationParameters (cognitive 30) src/UniGetUI.PackageEngine.Managers.WinGet/Helpers/WinGetPkgOperationHelper.cs:115— WinGetPkgOperationHelper._getOperationParameters has cognitive complexity 30 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
BaseNuGetDetailsHelper.GetDetails_UnSafe (cognitive 30) src/UniGetUI.PackageEngine.Managers.Generic.NuGet/BaseNuGetDetailsHelper.cs:20— BaseNuGetDetailsHelper.GetDetails_UnSafe has cognitive complexity 30 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
WindowsPeerAuthenticator.Authenticate (cognitive 29) src/UniGetUI.PackageEngine.AgentBroker/PolicyWriteElevation/Interop/WindowsPeerAuthenticator.cs:72— WindowsPeerAuthenticator.Authenticate has cognitive complexity 29 (threshold 15). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition.
MainWindow.SetupTitleBar (cognitive 28) src/UniGetUI.Avalonia/Views/MainWindow.axaml.cs:614— MainWindow.SetupTitleBar has cognitive complexity 28 (threshold 15). Of this number, 26 points are the body's own statements and 2 belong to one function literal inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
PackageManagerPage.BuildPage (cognitive 28) src/UniGetUI.Avalonia/Views/Pages/SettingsPages/PackageManagerPage.axaml.cs:56— PackageManagerPage.BuildPage has cognitive complexity 28 (threshold 15). Of this number, 14 points are the body's own statements and 14 belong to 6 function literals inside it that branch. To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
BrokerRequestValidator.Validate (cognitive 28) src/UniGetUI.PackageEngine.AgentBroker/BrokerRequestValidator.cs:50— BrokerRequestValidator.Validate has cognitive complexity 28 (threshold 15). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
ProcessTaskLogger.AsColoredString (cognitive 28) src/UniGetUI.PackageEngine.PackageManagerClasses/Manager/Classes/ManagerLogger.cs:224— ProcessTaskLogger.AsColoredString has cognitive complexity 28 (threshold 15). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
PipPkgDetailsHelper.GetDetails_UnSafe (cognitive 27) src/UniGetUI.PackageEngine.Managers.Pip/Helpers/PipPkgDetailsHelper.cs:18— PipPkgDetailsHelper.GetDetails_UnSafe has cognitive complexity 27 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
NuGetV3Client.ParseNuspec (cognitive 27) src/UniGetUI.PackageEngine.Managers.Generic.NuGet/Internal/NuGetV3Client.cs:635— NuGetV3Client.ParseNuspec has cognitive complexity 27 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
UserAvatarViewModel.RefreshAsync (cognitive 26) src/UniGetUI.Avalonia/ViewModels/Controls/UserAvatarViewModel.cs:67— UserAvatarViewModel.RefreshAsync has cognitive complexity 26 (threshold 15). Of this number, 25 points are the body's own statements and 1 belongs to one function literal inside it that branches. To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
DownloadOperation.PerformOperation (cognitive 26) src/UniGetUI.PackageEngine.Operations/DownloadOperation.cs:114— DownloadOperation.PerformOperation has cognitive complexity 26 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
TuiFormField.Render (cognitive 26) src/UniGetUI.Tui/Views/Controls/TuiFormField.cs:92— TuiFormField.Render has cognitive complexity 26 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
MainWindow.Window_KeyDown (cognitive 25) src/UniGetUI.Avalonia/Views/MainWindow.axaml.cs:338— MainWindow.Window_KeyDown has cognitive complexity 25 (threshold 15). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
AvaloniaAutoUpdater.CheckAndInstallUpdatesCoreAsync (cognitive 25) src/UniGetUI.Avalonia/Infrastructure/AvaloniaAutoUpdater.cs:459— AvaloniaAutoUpdater.CheckAndInstallUpdatesCoreAsync has cognitive complexity 25 (threshold 15). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
IpcClient.BuildPackageQueryParameters (cognitive 25) src/UniGetUI.Interface.IpcApi/IpcClient.cs:1322— IpcClient.BuildPackageQueryParameters has cognitive complexity 25 (threshold 15). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition.
MainWindow.RenderMenu (cognitive 25) src/UniGetUI.Tui/Views/MainWindow.cs:961— MainWindow.RenderMenu has cognitive complexity 25 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
AbstractPackagesPage.AbstractPackagesPage.ctor (cognitive 24) src/UniGetUI.Avalonia/Views/SoftwarePages/AbstractPackagesPage.axaml.cs:47— AbstractPackagesPage.AbstractPackagesPage.ctor has cognitive complexity 24 (threshold 15). Most of this is not in the body itself: 6 of the 24 points are its own statements and the rest belongs to 6 function literals inside it that branch (lines 160, 113, 75, …). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
CargoInstallTracker.GetBuildArgumentsAsync (cognitive 24) src/UniGetUI.PackageEngine.Managers.Cargo/CargoInstallTracker.cs:19— CargoInstallTracker.GetBuildArgumentsAsync has cognitive complexity 24 (threshold 15). Of this number, 21 points are the body's own statements and 3 belong to one function literal inside it that branches. To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition.
NativeWinGetHelper.FindPackages_UnSafe (cognitive 24) src/UniGetUI.PackageEngine.Managers.WinGet/ClientHelpers/NativeWinGetHelper.cs:182— NativeWinGetHelper.FindPackages_UnSafe has cognitive complexity 24 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
WinGetCliHelper.ParseAvailableUpdates (cognitive 24) src/UniGetUI.PackageEngine.Managers.WinGet/ClientHelpers/WinGetCliHelper.cs:98— WinGetCliHelper.ParseAvailableUpdates has cognitive complexity 24 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
BaseNuGet.GetAvailableUpdates_UnSafe (cognitive 24) src/UniGetUI.PackageEngine.Managers.Generic.NuGet/BaseNuGet.cs:435— BaseNuGet.GetAvailableUpdates_UnSafe has cognitive complexity 24 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
CrashHandler.ReportFatalException (cognitive 23) src/UniGetUI.Avalonia/CrashHandler.cs:142— CrashHandler.ReportFatalException has cognitive complexity 23 (threshold 15). Of this number, 20 points are the body's own statements and 3 belong to one function item inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
UpdaterDownloadEngine.DownloadInstallerPartAsync (cognitive 23) src/UniGetUI.Core.Tools/UpdaterDownloadEngine.cs:102— UpdaterDownloadEngine.DownloadInstallerPartAsync has cognitive complexity 23 (threshold 15). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition.
IpcCliSyntax.Parse (cognitive 23) src/UniGetUI.Interface.IpcApi/IpcCliSyntax.cs:27— IpcCliSyntax.Parse has cognitive complexity 23 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
BrokerRequestValidator.FindUnsupportedOptions (cognitive 23) src/UniGetUI.PackageEngine.AgentBroker/BrokerRequestValidator.cs:192— BrokerRequestValidator.FindUnsupportedOptions has cognitive complexity 23 (threshold 15). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition.
ArpRegistryHelper.BuildIndex (cognitive 23) src/UniGetUI.PackageEngine.PackageManagerClasses/Manager/Helpers/ArpRegistryHelper.cs:111— ArpRegistryHelper.BuildIndex has cognitive complexity 23 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
Cargo.GetPackages (cognitive 23) src/UniGetUI.PackageEngine.Managers.Cargo/Cargo.cs:224— Cargo.GetPackages has cognitive complexity 23 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
CargoManagedInstaller.TryPerformAsync (cognitive 23) REDACTED:18— CargoManagedInstaller.TryPerformAsync has cognitive complexity 23 (threshold 15). Of this number, 20 points are the body's own statements and 3 belong to 2 function literals inside it that branch. To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
CargoPkgOperationHelper._getOperationParameters (cognitive 23) src/UniGetUI.PackageEngine.Managers.Cargo/Helpers/CargoPkgOperationHelper.cs:18— CargoPkgOperationHelper._getOperationParameters has cognitive complexity 23 (threshold 15). Of this number, 22 points are the body's own statements and 1 belongs to one function literal inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
TuiMaintenanceScheduler.Evaluate (cognitive 23) src/UniGetUI.Tui/Infrastructure/TuiMaintenance.cs:143— TuiMaintenanceScheduler.Evaluate has cognitive complexity 23 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
OperationViewModel.RebuildMenu (cognitive 22) src/UniGetUI.Avalonia/ViewModels/DialogPages/OperationViewModel.cs:242— OperationViewModel.RebuildMenu has cognitive complexity 22 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
AgentPolicyInspectorViewModel.ApplyManagementSnapshot (cognitive 22) src/UniGetUI.Avalonia/ViewModels/Pages/SettingsPages/AgentPolicyInspectorViewModel.cs:669— AgentPolicyInspectorViewModel.ApplyManagementSnapshot has cognitive complexity 22 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
SmoothScrollManager.TryAttachOverpanTransform (cognitive 22) src/UniGetUI.Avalonia/Views/Controls/SmoothScrollManager.cs:510— SmoothScrollManager.TryAttachOverpanTransform has cognitive complexity 22 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
UpdaterAttemptCoordinator.RunOrJoinAsync (cognitive 22) src/Shared/AutoUpdater.Helpers.cs:576— UpdaterAttemptCoordinator.RunOrJoinAsync has cognitive complexity 22 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
CoreTools.VersionStringToStruct (cognitive 22) REDACTED:697— CoreTools.VersionStringToStruct has cognitive complexity 22 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
CargoHttp.GetAsync (cognitive 22) src/UniGetUI.PackageEngine.Managers.Cargo/CargoHttp.cs:48— CargoHttp.GetAsync has cognitive complexity 22 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
PolicyEditorDocumentUi.CommitPendingLocalValidity (cognitive 21) src/UniGetUI.Avalonia/ViewModels/Pages/SettingsPages/PolicyEditor/PolicyEditorStructuredUi.cs:521— PolicyEditorDocumentUi.CommitPendingLocalValidity has cognitive complexity 21 (threshold 15). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
MaintenanceScheduler.Evaluate (cognitive 21) src/UniGetUI.Avalonia/Infrastructure/MaintenanceScheduler.cs:207— MaintenanceScheduler.Evaluate has cognitive complexity 21 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
DWMThreadHelper.ChangeState (cognitive 21) src/UniGetUI.Core.Tools/DWMThreadHelper.cs:137— DWMThreadHelper.ChangeState has cognitive complexity 21 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
PythonVersion.CompareLocal (cognitive 21) src/UniGetUI.Core.Tools/PythonVersion.cs:248— PythonVersion.CompareLocal has cognitive complexity 21 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
NativeTaskLogger.AsColoredString (cognitive 21) src/UniGetUI.PackageEngine.PackageManagerClasses/Manager/Classes/ManagerLogger.cs:398— NativeTaskLogger.AsColoredString has cognitive complexity 21 (threshold 15). To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
InstallOptionsFactory.EnsureSecureOptions (cognitive 21) src/UniGetUI.PackageEngine.PackageManagerClasses/Packages/Classes/InstallOptionsFactory.cs:327— InstallOptionsFactory.EnsureSecureOptions has cognitive complexity 21 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
WinGetPkgOperationHelper.TryGetPortableInstallLocation (cognitive 21) src/UniGetUI.PackageEngine.Managers.WinGet/Helpers/WinGetPkgOperationHelper.cs:659— WinGetPkgOperationHelper.TryGetPortableInstallLocation has cognitive complexity 21 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
BaseNuGet.GetAvailableUpdatesLocal (cognitive 21) src/UniGetUI.PackageEngine.Managers.Generic.NuGet/BaseNuGet.cs:308— BaseNuGet.GetAvailableUpdatesLocal has cognitive complexity 21 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
AbstractPackagesPage.UpdateFilterPaneColumn (cognitive 20) src/UniGetUI.Avalonia/Views/SoftwarePages/AbstractPackagesPage.axaml.cs:556— AbstractPackagesPage.UpdateFilterPaneColumn has cognitive complexity 20 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
LanguageData.LoadLanguageTranslatorList (cognitive 20) src/UniGetUI.Core.LanguageEngine/LanguageData.cs:110— LanguageData.LoadLanguageTranslatorList has cognitive complexity 20 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
CoreTools.CacheUACForCurrentProcess (cognitive 20) REDACTED:922— CoreTools.CacheUACForCurrentProcess has cognitive complexity 20 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
IpcClient.GetRequestTimeout (cognitive 20) src/UniGetUI.Interface.IpcApi/IpcClient.cs:1466— IpcClient.GetRequestTimeout has cognitive complexity 20 (threshold 15). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition.
PackageOperation.PerformBrokerOperation (cognitive 20) src/UniGetUI.PackageEngine.Operations/PackageOperations.cs:451— PackageOperation.PerformBrokerOperation has cognitive complexity 20 (threshold 15). To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
FakePackageManagerProcess.RunPackageVerb (cognitive 20) src/UniGetUI.Tui/FakeData/FakePackageManagerProcess.cs:100— FakePackageManagerProcess.RunPackageVerb has cognitive complexity 20 (threshold 15). Of this number, 17 points are the body's own statements and 3 belong to 3 function literals inside it that branch. To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
UpgradablePackagesLoader.IsPackageValid (cognitive 19) src/UniGetUI.PackageEngine.PackageLoader/UpgradablePackagesLoader.cs:32— UpgradablePackagesLoader.IsPackageValid has cognitive complexity 19 (threshold 15). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
ArpRegistryHelper.ReadLocation (cognitive 19) src/UniGetUI.PackageEngine.PackageManagerClasses/Manager/Helpers/ArpRegistryHelper.cs:162— ArpRegistryHelper.ReadLocation has cognitive complexity 19 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
NuGetV3Client.Search (cognitive 19) src/UniGetUI.PackageEngine.Managers.Generic.NuGet/Internal/NuGetV3Client.cs:73— NuGetV3Client.Search has cognitive complexity 19 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
InstallOptionsViewModel.InstallOptionsViewModel.ctor (cognitive 18) src/UniGetUI.Avalonia/ViewModels/DialogPages/InstallOptionsViewModel.cs:268— InstallOptionsViewModel.InstallOptionsViewModel.ctor has cognitive complexity 18 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
ManagerLogsPageViewModel.LoadForManager (cognitive 18) src/UniGetUI.Avalonia/ViewModels/Pages/LogPages/ManagerLogsPageViewModel.cs:25— ManagerLogsPageViewModel.LoadForManager has cognitive complexity 18 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
PolicyEditorDialogViewModel.OnSessionPropertyChanged (cognitive 18) src/UniGetUI.Avalonia/ViewModels/Pages/SettingsPages/PolicyEditor/PolicyEditorDialogViewModel.cs:139— PolicyEditorDialogViewModel.OnSessionPropertyChanged has cognitive complexity 18 (threshold 15). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition.
PolicyFindingPresentation.DescribeLocation (cognitive 18) src/UniGetUI.Avalonia/ViewModels/Pages/SettingsPages/PolicyEditor/PolicyValidationFinding.cs:211— PolicyFindingPresentation.DescribeLocation has cognitive complexity 18 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
PackagesPageViewModel.GetSelectedSourceFilters (cognitive 18) src/UniGetUI.Avalonia/ViewModels/SoftwarePages/PackagesPageViewModel.cs:973— PackagesPageViewModel.GetSelectedSourceFilters has cognitive complexity 18 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
SvgIcon.ParseSvg (cognitive 18) src/UniGetUI.Avalonia/Views/Controls/SvgIcon.cs:114— SvgIcon.ParseSvg has cognitive complexity 18 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
SerializationHelpers.ConvertXmlNode (cognitive 18) REDACTED:45— SerializationHelpers.ConvertXmlNode has cognitive complexity 18 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
WindowsConsoleHost.PrepareInteractiveIO (cognitive 18) src/UniGetUI.Interface.IpcApi/WindowsConsoleHost.cs:53— WindowsConsoleHost.PrepareInteractiveIO has cognitive complexity 18 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
WindowsPolicyWriteElevator.ExchangeAsync (cognitive 18) src/UniGetUI.PackageEngine.AgentBroker/PolicyWriteElevation/WindowsPolicyWriteElevator.cs:302— WindowsPolicyWriteElevator.ExchangeAsync has cognitive complexity 18 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
BasePkgOperationHelper.BuildParameters (cognitive 18) src/UniGetUI.PackageEngine.PackageManagerClasses/Manager/Helpers/BasePkgOperationHelper.cs:51— BasePkgOperationHelper.BuildParameters has cognitive complexity 18 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
Scoop.ParseInstalledPackages (cognitive 18) src/UniGetUI.PackageEngine.Managers.Scoop/Scoop.cs:313— Scoop.ParseInstalledPackages has cognitive complexity 18 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
TuiCloudBackup.PollAccessTokenAsync (cognitive 18) src/UniGetUI.Tui/Infrastructure/TuiCloudBackup.cs:75— TuiCloudBackup.PollAccessTokenAsync has cognitive complexity 18 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
MainWindow.OnWindowKeyDown (cognitive 18) src/UniGetUI.Tui/Views/MainWindow.cs:477— MainWindow.OnWindowKeyDown has cognitive complexity 18 (threshold 15). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition.
MainWindowViewModel.MainWindowViewModel.ctor (cognitive 17) src/UniGetUI.Avalonia/ViewModels/MainWindowViewModel.cs:426— MainWindowViewModel.MainWindowViewModel.ctor has cognitive complexity 17 (threshold 15). Of this number, 12 points are the body's own statements and 5 belong to 2 function literals inside it that branch. To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
SoftwareCatalogViewModel.RefreshAsync (cognitive 17) src/UniGetUI.Avalonia/ViewModels/SoftwarePages/SoftwareCatalogViewModel.cs:325— SoftwareCatalogViewModel.RefreshAsync has cognitive complexity 17 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
SmoothScrollManager.RouteInput (cognitive 17) src/UniGetUI.Avalonia/Views/Controls/SmoothScrollManager.cs:108— SmoothScrollManager.RouteInput has cognitive complexity 17 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
MainWindow.IsRectangleFullyVisible (cognitive 17) src/UniGetUI.Avalonia/Views/MainWindow.axaml.cs:1161— MainWindow.IsRectangleFullyVisible has cognitive complexity 17 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
PackageBundlesPage.CreateBatchScriptAsync (cognitive 17) src/UniGetUI.Avalonia/Views/SoftwarePages/PackageBundlesPage.cs:530— PackageBundlesPage.CreateBatchScriptAsync has cognitive complexity 17 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
AvaloniaBootstrapper.GetMissingDependenciesAsync (cognitive 17) src/UniGetUI.Avalonia/Infrastructure/AvaloniaBootstrapper.cs:378— AvaloniaBootstrapper.GetMissingDependenciesAsync has cognitive complexity 17 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
PolicyElevationLaunchArguments.TryParse (cognitive 17) src/UniGetUI.PackageEngine.AgentBroker/PolicyWriteElevation/Protocol/PolicyElevationArguments.cs:44— PolicyElevationLaunchArguments.TryParse has cognitive complexity 17 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
CoreData.UniGetUIUserConfigurationDirectory.get (cognitive 17) src/UniGetUI.Core.Data/CoreData.cs:166— CoreData.UniGetUIUserConfigurationDirectory.get has cognitive complexity 17 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
PackageOperation._getPostInstallOps (cognitive 17) src/UniGetUI.PackageEngine.Operations/PackageOperations.cs:1469— PackageOperation._getPostInstallOps has cognitive complexity 17 (threshold 15). Of this number, 14 points are the body's own statements and 3 belong to 2 function items inside it that branch. To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
DesktopShortcutsDatabase.HandleNewShortcuts (cognitive 17) src/UniGetUI.PackageEngine.PackageManagerClasses/Packages/Classes/DesktopShortcutsDatabase.cs:202— DesktopShortcutsDatabase.HandleNewShortcuts has cognitive complexity 17 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
DnfPkgDetailsHelper.GetDetails_UnSafe (cognitive 17) src/UniGetUI.PackageEngine.Managers.Dnf/Helpers/DnfPkgDetailsHelper.cs:15— DnfPkgDetailsHelper.GetDetails_UnSafe has cognitive complexity 17 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
Scoop.ParseAvailableUpdates (cognitive 17) src/UniGetUI.PackageEngine.Managers.Scoop/Scoop.cs:238— Scoop.ParseAvailableUpdates has cognitive complexity 17 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
WinGetTableLayout.MergeContinuationColumns (cognitive 17) src/UniGetUI.PackageEngine.Managers.WinGet/ClientHelpers/WinGetTableLayout.cs:207— WinGetTableLayout.MergeContinuationColumns has cognitive complexity 17 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
FakeOperationHelper._getOperationParameters (cognitive 17) src/UniGetUI.Tui/FakeData/FakePackageManager.cs:230— FakeOperationHelper._getOperationParameters has cognitive complexity 17 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
TuiAppHost.Run (cognitive 17) src/UniGetUI.Tui/TuiAppHost.cs:32— TuiAppHost.Run has cognitive complexity 17 (threshold 15). To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
MainWindow.HandleGlobalShortcut (cognitive 17) src/UniGetUI.Tui/Views/MainWindow.cs:564— MainWindow.HandleGlobalShortcut has cognitive complexity 17 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
SettingsPage.BuildScheduler (cognitive 17) REDACTED:412— SettingsPage.BuildScheduler has cognitive complexity 17 (threshold 15). Most of this is not in the body itself: 5 of the 17 points are its own statements and the rest belongs to 9 function literals inside it that branch (lines 428, 431, 432, …). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
SoftwareCatalog.Parse (cognitive 16) src/UniGetUI.Avalonia/Models/SoftwareCatalog.cs:156— SoftwareCatalog.Parse has cognitive complexity 16 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
InternetViewModel.BuildProxyCompatTable (cognitive 16) src/UniGetUI.Avalonia/ViewModels/Pages/SettingsPages/InternetViewModel.cs:83— InternetViewModel.BuildProxyCompatTable has cognitive complexity 16 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
SmoothScrollManager.OnFrame (cognitive 16) src/UniGetUI.Avalonia/Views/Controls/SmoothScrollManager.cs:371— SmoothScrollManager.OnFrame has cognitive complexity 16 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
MainWindow.HitTestResizeBorder (cognitive 16) src/UniGetUI.Avalonia/Views/MainWindow.axaml.cs:1267— MainWindow.HitTestResizeBorder has cognitive complexity 16 (threshold 15). To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
AbstractPackagesPage.PopulateToolbarOverflowFlyout (cognitive 16) src/UniGetUI.Avalonia/Views/SoftwarePages/AbstractPackagesPage.axaml.cs:263— AbstractPackagesPage.PopulateToolbarOverflowFlyout has cognitive complexity 16 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
PolicyElevationAccessPolicy.IsControlRestrictedToTrustedPrincipals (cognitive 16) src/UniGetUI.PackageEngine.AgentBroker/PolicyWriteElevation/Interop/PolicyElevationAccessPolicy.cs:104— PolicyElevationAccessPolicy.IsControlRestrictedToTrustedPrincipals has cognitive complexity 16 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
PackageOperation.PrepareProcessStartInfo (cognitive 16) src/UniGetUI.PackageEngine.Operations/PackageOperations.cs:247— PackageOperation.PrepareProcessStartInfo has cognitive complexity 16 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
StreamedOutputLineBuffer.Append (cognitive 16) src/UniGetUI.PackageEngine.Operations/PackageOperations.cs:1019— StreamedOutputLineBuffer.Append has cognitive complexity 16 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
PEInterface.CreateManagers (cognitive 16) src/UniGetUI.PackageEngine.PackageEngine/PEInterface.cs:85— PEInterface.CreateManagers has cognitive complexity 16 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
BasePkgDetailsHelper.GetScreenshots (cognitive 16) src/UniGetUI.PackageEngine.PackageManagerClasses/Manager/Helpers/BasePkgDetailsHelper.cs:131— BasePkgDetailsHelper.GetScreenshots has cognitive complexity 16 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
Bun.ParseBunOutdatedTable (cognitive 16) src/UniGetUI.PackageEngine.Managers.Bun/Bun.cs:377— Bun.ParseBunOutdatedTable has cognitive complexity 16 (threshold 15). Of this number, 14 points are the body's own statements and 2 belong to 2 function literals inside it that branch. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
Npm.ParseSearchOutput (cognitive 16) src/UniGetUI.PackageEngine.Managers.Npm/Npm.cs:477— Npm.ParseSearchOutput has cognitive complexity 16 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
PowerShell7PkgOperationHelper._getOperationParameters (cognitive 16) src/UniGetUI.PackageEngine.Managers.PowerShell7/Helpers/PowerShell7PkgOperationHelper.cs:15— PowerShell7PkgOperationHelper._getOperationParameters has cognitive complexity 16 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
BaseNuGetDetailsHelper.GetDetailsV3 (cognitive 16) src/UniGetUI.PackageEngine.Managers.Generic.NuGet/BaseNuGetDetailsHelper.cs:307— BaseNuGetDetailsHelper.GetDetailsV3 has cognitive complexity 16 (threshold 15). To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
MainWindow.RunStartupTasksAsync (cognitive 16) src/UniGetUI.Tui/Views/MainWindow.cs:224— MainWindow.RunStartupTasksAsync has cognitive complexity 16 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
LogsPage.BuildRows (cognitive 16) src/UniGetUI.Tui/Views/Pages/LogsPage.cs:200— LogsPage.BuildRows has cognitive complexity 16 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
ManagerSettingsDialog.AddSourceAsync (cognitive 16) src/UniGetUI.Tui/Views/Pages/ManagersPage.cs:299— ManagerSettingsDialog.AddSourceAsync has cognitive complexity 16 (threshold 15). Of this number, 11 points are the body's own statements and 5 belong to one function literal inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
Change coupling clique: InstalledPackagesPage.cs, PackageBundlesPage.cs, SoftwareUpdatesPage.cs src/UniGetUI.Avalonia/Views/SoftwarePages/InstalledPackagesPage.cs— 3 files — `src/UniGetUI.Avalonia/Views/SoftwarePages/InstalledPackagesPage.cs`, `src/UniGetUI.Avalonia/Views/SoftwarePages/PackageBundlesPage.cs`, `src/UniGetUI.Avalonia/Views/SoftwarePages/SoftwareUpdatesPage.cs` — all change together with no explicit dependency: a fully-connected co-change clique, not 3 separate couplings. They share one concern (thin parallel siblings over a common abstraction), so extract the shared part into ONE unit and the whole clique's coupling clears at once — you do not need to break each pair individually.
D4 · Code Duplication· Edited copy of a member (23 corresponding lines) · ×1
Edited copy of a member (23 corresponding lines) src/UniGetUI.PackageEngine.Managers.Apt/Apt.cs:168— src/UniGetUI.PackageEngine.Managers.Apt/Apt.cs:168-210 | src/UniGetUI.PackageEngine.Managers.Apt/Apt.cs:213-261 — These two members are one piece of code written twice and then edited apart: 23 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Members sharing a duplicated core (6 members, 50+ identical tokens) · ×1
Members sharing a duplicated core (6 members, 50+ identical tokens) src/UniGetUI.PackageEngine.Managers.Apt/Apt.cs:100— src/UniGetUI.PackageEngine.Managers.Apt/Apt.cs:100-119 | src/UniGetUI.PackageEngine.Managers.Dnf/Dnf.cs:108-127 | src/UniGetUI.PackageEngine.Managers.Flatpak/Flatpak.cs:105-124 | src/UniGetUI.PackageEngine.Managers.Homebrew/Homebrew.cs:154-162 | src/UniGetUI.PackageEngine.Managers.Pacman/Pacman.cs:101-120 | src/UniGetUI.PackageEngine.Managers.Snap/Snap.cs:104-123 — These 6 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 6 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 6 times.
Duplicated block (76 lines × 2) src/UniGetUI.PackageEngine.Interfaces/IPackageDetails.cs:19— src/UniGetUI.PackageEngine.Interfaces/IPackageDetails.cs:19-94 | src/UniGetUI.PackageEngine.PackageManagerClasses/Packages/Classes/PackageDetails.cs:30-105 — before extracting anything, compare `src/UniGetUI.PackageEngine.Interfaces/IPackageDetails.cs` and `src/UniGetUI.PackageEngine.PackageManagerClasses/Packages/Classes/PackageDetails.cs` as WHOLE FILES: 82% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 1 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (52–75 lines × 2) src/UniGetUI.PackageEngine.Managers.Bun/Helpers/BunPkgDetailsHelper.cs:61— src/UniGetUI.PackageEngine.Managers.Bun/Helpers/BunPkgDetailsHelper.cs:61-112 | src/UniGetUI.PackageEngine.Managers.Npm/Helpers/NpmPkgDetailsHelper.cs:79-153 — before extracting anything, compare `src/UniGetUI.PackageEngine.Managers.Bun/Helpers/BunPkgDetailsHelper.cs` and `src/UniGetUI.PackageEngine.Managers.Npm/Helpers/NpmPkgDetailsHelper.cs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 106 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/UniGetUI.PackageEngine.Managers.Npm/Helpers/NpmPkgDetailsHelper.cs:79` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (23–41 lines × 3) src/UniGetUI.PackageEngine.Managers.Chocolatey/Helpers/ChocolateySourceHelper.cs:55— src/UniGetUI.PackageEngine.Managers.Chocolatey/Helpers/ChocolateySourceHelper.cs:55-94 | src/UniGetUI.PackageEngine.Managers.PowerShell/Helpers/PowerShellSourceHelper.cs:57-97 | src/UniGetUI.PackageEngine.Managers.PowerShell7/Helpers/PowerShell7SourceHelper.cs:79-101 — before extracting anything, compare `src/UniGetUI.PackageEngine.Managers.PowerShell/Helpers/PowerShellSourceHelper.cs` and `src/UniGetUI.PackageEngine.Managers.PowerShell7/Helpers/PowerShell7SourceHelper.cs` as WHOLE FILES: 92% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 2 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/UniGetUI.PackageEngine.Managers.PowerShell7/Helpers/PowerShell7SourceHelper.cs:79` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (38–41 lines × 2) src/UniGetUI.PackageEngine.Managers.PowerShell/PowerShell.cs:88— src/UniGetUI.PackageEngine.Managers.PowerShell/PowerShell.cs:88-125 | src/UniGetUI.PackageEngine.Managers.PowerShell7/PowerShell7.cs:89-129 — `src/UniGetUI.PackageEngine.Managers.PowerShell/PowerShell.cs` and `src/UniGetUI.PackageEngine.Managers.PowerShell7/PowerShell7.cs` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 4 separate duplicated blocks between them, totalling at least 85 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (38 lines × 2) src/UniGetUI.PackageEngine.Managers.PowerShell/Helpers/PowerShellSourceHelper.cs:101— src/UniGetUI.PackageEngine.Managers.PowerShell/Helpers/PowerShellSourceHelper.cs:101-138 | src/UniGetUI.PackageEngine.Managers.PowerShell7/Helpers/PowerShell7SourceHelper.cs:105-142 — before extracting anything, compare `src/UniGetUI.PackageEngine.Managers.PowerShell/Helpers/PowerShellSourceHelper.cs` and `src/UniGetUI.PackageEngine.Managers.PowerShell7/Helpers/PowerShell7SourceHelper.cs` as WHOLE FILES: 92% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 2 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (37 lines × 2) src/UniGetUI.Avalonia/Infrastructure/ProcessEnvironmentConfigurator.cs:63— src/UniGetUI.Avalonia/Infrastructure/ProcessEnvironmentConfigurator.cs:63-99 | src/UniGetUI.Avalonia/Views/MainWindow.axaml.cs:2355-2391 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (34 lines × 2) src/UniGetUI.PackageEngine.PackageManagerClasses/Manager/Classes/ManagerLogger.cs:288— src/UniGetUI.PackageEngine.PackageManagerClasses/Manager/Classes/ManagerLogger.cs:288-321 | src/UniGetUI.PackageEngine.PackageManagerClasses/Manager/Classes/ManagerLogger.cs:444-477 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/UniGetUI.PackageEngine.PackageManagerClasses/Manager/Classes/ManagerLogger.cs:288` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (31–33 lines × 2) src/UniGetUI.PackageEngine.Managers.Apt/Helpers/AptPkgDetailsHelper.cs:126— src/UniGetUI.PackageEngine.Managers.Apt/Helpers/AptPkgDetailsHelper.cs:126-158 | src/UniGetUI.PackageEngine.Managers.Dnf/Helpers/DnfPkgDetailsHelper.cs:109-139 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (32 lines × 2) src/UniGetUI.PackageEngine.Managers.Flatpak/Flatpak.cs:194— src/UniGetUI.PackageEngine.Managers.Flatpak/Flatpak.cs:194-225 | src/UniGetUI.PackageEngine.Managers.Snap/Snap.cs:193-224 — `src/UniGetUI.PackageEngine.Managers.Flatpak/Flatpak.cs` and `src/UniGetUI.PackageEngine.Managers.Snap/Snap.cs` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 4 separate duplicated blocks between them, totalling at least 112 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (29 lines × 2) src/UniGetUI.PackageEngine.Managers.Snap/SnapParsing.cs:14— src/UniGetUI.PackageEngine.Managers.Snap/SnapParsing.cs:14-42 | src/UniGetUI.PackageEngine.Managers.Snap/SnapParsing.cs:97-125 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (27 lines × 2) src/UniGetUI.Avalonia/Views/Pages/HelpPage.axaml.cs:19— src/UniGetUI.Avalonia/Views/Pages/HelpPage.axaml.cs:19-45 | src/UniGetUI.Avalonia/Views/Pages/ReleaseNotesPage.axaml.cs:18-44 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `src/UniGetUI.Avalonia/Views/Pages/HelpPage.axaml.cs:19` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (20–29 lines × 2) src/UniGetUI.Avalonia/Views/SoftwarePages/PackageBundlesPage.cs:553— src/UniGetUI.Avalonia/Views/SoftwarePages/PackageBundlesPage.cs:553-581 | src/UniGetUI.Tui/Infrastructure/TuiBundleService.cs:244-263 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `src/UniGetUI.Avalonia/Views/SoftwarePages/PackageBundlesPage.cs:553` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (26 lines × 2) src/UniGetUI.AgentPolicy.ElevatedHelper/AuthenticatedBrokerTransport.cs:86— src/UniGetUI.AgentPolicy.ElevatedHelper/AuthenticatedBrokerTransport.cs:86-111 | src/UniGetUI.PackageEngine.AgentBroker/PolicyWriteElevation/Shared/BoundedNamedPipeBrokerTransport.cs:68-93 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `src/UniGetUI.AgentPolicy.ElevatedHelper/AuthenticatedBrokerTransport.cs:86` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
Duplicated block (24–26 lines × 2) src/UniGetUI.PackageEngine.Managers.Dnf/Dnf.cs:182— src/UniGetUI.PackageEngine.Managers.Dnf/Dnf.cs:182-207 | src/UniGetUI.PackageEngine.Managers.Pacman/Pacman.cs:175-198 — `src/UniGetUI.PackageEngine.Managers.Dnf/Dnf.cs` and `src/UniGetUI.PackageEngine.Managers.Pacman/Pacman.cs` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 5 separate duplicated blocks between them, totalling at least 99 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own. Read the line range as the matched WINDOW rather than a finished unit: at `src/UniGetUI.PackageEngine.Managers.Dnf/Dnf.cs:182` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (11–25 lines × 3) src/UniGetUI.PackageEngine.Managers.Dnf/Dnf.cs:183— src/UniGetUI.PackageEngine.Managers.Dnf/Dnf.cs:183-207 | src/UniGetUI.PackageEngine.Managers.Homebrew/Homebrew.cs:215-225 | src/UniGetUI.PackageEngine.Managers.Pacman/Pacman.cs:176-198 — `src/UniGetUI.PackageEngine.Managers.Dnf/Dnf.cs` and `src/UniGetUI.PackageEngine.Managers.Pacman/Pacman.cs` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 5 separate duplicated blocks between them, totalling at least 99 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own. Read the line range as the matched WINDOW rather than a finished unit: at `src/UniGetUI.PackageEngine.Managers.Dnf/Dnf.cs:183` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `src/UniGetUI.PackageEngine.Managers.Homebrew/Homebrew.cs:215` calls `GetSourceOrDefault` and `src/UniGetUI.PackageEngine.Managers.Dnf/Dnf.cs:183` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (25 lines × 2) src/UniGetUI.Avalonia/ViewModels/Pages/SettingsPages/InternetViewModel.cs:134— src/UniGetUI.Avalonia/ViewModels/Pages/SettingsPages/InternetViewModel.cs:134-158 | src/UniGetUI.Avalonia/ViewModels/Pages/SettingsPages/UpdatesViewModel.cs:85-109 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `src/UniGetUI.Avalonia/ViewModels/Pages/SettingsPages/InternetViewModel.cs:134` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The `return` at the foot of the matched lines is the enclosing body's own terminal exit, not an early one: it moves with them unchanged, and each site calls the extracted unit from the position that `return` occupied — no decision has to be handed back and re-acted on.
Duplicated block (11–24 lines × 3) src/UniGetUI.Avalonia/Views/SoftwarePages/PackageBundlesPage.cs:457— src/UniGetUI.Avalonia/Views/SoftwarePages/PackageBundlesPage.cs:457-468 | src/UniGetUI.Interface.IpcApi/IpcBundleApi.cs:626-649 | src/UniGetUI.Tui/Infrastructure/TuiBundleService.cs:120-130 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 3 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 3 times. Read the line range as the matched WINDOW rather than a finished unit: at `src/UniGetUI.Avalonia/Views/SoftwarePages/PackageBundlesPage.cs:457` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
Duplicated block (23–24 lines × 2) src/UniGetUI.PackageEngine.Managers.Apt/Apt.cs:124— src/UniGetUI.PackageEngine.Managers.Apt/Apt.cs:124-146 | src/UniGetUI.PackageEngine.Managers.Pacman/Pacman.cs:125-148 — `src/UniGetUI.PackageEngine.Managers.Apt/Apt.cs` and `src/UniGetUI.PackageEngine.Managers.Pacman/Pacman.cs` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 3 separate duplicated blocks between them, totalling at least 58 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own. Read the line range as the matched WINDOW rather than a finished unit: at `src/UniGetUI.PackageEngine.Managers.Apt/Apt.cs:124` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (22–24 lines × 2) src/UniGetUI.PackageEngine.Managers.Dnf/Helpers/DnfPkgDetailsHelper.cs:16— src/UniGetUI.PackageEngine.Managers.Dnf/Helpers/DnfPkgDetailsHelper.cs:16-39 | src/UniGetUI.PackageEngine.Managers.Snap/Helpers/SnapPkgDetailsHelper.cs:16-37 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `src/UniGetUI.PackageEngine.Managers.Dnf/Helpers/DnfPkgDetailsHelper.cs:16` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (20–22 lines × 3) src/UniGetUI.PackageEngine.Managers.WinGet/ClientHelpers/NativeWinGetHelper.cs:798— src/UniGetUI.PackageEngine.Managers.WinGet/ClientHelpers/NativeWinGetHelper.cs:798-819 | src/UniGetUI.PackageEngine.Managers.WinGet/ClientHelpers/PingetCliHelper.cs:196-215 | src/UniGetUI.PackageEngine.Managers.WinGet/ClientHelpers/WinGetCliHelper.cs:432-453 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from all 3 call sites, so a change lands once. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `src/UniGetUI.PackageEngine.Managers.WinGet/ClientHelpers/NativeWinGetHelper.cs:794` calls `CreateNew` and `src/UniGetUI.PackageEngine.Managers.WinGet/ClientHelpers/PingetCliHelper.cs:195` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (21 lines × 2) src/UniGetUI.PackageEngine.Managers.Cargo/Cargo.cs:43— src/UniGetUI.PackageEngine.Managers.Cargo/Cargo.cs:43-63 | src/UniGetUI.PackageEngine.Managers.Npm/Npm.cs:329-349 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (9–20 lines × 6) src/UniGetUI.PackageEngine.Managers.Apt/Apt.cs:100— src/UniGetUI.PackageEngine.Managers.Apt/Apt.cs:100-119 | src/UniGetUI.PackageEngine.Managers.Dnf/Dnf.cs:108-127 | src/UniGetUI.PackageEngine.Managers.Flatpak/Flatpak.cs:105-124 | src/UniGetUI.PackageEngine.Managers.Homebrew/Homebrew.cs:154-162 | src/UniGetUI.PackageEngine.Managers.Pacman/Pacman.cs:101-120 | src/UniGetUI.PackageEngine.Managers.Snap/Snap.cs:104-123 — `src/UniGetUI.PackageEngine.Managers.Apt/Apt.cs` and `src/UniGetUI.PackageEngine.Managers.Dnf/Dnf.cs` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 3 separate duplicated blocks between them, totalling at least 47 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own.
Duplicated block (19 lines × 3) src/UniGetUI.Interface.IpcApi/IpcServer.cs:1972— src/UniGetUI.Interface.IpcApi/IpcServer.cs:1972-1990 | src/UniGetUI.Interface.IpcApi/IpcServer.cs:1997-2015 | src/UniGetUI.Interface.IpcApi/IpcServer.cs:2022-2040 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (18–20 lines × 2) src/UniGetUI.PackageEngine.Operations/PackageOperations.cs:1554— src/UniGetUI.PackageEngine.Operations/PackageOperations.cs:1554-1571 | src/UniGetUI.PackageEngine.Operations/PackageOperations.cs:1642-1661 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/UniGetUI.PackageEngine.Operations/PackageOperations.cs:1554` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (15–18 lines × 2) src/Shared/AutoUpdater.Helpers.cs:20— src/Shared/AutoUpdater.Helpers.cs:20-37 | src/UniGetUI.Avalonia/Infrastructure/AvaloniaAutoUpdater.cs:1667-1681 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `src/Shared/AutoUpdater.Helpers.cs:20` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (12–18 lines × 2) src/UniGetUI.PackageEngine.Managers.Bun/Helpers/BunPkgDetailsHelper.cs:46— src/UniGetUI.PackageEngine.Managers.Bun/Helpers/BunPkgDetailsHelper.cs:46-57 | src/UniGetUI.PackageEngine.Managers.Npm/Helpers/NpmPkgDetailsHelper.cs:59-76 — before extracting anything, compare `src/UniGetUI.PackageEngine.Managers.Bun/Helpers/BunPkgDetailsHelper.cs` and `src/UniGetUI.PackageEngine.Managers.Npm/Helpers/NpmPkgDetailsHelper.cs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 106 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (16 lines × 5) src/UniGetUI.Interface.IpcApi/IpcServer.cs:1616— src/UniGetUI.Interface.IpcApi/IpcServer.cs:1616-1631 | src/UniGetUI.Interface.IpcApi/IpcServer.cs:1648-1663 | src/UniGetUI.Interface.IpcApi/IpcServer.cs:1750-1765 | src/UniGetUI.Interface.IpcApi/IpcServer.cs:1825-1840 | src/UniGetUI.Interface.IpcApi/IpcServer.cs:1907-1922 — all 5 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/UniGetUI.Interface.IpcApi/IpcServer.cs:1616` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (16 lines × 3) src/UniGetUI.Interface.IpcApi/IpcServer.cs:886— src/UniGetUI.Interface.IpcApi/IpcServer.cs:886-901 | src/UniGetUI.Interface.IpcApi/IpcServer.cs:922-937 | src/UniGetUI.Interface.IpcApi/IpcServer.cs:957-972 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/UniGetUI.Interface.IpcApi/IpcServer.cs:886` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (12–17 lines × 2) src/UniGetUI.Interface.IpcApi/IpcLogsApi.cs:19— src/UniGetUI.Interface.IpcApi/IpcLogsApi.cs:19-30 | src/UniGetUI.PackageEngine.Operations/History/OperationHistoryRecord.cs:20-36 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `src/UniGetUI.Interface.IpcApi/IpcLogsApi.cs:19` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (7–14 lines × 2) src/UniGetUI.Avalonia/Infrastructure/GitHubCloudBackupService.cs:102— src/UniGetUI.Avalonia/Infrastructure/GitHubCloudBackupService.cs:102-115 | src/UniGetUI.Tui/Infrastructure/TuiCloudBackup.cs:229-235 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (13 lines × 3) src/UniGetUI.PackageEngine.Managers.Apt/Apt.cs:151— src/UniGetUI.PackageEngine.Managers.Apt/Apt.cs:151-163 | src/UniGetUI.PackageEngine.Managers.Dnf/Dnf.cs:164-177 | src/UniGetUI.PackageEngine.Managers.Pacman/Pacman.cs:158-170 — `src/UniGetUI.PackageEngine.Managers.Apt/Apt.cs` and `src/UniGetUI.PackageEngine.Managers.Dnf/Dnf.cs` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 3 separate duplicated blocks between them, totalling at least 47 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own. Read the line range as the matched WINDOW rather than a finished unit: at `src/UniGetUI.PackageEngine.Managers.Apt/Apt.cs:151` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (10–11 lines × 2) src/UniGetUI.Avalonia/ViewModels/SoftwarePages/PackagesPageViewModel.cs:591— src/UniGetUI.Avalonia/ViewModels/SoftwarePages/PackagesPageViewModel.cs:591-600 | src/UniGetUI.Avalonia/ViewModels/SoftwarePages/PackagesPageViewModel.cs:620-630 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/UniGetUI.Avalonia/ViewModels/SoftwarePages/PackagesPageViewModel.cs:591` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (7–10 lines × 2) src/UniGetUI.Avalonia/ViewModels/Pages/LogPages/UniGetUILogPageViewModel.cs:71— src/UniGetUI.Avalonia/ViewModels/Pages/LogPages/UniGetUILogPageViewModel.cs:71-80 | src/UniGetUI.Tui/Views/Pages/LogsPage.cs:265-271 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `src/UniGetUI.Avalonia/ViewModels/Pages/LogPages/UniGetUILogPageViewModel.cs:71` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (9 lines × 3) src/UniGetUI.PackageEngine.Managers.Homebrew/Homebrew.cs:218— src/UniGetUI.PackageEngine.Managers.Homebrew/Homebrew.cs:218-226 | src/UniGetUI.PackageEngine.Managers.Pacman/Pacman.cs:190-199 | src/UniGetUI.PackageEngine.Managers.Pacman/Pacman.cs:231-240 — `src/UniGetUI.PackageEngine.Managers.Homebrew/Homebrew.cs` and `src/UniGetUI.PackageEngine.Managers.Pacman/Pacman.cs` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 4 separate duplicated blocks between them, totalling at least 79 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own. Read the line range as the matched WINDOW rather than a finished unit: at `src/UniGetUI.PackageEngine.Managers.Homebrew/Homebrew.cs:218` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (7 lines × 5) src/UniGetUI.Avalonia/Infrastructure/AvaloniaPackageOperationHelper.cs:38— src/UniGetUI.Avalonia/Infrastructure/AvaloniaPackageOperationHelper.cs:38-44 | src/UniGetUI.Avalonia/Infrastructure/AvaloniaPackageOperationHelper.cs:54-60 | src/UniGetUI.Avalonia/Infrastructure/AvaloniaPackageOperationHelper.cs:73-79 | src/UniGetUI.Avalonia/Views/SoftwarePages/InstalledPackagesPage.cs:433-439 | src/UniGetUI.Avalonia/Views/SoftwarePages/SoftwareUpdatesPage.cs:404-410 — there are 5 copies across 3 file(s) — more copies than files, so at least one file holds the block twice. Extract it once into a single shared function every call site can reach and call it from all 5 sites; resolving a subset leaves the remainder to drift apart. Read the line range as the matched WINDOW rather than a finished unit: at `src/UniGetUI.Avalonia/Infrastructure/AvaloniaPackageOperationHelper.cs:38` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (7 lines × 3) src/UniGetUI.Avalonia/ViewModels/Pages/SettingsPages/InstallOptionsPanelViewModel.cs:291— src/UniGetUI.Avalonia/ViewModels/Pages/SettingsPages/InstallOptionsPanelViewModel.cs:291-297 | src/UniGetUI.Avalonia/ViewModels/Pages/SettingsPages/OperationsViewModel.cs:41-53 | src/UniGetUI.Avalonia/ViewModels/Pages/SettingsPages/PackageManagerViewModel.cs:188-194 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from all 3 call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `src/UniGetUI.Avalonia/ViewModels/Pages/SettingsPages/InstallOptionsPanelViewModel.cs:291` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Fake-async — async method never awaits src/UniGetUI.Avalonia/ViewModels/Pages/SettingsPages/SourceManagerCardViewModel.cs:109— `ConfirmAddSource` is declared `async` but never awaits anything, so it runs synchronously while pretending to be asynchronous. Drop `async` or do the real async work.
IC1 · Incompleteness & stubs· Both branches open with the same statements · ×1
Both branches open with the same statements — the condition does not decide them src/UniGetUI.Avalonia/Views/DialogPages/PackageDetailsWindow.axaml.cs:1077— The first 2 statements of the `if` and of the `else` are identical, so they run on both paths regardless of the condition. Lift them above the `if` — leaving them duplicated inside makes the branches read as though they handled this differently.
P3 · Security & performance tooling· SAST runs, but gates no merge · ×1
SAST runs, but gates no merge — `REDACTED` run(s) a static-analysis scan, but no workflow that runs one is triggered by a pull request (or a merge queue, or an unfiltered push) — the scan fires on a schedule or a manual dispatch only. A vulnerable change therefore merges clean and is reported on the next scheduled run, by which time it is on the default branch and the only remedy is a follow-up fix. Add the pull-request trigger to the workflow that runs the scan so the finding arrives before the merge rather than after it.
SC1 · Supply-chain hygiene· NuGet dependencies are not locked · ×1
NuGet dependencies are not locked — No packages.lock.json and no central package management — restores aren't reproducible or pinned (SSDF PW.4.4). Enable <RestorePackagesWithLockFile>true</RestorePackagesWithLockFile> (commit the lockfile) or adopt Directory.Packages.props. Advisory — never scored.
Blocking `File.ReadAllText` inside an `async` method src/UniGetUI.Avalonia/App.axaml.cs:296— `File.ReadAllText` blocks the thread on I/O while `File.ReadAllTextAsync` exists to wait without one — inside a method that is already `async`, await the twin.
X13 · Undrained process stream· Redirected process stream is never drained (deadlock) · ×1
Redirected process stream is never drained (deadlock) src/UniGetUI.PackageEngine.Managers.Scoop/Helpers/ScoopPkgDetailsHelper.cs:57— `RedirectStandardError` is set here, but nothing in this type ever reads `StandardError` — while `StandardOutput` is read to the end. The child blocks as soon as it fills the StandardError pipe (~4 KB, never more than 64 KB), and it can then never finish writing StandardOutput, so the read-to-end above never returns and the `WaitForExit` timeout beside it does not help: the timeout bounds the WAIT, not the read that precedes it. Drain both — read one stream on a background thread (`BeginErrorReadLine()` with an `ErrorDataReceived` handler, or a `Task` running the second `ReadToEndAsync()`) and await both before `WaitForExit()` — or stop redirecting the stream you do not consume.
X18 · Disposal-pattern correctness· Owned disposable field is never released · ×1
Owned disposable field is never released src/UniGetUI.Avalonia/Infrastructure/GHAuthApiRunner.cs:20— `GHAuthApiRunner` implements `IDisposable` — so it has told every caller it holds something worth releasing — and it constructs `_listener` itself (line 20), which makes that instance its own. But `_listener` is named in none of the methods the disposal search covered: `Dispose` (line 144) — that is `Dispose` plus every method `Dispose` calls BY NAME, so a release reached through an interface, a delegate or a base class is not followed and is worth checking before acting. On what was read, the type's disposal releases everything except the one thing it owns. A disposable the owner never disposes is held until finalization if its type has a finalizer, and forever if it does not — which for a synchronisation primitive, a timer, a stream or a handle means the resource accumulates once per instance for the life of the process. Release it in `Dispose` (`_listener?.Dispose();`), or, if it truly does not need releasing, drop `IDisposable` from the type so the claim and the behaviour agree.
X5 · Nullable reference types· Symbol treated as nullable, then dereferenced unguarded · ×1
Symbol treated as nullable, then dereferenced unguarded src/UniGetUI.PackageEngine.Managers.Pip/Helpers/PipPkgDetailsHelper.cs:38— This method contradicts itself about `info`: line 81 writes `info?.`, which says `info` can be null, but line 38 then dereferences it directly with no null test between them and no guard around it. If the `?.` is right, that dereference throws NullReferenceException on the input it was written for; if `info` truly cannot be null here, the `?.` is misleading. Settle it one way — test `info` once before the first use and handle the null case, or drop the `?.` — rather than leaving the two readings side by side.
Duplicated predicate src/UniGetUI.Avalonia/ViewModels/DialogPages/OperationViewModel.cs:307— `!pkgOp.Options.InteractiveInstallation && caps.CanRunInteractively` appears character-identically in 2 files — src/UniGetUI.Avalonia/ViewModels/DialogPages/OperationViewModel.cs, src/UniGetUI.Avalonia/Views/DialogPages/OperationFailedDialog.axaml.cs. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate src/UniGetUI.PackageEngine.AgentBroker/BrokerPolicyInspector.cs:153— `!string.IsNullOrEmpty(value) && ResponseVersionRegex().IsMatch(value)` appears character-identically in 2 files — src/UniGetUI.PackageEngine.AgentBroker/BrokerPolicyInspector.cs, src/UniGetUI.PackageEngine.AgentBroker/PolicyManagement/BrokerPolicyManagementService.cs. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate src/UniGetUI.Avalonia/ViewModels/DialogPages/OperationOutputViewModel.cs:64— `Application.Current?.TryGetResource(key, theme, out var resource) == true && resource is IBrush brush` appears character-identically in 2 files — src/UniGetUI.Avalonia/ViewModels/DialogPages/OperationOutputViewModel.cs, src/UniGetUI.Avalonia/Views/DialogPages/OperationFailedDialog.axaml.cs. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate src/UniGetUI.PackageEngine.PackageLoader/AbstractPackageLoader.cs:236— `Contains(package) || !await IsPackageValid(package)` appears character-identically in 2 files — src/UniGetUI.PackageEngine.PackageLoader/AbstractPackageLoader.cs, src/UniGetUI.PackageEngine.PackageLoader/InstalledPackagesLoader.cs. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate src/UniGetUI.PackageEngine.Managers.Chocolatey/Chocolatey.cs:425— `FALSE_PACKAGE_IDS.Contains(elements[0]) || FALSE_PACKAGE_VERSIONS.Contains(elements[1])` appears character-identically in 4 files — src/UniGetUI.PackageEngine.Managers.Chocolatey/Chocolatey.cs, src/UniGetUI.PackageEngine.Managers.Dotnet/DotNet.cs, src/UniGetUI.PackageEngine.Managers.Pip/Pip.cs, src/UniGetUI.PackageEngine.Managers.Scoop/Scoop.cs. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate src/UniGetUI.PackageEngine.Managers.Homebrew/Homebrew.cs:101— `File.Exists(path) && !candidates.Contains(path)` appears character-identically in 6 files — src/UniGetUI.PackageEngine.Managers.Apt/Apt.cs, src/UniGetUI.PackageEngine.Managers.Dnf/Dnf.cs, src/UniGetUI.PackageEngine.Managers.Flatpak/Flatpak.cs, src/UniGetUI.PackageEngine.Managers.Homebrew/Homebrew.cs. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate src/UniGetUI.Avalonia/Views/SoftwarePages/InstalledPackagesPage.cs:122— `MainWindow.Instance is not { } window || !await IgnoreUpdatesConfirmationDialog.ConfirmAsync(window, packages)` appears character-identically in 2 files — src/UniGetUI.Avalonia/Views/SoftwarePages/InstalledPackagesPage.cs, src/UniGetUI.Avalonia/Views/SoftwarePages/SoftwareUpdatesPage.cs. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate src/UniGetUI.PackageEngine.Operations/PackageOperations.cs:262— `OperatingSystem.IsLinux() || Settings.Get(Settings.K.DoCacheAdminRights) || Settings.Get(Settings.K.DoCacheAdminRightsForBatches)` appears character-identically in 2 files — src/UniGetUI.PackageEngine.Operations/PackageOperations.cs, src/UniGetUI.PackageEngine.Operations/SourceOperations.cs. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate src/UniGetUI.Avalonia/ViewModels/DialogPages/OperationViewModel.cs:303— `OperatingSystem.IsWindows() && !pkgOp.Options.RunAsAdministrator && caps.CanRunAsAdmin` appears character-identically in 2 files — src/UniGetUI.Avalonia/ViewModels/DialogPages/OperationViewModel.cs, src/UniGetUI.Avalonia/Views/DialogPages/OperationFailedDialog.axaml.cs. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate src/UniGetUI.Avalonia/Models/SoftwareCatalog.cs:107— `OperatingSystem.IsWindows() || OperatingSystem.IsMacOS()` appears character-identically in 2 files — src/UniGetUI.Avalonia/Models/SoftwareCatalog.cs, src/UniGetUI.Avalonia/ViewModels/Pages/SettingsPages/NotificationsViewModel.cs. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate src/UniGetUI.Avalonia/Infrastructure/MaintenanceScheduler.cs:230— `ScheduleEvaluator.IsTimeBased(schedule.Frequency) && !ScheduleEvaluator.IsWithinGrace(schedule, now)` appears character-identically in 2 files — src/UniGetUI.Avalonia/Infrastructure/MaintenanceScheduler.cs, src/UniGetUI.Tui/Infrastructure/TuiMaintenance.cs. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate src/UniGetUI.PackageEngine.Managers.Bun/Bun.cs:243— `SemanticVersion.TryParse(versionA, out SemanticVersion parsedA) && SemanticVersion.TryParse(versionB, out SemanticVersion parsedB)` appears character-identically in 3 files — src/UniGetUI.PackageEngine.Managers.Bun/Bun.cs, src/UniGetUI.PackageEngine.Managers.Cargo/Cargo.cs, src/UniGetUI.PackageEngine.Managers.Npm/Npm.cs. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate src/UniGetUI.Avalonia/ViewModels/DialogPages/InstallOptionsViewModel.cs:626— `Settings.Get(Settings.K.UseAgentBroker) && BrokerRequestBuilder.SupportsManager(package.Manager.Name) && !package.Source.IsVirtualManager` appears character-identically in 2 files — src/UniGetUI.Avalonia/ViewModels/DialogPages/InstallOptionsViewModel.cs, src/UniGetUI.PackageEngine.Operations/PackageOperations.cs. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate src/UniGetUI.Tui/Infrastructure/TuiSecureSettings.cs:18— `TuiEngine.IsFakeData || !OperatingSystem.IsWindows()` appears character-identically in 2 files — src/UniGetUI.Tui/Infrastructure/TuiSecureSettings.cs, src/UniGetUI.Tui/Views/Pages/ManagersPage.cs. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate src/UniGetUI.Avalonia/Infrastructure/MaintenanceScheduler.cs:64— `_pendingInstallSince is { } since && DateTime.Now - since > PendingInstallLifetime` appears character-identically in 2 files — src/UniGetUI.Avalonia/Infrastructure/MaintenanceScheduler.cs, src/UniGetUI.Tui/Infrastructure/TuiMaintenance.cs. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate src/UniGetUI.Avalonia/ViewModels/Pages/SettingsPages/PolicyEditor/PolicyValidationFinding.cs:272— `arguments is null || arguments.Count == 0` appears character-identically in 2 files — src/UniGetUI.Avalonia/ViewModels/Pages/SettingsPages/PolicyEditor/PolicyValidationFinding.cs, src/UniGetUI.PackageEngine.AgentBroker/PolicyManagement/BrokerPolicyManagementService.cs. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate src/UniGetUI.Avalonia/Infrastructure/GitHubCloudBackupService.cs:107— `backupGist is not null || !createIfMissing` appears character-identically in 2 files — src/UniGetUI.Avalonia/Infrastructure/GitHubCloudBackupService.cs, src/UniGetUI.Interface.IpcApi/IpcBackupApi.cs. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate src/UniGetUI.Core.SecureSettings/SecureSettings.cs:221— `character is '.' || char.IsWhiteSpace(character)` appears character-identically in 2 files — src/UniGetUI.Core.SecureSettings/SecureSettings.cs, REDACTED. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate src/UniGetUI.Tui/Views/Pages/LogsPage.cs:82— `e.Key == Key.C && e.KeyModifiers == KeyModifiers.Control` appears character-identically in 2 files — src/UniGetUI.Tui/Views/Pages/LogsPage.cs, src/UniGetUI.Tui/Views/Pages/OperationsPage.cs. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate src/UniGetUI.Tui/Views/Dialogs/TuiModal.cs:193— `e.Key == Key.Escape && e.KeyModifiers == KeyModifiers.None` appears character-identically in 2 files — src/UniGetUI.Tui/Views/Dialogs/TuiModal.cs, src/UniGetUI.Tui/Views/MainWindow.cs. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate src/UniGetUI.Tui/Views/Dialogs/StandardDialogs.cs:81— `e.Key is Key.Enter or Key.Return && _box.IsFocused` appears character-identically in 2 files — src/UniGetUI.Tui/Views/Dialogs/StandardDialogs.cs, REDACTED. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate src/UniGetUI.Tui/Views/Pages/HistoryPage.cs:86— `e.KeyModifiers == KeyModifiers.None && e.Key == Key.Delete` appears character-identically in 2 files — src/UniGetUI.Tui/Views/Pages/HistoryPage.cs, src/UniGetUI.Tui/Views/Pages/OperationsPage.cs. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate src/UniGetUI.Tui/Views/Pages/HistoryPage.cs:81— `e.KeyModifiers == KeyModifiers.None && e.Key is Key.Enter or Key.Return` appears character-identically in 2 files — src/UniGetUI.Tui/Views/Pages/HistoryPage.cs, src/UniGetUI.Tui/Views/Pages/OperationsPage.cs. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate src/UniGetUI.Avalonia/Views/Controls/InfoBar.axaml.cs:79— `e.Source is Visual source && source.FindAncestorOfType<Button>(includeSelf: true) is not null` appears character-identically in 3 files — src/UniGetUI.Avalonia/Views/Controls/InfoBar.axaml.cs, src/UniGetUI.Avalonia/Views/MainWindow.axaml.cs, src/UniGetUI.Avalonia/Views/Pages/LogPages/OperationHistoryPage.axaml.cs. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate src/UniGetUI.Avalonia/Infrastructure/GitHubCloudBackupService.cs:89— `f.Key.StartsWith(PackageBackupStartingKey, StringComparison.Ordinal) && f.Key.EndsWith(backupKey, StringComparison.Ordinal)` appears character-identically in 2 files — src/UniGetUI.Avalonia/Infrastructure/GitHubCloudBackupService.cs, src/UniGetUI.Tui/Infrastructure/TuiCloudBackup.cs. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Silent fallback default in catch src/UniGetUI.Avalonia/CrashHandler.cs:136— `ReadShippedLibraries` swallows every exception into `return [];` — a data error becomes a silent behavior change with no trail. Log the failure or let validation throw.
Silent fallback default in catch src/UniGetUI.Avalonia/Models/SoftwareCatalog.cs:143— `HasUsableCatalog` swallows `Exception` into `return false;` — a data error becomes a silent behavior change with no trail. Log the failure or let validation throw.
Silent fallback default in catch src/UniGetUI.Avalonia/ViewModels/DialogPages/CatalogEditorViewModel.cs:134— `IsMissing` swallows `Exception` into `return true;` — a data error becomes a silent behavior change with no trail. Log the failure or let validation throw.
Silent fallback default in catch src/UniGetUI.Avalonia/ViewModels/Pages/SettingsPages/PolicyEditor/PolicyValidationFinding.cs:286— `CopyArguments` swallows `InvalidOperationException` and sets `value = "";` — a data error becomes a silent behavior change with no trail. Log the failure or let validation throw.
Silent fallback default in catch src/UniGetUI.Avalonia/ViewModels/Pages/SettingsPages/PolicyEditor/PolicyValidationFinding.cs:517— `HasRestriction` swallows `JsonException` into `return false;` — a data error becomes a silent behavior change with no trail. Log the failure or let validation throw.
Silent fallback default in catch src/UniGetUI.Avalonia/Views/MainWindow.axaml.cs:1255— `HitTestCaptionButtons` swallows every exception into `return false;` — a data error becomes a silent behavior change with no trail. Log the failure or let validation throw.
Silent fallback default in catch src/Shared/AutoUpdater.InstallerArguments.cs:176— `ReadRecordedInstallPath` swallows every exception into `return null;` — a data error becomes a silent behavior change with no trail. Log the failure or let validation throw.
Silent fallback default in catch src/UniGetUI.Core.Data/UpdateInProgressGuard.cs:36— `IsUpdateInProgress` swallows every exception into `return false;` — a data error becomes a silent behavior change with no trail. Log the failure or let validation throw.
Silent fallback default in catch src/UniGetUI.Core.Data/UpdateInProgressGuard.cs:70— `IsProcessRunning` swallows `ArgumentException` into `return false;` — a data error becomes a silent behavior change with no trail. Log the failure or let validation throw.
Silent fallback default in catch src/UniGetUI.Core.SecureSettings/SecureSettings.cs:167— `ApplyForUser` swallows every exception into `return -1;` — a data error becomes a silent behavior change with no trail. Log the failure or let validation throw.
Silent fallback default in catch src/UniGetUI.Core.SecureSettings/SecureSettings.cs:237— `IsLink` swallows every exception into `return true;` — a data error becomes a silent behavior change with no trail. Log the failure or let validation throw.
Silent fallback default in catch src/UniGetUI.Core.Tools/ShortcutFileRemover.cs:135— `TryClearReadOnlyAttribute` swallows every exception into `return false;` — a data error becomes a silent behavior change with no trail. Log the failure or let validation throw.
Silent fallback default in catch src/UniGetUI.Core.Tools/ShortcutFileRemover.cs:560— `IsRemovableShortcutPath` swallows every exception into `return false;` — a data error becomes a silent behavior change with no trail. Log the failure or let validation throw.
Silent fallback default in catch src/UniGetUI.Core.Tools/ShortcutFileRemover.cs:627— `CrossesReparsePoint` swallows every exception into `return true;` — a data error becomes a silent behavior change with no trail. Log the failure or let validation throw.
Silent fallback default in catch REDACTED:2251— `IsExecutablePath` swallows `IOException` into `return false;` — a data error becomes a silent behavior change with no trail. Log the failure or let validation throw.
Silent fallback default in catch src/UniGetUI.Interface.IpcApi/IpcClient.cs:1591— `IsProcessRunning` swallows every exception into `return false;` — a data error becomes a silent behavior change with no trail. Log the failure or let validation throw.
Silent fallback default in catch src/UniGetUI.Interface.IpcApi/IpcManagerSettingsApi.cs:484— `GetConfiguredSources` swallows `NotImplementedException` into `return [];` — a data error becomes a silent behavior change with no trail. Log the failure or let validation throw.
Silent fallback default in catch src/UniGetUI.PackageEngine.Operations/DownloadOperation.cs:76— `ComesFromTheSourceFolder` swallows every exception into `return false;` — a data error becomes a silent behavior change with no trail. Log the failure or let validation throw.
Silent fallback default in catch src/UniGetUI.PackageEngine.Operations/DownloadOperation.cs:108— `IsSameFile` swallows every exception into `return false;` — a data error becomes a silent behavior change with no trail. Log the failure or let validation throw.
Silent fallback default in catch src/UniGetUI.PackageEngine.PackageManagerClasses/Packages/Classes/StartMenuShortcutsDatabase.cs:123— `LeavesTheStartMenu` swallows every exception into `return true;` — a data error becomes a silent behavior change with no trail. Log the failure or let validation throw.
Silent fallback default in catch src/UniGetUI.PackageEngine.PackageManagerClasses/Packages/Classes/StartMenuShortcutsDatabase.cs:136— `IsReparsePoint` swallows every exception into `return true;` — a data error becomes a silent behavior change with no trail. Log the failure or let validation throw.
Silent fallback default in catch src/UniGetUI.PackageEngine.PackageManagerClasses/Packages/Classes/StartMenuShortcutsDatabase.cs:1350— `IsUnder` swallows every exception into `return false;` — a data error becomes a silent behavior change with no trail. Log the failure or let validation throw.
Silent fallback default in catch src/UniGetUI.PackageEngine.PackageManagerClasses/Packages/Classes/StartMenuShortcutsDatabase.cs:1366— `AreSamePath` swallows every exception into `return false;` — a data error becomes a silent behavior change with no trail. Log the failure or let validation throw.
Silent fallback default in catch src/UniGetUI.PackageEngine.PackageManagerClasses/Manager/Helpers/ArpRegistryHelper.cs:213— `DirectoryOf` swallows every exception into `return null;` — a data error becomes a silent behavior change with no trail. Log the failure or let validation throw.
Silent fallback default in catch src/UniGetUI.PackageEngine.Managers.Cargo/Cargo.cs:56— `IsExecutableFile` swallows `IOException` into `return false;` — a data error becomes a silent behavior change with no trail. Log the failure or let validation throw.
Orphaned file src/UniGetUI.PackageEngine.PackageManagerClasses/Packages/Classes/IgnoredUpdatesDatabase.cs:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file src/UniGetUI.Core.LanguageEngine/LanguageData.cs:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file REDACTED:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file src/ExternalLibraries.Clipboard/WindowsClipboard.cs:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file src/UniGetUI.PackageEngine.PackageManagerClasses/Manager/Helpers/BaseSourceHelper.cs:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file src/UniGetUI.Core.Settings/SettingsEngine.cs:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file src/UniGetUI.PackageEngine.Interfaces/IPackageDetails.cs:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file src/UniGetUI.PackageEngine.Serializable/SerializablePackage.cs:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file src/UniGetUI.PackageEngine.Managers.WinGet/Helpers/WinGetSourceHelper.cs:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file src/UniGetUI.Core.SecureSettings/SecureGHTokenManager.cs:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file src/UniGetUI.PackageEngine.PackageManagerClasses/Packages/ImportedPackage.cs:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file src/WindowsPackageManager.Interop/Exceptions/WinGetConfigurationException.cs:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file src/UniGetUI.PackageEngine.Interfaces/ManagerHelpers/IPackageDetailsHelper.cs:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file src/UniGetUI.PackageEngine.Interfaces/ManagerHelpers/IMultiSourceHelper.cs:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Silent fallback default on parse failure src/UniGetUI.Avalonia/ViewModels/DialogPages/ManageShortcutsViewModel.cs:195— `LoadStartMenuRules` falls back to `(IReadOnlyList<string>)[]` when `pendingByPackage.TryGetValue(packageId, out var found)` is false, with no log or throw — a malformed value silently becomes that default. Log the input or fail validation. If that constant is the correct answer to the test rather than a stand-in for a value that could not be read, this is not a silent default: say so in a comment on the member and the row stops firing.
Silent fallback default on parse failure src/UniGetUI.Avalonia/ViewModels/Pages/LogPages/OperationHistoryRowViewModel.cs:99— `Timestamp` falls back to `DateTime.MinValue` when `DateTime.TryParse(Record.TimestampUtc, null, System.Globalization.DateTimeStyles…` is false, with no log or throw — a malformed value silently becomes that default. Log the input or fail validation. If that constant is the correct answer to the test rather than a stand-in for a value that could not be read, this is not a silent default: say so in a comment on the member and the row stops firing.
Silent fallback default on parse failure src/UniGetUI.Avalonia/ViewModels/Pages/SettingsPages/PolicyEditor/PolicyEditorRawSyntax.cs:319— `PointerFromException` falls back to `""` when `pathInMessage.Success` is false, with no log or throw — a malformed value silently becomes that default. Log the input or fail validation. If that constant is the correct answer to the test rather than a stand-in for a value that could not be read, this is not a silent default: say so in a comment on the member and the row stops firing.
Silent fallback default on parse failure src/UniGetUI.Avalonia/ViewModels/Pages/SettingsPages/PolicyEditor/PolicyEditorSessionViewModel.cs:157— `SwitchToStructuredAsync` returns `Task.CompletedTask` when `PolicyEditorRawSyntax.TryParseStrict( submitted, out PolicyEditorDraftDocument? …` is false, with no log or throw — a malformed value silently becomes that default. Log the input or fail validation. If that constant is the correct answer to the test rather than a stand-in for a value that could not be read, this is not a silent default: say so in a comment on the member and the row stops firing.
Silent fallback default on parse failure src/UniGetUI.Avalonia/ViewModels/Pages/SettingsPages/PolicyEditor/PolicyValidationFinding.cs:762— `ForPointer` falls back to `Empty` when `_byPointer.TryGetValue(pointer, out IReadOnlyList<PolicyValidationFinding>? find…` is false, with no log or throw — a malformed value silently becomes that default. Log the input or fail validation. If that constant is the correct answer to the test rather than a stand-in for a value that could not be read, this is not a silent default: say so in a comment on the member and the row stops firing.
Silent fallback default on parse failure src/UniGetUI.Avalonia/ViewModels/Pages/SettingsPages/PolicyEditor/PolicyValidationFinding.cs:765— `ForRule` falls back to `Empty` when `_byRuleId.TryGetValue(ruleId, out IReadOnlyList<PolicyValidationFinding>? findin…` is false, with no log or throw — a malformed value silently becomes that default. Log the input or fail validation. If that constant is the correct answer to the test rather than a stand-in for a value that could not be read, this is not a silent default: say so in a comment on the member and the row stops firing.
Silent fallback default on parse failure src/Shared/AutoUpdater.Helpers.cs:328— `IsDefaultDevVersion` returns `false` when `Version.TryParse(sanitized, out Version? parsed)` is false, with no log or throw — a malformed value silently becomes that default. Log the input or fail validation. If that constant is the correct answer to the test rather than a stand-in for a value that could not be read, this is not a silent default: say so in a comment on the member and the row stops firing.
Silent fallback default on parse failure src/UniGetUI.AgentPolicy.ElevatedHelper/Program.cs:38— `Main` returns `PolicyElevationProtocol.ExitInvalidArguments` when `PolicyElevationLaunchArguments.TryParse(args, out PolicyElevationLaunchArguments…` is false, with no log or throw — a malformed value silently becomes that default. Log the input or fail validation. If that constant is the correct answer to the test rather than a stand-in for a value that could not be read, this is not a silent default: say so in a comment on the member and the row stops firing.
Silent fallback default on parse failure src/UniGetUI.Core.Tools/LocalBackupManager.cs:127— `GetRetentionLimit` falls back to `0` when `int.TryParse(value, CultureInfo.InvariantCulture, out int limit) && limit > 0` is false, with no log or throw — a malformed value silently becomes that default. Log the input or fail validation. If that constant is the correct answer to the test rather than a stand-in for a value that could not be read, this is not a silent default: say so in a comment on the member and the row stops firing.
Silent fallback default on parse failure src/UniGetUI.Core.Tools/Scheduling/MaintenanceScheduleStore.cs:204— `ReadCheckIntervalSeconds` falls back to `DefaultCheckIntervalSeconds` when `int.TryParse( Settings.GetValue(Settings.K.UpdatesCheckInterval), CultureInfo.In…` is false, with no log or throw — a malformed value silently becomes that default. Log the input or fail validation. If that constant is the correct answer to the test rather than a stand-in for a value that could not be read, this is not a silent default: say so in a comment on the member and the row stops firing.
Silent fallback default on parse failure REDACTED:789— `ParseVersionSegment` falls back to `BigInteger.Zero` when `int.TryParse(digits, out int small)` is false, with no log or throw — a malformed value silently becomes that default. Log the input or fail validation. If that constant is the correct answer to the test rather than a stand-in for a value that could not be read, this is not a silent default: say so in a comment on the member and the row stops firing.
Silent fallback default on parse failure src/UniGetUI.Interface.IpcApi/IpcServer.cs:1238— `V3_GetAppLog` falls back to `4` when `int.TryParse(context.Request.Query["level"], out int parsedLevel)` is false, with no log or throw — a malformed value silently becomes that default. Log the input or fail validation. If that constant is the correct answer to the test rather than a stand-in for a value that could not be read, this is not a silent default: say so in a comment on the member and the row stops firing.
Silent fallback default on parse failure src/UniGetUI.PackageEngine.Serializable/InstallOptions.cs:115— `SkipMinorUpdatesLevel` falls back to `DefaultSkipMinorLevel` when `int.TryParse(_strVal[SKIP_MINOR_LEVEL], out int v) && v is >= 2 and <= 4` is false, with no log or throw — a malformed value silently becomes that default. Log the input or fail validation. If that constant is the correct answer to the test rather than a stand-in for a value that could not be read, this is not a silent default: say so in a comment on the member and the row stops firing.
Interpolated log message defeats structured logging src/UniGetUI.Tui/FakeData/FakePackageManager.cs:105— Logging an interpolated string (`$"..."`) collapses the event to plain text — you lose the named, queryable properties structured logging exists for. Use a message template with placeholders: `LogInformation("User {UserId} did {Action}", id, action)`. If these calls go through a logging wrapper that only accepts a pre-formatted string, give the wrapper a template+args overload that forwards to the underlying logger, then migrate call sites to it.
Interpolated log message defeats structured logging src/UniGetUI.Tui/FakeData/FakePackageManager.cs:114— Logging an interpolated string (`$"..."`) collapses the event to plain text — you lose the named, queryable properties structured logging exists for. Use a message template with placeholders: `LogInformation("User {UserId} did {Action}", id, action)`. If these calls go through a logging wrapper that only accepts a pre-formatted string, give the wrapper a template+args overload that forwards to the underlying logger, then migrate call sites to it.
Interpolated log message defeats structured logging src/UniGetUI.Tui/FakeData/FakePackageManager.cs:131— Logging an interpolated string (`$"..."`) collapses the event to plain text — you lose the named, queryable properties structured logging exists for. Use a message template with placeholders: `LogInformation("User {UserId} did {Action}", id, action)`. If these calls go through a logging wrapper that only accepts a pre-formatted string, give the wrapper a template+args overload that forwards to the underlying logger, then migrate call sites to it.
Interpolated log message defeats structured logging src/UniGetUI.Tui/FakeData/FakePackageManager.cs:148— Logging an interpolated string (`$"..."`) collapses the event to plain text — you lose the named, queryable properties structured logging exists for. Use a message template with placeholders: `LogInformation("User {UserId} did {Action}", id, action)`. If these calls go through a logging wrapper that only accepts a pre-formatted string, give the wrapper a template+args overload that forwards to the underlying logger, then migrate call sites to it.
Interpolated log message defeats structured logging src/UniGetUI.Tui/FakeData/FakePackageManager.cs:171— Logging an interpolated string (`$"..."`) collapses the event to plain text — you lose the named, queryable properties structured logging exists for. Use a message template with placeholders: `LogInformation("User {UserId} did {Action}", id, action)`. If these calls go through a logging wrapper that only accepts a pre-formatted string, give the wrapper a template+args overload that forwards to the underlying logger, then migrate call sites to it.
Hand-rolled JSON/XML parsing via regex src/UniGetUI.PackageEngine.Managers.Generic.NuGet/BaseNuGet.cs:180— A regex whose pattern encodes JSON/XML syntax is parsing a structured format by hand — malformed or differently-typed content (e.g. `"amount": "5"` as a string) silently mis-parses instead of failing validation. This project already references a real parser; use it here too.
Hand-rolled JSON/XML parsing via regex src/UniGetUI.PackageEngine.Managers.Generic.NuGet/BaseNuGet.cs:820— A regex whose pattern encodes JSON/XML syntax is parsing a structured format by hand — malformed or differently-typed content (e.g. `"amount": "5"` as a string) silently mis-parses instead of failing validation. This project already references a real parser; use it here too.
Hand-rolled JSON/XML parsing via regex src/UniGetUI.PackageEngine.Managers.Generic.NuGet/BaseNuGetDetailsHelper.cs:101— A regex whose pattern encodes JSON/XML syntax is parsing a structured format by hand — malformed or differently-typed content (e.g. `"amount": "5"` as a string) silently mis-parses instead of failing validation. This project already references a real parser; use it here too.
Hand-rolled JSON/XML parsing via regex src/UniGetUI.PackageEngine.Managers.Generic.NuGet/BaseNuGetDetailsHelper.cs:125— A regex whose pattern encodes JSON/XML syntax is parsing a structured format by hand — malformed or differently-typed content (e.g. `"amount": "5"` as a string) silently mis-parses instead of failing validation. This project already references a real parser; use it here too.
Fat interface: IPackage (38 members) src/UniGetUI.PackageEngine.Interfaces/IPackage.cs:10— `IPackage` declares 38 members: `Details`, `Tag`, `IsChecked`, `Name`, `Id`, `VersionString`, `HasConcreteVersion`, `InstalledVersionIsUnverified`, `NormalizedVersion`, `NormalizedNewVersion`, `Source`, `Manager`, `NewVersionString`, `IsUpgradable`, `OverridenOptions`, `AutomationName`, `GetHash`, `GetVersionedHash`, `Equals`, `IsEquivalentTo`, `GetIconId`, `GetIconUrl`, `GetIconUrlIfAny`, `GetScreenshots`, `AddToIgnoredUpdatesAsync`, `RemoveFromIgnoredUpdatesAsync`, `HasUpdatesIgnoredAsync`, `GetIgnoredUpdatesVersionAsync`, `GetInstalledPackages`, `GetAvailablePackage`, `GetUpgradablePackage`, `SetTag`, `NewerVersionIsInstalled`, `GetInstallerFileName`, `IsUpdateMinor`, `GetInstallOptions`, `AsSerializableAsync`, `AsSerializable_Incompatible`. 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.
Fat interface: IPackageDetails (20 members) src/UniGetUI.PackageEngine.Interfaces/IPackageDetails.cs:3— `IPackageDetails` declares 20 members: `Package`, `IsPopulated`, `Description`, `Publisher`, `Author`, `HomepageUrl`, `License`, `LicenseUrl`, `Version`, `InstallerUrl`, `InstallerHash`, `InstallerType`, `InstallerSize`, `ManifestUrl`, `UpdateDate`, `ReleaseNotes`, `ReleaseNotesUrl`, `Tags`, `Load`, `Dependencies`. 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.
Fat interface: IPackageManager (29 members) src/UniGetUI.PackageEngine.Interfaces/IPackageManager.cs:10— `IPackageManager` declares 29 members: `Properties`, `Capabilities`, `Status`, `Id`, `Name`, `DisplayName`, `DefaultSource`, `TaskLogger`, `SourcesHelper`, `DetailsHelper`, `OperationHelper`, `Dependencies`, `OutputEncoding`, `InstallerUrlFollowsPackageVersion`, `CommandLineIsShellInterpreted`, `IdentifiersAreQuotedOnCommandLine`, `CompareVersions`, `Initialize`, `IsEnabled`, `IsReady`, `FindPackages`, `GetAvailableUpdates`, `LastUpdatesListingFailed`, `LastInstalledListingFailed`, `GetInstalledPackages`, `RefreshPackageIndexes`, `AttemptFastRepair`, `FindCandidateExecutableFiles`, `GetExecutableFile`. 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.
README/code drift docs/CLI.md:225— docs/CLI.md links to `src/UniGetUI.Core.Settings/SettingsEngine_Names.cs`, but `docs/src/UniGetUI.Core.Settings/SettingsEngine_Names.cs` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
README/code drift docs/CLI.md:226— docs/CLI.md links to `src/UniGetUI.Core.SecureSettings/SecureSettings.cs`, but `docs/src/UniGetUI.Core.SecureSettings/SecureSettings.cs` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
README/code drift docs/IPC.md:26— docs/IPC.md names the project `UniGetUI.IPC`, but no project, folder or namespace of that name exists. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
Off-boarding risk: anonymized user #1 — If anonymized user #1 becomes unavailable, 41 significant file(s) lose their only recent owner: src/UniGetUI.PackageEngine.PackageManagerClasses/Packages/Classes/StartMenuShortcutsDatabase.cs, src/UniGetUI.Avalonia/Views/SoftwarePages/PackageBundlesPage.cs, src/UniGetUI.Interface.IpcApi/IpcPackageApi.cs, src/UniGetUI.Avalonia/ViewModels/DialogPages/ManageShortcutsViewModel.cs, src/UniGetUI.Core.Tools/ShortcutFileRemover.cs, src/UniGetUI.Avalonia/ViewModels/Pages/SettingsPages/ScheduledTaskViewModel.cs, src/UniGetUI.Avalonia/ViewModels/DialogPages/PackageDetailsViewModel.cs, src/UniGetUI.PackageEngine.Managers.WinGet/ClientHelpers/WinGetTableLayout.cs (+33 more). Pair on, review, or document these before any departure.
Off-boarding risk: anonymized user #2 — If anonymized user #2 becomes unavailable, 13 significant file(s) lose their only recent owner: src/UniGetUI.Avalonia/ViewModels/Pages/SettingsPages/PolicyEditor/PolicyEditorSessionViewModel.cs, src/UniGetUI.Avalonia/ViewModels/Pages/SettingsPages/PolicyEditor/PolicyEditorSession.cs, src/UniGetUI.PackageEngine.AgentBroker/PolicyWriteElevation/WindowsPolicyWriteElevator.cs, src/UniGetUI.Avalonia/ViewModels/Pages/SettingsPages/PolicyEditor/PolicyEditorDialogViewModel.cs, src/UniGetUI.PackageEngine.AgentBroker/PolicyManagement/BrokerPolicyManagementService.cs, src/UniGetUI.PackageEngine.AgentBroker/PolicyWriteElevation/Protocol/PolicyElevationFrame.cs, src/UniGetUI.Avalonia/Views/Pages/SettingsPages/PolicyEditor/PolicyEditorDialog.axaml.cs, src/UniGetUI.PackageEngine.AgentBroker/PolicyWriteElevation/WindowsElevatedHelperLauncher.cs (+5 more). Pair on, review, or document these before any departure.
No security response headers detected — None of the 11 security response headers the OWASP Secure Headers Project recommends (Content-Security-Policy, Strict-Transport-Security, X-Content-Type-Options, X-Frame-Options, …) is configured — defense in depth, even when a reverse proxy could set them. (−2.0 on this card.)
No security response headers detected src/UniGetUI.Interface.IpcApi/IpcServer.cs:71— This web host's pipeline is composed here and adds no security response header (Content-Security-Policy, Strict-Transport-Security, X-Content-Type-Options, a frame policy) to what it serves.
No app-layer HTTPS enforcement detected — No UseHttpsRedirection/UseHsts and no reverse-proxy signal — transport security is unverified at the app layer. (−2.0 on this card.)
No app-layer HTTPS enforcement detected src/UniGetUI.Interface.IpcApi/IpcServer.cs:71— This web host's pipeline is composed here with no UseHttpsRedirection/UseHsts, and nothing says a reverse proxy terminates TLS in front of it.
C4 · Data Retention· Partial data-retention evidence · ×1
Partial data-retention evidence — A retention mechanism is present, but the data-lifecycle is not yet complete — missing: a scheduled purge / cleanup job (PurgeOlderThan / CleanupJob).
D16 · Bus Factor· Further sole-owners (lower concentration) · ×1
Further sole-owners (lower concentration) — 4 other contributor(s) are each the sole owner of a small amount of code below the off-boarding threshold — folded into the bus-factor score and metrics (61 single-owned of 382 analysed files in total, counted over production source files of roughly 2,400 bytes or more, excluding vendored, generated and example/demo trees and test files identified by path convention, largest first; 382 of the 592 production source files in this repository met that bar). They are anonymized user #3 (3 file(s)), anonymized user #4 (2 file(s)), anonymized user #5 (1 file(s)), anonymized user #6 (1 file(s)) — spread or document their files in the same way, at lower priority than the named off-boarding risks above. The files folded here: src/Shared/AutoUpdater.Helpers.cs, src/UniGetUI.Avalonia/Infrastructure/WindowsAvaloniaRenderingPolicy.cs, REDACTED, src/UniGetUI.PackageEngine.PackageManagerClasses/Manager/Helpers/BaseSourceHelper.cs, src/UniGetUI.PackageEngine.Serializable/SerializablePackage.cs, src/UniGetUI.Avalonia/Views/Controls/SmoothScrollManager.cs, src/UniGetUI.PackageEngine.Managers.Vcpkg/VcpkgGitDependency.cs.
No ADRs found — No ADRs found. No recognised ADR directory (`docs/adr/`, `docs/decisions/`, `adr/`, `docs/rfcs/`, an `ADR0001/` folder, or their siblings) exists anywhere in this tree. What was searched, so you can tell an empty log from a search that missed one: every directory under the tree (build output, dependencies and VCS metadata excepted), for a document that is either any non-index page inside a recognised ADR directory, whatever its name and however deeply nested (`docs/adr/use-postgres.md`, `docs/adr/2024/0001-x.md`); or a file anywhere whose name is ADR-shaped (`0001-use-postgres.md`, `adr-012-caching.md`); or, when neither turned anything up, a document carrying the decision-record signature (an "Architecture Decision Record" heading, or Status / Context / Decision / Consequences as section headings). A decision log that clears none of these — unnumbered files outside any recognised directory, without those headings — is not seen by this check and this row is then wrong. If that is your case, say so rather than renaming anything; otherwise, consider recording architectural decisions in `docs/adr/`.
Typo in field name: 'DWMThreadAdress' uses 'ss' instead of the standard 'ss' -> 'ss' wait, 'Adress' is a typo for 'Address'. The field is named 'DWMThreadAdress' which is a misspelling of 'Address'. — Rename 'DWMThreadAdress' to 'DWMThreadAddress' to correct the spelling error. (symbols: UniGetUI.DWMThreadHelper.DWMThreadAdress, UniGetUI.DWMThreadHelper.DWMThreadAddress)
D26 · Project Cohesion· Projects may be oversized for their cohesion · ×1
Projects may be oversized for their cohesion — 1 of 57 project(s) overshoot their size bounds, lowering Project Cohesion to 9.6/10. The most over is `UniGetUI.Avalonia` (39730 LoC, 257 public types across 24 namespaces). Review these for cohesion — split a project that spans unrelated responsibilities.
Pass-through layer src/UniGetUI.Tui/Views/Pages/ManagersPage.cs:22— ManagersPage: all 3 public methods forward their arguments unchanged to _form and add no behaviour — an extra hop (and usually an extra interface) to trace through. Call _form directly, or give the layer a job.
D28 · Secrets (history)· Rotate the exposed credentials · ×1
REDACTED
D34 · Knowledge Freshness· Orphaned files with no living knowledge · ×1
Orphaned files with no living knowledge — 14 of 382 analysed file(s) have no living knowledge left — their last meaningful change has decayed away, so if one breaks, no one currently understands it (counted over production source files of roughly 2,400 bytes or more, excluding vendored, generated and example/demo trees and test files identified by path convention, largest first; 382 of the 592 production source files in this repository met that bar). None is large enough to earn a read-through of its own, so this row stands in for the per-file rows rather than raising one each — most significant first: src/UniGetUI.PackageEngine.PackageManagerClasses/Packages/Classes/IgnoredUpdatesDatabase.cs, src/UniGetUI.Core.LanguageEngine/LanguageData.cs, REDACTED, src/ExternalLibraries.Clipboard/WindowsClipboard.cs, src/UniGetUI.PackageEngine.PackageManagerClasses/Manager/Helpers/BaseSourceHelper.cs, src/UniGetUI.Core.Settings/SettingsEngine.cs, src/UniGetUI.PackageEngine.Interfaces/IPackageDetails.cs, src/UniGetUI.PackageEngine.Serializable/SerializablePackage.cs (and 6 more). Attach the read to the next change that touches one of them: have a second person review that change, and leave behind a short comment or test recording what the file is for, so the knowledge comes back at the cost of a change you were making anyway.
No ADRs — 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.
P12 · CI test-gate honesty· Sleep-based test synchronization · ×1
Sleep-based test synchronization — 37 Task.Delay/Thread.Sleep call(s) in test code synchronize with background work by sleeping — a known flakiness precursor on slow runners. Prefer polling with a deadline or completion signals.
Logging is not universal — Only 29/30 service-like projects use logging (pure contract/DTO projects are excluded — they have nothing to log). Of those 30, 2 ship a process this repository operates; the rest are libraries their consumer hosts, where the logging decision belongs to the host.
P2 · Observability· Console output used as the logging channel · ×1
Console output used as the logging channel src/UniGetUI.Avalonia/CrashHandler.cs:270— `src/UniGetUI.Avalonia/CrashHandler.cs` reports through `Console.Write…` at line 270 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.
No changelog — No CHANGELOG/HISTORY/RELEASES file — what shipped when isn't easy to reconstruct for support or audit. (Versioning/tagging makes releases traceable, but a changelog records the what.)
PF1 · Benchmark discipline· No performance benchmarks · ×1
No performance benchmarks — No benchmark suite was found by the two searches this check runs. FIRST, a BenchmarkDotNet package reference in any project file — every project the workspace loaded, plus a walk of project files on disk that never loaded, because a benchmark suite is exactly the project a partial load drops. SECOND, a script harness: a file whose name contains `benchmark` and ends `.py`, `.sh`, `.ps1`, `.bash`, `.rb`, `.js` or `.mjs`, credited ONLY when this repository's CI text also mentions benchmarks — a harness no pipeline runs is read as a fixture, deliberately. Neither search can see a benchmark suite in another ecosystem's idiom (a Go `testing.B` file, a JMH or criterion project, a pytest-benchmark run), so this is 'no benchmark found by those two searches', not a verdict that the repository has none. Where code is performance-sensitive, a benchmark guards against silent regressions — but it's a bonus here, not a deduction.
X2 · Cancellation propagation· Not all async methods take a CancellationToken · ×1
Not all async methods take a CancellationToken — Only 78/685 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.
Null-forgiving operator (`!`) suppressions reduce the NRT score — ~0.3 `!` suppressions per 1k syntax nodes — 183 suppression(s) across the 563871 syntax node(s) in code where nullable warnings are ENABLED, which is the only code a `!` can suppress anything in (a `!` under `#nullable disable` is inert and is not counted, and its file's nodes are not in the denominator). Each one tells the compiler to trust you about null, suppressing the very safety NRTs provide.
Silent fallback default on unknown code src/UniGetUI.Avalonia/App.axaml.cs:357— `ApplyTheme` maps every unrecognised code to `ThemeVariant.Default`, one of the real values, with no log or throw — a malformed or new code silently reads as a known one. Throw on the unknown code, or log it. If that member is the correct answer for any other code, say so in a comment on the member and the row stops firing.
X7 · Silent fallback defaults· Silent fallback default on lookup miss · ×1
Silent fallback default on lookup miss src/UniGetUI.Interface.IpcApi/IpcClient.cs:149— `GetOperationOutputAsync` answers a miss of `ReadAuthenticatedJsonAsync<IpcOperationOutputResult>( HttpMethod.Get, IpcHttpRou…` with `new IpcOperationOutputResult { OperationId = operationId, }` — an entity fabricated around `operationId`, which the caller cannot tell from a stored one. Return null or a not-found result, or throw.
Every external tool invocation behind a deep-scan dimension — the tool, its captured version, the exact command, how many findings it yielded, and a link to the retained raw output. To reproduce any finding: check out the same commit and run the command shown (repo-relative — never an absolute scratch path). The complete raw scanner output is retained verbatim under artifacts/raw/ (indexed in artifacts/raw/index.json); per-invocation exit codes and wall-clock durations are in sidecar.json — kept out of this table so the rendered report stays byte-identical across runs of the same commit.
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
trivy: not applicable — No Infrastructure-as-Code or container manifests found (Dockerfile, Docker Compose, Terraform, Kubernetes/Helm, CloudFormation, ARM, Bicep, Ansible); nothing to scan.
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 96 file(s) — `scripts/CargoSmoke/Program.cs`, `src/Shared/SharedPreUiCommandDispatcher.cs`, `src/Shared/StartupBundleArguments.cs`, `src/UniGetUI.Avalonia/App.axaml.cs`, `src/UniGetUI.Avalonia/CrashHandler.cs`, … (+91 more) — so the PII/GDPR sweep did not cover the unparsed regions of them; rows reported elsewhere in those files are real.
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.
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.
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.
none (no readable dependency manifest): not applicable — Not scored — no dependency manifest in a supported ecosystem was read for this repository. A gap in the analyzer's language coverage, NOT a finding that the repository is free of vulnerable dependencies (a Python pyproject.toml/requirements.txt (pip/uv/Poetry), a Swift Package.swift/Package.resolved, a Cargo manifest, a Go module (go.mod/go.sum), a Gradle version catalogue, a Maven POM, an sbt build (build.sbt), composer.json, package.json, a Dart pubspec.yaml, an Elixir mix.exs/mix.lock (Hex), a rebar.config / erlang.mk DEPS (Hex), a Ruby Gemfile/Gemfile.lock or .gemspec (Bundler/RubyGems) — not scanned yet).
0
—
Run 01a167aa-0ab5-7760-a7a2-3e32593e0d98 · every finding is also locatable in findings.md, and the complete scoring record (with exit codes + durations) in sidecar.json.
Issues: 120 · Warnings: 794 · Recommendations: 118 · Info: 44 — Appendix A · all findings · full markdown report.
Generated by Watchdog — deterministic code-health analysis. 23-10-2026 @ 07:29 UTC.
Downloadable artifacts
Machine-readable and reproducible from this commit + frozen rubric — drop them straight into a contract appendix, a CRA dossier, or a downstream SCA / VEX tool.