Public report of Flow-Launcher/Flow.Launcher, 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 report Measured 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, 06:52 UTC · Survey ID cd_bb857dbef6d04ed095414b6f1879abee

Flow-Launcher/Flow.Launcher

Measured 23 October 2026, 06:46 UTC, at code version 3b89277

No regression since the last survey Code coverage: not measuredTest reliability: not measuredBoundary Type-Coupling: not measured

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.

Code coverage is not measured: No coverage collector is wired up.

Test reliability is not measured: No test run produced results.

Boundary Type-Coupling is not measured: Bounded contexts not declared.

CAI score 46out of 100 Provisional 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.

Architecture 76 Adequate Performance 72 Strong Production Readiness 64 Adequate Maturity 50 Adequate Code Health 50 Adequate Security and Compliance 35 Weak

A medium codebase: 47,054 lines of product code in 17 projects, tests not counted · Estimated rebuild effort: about 0.7 person-years · Weakest lens: Security and Compliance, 35

Findings by how serious they are

102 critical 332 serious 158 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, 06:46 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 code didn't build, so the score is provisional
Watchdog couldn't build the code: the build stopped with 90 errors. The dimensions that need a working build, such as complexity, duplication and dead code, were measured on an incomplete picture of the code, so their grades and the score are provisional. Fix the build errors and run the survey again for a final score. The first errors: CS0103: The name 'Localize' does not exist in the current context

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 ▸

72of 76 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.
536of 592 findings point to an exact file and line, so you can open each one in the code. The other 56 concern the repository as a whole, such as missing documentation.
76dimensions across 6 lenses, read from 47,054 lines of product code in 17 projects.
Chapters

Executive summary

Flow-Launcher/Flow.Launcher scores 46 out of 100, but the score is provisional because the code didn't build, so the ratings below may change once it does.

The weakest lens counts most in the score, and here that is Security and Compliance, which scores 35 and is rated Weak. Its Supply-chain Provenance & Signing 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 encrypt sensitive data at rest (ASP.NET Core Data Protection / column encryption) and manage keys in a vault and to resolve the 4 REDACTED finding(s) in Supply-chain Provenance & Signing, and if Security and Compliance rose to 70, the score would rise from 46 to about 55.

102 findings are critical: 65 in Static Analysis (SAST), 30 in Explicit Debt, six in Project dependency cycles and one in Secrets (history).

Watchdog couldn't measure IL Efficiency, Platform End-of-Life and Runtime evidence locked — no reproducible boot in this code, so those dimensions are left out of the score. The product code is 47,054 lines, which would take an estimated 0.7 person-years, around €110,000, to rebuild.

Code Health 50 Adequate, capped by Solution Shape and Nullable reference types Architecture 76 Adequate, capped by Stateful singletons Maturity 50 Adequate, capped by Architecture documentation Production Readiness 64 Adequate, capped by Security & performance tooling Security and Compliance 35 Weak, capped by Static Analysis (SAST), Supply-chain Provenance & Signing and Data Protection Performance 72 Strong

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 for The 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.
Security and Compliance 35 · counts for 46%Code Health 50 · counts for 25%Maturity 50 · counts for 14%Production Readiness 64 · counts for 8%Performance 72 · counts for 4%Architecture 76 · counts for 2%

If Security and Compliance rose from 35 to 70, the lowest score rated Strong, the score would rise from 46 to about 55.

Code composition: what the lines of code are
Business logic 41%Supporting code 40%Tests 8%Generated by tools 11%
New since the last survey: 61 findings

These 61 critical or serious findings weren't in the previous survey, on 9 October 2026.

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: 122 findings

These 122 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.

  • Explicit Debt · WriteOnlyPrivateField Plugins/Flow.Launcher.Plugin.WindowsSettings/Classes/WindowsSetting.cs
  • Knowledge Freshness · Orphaned knowledge Plugins/Flow.Launcher.Plugin.Explorer/Helper/ShellContextMenu.cs
  • Supply-chain Provenance & Signing REDACTED
  • Supply-chain Provenance & Signing REDACTED
  • Cancellation propagation · Async method without CancellationToken: OpenHotkeyDialogAsync Flow.Launcher/HotkeyControl.xaml.cs
  • Cancellation propagation · Async method without CancellationToken: SetImageAsync Flow.Launcher/MessageBoxEx.xaml.cs
  • Cancellation propagation · Async method without CancellationToken: LoadImageAsync Flow.Launcher/Msg.xaml.cs
  • Cancellation propagation · Async method without CancellationToken: LoadImageAsync Flow.Launcher/MsgWithButton.xaml.cs
  • Cancellation propagation · Async method without CancellationToken: OpenHelperAsync Flow.Launcher/SettingPages/ViewModels/SettingsPanePluginsViewModel.cs
  • Cancellation propagation · Async method without CancellationToken: TogglePreviewAsync Flow.Launcher/ViewModel/MainViewModel.cs
  • Cancellation propagation · Async method without CancellationToken: OpenExternalPreviewAsync Flow.Launcher/ViewModel/MainViewModel.cs
  • Cancellation propagation · Async method without CancellationToken: CloseExternalPreviewAsync Flow.Launcher/ViewModel/MainViewModel.cs
  • Cancellation propagation · Async method without CancellationToken: SwitchExternalPreviewAsync Flow.Launcher/ViewModel/MainViewModel.cs
  • Cancellation propagation · Async method without CancellationToken: UpdatePreviewAsync Flow.Launcher/ViewModel/MainViewModel.cs
  • Cancellation propagation · Async method without CancellationToken: ResetPreviewAsync Flow.Launcher/ViewModel/MainViewModel.cs
  • Cancellation propagation · Async method without CancellationToken: QueryAsync Flow.Launcher/ViewModel/MainViewModel.cs
  • Cancellation propagation · Async method without CancellationToken: ConstructQueryAsync Flow.Launcher/ViewModel/MainViewModel.cs
  • Cancellation propagation · Async method without CancellationToken: BuildQueryAsync Flow.Launcher/ViewModel/MainViewModel.cs
  • Cancellation propagation · Async method without CancellationToken: SetupDialogJumpAsync Flow.Launcher/ViewModel/MainViewModel.cs
  • Cancellation propagation · Async method without CancellationToken: ResetDialogJump Flow.Launcher/ViewModel/MainViewModel.cs
  • Cancellation propagation · Async method without CancellationToken: ResetWindowAsync Flow.Launcher/ViewModel/MainViewModel.cs
  • Cancellation propagation · Async method without CancellationToken: Hide Flow.Launcher/ViewModel/MainViewModel.cs
  • Cancellation propagation · Async method without CancellationToken: ShowCommandQueryAsync Flow.Launcher/ViewModel/PluginStoreItemViewModel.cs
  • Cancellation propagation · Async method without CancellationToken: LoadIconAsync Flow.Launcher/ViewModel/PluginViewModel.cs
  • Cancellation propagation · Async method without CancellationToken: OpenDeletePluginWindowAsync Flow.Launcher/ViewModel/PluginViewModel.cs
  • Cancellation propagation · Async method without CancellationToken: UpdatePluginAsync Flow.Launcher/ViewModel/PluginViewModel.cs
  • Cancellation propagation · Async method without CancellationToken: LoadImageInternalAsync Flow.Launcher/ViewModel/ResultViewModel.cs
  • Cancellation propagation · Async method without CancellationToken: LoadImageAsync Flow.Launcher/ViewModel/ResultViewModel.cs
  • Cancellation propagation · Async method without CancellationToken: LoadBadgeImageAsync Flow.Launcher/ViewModel/ResultViewModel.cs
  • Cancellation propagation · Async method without CancellationToken: LoadPreviewImageAsync Flow.Launcher/ViewModel/ResultViewModel.cs
  • Cancellation propagation · Async method without CancellationToken: InvokeShowDialogJumpWindowAsync Flow.Launcher.Infrastructure/DialogJump/DialogJump.cs
  • Cancellation propagation · Async method without CancellationToken: ForegroundChangeCallback Flow.Launcher.Infrastructure/DialogJump/DialogJump.cs
  • Cancellation propagation · Async method without CancellationToken: JumpToPathAsync Flow.Launcher.Infrastructure/DialogJump/DialogJump.cs
  • Cancellation propagation · Async method without CancellationToken: NavigateDialogPathAsync Flow.Launcher.Infrastructure/DialogJump/DialogJump.cs
  • Cancellation propagation · Async method without CancellationToken: JumpToPathAsync Flow.Launcher.Infrastructure/DialogJump/DialogJump.cs
  • Cancellation propagation · Async method without CancellationToken: GetOrAddAsync Flow.Launcher.Infrastructure/Image/ImageCache.cs
  • Cancellation propagation · Async method without CancellationToken: InitializeAsync Flow.Launcher.Infrastructure/Image/ImageLoader.cs
  • Cancellation propagation · Async method without CancellationToken: LoadInternalAsync Flow.Launcher.Infrastructure/Image/ImageLoader.cs
  • Cancellation propagation · Async method without CancellationToken: LoadRemoteImageAsync Flow.Launcher.Infrastructure/Image/ImageLoader.cs
  • Cancellation propagation · Async method without CancellationToken: LoadAsync Flow.Launcher.Infrastructure/Image/ImageLoader.cs
  • Cancellation propagation · Async method without CancellationToken: DebugAsync Flow.Launcher.Infrastructure/Stopwatch.cs
  • Cancellation propagation · Async method without CancellationToken: InfoAsync Flow.Launcher.Infrastructure/Stopwatch.cs
  • Cancellation propagation · Async method without CancellationToken: TryLoadAsync Flow.Launcher.Infrastructure/Storage/BinaryStorage.cs
  • Cancellation propagation · Async method without CancellationToken: DeserializeAsync Flow.Launcher.Infrastructure/Storage/BinaryStorage.cs
  • Cancellation propagation · Async method without CancellationToken: SaveAsync Flow.Launcher.Infrastructure/Storage/BinaryStorage.cs
  • Cancellation propagation · Async method without CancellationToken: SaveAsync Flow.Launcher.Infrastructure/Storage/BinaryStorage.cs
  • Cancellation propagation · Async method without CancellationToken: SaveAsync Flow.Launcher.Infrastructure/Storage/FlowLauncherJsonStorage.cs
  • Cancellation propagation · Async method without CancellationToken: LoadAsync Flow.Launcher.Infrastructure/Storage/JsonStorage.cs
  • Cancellation propagation · Async method without CancellationToken: LoadBackupOrDefaultAsync Flow.Launcher.Infrastructure/Storage/JsonStorage.cs
  • Cancellation propagation · Async method without CancellationToken: TryLoadBackupAsync Flow.Launcher.Infrastructure/Storage/JsonStorage.cs
  • Cancellation propagation · Async method without CancellationToken: SaveAsync Flow.Launcher.Infrastructure/Storage/JsonStorage.cs
  • Cancellation propagation · Async method without CancellationToken: SaveAsync Flow.Launcher.Infrastructure/Storage/PluginBinaryStorage.cs
  • Cancellation propagation · Async method without CancellationToken: SaveAsync Flow.Launcher.Infrastructure/Storage/PluginJsonStorage.cs
  • Cancellation propagation · Async method without CancellationToken: DeserializedResultAsync Flow.Launcher.Core/Plugin/JsonRPCPlugin.cs
  • Cancellation propagation · Async method without CancellationToken: InitSettingAsync Flow.Launcher.Core/Plugin/JsonRPCPluginBase.cs
  • Cancellation propagation · Async method without CancellationToken: InitializeAsync Flow.Launcher.Core/Plugin/JsonRPCPluginSettings.cs
  • Cancellation propagation · Async method without CancellationToken: SaveAsync Flow.Launcher.Core/Plugin/JsonRPCPluginSettings.cs
  • Cancellation propagation · Async method without CancellationToken: InstallPluginAndCheckRestartAsync Flow.Launcher.Core/Plugin/PluginInstaller.cs
  • Cancellation propagation · Async method without CancellationToken: InstallPluginAndCheckRestartAsync Flow.Launcher.Core/Plugin/PluginInstaller.cs
  • Cancellation propagation · Async method without CancellationToken: UninstallPluginAndCheckRestartAsync Flow.Launcher.Core/Plugin/PluginInstaller.cs
  • Cancellation propagation · Async method without CancellationToken: UpdatePluginAndCheckRestartAsync Flow.Launcher.Core/Plugin/PluginInstaller.cs
  • Cancellation propagation · Async method without CancellationToken: UpdateAllPluginsFromNotificationAsync Flow.Launcher.Core/Plugin/PluginInstaller.cs
  • Cancellation propagation · Async method without CancellationToken: UpdateAllPluginsAsync Flow.Launcher.Core/Plugin/PluginInstaller.cs
  • Cancellation propagation · Async method without CancellationToken: UpdateAllPluginsCoreAsync Flow.Launcher.Core/Plugin/PluginInstaller.cs
  • Cancellation propagation · Async method without CancellationToken: DisposePluginsAsync Flow.Launcher.Core/Plugin/PluginManager.cs
  • Cancellation propagation · Async method without CancellationToken: DisposePluginAsync Flow.Launcher.Core/Plugin/PluginManager.cs
  • Cancellation propagation · Async method without CancellationToken: ReloadDataAsync Flow.Launcher.Core/Plugin/PluginManager.cs
  • Cancellation propagation · Async method without CancellationToken: OpenExternalPreviewAsync Flow.Launcher.Core/Plugin/PluginManager.cs
  • Cancellation propagation · Async method without CancellationToken: CloseExternalPreviewAsync Flow.Launcher.Core/Plugin/PluginManager.cs
  • Cancellation propagation · Async method without CancellationToken: SwitchExternalPreviewAsync Flow.Launcher.Core/Plugin/PluginManager.cs
  • Cancellation propagation · Async method without CancellationToken: InitializePluginsAsync Flow.Launcher.Core/Plugin/PluginManager.cs
  • Cancellation propagation · Async method without CancellationToken: UpdatePluginAsync Flow.Launcher.Core/Plugin/PluginManager.cs
  • Cancellation propagation · Async method without CancellationToken: UninstallPluginAsync Flow.Launcher.Core/Plugin/PluginManager.cs
  • Cancellation propagation · Async method without CancellationToken: UninstallPluginAsync Flow.Launcher.Core/Plugin/PluginManager.cs
  • Cancellation propagation · Async method without CancellationToken: InitializeLanguageAsync Flow.Launcher.Core/Resource/Internationalization.cs
  • Cancellation propagation · Async method without CancellationToken: ChangeLanguageAsync Flow.Launcher.Core/Resource/Internationalization.cs
  • Cancellation propagation · Async method without CancellationToken: RefreshFrameAsync Flow.Launcher.Core/Resource/Theme.cs
  • Cancellation propagation · Async method without CancellationToken: SetBlurForWindowAsync Flow.Launcher.Core/Resource/Theme.cs
  • Cancellation propagation · Async method without CancellationToken: UpdateAppAsync Flow.Launcher.Core/Updater.cs
  • Cancellation propagation · Async method without CancellationToken: GitHubUpdateManagerAsync Flow.Launcher.Core/Updater.cs
  • Cancellation propagation · Async method without CancellationToken: IndexWin32ProgramsAsync Plugins/Flow.Launcher.Plugin.Program/Main.cs
  • Cancellation propagation · Async method without CancellationToken: IndexUwpProgramsAsync Plugins/Flow.Launcher.Plugin.Program/Main.cs
  • Cancellation propagation · Async method without CancellationToken: IndexProgramsAsync Plugins/Flow.Launcher.Plugin.Program/Main.cs
  • Cancellation propagation · Async method without CancellationToken: DisableProgramAsync Plugins/Flow.Launcher.Plugin.Program/Main.cs
  • Cancellation propagation · Async method without CancellationToken: WatchPackageChangeAsync REDACTED
  • Cancellation propagation · Async method without CancellationToken: MonitorDirectoryChangeAsync Plugins/Flow.Launcher.Plugin.Program/Programs/Win32.cs
  • Cancellation propagation · Async method without CancellationToken: DisplayAllProgramsAsync Plugins/Flow.Launcher.Plugin.Program/Views/Commands/ProgramSettingDisplay.cs
  • Cancellation propagation · Async method without CancellationToken: SetProgramSourcesStatusAsync Plugins/Flow.Launcher.Plugin.Program/Views/Commands/ProgramSettingDisplay.cs
  • Cancellation propagation · Async method without CancellationToken: IsReindexRequiredAsync Plugins/Flow.Launcher.Plugin.Program/Views/Commands/ProgramSettingDisplay.cs
  • Cancellation propagation · Async method without CancellationToken: ReIndexing Plugins/Flow.Launcher.Plugin.Program/Views/ProgramSetting.xaml.cs
  • Cancellation propagation · Async method without CancellationToken: EditProgramSource Plugins/Flow.Launcher.Plugin.Program/Views/ProgramSetting.xaml.cs
  • Cancellation propagation · Async method without CancellationToken: btnLoadAllProgramSource_OnClick Plugins/Flow.Launcher.Plugin.Program/Views/ProgramSetting.xaml.cs
  • Cancellation propagation · Async method without CancellationToken: btnProgramSourceStatus_OnClick Plugins/Flow.Launcher.Plugin.Program/Views/ProgramSetting.xaml.cs
  • Cancellation propagation · Async method without CancellationToken: btnDeleteProgramSource_OnClick Plugins/Flow.Launcher.Plugin.Program/Views/ProgramSetting.xaml.cs
  • Cancellation propagation · Async method without CancellationToken: Initialize Plugins/Flow.Launcher.Plugin.WebSearch/SearchSourceSetting.xaml.cs
  • Cancellation propagation · Async method without CancellationToken: OnSelectIconClick Plugins/Flow.Launcher.Plugin.WebSearch/SearchSourceSetting.xaml.cs
  • Cancellation propagation · Async method without CancellationToken: LoadPreviewIconAsync Plugins/Flow.Launcher.Plugin.WebSearch/SearchSourceViewModel.cs
  • Cancellation propagation · Async method without CancellationToken: MonitorRefreshQueueAsync Plugins/Flow.Launcher.Plugin.BrowserBookmark/Main.cs
  • Cancellation propagation · Async method without CancellationToken: PromptDownloadIfNotInstallAsync Plugins/Flow.Launcher.Plugin.Explorer/Search/Everything/EverythingDownloadHelper.cs
  • Cancellation propagation · Async method without CancellationToken: ClickToInstallEverythingAsync Plugins/Flow.Launcher.Plugin.Explorer/Search/Everything/EverythingSearchManager.cs
Rebuild cost: about €110,000 · Estimate
Cost to rebuild€35,000 to €180,000, for 591 to 1,925 hours of work, about 0.7 person-years for 1 to 2 engineers
Difficulty of the problemStandard, 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 46. 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.
SizeMedium: 47,054 lines of product code
Comment linesThe estimate prices 41,994 lines. Comment lines count towards the size of 47,054 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
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.).
Raises the score by about 9 points · Medium effort · Data Protection
2
Resolve the 4 REDACTED finding(s) in Supply-chain Provenance & Signing — start with REDACTED, REDACTED, REDACTED.
Raises the score by about 4 points · Low effort · Supply-chain Provenance & Signing
3
Resolve the 1 No ADRs found finding(s) in ADR Quality.
Raises the score by about 3 points · Low effort · ADR Quality

Diagnosis: what the measurements show together

Each conclusion below combines several dimensions into one point that no single dimension shows, and lists the measurements it rests on.

If you do one thing first · First action
Fix the build. The code didn't build, so the dimensions that need a working build were measured on an incomplete picture of the code, and every grade in this report is provisional. Once the build works, the next survey gives a final score. The compiler's first errors: CS0103: The name 'Localize' does not exist in the current context
Based on: Solution Shape
Where the investment is most exposed · Value at risk
This code would cost about €110,000 to build again, about 0.7 person-years of work. Its weakest lens is Security and Compliance, at 35 (Weak). 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.

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.

arch Flow.Launcher Launcher Flow.Launcher.Core Core Flow.Launcher->Flow.Launcher.Core Flow.Launcher.Infrastructure Infrastructure Flow.Launcher->Flow.Launcher.Infrastructure Flow.Launcher.Plugin Plugin Flow.Launcher->Flow.Launcher.Plugin Flow.Launcher.Core->Flow.Launcher.Infrastructure Flow.Launcher.Core->Flow.Launcher.Plugin Flow.Launcher.Infrastructure->Flow.Launcher.Plugin Flow.Launcher.Plugin.BrowserBookmark BrowserBookmark Flow.Launcher.Plugin.BrowserBookmark->Flow.Launcher.Plugin Flow.Launcher.Plugin.Calculator Calculator Flow.Launcher.Plugin.Calculator->Flow.Launcher.Plugin Flow.Launcher.Plugin.Explorer Explorer Flow.Launcher.Plugin.Explorer->Flow.Launcher.Plugin Flow.Launcher.Plugin.PluginIndicator PluginIndicator Flow.Launcher.Plugin.PluginIndicator->Flow.Launcher.Plugin Flow.Launcher.Plugin.PluginsManager PluginsManager Flow.Launcher.Plugin.PluginsManager->Flow.Launcher.Plugin Flow.Launcher.Plugin.ProcessKiller ProcessKiller Flow.Launcher.Plugin.ProcessKiller->Flow.Launcher.Plugin Flow.Launcher.Plugin.Program Program Flow.Launcher.Plugin.Program->Flow.Launcher.Plugin Flow.Launcher.Plugin.Shell Shell Flow.Launcher.Plugin.Shell->Flow.Launcher.Plugin Flow.Launcher.Plugin.Sys Sys Flow.Launcher.Plugin.Sys->Flow.Launcher.Plugin Flow.Launcher.Plugin.Url Url Flow.Launcher.Plugin.Url->Flow.Launcher.Plugin Flow.Launcher.Plugin.WebSearch WebSearch Flow.Launcher.Plugin.WebSearch->Flow.Launcher.Plugin Flow.Launcher.Plugin.WindowsSettings WindowsSettings Flow.Launcher.Plugin.WindowsSettings->Flow.Launcher.Plugin

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.

82 modules, with 152 dependencies between them. 6 loops run through 19 of the modules, marked above the diagonal.

The table shows the 40 modules with the most connections; 42 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.
uses →1 Plugin.SharedModels2 Infrastructure3 Plugin4 Plugin.ProcessKiller.ViewModels5 Plugin.Program.Views.Models6 Core7 Infrastructure.Hotkey8 Infrastructure.Storage9 Plugin.BrowserBookmark.Models10 Plugin.Calculator.ViewModels11 Plugin.Explorer.Search12 Plugin.PluginsManager.ViewModels13 Plugin.ProcessKiller14 Plugin.Program.Programs15 Plugin.Program.ViewModels16 Plugin.Shell17 Plugin.WindowsSettings.Classes18 Infrastructure.UserSettings19 Plugin.Calculator20 Plugin.Explorer.Search.IProvider21 Plugin.Explorer.Search.QuickAccessLinks22 Plugin.PluginsManager23 Plugin.Program24 Storage25 Core.ExternalPlugins.Environments26 Core.Plugin27 Core.Resource28 Infrastructure.DialogJump29 Plugin.Explorer.Search.Everything30 Plugin.Explorer.Search.WindowsIndex31 Plugin.Program.Views32 Core.Plugin.JsonRPCV2Models33 Plugin.Explorer.ViewModels34 ViewModel35 Helper36 Plugin.Explorer37 Resources.Pages38 SettingPages.ViewModels39 Flow.Launcher40 Plugin.Explorer.Views
1 Plugin.SharedModels
2 Infrastructure24
3 Plugin2
4 Plugin.ProcessKiller.ViewModels1
5 Plugin.Program.Views.Models1
6 Core1
7 Infrastructure.Hotkey4
8 Infrastructure.Storage5
9 Plugin.BrowserBookmark.Models2
10 Plugin.Calculator.ViewModels12
11 Plugin.Explorer.Search103
12 Plugin.PluginsManager.ViewModels11
13 Plugin.ProcessKiller171
14 Plugin.Program.Programs1612
15 Plugin.Program.ViewModels311
16 Plugin.Shell10
17 Plugin.WindowsSettings.Classes1
18 Infrastructure.UserSettings11621
19 Plugin.Calculator61
20 Plugin.Explorer.Search.IProvider3
21 Plugin.Explorer.Search.QuickAccessLinks21
22 Plugin.PluginsManager161
23 Plugin.Program9131
24 Storage81
25 Core.ExternalPlugins.Environments138
26 Core.Plugin3913
27 Core.Resource123
28 Infrastructure.DialogJump82
29 Plugin.Explorer.Search.Everything2531
30 Plugin.Explorer.Search.WindowsIndex232
31 Plugin.Program.Views111
32 Core.Plugin.JsonRPCV2Models121
33 Plugin.Explorer.ViewModels31116
34 ViewModel2911242
35 Helper11211
36 Plugin.Explorer12231211
37 Resources.Pages1525
38 SettingPages.ViewModels1831933
39 Flow.Launcher31213913811
40 Plugin.Explorer.Views2121
Uses a module listed above itPart of a loopThe module itself
1 Plugin.SharedModels2 Infrastructure3 Plugin4 Plugin.ProcessKiller.ViewModels5 Plugin.Program.Views.Models6 Core7 Infrastructure.Hotkey8 Infrastructure.Storage9 Plugin.BrowserBookmark.Models10 Plugin.Calculator.ViewModels11 Plugin.Explorer.Search12 Plugin.PluginsManager.ViewModels13 Plugin.ProcessKiller14 Plugin.Program.Programs15 Plugin.Program.ViewModels16 Plugin.Shell17 Plugin.WindowsSettings.Classes18 Infrastructure.UserSettings19 Plugin.Calculator20 Plugin.Explorer.Search.IProvider21 Plugin.Explorer.Search.QuickAccessLinks22 Plugin.PluginsManager23 Plugin.Program24 Storage25 Core.ExternalPlugins.Environments26 Core.Plugin27 Core.Resource28 Infrastructure.DialogJump29 Plugin.Explorer.Search.Everything30 Plugin.Explorer.Search.WindowsIndex31 Plugin.Program.Views32 Core.Plugin.JsonRPCV2Models33 Plugin.Explorer.ViewModels34 ViewModel35 Helper36 Plugin.Explorer37 Resources.Pages38 SettingPages.ViewModels39 Flow.Launcher40 Plugin.Explorer.ViewsPlugin.SharedModels1Infrastructure2Plugin3Plugin.ProcessKiller.ViewModels4Plugin.Program.Views.Models5Core6Infrastructure.Hotkey7Infrastructure.Storage8Plugin.BrowserBookmark.Models9Plugin.Calculator.ViewModels10Plugin.Explorer.Search11Plugin.PluginsManager.ViewModels12Plugin.ProcessKiller13Plugin.Program.Programs14Plugin.Program.ViewModels15Plugin.Shell16Plugin.WindowsSettings.Classes17Infrastructure.UserSettings18Plugin.Calculator19Plugin.Explorer.Search.IProvider20Plugin.Explorer.Search.QuickAccessLinks21Plugin.PluginsManager22Plugin.Program23Storage24Core.ExternalPlugins.Environments25Core.Plugin26Core.Resource27Infrastructure.DialogJump28Plugin.Explorer.Search.Everything29Plugin.Explorer.Search.WindowsIndex30Plugin.Program.Views31Core.Plugin.JsonRPCV2Models32Plugin.Explorer.ViewModels33ViewModel34Helper35Plugin.Explorer36Resources.Pages37SettingPages.ViewModels38Flow.Launcher39Plugin.Explorer.Views402421114521210311171161231110111621613211619131811383913123822531232111121311162911242112111223121115251831933312139138112121+42 more modules (most-connected shown)

At a glance — Code Health · 50% · Adequate · gated by D18, X5 ·

The Good
D1 · .NET / C# Cyclomatic Complexity 7.2 D3 · .NET / C# God Classes 8.4 D4 · .NET / C# Code Duplication 9.6 D17 · .NET / C# Explicit Debt 7.7 GD1 · Repo Unfinished & placeholder code 9.9 IC1 · Repo Incompleteness & stubs 9.0 X12 · Repo Unreachable branch 10.0 X13 · Repo Undrained process stream 10.0 X16 · Repo Unfloored truncation loop 10.0 X19 · Repo Unrestored process-global state 10.0 X20 · Repo Mistyped argument guard 10.0 X21 · Repo Side-effecting pattern guard 10.0 X22 · Repo Contradicted release guard 10.0 X23 · Repo Unguarded diagnostic materialisation 7.0 X25 · Repo Inert configuration knob 10.0 X26 · Repo Unsynchronised callback handoff 10.0 X27 · Repo Collection changed while being enumerated 10.0 X28 · Repo Index access outside its own emptiness guard 10.0 X29 · Repo Per-element action decided by a fixed element 10.0 X30 · Repo Support guard that admits what it rejects 10.0 X32 · Repo Type resolved by simple name across every loaded assembly 10.0
The Bad
D2 · .NET / C# Cognitive Complexity 6.5 X1 · Repo Async correctness 5.5 X18 · Repo Disposal-pattern correctness 5.5 X2 · Repo Cancellation propagation 5.5 X3 · Repo Exception handling 5.6 X4 · Repo Structured logging 5.6
The Ugly
D18 · .NET / C# Solution Shape 3.0 X5 · Repo Nullable reference types 2.4

At a glance — Architecture · 76% · Adequate · gated by AX2 ·

The Good
D5 · .NET / C# Coupling 10.0 D6 · .NET / C# Cohesion (LCOM4) 9.6 D26 · .NET / C# Project Cohesion 9.2 D27 · .NET / C# Navigability 8.8 D35 · .NET / C# Change Coupling 9.8 AX1 · Repo Captive dependencies 10.0 AX10 · Repo Code composition 8.5 AX3 · Repo Project dependency cycles 10.0 AX4 · Repo Dependency direction 10.0 AX5 · Repo Architecture & structure 10.0 AX6 · Repo Interface segregation 9.9 AX8 · Repo Test isolation 10.0
The Ugly
AX2 · Repo Stateful singletons 2.8

At a glance — Maturity · 50% · Adequate · gated by M2 ·

The Good
D15 · .NET / C# Churn × Complexity Hotspots 9.6 D16 · .NET / C# Bus Factor 8.4 D21 · .NET / C# Naming Consistency 10.0 D24 · .NET / C# Comment Value 9.8 D34 · .NET / C# Knowledge Freshness 9.6 M1 · Repo Documentation (README) 7.1 M3 · Repo Folder & project structure 8.0 M4 · Repo Documentation accuracy 10.0
The Bad
D19 · .NET / C# Documentation Quality 6.0
The Ugly
D20 · .NET / C# ADR Quality 0.0 M2 · Repo Architecture documentation 0.0

At a glance — Readiness · 64% · Adequate · gated by P3 ·

The Good
D9 · .NET / C# Test Distribution 10.0 D10 · .NET / C# Test Quality 10.0 D12 · .NET / C# Dependency Hygiene 8.4 D13 · .NET / C# REDACTED Scanning 10.0 D14 · .NET / C# License Compliance 10.0 P1 · Repo CI/CD gates 10.0 P10 · Repo Library API & versioning 10.0 P4 · Repo Deployment & Rollback 7.0
The Bad
P6 · Repo Release Hygiene 5.0
The Ugly
P3 · Repo Security & performance tooling 3.0

At a glance — Security · 35% · Weak · gated by D29, D36, C1 ·

The Good
D28 · .NET / C# Secrets (history) 9.0 D43 · .NET / C# Malicious Dependencies 10.0 S1 · Repo Cryptographic Hygiene 8.0 X14 · Repo Bypassable address classification 10.0 X15 · Repo Unvalidated length from an untrusted reader 10.0 X17 · Repo Uncapped recursion over a caller-supplied document 10.0 X24 · Repo Document value interpolated into markup unescaped 10.0
The Ugly
D29 · .NET / C# Static Analysis (SAST) 0.1 D36 · .NET / C# Supply-chain Provenance & Signing 0.0 C1 · Repo Data Protection 0.0

At a glance — Performance · 72% · Strong ·

The Good
PF3 · Repo Async & latency hygiene 10.0
The Bad
PF1 · Repo Benchmark discipline 6.0 PF2 · Repo Allocation hygiene 6.6

Security & Compliance — OWASP Top-10 mapping

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 categoryFindingsSeverity
A05:2025 — Injection75High / Critical
A03:2025 — Software Supply Chain Failures12Medium
A07:2025 — Authentication Failures2High / Critical

Roadmap

Immediately secure sensitive data by implementing encryption at rest and managing keys in a vault, while resolving the fifteen static analysis findings related to secrets in workflow files. Address supply-chain risks by fixing unscoped long-lived secrets in deployment workflows and establish architectural governance by documenting significant design decisions as Architecture Decision Records in a dedicated folder.

Ranked by impact ÷ effort. "Helps" is the estimated gain on the 0–100 health score.

Do thisHelpsEffortDimension
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.).+9.5 ptsMediumData Protection
Resolve the 4 REDACTED finding(s) in Supply-chain Provenance & Signing — start with REDACTED, REDACTED, REDACTED.+3.9 ptsLowSupply-chain Provenance & Signing
Resolve the 1 No ADRs found finding(s) in ADR Quality.+2.7 ptsLowADR Quality
Resolve the 15 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (12), REDACTED, REDACTED.+5.1 ptsMediumStatic Analysis (SAST)
Resolve the 1 NoWarnInCsproj repeated across 11 files finding(s) in Explicit Debt — start with Flow.Launcher.csproj.+2.4 ptsLowExplicit Debt
Resolve the 29 EmptyCatchBlock finding(s) in Explicit Debt — start with JsonRPCPluginV2.cs (4), Win32Helper.cs (4), WindowsExplorer.cs (3).+2.4 ptsMediumExplicit Debt
Resolve the 1 REDACTED finding(s) in Secrets (history) — start with REDACTED.+2.3 ptsLowSecrets (history)
Resolve the 3 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (3).+2.3 ptsLowStatic Analysis (SAST)

File quality

Per-file score 0–10 — a quality signature. Of 103 files carrying findings, judged against the Production bar: 9% slop · 53% mixed · 38% near-clean.

FileScoreBandWorst signal
REDACTED1.3SlopStatic Analysis (SAST): High: REDACTED
REDACTED1.3SlopStatic Analysis (SAST): High: REDACTED
Flow.Launcher/MainWindow.xaml.cs2.8SlopExplicit Debt: EmptyCatchBlock
Flow.Launcher.Infrastructure/DialogJump/DialogJump.cs2.8SlopExplicit Debt: EmptyCatchBlock
REDACTED3.0SlopStatic Analysis (SAST): High: REDACTED
REDACTED3.0SlopStatic Analysis (SAST): High: REDACTED
Flow.Launcher.Infrastructure/Win32Helper.cs3.3SlopExplicit Debt: EmptyCatchBlock
REDACTED3.7SlopStatic Analysis (SAST): High: REDACTED
REDACTED3.7SlopStatic Analysis (SAST): High: REDACTED
REDACTED4.0MixedStatic Analysis (SAST): Medium: REDACTED
REDACTED4.6MixedStatic Analysis (SAST): Medium: REDACTED
Plugins/Flow.Launcher.Plugin.Program/Programs/Win32.cs5.0MixedExplicit Debt: EmptyCatchBlock
REDACTED5.1MixedStatic Analysis (SAST): High: REDACTED
Flow.Launcher.Core/Plugin/JsonRPCPluginV2.cs5.5MixedExplicit Debt: EmptyCatchBlock
Flow.Launcher.Infrastructure/DialogJump/Models/WindowsExplorer.cs5.8MixedExplicit Debt: EmptyCatchBlock
Plugins/Flow.Launcher.Plugin.Program/Main.cs5.8MixedExplicit Debt: EmptyCatchBlock
REDACTED5.8MixedStatic Analysis (SAST): High: REDACTED
Flow.Launcher/ViewModel/MainViewModel.cs6.0MixedExplicit Debt: BarePragmaDisable
Flow.Launcher.Plugin/SharedCommands/FilesFolders.cs6.0MixedExplicit Debt: BarePragmaDisable
Flow.Launcher.Infrastructure/Exception/ExceptionFormatter.cs6.0MixedExplicit Debt: TodoComment

How the grades work

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 — 102

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 — 332

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 — 158

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. 72 of 76 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.8 — the weighted average across measured dimensions; it falls as more of the score leans on LLM-assisted judgement and rises when it's fully tool-backed.

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 — 76 dimensions across the health lenses
D1D2D3D4D5D6D9D10D12D13D14D15D16D17D18D19D20D21D24D26D27D28D29D34D35D36D43AX1AX10AX2AX3AX4AX5AX6AX8C1GD1IC1M1M2M3M4P1P10P3P4P6PF1PF2PF3S1X1X12X13X14X15X16X17X18X19X2X20X21X22X23X24X25X26X27X28X29X3X30X32X4X5

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
  1. 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, 536 of 592 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.)
  2. 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.
  3. 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.

MethodBacksVersionEvaluator
Roslyn static analysisComplexity, cohesion, coupling, dead code, API surface, layering5.3.0✓ deterministic
Native secret scannerHardcoded secrets / credentials1.0.0✓ deterministic
Watchdog duplication detector (in-process)Code duplication1.0.0✓ deterministic
Coverage (coverlet / dotnet-coverage)Line & branch coverage10.0.400✓ deterministic
NuGet / dotnetOutdated, vulnerable & deprecated dependencies10.0.400✓ deterministic
git / LibGit2SharpChurn hotspots, knowledge concentration, history2.43.0 · 0.31.0✓ deterministic
gitleaks · semgrep · trivySecrets in history, SAST, CVEs, IaC & container, PII / GDPR1.86.0 · 0.69.3✓ deterministic
LLM (sampled · advisory)Documentation quality, ADR conformance, naming — sampled over a bounded sample; advisory, never a deterministic measurementLocal LLM◐ LLM · sampled · advisory

Every finding is locatable in findings.md. Run 01a16782-ecb6-7ea2-96f5-a344783b157f.

The exact command behind every deep-scan dimension — tool, version, invocation and retained raw output — is in Appendix B — Reproduction & audit trail.

Run transparency — what happened this run

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.

  • 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 MEASURED: the test run produced no results for any test tier, so no test ever ran and flakiness could not be exercised. The cause could not be attributed, so it is excluded from the score rather than read as an absence of tests.
  • 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 'Flow.Launcher/Flow.Launcher.csproj' with message: Package 'DeltaCompressionDotNet 1.1.0' was restored using '.NETFramework,Version=v4.6.1, .NETFramework,Version=v4.6.2, .NETFramework,Version=v4.7, .NETFramework,Version=v4.7.1, .NETFramework,Version=v4.7.2, .NETFramework,Version=v4.8, .NETFramewor….
  • 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 (47,032 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. `Plugins/Flow.Launcher.Plugin.Calculator/ViewModels/SettingsViewModel.cs`, `Plugins/Flow.Launcher.Plugin.ProcessKiller/ProcessResult.cs`, `Plugins/Flow.Launcher.Plugin.ProcessKiller/ViewModels/SettingsViewModel.cs`, `Plugins/Flow.Launcher.Plugin.Sys/SettingsViewModel.cs` produced a parse error, so every rule in this engine's `gdpr.yml` was absent there. That absence is NOT a clean result: these rules detect personal data crossing a boundary into a log sink, a URL or browser storage, and a file that was never parsed cannot report any of the three. The rest of the tree analysed normally and its rows above stand; only these files are unaccounted for. You can widen what we reach: fix the syntax error (or exclude the file deliberately) and re-scan to cover it.
  • 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 build of this repository exited 1 and the cause could not be attributed, so no assemblies were produced and there was no IL to read. We do not read it as a defect in the repository: an unattributed failure leans OURS. D18 owns the question of whether this repository builds; it was not answered here.
  • D44 Platform End-of-Life — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This dimension reads a project's own statement about the platform it runs on: a TargetFramework in a .NET project file, a .nvmrc or .python-version, a capped requires-python, a Rust toolchain file or Cargo.toml rust-version, a .go-version, .java-version, .ruby-version, .tool-versions or .sdkmanrc, a go.mod go directive, a Maven or Gradle Java level or toolchain, a Gemfile's ruby directive, a mix.exs elixir requirement, a rebar.config minimum_otp_vsn, a pubspec.yaml SDK constraint, a build.sbt scalaVersion, or a framework major pinned by a dependency constraint. This repository carries none of them, so nothing about its platform was established. That is a gap in this analyzer's coverage, NOT a finding that the platform is supported — a language whose runtime is declared elsewhere (Package.swift, a Dockerfile) is simply not read here yet.
  • 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 (Flow.Launcher/WelcomeWindow.xaml). The Runtime Evidence tier boots an app only via docker-compose, an Aspire AppHost, a Dockerfile, an npm dev script, a web service's own toolchain entry point (cargo, go, dotnet, Python, Spring Boot), or an Android app's own Gradle wrapper (run on an emulator); an Apple or Flutter app needs a host it lacks. None applied, so no live runtime a11y/egress/header evidence was collected. You can widen what we reach: add a docker-compose.yml (or an Aspire AppHost) that brings the app up with its dependencies. Watchdog then boots it in an isolated sandbox and gathers real runtime evidence — you change nothing in your pipeline (no CI step, no SDK).
  • 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. 99 further occurrence(s) are not listed individually; the score already reflects all 139.

Repo exclusion declarations: 1 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.
  • D12 Dependency Hygiene: Dependency health reads manifests and lockfiles — a vulnerability in a vendored/copied dependency, or risk from how a dependency is actually used, is outside this view.
  • D13 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.
  • D43 Malicious Dependencies: Only packages some vulnerability database has already NAMED as malicious are seen — a compromise published in the last hours, or never reported at all, is invisible here, and this dimension reading 10 is not evidence that a dependency is trustworthy. There is no typosquat or dependency-confusion analysis: a package nobody has reported is simply absent from the feeds. Coverage is the dependency scan's: an ecosystem that could not be scanned is disclosed as unmeasured, never as clean.
  • AX10 Code composition: Role is inferred from namespace/folder convention, not semantics — a domain concept living in a folder named "Services" reads as application, and the split is lines-of-code, not business value. The business-logic-share score is a SOFT, FLOORED signal: it contributes to the Architecture lens but is floored at the Critical gate, so an infrastructure-heavy design (a gateway, an ETL, a driver) is legitimately low without being nuked to zero.
  • M4 Documentation accuracy: Onboarding quality is an LLM read of the docs/setup present — it cannot run the onboarding or measure how long a real new joiner takes; the verdict is sampled and advisory.
  • P4 Deployment & Rollback: Approval/branch-protection rules live in repository settings the scan cannot see — only their in-repo evidence (config files, workflows) is checked, so a control enforced purely in the host's settings reads as "not evidenced".
  • P6 Release Hygiene: Rollback/observability controls are inferred from repo artefacts (pipelines, dashboards-as-code) — controls configured in external tooling, with no in-repo trace, cannot be credited.

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.

Dimensions

D1 · Cyclomatic Complexity7.2 / 10Strong✓ Tool-verified

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.

Maturity: Documented → Verified → Prevented · effective 7.2 / 10 · rule-coverage 100% · ceiling Prevented

21 method(s) exceeded the cyclomatic complexity threshold of 15; the worst was MainWindow.OnLoaded at 44. A further 6 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 AvailableLanguages.GetSystemTranslation at 28 — they are counted neither in the figure above nor in this dimension's score. 4 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: Flow.Launcher.Core/Resource/AvailableLanguages.cs (AvailableLanguages.GetSystemTranslation at 28), Plugins/Flow.Launcher.Plugin.Explorer/Search/Everything/EverythingApiV3.cs (EverythingApiV3.TryConvertSortOption at 27), Flow.Launcher.Infrastructure/Hotkey/HotkeyModel.cs (HotkeyModel.IsPrintableCharacter at 24), Flow.Launcher/HotkeyControl.xaml.cs (HotkeyControl.Hotkey.get at 19). 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.

MainWindow.OnLoaded (cyclomatic 44)Flow.Launcher/MainWindow.xaml.cs:128
StringMatcher.FuzzyMatch (cyclomatic 35)Flow.Launcher.Infrastructure/StringMatcher.cs:61
MainViewModel.QueryResultsAsync (cyclomatic 34)Flow.Launcher/ViewModel/MainViewModel.cs:1537
ContextMenu.LoadContextMenus (cyclomatic 33)Plugins/Flow.Launcher.Plugin.Explorer/ContextMenu.cs:30
JsonRPCPluginSettings.CreateSettingPanel (cyclomatic 29)Flow.Launcher.Core/Plugin/JsonRPCPluginSettings.cs:156

+ 16 more group(s) — more in Appendix A; the complete list is findings.md.

What to do

  1. Bring the 21 bodies over 15 down to 15 or less in Cyclomatic Complexity — start with MainWindow.OnLoaded (cyclomatic 44), StringMatcher.FuzzyMatch (cyclomatic 35), MainViewModel.QueryResultsAsync (cyclomatic 34). — 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 21 together lifts Cyclomatic Complexity from 7.2 to about 10.0/10, projected with the scoring formula itself and assuming each lands exactly at 15.
  2. 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.

D2 · Cognitive Complexity6.5 / 10Adequate✓ Tool-verified

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.

Maturity: Documented → Verified → Prevented · effective 6.5 / 10 · rule-coverage 100% · ceiling Prevented

51 method(s) exceeded the cognitive complexity threshold of 15; the worst was ContextMenu.LoadContextMenus at 65.

ContextMenu.LoadContextMenus (cognitive 65)Plugins/Flow.Launcher.Plugin.Explorer/ContextMenu.cs:30
StringMatcher.FuzzyMatch (cognitive 56)Flow.Launcher.Infrastructure/StringMatcher.cs:61
Main.CreateResultsFromQuery (cognitive 53)Plugins/Flow.Launcher.Plugin.ProcessKiller/Main.cs:72
MainWindow.OnLoaded (cognitive 42)Flow.Launcher/MainWindow.xaml.cs:128
DialogJump.ForegroundChangeCallback (cognitive 42)Flow.Launcher.Infrastructure/DialogJump/DialogJump.cs:488

+ 46 more group(s) — more in Appendix A; the complete list is findings.md.

What to do

  1. Bring the 10 bodies over 30 down to 30 or less in Cognitive Complexity — start with ContextMenu.LoadContextMenus (cognitive 65), StringMatcher.FuzzyMatch (cognitive 56), Main.CreateResultsFromQuery (cognitive 53). — 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 10 together lifts Cognitive Complexity from 6.5 to about 7.3/10, projected with the scoring formula itself and assuming each lands exactly at 30; a cleaner split scores higher.
  2. 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.

D3 · God Classes8.4 / 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.

Maturity: Documented → Verified → Prevented · effective 8.4 / 10 · rule-coverage 100% · ceiling Prevented

25 god class(es) detected.

MethodTooLong: Main.Commands · ×7Plugins/Flow.Launcher.Plugin.Sys/Main.cs:312
TooManyMethods: MainViewModel · ×6Flow.Launcher/ViewModel/MainViewModel.cs
FileTooLong: ViewModel/MainViewModel.cs · ×6Flow.Launcher/ViewModel/MainViewModel.cs
ClassTooLong: ShellContextMenu · ×6Plugins/Flow.Launcher.Plugin.Explorer/Helper/ShellContextMenu.cs

What to do

  1. Resolve the 7 MethodTooLong finding(s) in God Classes — start with REDACTED, JsonRPCPluginSettings.cs, PluginsManager.cs. — One of this dimension's main actionable groups (7 warning-level).
  2. Resolve the 6 TooManyMethods finding(s) in God Classes — start with MainViewModel.cs, PublicAPIInstance.cs, MainWindow.xaml.cs. — One of this dimension's main actionable groups (6 warning-level).
  3. Resolve the 6 FileTooLong finding(s) in God Classes — start with MainViewModel.cs, ShellContextMenu.cs, MainWindow.xaml.cs. — One of this dimension's main actionable groups (6 warning-level).
  4. 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.

D4 · Code Duplication9.6 / 10Stronggated by 46 serious findings✓ Tool-verified

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.

Maturity: Documented → Verified → Prevented · effective 9.6 / 10 · rule-coverage 100% · ceiling Verified

44 duplicated block group(s) detected. A further 2 rows report members as variants of one another; they aggregate block groups already counted above and are not themselves counted.

Duplicated block (20 lines × 2) · ×3Plugins/Flow.Launcher.Plugin.Explorer/Views/PreviewPanel.xaml.cs:134
Duplicated block (5 lines × 2) · ×3Plugins/Flow.Launcher.Plugin.BrowserBookmark/ChromiumBookmarkLoader.cs:181
Duplicated block (18 lines × 2) · ×2Flow.Launcher.Plugin/SharedModels/MonitorInfo.cs:79
Duplicated block (15 lines × 2) · ×2Flow.Launcher.Core/Plugin/PluginManager.cs:863
Duplicated block (13 lines × 2) · ×2Plugins/Flow.Launcher.Plugin.Program/Views/ProgramSetting.xaml.cs:452

+ 29 more group(s) — more in Appendix A; the complete list is findings.md.

What to do

  1. Resolve the 3 Duplicated block (20 lines × 2) finding(s) in Code Duplication — start with PreviewPanel.xaml.cs (2), DialogJump.cs. — One of this dimension's main actionable groups (3 warning-level).
  2. Resolve the 3 Duplicated block (5 lines × 2) finding(s) in Code Duplication — start with ChromiumBookmarkLoader.cs, PluginInstaller.cs, SettingWindow.xaml.cs. — One of this dimension's main actionable groups (3 warning-level).
  3. Resolve the 2 Duplicated block (18 lines × 2) finding(s) in Code Duplication — start with MonitorInfo.cs, ProgramSetting.xaml.cs. — One of this dimension's main actionable groups (2 warning-level).
  4. 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.

D5 · Coupling10.0 / 10Exemplary✓ 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.

Maturity: Documented → Verified → Prevented · effective 10.0 / 10 · rule-coverage 100% · ceiling Prevented

17 projects, 0 dependency cycle(s), 0 unstable depended-on project(s).

✓ On the Gold path — maintain.

Detailed fixes: d5_recommendation.md.

D6 · Cohesion (LCOM4)9.6 / 10Stronggated by 3 serious findings✓ Tool-verified

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.

Maturity: Documented → Verified → Prevented · effective 9.6 / 10 · rule-coverage 100% · ceiling Verified

3 of 87 classes have LCOM4 above 3.

Low cohesion: ResultListBox (LCOM4 5) · ×3Flow.Launcher/ResultListBox.xaml.cs:11

What to do

  1. Resolve the 3 Low cohesion finding(s) in Cohesion (LCOM4) — start with ResultListBox.xaml.cs, ProgramSetting.xaml.cs, SettingsControl.xaml.cs. — One of this dimension's main actionable groups (3 warning-level).
  2. 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.

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.

Maturity: Documented → Verified → Prevented · effective 10.0 / 10 · rule-coverage 100% · ceiling Documented

154 test methods: 154 unit, 0 integration, 0 BDD, 0 e2e.

✓ On the Gold path — maintain.

Detailed fixes: d9_recommendation.md.

D10 · Test Quality10.0 / 10Stronggated by 1 serious finding✓ 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.

Maturity: Documented → Verified → Prevented · effective 10.0 / 10 · rule-coverage 100% · ceiling Prevented

0 skipped, 0 zero-assertion, 1 synchronised by a fixed sleep, 1 mock references across 154 tests.

Fixed-sleep synchronisation: JumpFolder_CancelsWhenHotkeyModifierRemainsHeldFlow.Launcher.Test/WindowsDialogTest.cs:160
Mock framework: Moq

What to do

  1. Resolve the 1 Fixed-sleep synchronisation finding(s) in Test Quality — start with WindowsDialogTest.cs. — One of this dimension's main actionable groups (1 warning-level).
  2. Enforce Test Quality in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.

Detailed fixes: d10_recommendation.md · top locations in Appendix A, every location in findings.md.

D12 · Dependency Hygiene8.4 / 10Strong✓ Tool-verified

What it measures: Whether dependencies are current, secure, and not bloated.

Method: Manifest scan via dotnet list package across all projects; worst-signal-per-package deduction (saturating for vulnerabilities, capped-linear for deprecation/outdated) per KLoC. Exhaustive, deterministic.

Maturity: Documented → Verified → Prevented · effective 8.4 / 10 · rule-coverage 100% · ceiling Verified

32 outdated, 0 vulnerable, 0 deprecated packages.

Deprecated: System.Reflection.Metadata · ×5Flow.Launcher/packages.lock.json:1230
Outdated: System.Drawing.CommonFlow.Launcher.Infrastructure/Flow.Launcher.Infrastructure.csproj:81
Outdated: AvalonEdit · ×31

What to do

  1. Resolve the 5 Deprecated finding(s) in Dependency Hygiene — start with packages.lock.json (5). — One of this dimension's main actionable groups (5 recommendation-level).
  2. Resolve the 1 Outdated finding(s) in Dependency Hygiene — start with Flow.Launcher.Infrastructure.csproj. — One of this dimension's main actionable groups (1 recommendation-level).
  3. Enforce Dependency Hygiene in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Verified — provenance only; does not change the score.

Detailed fixes: d12_recommendation.md · top locations in Appendix A, every location in findings.md.

D13 · REDACTED Scanning10.0 / 10Exemplary○ Nothing flagged

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.

Maturity: Documented → Verified → Prevented · effective 10.0 / 10 · rule-coverage 100% · ceiling Prevented

REDACTED scan ran and found no leaked secrets.

✓ On the Gold path — maintain.

Detailed fixes: d13_recommendation.md.

D14 · License Compliance10.0 / 10Exemplary○ Nothing flagged

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.

Maturity: Documented → Verified → Prevented · effective 10.0 / 10 · rule-coverage 100% · ceiling Verified

0 of 279 packages use a banned license. ★ DEPTH: this repository's MSBuild projects declare 52 direct `PackageReference`(s), and 198 further package(s) were reached beyond them by closing the graph over the committed `packages.lock.json` and 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.

✓ On the Gold path — maintain.

Detailed fixes: d14_recommendation.md.

D15 · Churn × Complexity Hotspots9.6 / 10Stronggated by 5 serious findings✓ Tool-verified

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.

Maturity: Documented → Verified → Prevented · effective 9.6 / 10 · rule-coverage 100% · ceiling Documented

Top hotspots: Flow.Launcher/MainWindow.xaml.cs (8×44=352); Flow.Launcher/ViewModel/MainViewModel.cs (13×24=312) Repeated repair below the complexity floor: Flow.Launcher/SettingPages/ViewModels/SettingsPanePluginsViewModel.cs (3 of 5 changes were fixes); Flow.Launcher.Infrastructure/Storage/JsonStorage.cs (3 of 4 changes were fixes); Flow.Launcher.Core/Plugin/PluginConfig.cs (3 of 3 changes were fixes)

Repeated repair: Flow.Launcher/SettingPages/ViewModels/SettingsPanePluginsViewModel.cs · ×3Flow.Launcher/SettingPages/ViewModels/SettingsPanePluginsViewModel.cs:264
Hotspot: Flow.Launcher/MainWindow.xaml.cs · ×2Flow.Launcher/MainWindow.xaml.cs:128

What to do

  1. Resolve the 3 Repeated repair finding(s) in Churn × Complexity Hotspots — start with SettingsPanePluginsViewModel.cs, JsonStorage.cs, PluginConfig.cs. — One of this dimension's main actionable groups (3 warning-level).
  2. Resolve the 2 Hotspot finding(s) in Churn × Complexity Hotspots — start with MainWindow.xaml.cs, MainViewModel.cs. — One of this dimension's main actionable groups (2 warning-level).

Detailed fixes: d15_recommendation.md · top locations in Appendix A, every location in findings.md.

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.

Maturity: Documented → Verified → Prevented · effective 8.4 / 10 · rule-coverage 100% · ceiling Documented

28 source file(s) have their living knowledge concentrated in one author (≥90% of recent, decayed contribution). The largest is Flow.Launcher.Core/Plugin/PluginManager.cs. Counted over 170 of the 361 production source files in this repository: 190 are under the ~2,400-byte size floor this dimension measures over, and the remaining 1 have no attributable history left to measure.

Off-boarding risk: anonymized user #1
Further sole-owners (lower concentration)

What to do

  1. Resolve the 1 Off-boarding risk finding(s) in Bus Factor. — One of this dimension's main actionable groups (1 recommendation-level).
  2. 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.

D17 · Explicit Debt7.7 / 10Adequategated by 30 critical findings✓ Tool-verified

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.

Maturity: Documented → Verified → Prevented · effective 7.7 / 10 · rule-coverage 100% · ceiling Prevented

86 deducted debt markers + unmeasured dead symbols across 47032 LoC in the .NET projects (1.1/KLoC) → score 7.7. Dead code not measured: the solution did not load cleanly, so the reference search was skipped.

EmptyCatchBlock · ×29Flow.Launcher.Core/Plugin/JsonRPCPluginV2.cs:119
NoWarnInCsproj repeated across 11 filesFlow.Launcher/Flow.Launcher.csproj:39
TodoComment · ×15Flow.Launcher.Core/Plugin/PluginConfig.cs:28
BarePragmaDisable · ×12Flow.Launcher.Core/Plugin/PluginsLoader.cs:6
ObsoleteWithCallers · ×3Flow.Launcher.Plugin/Interfaces/IPublicAPI.cs:309

+ 3 more group(s) — more in Appendix A; the complete list is findings.md.

What to do

  1. Resolve the 29 EmptyCatchBlock finding(s) in Explicit Debt — start with JsonRPCPluginV2.cs (4), Win32Helper.cs (4), WindowsExplorer.cs (3). — One of this dimension's main actionable groups (29 issue-level).
  2. Resolve the 1 NoWarnInCsproj repeated across 11 files finding(s) in Explicit Debt — start with Flow.Launcher.csproj. — One of this dimension's main actionable groups (1 issue-level).
  3. Resolve the 15 TodoComment finding(s) in Explicit Debt — start with REDACTED (5), PluginConfig.cs, PythonPlugin.cs. — One of this dimension's main actionable groups (15 warning-level).
  4. 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.

D18 · Solution Shape3.0 / 10Weak✓ Tool-verified

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.

Maturity: Documented → Verified → Prevented · effective 3.0 / 10 · rule-coverage 100% · ceiling Documented

17 projects, 390 source files, 51086 hand-written lines of code (47032 production / 4054 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 5685 generated (machine-written code — designer, scaffolded and tool-emitted files — excluded from quality), 28 inter-project edges (build failed).

Build failed

What to do

  1. Resolve the 1 Build failed finding(s) in Solution Shape. — One of this dimension's main actionable groups (1 warning-level).

Detailed fixes: d18_recommendation.md · top locations in Appendix A, every location in findings.md.

D19 · Documentation QualityAdequate◐ Sampled · advisory

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.

Maturity: Documented → Verified → Prevented · effective Adequate / 10 · rule-coverage 100% · ceiling Documented

The README is a polished marketing page with an official channels banner and a quick overview of what Flow Launcher does. It documents the repository root as a single-file README (the 'A quick file search and app launcher for Windows' header), but each subdirectory's README is written for that directory rather than the whole project, so the Flow.Launcher.Core/README.md and Plugins/*.README.md are internal-only per-project docs with no overview or usage. The visible content is clean and well-structured; the real gaps lie beneath the surface in the unshown outline.

XML-doc coverage: Flow.Launcher · ×16Flow.Launcher/Flow.Launcher.csproj

What to do

  1. Improve Documentation Quality — currently 6.0/10. — The README is a polished marketing page with an official channels banner and a quick overview of what Flow Launcher does. It documents the repository root as a single-file README (the 'A quick file search and app launcher for Windows' header), but each subdirectory's README is written for that directory rather than the whole project, so the Flow.Launcher.Core/README.md and Plugins/*.README.md are internal-only per-project docs with no overview or usage. The visible content is clean and well-structured; the real gaps lie beneath the surface in the unshown outline.

Detailed fixes: d19_recommendation.md · top locations in Appendix A, every location in findings.md.

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.

Maturity: Documented → Verified → Prevented · effective 0.0 / 10 · rule-coverage 100% · ceiling Documented

No architecture decision records were found.

No ADRs found

What to do

  1. Resolve the 1 No ADRs found finding(s) in ADR Quality. — One of this dimension's main actionable groups (1 recommendation-level).

Detailed fixes: d20_recommendation.md · top locations in Appendix A, every location in findings.md.

D21 · Naming ConsistencyExemplary◐ Sampled · 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.

Maturity: Documented → Verified → Prevented · effective Exemplary / 10 · rule-coverage 100% · ceiling Verified

0 naming inconsistencies across 200 sampled symbols.

✓ On the Gold path — maintain.

Detailed fixes: d21_recommendation.md.

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.

Maturity: Documented → Verified → Prevented · effective Exemplary / 10 · rule-coverage 100% · ceiling Documented

75 valuable / 0 redundant across 200 sampled comments.

✓ On the Gold path — maintain.

Detailed fixes: d24_recommendation.md.

D26 · Project Cohesion9.2 / 10Exemplary✓ Tool-verified

What it measures: Whether each project is a focused, coherent unit rather than an oversized grab-bag.

Method: Project size overshoot penalties (LoC / public-type count / namespace count, 2-of-3 flag) weighted by log magnitude. Exhaustive across projects, deterministic, LLM-independent.

Maturity: Documented → Verified → Prevented · effective 9.2 / 10 · rule-coverage 100% · ceiling Documented

1 of 17 projects flagged as possibly oversized/incoherent.

Projects may be oversized for their cohesion

✓ On the Gold path — maintain.

Detailed fixes: d26_recommendation.md · top locations in Appendix A, every location in findings.md.

D27 · Navigability8.8 / 10Strong✓ Tool-verified

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.

Maturity: Documented → Verified → Prevented · effective 8.8 / 10 · rule-coverage 100% · ceiling Documented

71 % of calls cross a namespace and 11 % go through an interface, but 98 % of collaborators are co-located — so a call's collaborators sit together and tracing stays easy. Baseline: medium — clean/modular boundaries expected.

Pass-through layerFlow.Launcher.Core/Plugin/JsonRPCV2Models/JsonRPCPublicAPI.cs:13

What to do

  1. Resolve the 1 Pass-through layer finding(s) in Navigability — start with JsonRPCPublicAPI.cs. — One of this dimension's main actionable groups (1 recommendation-level).

Detailed fixes: d27_recommendation.md · top locations in Appendix A, every location in findings.md.

D28 · Secrets (history)9.0 / 10Adequategated by 1 critical finding✓ Tool-verified

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.

Maturity: Documented → Verified → Prevented · effective 9.0 / 10 · rule-coverage 100% · ceiling Documented

1 finding(s): 0 critical, 1 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

  1. Resolve the 1 REDACTED finding(s) in Secrets (history) — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
  2. 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.

D29 · Static Analysis (SAST)0.1 / 10Critical✓ Tool-verified

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).

Maturity: Documented → Verified → Prevented · effective 0.1 / 10 · rule-coverage 100% · ceiling Documented

75 finding(s): 0 critical, 65 high, 10 medium, 0 low. 41 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 5 file(s) — `Flow.Launcher.Test/ThemePreviewTest.cs`, `Plugins/Flow.Launcher.Plugin.Calculator/ViewModels/SettingsViewModel.cs` (line 6), `Plugins/Flow.Launcher.Plugin.ProcessKiller/ProcessResult.cs` (lines 6–7, line 18), `Plugins/Flow.Launcher.Plugin.ProcessKiller/ViewModels/SettingsViewModel.cs` (lines 3–4, line 7), `Plugins/Flow.Launcher.Plugin.Sys/SettingsViewModel.cs` (lines 3–4, line 7) — 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 4 of those file(s) — `Plugins/Flow.Launcher.Plugin.Calculator/ViewModels/SettingsViewModel.cs`, `Plugins/Flow.Launcher.Plugin.ProcessKiller/ProcessResult.cs`, `Plugins/Flow.Launcher.Plugin.ProcessKiller/ViewModels/SettingsViewModel.cs`, `Plugins/Flow.Launcher.Plugin.Sys/SettingsViewModel.cs` — 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 1 of those file(s) — `Flow.Launcher.Test/ThemePreviewTest.cs` — 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 2 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

+ 5 more group(s) — more in Appendix A; the complete list is findings.md.

What to do

  1. Resolve the 15 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (12), REDACTED, REDACTED. — One of this dimension's main actionable groups (15 issue-level).
  2. Resolve the 3 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (3). — One of this dimension's main actionable groups (3 issue-level).
  3. No action in Static Analysis (SAST) — all 41 REDACTED finding(s) are reported here at file:line but scored by D36 (supply-chain provenance), so none is charged to this dimension. — One of this dimension's main actionable groups (41 issue-level, 0 of them charged here).

Detailed fixes: d29_recommendation.md · top locations in Appendix A, every location in findings.md.

D34 · Knowledge Freshness9.6 / 10Exemplary✓ Tool-verified

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.

Maturity: Documented → Verified → Prevented · effective 9.6 / 10 · rule-coverage 100% · ceiling Documented

8 of 171 significant source file(s) are orphaned — their living knowledge has decayed to nothing, so no one currently understands them. The largest is Plugins/Flow.Launcher.Plugin.Explorer/Helper/ShellContextMenuDisplayHelper.cs. Counted over 171 of the 361 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.

Orphaned file · ×8Plugins/Flow.Launcher.Plugin.Explorer/Helper/ShellContextMenuDisplayHelper.cs:1
Orphaned files with no living knowledge

✓ On the Gold path — maintain.

Detailed fixes: d34_recommendation.md · top locations in Appendix A, every location in findings.md.

D35 · Change Coupling9.8 / 10Stronggated by 5 serious findings✓ Tool-verified

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.

Maturity: Documented → Verified → Prevented · effective 9.8 / 10 · rule-coverage 100% · ceiling Documented

Strongest change-coupling: EverythingSearchManager.cs↔WindowsIndexSearchManager.cs 69%; SearchManager.cs↔WindowsIndexSearchManager.cs 62%; TypeScriptEnvironment.cs↔Updater.cs 60%

Change coupling: EverythingSearchManager.cs ↔ WindowsIndexSearchManager.cs · ×5Plugins/Flow.Launcher.Plugin.Explorer/Search/Everything/EverythingSearchManager.cs:1

What to do

  1. Resolve the 5 Change coupling finding(s) in Change Coupling — start with EverythingSearchManager.cs, SearchManager.cs, TypeScriptEnvironment.cs. — One of this dimension's main actionable groups (5 warning-level).

Detailed fixes: d35_recommendation.md · top locations in Appendix A, every location in findings.md.

D36 · Supply-chain Provenance & Signing0.0 / 10Critical✓ Tool-verified

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.

Maturity: Documented → Verified → Prevented · effective 0.0 / 10 · rule-coverage 100% · ceiling Documented

0/4 supply-chain integrity signals present (provenance, signing, SBOM, pinned actions).

REDACTED
REDACTED
REDACTED
REDACTED
REDACTED

+ 4 more group(s) — more in Appendix A; the complete list is findings.md.

What to do

  1. Resolve the 4 REDACTED finding(s) in Supply-chain Provenance & Signing — start with REDACTED, REDACTED, REDACTED. — One of this dimension's main actionable groups (4 warning-level).
  2. Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 warning-level).
  3. 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.

D43 · Malicious Dependencies10.0 / 10Exemplary✓ Tool-verified

What it measures: Whether any dependency the repository declares is published as MALICIOUS rather than merely vulnerable — a package that is an attacker's work, in any ecosystem osv-scanner reads. Scored apart from D30 because the answer is binary: there is no safe version to upgrade to, and the fix is to remove the package and rotate every credential it could have read.

Method: The same dependency scan D30 reads, partitioned on the scanner's own classification rather than rescanned: a row is MALICIOUS when its id is in the `MAL-` space (the ossf/malicious-packages feed) OR its `database_specific.cwe_ids` carries `CWE-506` ("Embedded Malicious Code"). Both channels are structural; the summary text is deliberately NOT read, because a malicious-package record whose summary says only "Critical severity vulnerability" is a real shape ([GHSA redacted]) and a text matcher misses it. Scored BINARY: any surviving row is 0, whatever its severity and however many CVEs sit beside it — a hostile dependency is not a quantity. Applicability and degradation are D30's: NotApplicable only when no ecosystem is readable, and an unscannable ecosystem degrades rather than reading clean. SCORED, not informational.

Maturity: Documented → Verified → Prevented · effective 10.0 / 10 · rule-coverage 100% · ceiling Documented

No dependency in any ecosystem this repository declares is published as malicious.

✓ On the Gold path — maintain.

Detailed fixes: d43_recommendation.md.

Frontend & cross-cutting dimensions

R = React/JS · M = Maturity · P = Readiness.

AX1 · Captive dependencies10.0 / 10Exemplary✓ Tool-verified

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.

AX10 · Code composition8.5 / 10Strong✓ Tool-verified

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.
AX2 · Stateful singletons2.8 / 10Weak✓ Tool-verified

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.

  • `SettingWindowViewModel` is a singleton (one shared instance) but mutates instance state outside any lock (_pageType; e.g. `_pageType` at line 20). — Flow.Launcher/ViewModel/SettingWindowViewModel.cs:7
  • `WelcomeViewModel` is a singleton (one shared instance) but mutates instance state outside any lock (_pageNum, _backEnabled, _nextEnabled; e.g. `_pageNum` at line 19). — Flow.Launcher/ViewModel/WelcomeViewModel.cs:5
  • `MainViewModel` is a singleton (one shared instance) but mutates instance state outside any lock (lastHistoryIndex, _selectionBeforeContextMenu, GameModeStatus, _queryText, QueryTextCursorMovedToEnd, _selectedResults; e.g. `lastHistoryIndex` at line 387). — Flow.Launcher/ViewModel/MainViewModel.cs:33
  • `Theme` is a singleton (one shared instance) but mutates instance state outside any lock (_oldResource, _oldTheme, BlurEnabled, _themeResizeBorderThickness; e.g. `_oldResource` at line 116). — Flow.Launcher.Core/Resource/Theme.cs:23
  • `PublicAPIInstance` is a singleton (one shared instance) but mutates instance state outside any lock (_theme, _updater, _globalKeyboardHandlers; e.g. `_theme` at line 50). — Flow.Launcher/PublicAPIInstance.cs:41
  • `Internationalization` is a singleton (one shared instance) but mutates instance state outside any lock (_languageDirectories, _oldResources; e.g. `_languageDirectories` at line 107). — Flow.Launcher.Core/Resource/Internationalization.cs:16
  • `Settings` is a singleton (one shared instance) but mutates instance state outside any lock (_storage, _stringMatcher, _openResultModifiers, _showOpenResultHotkey, _language, _theme; e.g. `_storage` at line 27). — Flow.Launcher.Infrastructure/UserSettings/Settings.cs:18

What to do

  • Keep singletons stateless or back their state with thread-safe types (Concurrent*/Immutable*); otherwise concurrent callers race.
AX3 · Project dependency cycles10.0 / 10Exemplary✓ Tool-verified

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 Flow.Launcher.Infrastructure ↔ Flow.Launcher.Infrastructure.UserSettings depend on each other. The lightest dependency in the cycle is Flow.Launcher.Infrastructure.UserSettings → Flow.Launcher.Infrastructure (Flow.Launcher.Infrastructure.UserSettings.Settings → Flow.Launcher.Infrastructure.StringMatcher, 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. — Flow.Launcher.Infrastructure/UserSettings/Settings.cs:18
  • The namespaces Flow.Launcher.Plugin.Calculator ↔ Flow.Launcher.Plugin.Calculator.ViewModels depend on each other. The lightest dependency in the cycle is Flow.Launcher.Plugin.Calculator → Flow.Launcher.Plugin.Calculator.ViewModels (Flow.Launcher.Plugin.Calculator.Main → Flow.Launcher.Plugin.Calculator.ViewModels.SettingsViewModel, 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. — Plugins/Flow.Launcher.Plugin.Calculator/Main.cs:8
  • The namespaces Flow.Launcher.Plugin.Explorer ↔ Flow.Launcher.Plugin.Explorer.Search ↔ Flow.Launcher.Plugin.Explorer.Search.Everything ↔ Flow.Launcher.Plugin.Explorer.Search.IProvider ↔ Flow.Launcher.Plugin.Explorer.Search.QuickAccessLinks ↔ Flow.Launcher.Plugin.Explorer.Search.WindowsIndex ↔ Flow.Launcher.Plugin.Explorer.ViewModels depend on each other. The lightest dependency in the cycle is Flow.Launcher.Plugin.Explorer → Flow.Launcher.Plugin.Explorer.Search.QuickAccessLinks (Flow.Launcher.Plugin.Explorer.Settings → Flow.Launcher.Plugin.Explorer.Search.QuickAccessLinks.AccessLink, 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. — Plugins/Flow.Launcher.Plugin.Explorer/Settings.cs:9
  • The namespaces Flow.Launcher.Plugin.PluginsManager ↔ Flow.Launcher.Plugin.PluginsManager.ViewModels depend on each other. The lightest dependency in the cycle is Flow.Launcher.Plugin.PluginsManager → Flow.Launcher.Plugin.PluginsManager.ViewModels (Flow.Launcher.Plugin.PluginsManager.Main → Flow.Launcher.Plugin.PluginsManager.ViewModels.SettingsViewModel, 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. — Plugins/Flow.Launcher.Plugin.PluginsManager/Main.cs:6
  • The namespaces Flow.Launcher.Plugin.ProcessKiller ↔ Flow.Launcher.Plugin.ProcessKiller.ViewModels depend on each other. The lightest dependency in the cycle is Flow.Launcher.Plugin.ProcessKiller → Flow.Launcher.Plugin.ProcessKiller.ViewModels (Flow.Launcher.Plugin.ProcessKiller.Main → Flow.Launcher.Plugin.ProcessKiller.ViewModels.SettingsViewModel, 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. — Plugins/Flow.Launcher.Plugin.ProcessKiller/Main.cs:5
  • The namespaces Flow.Launcher.Plugin.Program ↔ Flow.Launcher.Plugin.Program.Programs ↔ Flow.Launcher.Plugin.Program.ViewModels ↔ Flow.Launcher.Plugin.Program.Views.Models depend on each other. The lightest dependency in the cycle is Flow.Launcher.Plugin.Program → Flow.Launcher.Plugin.Program.ViewModels (Flow.Launcher.Plugin.Program.AddProgramSource → Flow.Launcher.Plugin.Program.ViewModels.AddProgramSourceViewModel, 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. — Plugins/Flow.Launcher.Plugin.Program/AddProgramSource.xaml.cs:2

What to do

  • Break namespace cycles inside a project by moving the shared type to a namespace both sides can use, or by inverting the back edge behind an interface.
AX4 · Dependency direction10.0 / 10Exemplary✓ Tool-verified

Other · Architecture — Whether dependencies point inward (Domain ← Application ← Infrastructure/Web) — the clean-architecture dependency rule, checked across the project graph.

Method: Layer violations by name-segment inference (Domain/Core to Application to Infrastructure/Web) over the project-reference graph. Exhaustive over all projects, deterministic.

AX5 · Architecture & structure10.0 / 10Exemplary✓ Tool-verified

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.

AX6 · Interface segregation9.9 / 10Exemplary✓ Tool-verified

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.

  • `IPublicAPI` declares 78 members: `ChangeQuery`, `RestartApp`, `ShellRun`, `CopyToClipboard`, `SaveAppAllSettings`, `SavePluginSettings`, `ReloadAllPluginData`, `CheckForNewUpdate`, `ShowMsgError`, `ShowMsgErrorWithButton`, `ShowMainWindow`, `FocusQueryTextBox`, `HideMainWindow`, `IsMainWindowVisible`, `VisibilityChanged`, `ShowMsg`, `ShowMsg`, `ShowMsgWithButton`, `ShowMsgWithButton`, `OpenSettingDialog`, `OpenPluginSettingsWindow`, `GetTranslation`, `GetAllPlugins`, `GetAllInitializedPlugins`, `RegisterGlobalKeyboardCallback`, `RemoveGlobalKeyboardCallback`, `FuzzySearch`, `HttpGetStringAsync`, `HttpGetStreamAsync`, `HttpDownloadAsync`, `AddActionKeyword`, `RemoveActionKeyword`, `ActionKeywordAssigned`, `LogDebug`, `LogInfo`, `LogWarn`, `LogError`, `LogException`, `LoadSettingJsonStorage`, `SaveSettingJsonStorage`, and 38 more. Counted as the author wrote them — a property is ONE member and its get/set accessors are not counted separately, and an event counts once. Those 78 declarations carry 73 distinct name(s), so part of the width is overloading rather than separate responsibilities — but 73 operations clears the >15 bar on its own, so the row is about responsibilities, not signatures. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces. — Flow.Launcher.Plugin/Interfaces/IPublicAPI.cs:18

What to do

  • Split fat interfaces into focused role-interfaces so clients depend only on what they use.
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.

C1 · Data Protection0.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.
GD1 · Unfinished & placeholder code9.9 / 10Exemplary✓ Tool-verified

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. (×8) — Flow.Launcher/Converters/BoolToIMEConversionModeConverter.cs:19, Flow.Launcher/Converters/BoolToIMEConversionModeConverter.cs:36, Flow.Launcher/Converters/CornerRadiusFilterConverter.cs:64, …

What to do

  • Finish or delete NotImplementedException stubs and replace placeholder literals before shipping.
IC1 · Incompleteness & stubs9.0 / 10Strong✓ Tool-verified

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.

  • Control only reaches here when `token.IsCancellationRequested` is false, because the guard on line 227 exits otherwise. This test is therefore always false and everything it guards is unreachable. Implement the distinction that was intended, or delete the test. — Plugins/Flow.Launcher.Plugin.Explorer/Search/SearchManager.cs:249
  • A line of code has been commented out rather than removed — dead weight that rots and confuses. Delete it (version control remembers). (×30) — Flow.Launcher/Helper/ErrorReporting.cs:49, Flow.Launcher/Resources/Controls/HotkeyDisplay.xaml.cs:18, Flow.Launcher/Settings.cs:15, …
  • 7 consecutive lines of code sit inside a `/* … */` block — a block of code switched off rather than removed, which rots and confuses. Delete it (version control remembers). — Flow.Launcher/ViewModel/MainViewModel.cs:1621

What to do

  • Clear the softer debt: remove commented-out code and dead branches, re-enable or delete skipped tests, and replace blanket warning suppressions with targeted ones.
M1 · Documentation (README)7.1 / 10Strong✓ Tool-verified

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 13 of 17 project(s) that lack one — worth up to 1.5 pts.
M2 · Architecture documentation0.0 / 10Critical✓ Tool-verified

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.
  • No C4/Structurizr/PlantUML/Mermaid/Graphviz/D2 diagram, no drawn diagram named for the architecture, no file named `architecture` or `design` in any markup this check reads, and nothing in the README, docs or contributor guides that announces the shape — no `## Architecture` heading, no "architecture overview"/"high-level design" phrasing, no "the architecture is …" introduction, no guided code tour. A shape laid out in prose that never names itself as the architecture is not visible to this check, and neither is one kept outside the repository, so this row reports the absence of a re-findable shape document — not evidence that nobody wrote the shape down.

What to do

  • Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them.
  • Add a C4 context/container diagram (Structurizr, PlantUML or Mermaid) or an architecture.md overview.
M3 · Folder & project structure8.0 / 10Strong✓ Tool-verified

Maturity · Maturity — Whether the repo is organised deliberately — src/test separation and consistent project naming.

Method: Filesystem scan: src/test folder separation and namespace-prefix consistency (majority RootNamespace agreement). Exhaustive across projects, deterministic.

  • Production code isn't grouped under a src/ folder — it's spread across several top-level directories, so there's no one place that says 'this is the product'.

What to do

  • Group production code under src/ (or split deliberately, e.g. backend/ + frontend/) so production and tooling code aren't mixed at the root.
M4 · Documentation accuracy10.0 / 10Exemplary◐ Sampled · advisory

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.

P1 · CI/CD gates10.0 / 10Exemplary○ Nothing flagged

Readiness · Readiness — Whether an automated pipeline builds and tests every change.

Method: Filesystem scan: CI workflow files (.github/workflows, .gitlab-ci.yml, etc.) for build and test stages. Exhaustive, deterministic.

P10 · Library API & versioning10.0 / 10Exemplary○ Nothing flagged

Readiness · Readiness — For a library: a deliberate (small) public API surface and explicit semantic versioning so consumers can depend on it safely.

Method: Roslyn scan: public API surface area and semantic-versioning markers (SemVer attributes, changelog entries) for libraries; off .NET, a library is the ecosystem's publication act (an npm package that is not private and names an entry point, a PyPI distribution with a build system, a Rust library crate, a Maven/Gradle module that publishes, a Go module with no package main, a gemspec, a Composer library, a SwiftPM library product, a pub.dev or Hex package), its surface is the share of types the language model records as public (Rust, Swift, Java, Kotlin, Go, Dart; not measured where the model records no type visibility or, as in TypeScript, only module-level export), and its version is read from the manifest, a semver CHANGELOG, release tooling or semver git tags. Exhaustive, deterministic.

P3 · Security & performance tooling3.0 / 10Weak✓ Tool-verified

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.

  • No static application security testing detected. For this repository's stack, add CodeQL's csharp pack, or a .NET security analyzer package (or `semgrep --config=auto`, which runs on any language) as a CI step. What was searched, so you can tell an absence from a miss: the 26744 CI workflow file(s) in this repository, and the scanner and linter configuration checked in beside them. A scan that runs outside CI, one configured in your forge's web UI rather than in a committed file, or a tool whose name is none of those this check carries, is not seen — if that is your case the row is wrong, and saying so is more useful than adding a second scanner.

What to do

  • Add a SAST step to CI running what this repository's stack ships: CodeQL's csharp pack, or a .NET security analyzer package — or `semgrep --config=auto`, which runs on any language — so a security regression fails the build instead of landing.
  • Add gitleaks/trufflehog in CI to block PRs that introduce committed secrets.
P4 · Deployment & Rollback7.0 / 10Strong✓ Tool-verified

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.

P6 · Release Hygiene5.0 / 10Adequate✓ Tool-verified

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.
PF1 · Benchmark discipline6.0 / 10Adequate✓ Tool-verified

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).
PF2 · Allocation hygiene6.6 / 10Adequate✓ Tool-verified

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 66 use(s) across 53,023 production line(s) (~1.2/1k). More Span/Memory, pooling (ArrayPool/ObjectPool), stackalloc and ValueTask on the allocation-heavy paths climbs this toward 10.
PF3 · Async & latency hygiene10.0 / 10Exemplary✓ Tool-verified

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.

S1 · Cryptographic Hygiene8.0 / 10Strong✓ Tool-verified

Other · Security — Cryptographic hygiene (weak hash/cipher, password key-derivation). This codebase has no web surface, so transport/header/cookie/CSRF controls are N/A and only crypto is scored. Outbound TLS (certificate validation, protocol version) is scored wherever it appears — a client verifies its peer whether or not it serves anything itself.

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.

  • `SecurityProtocol` explicitly selects `SecurityProtocolType.Tls`, a protocol version that is broken (SSL 2.0/3.0) or withdrawn (TLS 1.0/1.1, RFC 8996). Offering an obsolete version does not merely permit it — it is what a downgrade attack negotiates, so the weakest version on the list is the one that decides the connection's strength. Stop pinning versions here: leave the protocol unset (`SecurityProtocolType.SystemDefault`, or simply do not assign it) so the connection uses the OS policy and picks up TLS 1.3 and future versions without a code change. Where a version must be named explicitly, name `Tls12` and `Tls13` only. — REDACTED:25

What to do

  • Drop SSL 2.0/3.0 and TLS 1.0/1.1 from the enabled protocol list — prefer leaving it to the OS default (`SystemDefault`) so new versions are picked up automatically, or name `Tls12`/`Tls13` explicitly if it must be pinned.
X1 · Async correctness5.5 / 10Adequate✓ Tool-verified

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. (×20) — Flow.Launcher/App.xaml.cs:181, Flow.Launcher/MainWindow.xaml.cs:394, Flow.Launcher/MainWindow.xaml.cs:438, …

What to do

  • async void method: OnStartup
X12 · Unreachable branch10.0 / 10Exemplary○ Nothing flagged

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.

X13 · Undrained process stream10.0 / 10Exemplary○ Nothing flagged

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.

X14 · Bypassable address classification10.0 / 10Exemplary○ Nothing flagged

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.

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.

X16 · Unfloored truncation loop10.0 / 10Exemplary○ Nothing flagged

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.

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.

X18 · Disposal-pattern correctness5.5 / 10Adequate✓ Tool-verified

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.

  • `_inner` is never created by `ThemedHighlighter` — every assignment to it takes a constructor parameter — yet this type disposes it here (line 434). Its declared type `IHighlighter` is an interface, so the instance came from whoever resolved it, and that owner decides when it ends. Disposing it from here reaches outside this object's lifetime: a dependency shared with the rest of the process is torn down when THIS instance goes away, and the real owner's later `Dispose()` runs a second time on an object already disposed. Drop the call — a type disposes what it constructed, and only that. If this dependency genuinely is exclusive to this instance, construct it here (or take an owned factory) so the ownership is stated in the code rather than assumed. — Flow.Launcher/Resources/Controls/PreviewMarkdownScrollViewer.cs:434
  • `timer` is a `PeriodicTimer`, which implements `IDisposable`, and it is created here (line 320). Every use of it in `RegisterClockAndDateUpdateAsync` 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 timer = …;`), which releases it at the end of the scope on every path including a throw. — Flow.Launcher/ViewModel/MainViewModel.cs:320
  • `process` is a `Process`, which implements `IDisposable`, and it is created here (line 79). Every use of it in `IsFileManagerValid` 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. — Flow.Launcher/ViewModel/SelectFileManagerViewModel.cs:79
  • `converter` is a `FileSvgReader`, which implements `IDisposable`, and it is created here (line 511). Every use of it in `LoadSvgImage` 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 converter = …;`), which releases it at the end of the scope on every path including a throw. — Flow.Launcher.Infrastructure/Image/ImageLoader.cs:511

What to do

  • Each finding names the value and the span that decides who owns it — the `new` that created it, or the constructor parameter that handed it over. Confirm ownership from that span, then make the disposal match it: release what this type created, leave what it was injected with to whoever created THAT, and drop a finalizer whose type holds nothing unmanaged to release.
X19 · Unrestored process-global state10.0 / 10Exemplary○ Nothing flagged

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.

X2 · Cancellation propagation5.5 / 10Adequate✓ Tool-verified

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 47/185 async methods accept a CancellationToken, so in-flight work can't be stopped early when the caller gives up — whatever ends it in your host (shutdown signal, timeout, abandoned request, user cancel). Thread a token through the call chain and honour it at each await and loop; where a method genuinely cannot be interrupted, omitting it is a deliberate choice — judge against your hosting model.
  • No CancellationToken parameter — this work can't be stopped early once started. (×38) — Flow.Launcher/App.xaml.cs:181, Flow.Launcher/Helper/ResultHelper.cs:14, Flow.Launcher/Helper/ResultHelper.cs:19, …
  • 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. — Flow.Launcher/SettingPages/ViewModels/SettingsPaneAboutViewModel.cs:107

What to do

  • Thread a CancellationToken through async methods so work stops promptly on cancellation.
X20 · Mistyped argument guard10.0 / 10Exemplary○ Nothing flagged

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.

X21 · Side-effecting pattern guard10.0 / 10Exemplary○ Nothing flagged

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.

X22 · Contradicted release guard10.0 / 10Exemplary○ Nothing flagged

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.

X23 · Unguarded diagnostic materialisation7.0 / 10Strong✓ Tool-verified

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.

  • `LogDebug` at line 1618 is called with an argument built by `string.Join(" ", plugins.Select(x => $"<{x.Metadata.Name}>"))` (line 1618), whose cost grows with the collection it walks. C# evaluates a call's arguments BEFORE entering the method, so that join/projection runs in full every time this line is reached — and then the level check inside the logger discards the string it produced, because LogDebug is a level a shipped configuration normally leaves off. Nothing here decides beforehand whether the message is wanted: no `IsEnabled` test, no debug flag, no conditional-compilation region. — Flow.Launcher/ViewModel/MainViewModel.cs:1618

What to do

  • Each finding names the diagnostic call and the expression inside its argument whose cost scales with a collection. Confirm from the two that the argument is built before the call — that is C#'s evaluation order, not a guess — then put the construction behind the same level check the sink applies: `if (logger.IsEnabled(LogLevel.Trace))` for Microsoft.Extensions.Logging, the repository's own debug flag where it has one, or a message template whose ARGUMENTS the logging framework only formats when the level is on. Moving the call is not the fix: it is the join/projection in the argument that is paid, wherever the call sits.
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.

X25 · Inert configuration knob10.0 / 10Exemplary○ Nothing flagged

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.

X26 · Unsynchronised callback handoff10.0 / 10Exemplary○ Nothing flagged

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.

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.

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.

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.

X3 · Exception handling5.6 / 10Adequate✓ Tool-verified

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. (×27) — Flow.Launcher/Helper/HotKeyMapper.cs:160, Flow.Launcher/MainWindow.xaml.cs:416, Flow.Launcher/ReportWindow.xaml.cs:51, …
  • `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. (×4) — Flow.Launcher.Plugin/SharedCommands/FilesFolders.cs:189, Flow.Launcher.Plugin/SharedCommands/FilesFolders.cs:216, Flow.Launcher.Plugin/SharedCommands/FilesFolders.cs:235, …
  • An empty catch block silently discards the error — failures vanish with no log and no rethrow. On a teardown path letting it propagate is not an option (throwing out of `Dispose()` masks the failure already in flight and abandons the rest of the cleanup), so make the swallow deliberate instead: record it through whatever this codebase already uses to report problems — or, if one specific failure truly cannot matter, catch exactly that exception type and say why in a comment on the catch (a comment on a catch-all still swallows everything else). (×2) — Flow.Launcher.Core/Plugin/JsonRPCPluginV2.cs:139, Flow.Launcher.Core/Plugin/JsonRPCPluginV2.cs:143
  • `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. — Flow.Launcher.Core/Resource/Theme.cs:914

What to do

  • Swallowed exception (empty catch)
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.

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.

X4 · Structured logging5.6 / 10Adequate✓ Tool-verified

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. (×17) — Plugins/Flow.Launcher.Plugin.Program/Programs/ShellLinkReader.cs:36, Plugins/Flow.Launcher.Plugin.Program/Programs/ShellLinkReader.cs:70, Plugins/Flow.Launcher.Plugin.Program/Programs/ShellLinkReader.cs:105, …

What to do

  • Interpolated log message defeats structured logging
X5 · Nullable reference types2.4 / 10Critical✓ Tool-verified

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 `windowStyle`: line 322 assigns it with `as Style`, which hands back null rather than throwing when the value is not a `Style`, but line 324 then dereferences it directly as `windowStyle.Setters` with no null test between them and no guard around it. If the `as` is right, that dereference throws NullReferenceException on the input it was written for — and the NullReferenceException names neither the cast nor the type that failed. Settle it one way — test `windowStyle` once before the first use and handle the null case, or cast with `(Style)` so the failure is reported where it happens — rather than leaving the two readings side by side. — Flow.Launcher.Core/Resource/Theme.cs:324
  • This method contradicts itself about `match`: line 96 writes `match?.IsSearchPrecisionScoreMet`, which says `match` can be null, but line 94 then dereferences it directly as `match.Score` 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 `match` truly cannot be null here, the `?.` is misleading. Settle it one way — test `match` once before the first use and handle the null case, or drop the `?.` — rather than leaving the two readings side by side. — Plugins/Flow.Launcher.Plugin.Program/Programs/Win32.cs:94
  • This method contradicts itself about `listView`: line 449 assigns it with `as ListView`, which hands back null rather than throwing when the value is not a `ListView`, but line 450 then dereferences it directly as `listView.View` with no null test between them and no guard around it. If the `as` is right, that dereference throws NullReferenceException on the input it was written for — and the NullReferenceException names neither the cast nor the type that failed. Settle it one way — test `listView` once before the first use and handle the null case, or cast with `(ListView)` so the failure is reported where it happens — rather than leaving the two readings side by side. — Plugins/Flow.Launcher.Plugin.Program/Views/ProgramSetting.xaml.cs:450
  • This method contradicts itself about `gView`: line 450 assigns it with `as GridView`, which hands back null rather than throwing when the value is not a `GridView`, but line 461 then dereferences it directly as `gView.Columns` with no null test between them and no guard around it. If the `as` is right, that dereference throws NullReferenceException on the input it was written for — and the NullReferenceException names neither the cast nor the type that failed. Settle it one way — test `gView` once before the first use and handle the null case, or cast with `(GridView)` so the failure is reported where it happens — rather than leaving the two readings side by side. — Plugins/Flow.Launcher.Plugin.Program/Views/ProgramSetting.xaml.cs:461
  • This method contradicts itself about `listView`: line 150 assigns it with `as ListView`, which hands back null rather than throwing when the value is not a `ListView`, but line 151 then dereferences it directly as `listView.View` with no null test between them and no guard around it. If the `as` is right, that dereference throws NullReferenceException on the input it was written for — and the NullReferenceException names neither the cast nor the type that failed. Settle it one way — test `listView` once before the first use and handle the null case, or cast with `(ListView)` so the failure is reported where it happens — rather than leaving the two readings side by side. — Plugins/Flow.Launcher.Plugin.WebSearch/SettingsControl.xaml.cs:151
  • This method contradicts itself about `gView`: line 151 assigns it with `as GridView`, which hands back null rather than throwing when the value is not a `GridView`, but line 164 then dereferences it directly as `gView.Columns` with no null test between them and no guard around it. If the `as` is right, that dereference throws NullReferenceException on the input it was written for — and the NullReferenceException names neither the cast nor the type that failed. Settle it one way — test `gView` once before the first use and handle the null case, or cast with `(GridView)` so the failure is reported where it happens — rather than leaving the two readings side by side. — Plugins/Flow.Launcher.Plugin.WebSearch/SettingsControl.xaml.cs:164
  • This method contradicts itself about `listView`: line 20 assigns it with `as ListView`, which hands back null rather than throwing when the value is not a `ListView`, but line 21 then dereferences it directly as `listView.View` with no null test between them and no guard around it. If the `as` is right, that dereference throws NullReferenceException on the input it was written for — and the NullReferenceException names neither the cast nor the type that failed. Settle it one way — test `listView` once before the first use and handle the null case, or cast with `(ListView)` so the failure is reported where it happens — rather than leaving the two readings side by side. — Plugins/Flow.Launcher.Plugin.Sys/SysSettings.xaml.cs:21
  • This method contradicts itself about `gView`: line 21 assigns it with `as GridView`, which hands back null rather than throwing when the value is not a `GridView`, but line 32 then dereferences it directly as `gView.Columns` with no null test between them and no guard around it. If the `as` is right, that dereference throws NullReferenceException on the input it was written for — and the NullReferenceException names neither the cast nor the type that failed. Settle it one way — test `gView` once before the first use and handle the null case, or cast with `(GridView)` so the failure is reported where it happens — rather than leaving the two readings side by side. — Plugins/Flow.Launcher.Plugin.Sys/SysSettings.xaml.cs:32
  • 1/16 NRT-eligible project(s) enable <Nullable>enable</Nullable> (projects targeting a pre-C#-8 framework are excluded — NRTs aren't available there). NRTs catch a whole class of null-deref bugs at compile time.
  • ~0.5 `!` suppressions per 1k syntax nodes — 20 suppression(s) across the 42528 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 `!`.

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.

LensScoreRatingImpact
Code Health50%Adequate — gated by D18, X5Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Architecture76%Adequate — gated by AX2Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Maturity50%Adequate — gated by M2Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Readiness64%Adequate — gated by P3Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Security35%Weak — gated by D29, D36, C1Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Performance72%StrongStrongest area.
Unscored — 2 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.

  • X10 Duplicated predicate — 14 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
  • X7 Silent fallback defaults — 11 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
Not evidenced — 4 control(s) we could not find positive evidence for

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.
  • C4 Data Retention — Repo shows no data-retention / TTL / cleanup mechanism for personal data — absence of evidence is not evidence of a working control. Define retention periods and a purge/cleanup job (or TTL) in code, or document where retention is enforced, 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.
  • P5 DR & Backup — not evidenced — repo shows no backup/RTO/RPO controls; absence of evidence is not evidence of a working control
Not included — 39 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.
  • 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.
  • C2 Access Controls — No access-control surface detected in the analyzed source — no web/app surface to authorize (no HTTP API or web-UI project) and no authorization code at all (no [Authorize]/policies, no imperative guard methods). Access control is therefore N/A here — this is a library/CLI, which is authorized by its CALLER, not by itself. If this codebase grows request handlers, the dimension reactivates and a default-deny posture is expected then.
  • D11 Test Reliability — Test reliability not measured — no test run produced results
  • 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: `dotnet list package --vulnerable` could not read this solution's dependency graph — it reported an error for at least one project and returned no package data at all (typically a packages.config / non-PackageReference project, which the command cannot read). An unreadable dependency graph is not a clean one; migrate the project(s) to PackageReference to enable this 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) — 4 file(s) were not parsed by semgrep — the PII/GDPR ruleset never ran over them
  • D37 Vulnerability-disclosure Policy — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed.
  • 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.
  • D44 Platform End-of-Life — Platform end-of-life not assessed — this repository declares no platform this pass reads
  • D7 Architectural Integrity — no checkable ADRs and no dependency cycles — architectural integrity not assessed
  • D8 Code Coverage — Coverage NOT MEASURED: `--collect:"XPlat Code Coverage"` names a data collector that ships in the `coverlet.collector` package, and this repository wires up none — no test project references it and no runsettings declares one. The absence of coverage here is therefore not evidence about the suite or about our analyzer environment: without a collector, `--collect` produces nothing even from a suite that builds and passes. Add a `coverlet.collector` PackageReference to the test project(s) (or commit the Cobertura/OpenCover/lcov report your CI produces) and real coverage will be measured. It is excluded from the score rather than counted as a near-zero defect.
  • DM1 Domain Modelling — not scored — this repository shows only 1 of the 3 signals this lens looks for (3 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
  • P12 CI test-gate honesty — Reported, not scored — and nothing was matched here. The coverage check applies to any stack, and the automatic-re-run check to any GitHub-Actions workflow, but the checks for excluded tests, skipped tests and sleep-based synchronisation currently recognise only some ecosystems' test-runner idioms, so on a repository built with another stack the zeros below mean 'not checked', not 'clean'.
  • P2 Observability — This repo is a library, not a deployed service — it has no process to operate, so production observability (structured logging, tracing/metrics, health checks) is N/A. A library may log via an injected ILogger, but the absence of operational telemetry is not a defect here. If it grows a host (web API, worker), the dimension reactivates.
  • P7 Outbound HTTP resilience — not applicable — this isn't a service/API/worker
  • 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
  • SC1 Supply-chain hygiene — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
  • X6 Hand-rolled structured-format parsing — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
  • X9 Subsumed condition operand — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.

Appendix A — Findings (grouped)

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.

Critical — 102 finding(s)
D29 · Static Analysis (SAST) · REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • + 16 more in this group — see findings.md.
D17 · Explicit Debt · EmptyCatchBlock · ×29
  • EmptyCatchBlock Flow.Launcher.Core/Plugin/JsonRPCPluginV2.cs:119 — 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 Flow.Launcher.Core/Plugin/JsonRPCPluginV2.cs:123 — 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 Flow.Launcher.Core/Plugin/JsonRPCPluginV2.cs:139 — 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 Flow.Launcher.Core/Plugin/JsonRPCPluginV2.cs:143 — 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 Flow.Launcher.Infrastructure/DialogJump/DialogJump.cs:163 — 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 Flow.Launcher.Infrastructure/DialogJump/Models/WindowsExplorer.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 Flow.Launcher.Infrastructure/DialogJump/Models/WindowsExplorer.cs:150 — 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 Flow.Launcher.Infrastructure/DialogJump/Models/WindowsExplorer.cs:162 — 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 Flow.Launcher.Infrastructure/Hotkey/HotkeyModel.cs:113 — 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 Flow.Launcher.Infrastructure/Win32Helper.cs:678 — 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 Flow.Launcher.Infrastructure/Win32Helper.cs:699 — 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 Flow.Launcher.Infrastructure/Win32Helper.cs:713 — 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 Flow.Launcher.Infrastructure/Win32Helper.cs:916 — 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 Flow.Launcher/Helper/HotKeyMapper.cs:160 — 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 Flow.Launcher/MainWindow.xaml.cs:416 — 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 Flow.Launcher/ReportWindow.xaml.cs:51 — 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 Flow.Launcher/ReportWindow.xaml.cs:103 — 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 Flow.Launcher/Storage/TopMostRecord.cs:37 — 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 Flow.Launcher/Storage/TopMostRecord.cs:66 — 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 Plugins/Flow.Launcher.Plugin.BrowserBookmark/Helper/FaviconHelper.cs:94 — 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 Plugins/Flow.Launcher.Plugin.BrowserBookmark/Helper/FaviconHelper.cs:102 — 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 Plugins/Flow.Launcher.Plugin.Explorer/Helper/ShellContextMenuDisplayHelper.cs:394 — 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 Plugins/Flow.Launcher.Plugin.Explorer/Search/Everything/EverythingAPI.cs:177 — 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 Plugins/Flow.Launcher.Plugin.Explorer/Search/Everything/EverythingApiV3.cs:137 — 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 Plugins/Flow.Launcher.Plugin.ProcessKiller/ProcessHelper.cs:111 — 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.
  • + 4 more in this group — see findings.md.
D29 · Static Analysis (SAST) · REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
AX3 · Project dependency cycles · Namespace dependency cycle · ×6
  • Namespace dependency cycle Flow.Launcher.Infrastructure/UserSettings/Settings.cs:18 — The namespaces Flow.Launcher.Infrastructure ↔ Flow.Launcher.Infrastructure.UserSettings depend on each other. The lightest dependency in the cycle is Flow.Launcher.Infrastructure.UserSettings → Flow.Launcher.Infrastructure (Flow.Launcher.Infrastructure.UserSettings.Settings → Flow.Launcher.Infrastructure.StringMatcher, 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 Plugins/Flow.Launcher.Plugin.Calculator/Main.cs:8 — The namespaces Flow.Launcher.Plugin.Calculator ↔ Flow.Launcher.Plugin.Calculator.ViewModels depend on each other. The lightest dependency in the cycle is Flow.Launcher.Plugin.Calculator → Flow.Launcher.Plugin.Calculator.ViewModels (Flow.Launcher.Plugin.Calculator.Main → Flow.Launcher.Plugin.Calculator.ViewModels.SettingsViewModel, 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 Plugins/Flow.Launcher.Plugin.Explorer/Settings.cs:9 — The namespaces Flow.Launcher.Plugin.Explorer ↔ Flow.Launcher.Plugin.Explorer.Search ↔ Flow.Launcher.Plugin.Explorer.Search.Everything ↔ Flow.Launcher.Plugin.Explorer.Search.IProvider ↔ Flow.Launcher.Plugin.Explorer.Search.QuickAccessLinks ↔ Flow.Launcher.Plugin.Explorer.Search.WindowsIndex ↔ Flow.Launcher.Plugin.Explorer.ViewModels depend on each other. The lightest dependency in the cycle is Flow.Launcher.Plugin.Explorer → Flow.Launcher.Plugin.Explorer.Search.QuickAccessLinks (Flow.Launcher.Plugin.Explorer.Settings → Flow.Launcher.Plugin.Explorer.Search.QuickAccessLinks.AccessLink, 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 Plugins/Flow.Launcher.Plugin.PluginsManager/Main.cs:6 — The namespaces Flow.Launcher.Plugin.PluginsManager ↔ Flow.Launcher.Plugin.PluginsManager.ViewModels depend on each other. The lightest dependency in the cycle is Flow.Launcher.Plugin.PluginsManager → Flow.Launcher.Plugin.PluginsManager.ViewModels (Flow.Launcher.Plugin.PluginsManager.Main → Flow.Launcher.Plugin.PluginsManager.ViewModels.SettingsViewModel, 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 Plugins/Flow.Launcher.Plugin.ProcessKiller/Main.cs:5 — The namespaces Flow.Launcher.Plugin.ProcessKiller ↔ Flow.Launcher.Plugin.ProcessKiller.ViewModels depend on each other. The lightest dependency in the cycle is Flow.Launcher.Plugin.ProcessKiller → Flow.Launcher.Plugin.ProcessKiller.ViewModels (Flow.Launcher.Plugin.ProcessKiller.Main → Flow.Launcher.Plugin.ProcessKiller.ViewModels.SettingsViewModel, 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 Plugins/Flow.Launcher.Plugin.Program/AddProgramSource.xaml.cs:2 — The namespaces Flow.Launcher.Plugin.Program ↔ Flow.Launcher.Plugin.Program.Programs ↔ Flow.Launcher.Plugin.Program.ViewModels ↔ Flow.Launcher.Plugin.Program.Views.Models depend on each other. The lightest dependency in the cycle is Flow.Launcher.Plugin.Program → Flow.Launcher.Plugin.Program.ViewModels (Flow.Launcher.Plugin.Program.AddProgramSource → Flow.Launcher.Plugin.Program.ViewModels.AddProgramSourceViewModel, 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.
D29 · Static Analysis (SAST) · REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
D29 · Static Analysis (SAST) · REDACTED
  • REDACTED
  • REDACTED
D29 · Static Analysis (SAST) · REDACTED
  • REDACTED
  • REDACTED
D17 · Explicit Debt · NoWarnInCsproj repeated across 11 files · ×1
  • NoWarnInCsproj repeated across 11 files Flow.Launcher/Flow.Launcher.csproj:39 — The identical NoWarnInCsproj (`FLSG0007`) appears in 11 files (11 occurrences) — a single repo-wide policy (e.g. a Directory.Build.props decision or an idiomatic suppression), not 11 independent debts. Decide it once centrally rather than file-by-file. (Every occurrence still counts toward the score and metrics.)
D28 · Secrets (history) · REDACTED · ×1
  • REDACTED
D29 · Static Analysis (SAST) · REDACTED · ×1
  • REDACTED
D29 · Static Analysis (SAST) · REDACTED · ×1
  • REDACTED
Serious — 332 finding(s)
X2 · Cancellation propagation · Async method without CancellationToken · ×38
  • Async method without CancellationToken: OnStartup Flow.Launcher/App.xaml.cs:181 — No CancellationToken parameter — this work can't be stopped early once started.
  • Async method without CancellationToken: PopulateResultsAsync Flow.Launcher/Helper/ResultHelper.cs:14 — No CancellationToken parameter — this work can't be stopped early once started.
  • Async method without CancellationToken: PopulateResultsAsync Flow.Launcher/Helper/ResultHelper.cs:19 — No CancellationToken parameter — this work can't be stopped early once started.
  • Async method without CancellationToken: CreateRemoteServiceAsync Flow.Launcher/Helper/SingleInstance.cs:94 — No CancellationToken parameter — this work can't be stopped early once started.
  • Async method without CancellationToken: SignalFirstInstanceAsync Flow.Launcher/Helper/SingleInstance.cs:117 — No CancellationToken parameter — this work can't be stopped early once started.
  • Async method without CancellationToken: OnClosing Flow.Launcher/MainWindow.xaml.cs:394 — No CancellationToken parameter — this work can't be stopped early once started.
  • Async method without CancellationToken: OnDeactivated Flow.Launcher/MainWindow.xaml.cs:438 — No CancellationToken parameter — this work can't be stopped early once started.
  • Async method without CancellationToken: OnContextMenusForSettingsClick Flow.Launcher/MainWindow.xaml.cs:621 — No CancellationToken parameter — this work can't be stopped early once started.
  • Async method without CancellationToken: PositionResetAsync Flow.Launcher/MainWindow.xaml.cs:971 — No CancellationToken parameter — this work can't be stopped early once started.
  • Async method without CancellationToken: SetImageOfMessageBoxAsync Flow.Launcher/MessageBoxEx.xaml.cs:128 — No CancellationToken parameter — this work can't be stopped early once started.
  • Async method without CancellationToken: Show Flow.Launcher/Msg.xaml.cs:63 — No CancellationToken parameter — this work can't be stopped early once started.
  • Async method without CancellationToken: Show Flow.Launcher/MsgWithButton.xaml.cs:63 — No CancellationToken parameter — this work can't be stopped early once started.
  • Async method without CancellationToken: ShowAsync Flow.Launcher/ProgressBoxEx.xaml.cs:20 — No CancellationToken parameter — this work can't be stopped early once started.
  • Async method without CancellationToken: RetryActionOnSTAThreadAsync Flow.Launcher/PublicAPIInstance.cs:248 — No CancellationToken parameter — this work can't be stopped early once started.
  • Async method without CancellationToken: LoadCacheBinaryStorageAsync Flow.Launcher/PublicAPIInstance.cs:592 — No CancellationToken parameter — this work can't be stopped early once started.
  • Async method without CancellationToken: SaveCacheBinaryStorageAsync Flow.Launcher/PublicAPIInstance.cs:601 — No CancellationToken parameter — this work can't be stopped early once started.
  • Async method without CancellationToken: RefreshMarkdownViewer Flow.Launcher/ReleaseNotesWindow.xaml.cs:80 — No CancellationToken parameter — this work can't be stopped early once started.
  • Async method without CancellationToken: GetReleaseNotesMarkdownAsync Flow.Launcher/ReleaseNotesWindow.xaml.cs:137 — No CancellationToken parameter — this work can't be stopped early once started.
  • Async method without CancellationToken: RefreshExternalPluginsAsync Flow.Launcher/SettingPages/ViewModels/SettingsPanePluginStoreViewModel.cs:114 — No CancellationToken parameter — this work can't be stopped early once started.
  • Async method without CancellationToken: InstallPluginAsync Flow.Launcher/SettingPages/ViewModels/SettingsPanePluginStoreViewModel.cs:123 — No CancellationToken parameter — this work can't be stopped early once started.
  • Async method without CancellationToken: CheckPluginUpdatesAsync Flow.Launcher/SettingPages/ViewModels/SettingsPanePluginStoreViewModel.cs:134 — No CancellationToken parameter — this work can't be stopped early once started.
  • Async method without CancellationToken: UpdateAllPluginsAsync Flow.Launcher/SettingPages/ViewModels/SettingsPanePluginsViewModel.cs:228 — No CancellationToken parameter — this work can't be stopped early once started.
  • Async method without CancellationToken: CheckForUpdatesSilentlyAsync Flow.Launcher/SettingPages/ViewModels/SettingsPanePluginsViewModel.cs:248 — No CancellationToken parameter — this work can't be stopped early once started.
  • Async method without CancellationToken: CheckForUpdatesCoreAsync Flow.Launcher/SettingPages/ViewModels/SettingsPanePluginsViewModel.cs:264 — No CancellationToken parameter — this work can't be stopped early once started.
  • Async method without CancellationToken: OnTestProxyClickedAsync Flow.Launcher/SettingPages/ViewModels/SettingsPaneProxyViewModel.cs:24 — No CancellationToken parameter — this work can't be stopped early once started.
  • + 13 more in this group — see findings.md.
X3 · Exception handling · Swallowed exception (empty catch) · ×29
  • Swallowed exception (empty catch) Flow.Launcher/Helper/HotKeyMapper.cs:160 — 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) Flow.Launcher/MainWindow.xaml.cs:416 — 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) Flow.Launcher/ReportWindow.xaml.cs:51 — 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) Flow.Launcher/ReportWindow.xaml.cs:103 — 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) Flow.Launcher/Storage/TopMostRecord.cs:37 — 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) Flow.Launcher/Storage/TopMostRecord.cs:66 — 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) Flow.Launcher.Infrastructure/DialogJump/DialogJump.cs:163 — 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) Flow.Launcher.Infrastructure/DialogJump/Models/WindowsExplorer.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) Flow.Launcher.Infrastructure/DialogJump/Models/WindowsExplorer.cs:150 — 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) Flow.Launcher.Infrastructure/DialogJump/Models/WindowsExplorer.cs:162 — 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) Flow.Launcher.Infrastructure/Hotkey/HotkeyModel.cs:113 — 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) Flow.Launcher.Infrastructure/Win32Helper.cs:678 — 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) Flow.Launcher.Infrastructure/Win32Helper.cs:699 — 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) Flow.Launcher.Infrastructure/Win32Helper.cs:713 — 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) Flow.Launcher.Infrastructure/Win32Helper.cs:916 — 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) Flow.Launcher.Core/Plugin/JsonRPCPluginV2.cs:119 — 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) Flow.Launcher.Core/Plugin/JsonRPCPluginV2.cs:123 — 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) Flow.Launcher.Core/Plugin/JsonRPCPluginV2.cs:139 — An empty catch block silently discards the error — failures vanish with no log and no rethrow. On a teardown path letting it propagate is not an option (throwing out of `Dispose()` masks the failure already in flight and abandons the rest of the cleanup), so make the swallow deliberate instead: record it through whatever this codebase already uses to report problems — or, if one specific failure truly cannot matter, catch exactly that exception type and say why in a comment on the catch (a comment on a catch-all still swallows everything else).
  • Swallowed exception (empty catch) Flow.Launcher.Core/Plugin/JsonRPCPluginV2.cs:143 — An empty catch block silently discards the error — failures vanish with no log and no rethrow. On a teardown path letting it propagate is not an option (throwing out of `Dispose()` masks the failure already in flight and abandons the rest of the cleanup), so make the swallow deliberate instead: record it through whatever this codebase already uses to report problems — or, if one specific failure truly cannot matter, catch exactly that exception type and say why in a comment on the catch (a comment on a catch-all still swallows everything else).
  • Swallowed exception (empty catch) Plugins/Flow.Launcher.Plugin.Program/Main.cs:232 — 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) Plugins/Flow.Launcher.Plugin.Program/Main.cs:246 — 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) Plugins/Flow.Launcher.Plugin.Program/Main.cs:255 — 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) Plugins/Flow.Launcher.Plugin.Program/Programs/Win32.cs:422 — 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) Plugins/Flow.Launcher.Plugin.BrowserBookmark/Helper/FaviconHelper.cs:94 — 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) Plugins/Flow.Launcher.Plugin.BrowserBookmark/Helper/FaviconHelper.cs:102 — 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.
  • + 4 more in this group — see findings.md.
X1 · Async correctness · async void method · ×20
  • async void method: OnStartup Flow.Launcher/App.xaml.cs:181 — `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: OnClosing Flow.Launcher/MainWindow.xaml.cs:394 — `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: OnDeactivated Flow.Launcher/MainWindow.xaml.cs:438 — `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: OnContextMenusForSettingsClick Flow.Launcher/MainWindow.xaml.cs:621 — `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: Show Flow.Launcher/Msg.xaml.cs:62 — `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: Show Flow.Launcher/MsgWithButton.xaml.cs:62 — `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: CopyToClipboard Flow.Launcher/PublicAPIInstance.cs:183 — `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: RefreshMarkdownViewer Flow.Launcher/ReleaseNotesWindow.xaml.cs:79 — `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: OnResultsPropertyChanged Flow.Launcher/ViewModel/MainViewModel.cs:1089 — `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: OnHistoryPropertyChanged Flow.Launcher/ViewModel/MainViewModel.cs:1110 — `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: ResetDialogJump Flow.Launcher/ViewModel/MainViewModel.cs:2231 — `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: Hide Flow.Launcher/ViewModel/MainViewModel.cs:2372 — `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: ForegroundChangeCallback Flow.Launcher.Infrastructure/DialogJump/DialogJump.cs:488 — `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: ReIndexing Plugins/Flow.Launcher.Plugin.Program/Views/ProgramSetting.xaml.cs:151 — `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: EditProgramSource Plugins/Flow.Launcher.Plugin.Program/Views/ProgramSetting.xaml.cs:189 — `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: btnLoadAllProgramSource_OnClick Plugins/Flow.Launcher.Plugin.Program/Views/ProgramSetting.xaml.cs:284 — `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: btnProgramSourceStatus_OnClick Plugins/Flow.Launcher.Plugin.Program/Views/ProgramSetting.xaml.cs:292 — `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: btnDeleteProgramSource_OnClick Plugins/Flow.Launcher.Plugin.Program/Views/ProgramSetting.xaml.cs:407 — `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: Initialize Plugins/Flow.Launcher.Plugin.WebSearch/SearchSourceSetting.xaml.cs:33 — `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: OnSelectIconClick Plugins/Flow.Launcher.Plugin.WebSearch/SearchSourceSetting.xaml.cs:140 — `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.
D17 · Explicit Debt · TodoComment · ×15
  • TodoComment Flow.Launcher.Core/Plugin/PluginConfig.cs:28 — // todo use linq when diable plugin is implmented since parallel.foreach + list is not thread saft — 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 Flow.Launcher.Core/Plugin/PythonPlugin.cs:50 — // TODO: Async Action — 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 Flow.Launcher.Infrastructure/Exception/ExceptionFormatter.cs:17 — //todo log /display line by line — 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 Flow.Launcher.Infrastructure/Logger/Log.cs:115 — // todo: not sure we really need that — 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 Flow.Launcher.Infrastructure/Storage/JsonStorage.cs:208 — // todo give user notification for the backup process — 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 Flow.Launcher.Test/Plugins/ProgramPluginTest.cs:18 — // TODO: Program.Main relies on static state (cache, locks, program lists, settings), — 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 Flow.Launcher/HotkeyControl.xaml.cs:280 — // TODO: This is a temporary way to enforce changing only the open flow hotkey to Win, and will be removed by PR #3157
  • TodoComment Flow.Launcher/HotkeyControlDialog.xaml.cs:53 — // TODO: This is a temporary way to enforce changing only the open flow hotkey to Win, and will be removed by PR #3157
  • TodoComment Flow.Launcher/Resources/Controls/CustomScrollViewerEx.cs:11 — // TODO: Use IsScrollAnimationEnabled property in future: https://github.com/iNKORE-NET/UI.WPF.Modern/pull/347
  • TodoComment REDACTED:554 — // TODO: Don't know why, just keep it at the moment — 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:591 — // todo select from file name like pt run — 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:644 — // var plated = PlatedImage(logo); // TODO: maybe get plated directly from app package? — 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:646 — // // todo magic! temp fix for cross thread object — 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:722 — // // todo use windows theme as background — 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 Plugins/Flow.Launcher.Plugin.Shell/Main.cs:525 — // todo: remove this code block after release v2.2.0 — 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.
D17 · Explicit Debt · BarePragmaDisable · ×12
  • BarePragmaDisable Flow.Launcher.Core/Plugin/PluginsLoader.cs:6 — #pragma warning disable IDE0005 — 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 Flow.Launcher.Plugin/SharedCommands/FilesFolders.cs:7 — #pragma warning disable IDE0005 — 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 Plugins/Flow.Launcher.Plugin.WebSearch/SearchSourceViewModel.cs:4 — #pragma warning disable IDE0005 — 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 Flow.Launcher.Test/WindowsDialogTest.cs:149 — #pragma warning disable VSTHRD002 — 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 Flow.Launcher.Test/WindowsDialogTest.cs:204 — #pragma warning disable VSTHRD002 — 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 Flow.Launcher.Test/WindowsDialogTest.cs:260 — #pragma warning disable VSTHRD002 — 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 Flow.Launcher.Test/WindowsDialogTest.cs:289 — #pragma warning disable VSTHRD002 — 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 Flow.Launcher.Test/WindowsDialogTest.cs:334 — #pragma warning disable VSTHRD002 — 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 Flow.Launcher.Test/WindowsDialogTest.cs:418 — #pragma warning disable VSTHRD002 — 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 Flow.Launcher/App.xaml.cs:179 — #pragma warning disable VSTHRD100 // Avoid async void methods — 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 Flow.Launcher/MainWindow.xaml.cs:110 — #pragma warning disable VSTHRD100 // Avoid async void methods — 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 Flow.Launcher/ViewModel/MainViewModel.cs:2319 — #pragma warning disable VSTHRD100 // Avoid async void methods — 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.
GD1 · Unfinished & placeholder code · Unfinished stub · ×8
  • Unfinished stub — throws NotImplementedException Flow.Launcher/Converters/BoolToIMEConversionModeConverter.cs:19 — A shipped member still throws NotImplementedException — generated scaffolding that was never completed. Implement it or remove the dead surface.
  • Unfinished stub — throws NotImplementedException Flow.Launcher/Converters/BoolToIMEConversionModeConverter.cs:36 — A shipped member still throws NotImplementedException — generated scaffolding that was never completed. Implement it or remove the dead surface.
  • Unfinished stub — throws NotImplementedException Flow.Launcher/Converters/CornerRadiusFilterConverter.cs:64 — A shipped member still throws NotImplementedException — generated scaffolding that was never completed. Implement it or remove the dead surface.
  • Unfinished stub — throws NotImplementedException Flow.Launcher/Converters/DateTimeFormatToNowConverter.cs:14 — A shipped member still throws NotImplementedException — generated scaffolding that was never completed. Implement it or remove the dead surface.
  • Unfinished stub — throws NotImplementedException Flow.Launcher/Converters/PlacementRectangleConverter.cs:28 — A shipped member still throws NotImplementedException — generated scaffolding that was never completed. Implement it or remove the dead surface.
  • Unfinished stub — throws NotImplementedException Flow.Launcher/Converters/QuerySuggestionBoxConverter.cs:97 — A shipped member still throws NotImplementedException — generated scaffolding that was never completed. Implement it or remove the dead surface.
  • Unfinished stub — throws NotImplementedException Flow.Launcher/Converters/SharedSizeGroupConverter.cs:15 — A shipped member still throws NotImplementedException — generated scaffolding that was never completed. Implement it or remove the dead surface.
  • Unfinished stub — throws NotImplementedException Flow.Launcher/Converters/StringToKeyBindingConverter.cs:25 — A shipped member still throws NotImplementedException — generated scaffolding that was never completed. Implement it or remove the dead surface.
X5 · Nullable reference types · Symbol treated as nullable, then dereferenced unguarded · ×8
  • Symbol treated as nullable, then dereferenced unguarded Flow.Launcher.Core/Resource/Theme.cs:324 — This method contradicts itself about `windowStyle`: line 322 assigns it with `as Style`, which hands back null rather than throwing when the value is not a `Style`, but line 324 then dereferences it directly as `windowStyle.Setters` with no null test between them and no guard around it. If the `as` is right, that dereference throws NullReferenceException on the input it was written for — and the NullReferenceException names neither the cast nor the type that failed. Settle it one way — test `windowStyle` once before the first use and handle the null case, or cast with `(Style)` so the failure is reported where it happens — rather than leaving the two readings side by side.
  • Symbol treated as nullable, then dereferenced unguarded Plugins/Flow.Launcher.Plugin.Program/Programs/Win32.cs:94 — This method contradicts itself about `match`: line 96 writes `match?.IsSearchPrecisionScoreMet`, which says `match` can be null, but line 94 then dereferences it directly as `match.Score` 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 `match` truly cannot be null here, the `?.` is misleading. Settle it one way — test `match` once before the first use and handle the null case, or drop the `?.` — rather than leaving the two readings side by side.
  • Symbol treated as nullable, then dereferenced unguarded Plugins/Flow.Launcher.Plugin.Program/Views/ProgramSetting.xaml.cs:450 — This method contradicts itself about `listView`: line 449 assigns it with `as ListView`, which hands back null rather than throwing when the value is not a `ListView`, but line 450 then dereferences it directly as `listView.View` with no null test between them and no guard around it. If the `as` is right, that dereference throws NullReferenceException on the input it was written for — and the NullReferenceException names neither the cast nor the type that failed. Settle it one way — test `listView` once before the first use and handle the null case, or cast with `(ListView)` so the failure is reported where it happens — rather than leaving the two readings side by side.
  • Symbol treated as nullable, then dereferenced unguarded Plugins/Flow.Launcher.Plugin.Program/Views/ProgramSetting.xaml.cs:461 — This method contradicts itself about `gView`: line 450 assigns it with `as GridView`, which hands back null rather than throwing when the value is not a `GridView`, but line 461 then dereferences it directly as `gView.Columns` with no null test between them and no guard around it. If the `as` is right, that dereference throws NullReferenceException on the input it was written for — and the NullReferenceException names neither the cast nor the type that failed. Settle it one way — test `gView` once before the first use and handle the null case, or cast with `(GridView)` so the failure is reported where it happens — rather than leaving the two readings side by side.
  • Symbol treated as nullable, then dereferenced unguarded Plugins/Flow.Launcher.Plugin.WebSearch/SettingsControl.xaml.cs:151 — This method contradicts itself about `listView`: line 150 assigns it with `as ListView`, which hands back null rather than throwing when the value is not a `ListView`, but line 151 then dereferences it directly as `listView.View` with no null test between them and no guard around it. If the `as` is right, that dereference throws NullReferenceException on the input it was written for — and the NullReferenceException names neither the cast nor the type that failed. Settle it one way — test `listView` once before the first use and handle the null case, or cast with `(ListView)` so the failure is reported where it happens — rather than leaving the two readings side by side.
  • Symbol treated as nullable, then dereferenced unguarded Plugins/Flow.Launcher.Plugin.WebSearch/SettingsControl.xaml.cs:164 — This method contradicts itself about `gView`: line 151 assigns it with `as GridView`, which hands back null rather than throwing when the value is not a `GridView`, but line 164 then dereferences it directly as `gView.Columns` with no null test between them and no guard around it. If the `as` is right, that dereference throws NullReferenceException on the input it was written for — and the NullReferenceException names neither the cast nor the type that failed. Settle it one way — test `gView` once before the first use and handle the null case, or cast with `(GridView)` so the failure is reported where it happens — rather than leaving the two readings side by side.
  • Symbol treated as nullable, then dereferenced unguarded Plugins/Flow.Launcher.Plugin.Sys/SysSettings.xaml.cs:21 — This method contradicts itself about `listView`: line 20 assigns it with `as ListView`, which hands back null rather than throwing when the value is not a `ListView`, but line 21 then dereferences it directly as `listView.View` with no null test between them and no guard around it. If the `as` is right, that dereference throws NullReferenceException on the input it was written for — and the NullReferenceException names neither the cast nor the type that failed. Settle it one way — test `listView` once before the first use and handle the null case, or cast with `(ListView)` so the failure is reported where it happens — rather than leaving the two readings side by side.
  • Symbol treated as nullable, then dereferenced unguarded Plugins/Flow.Launcher.Plugin.Sys/SysSettings.xaml.cs:32 — This method contradicts itself about `gView`: line 21 assigns it with `as GridView`, which hands back null rather than throwing when the value is not a `GridView`, but line 32 then dereferences it directly as `gView.Columns` with no null test between them and no guard around it. If the `as` is right, that dereference throws NullReferenceException on the input it was written for — and the NullReferenceException names neither the cast nor the type that failed. Settle it one way — test `gView` once before the first use and handle the null case, or cast with `(GridView)` so the failure is reported where it happens — rather than leaving the two readings side by side.
AX2 · Stateful singletons · Stateful singleton · ×7
  • Stateful singleton: SettingWindowViewModel Flow.Launcher/ViewModel/SettingWindowViewModel.cs:7 — `SettingWindowViewModel` is a singleton (one shared instance) but mutates instance state outside any lock (_pageType; e.g. `_pageType` at line 20).
  • Stateful singleton: WelcomeViewModel Flow.Launcher/ViewModel/WelcomeViewModel.cs:5 — `WelcomeViewModel` is a singleton (one shared instance) but mutates instance state outside any lock (_pageNum, _backEnabled, _nextEnabled; e.g. `_pageNum` at line 19).
  • Stateful singleton: MainViewModel Flow.Launcher/ViewModel/MainViewModel.cs:33 — `MainViewModel` is a singleton (one shared instance) but mutates instance state outside any lock (lastHistoryIndex, _selectionBeforeContextMenu, GameModeStatus, _queryText, QueryTextCursorMovedToEnd, _selectedResults; e.g. `lastHistoryIndex` at line 387).
  • Stateful singleton: Theme Flow.Launcher.Core/Resource/Theme.cs:23 — `Theme` is a singleton (one shared instance) but mutates instance state outside any lock (_oldResource, _oldTheme, BlurEnabled, _themeResizeBorderThickness; e.g. `_oldResource` at line 116).
  • Stateful singleton: PublicAPIInstance Flow.Launcher/PublicAPIInstance.cs:41 — `PublicAPIInstance` is a singleton (one shared instance) but mutates instance state outside any lock (_theme, _updater, _globalKeyboardHandlers; e.g. `_theme` at line 50).
  • Stateful singleton: Internationalization Flow.Launcher.Core/Resource/Internationalization.cs:16 — `Internationalization` is a singleton (one shared instance) but mutates instance state outside any lock (_languageDirectories, _oldResources; e.g. `_languageDirectories` at line 107).
  • Stateful singleton: Settings Flow.Launcher.Infrastructure/UserSettings/Settings.cs:18 — `Settings` is a singleton (one shared instance) but mutates instance state outside any lock (_storage, _stringMatcher, _openResultModifiers, _showOpenResultHotkey, _language, _theme; e.g. `_storage` at line 27).
D29 · Static Analysis (SAST) · REDACTED · ×7
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
D3 · God Classes · MethodTooLong · ×7
  • MethodTooLong: Main.Commands Plugins/Flow.Launcher.Plugin.Sys/Main.cs:312 — MethodTooLong — Commands runs 217 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 117 over it, 2.17× 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: JsonRPCPluginSettings.CreateSettingPanel Flow.Launcher.Core/Plugin/JsonRPCPluginSettings.cs:156 — MethodTooLong — CreateSettingPanel runs 189 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 89 over it, 1.89× 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: PluginsManager.RequestUpdateAsync Plugins/Flow.Launcher.Plugin.PluginsManager/PluginsManager.cs:244 — MethodTooLong — RequestUpdateAsync runs 182 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 82 over it, 1.82× 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: ContextMenu.LoadContextMenus Plugins/Flow.Launcher.Plugin.Explorer/ContextMenu.cs:30 — MethodTooLong — LoadContextMenus runs 170 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 70 over it, 1.70× 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.OnLoaded Flow.Launcher/MainWindow.xaml.cs:128 — MethodTooLong — OnLoaded runs 133 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 33 over it, 1.33× 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: MainViewModel.QueryResultsAsync Flow.Launcher/ViewModel/MainViewModel.cs:1537 — MethodTooLong — QueryResultsAsync runs 117 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 17 over it, 1.17× 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: EverythingApiV3.TryConvertSortOption Plugins/Flow.Launcher.Plugin.Explorer/Search/Everything/EverythingApiV3.cs:339 — MethodTooLong — TryConvertSortOption 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.
D3 · God Classes · TooManyMethods · ×6
  • TooManyMethods: MainViewModel Flow.Launcher/ViewModel/MainViewModel.cs — TooManyMethods — 1217 significant lines (blank, comment-only and punctuation-only lines excluded), 89 methods. The bar is 30 methods; this is 59 over it, 2.97× 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: PublicAPIInstance Flow.Launcher/PublicAPIInstance.cs — TooManyMethods — 316 significant lines (blank, comment-only and punctuation-only lines excluded), 81 methods. The bar is 30 methods; this is 51 over it, 2.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: MainWindow Flow.Launcher/MainWindow.xaml.cs — TooManyMethods — 804 significant lines (blank, comment-only and punctuation-only lines excluded), 58 methods. The bar is 30 methods; this is 28 over it, 1.93× 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: PluginManager Flow.Launcher.Core/Plugin/PluginManager.cs — TooManyMethods — 537 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. 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: Win32Helper Flow.Launcher.Infrastructure/Win32Helper.cs — TooManyMethods — 428 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. 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: Win32 Plugins/Flow.Launcher.Plugin.Program/Programs/Win32.cs — TooManyMethods — 417 significant lines (blank, comment-only and punctuation-only lines excluded), 33 methods. The bar is 30 methods; this is 3 over it, 1.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.
D3 · God Classes · FileTooLong · ×6
  • FileTooLong: ViewModel/MainViewModel.cs Flow.Launcher/ViewModel/MainViewModel.cs — FileTooLong — 1252 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 752 over it, 2.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: Helper/ShellContextMenu.cs Plugins/Flow.Launcher.Plugin.Explorer/Helper/ShellContextMenu.cs — FileTooLong — 947 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 447 over it, 1.89× 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: Flow.Launcher/MainWindow.xaml.cs Flow.Launcher/MainWindow.xaml.cs — FileTooLong — 839 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 339 over it, 1.68× 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: DialogJump/DialogJump.cs Flow.Launcher.Infrastructure/DialogJump/DialogJump.cs — FileTooLong — 560 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 60 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: Plugin/PluginManager.cs Flow.Launcher.Core/Plugin/PluginManager.cs — FileTooLong — 556 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 56 over it, 1.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: Flow.Launcher.Plugin.PluginsManager/PluginsManager.cs Plugins/Flow.Launcher.Plugin.PluginsManager/PluginsManager.cs — FileTooLong — 532 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 32 over it, 1.06× 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.
D3 · God Classes · ClassTooLong · ×6
  • ClassTooLong: ShellContextMenu Plugins/Flow.Launcher.Plugin.Explorer/Helper/ShellContextMenu.cs — ClassTooLong — 649 significant lines (blank, comment-only and punctuation-only lines excluded), 21 methods. The bar is 400 significant lines; this is 249 over it, 1.62× 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: DialogJump Flow.Launcher.Infrastructure/DialogJump/DialogJump.cs — ClassTooLong — 543 significant lines (blank, comment-only and punctuation-only lines excluded), 25 methods. The bar is 400 significant lines; this is 143 over it, 1.36× 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: PluginsManager Plugins/Flow.Launcher.Plugin.PluginsManager/PluginsManager.cs — ClassTooLong — 521 significant lines (blank, comment-only and punctuation-only lines excluded), 16 methods. The bar is 400 significant lines; this is 121 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.
  • ClassTooLong: Theme Flow.Launcher.Core/Resource/Theme.cs — ClassTooLong — 456 significant lines (blank, comment-only and punctuation-only lines excluded), 28 methods. The bar is 400 significant lines; this is 56 over it, 1.14× 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: Settings Flow.Launcher.Infrastructure/UserSettings/Settings.cs — ClassTooLong — 415 significant lines (blank, comment-only and punctuation-only lines excluded), 5 methods. The bar is 400 significant lines; this is 15 over it, 1.04× 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: SettingsViewModel Plugins/Flow.Launcher.Plugin.Explorer/ViewModels/SettingsViewModel.cs — ClassTooLong — 401 significant lines (blank, comment-only and punctuation-only lines excluded), 17 methods. The bar is 400 significant lines; this is 1 over it, 1.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.
D35 · Change Coupling · Change coupling · ×5
  • Change coupling: EverythingSearchManager.cs ↔ WindowsIndexSearchManager.cs Plugins/Flow.Launcher.Plugin.Explorer/Search/Everything/EverythingSearchManager.cs:1 — `Plugins/Flow.Launcher.Plugin.Explorer/Search/Everything/EverythingSearchManager.cs` and `Plugins/Flow.Launcher.Plugin.Explorer/Search/WindowsIndex/WindowsIndexSearchManager.cs` change together 69% of the time (9 of the 13 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well, and counted over this repository's 10,000 most recent commits rather than its whole history — 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 9 shared commits counted here, the most recent 3 are `78e5bf2a` Use Flow.Launcher.Localization to improve code quality; `51f5d8a4` Add new constructor for EngineNotAvailableException; `2c3df3f4` Change signature back to string to accommodate async method. — run `git show` on any of them.
  • Change coupling: SearchManager.cs ↔ WindowsIndexSearchManager.cs Plugins/Flow.Launcher.Plugin.Explorer/Search/SearchManager.cs:1 — `Plugins/Flow.Launcher.Plugin.Explorer/Search/SearchManager.cs` and `Plugins/Flow.Launcher.Plugin.Explorer/Search/WindowsIndex/WindowsIndexSearchManager.cs` change together 62% of the time (8 of the 13 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well, and counted over this repository's 10,000 most recent commits rather than its whole history — 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 8 shared commits counted here, the most recent 3 are `78e5bf2a` Use Flow.Launcher.Localization to improve code quality; `52e72992` Change context and settings to non static; `8b1c125b` Custom Exception & Some Refactor — run `git show` on any of them.
  • Change coupling: TypeScriptEnvironment.cs ↔ Updater.cs Flow.Launcher.Core/ExternalPlugins/Environments/TypeScriptEnvironment.cs:1 — `Flow.Launcher.Core/ExternalPlugins/Environments/TypeScriptEnvironment.cs` and `Flow.Launcher.Core/Updater.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, and counted over this repository's 10,000 most recent commits rather than its whole history — 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 `7350c1d4` Use Flow.Launcher.Localization to improve code quality; `3cb9d1dc` Remove IApp & AppExtensions and use dependency injection instead; `88e84378` Use api in app extensions to call api functions — run `git show` on any of them.
  • Change coupling: ChromiumBookmarkLoader.cs ↔ FirefoxBookmarkLoader.cs Plugins/Flow.Launcher.Plugin.BrowserBookmark/ChromiumBookmarkLoader.cs:1 — `Plugins/Flow.Launcher.Plugin.BrowserBookmark/ChromiumBookmarkLoader.cs` and `Plugins/Flow.Launcher.Plugin.BrowserBookmark/FirefoxBookmarkLoader.cs` change together 50% of the time (19 of the 38 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well, and counted over this repository's 10,000 most recent commits rather than its whole history — 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 `1b05643b` Use Flow.Launcher.Localization to improve code quality; `d7b8f85f` Use FaviconHelper; `2ed32b31` Do not use pooling so that we do not need to clear pool — run `git show` on any of them.
  • Change coupling: PythonEnvironment.cs ↔ Updater.cs Flow.Launcher.Core/ExternalPlugins/Environments/PythonEnvironment.cs:1 — `Flow.Launcher.Core/ExternalPlugins/Environments/PythonEnvironment.cs` and `Flow.Launcher.Core/Updater.cs` change together 50% of the time (6 of the 12 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well, and counted over this repository's 10,000 most recent commits rather than its whole history — 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 `7350c1d4` Use Flow.Launcher.Localization to improve code quality; `3cb9d1dc` Remove IApp & AppExtensions and use dependency injection instead; `88e84378` Use api in app extensions to call api functions — run `git show` on any of them.
X3 · Exception handling · Swallowed exception (caught, then discarded) · ×5
  • Swallowed exception (caught, then discarded) Flow.Launcher.Plugin/SharedCommands/FilesFolders.cs:189 — `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) Flow.Launcher.Plugin/SharedCommands/FilesFolders.cs:216 — `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) Flow.Launcher.Plugin/SharedCommands/FilesFolders.cs:235 — `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) Flow.Launcher.Plugin/SharedCommands/FilesFolders.cs:240 — `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) Flow.Launcher.Core/Resource/Theme.cs:914 — `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.
D36 · Supply-chain Provenance & Signing REDACTED · ×4
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
D15 · Churn × Complexity Hotspots · Repeated repair · ×3
  • Repeated repair: Flow.Launcher/SettingPages/ViewModels/SettingsPanePluginsViewModel.cs Flow.Launcher/SettingPages/ViewModels/SettingsPanePluginsViewModel.cs:264 — Flow.Launcher/SettingPages/ViewModels/SettingsPanePluginsViewModel.cs changed 5 times in last 90 days and 3 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 7 (its worst body is SettingsPanePluginsViewModel.CheckForUpdatesCoreAsync at line 264), UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “fix: Catch and log silent update check failures, reset guard for retry”; “fix: Clear plugin update badge and toolbar count after successful update”; “fix: Use semantic version comparison for plugin update check”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-07-20..2026-10-18, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-20 16:02:49 +08:00' --until='2026-10-18 16:02:49 +08:00' --full-history --no-merges -- Flow.Launcher/SettingPages/ViewModels/SettingsPanePluginsViewModel.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.
  • Repeated repair: Flow.Launcher.Infrastructure/Storage/JsonStorage.cs Flow.Launcher.Infrastructure/Storage/JsonStorage.cs:64 — Flow.Launcher.Infrastructure/Storage/JsonStorage.cs changed 4 times in last 90 days and 3 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 5 (its worst body is JsonStorage.LoadAsync at line 64), UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “fix: qualify System.Exception in JsonStorage”; “fix: keep loaded backup data when restoring it fails”; “fix: restore JSON backup outside the read stream scope”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-07-20..2026-10-18, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-20 16:02:49 +08:00' --until='2026-10-18 16:02:49 +08:00' --full-history --no-merges -- Flow.Launcher.Infrastructure/Storage/JsonStorage.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.
  • Repeated repair: Flow.Launcher.Core/Plugin/PluginConfig.cs Flow.Launcher.Core/Plugin/PluginConfig.cs:76 — Flow.Launcher.Core/Plugin/PluginConfig.cs changed 3 times in last 90 days and 3 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 8 (its worst body is PluginConfig.GetUniqueLatestPluginMetadata at line 76), UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “Fix tie detection for semantically equal versions in duplicate plugin check”; “Fix version comparison cycle in duplicate plugin detection”; “fix: enhance semantic version comparison in PluginConfig”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-07-20..2026-10-18, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-20 16:02:49 +08:00' --until='2026-10-18 16:02:49 +08:00' --full-history --no-merges -- Flow.Launcher.Core/Plugin/PluginConfig.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.
D17 · Explicit Debt · ObsoleteWithCallers · ×3
  • ObsoleteWithCallers Flow.Launcher.Plugin/Interfaces/IPublicAPI.cs:309 — [Obsolete] ActionKeywordAssigned
  • ObsoleteWithCallers Flow.Launcher/Storage/QueryHistory.cs:27 — [Obsolete] PopulateHistoryFromLegacyHistory
  • ObsoleteWithCallers REDACTED:23 — [Obsolete] ProgramSuffixes
D4 · Code Duplication · Duplicated block (20 lines × 2) · ×3
  • Duplicated block (20 lines × 2) Plugins/Flow.Launcher.Plugin.Explorer/Views/PreviewPanel.xaml.cs:134 — Plugins/Flow.Launcher.Plugin.Explorer/Views/PreviewPanel.xaml.cs:134-153 | Plugins/Flow.Launcher.Plugin.Explorer/Views/PreviewPanel.xaml.cs:165-184 — 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 `Plugins/Flow.Launcher.Plugin.Explorer/Views/PreviewPanel.xaml.cs:134` 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 (20 lines × 2) Plugins/Flow.Launcher.Plugin.Explorer/Views/PreviewPanel.xaml.cs:252 — Plugins/Flow.Launcher.Plugin.Explorer/Views/PreviewPanel.xaml.cs:252-271 | Plugins/Flow.Launcher.Plugin.Explorer/Views/PreviewPanel.xaml.cs:283-302 — 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 `Plugins/Flow.Launcher.Plugin.Explorer/Views/PreviewPanel.xaml.cs:252` 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 (20 lines × 2) Flow.Launcher.Infrastructure/DialogJump/DialogJump.cs:507 — Flow.Launcher.Infrastructure/DialogJump/DialogJump.cs:507-526 | Flow.Launcher.Infrastructure/DialogJump/DialogJump.cs:924-943 — 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 `Flow.Launcher.Infrastructure/DialogJump/DialogJump.cs:507` 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.
D4 · Code Duplication · Duplicated block (5 lines × 2) · ×3
  • Duplicated block (5 lines × 2) Plugins/Flow.Launcher.Plugin.BrowserBookmark/ChromiumBookmarkLoader.cs:181 — Plugins/Flow.Launcher.Plugin.BrowserBookmark/ChromiumBookmarkLoader.cs:181-185 | Plugins/Flow.Launcher.Plugin.BrowserBookmark/FirefoxBookmarkLoader.cs:156-160 — 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) Flow.Launcher.Core/Plugin/PluginInstaller.cs:50 — Flow.Launcher.Core/Plugin/PluginInstaller.cs:50-54 | Plugins/Flow.Launcher.Plugin.PluginsManager/PluginsManager.cs:145-149 — 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) Flow.Launcher/SettingWindow.xaml.cs:89 — Flow.Launcher/SettingWindow.xaml.cs:89-93 | Flow.Launcher/WelcomeWindow.xaml.cs:80-84 — 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.
D6 · Cohesion (LCOM4) · Low cohesion · ×3
  • Low cohesion: ResultListBox (LCOM4 5) Flow.Launcher/ResultListBox.xaml.cs:11 — ResultListBox's methods fall into 5 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 5 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: ProgramSetting (LCOM4 4) Plugins/Flow.Launcher.Plugin.Program/Views/ProgramSetting.xaml.cs:19 — ProgramSetting's methods fall into 4 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 4 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: SettingsControl (LCOM4 4) Plugins/Flow.Launcher.Plugin.WebSearch/SettingsControl.xaml.cs:14 — SettingsControl's methods fall into 4 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 4 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.
X18 · Disposal-pattern correctness · Disposable created and abandoned in the method that made it · ×3
  • Disposable created and abandoned in the method that made it Flow.Launcher/ViewModel/MainViewModel.cs:320 — `timer` is a `PeriodicTimer`, which implements `IDisposable`, and it is created here (line 320). Every use of it in `RegisterClockAndDateUpdateAsync` 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 timer = …;`), 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 Flow.Launcher/ViewModel/SelectFileManagerViewModel.cs:79 — `process` is a `Process`, which implements `IDisposable`, and it is created here (line 79). Every use of it in `IsFileManagerValid` 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 Flow.Launcher.Infrastructure/Image/ImageLoader.cs:511 — `converter` is a `FileSvgReader`, which implements `IDisposable`, and it is created here (line 511). Every use of it in `LoadSvgImage` 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 converter = …;`), which releases it at the end of the scope on every path including a throw.
D15 · Churn × Complexity Hotspots · Hotspot · ×2
  • Hotspot: Flow.Launcher/MainWindow.xaml.cs Flow.Launcher/MainWindow.xaml.cs:128 — Flow.Launcher/MainWindow.xaml.cs changed 8 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 44 in MainWindow.OnLoaded at line 128. 3 of those changes were fix/bug commits, and the other 5 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-20..2026-10-18, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-20 16:02:49 +08:00' --until='2026-10-18 16:02:49 +08:00' --full-history --no-merges -- Flow.Launcher/MainWindow.xaml.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: Flow.Launcher/ViewModel/MainViewModel.cs Flow.Launcher/ViewModel/MainViewModel.cs:82 — Flow.Launcher/ViewModel/MainViewModel.cs changed 13 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 24 in MainViewModel.MainViewModel.ctor at line 82. 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-20..2026-10-18, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-20 16:02:49 +08:00' --until='2026-10-18 16:02:49 +08:00' --full-history --no-merges -- Flow.Launcher/ViewModel/MainViewModel.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.
D17 · Explicit Debt · CommentedOutCode · ×2
  • CommentedOutCode REDACTED:568 — 4 consecutive commented-code lines
  • CommentedOutCode REDACTED:693 — 3 consecutive commented-code lines
D29 · Static Analysis (SAST) · REDACTED · ×2
  • REDACTED
  • REDACTED
D4 · Code Duplication · Duplicated block (18 lines × 2) · ×2
  • Duplicated block (18 lines × 2) Flow.Launcher.Plugin/SharedModels/MonitorInfo.cs:79 — Flow.Launcher.Plugin/SharedModels/MonitorInfo.cs:79-96 | Flow.Launcher.Plugin/SharedModels/MonitorInfo.cs:110-127 — 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 `Flow.Launcher.Plugin/SharedModels/MonitorInfo.cs:79` 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 (18 lines × 2) Plugins/Flow.Launcher.Plugin.Program/Views/ProgramSetting.xaml.cs:339 — Plugins/Flow.Launcher.Plugin.Program/Views/ProgramSetting.xaml.cs:339-356 | Plugins/Flow.Launcher.Plugin.WebSearch/SettingsControl.xaml.cs:82-99 — 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.
D4 · Code Duplication · Duplicated block (15 lines × 2) · ×2
  • Duplicated block (15 lines × 2) Flow.Launcher.Core/Plugin/PluginManager.cs:863 — Flow.Launcher.Core/Plugin/PluginManager.cs:863-877 | Plugins/Flow.Launcher.Plugin.PluginsManager/Utilities.cs:46-60 — 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 (15 lines × 2) Plugins/Flow.Launcher.Plugin.WebSearch/SuggestionSources/DuckDuckGo.cs:24 — Plugins/Flow.Launcher.Plugin.WebSearch/SuggestionSources/DuckDuckGo.cs:24-38 | Plugins/Flow.Launcher.Plugin.WebSearch/SuggestionSources/Google.cs:17-31 — 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 `Plugins/Flow.Launcher.Plugin.WebSearch/SuggestionSources/DuckDuckGo.cs:24` 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.
D4 · Code Duplication · Duplicated block (13 lines × 2) · ×2
  • Duplicated block (13 lines × 2) Plugins/Flow.Launcher.Plugin.Program/Views/ProgramSetting.xaml.cs:452 — Plugins/Flow.Launcher.Plugin.Program/Views/ProgramSetting.xaml.cs:452-464 | Plugins/Flow.Launcher.Plugin.Sys/SysSettings.xaml.cs:23-35 — 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 `Plugins/Flow.Launcher.Plugin.Program/Views/ProgramSetting.xaml.cs:452` 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 (13 lines × 2) Plugins/Flow.Launcher.Plugin.Explorer/Views/ActionKeywordSetting.xaml.cs:102 — Plugins/Flow.Launcher.Plugin.Explorer/Views/ActionKeywordSetting.xaml.cs:102-114 | Plugins/Flow.Launcher.Plugin.WebSearch/SearchSourceSetting.xaml.cs:171-183 — 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.
D4 · Code Duplication · Duplicated block (12 lines × 2) · ×2
  • Duplicated block (12 lines × 2) Flow.Launcher.Core/Plugin/PluginInstaller.cs:473 — Flow.Launcher.Core/Plugin/PluginInstaller.cs:473-484 | Plugins/Flow.Launcher.Plugin.PluginsManager/PluginsManager.cs:657-668 — 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) Flow.Launcher.Plugin/SharedCommands/ShellCommand.cs:69 — Flow.Launcher.Plugin/SharedCommands/ShellCommand.cs:69-80 | Plugins/Flow.Launcher.Plugin.ProcessKiller/ProcessHelper.cs:124-135 — 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.
D4 · Code Duplication · Duplicated block (11 lines × 2) · ×2
  • Duplicated block (11 lines × 2) Plugins/Flow.Launcher.Plugin.Explorer/Helper/ShellContextMenu.cs:315 — Plugins/Flow.Launcher.Plugin.Explorer/Helper/ShellContextMenu.cs:315-325 | Plugins/Flow.Launcher.Plugin.Explorer/Helper/ShellContextMenu.cs:354-364 — 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) Flow.Launcher/App.xaml.cs:335 — Flow.Launcher/App.xaml.cs:335-345 | Flow.Launcher/App.xaml.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.
D4 · Code Duplication · Duplicated block (10 lines × 2) · ×2
  • Duplicated block (10 lines × 2) Flow.Launcher/SelectBrowserWindow.xaml.cs:35 — Flow.Launcher/SelectBrowserWindow.xaml.cs:35-44 | Flow.Launcher/SelectFileManagerWindow.xaml.cs:36-45 — 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) Flow.Launcher.Core/Plugin/PluginInstaller.cs:500 — Flow.Launcher.Core/Plugin/PluginInstaller.cs:500-509 | Plugins/Flow.Launcher.Plugin.PluginsManager/PluginsManager.cs:845-854 — 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.
D4 · Code Duplication · Duplicated block (9 lines × 2) · ×2
  • Duplicated block (9 lines × 2) Flow.Launcher.Infrastructure/Win32Helper.cs:842 — Flow.Launcher.Infrastructure/Win32Helper.cs:842-850 | Plugins/Flow.Launcher.Plugin.ProcessKiller/ProcessHelper.cs:172-180 — 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 `Flow.Launcher.Infrastructure/Win32Helper.cs:842` 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 (9 lines × 2) Flow.Launcher.Core/Resource/Theme.cs:476 — Flow.Launcher.Core/Resource/Theme.cs:476-484 | Flow.Launcher.Core/Resource/Theme.cs:546-554 — 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. 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.
D4 · Code Duplication · Duplicated block (7 lines × 2) · ×2
  • Duplicated block (7 lines × 2) Flow.Launcher.Plugin/Result.cs:93 — Flow.Launcher.Plugin/Result.cs:93-99 | Flow.Launcher.Plugin/Result.cs:128-134 — 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 `Flow.Launcher.Plugin/Result.cs:93` 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) Flow.Launcher.Core/Resource/Theme.cs:148 — Flow.Launcher.Core/Resource/Theme.cs:148-154 | Flow.Launcher.Core/Resource/Theme.cs:264-270 — 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 `Flow.Launcher.Core/Resource/Theme.cs:148` 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.
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.
D1 · Cyclomatic Complexity · MainWindow.OnLoaded (cyclomatic 44) · ×1
  • MainWindow.OnLoaded (cyclomatic 44) Flow.Launcher/MainWindow.xaml.cs:128 — MainWindow.OnLoaded has cyclomatic complexity 44 (threshold 15). Most of this is not in the body itself: 13 of the 44 points are its own statements and the rest belongs to 4 function literals inside it that branch (lines 317, 257, 251, …). 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.
D1 · Cyclomatic Complexity · StringMatcher.FuzzyMatch (cyclomatic 35) · ×1
  • StringMatcher.FuzzyMatch (cyclomatic 35) Flow.Launcher.Infrastructure/StringMatcher.cs:61 — StringMatcher.FuzzyMatch has cyclomatic complexity 35 (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.
D1 · Cyclomatic Complexity · MainViewModel.QueryResultsAsync (cyclomatic 34) · ×1
  • MainViewModel.QueryResultsAsync (cyclomatic 34) Flow.Launcher/ViewModel/MainViewModel.cs:1537 — MainViewModel.QueryResultsAsync has cyclomatic complexity 34 (threshold 15). Of this number, 28 points are the body's own statements and 6 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.
D1 · Cyclomatic Complexity · ContextMenu.LoadContextMenus (cyclomatic 33) · ×1
  • ContextMenu.LoadContextMenus (cyclomatic 33) Plugins/Flow.Launcher.Plugin.Explorer/ContextMenu.cs:30 — ContextMenu.LoadContextMenus has cyclomatic complexity 33 (threshold 15). Of this number, 22 points are the body's own statements and 11 belong to 7 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.
D1 · Cyclomatic Complexity · JsonRPCPluginSettings.CreateSettingPanel (cyclomatic 29) · ×1
  • JsonRPCPluginSettings.CreateSettingPanel (cyclomatic 29) Flow.Launcher.Core/Plugin/JsonRPCPluginSettings.cs:156 — JsonRPCPluginSettings.CreateSettingPanel has cyclomatic complexity 29 (threshold 15). Of this number, 23 points are the body's own statements and 6 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.
D1 · Cyclomatic Complexity · PluginsManager.RequestUpdateAsync (cyclomatic 25) · ×1
  • PluginsManager.RequestUpdateAsync (cyclomatic 25) Plugins/Flow.Launcher.Plugin.PluginsManager/PluginsManager.cs:244 — PluginsManager.RequestUpdateAsync has cyclomatic complexity 25 (threshold 15). Most of this is not in the body itself: 8 of the 25 points are its own statements and the rest belongs to 4 function literals inside it that branch (lines 348, 439, 312, …). 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.
D1 · Cyclomatic Complexity · DialogJump.SetupDialogJump (cyclomatic 24) · ×1
  • DialogJump.SetupDialogJump (cyclomatic 24) Flow.Launcher.Infrastructure/DialogJump/DialogJump.cs:149 — DialogJump.SetupDialogJump 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.
D1 · Cyclomatic Complexity · DialogJump.ForegroundChangeCallback (cyclomatic 23) · ×1
  • DialogJump.ForegroundChangeCallback (cyclomatic 23) Flow.Launcher.Infrastructure/DialogJump/DialogJump.cs:488 — DialogJump.ForegroundChangeCallback has cyclomatic 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, 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.
D1 · Cyclomatic Complexity · FilesFolders.TryDeleteDirectoryRobust (cyclomatic 21) · ×1
  • FilesFolders.TryDeleteDirectoryRobust (cyclomatic 21) Flow.Launcher.Plugin/SharedCommands/FilesFolders.cs:144 — FilesFolders.TryDeleteDirectoryRobust 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.
D1 · Cyclomatic Complexity · SearchManager.SearchAsync (cyclomatic 21) · ×1
  • SearchManager.SearchAsync (cyclomatic 21) Plugins/Flow.Launcher.Plugin.Explorer/Search/SearchManager.cs:79 — SearchManager.SearchAsync has cyclomatic complexity 21 (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.
D1 · Cyclomatic Complexity · Main.CreateResultsFromQuery (cyclomatic 21) · ×1
  • Main.CreateResultsFromQuery (cyclomatic 21) Plugins/Flow.Launcher.Plugin.ProcessKiller/Main.cs:72 — Main.CreateResultsFromQuery has cyclomatic complexity 21 (threshold 15). Of this number, 20 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.
D1 · Cyclomatic Complexity · MainWindow.OnKeyDown (cyclomatic 20) · ×1
  • MainWindow.OnKeyDown (cyclomatic 20) Flow.Launcher/MainWindow.xaml.cs:470 — MainWindow.OnKeyDown 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.
D1 · Cyclomatic Complexity · Settings.RegisteredHotkeys.get (cyclomatic 19) · ×1
  • Settings.RegisteredHotkeys.get (cyclomatic 19) Flow.Launcher.Infrastructure/UserSettings/Settings.cs:616 — Settings.RegisteredHotkeys.get has cyclomatic complexity 19 (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.
D1 · Cyclomatic Complexity · MainWindow.UpdateClockPanelVisibility (cyclomatic 18) · ×1
  • MainWindow.UpdateClockPanelVisibility (cyclomatic 18) Flow.Launcher/MainWindow.xaml.cs:1297 — MainWindow.UpdateClockPanelVisibility has cyclomatic complexity 18 (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.
D1 · Cyclomatic Complexity · PluginManager.InstallPlugin (cyclomatic 18) · ×1
  • PluginManager.InstallPlugin (cyclomatic 18) Flow.Launcher.Core/Plugin/PluginManager.cs:932 — PluginManager.InstallPlugin 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.
D1 · Cyclomatic Complexity · ExceptionFormatter.GetFrameworkVersionFromRegistry (cyclomatic 17) · ×1
  • ExceptionFormatter.GetFrameworkVersionFromRegistry (cyclomatic 17) Flow.Launcher.Infrastructure/Exception/ExceptionFormatter.cs:108 — ExceptionFormatter.GetFrameworkVersionFromRegistry 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.
D1 · Cyclomatic Complexity · PluginManager.UninstallPluginAsync (cyclomatic 17) · ×1
  • PluginManager.UninstallPluginAsync (cyclomatic 17) Flow.Launcher.Core/Plugin/PluginManager.cs:1057 — PluginManager.UninstallPluginAsync 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.
D1 · Cyclomatic Complexity · Theme.ColorizeWindow (cyclomatic 17) · ×1
  • Theme.ColorizeWindow (cyclomatic 17) Flow.Launcher.Core/Resource/Theme.cs:844 — Theme.ColorizeWindow 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.
D1 · Cyclomatic Complexity · Win32.Result (cyclomatic 17) · ×1
  • Win32.Result (cyclomatic 17) Plugins/Flow.Launcher.Plugin.Program/Programs/Win32.cs:99 — Win32.Result has cyclomatic complexity 17 (threshold 15). Of this number, 15 points are the body's own statements and 2 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.
D1 · Cyclomatic Complexity · QuerySuggestionBoxConverter.Convert (cyclomatic 16) · ×1
  • QuerySuggestionBoxConverter.Convert (cyclomatic 16) Flow.Launcher/Converters/QuerySuggestionBoxConverter.cs:15 — QuerySuggestionBoxConverter.Convert 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.
D1 · Cyclomatic Complexity · MainWindow.WndProc (cyclomatic 16) · ×1
  • MainWindow.WndProc (cyclomatic 16) Flow.Launcher/MainWindow.xaml.cs:637 — MainWindow.WndProc 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.
D10 · Test Quality · Fixed-sleep synchronisation · ×1
  • Fixed-sleep synchronisation: JumpFolder_CancelsWhenHotkeyModifierRemainsHeld Flow.Launcher.Test/WindowsDialogTest.cs:160 — This test starts a background task and then orders itself against it with `Thread.Sleep(100)` — a fixed wait, not a signal that the work is done. Whether it passes depends on how loaded the machine is, which is why a test written this way is green on a developer's box and random in CI. Wait for the event itself instead: the process's own exit or output, a completion handle, or a condition polled to a timeout.
D17 · Explicit Debt · BareSuppressMessage repeated 13 times in 8 files · ×1
  • BareSuppressMessage repeated 13 times in 8 files Flow.Launcher.Infrastructure/DialogJump/DialogJump.cs:488 — The identical BareSuppressMessage (`System.Diagnostics.CodeAnalysis.SuppressMessage`) appears 13 times in 8 files — one decision applied repeatedly (e.g. the same rule silenced on every overload of a fluent API), not 13 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.)
D18 · Solution Shape · Build failed · ×1
  • Build failed — The target solution did not build cleanly (errors: 90), which caps Solution Shape at 3/10 — the most basic shape signal is that it compiles. First errors: CS0103: The name 'Localize' does not exist in the current context.
D2 · Cognitive Complexity · ContextMenu.LoadContextMenus (cognitive 65) · ×1
  • ContextMenu.LoadContextMenus (cognitive 65) Plugins/Flow.Launcher.Plugin.Explorer/ContextMenu.cs:30 — ContextMenu.LoadContextMenus has cognitive complexity 65 (threshold 15). Of this number, 40 points are the body's own statements and 25 belong to 7 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.
D2 · Cognitive Complexity · StringMatcher.FuzzyMatch (cognitive 56) · ×1
  • StringMatcher.FuzzyMatch (cognitive 56) Flow.Launcher.Infrastructure/StringMatcher.cs:61 — StringMatcher.FuzzyMatch has cognitive complexity 56 (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.
D2 · Cognitive Complexity · Main.CreateResultsFromQuery (cognitive 53) · ×1
  • Main.CreateResultsFromQuery (cognitive 53) Plugins/Flow.Launcher.Plugin.ProcessKiller/Main.cs:72 — Main.CreateResultsFromQuery has cognitive complexity 53 (threshold 15). Of this number, 51 points are the body's own statements and 2 belong 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.
D2 · Cognitive Complexity · MainWindow.OnLoaded (cognitive 42) · ×1
  • MainWindow.OnLoaded (cognitive 42) Flow.Launcher/MainWindow.xaml.cs:128 — MainWindow.OnLoaded has cognitive complexity 42 (threshold 15). Most of this is not in the body itself: 15 of the 42 points are its own statements and the rest belongs to 4 function literals inside it that branch (lines 257, 317, 251, …). 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.
D2 · Cognitive Complexity · DialogJump.ForegroundChangeCallback (cognitive 42) · ×1
  • DialogJump.ForegroundChangeCallback (cognitive 42) Flow.Launcher.Infrastructure/DialogJump/DialogJump.cs:488 — DialogJump.ForegroundChangeCallback has cognitive complexity 42 (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.
D2 · Cognitive Complexity · MainViewModel.QueryResultsAsync (cognitive 41) · ×1
  • MainViewModel.QueryResultsAsync (cognitive 41) Flow.Launcher/ViewModel/MainViewModel.cs:1537 — MainViewModel.QueryResultsAsync has cognitive complexity 41 (threshold 15). Of this number, 39 points are the body's own statements and 2 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.
D2 · Cognitive Complexity · PluginsManager.RequestUpdateAsync (cognitive 40) · ×1
  • PluginsManager.RequestUpdateAsync (cognitive 40) Plugins/Flow.Launcher.Plugin.PluginsManager/PluginsManager.cs:244 — PluginsManager.RequestUpdateAsync has cognitive complexity 40 (threshold 15). Most of this is not in the body itself: 8 of the 40 points are its own statements and the rest belongs to 4 function literals inside it that branch (lines 348, 439, 312, …). 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.
D2 · Cognitive Complexity · FilesFolders.TryDeleteDirectoryRobust (cognitive 38) · ×1
  • FilesFolders.TryDeleteDirectoryRobust (cognitive 38) Flow.Launcher.Plugin/SharedCommands/FilesFolders.cs:144 — FilesFolders.TryDeleteDirectoryRobust has cognitive complexity 38 (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.
D2 · Cognitive Complexity · DialogJump.SetupDialogJump (cognitive 38) · ×1
  • DialogJump.SetupDialogJump (cognitive 38) Flow.Launcher.Infrastructure/DialogJump/DialogJump.cs:149 — DialogJump.SetupDialogJump has cognitive complexity 38 (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.
D2 · Cognitive Complexity · ExceptionFormatter.GetFrameworkVersionFromRegistry (cognitive 37) · ×1
  • ExceptionFormatter.GetFrameworkVersionFromRegistry (cognitive 37) Flow.Launcher.Infrastructure/Exception/ExceptionFormatter.cs:108 — ExceptionFormatter.GetFrameworkVersionFromRegistry 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.
D2 · Cognitive Complexity · JsonRPCPluginSettings.CreateSettingPanel (cognitive 30) · ×1
  • JsonRPCPluginSettings.CreateSettingPanel (cognitive 30) Flow.Launcher.Core/Plugin/JsonRPCPluginSettings.cs:156 — JsonRPCPluginSettings.CreateSettingPanel has cognitive complexity 30 (threshold 15). Of this number, 27 points are the body's own statements and 3 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.
D2 · Cognitive Complexity · MainWindow.WndProc (cognitive 29) · ×1
  • MainWindow.WndProc (cognitive 29) Flow.Launcher/MainWindow.xaml.cs:637 — MainWindow.WndProc has cognitive complexity 29 (threshold 15). The drivers above price the dispatch low by construction — a dispatch is charged once however many cases it lists, while each branch inside an arm is charged in full — so most of this count is what the case bodies hold, and the arms are where it can be reduced. To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident.
D2 · Cognitive Complexity · MainViewModel.UpdateResultView (cognitive 26) · ×1
  • MainViewModel.UpdateResultView (cognitive 26) Flow.Launcher/ViewModel/MainViewModel.cs:2469 — MainViewModel.UpdateResultView 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.
D2 · Cognitive Complexity · Win32.Result (cognitive 26) · ×1
  • Win32.Result (cognitive 26) Plugins/Flow.Launcher.Plugin.Program/Programs/Win32.cs:99 — Win32.Result has cognitive complexity 26 (threshold 15). Of this number, 24 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.
D2 · Cognitive Complexity · MainViewModel.SetupDialogJumpAsync (cognitive 25) · ×1
  • MainViewModel.SetupDialogJumpAsync (cognitive 25) Flow.Launcher/ViewModel/MainViewModel.cs:2135 — MainViewModel.SetupDialogJumpAsync has cognitive complexity 25 (threshold 15). Of this number, 17 points are the body's own statements and 8 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.
D2 · Cognitive Complexity · PluginManager.UninstallPluginAsync (cognitive 25) · ×1
  • PluginManager.UninstallPluginAsync (cognitive 25) Flow.Launcher.Core/Plugin/PluginManager.cs:1057 — PluginManager.UninstallPluginAsync 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.
D2 · Cognitive Complexity · Main.NormalizeNumber (cognitive 25) · ×1
  • Main.NormalizeNumber (cognitive 25) Plugins/Flow.Launcher.Plugin.Calculator/Main.cs:256 — Main.NormalizeNumber has cognitive complexity 25 (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.
D2 · Cognitive Complexity · AbstractPluginEnvironment.Setup (cognitive 24) · ×1
  • AbstractPluginEnvironment.Setup (cognitive 24) Flow.Launcher.Core/ExternalPlugins/Environments/AbstractPluginEnvironment.cs:49 — AbstractPluginEnvironment.Setup 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.
D2 · Cognitive Complexity · DialogJump.InvokeShowDialogJumpWindowAsync (cognitive 23) · ×1
  • DialogJump.InvokeShowDialogJumpWindowAsync (cognitive 23) Flow.Launcher.Infrastructure/DialogJump/DialogJump.cs:365 — DialogJump.InvokeShowDialogJumpWindowAsync has cognitive complexity 23 (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.
D2 · Cognitive Complexity · PublicAPIInstance.CopyToClipboard (cognitive 21) · ×1
  • PublicAPIInstance.CopyToClipboard (cognitive 21) Flow.Launcher/PublicAPIInstance.cs:183 — PublicAPIInstance.CopyToClipboard has cognitive complexity 21 (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.
D2 · Cognitive Complexity · HistoryItem.DateTimeAgo (cognitive 21) · ×1
  • HistoryItem.DateTimeAgo (cognitive 21) Flow.Launcher/Storage/HistoryItem.cs:16 — HistoryItem.DateTimeAgo 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.
D2 · Cognitive Complexity · Theme.ColorizeWindow (cognitive 21) · ×1
  • Theme.ColorizeWindow (cognitive 21) Flow.Launcher.Core/Resource/Theme.cs:844 — Theme.ColorizeWindow 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.
D2 · Cognitive Complexity · UWPApp.LogoPathFromUri (cognitive 21) · ×1
  • UWPApp.LogoPathFromUri (cognitive 21) REDACTED:530 — UWPApp.LogoPathFromUri 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.
D2 · Cognitive Complexity · Main.Commands (cognitive 21) · ×1
  • Main.Commands (cognitive 21) Plugins/Flow.Launcher.Plugin.Sys/Main.cs:312 — Main.Commands has cognitive complexity 21 (threshold 15). None of this is in the body itself: all 21 points belong to 6 function literals inside it that branch (lines 323, 348, 373, …). 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.
D2 · Cognitive Complexity · MainWindow.OnKeyDown (cognitive 20) · ×1
  • MainWindow.OnKeyDown (cognitive 20) Flow.Launcher/MainWindow.xaml.cs:470 — MainWindow.OnKeyDown 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.
D2 · Cognitive Complexity · PublicAPIInstance.OpenUri (cognitive 20) · ×1
  • PublicAPIInstance.OpenUri (cognitive 20) Flow.Launcher/PublicAPIInstance.cs:441 — PublicAPIInstance.OpenUri 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.
D2 · Cognitive Complexity · PluginsManager.InstallOrUpdateAsync (cognitive 20) · ×1
  • PluginsManager.InstallOrUpdateAsync (cognitive 20) Plugins/Flow.Launcher.Plugin.PluginsManager/PluginsManager.cs:91 — PluginsManager.InstallOrUpdateAsync has cognitive complexity 20 (threshold 15). Of this number, 19 points are the body's own statements and 1 belongs 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, 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.
D2 · Cognitive Complexity · TranslationHelper.TranslateAllSettings (cognitive 20) · ×1
  • TranslationHelper.TranslateAllSettings (cognitive 20) Plugins/Flow.Launcher.Plugin.WindowsSettings/Helper/TranslationHelper.cs:17 — TranslationHelper.TranslateAllSettings 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.
D2 · Cognitive Complexity · CustomScrollViewerEx.OnMouseWheel (cognitive 19) · ×1
  • CustomScrollViewerEx.OnMouseWheel (cognitive 19) Flow.Launcher/Resources/Controls/CustomScrollViewerEx.cs:86 — CustomScrollViewerEx.OnMouseWheel 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.
D2 · Cognitive Complexity · MainViewModel.SelectedResults.set (cognitive 19) · ×1
  • MainViewModel.SelectedResults.set (cognitive 19) Flow.Launcher/ViewModel/MainViewModel.cs:899 — MainViewModel.SelectedResults.set 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.
D2 · Cognitive Complexity · DialogJump.GetDialogWindow (cognitive 19) · ×1
  • DialogJump.GetDialogWindow (cognitive 19) Flow.Launcher.Infrastructure/DialogJump/DialogJump.cs:899 — DialogJump.GetDialogWindow 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.
D2 · Cognitive Complexity · PinyinAlphabet.BuildCacheFromContent (cognitive 19) · ×1
  • PinyinAlphabet.BuildCacheFromContent (cognitive 19) Flow.Launcher.Infrastructure/PinyinAlphabet.cs:249 — PinyinAlphabet.BuildCacheFromContent 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.
D2 · Cognitive Complexity · Settings.RegisteredHotkeys.get (cognitive 19) · ×1
  • Settings.RegisteredHotkeys.get (cognitive 19) Flow.Launcher.Infrastructure/UserSettings/Settings.cs:616 — Settings.RegisteredHotkeys.get has cognitive complexity 19 (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.
D2 · Cognitive Complexity · SearchManager.SearchAsync (cognitive 19) · ×1
  • SearchManager.SearchAsync (cognitive 19) Plugins/Flow.Launcher.Plugin.Explorer/Search/SearchManager.cs:79 — SearchManager.SearchAsync 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.
D2 · Cognitive Complexity · ResultHelper.GetResultList (cognitive 19) · ×1
  • ResultHelper.GetResultList (cognitive 19) Plugins/Flow.Launcher.Plugin.WindowsSettings/Helper/ResultHelper.cs:40 — ResultHelper.GetResultList 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.
D2 · Cognitive Complexity · Http.DownloadAsync (cognitive 18) · ×1
  • Http.DownloadAsync (cognitive 18) REDACTED:84 — Http.DownloadAsync 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.
D2 · Cognitive Complexity · JsonRPCPluginSettings.InitializeAsync (cognitive 18) · ×1
  • JsonRPCPluginSettings.InitializeAsync (cognitive 18) Flow.Launcher.Core/Plugin/JsonRPCPluginSettings.cs:39 — JsonRPCPluginSettings.InitializeAsync 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.
D2 · Cognitive Complexity · PluginManager.InstallPlugin (cognitive 18) · ×1
  • PluginManager.InstallPlugin (cognitive 18) Flow.Launcher.Core/Plugin/PluginManager.cs:932 — PluginManager.InstallPlugin has cognitive complexity 18 (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.
D2 · Cognitive Complexity · Main.Query (cognitive 18) · ×1
  • Main.Query (cognitive 18) Plugins/Flow.Launcher.Plugin.Calculator/Main.cs:49 — Main.Query has cognitive complexity 18 (threshold 15). Of this number, 16 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.
D2 · Cognitive Complexity · ResultManager.CreateFolderResult (cognitive 18) · ×1
  • ResultManager.CreateFolderResult (cognitive 18) Plugins/Flow.Launcher.Plugin.Explorer/Search/ResultManager.cs:137 — ResultManager.CreateFolderResult has cognitive complexity 18 (threshold 15). Most of this is not in the body itself: 5 of the 18 points are its own statements and the rest belongs to one function literal inside it that branches (line 157). The decisions are inside the literal, 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 literal's work into a named function or method at the enclosing scope and have the literal call it, then reduce whichever part then reads as the largest.
D2 · Cognitive Complexity · CustomWindowTitleBar.UpdateElementsVisibility (cognitive 17) · ×1
  • CustomWindowTitleBar.UpdateElementsVisibility (cognitive 17) Flow.Launcher/Resources/Controls/CustomWindowTitleBar.xaml.cs:326 — CustomWindowTitleBar.UpdateElementsVisibility 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.
D2 · Cognitive Complexity · MainViewModel.Hide (cognitive 17) · ×1
  • MainViewModel.Hide (cognitive 17) Flow.Launcher/ViewModel/MainViewModel.cs:2372 — MainViewModel.Hide has cognitive complexity 17 (threshold 15). Of this number, 13 points are the body's own statements and 4 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.
D2 · Cognitive Complexity · PluginConfig.Parse (cognitive 17) · ×1
  • PluginConfig.Parse (cognitive 17) Flow.Launcher.Core/Plugin/PluginConfig.cs:23 — PluginConfig.Parse 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.
D2 · Cognitive Complexity · Updater.UpdateAppAsync (cognitive 17) · ×1
  • Updater.UpdateAppAsync (cognitive 17) Flow.Launcher.Core/Updater.cs:38 — Updater.UpdateAppAsync 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.
D2 · Cognitive Complexity · Main.Query (cognitive 17) · ×1
  • Main.Query (cognitive 17) Plugins/Flow.Launcher.Plugin.Shell/Main.cs:29 — Main.Query has cognitive complexity 17 (threshold 15). Of this number, 15 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.
D2 · Cognitive Complexity · EverythingHelper.EverythingHighlightStringToHighlightList (cognitive 17) · ×1
  • EverythingHelper.EverythingHighlightStringToHighlightList (cognitive 17) Plugins/Flow.Launcher.Plugin.Explorer/Search/Everything/EverythingHelper.cs:54 — EverythingHelper.EverythingHighlightStringToHighlightList 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.
D2 · Cognitive Complexity · MainViewModel.QueryContextMenu (cognitive 16) · ×1
  • MainViewModel.QueryContextMenu (cognitive 16) Flow.Launcher/ViewModel/MainViewModel.cs:1382 — MainViewModel.QueryContextMenu has cognitive complexity 16 (threshold 15). Of this number, 9 points are the body's own statements and 7 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.
D2 · Cognitive Complexity · AbstractPluginEnvironment.PreStartPluginExecutablePathUpdate (cognitive 16) · ×1
  • AbstractPluginEnvironment.PreStartPluginExecutablePathUpdate (cognitive 16) Flow.Launcher.Core/ExternalPlugins/Environments/AbstractPluginEnvironment.cs:182 — AbstractPluginEnvironment.PreStartPluginExecutablePathUpdate 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.
D2 · Cognitive Complexity · UWPApp.Result (cognitive 16) · ×1
  • UWPApp.Result (cognitive 16) REDACTED:397 — UWPApp.Result has cognitive complexity 16 (threshold 15). Of this number, 12 points are the body's own statements and 4 belong to one function literal inside it that branches. 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.
D2 · Cognitive Complexity · Main.QueryAsync (cognitive 16) · ×1
  • Main.QueryAsync (cognitive 16) Plugins/Flow.Launcher.Plugin.WebSearch/Main.cs:30 — Main.QueryAsync has cognitive complexity 16 (threshold 15). Of this number, 14 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.
D2 · Cognitive Complexity · update_release_pr.get_prs (cognitive 16) · ×1
  • update_release_pr.get_prs (cognitive 16) .github/update_release_pr.py:58 — update_release_pr.get_prs has cognitive complexity 16 (threshold 15). Drivers by points: if/else 5 (11 pts), boolean chains 2, ternaries 2, loops 1 (nesting depth added 6). 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.
D29 · Static Analysis (SAST) · REDACTED · ×1
  • REDACTED
D36 · Supply-chain Provenance & Signing · REDACTED · ×1
  • REDACTED
D36 · Supply-chain Provenance & Signing REDACTED · ×1
  • REDACTED
D36 · Supply-chain Provenance & Signing REDACTED · ×1
  • REDACTED
D36 · Supply-chain Provenance & Signing · REDACTED · ×1
  • REDACTED
D4 · Code Duplication · Members sharing a duplicated core (6 members, 50+ identical tokens) · ×1
  • Members sharing a duplicated core (6 members, 50+ identical tokens) Plugins/Flow.Launcher.Plugin.Explorer/Views/PreviewPanel.xaml.cs:105 — Plugins/Flow.Launcher.Plugin.Explorer/Views/PreviewPanel.xaml.cs:105-126 | Plugins/Flow.Launcher.Plugin.Explorer/Views/PreviewPanel.xaml.cs:129-157 | Plugins/Flow.Launcher.Plugin.Explorer/Views/PreviewPanel.xaml.cs:160-188 | Plugins/Flow.Launcher.Plugin.Explorer/Views/PreviewPanel.xaml.cs:191-244 | Plugins/Flow.Launcher.Plugin.Explorer/Views/PreviewPanel.xaml.cs:247-275 | Plugins/Flow.Launcher.Plugin.Explorer/Views/PreviewPanel.xaml.cs:278-306 — 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.
D4 · Code Duplication · Members sharing a duplicated core (4 members, 50+ identical tokens) · ×1
  • Members sharing a duplicated core (4 members, 50+ identical tokens) Flow.Launcher.Plugin/SharedModels/MonitorInfo.cs:25 — Flow.Launcher.Plugin/SharedModels/MonitorInfo.cs:25-41 | Flow.Launcher.Plugin/SharedModels/MonitorInfo.cs:49-69 | Flow.Launcher.Plugin/SharedModels/MonitorInfo.cs:76-96 | Flow.Launcher.Plugin/SharedModels/MonitorInfo.cs:103-127 — These 4 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 4 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 4 times.
D4 · Code Duplication · Duplicated block (31 lines × 2) · ×1
  • Duplicated block (31 lines × 2) Plugins/Flow.Launcher.Plugin.Explorer/Helper/ShellContextMenu.cs:1329 — Plugins/Flow.Launcher.Plugin.Explorer/Helper/ShellContextMenu.cs:1329-1359 | Plugins/Flow.Launcher.Plugin.Explorer/Helper/ShellContextMenu.cs:1367-1397 — 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.
D4 · Code Duplication · Duplicated block (28 lines × 2) · ×1
  • Duplicated block (28 lines × 2) Flow.Launcher.Core/Plugin/PluginManager.cs:420 — Flow.Launcher.Core/Plugin/PluginManager.cs:420-447 | Flow.Launcher.Core/Plugin/PluginManager.cs:486-513 — 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 `Flow.Launcher.Core/Plugin/PluginManager.cs:420` 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.
D4 · Code Duplication · Duplicated block (26 lines × 2) · ×1
  • Duplicated block (26 lines × 2) Flow.Launcher.Infrastructure/DialogJump/DialogJump.cs:168 — Flow.Launcher.Infrastructure/DialogJump/DialogJump.cs:168-193 | Flow.Launcher.Infrastructure/DialogJump/DialogJump.cs:278-303 — 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.
D4 · Code Duplication · Duplicated block (26 lines × 3) · ×1
  • Duplicated block (26 lines × 3) Flow.Launcher.Core/Plugin/PluginConfig.cs:151 — Flow.Launcher.Core/Plugin/PluginConfig.cs:151-176 | Flow.Launcher.Core/Plugin/PluginInstaller.cs:513-538 | Plugins/Flow.Launcher.Plugin.PluginsManager/PluginsManager.cs:858-883 — 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.
D4 · Code Duplication · Duplicated block (25 lines × 2) · ×1
  • Duplicated block (25 lines × 2) Flow.Launcher/Msg.xaml.cs:67 — Flow.Launcher/Msg.xaml.cs:67-91 | Flow.Launcher/MsgWithButton.xaml.cs:69-93 — before extracting anything, compare `Flow.Launcher/Msg.xaml.cs` and `Flow.Launcher/MsgWithButton.xaml.cs` as WHOLE FILES: 86% 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. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `Flow.Launcher/Msg.xaml.cs:67` 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `Flow.Launcher/MsgWithButton.xaml.cs:68` calls `buttonAction` and `Flow.Launcher/Msg.xaml.cs:66` 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.
D4 · Code Duplication · Duplicated block (24 lines × 2) · ×1
  • Duplicated block (24 lines × 2) Flow.Launcher/Msg.xaml.cs:18 — Flow.Launcher/Msg.xaml.cs:18-41 | Flow.Launcher/MsgWithButton.xaml.cs:18-41 — before extracting anything, compare `Flow.Launcher/Msg.xaml.cs` and `Flow.Launcher/MsgWithButton.xaml.cs` as WHOLE FILES: 86% 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. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — 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.
D4 · Code Duplication · Duplicated block (22 lines × 3) · ×1
  • Duplicated block (22 lines × 3) Plugins/Flow.Launcher.Plugin.Explorer/Helper/ShellContextMenu.cs:1298 — Plugins/Flow.Launcher.Plugin.Explorer/Helper/ShellContextMenu.cs:1298-1319 | Plugins/Flow.Launcher.Plugin.Explorer/Helper/ShellContextMenu.cs:1328-1349 | Plugins/Flow.Launcher.Plugin.Explorer/Helper/ShellContextMenu.cs:1366-1387 — 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 `Plugins/Flow.Launcher.Plugin.Explorer/Helper/ShellContextMenu.cs:1298` 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.
D4 · Code Duplication · Duplicated block (19 lines × 2) · ×1
  • Duplicated block (19 lines × 2) Plugins/Flow.Launcher.Plugin.Explorer/Helper/ShellContextMenuDisplayHelper.cs:182 — Plugins/Flow.Launcher.Plugin.Explorer/Helper/ShellContextMenuDisplayHelper.cs:182-200 | Plugins/Flow.Launcher.Plugin.Explorer/Helper/ShellContextMenuDisplayHelper.cs:259-277 — 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 `Plugins/Flow.Launcher.Plugin.Explorer/Helper/ShellContextMenuDisplayHelper.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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `Plugins/Flow.Launcher.Plugin.Explorer/Helper/ShellContextMenuDisplayHelper.cs:281` calls `Sleep` and `Plugins/Flow.Launcher.Plugin.Explorer/Helper/ShellContextMenuDisplayHelper.cs:202` 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.
D4 · Code Duplication · Duplicated block (16 lines × 2) · ×1
  • Duplicated block (16 lines × 2) Flow.Launcher.Core/Plugin/PluginInstaller.cs:56 — Flow.Launcher.Core/Plugin/PluginInstaller.cs:56-71 | Flow.Launcher.Core/Plugin/PluginInstaller.cs:221-236 — 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 `Flow.Launcher.Core/Plugin/PluginInstaller.cs:56` 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.
D4 · Code Duplication · Duplicated block (17 lines × 2) · ×1
  • Duplicated block (17 lines × 2) Flow.Launcher.Core/ExternalPlugins/Environments/TypeScriptEnvironment.cs:37 — Flow.Launcher.Core/ExternalPlugins/Environments/TypeScriptEnvironment.cs:37-53 | Flow.Launcher.Core/ExternalPlugins/Environments/TypeScriptV2Environment.cs:37-53 — before extracting anything, compare `Flow.Launcher.Core/ExternalPlugins/Environments/TypeScriptEnvironment.cs` and `Flow.Launcher.Core/ExternalPlugins/Environments/TypeScriptV2Environment.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. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — 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.
D4 · Code Duplication · Duplicated block (15 lines × 3) · ×1
  • Duplicated block (15 lines × 3) Flow.Launcher.Infrastructure/DialogJump/DialogJump.cs:179 — Flow.Launcher.Infrastructure/DialogJump/DialogJump.cs:179-193 | Flow.Launcher.Infrastructure/DialogJump/DialogJump.cs:289-303 | Flow.Launcher.Infrastructure/DialogJump/DialogJump.cs:1066-1080 — 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.
D4 · Code Duplication · Duplicated block (14 lines × 2) · ×1
  • Duplicated block (14 lines × 2) Flow.Launcher.Core/Plugin/PluginManager.cs:516 — Flow.Launcher.Core/Plugin/PluginManager.cs:516-529 | Flow.Launcher.Core/Plugin/PluginManager.cs:552-565 — 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 `Flow.Launcher.Core/Plugin/PluginManager.cs:516` 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.
D4 · Code Duplication · Duplicated block (12 lines × 3) · ×1
  • Duplicated block (12 lines × 3) Plugins/Flow.Launcher.Plugin.Explorer/Views/PreviewPanel.xaml.cs:111 — Plugins/Flow.Launcher.Plugin.Explorer/Views/PreviewPanel.xaml.cs:111-122 | Plugins/Flow.Launcher.Plugin.Explorer/Views/PreviewPanel.xaml.cs:142-153 | Plugins/Flow.Launcher.Plugin.Explorer/Views/PreviewPanel.xaml.cs:173-184 — 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 `Plugins/Flow.Launcher.Plugin.Explorer/Views/PreviewPanel.xaml.cs:111` 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.
D4 · Code Duplication · Duplicated block (14 lines × 4) · ×1
  • Duplicated block (14 lines × 4) Flow.Launcher/Resources/Controls/CodeHighlightTheme.cs:83 — Flow.Launcher/Resources/Controls/CodeHighlightTheme.cs:83-96 | Flow.Launcher/Resources/Controls/CodeHighlightTheme.cs:99-112 | Flow.Launcher/Resources/Controls/CodeHighlightTheme.cs:115-128 | Flow.Launcher/Resources/Controls/CodeHighlightTheme.cs:132-145 — all 4 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 `Flow.Launcher/Resources/Controls/CodeHighlightTheme.cs:83` 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.
D4 · Code Duplication · Duplicated block (13–14 lines × 2) · ×1
  • Duplicated block (13–14 lines × 2) Flow.Launcher.Core/Resource/Internationalization.cs:402 — Flow.Launcher.Core/Resource/Internationalization.cs:402-414 | Flow.Launcher.Core/Resource/Internationalization.cs:418-431 — 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. 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.
D4 · Code Duplication · Duplicated block (10 lines × 4) · ×1
  • Duplicated block (10 lines × 4) Plugins/Flow.Launcher.Plugin.Explorer/Views/PreviewPanel.xaml.cs:134 — Plugins/Flow.Launcher.Plugin.Explorer/Views/PreviewPanel.xaml.cs:134-143 | Plugins/Flow.Launcher.Plugin.Explorer/Views/PreviewPanel.xaml.cs:165-174 | Plugins/Flow.Launcher.Plugin.Explorer/Views/PreviewPanel.xaml.cs:252-261 | Plugins/Flow.Launcher.Plugin.Explorer/Views/PreviewPanel.xaml.cs:283-292 — all 4 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 `Plugins/Flow.Launcher.Plugin.Explorer/Views/PreviewPanel.xaml.cs:134` 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.
D4 · Code Duplication · Duplicated block (11 lines × 3) · ×1
  • Duplicated block (11 lines × 3) Flow.Launcher.Plugin/SharedModels/MonitorInfo.cs:57 — Flow.Launcher.Plugin/SharedModels/MonitorInfo.cs:57-67 | Flow.Launcher.Plugin/SharedModels/MonitorInfo.cs:84-94 | Flow.Launcher.Plugin/SharedModels/MonitorInfo.cs:115-125 — 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 `Flow.Launcher.Plugin/SharedModels/MonitorInfo.cs:57` 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.
D4 · Code Duplication · Duplicated block (10 lines × 3) · ×1
  • Duplicated block (10 lines × 3) Plugins/Flow.Launcher.Plugin.Explorer/Views/PreviewPanel.xaml.cs:205 — Plugins/Flow.Launcher.Plugin.Explorer/Views/PreviewPanel.xaml.cs:205-214 | Plugins/Flow.Launcher.Plugin.Explorer/Views/PreviewPanel.xaml.cs:260-269 | Plugins/Flow.Launcher.Plugin.Explorer/Views/PreviewPanel.xaml.cs:291-300 — 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 `Plugins/Flow.Launcher.Plugin.Explorer/Views/PreviewPanel.xaml.cs:205` 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.
D4 · Code Duplication · Duplicated block (11 lines × 4) · ×1
  • Duplicated block (11 lines × 4) Flow.Launcher.Plugin/SharedModels/MonitorInfo.cs:31 — Flow.Launcher.Plugin/SharedModels/MonitorInfo.cs:31-41 | Flow.Launcher.Plugin/SharedModels/MonitorInfo.cs:59-69 | Flow.Launcher.Plugin/SharedModels/MonitorInfo.cs:86-96 | Flow.Launcher.Plugin/SharedModels/MonitorInfo.cs:117-127 — all 4 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 `Flow.Launcher.Plugin/SharedModels/MonitorInfo.cs:31` 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.
D4 · Code Duplication · Duplicated block (4–11 lines × 3) · ×1
  • Duplicated block (4–11 lines × 3) Flow.Launcher.Core/Resource/Theme.cs:214 — Flow.Launcher.Core/Resource/Theme.cs:214-224 | Flow.Launcher.Core/Resource/Theme.cs:272-281 | Flow.Launcher.Core/Resource/Theme.cs:284-287 — 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.
D4 · Code Duplication · Duplicated block (6 lines × 2) · ×1
  • Duplicated block (6 lines × 2) Plugins/Flow.Launcher.Plugin.Explorer/Search/ResultManager.cs:428 — Plugins/Flow.Launcher.Plugin.Explorer/Search/ResultManager.cs:428-433 | Plugins/Flow.Launcher.Plugin.Explorer/Search/ResultManager.cs:444-449 — 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 `Plugins/Flow.Launcher.Plugin.Explorer/Search/ResultManager.cs:428` 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.
D4 · Code Duplication · Duplicated block (32 lines × 2) · ×1
  • Duplicated block (32 lines × 2) Flow.Launcher.Core/Plugin/PluginInstaller.cs:430 — Flow.Launcher.Core/Plugin/PluginInstaller.cs:430-461 | Plugins/Flow.Launcher.Plugin.PluginsManager/PluginsManager.cs:211-242 — 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.
D8 · Code Coverage · Coverage not measured · ×1
  • Coverage not measured — no coverage collector is wired up — Coverage NOT MEASURED: `--collect:"XPlat Code Coverage"` names a data collector that ships in the `coverlet.collector` package, and this repository wires up none — no test project references it and no runsettings declares one. The absence of coverage here is therefore not evidence about the suite or about our analyzer environment: without a collector, `--collect` produces nothing even from a suite that builds and passes. Add a `coverlet.collector` PackageReference to the test project(s) (or commit the Cobertura/OpenCover/lcov report your CI produces) and real coverage will be measured. It is excluded from the score rather than counted as a near-zero defect.
IC1 · Incompleteness & stubs · Condition was already decided · ×1
  • Condition was already decided — an earlier guard makes this test constant Plugins/Flow.Launcher.Plugin.Explorer/Search/SearchManager.cs:249 — Control only reaches here when `token.IsCancellationRequested` is false, because the guard on line 227 exits otherwise. This test is therefore always false and everything it guards is unreachable. Implement the distinction that was intended, or delete the test.
S1 · Cryptographic Hygiene · Obsolete TLS/SSL protocol version enabled · ×1
  • Obsolete TLS/SSL protocol version enabled REDACTED:25 — `SecurityProtocol` explicitly selects `SecurityProtocolType.Tls`, a protocol version that is broken (SSL 2.0/3.0) or withdrawn (TLS 1.0/1.1, RFC 8996). Offering an obsolete version does not merely permit it — it is what a downgrade attack negotiates, so the weakest version on the list is the one that decides the connection's strength. Stop pinning versions here: leave the protocol unset (`SecurityProtocolType.SystemDefault`, or simply do not assign it) so the connection uses the OS policy and picks up TLS 1.3 and future versions without a code change. Where a version must be named explicitly, name `Tls12` and `Tls13` only.
X18 · Disposal-pattern correctness · Disposes a dependency it does not own · ×1
  • Disposes a dependency it does not own Flow.Launcher/Resources/Controls/PreviewMarkdownScrollViewer.cs:434 — `_inner` is never created by `ThemedHighlighter` — every assignment to it takes a constructor parameter — yet this type disposes it here (line 434). Its declared type `IHighlighter` is an interface, so the instance came from whoever resolved it, and that owner decides when it ends. Disposing it from here reaches outside this object's lifetime: a dependency shared with the rest of the process is torn down when THIS instance goes away, and the real owner's later `Dispose()` runs a second time on an object already disposed. Drop the call — a type disposes what it constructed, and only that. If this dependency genuinely is exclusive to this instance, construct it here (or take an owned factory) so the ownership is stated in the code rather than assumed.
Minor — 110 finding(s)
IC1 · Incompleteness & stubs · Commented-out code · ×31
  • Commented-out code Flow.Launcher/Helper/ErrorReporting.cs:49 — A line of code has been commented out rather than removed — dead weight that rots and confuses. Delete it (version control remembers).
  • Commented-out code Flow.Launcher/Resources/Controls/HotkeyDisplay.xaml.cs:18 — A line of code has been commented out rather than removed — dead weight that rots and confuses. Delete it (version control remembers).
  • Commented-out code Flow.Launcher/Settings.cs:15 — A line of code has been commented out rather than removed — dead weight that rots and confuses. Delete it (version control remembers).
  • Commented-out code Flow.Launcher/Settings.cs:17 — A line of code has been commented out rather than removed — dead weight that rots and confuses. Delete it (version control remembers).
  • Commented-out code Flow.Launcher/ViewModel/MainViewModel.cs:533 — A line of code has been commented out rather than removed — dead weight that rots and confuses. Delete it (version control remembers).
  • Commented-out code Flow.Launcher/ViewModel/MainViewModel.cs:537 — A line of code has been commented out rather than removed — dead weight that rots and confuses. Delete it (version control remembers).
  • Commented-out code Flow.Launcher/ViewModel/MainViewModel.cs:1621 — 7 consecutive lines of code sit inside a `/* … */` block — a block of code switched off rather than removed, which rots and confuses. Delete it (version control remembers).
  • Commented-out code Plugins/Flow.Launcher.Plugin.Explorer/Helper/ShellContextMenu.cs:549 — A line of code has been commented out rather than removed — dead weight that rots and confuses. Delete it (version control remembers).
  • Commented-out code Plugins/Flow.Launcher.Plugin.Explorer/Search/WindowsIndex/QueryConstructor.cs:35 — A line of code has been commented out rather than removed — dead weight that rots and confuses. Delete it (version control remembers).
  • Commented-out code REDACTED:570 — A line of code has been commented out rather than removed — dead weight that rots and confuses. Delete it (version control remembers).
  • Commented-out code REDACTED:643 — A line of code has been commented out rather than removed — dead weight that rots and confuses. Delete it (version control remembers).
  • Commented-out code REDACTED:644 — A line of code has been commented out rather than removed — dead weight that rots and confuses. Delete it (version control remembers).
  • Commented-out code REDACTED:654 — A line of code has been commented out rather than removed — dead weight that rots and confuses. Delete it (version control remembers).
  • Commented-out code REDACTED:675 — A line of code has been commented out rather than removed — dead weight that rots and confuses. Delete it (version control remembers).
  • Commented-out code REDACTED:676 — A line of code has been commented out rather than removed — dead weight that rots and confuses. Delete it (version control remembers).
  • Commented-out code REDACTED:677 — A line of code has been commented out rather than removed — dead weight that rots and confuses. Delete it (version control remembers).
  • Commented-out code REDACTED:678 — A line of code has been commented out rather than removed — dead weight that rots and confuses. Delete it (version control remembers).
  • Commented-out code REDACTED:680 — A line of code has been commented out rather than removed — dead weight that rots and confuses. Delete it (version control remembers).
  • Commented-out code REDACTED:682 — A line of code has been commented out rather than removed — dead weight that rots and confuses. Delete it (version control remembers).
  • Commented-out code REDACTED:685 — A line of code has been commented out rather than removed — dead weight that rots and confuses. Delete it (version control remembers).
  • Commented-out code REDACTED:686 — A line of code has been commented out rather than removed — dead weight that rots and confuses. Delete it (version control remembers).
  • Commented-out code REDACTED:687 — A line of code has been commented out rather than removed — dead weight that rots and confuses. Delete it (version control remembers).
  • Commented-out code REDACTED:688 — A line of code has been commented out rather than removed — dead weight that rots and confuses. Delete it (version control remembers).
  • Commented-out code REDACTED:689 — A line of code has been commented out rather than removed — dead weight that rots and confuses. Delete it (version control remembers).
  • Commented-out code REDACTED:690 — A line of code has been commented out rather than removed — dead weight that rots and confuses. Delete it (version control remembers).
  • + 6 more in this group — see findings.md.
X4 · Structured logging · Interpolated log message defeats structured logging · ×17
  • Interpolated log message defeats structured logging Plugins/Flow.Launcher.Plugin.Program/Programs/ShellLinkReader.cs:36 — 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 Plugins/Flow.Launcher.Plugin.Program/Programs/ShellLinkReader.cs:70 — 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 Plugins/Flow.Launcher.Plugin.Program/Programs/ShellLinkReader.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 Plugins/Flow.Launcher.Plugin.Program/Programs/ShellLinkReader.cs:140 — 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 REDACTED:62 — 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 REDACTED:121 — 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 REDACTED:163 — 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 REDACTED:170 — 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 REDACTED:539 — 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 REDACTED:578 — 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 REDACTED:620 — 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 REDACTED:628 — 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 Plugins/Flow.Launcher.Plugin.Program/Programs/Win32.cs:318 — 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 Plugins/Flow.Launcher.Plugin.Program/Programs/Win32.cs:374 — 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 Plugins/Flow.Launcher.Plugin.Program/Programs/Win32.cs:442 — 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 Plugins/Flow.Launcher.Plugin.Program/Programs/Win32.cs:449 — 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 Plugins/Flow.Launcher.Plugin.Program/Programs/Win32.cs:585 — 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.
X10 · Duplicated predicate · Duplicated predicate · ×14
  • Duplicated predicate Flow.Launcher.Core/Plugin/PluginInstaller.cs:483 — `!Uri.TryCreate(url, UriKind.Absolute, out var uri) || uri.Host != acceptedHost` appears character-identically in 2 files — Flow.Launcher.Core/Plugin/PluginInstaller.cs, Plugins/Flow.Launcher.Plugin.PluginsManager/PluginsManager.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 REDACTED:428 — `!matchResult.IsSearchPrecisionScoreMet() && !string.IsNullOrEmpty(query)` appears character-identically in 2 files — REDACTED, Plugins/Flow.Launcher.Plugin.Program/Programs/Win32.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 Plugins/Flow.Launcher.Plugin.WebSearch/SearchSourceSetting.xaml.cs:174 — `!string.IsNullOrEmpty(text) && text.Any(char.IsWhiteSpace)` appears character-identically in 2 files — Plugins/Flow.Launcher.Plugin.Explorer/Views/ActionKeywordSetting.xaml.cs, Plugins/Flow.Launcher.Plugin.WebSearch/SearchSourceSetting.xaml.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 Flow.Launcher.Core/Plugin/PluginInstaller.cs:487 — `!string.IsNullOrEmpty(x.Metadata.Website) && x.Metadata.Website.StartsWith(constructedUrlPart)` appears character-identically in 2 files — Flow.Launcher.Core/Plugin/PluginInstaller.cs, Plugins/Flow.Launcher.Plugin.PluginsManager/PluginsManager.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 Flow.Launcher.Core/Plugin/PluginInstaller.cs:500 — `TryParseSemanticVersion(currentVersion, out var current) && TryParseSemanticVersion(latestVersion, out var latest)` appears character-identically in 2 files — Flow.Launcher.Core/Plugin/PluginInstaller.cs, Plugins/Flow.Launcher.Plugin.PluginsManager/PluginsManager.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 Flow.Launcher.Core/ExternalPlugins/CommunityPluginSource.cs:84 — `e is HttpRequestException or WebException or SocketException || e.InnerException is TimeoutException` appears character-identically in 2 files — Flow.Launcher.Core/ExternalPlugins/CommunityPluginSource.cs, Flow.Launcher.Core/Updater.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 Flow.Launcher/ViewModel/MainViewModel.cs:1062 — `e is NotSupportedException || e is InvalidEnumArgumentException` appears character-identically in 2 files — Flow.Launcher.Infrastructure/Hotkey/HotkeyModel.cs, Flow.Launcher/ViewModel/MainViewModel.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 Flow.Launcher/SettingPages/Views/SettingsPanePlugins.xaml.cs:63 — `e.Key is not Key.F || Keyboard.Modifiers is not ModifierKeys.Control` appears character-identically in 2 files — Flow.Launcher/SettingPages/Views/SettingsPanePluginStore.xaml.cs, Flow.Launcher/SettingPages/Views/SettingsPanePlugins.xaml.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 Plugins/Flow.Launcher.Plugin.Explorer/Search/Everything/EverythingSearchManager.cs:146 — `ex is DllNotFoundException || ex is EntryPointNotFoundException` appears character-identically in 2 files — Plugins/Flow.Launcher.Plugin.Explorer/Search/Everything/EverythingSearchManager.cs, Plugins/Flow.Launcher.Plugin.Explorer/ViewModels/SettingsViewModel.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 Flow.Launcher.Core/Plugin/PluginInstaller.cs:454 — `exceptionHappened && (!cts.IsCancellationRequested)` appears character-identically in 2 files — Flow.Launcher.Core/Plugin/PluginInstaller.cs, Plugins/Flow.Launcher.Plugin.PluginsManager/PluginsManager.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 Flow.Launcher/HotkeyControl.xaml.cs:318 — `hotkey == null || hotkey == default(HotkeyModel)` appears character-identically in 2 files — Flow.Launcher/HotkeyControl.xaml.cs, Flow.Launcher/HotkeyControlDialog.xaml.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 Flow.Launcher/HotkeyControl.xaml.cs:235 — `hotkey.Validate(validateKeyGesture) && HotKeyMapper.CheckAvailability(hotkey)` appears character-identically in 2 files — Flow.Launcher/HotkeyControl.xaml.cs, Flow.Launcher/HotkeyControlDialog.xaml.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 Flow.Launcher/Storage/LastOpenedHistoryResult.cs:132 — `string.IsNullOrEmpty(RecordKey) || string.IsNullOrEmpty(r.RecordKey)` appears character-identically in 2 files — Flow.Launcher/Storage/LastOpenedHistoryResult.cs, Flow.Launcher/Storage/TopMostRecord.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 Flow.Launcher.Core/Plugin/PluginManager.cs:868 — `unzippedFolderCount == 1 && unzippedFilesCount == 0` appears character-identically in 2 files — Flow.Launcher.Core/Plugin/PluginManager.cs, Plugins/Flow.Launcher.Plugin.PluginsManager/Utilities.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.
X7 · Silent fallback defaults · Silent fallback default in catch · ×10
  • Silent fallback default in catch Flow.Launcher/SettingPages/ViewModels/SettingsPaneProxyViewModel.cs:51 — `TestProxyAsync` swallows every exception into `return "proxyConnectFailed";` — a data error becomes a silent behavior change with no trail. Log the failure or let validation throw.
  • Silent fallback default in catch Flow.Launcher/ViewModel/SelectFileManagerViewModel.cs:96 — `IsFileManagerValid` 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 Flow.Launcher.Infrastructure/Exception/ExceptionFormatter.cs:200 — `GetWindowsRevisionFromRegistry` swallows every exception into `return "0";` — a data error becomes a silent behavior change with no trail. Log the failure or let validation throw.
  • Silent fallback default in catch Flow.Launcher.Infrastructure/Storage/JsonStorage.cs:114 — `TryLoadBackupAsync` swallows `JsonException` into `return default;` — a data error becomes a silent behavior change with no trail. Log the failure or let validation throw.
  • Silent fallback default in catch Flow.Launcher.Infrastructure/Storage/JsonStorage.cs:194 — `TryLoadBackup` swallows `JsonException` into `return default;` — a data error becomes a silent behavior change with no trail. Log the failure or let validation throw.
  • Silent fallback default in catch Flow.Launcher.Core/Resource/FontHelper.cs:19 — `GetFontWeightFromInvariantStringOrNormal` swallows every exception into `return FontWeights.Normal;` — a data error becomes a silent behavior change with no trail. Log the failure or let validation throw.
  • Silent fallback default in catch Flow.Launcher.Core/Resource/FontHelper.cs:33 — `GetFontStyleFromInvariantStringOrNormal` swallows every exception into `return FontStyles.Normal;` — a data error becomes a silent behavior change with no trail. Log the failure or let validation throw.
  • Silent fallback default in catch Flow.Launcher.Core/Resource/FontHelper.cs:47 — `GetFontStretchFromInvariantStringOrNormal` swallows every exception into `return FontStretches.Normal;` — a data error becomes a silent behavior change with no trail. Log the failure or let validation throw.
  • Silent fallback default in catch Plugins/Flow.Launcher.Plugin.Explorer/Main.cs:126 — `QueryDialogJumpAsync` swallows `Exception` into `return _emptyDialogJumpResultList;` — a data error becomes a silent behavior change with no trail. Log the failure or let validation throw.
  • Silent fallback default in catch Plugins/Flow.Launcher.Plugin.ProcessKiller/ProcessHelper.cs:181 — `TryGetProcessFilename` swallows every exception into `return string.Empty;` — a data error becomes a silent behavior change with no trail. Log the failure or let validation throw.
D34 · Knowledge Freshness · Orphaned file · ×8
  • Orphaned file Plugins/Flow.Launcher.Plugin.Explorer/Helper/ShellContextMenuDisplayHelper.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 Flow.Launcher.Infrastructure/Exception/ExceptionFormatter.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 Flow.Launcher/HotkeyControlDialog.xaml.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 Flow.Launcher.Infrastructure/Hotkey/RegisteredHotkeyData.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 Flow.Launcher.Core/Plugin/PythonPlugin.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 Plugins/Flow.Launcher.Plugin.WindowsSettings/Helper/UnsupportedSettingsHelper.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 Flow.Launcher.Core/Resource/FontHelper.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 Flow.Launcher.Core/ExternalPlugins/CommunityPluginStore.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.
D12 · Dependency Hygiene · Deprecated · ×5
  • Deprecated: System.Reflection.Metadata Flow.Launcher/packages.lock.json:1230 — System.Reflection.Metadata 5.0.0 — Other,Legacy. It is resolved transitively in Flow.Launcher/packages.lock.json: no project of this repository references it directly, so the move is on the reference that pulls it in.
  • Deprecated: YamlDotNet Flow.Launcher/packages.lock.json:1611 — YamlDotNet 9.1.0 — CriticalBugs — the publisher's replacement is `YamlDotNet` >= 9.1.2; migrate the reference to it. It is resolved transitively in Flow.Launcher/packages.lock.json: no project of this repository references it directly, so the move is on the reference that pulls it in.
  • Deprecated: System.Reflection.Metadata Flow.Launcher.Infrastructure/packages.lock.json:197 — System.Reflection.Metadata 5.0.0 — Other,Legacy. It is resolved transitively in Flow.Launcher.Infrastructure/packages.lock.json: no project of this repository references it directly, so the move is on the reference that pulls it in.
  • Deprecated: System.Reflection.Metadata Flow.Launcher.Core/packages.lock.json:803 — System.Reflection.Metadata 5.0.0 — Other,Legacy. It is resolved transitively in Flow.Launcher.Core/packages.lock.json: no project of this repository references it directly, so the move is on the reference that pulls it in.
  • Deprecated: YamlDotNet Flow.Launcher.Core/packages.lock.json:1164 — YamlDotNet 9.1.0 — CriticalBugs — the publisher's replacement is `YamlDotNet` >= 9.1.2; migrate the reference to it. It is resolved transitively in Flow.Launcher.Core/packages.lock.json: no project of this repository references it directly, so the move is on the reference that pulls it in.
AX6 · Interface segregation · Fat interface · ×1
  • Fat interface: IPublicAPI (78 members) Flow.Launcher.Plugin/Interfaces/IPublicAPI.cs:18 — `IPublicAPI` declares 78 members: `ChangeQuery`, `RestartApp`, `ShellRun`, `CopyToClipboard`, `SaveAppAllSettings`, `SavePluginSettings`, `ReloadAllPluginData`, `CheckForNewUpdate`, `ShowMsgError`, `ShowMsgErrorWithButton`, `ShowMainWindow`, `FocusQueryTextBox`, `HideMainWindow`, `IsMainWindowVisible`, `VisibilityChanged`, `ShowMsg`, `ShowMsg`, `ShowMsgWithButton`, `ShowMsgWithButton`, `OpenSettingDialog`, `OpenPluginSettingsWindow`, `GetTranslation`, `GetAllPlugins`, `GetAllInitializedPlugins`, `RegisterGlobalKeyboardCallback`, `RemoveGlobalKeyboardCallback`, `FuzzySearch`, `HttpGetStringAsync`, `HttpGetStreamAsync`, `HttpDownloadAsync`, `AddActionKeyword`, `RemoveActionKeyword`, `ActionKeywordAssigned`, `LogDebug`, `LogInfo`, `LogWarn`, `LogError`, `LogException`, `LoadSettingJsonStorage`, `SaveSettingJsonStorage`, and 38 more. Counted as the author wrote them — a property is ONE member and its get/set accessors are not counted separately, and an event counts once. Those 78 declarations carry 73 distinct name(s), so part of the width is overloading rather than separate responsibilities — but 73 operations clears the >15 bar on its own, so the row is about responsibilities, not signatures. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces.
D12 · Dependency Hygiene · Outdated · ×1
  • Outdated: System.Drawing.Common Flow.Launcher.Infrastructure/Flow.Launcher.Infrastructure.csproj:81 — System.Drawing.Common 7.0.0 → 10.0.13 available (referenced by Flow.Launcher.Infrastructure).
D16 · Bus Factor · Off-boarding risk · ×1
  • Off-boarding risk: anonymized user #1 — If anonymized user #1 becomes unavailable, 23 significant file(s) lose their only recent owner: Flow.Launcher.Core/Plugin/PluginManager.cs, Flow.Launcher.Infrastructure/DialogJump/DialogJump.cs, Flow.Launcher.Core/Plugin/JsonRPCPluginSettings.cs, Plugins/Flow.Launcher.Plugin.Program/Views/ProgramSetting.xaml.cs, Flow.Launcher/Storage/TopMostRecord.cs, Flow.Launcher.Core/ExternalPlugins/Environments/AbstractPluginEnvironment.cs, REDACTED, Flow.Launcher/ReleaseNotesWindow.xaml.cs (+15 more). Pair on, review, or document these before any departure.
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 (28 single-owned of 170 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; 170 of the 361 production source files in this repository met that bar). They are anonymized user #2 (2 file(s)), anonymized user #3 (1 file(s)), anonymized user #4 (1 file(s)), anonymized user #5 (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: Flow.Launcher/Resources/Controls/CustomWindowTitleBar.xaml.cs, Plugins/Flow.Launcher.Plugin.Program/Programs/ShellLinkReader.cs, Plugins/Flow.Launcher.Plugin.Explorer/Helper/ShellContextMenuDisplayHelper.cs, Plugins/Flow.Launcher.Plugin.Explorer/Search/Everything/EverythingApiDllImport.cs, Flow.Launcher.Core/Plugin/JsonPRCModel.cs.
D17 · Explicit Debt · ObsoleteWithoutCallers · ×1
  • ObsoleteWithoutCallers Flow.Launcher.Infrastructure/Storage/BinaryStorage.cs:47 — [Obsolete] .ctor
D20 · ADR Quality · No ADRs found · ×1
  • 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/`.
D26 · Project Cohesion · Projects may be oversized for their cohesion · ×1
  • Projects may be oversized for their cohesion — 1 of 17 project(s) overshoot their size bounds, lowering Project Cohesion to 9.2/10. The most over is `Flow.Launcher.Plugin.Explorer` (6733 LoC, 60 public types across 13 namespaces). Review these for cohesion — split a project that spans unrelated responsibilities.
D27 · Navigability · Pass-through layer · ×1
  • Pass-through layer Flow.Launcher.Core/Plugin/JsonRPCV2Models/JsonRPCPublicAPI.cs:13 — JsonRPCPublicAPI: all 36 public methods forward their arguments unchanged to _api and add no behaviour — an extra hop (and usually an extra interface) to trace through. Call _api 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 — 8 of 171 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; 171 of the 361 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: Plugins/Flow.Launcher.Plugin.Explorer/Helper/ShellContextMenuDisplayHelper.cs, Flow.Launcher/HotkeyControlDialog.xaml.cs, Flow.Launcher.Core/Plugin/PythonPlugin.cs, Flow.Launcher.Infrastructure/Exception/ExceptionFormatter.cs, Plugins/Flow.Launcher.Plugin.WindowsSettings/Helper/UnsupportedSettingsHelper.cs, Flow.Launcher.Infrastructure/Hotkey/RegisteredHotkeyData.cs, Flow.Launcher.Core/Resource/FontHelper.cs, Flow.Launcher.Core/ExternalPlugins/CommunityPluginStore.cs. 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.
D36 · Supply-chain Provenance & Signing · REDACTED · ×1
  • REDACTED
D36 · Supply-chain Provenance & Signing · REDACTED · ×1
  • REDACTED
D36 · Supply-chain Provenance & Signing · REDACTED · ×1
  • REDACTED
D36 · Supply-chain Provenance & Signing · REDACTED · ×1
  • REDACTED
M2 · Architecture documentation · No ADRs · ×1
  • 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.
M2 · Architecture documentation · No architecture diagram/doc · ×1
  • No architecture diagram/doc — No C4/Structurizr/PlantUML/Mermaid/Graphviz/D2 diagram, no drawn diagram named for the architecture, no file named `architecture` or `design` in any markup this check reads, and nothing in the README, docs or contributor guides that announces the shape — no `## Architecture` heading, no "architecture overview"/"high-level design" phrasing, no "the architecture is …" introduction, no guided code tour. A shape laid out in prose that never names itself as the architecture is not visible to this check, and neither is one kept outside the repository, so this row reports the absence of a re-findable shape document — not evidence that nobody wrote the shape down.
M3 · Folder & project structure · No src/ separation · ×1
  • No src/ separation — Production code isn't grouped under a src/ folder — it's spread across several top-level directories, so there's no one place that says 'this is the product'.
P3 · Security & performance tooling · No SAST · ×1
  • No SAST — No static application security testing detected. For this repository's stack, add CodeQL's csharp pack, or a .NET security analyzer package (or `semgrep --config=auto`, which runs on any language) as a CI step. What was searched, so you can tell an absence from a miss: the 26744 CI workflow file(s) in this repository, and the scanner and linter configuration checked in beside them. A scan that runs outside CI, one configured in your forge's web UI rather than in a committed file, or a tool whose name is none of those this check carries, is not seen — if that is your case the row is wrong, and saying so is more useful than adding a second scanner.
P6 · Release Hygiene · No changelog · ×1
  • 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 47/185 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.
X23 · Unguarded diagnostic materialisation · Diagnostic log message is built whether or not it is wanted · ×1
  • Diagnostic log message is built whether or not it is wanted Flow.Launcher/ViewModel/MainViewModel.cs:1618 — `LogDebug` at line 1618 is called with an argument built by `string.Join(" ", plugins.Select(x => $"<{x.Metadata.Name}>"))` (line 1618), whose cost grows with the collection it walks. C# evaluates a call's arguments BEFORE entering the method, so that join/projection runs in full every time this line is reached — and then the level check inside the logger discards the string it produced, because LogDebug is a level a shipped configuration normally leaves off. Nothing here decides beforehand whether the message is wanted: no `IsEnabled` test, no debug flag, no conditional-compilation region.
X5 · Nullable reference types · Nullable reference types not enabled everywhere · ×1
  • Nullable reference types not enabled everywhere — 1/16 NRT-eligible project(s) enable <Nullable>enable</Nullable> (projects targeting a pre-C#-8 framework are excluded — NRTs aren't available there). NRTs catch a whole class of null-deref bugs at compile time.
X5 · Nullable reference types · Null-forgiving operator (`!`) suppressions reduce the NRT score · ×1
  • Null-forgiving operator (`!`) suppressions reduce the NRT score — ~0.5 `!` suppressions per 1k syntax nodes — 20 suppression(s) across the 42528 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.
X7 · Silent fallback defaults · Silent fallback default on unknown code · ×1
  • Silent fallback default on unknown code Flow.Launcher/SettingPages/ViewModels/SettingsPaneAboutViewModel.cs:54 — `Version` maps every unrecognised code to `Constant.Version`, 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.
Minor — 48 finding(s)
D12 · Dependency Hygiene · Outdated · ×31
  • Outdated: AvalonEdit — AvalonEdit 6.3.0.90 → 6.3.1.120 available (referenced by Flow.Launcher).
  • Outdated: CommunityToolkit.Mvvm — CommunityToolkit.Mvvm 8.4.0 → 8.4.2 available (referenced by Flow.Launcher).
  • Outdated: Flow.Launcher.Localization — Flow.Launcher.Localization 0.0.6 → 0.0.7 available (referenced by Flow.Launcher).
  • Outdated: iNKORE.UI.WPF.Modern — iNKORE.UI.WPF.Modern 0.10.1 → 0.10.2.1 available (referenced by Flow.Launcher).
  • Outdated: Microsoft.Extensions.DependencyInjection — Microsoft.Extensions.DependencyInjection 9.0.9 → 10.0.13 available (referenced by Flow.Launcher).
  • Outdated: Microsoft.Extensions.Hosting — Microsoft.Extensions.Hosting 9.0.9 → 10.0.13 available (referenced by Flow.Launcher).
  • Outdated: VirtualizingWrapPanel — VirtualizingWrapPanel 2.3.1 → 2.5.4 available (referenced by Flow.Launcher).
  • Outdated: Microsoft.NET.Test.Sdk — Microsoft.NET.Test.Sdk 17.14.1 → 18.11.0 available (referenced by Flow.Launcher.Test).
  • Outdated: Moq — Moq 4.20.72 → 4.21.0 available (referenced by Flow.Launcher.Test).
  • Outdated: nunit — nunit 4.4.0 → 5.0.0 available (referenced by Flow.Launcher.Test).
  • Outdated: NUnit3TestAdapter — NUnit3TestAdapter 5.1.0 → 6.3.1 available (referenced by Flow.Launcher.Test).
  • Outdated: JetBrains.Annotations — JetBrains.Annotations 2025.2.2 → 2026.2.0 available (referenced by Flow.Launcher.Plugin).
  • Outdated: Microsoft.SourceLink.GitHub — Microsoft.SourceLink.GitHub 10.0.300 → 10.0.402 available (referenced by Flow.Launcher.Plugin).
  • Outdated: Microsoft.Windows.CsWin32 — Microsoft.Windows.CsWin32 0.3.298 → 0.3.367 available (referenced by Flow.Launcher.Plugin).
  • Outdated: BitFaster.Caching — BitFaster.Caching 2.5.4 → 2.6.1 available (referenced by Flow.Launcher.Infrastructure).
  • Outdated: Microsoft.VisualStudio.Threading — Microsoft.VisualStudio.Threading 17.14.15 → 18.12.1 available (referenced by Flow.Launcher.Infrastructure).
  • Outdated: NHotkey.Wpf — NHotkey.Wpf 3.0.0 → 4.0.0 available (referenced by Flow.Launcher.Infrastructure).
  • Outdated: NLog — NLog 6.0.4 → 6.2.2 available (referenced by Flow.Launcher.Infrastructure).
  • Outdated: NLog.OutputDebugString — NLog.OutputDebugString 6.0.4 → 6.2.2 available (referenced by Flow.Launcher.Infrastructure).
  • Outdated: SharpVectors.Wpf — SharpVectors.Wpf 1.8.5 → 1.8.6 available (referenced by Flow.Launcher.Infrastructure).
  • Outdated: ToolGood.Words.Pinyin — ToolGood.Words.Pinyin 3.1.0.3 → 3.1.0.4 available (referenced by Flow.Launcher.Infrastructure).
  • Outdated: FSharp.Core — FSharp.Core 9.0.303 → 10.1.402 available (referenced by Flow.Launcher.Core).
  • Outdated: Meziantou.Framework.Win32.Jobs — Meziantou.Framework.Win32.Jobs 3.4.5 → 4.0.5 available (referenced by Flow.Launcher.Core).
  • Outdated: squirrel.windows — squirrel.windows 1.9.0 → 2.0.1 available (referenced by Flow.Launcher.Core).
  • Outdated: StreamJsonRpc — StreamJsonRpc 2.22.11 → 2.26.150 available (referenced by Flow.Launcher.Core).
  • + 6 more in this group — see findings.md.
D19 · Documentation Quality · XML-doc coverage · ×16
  • XML-doc coverage: Flow.Launcher Flow.Launcher/Flow.Launcher.csproj — Flow.Launcher: 5 % XML-doc coverage (43/802).
  • XML-doc coverage: Flow.Launcher.Plugin Flow.Launcher.Plugin/Flow.Launcher.Plugin.csproj — Flow.Launcher.Plugin: 100 % XML-doc coverage (287/287).
  • XML-doc coverage: Flow.Launcher.Infrastructure Flow.Launcher.Infrastructure/Flow.Launcher.Infrastructure.csproj — Flow.Launcher.Infrastructure: 9 % XML-doc coverage (49/538).
  • XML-doc coverage: Flow.Launcher.Core Flow.Launcher.Core/Flow.Launcher.Core.csproj — Flow.Launcher.Core: 13 % XML-doc coverage (35/276).
  • XML-doc coverage: Flow.Launcher.Plugin.Program Plugins/Flow.Launcher.Plugin.Program/Flow.Launcher.Plugin.Program.csproj — Flow.Launcher.Plugin.Program: 9 % XML-doc coverage (14/153).
  • XML-doc coverage: Flow.Launcher.Plugin.WebSearch Plugins/Flow.Launcher.Plugin.WebSearch/Flow.Launcher.Plugin.WebSearch.csproj — Flow.Launcher.Plugin.WebSearch: 5 % XML-doc coverage (3/55).
  • XML-doc coverage: Flow.Launcher.Plugin.PluginIndicator Plugins/Flow.Launcher.Plugin.PluginIndicator/Flow.Launcher.Plugin.PluginIndicator.csproj — Flow.Launcher.Plugin.PluginIndicator: 0 % XML-doc coverage (0/7).
  • XML-doc coverage: Flow.Launcher.Plugin.Sys Plugins/Flow.Launcher.Plugin.Sys/Flow.Launcher.Plugin.Sys.csproj — Flow.Launcher.Plugin.Sys: 0 % XML-doc coverage (0/27).
  • XML-doc coverage: Flow.Launcher.Plugin.Url Plugins/Flow.Launcher.Plugin.Url/Flow.Launcher.Plugin.Url.csproj — Flow.Launcher.Plugin.Url: 0 % XML-doc coverage (0/23).
  • XML-doc coverage: Flow.Launcher.Plugin.Shell Plugins/Flow.Launcher.Plugin.Shell/Flow.Launcher.Plugin.Shell.csproj — Flow.Launcher.Plugin.Shell: 0 % XML-doc coverage (0/40).
  • XML-doc coverage: Flow.Launcher.Plugin.BrowserBookmark Plugins/Flow.Launcher.Plugin.BrowserBookmark/Flow.Launcher.Plugin.BrowserBookmark.csproj — Flow.Launcher.Plugin.BrowserBookmark: 6 % XML-doc coverage (4/69).
  • XML-doc coverage: Flow.Launcher.Plugin.Calculator Plugins/Flow.Launcher.Plugin.Calculator/Flow.Launcher.Plugin.Calculator.csproj — Flow.Launcher.Plugin.Calculator: 0 % XML-doc coverage (0/26).
  • XML-doc coverage: Flow.Launcher.Plugin.Explorer Plugins/Flow.Launcher.Plugin.Explorer/Flow.Launcher.Plugin.Explorer.csproj — Flow.Launcher.Plugin.Explorer: 7 % XML-doc coverage (25/376).
  • XML-doc coverage: Flow.Launcher.Plugin.ProcessKiller Plugins/Flow.Launcher.Plugin.ProcessKiller/Flow.Launcher.Plugin.ProcessKiller.csproj — Flow.Launcher.Plugin.ProcessKiller: 16 % XML-doc coverage (4/25).
  • XML-doc coverage: Flow.Launcher.Plugin.PluginsManager Plugins/Flow.Launcher.Plugin.PluginsManager/Flow.Launcher.Plugin.PluginsManager.csproj — Flow.Launcher.Plugin.PluginsManager: 6 % XML-doc coverage (1/17).
  • XML-doc coverage: Flow.Launcher.Plugin.WindowsSettings Plugins/Flow.Launcher.Plugin.WindowsSettings/Flow.Launcher.Plugin.WindowsSettings.csproj — Flow.Launcher.Plugin.WindowsSettings: 99 % XML-doc coverage (715/721).
D10 · Test Quality · Mock framework · ×1
  • Mock framework: Moq — Flow.Launcher.Test references Moq.

Appendix B — Reproduction & audit trail

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.

DimensionToolVersionCommandFindingsRaw output
D28 · Secrets (history)gitleaks—gitleaks detect --no-banner --config /opt/gitleaks-rules/watchdog-gitleaks.toml --report-format json --report-path /tmp/watchdog-gitleaks-b7de64cf724b418fb2d87f8dba470fdd/history.json --exit-code 0 --source .1artifacts/raw/gitleaks-history.json
D28 · Secrets (history)gitleaks—gitleaks detect --no-git --no-banner --config /opt/gitleaks-rules/watchdog-gitleaks.toml --report-format json --report-path /tmp/watchdog-gitleaks-b7de64cf724b418fb2d87f8dba470fdd/tree.json --exit-code 0 --source .0artifacts/raw/gitleaks-tree.json
D29 · Static Analysis (SAST)semgrep—semgrep --config /opt/semgrep-rules/security-audit.yml --config /opt/semgrep-rules/owasp-top-ten.yml --config /opt/semgrep-rules/watchdog-sast.yml --json --quiet --timeout 10 --timeout-threshold 3 --metrics off .75artifacts/raw/semgrep.json
D30 · Dependency Vulnerabilitiesnuget—nuget: not applicable — nuget: `dotnet list package --vulnerable` could not read this solution's dependency graph — it reported an error for at least one project and returned no package data at all (typically a packages.config / non-PackageReference project, which the command cannot read). An unreadable dependency graph is not a clean one; migrate the project(s) to PackageReference to enable this scan0—
D31 · IaC & Container Securitytrivy—trivy: not applicable — No Infrastructure-as-Code or container manifests found (Dockerfile, Docker Compose, Terraform, Kubernetes/Helm, CloudFormation, ARM, Bicep, Ansible); nothing to scan.0—
D32 · Data Compliance (PII/GDPR)semgrep—semgrep: not applicable — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that. semgrep could not parse 4 file(s) — `Plugins/Flow.Launcher.Plugin.Calculator/ViewModels/SettingsViewModel.cs`, `Plugins/Flow.Launcher.Plugin.ProcessKiller/ProcessResult.cs`, `Plugins/Flow.Launcher.Plugin.ProcessKiller/ViewModels/SettingsViewModel.cs`, `Plugins/Flow.Launcher.Plugin.Sys/SettingsViewModel.cs` — so the PII/GDPR sweep did not cover the unparsed regions of them; rows reported elsewhere in those files are real.0—
D37 · Vulnerability-disclosure Policydisclosure—disclosure: not applicable — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed.0—
D40 · Network Egress Confinementruntime-hardening—runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here.0—
D41 · Kernel & Syscall Confinementruntime-hardening—runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here.0—
D42 · Runtime Threat Enforcementruntime-hardening—runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here.0—
D43 · Malicious Dependenciesosv-scanner—osv-scanner --format json --recursive --experimental-disable-plugins transitivedependency/requirements --experimental-disable-plugins dotnet/csproj --experimental-disable-plugins dotnet/nugetcpm .0artifacts/raw/osv-scanner.json

Run 01a16782-ecb6-7ea2-96f5-a344783b157f · every finding is also locatable in findings.md, and the complete scoring record (with exit codes + durations) in sidecar.json.

Appendix C — Personal-data map

Every field, property and record parameter whose name is conventional personal data — 2 field(s) across 1 category, each with an exact repo-relative file:line. This is the data inventory a compliance review starts from — right-to-erasure, retention, minimisation. Detected by NAME, from the C# syntax tree, with a deliberately specific identifier classifier — the same one the C1–C5 compliance cards use to decide whether personal data is present, so CardDefinition or FileName don't trip. Two caveats stated rather than glossed: those cards additionally require corroboration (a persistence/account signal, or two distinct PII categories) that this inventory deliberately does not, so it lists more than they gate on; and D32 Data Compliance shares nothing with it — that dimension is a separate semgrep ruleset for personal data leaking into logs, URLs and browser storage, and a clean D32 result says nothing about this list. Informational — it feeds no score.

Name — 2 field(s)
  • UWPPackage.FullName REDACTED:25
  • UWPPackage.FamilyName REDACTED:26

Issues: 102 · Warnings: 332 · Recommendations: 110 · Info: 48 — Appendix A · all findings · full markdown report.
Generated by Watchdog — deterministic code-health analysis. 23-10-2026 @ 06:46 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.

⬇ Findings, MITRE CWE-tagged .sarif⬇ Health changelog .md