Public report of BCUninstaller/Bulk-Crap-Uninstaller, 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, 07:10 UTC · Survey ID cd_455ba51d1f8f4c1d8ff0452b0580981b

BCUninstaller/Bulk-Crap-Uninstaller

Measured 23 October 2026, 07:07 UTC, at code version 30da609

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 38out of 100 Weak
CriticalWeakAdequateStrongExemplary
Down 2 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.

Performance 100 Exemplary Architecture 96 Exemplary Maturity 61 Adequate Production Readiness 49 Weak Code Health 40 Weak Security and Compliance 22 Critical

A medium codebase: 95,146 lines of product code in 18 projects, tests not counted · Estimated rebuild effort: about 1.1 person-years · Weakest lens: Security and Compliance, 22

Findings by how serious they are

104 critical 283 serious 103 minor

5 dimensions are left out of the score. For each one, Watchdog either couldn't measure it in this code, or found no evidence of the safeguard it looks for, such as a tested backup restore. They count neither for nor against the score, and Limitations lists each one with its reason.

This survey was produced by

Watchdog
Producer
Canine Development
Analyzer
Watchdog engine 1.0.0
Measured
23 October 2026, 07:07 UTC

A measurement, not a certificate. The Code Assurance Index records a number together with the evidence it was worked out from, so anyone can recalculate it, but it doesn't certify or guarantee the code. The standard was written by Canine Development, which also builds Watchdog. It is open to any tool that implements it, and today Watchdog is the only one that does.

The score is deterministic, which means the same code always gets the same score. Watchdog works it out with tools that follow published rules, and an AI model never decides it, so anyone who applies the same rules to the same code gets the same number. How it is done is explained under Methodology ▸

67of 71 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.
470of 490 findings point to an exact file and line, so you can open each one in the code. The other 20 concern the repository as a whole, such as missing documentation.
71dimensions across 6 lenses, read from 95,146 lines of product code in 18 projects.
Chapters

Executive summary

BCUninstaller/Bulk-Crap-Uninstaller scores 38 out of 100 and is rated Weak, while five of its six lenses score higher still: Performance at 100 and Architecture at 96, both rated Exemplary, Maturity at 61, rated Adequate, and Production Readiness at 49 and Code Health at 40, both rated Weak.

The score is lower than those five because the weakest lens counts most, and here that is Security and Compliance, which scores 22 and is rated Critical. Its Cryptographic Hygiene 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 move the payload out of the URL and into the request body — pass real content (`new StringContent(...)` / `PostAsJsonAsync(uri, payload)`) instead of `null`, and keep only non-identifying routing parameters in the query string and to resolve the 1 InvertedExistenceGuard finding(s) in Explicit Debt, and if Security and Compliance rose to 70, the score would rise from 38 to about 51.

104 findings are critical: 91 in Explicit Debt, six in Static Analysis (SAST), two in Incompleteness & stubs, two in Project dependency cycles, two in Secrets (history) and one in Cryptographic Hygiene.

Watchdog couldn't measure Dependency Hygiene, IL Efficiency and Platform End-of-Life in this code, so those dimensions are left out of the score. The product code is 95,146 lines, which would take an estimated 1.1 person-years, around €160,000, to rebuild.

Code Health 40 Weak, capped by Async correctness and Nullable reference types Architecture 96 ★ Exemplary Maturity 61 Adequate, capped by Architecture documentation Production Readiness 49 Weak, capped by Security & performance tooling Security and Compliance 22 ⚠ Critical, capped by Static Analysis (SAST), Supply-chain Provenance & Signing, Data Protection, Data-Subject Rights and Cryptographic Hygiene Performance 100 ★ Exemplary

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 22 · counts for 46%Code Health 40 · counts for 25%Production Readiness 49 · counts for 14%Maturity 61 · counts for 8%Architecture 96 · counts for 4%Performance 100 · counts for 2%

If Security and Compliance rose from 22 to 70, the lowest score rated Strong, the score would rise from 38 to about 51.

Code composition: what the lines of code are
Business logic 34%Supporting code 41%Tests 1%Generated by tools 24%
New since the last survey: 131 findings

These 131 critical or serious findings weren't in the previous survey, on 9 October 2026. The first 100 are listed here, and the findings file in the download package lists them all.

  • Explicit Debt · EmptyCatchBlock source/BulkCrapUninstaller/Controls/Settings/AdvancedFilters.cs
  • Explicit Debt · EmptyCatchBlock source/BulkCrapUninstaller/Controls/Settings/AdvancedFilters.cs
  • Explicit Debt · EmptyCatchBlock source/BulkCrapUninstaller/Controls/Settings/AdvancedFilters.cs
  • Explicit Debt · EmptyCatchBlock source/BulkCrapUninstaller/Controls/Settings/AdvancedFilters.cs
  • Explicit Debt · EmptyCatchBlock REDACTED
  • Explicit Debt · EmptyCatchBlock source/BulkCrapUninstaller/Forms/Helpers/ListLegendWindow.cs
  • Explicit Debt · EmptyCatchBlock source/BulkCrapUninstaller/Forms/Helpers/ListLegendWindow.cs
  • Explicit Debt · EmptyCatchBlock source/BulkCrapUninstaller/Forms/Windows/JunkRemoveWindow.cs
  • Explicit Debt · EmptyCatchBlock REDACTED
  • Explicit Debt · EmptyCatchBlock REDACTED
  • Explicit Debt · EmptyCatchBlock source/BulkCrapUninstaller/Functions/AppUninstaller.cs
  • Explicit Debt · EmptyCatchBlock source/BulkCrapUninstaller/Functions/AppUninstaller.cs
  • Explicit Debt · EmptyCatchBlock source/BulkCrapUninstaller/Functions/ApplicationList/ListViewDelegates.cs
  • Explicit Debt · EmptyCatchBlock source/BulkCrapUninstaller/Functions/ApplicationList/UninstallerListViewUpdater.cs
  • Explicit Debt · EmptyCatchBlock source/BulkCrapUninstaller/Functions/Ratings/RatingManagerWrapper.cs
  • Explicit Debt · EmptyCatchBlock source/BulkCrapUninstaller/Functions/Tools/SettingTools.cs
  • Explicit Debt · EmptyCatchBlock source/BulkCrapUninstaller/Functions/Tools/SettingTools.cs
  • Explicit Debt · EmptyCatchBlock source/BulkCrapUninstaller/Functions/Tools/UpdateGrabber.cs
  • Explicit Debt · EmptyCatchBlock source/BulkCrapUninstaller/Functions/Tracking/EventHook.cs
  • Explicit Debt · EmptyCatchBlock REDACTED
  • Explicit Debt · EmptyCatchBlock source/KlocTools/Extensions/FormsExtensions.cs
  • Explicit Debt · EmptyCatchBlock source/KlocTools/Extensions/FormsExtensions.cs
  • Explicit Debt · EmptyCatchBlock source/KlocTools/Extensions/FormsExtensions.cs
  • Explicit Debt · EmptyCatchBlock source/KlocTools/Extensions/ProcessExtensions.cs
  • Explicit Debt · EmptyCatchBlock source/KlocTools/Forms/CustomMessageBox.cs
  • Explicit Debt · EmptyCatchBlock source/KlocTools/Forms/LoadingDialog.cs
  • Explicit Debt · EmptyCatchBlock source/KlocTools/Forms/StringEditBox.cs
  • Explicit Debt · EmptyCatchBlock source/KlocTools/Forms/Tools/PremadeDialogs.cs
  • Explicit Debt · EmptyCatchBlock source/KlocTools/Forms/Tools/PremadeDialogs.cs
  • Explicit Debt · EmptyCatchBlock source/KlocTools/Forms/Tools/PremadeDialogs.cs
  • Explicit Debt · EmptyCatchBlock source/KlocTools/Tools/PathTools.cs
  • Explicit Debt · EmptyCatchBlock source/KlocTools/Tools/PathTools.cs
  • Explicit Debt · EmptyCatchBlock source/KlocTools/Tools/ProcessTools.cs
  • Explicit Debt · EmptyCatchBlock REDACTED
  • Explicit Debt · EmptyCatchBlock REDACTED
  • Explicit Debt · EmptyCatchBlock source/UninstallTools/ApplicationUninstallerEntry.cs
  • Explicit Debt · EmptyCatchBlock source/UninstallTools/Controls/UninstallerIconGetter.cs
  • Explicit Debt · EmptyCatchBlock source/UninstallTools/Factory/ApplicationEntryTools.cs
  • Explicit Debt · EmptyCatchBlock source/UninstallTools/Factory/ApplicationEntryTools.cs
  • Explicit Debt · EmptyCatchBlock source/UninstallTools/Factory/ApplicationEntryTools.cs
  • Explicit Debt · EmptyCatchBlock source/UninstallTools/Factory/ApplicationEntryTools.cs
  • Explicit Debt · EmptyCatchBlock source/UninstallTools/Factory/DirectoryFactory.cs
  • Explicit Debt · EmptyCatchBlock source/UninstallTools/Factory/InfoAdders/AppExecutablesSearcher.cs
  • Explicit Debt · EmptyCatchBlock source/UninstallTools/Factory/InfoAdders/AppExecutablesSearcher.cs
  • Explicit Debt · EmptyCatchBlock source/UninstallTools/Factory/InfoAdders/AppExecutablesSearcher.cs
  • Explicit Debt · EmptyCatchBlock source/UninstallTools/Factory/InfoAdders/AppExecutablesSearcher.cs
  • Explicit Debt · EmptyCatchBlock source/UninstallTools/Factory/InfoAdders/BasicIconGetter.cs
  • Explicit Debt · EmptyCatchBlock source/UninstallTools/Factory/InfoAdders/CertificateGetter.cs
  • Explicit Debt · EmptyCatchBlock REDACTED
  • Explicit Debt · EmptyCatchBlock source/UninstallTools/Factory/InfoAdders/KnownNameIconGetter.cs
  • Explicit Debt · EmptyCatchBlock source/UninstallTools/Factory/InfoAdders/KnownNameIconGetter.cs
  • Explicit Debt · EmptyCatchBlock source/UninstallTools/Factory/InfoAdders/MsiInfoAdder.cs
  • Explicit Debt · EmptyCatchBlock source/UninstallTools/Factory/InfoAdders/UninstallerSearcher.cs
  • Explicit Debt · EmptyCatchBlock source/UninstallTools/Factory/InfoAdders/UninstallerSearcher.cs
  • Explicit Debt · EmptyCatchBlock source/UninstallTools/Factory/InfoAdders/UninstallerTypeAdder.cs
  • Explicit Debt · EmptyCatchBlock source/UninstallTools/Factory/InfoAdders/UninstallerTypeAdder.cs
  • Explicit Debt · EmptyCatchBlock source/UninstallTools/Factory/InfoAdders/UninstallerTypeAdder.cs
  • Explicit Debt · EmptyCatchBlock source/UninstallTools/Factory/RegistryFactory.cs
  • Explicit Debt · EmptyCatchBlock source/UninstallTools/Factory/RegistryFactory.cs
  • Explicit Debt · EmptyCatchBlock REDACTED
  • Explicit Debt · EmptyCatchBlock REDACTED
  • Explicit Debt · EmptyCatchBlock REDACTED
  • Explicit Debt · EmptyCatchBlock source/UninstallTools/Junk/Finders/Registry/SoftwareRegKeyScanner.cs
  • Explicit Debt · EmptyCatchBlock source/UninstallTools/Junk/Finders/Registry/SoftwareRegKeyScanner.cs
  • Explicit Debt · EmptyCatchBlock source/UninstallTools/Junk/Finders/Registry/SoftwareRegKeyScanner.cs
  • Explicit Debt · EmptyCatchBlock source/UninstallTools/Startup/Normal/OldStartupDisable.cs
  • Explicit Debt · EmptyCatchBlock REDACTED
  • Explicit Debt · EmptyCatchBlock source/UninstallTools/Startup/Service/ServiceEntryFactory.cs
  • Explicit Debt · EmptyCatchBlock source/UninstallTools/Startup/StartupEntryBase.cs
  • Explicit Debt · EmptyCatchBlock REDACTED
  • Explicit Debt · EmptyCatchBlock REDACTED
  • Explicit Debt · EmptyCatchBlock REDACTED
  • Explicit Debt · EmptyCatchBlock source/UninstallTools/Uninstaller/BulkUninstallEntry.cs
  • Explicit Debt · EmptyCatchBlock source/UninstallTools/Uninstaller/BulkUninstallEntry.cs
  • Explicit Debt · EmptyCatchBlock source/UninstallTools/Uninstaller/BulkUninstallEntry.cs
  • Explicit Debt · EmptyCatchBlock source/UninstallTools/Uninstaller/BulkUninstallEntry.cs
  • Explicit Debt · EmptyCatchBlock source/UninstallTools/Uninstaller/BulkUninstallEntry.cs
  • Explicit Debt · EmptyCatchBlock source/UninstallerAutomatizer/Automation/UninstallHandler.cs
  • Static Analysis (SAST) · REDACTED
  • Static Analysis (SAST) · REDACTED
  • Static Analysis (SAST) · REDACTED
  • Static Analysis (SAST) · REDACTED
  • Static Analysis (SAST) · REDACTED
  • Static Analysis (SAST) · REDACTED
  • Static Analysis (SAST) · REDACTED
  • Static Analysis (SAST) · REDACTED
  • Static Analysis (SAST) · REDACTED
  • Static Analysis (SAST) · REDACTED
  • Cryptographic Hygiene · Password key derivation is priced too cheaply source/NBug_custom/Settings.cs
  • Async correctness · Sync-over-async (deadlock risk) through `.Result` source/BulkCrapUninstaller/Functions/Ratings/UninstallerRatingManager.cs
  • Async correctness · Sync-over-async (deadlock risk) through `.Result` source/BulkCrapUninstaller/Functions/Ratings/UninstallerRatingManager.cs
  • Async correctness · Sync-over-async (deadlock risk) through `.Result` source/BulkCrapUninstaller/Functions/Ratings/UninstallerRatingManager.cs
  • Async correctness · Sync-over-async (deadlock risk) through `.Result` source/BulkCrapUninstaller/Functions/Tools/UpdateGrabber.cs
  • Async correctness · Sync-over-async (deadlock risk) through `.Result` source/BulkCrapUninstaller/Functions/Tracking/DatabaseStatSender.cs
  • Async correctness · Sync-over-async (deadlock risk) through `.Result` source/BulkCrapUninstaller/NBugConfigurator.cs
  • Async correctness · Sync-over-async (deadlock risk) through `.Result` REDACTED
  • Async correctness · Blocking `Process.WaitForExit` inside an `async` method REDACTED
  • Exception handling · Swallowed exception (empty catch) source/BulkCrapUninstaller/Controls/Settings/AdvancedFilters.cs
  • Exception handling · Swallowed exception (empty catch) source/BulkCrapUninstaller/Controls/Settings/AdvancedFilters.cs
  • Exception handling · Swallowed exception (empty catch) source/BulkCrapUninstaller/Controls/Settings/AdvancedFilters.cs

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

These 48 critical or serious findings were in the previous survey, on 9 October 2026, and are gone from this one.

  • Coupling · Off the main sequence: PortableSettingsProvider
  • Coupling · Off the main sequence: KlocTools
  • Coupling · Off the main sequence: NBug
  • Coupling · Off the main sequence: NetSettingBinder
  • Exception handling · Swallowed exception (caught, then discarded) source/BulkCrapUninstaller/EntryPoint.cs
  • Exception handling · Swallowed exception (caught, then discarded) source/BulkCrapUninstaller/Functions/ApplicationList/UninstallerListConfigurator.cs
  • Exception handling · Swallowed exception (caught, then discarded) source/UninstallTools/ApplicationUninstallerEntry.cs
  • Exception handling · Swallowed exception (caught, then discarded) source/UninstallTools/ApplicationUninstallerEntry.cs
  • Exception handling · Swallowed exception (caught, then discarded) source/UninstallTools/ApplicationUninstallerEntry.cs
  • Exception handling · Swallowed exception (caught, then discarded) source/UninstallTools/Factory/DirectoryFactory.cs
  • Exception handling · Swallowed exception (caught, then discarded) source/UninstallTools/Factory/InfoAdders/ExecutableAttributeExtractor.cs
  • Exception handling · Swallowed exception (caught, then discarded) source/UninstallTools/Factory/InfoAdders/InstallDateAdder.cs
  • Exception handling · Swallowed exception (caught, then discarded) source/UninstallTools/Factory/InfoAdders/Is64BitGetter.cs
  • Exception handling · Swallowed exception (caught, then discarded) source/UninstallTools/Factory/RegistryFactory.cs
  • Exception handling · Swallowed exception (empty catch) source/UninstallTools/Factory/RegistryFactory.cs
  • Exception handling · Unguarded deserialized result under a catch list that cannot catch it REDACTED
  • Exception handling · Unguarded deserialized result under a catch list that cannot catch it REDACTED
  • Exception handling · Unguarded deserialized result under a catch list that cannot catch it REDACTED
  • Exception handling · Swallowed exception (caught, then discarded) source/UninstallTools/Factory/StoreAppFactory.cs
  • Exception handling · Swallowed exception (caught, then discarded) source/UninstallTools/Junk/Finders/JunkCreatorBase.cs
  • Exception handling · Swallowed exception (empty catch) source/UninstallTools/Lists/FilterCondition.cs
  • Exception handling · Swallowed exception (caught, then discarded) source/UninstallTools/Startup/Normal/OldStartupDisable.cs
  • Exception handling · Swallowed exception (caught, then discarded) source/UninstallTools/Startup/Normal/StartupEntry.cs
  • Exception handling · Swallowed exception (caught, then discarded) source/UninstallTools/Startup/Task/TaskEntryFactory.cs
  • Exception handling · Swallowed exception (caught, then discarded) source/UninstallTools/Startup/Task/TaskEntryFactory.cs
  • Exception handling · Swallowed exception (caught, then discarded) source/UninstallTools/Uninstaller/BulkUninstallEntry.cs
  • Exception handling · Swallowed exception (empty catch) source/UninstallTools/Uninstaller/BulkUninstallTask.cs
  • Exception handling · Swallowed exception (empty catch) source/KlocTools/Collections/ObservedList.cs
  • Exception handling · Swallowed exception (caught, then discarded) source/KlocTools/Forms/LoadingDialogInterface.cs
  • Exception handling · Swallowed exception (caught, then discarded) source/KlocTools/Forms/LoadingDialogInterface.cs
  • Exception handling · Swallowed exception (caught, then discarded) source/KlocTools/Forms/LoadingDialogInterface.cs
  • Exception handling · Swallowed exception (caught, then discarded) source/KlocTools/IO/AdvancedFileInfo.cs
  • Exception handling · Swallowed exception (caught, then discarded) source/KlocTools/Tools/PathTools.cs
  • Exception handling · Swallowed exception (empty catch) source/KlocTools/Tools/PathTools.cs
  • Exception handling · Swallowed exception (empty catch) source/KlocTools/Tools/PathTools.cs
  • Exception handling · Swallowed exception (caught, then discarded) source/KlocTools/Tools/ProcessStartCommand.cs
  • Exception handling · Swallowed exception (caught, then discarded) source/KlocTools/Tools/ProcessTools.cs
  • Exception handling · Swallowed exception (empty catch) source/KlocTools/Tools/ProcessTools.cs
  • Exception handling · Swallowed exception (caught, then discarded) source/KlocTools/Tools/ProcessTools.cs
  • Exception handling · Swallowed exception (caught, then discarded) REDACTED
  • Exception handling · Swallowed exception (caught, then discarded) source/KlocTools/Tools/WindowsTools.cs
  • Exception handling · Swallowed exception (caught, then discarded) source/UninstallerAutomatizer/Automation/AutomatedUninstallManager.cs
  • Exception handling · Swallowed exception (empty catch) source/ObjectListView/VirtualObjectListView.cs
  • Exception handling · Swallowed exception (caught, then discarded) REDACTED
  • Exception handling · Swallowed exception (caught, then discarded) REDACTED
  • Exception handling · Swallowed exception (empty catch) source/BCU-console/Program.cs
  • Exception handling · Swallowed exception (caught, then discarded) source/NBug_custom/Core/Util/Storage/ZipStorer.cs
  • Exception handling · Swallowed exception (empty catch) source/NBug_custom/Core/Util/Storage/ZipStorer.cs
Rebuild cost: about €160,000 · Estimate
Cost to rebuild€52,000 to €270,000, for 859 to 2,794 hours of work, about 1.1 person-years for 1 to 3 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 38. 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: 95,146 lines of product code
Comment linesThe estimate prices 62,988 lines. Comment lines count towards the size of 95,146 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
Move the payload out of the URL and into the request body — pass real content (`new StringContent(...)` / `PostAsJsonAsync(uri, payload)`) instead of `null`, and keep only non-identifying routing parameters in the query string.
A URL is logged verbatim by the receiving server and every proxy in front of it; a body is not.
Raises the score by about 8 points · Medium effort · Cryptographic Hygiene
2
Resolve the 1 InvertedExistenceGuard finding(s) in Explicit Debt — start with REDACTED.
Raises the score by about 4 points · Low effort · Explicit Debt
3
Resolve the 2 NoWarnInCsproj finding(s) in Explicit Debt — start with BulkCrapUninstallerTests.csproj (2).
Raises the score by about 4 points · Low effort · Explicit Debt

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.

Where the investment is most exposed · Value at risk
This code would cost about €160,000 to build again, about 1.1 person-years of work. Its weakest lens is Security and Compliance, at 22 (Critical). Security and Compliance is about how well the product is protected, and how it handles personal data. Because the weakest lens counts most in the score, work on Security and Compliance also moves the score most.
Based on: the rebuild estimate · the Security and Compliance grade · how much each lens counts
What to do: Start with the Security and Compliance actions in Top priorities.
If you do one thing first · First action
Move the payload out of the URL and into the request body — pass real content (`new StringContent(...)` / `PostAsJsonAsync(uri, payload)`) instead of `null`, and keep only non-identifying routing parameters in the query string. Of all the actions in this report, it raises the score most for the work it takes: about 8 points for medium effort. The next survey will show the change in the score.
Based on: the ranked actions in Top priorities, by score gain and effort

Architecture — module dependency graph

Project dependencies, layered top-to-bottom; arrows show direction. Any dashed red edge points upward or sideways — a layering smell or cycle. A clean layered graph has none.

arch BCU-console BCU-console UninstallTools UninstallTools BCU-console->UninstallTools BulkCrapUninstaller BulkCrapUninstaller KlocTools KlocTools BulkCrapUninstaller->KlocTools NBug NBug BulkCrapUninstaller->NBug NetSettingBinder NetSettingBinder BulkCrapUninstaller->NetSettingBinder ObjectListView ObjectListView BulkCrapUninstaller->ObjectListView PortableSettingsProvider PortableSettingsProvider BulkCrapUninstaller->PortableSettingsProvider SimpleTreeMap SimpleTreeMap BulkCrapUninstaller->SimpleTreeMap BulkCrapUninstaller->UninstallTools OculusHelper OculusHelper OculusHelper->KlocTools ScriptHelper ScriptHelper ScriptHelper->KlocTools SimpleTreeMap->ObjectListView SimpleTreeMapTestApp SimpleTreeMapTestApp SimpleTreeMapTestApp->SimpleTreeMap SteamHelper SteamHelper SteamHelper->KlocTools StoreAppHelper StoreAppHelper UninstallTools->KlocTools UninstallTools->ObjectListView UninstallerAutomatizer UninstallerAutomatizer UninstallerAutomatizer->KlocTools UninstallerAutomatizer->UninstallTools UniversalUninstaller UniversalUninstaller UniversalUninstaller->KlocTools UniversalUninstaller->ObjectListView WinUpdateHelper WinUpdateHelper

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.

84 modules, with 185 dependencies between them. 2 loops run through 15 of the modules, marked above the diagonal.

The table shows the 40 modules with the most connections; 44 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 BrightIdeasSoftware2 Klocman.Binding.Settings3 Klocman.Forms.Tools4 Klocman.Native5 NBug.Core.Util.Serialization6 NBug.Enums7 Klocman.IO8 Klocman.Subsystems9 Klocman.Tools10 NBug.Core.Reporting.Info11 UninstallTools.Junk.Confidence12 UninstallTools.Startup13 Klocman.Controls14 NBug.Core.Submission15 NBug.Core.UI16 UninstallTools.Factory.InfoAdders17 UninstallTools.Junk.Containers18 Klocman.Forms19 NBug.Core.Reporting20 NBug.Core.UI.Console21 NBug.Core.UI.Custom22 NBug.Core.UI.WPF23 NBug.Core.UI.WinForms24 NBug.Events25 UninstallTools.Junk26 NBug27 UninstallTools.Factory28 UninstallTools29 BulkCrapUninstaller.Functions30 BulkCrapUninstaller.Functions.Ratings31 BulkCrapUninstaller.Functions.Tools32 UninstallTools.Junk.Finders33 UninstallTools.Lists34 UninstallTools.Controls35 UninstallTools.Junk.Finders.Drive36 UninstallTools.Junk.Finders.Misc37 BulkCrapUninstaller.Functions.ApplicationList38 BulkCrapUninstaller.Forms39 BulkCrapUninstaller.Properties40 BulkCrapUninstaller.Controls
1 BrightIdeasSoftware
2 Klocman.Binding.Settings
3 Klocman.Forms.Tools
4 Klocman.Native
5 NBug.Core.Util.Serialization
6 NBug.Enums
7 Klocman.IO1
8 Klocman.Subsystems1
9 Klocman.Tools2
10 NBug.Core.Reporting.Info2
11 UninstallTools.Junk.Confidence11
12 UninstallTools.Startup1
13 Klocman.Controls2
14 NBug.Core.Submission33
15 NBug.Core.UI111
16 UninstallTools.Factory.InfoAdders11125
17 UninstallTools.Junk.Containers13177
18 Klocman.Forms121
19 NBug.Core.Reporting121
20 NBug.Core.UI.Console1111
21 NBug.Core.UI.Custom1111
22 NBug.Core.UI.WPF1111
23 NBug.Core.UI.WinForms2144
24 NBug.Events2121
25 UninstallTools.Junk44
26 NBug4122
27 UninstallTools.Factory21131136
28 UninstallTools12111
29 BulkCrapUninstaller.Functions1331
30 BulkCrapUninstaller.Functions.Ratings3111
31 BulkCrapUninstaller.Functions.Tools1211
32 UninstallTools.Junk.Finders211
33 UninstallTools.Lists5
34 UninstallTools.Controls215
35 UninstallTools.Junk.Finders.Drive1766
36 UninstallTools.Junk.Finders.Misc13121
37 BulkCrapUninstaller.Functions.ApplicationList33111413123
38 BulkCrapUninstaller.Forms157121213731116410
39 BulkCrapUninstaller.Properties11
40 BulkCrapUninstaller.Controls23111
Uses a module listed above itPart of a loopThe module itself
1 BrightIdeasSoftware2 Klocman.Binding.Settings3 Klocman.Forms.Tools4 Klocman.Native5 NBug.Core.Util.Serialization6 NBug.Enums7 Klocman.IO8 Klocman.Subsystems9 Klocman.Tools10 NBug.Core.Reporting.Info11 UninstallTools.Junk.Confidence12 UninstallTools.Startup13 Klocman.Controls14 NBug.Core.Submission15 NBug.Core.UI16 UninstallTools.Factory.InfoAdders17 UninstallTools.Junk.Containers18 Klocman.Forms19 NBug.Core.Reporting20 NBug.Core.UI.Console21 NBug.Core.UI.Custom22 NBug.Core.UI.WPF23 NBug.Core.UI.WinForms24 NBug.Events25 UninstallTools.Junk26 NBug27 UninstallTools.Factory28 UninstallTools29 BulkCrapUninstaller.Functions30 BulkCrapUninstaller.Functions.Ratings31 BulkCrapUninstaller.Functions.Tools32 UninstallTools.Junk.Finders33 UninstallTools.Lists34 UninstallTools.Controls35 UninstallTools.Junk.Finders.Drive36 UninstallTools.Junk.Finders.Misc37 BulkCrapUninstaller.Functions.ApplicationList38 BulkCrapUninstaller.Forms39 BulkCrapUninstaller.Properties40 BulkCrapUninstaller.ControlsBrightIdeasSoftware1Klocman.Binding.Settings2Klocman.Forms.Tools3Klocman.Native4NBug.Core.Util.Serialization5NBug.Enums6Klocman.IO7Klocman.Subsystems8Klocman.Tools9NBug.Core.Reporting.Info10UninstallTools.Junk.Confidence11UninstallTools.Startup12Klocman.Controls13NBug.Core.Submission14NBug.Core.UI15UninstallTools.Factory.InfoAdders16UninstallTools.Junk.Containers17Klocman.Forms18NBug.Core.Reporting19NBug.Core.UI.Console20NBug.Core.UI.Custom21NBug.Core.UI.WPF22NBug.Core.UI.WinForms23NBug.Events24UninstallTools.Junk25NBug26UninstallTools.Factory27UninstallTools28BulkCrapUninstaller.Functions29BulkCrapUninstaller.Functions.Ratings30BulkCrapUninstaller.Functions.Tools31UninstallTools.Junk.Finders32UninstallTools.Lists33UninstallTools.Controls34UninstallTools.Junk.Finders.Drive35UninstallTools.Junk.Finders.Misc36BulkCrapUninstaller.Functions.ApplicationList37BulkCrapUninstaller.Forms38BulkCrapUninstaller.Properties39BulkCrapUninstaller.Controls40112211123311111125131771211211111111111112144212144412221131136121111331311112112115215176613121331114131231571212137311164101123111+44 more modules (most-connected shown)

At a glance — Code Health · 40% · Weak · gated by X1, X5 ·

The Good
D3 · .NET / C# God Classes 9.7 D4 · .NET / C# Code Duplication 9.9 D17 · .NET / C# Explicit Debt 7.9 D18 · .NET / C# Solution Shape 10.0 GD1 · Repo Unfinished & placeholder code 9.9 IC1 · Repo Incompleteness & stubs 7.5 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 X21 · Repo Side-effecting pattern guard 10.0 X22 · Repo Contradicted release guard 10.0 X23 · Repo Unguarded diagnostic materialisation 10.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 X4 · Repo Structured logging 10.0
The Bad
D1 · .NET / C# Cyclomatic Complexity 6.9 D2 · .NET / C# Cognitive Complexity 6.0 X18 · Repo Disposal-pattern correctness 5.4 X20 · Repo Mistyped argument guard 6.8
The Ugly
X1 · Repo Async correctness 1.6 X2 · Repo Cancellation propagation 4.0 X3 · Repo Exception handling 4.8 X5 · Repo Nullable reference types 2.0

At a glance — Architecture · 96% · Exemplary ·

The Good
D5 · .NET / C# Coupling 9.6 D6 · .NET / C# Cohesion (LCOM4) 9.3 D27 · .NET / C# Navigability 9.3 D35 · .NET / C# Change Coupling 10.0 AX10 · Repo Code composition 9.9 AX3 · Repo Project dependency cycles 10.0 AX4 · Repo Dependency direction 10.0 AX5 · Repo Architecture & structure 10.0 AX6 · Repo Interface segregation 10.0 AX8 · Repo Test isolation 10.0
The Bad
D26 · .NET / C# Project Cohesion 5.6

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

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

At a glance — Readiness · 49% · Weak · gated by P3 ·

The Good
D9 · .NET / C# Test Distribution 10.0 D10 · .NET / C# Test Quality 10.0 D13 · .NET / C# Secret Scanning 10.0 D14 · .NET / C# License Compliance 10.0 P1 · Repo CI/CD gates 10.0 P4 · Repo Deployment & Rollback 7.0
The Bad
P2 · Repo Observability 5.1 P6 · Repo Release Hygiene 5.0
The Ugly
P3 · Repo Security & performance tooling 0.0

At a glance — Security · 22% · Critical · gated by D29, D36, C1, C5, S1 ·

The Good
D28 · .NET / C# Secrets (history) 8.0 X14 · Repo Bypassable address classification 10.0 X17 · Repo Uncapped recursion over a caller-supplied document 10.0 X24 · Repo Document value interpolated into markup unescaped 10.0
The Bad
C4 · Repo Data Retention 5.0
The Ugly
D29 · .NET / C# Static Analysis (SAST) 1.4 D36 · .NET / C# Supply-chain Provenance & Signing 2.5 C1 · Repo Data Protection 3.5 C5 · Repo Data-Subject Rights 2.0 S1 · Repo Cryptographic Hygiene 0.0 X15 · Repo Unvalidated length from an untrusted reader 3.5

At a glance — Performance · 100% · Exemplary ·

The Good
PF3 · Repo Async & latency hygiene 10.0

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 — Injection21High / Critical
A03:2025 — Software Supply Chain Failures4Medium
A07:2025 — Authentication Failures3High / Critical

Roadmap

Immediately secure sensitive data by moving request payloads from URLs to the body to prevent logging exposure, and resolve the ten insecure request findings identified in static analysis. Implement the right to be forgotten to allow users to erase their records, and address explicit code debt by fixing the inverted existence guard and removing unnecessary warnings in the project configuration.

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

Do thisHelpsEffortDimension
Move the payload out of the URL and into the request body — pass real content (`new StringContent(...)` / `PostAsJsonAsync(uri, payload)`) instead of `null`, and keep only non-identifying routing parameters in the query string. A URL is logged verbatim by the receiving server and every proxy in front of it; a body is not.+8.2 ptsMediumCryptographic Hygiene
Resolve the 1 InvertedExistenceGuard finding(s) in Explicit Debt — start with REDACTED.+3.8 ptsLowExplicit Debt
Resolve the 2 NoWarnInCsproj finding(s) in Explicit Debt — start with BulkCrapUninstallerTests.csproj (2).+3.8 ptsLowExplicit Debt
Resolve the 10 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (4), REDACTED, REDACTED.+6.3 ptsMediumStatic Analysis (SAST)
Resolve the 5 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (2), REDACTED, REDACTED.+3.2 ptsLowStatic Analysis (SAST)
Resolve the 2 High secret finding(s) in Secrets (history) — start with REDACTED, REDACTED.+3.1 ptsLowSecrets (history)
Resolve the 1 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED.+3.1 ptsLowStatic Analysis (SAST)
Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing.+2.9 ptsLowSupply-chain Provenance & Signing

File quality

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

FileScoreBandWorst signal
REDACTED0.0SlopStatic Analysis (SAST): High: REDACTED
REDACTED0.0SlopStatic Analysis (SAST): High: REDACTED
REDACTED0.0SlopStatic Analysis (SAST): High: REDACTED
source/UninstallTools/Factory/InfoAdders/UninstallerTypeAdder.cs1.8SlopExplicit Debt: EmptyCatchBlock
source/UninstallTools/Factory/InfoAdders/AppExecutablesSearcher.cs2.2SlopExplicit Debt: EmptyCatchBlock
source/UninstallTools/Junk/Finders/Registry/SoftwareRegKeyScanner.cs2.5SlopExplicit Debt: EmptyCatchBlock
source/UninstallTools/Uninstaller/BulkUninstallEntry.cs2.5SlopExplicit Debt: EmptyCatchBlock
source/UninstallTools/Factory/ApplicationEntryTools.cs3.3SlopExplicit Debt: EmptyCatchBlock
source/BulkCrapUninstaller/Functions/AppUninstaller.cs3.4SlopExplicit Debt: EmptyCatchBlock
source/UninstallTools/Uninstaller/BulkUninstallTask.cs3.6SlopExplicit Debt: EmptyCatchBlock
REDACTED3.7SlopExplicit Debt: EmptyCatchBlock
source/KlocTools/Tools/PathTools.cs4.0MixedExplicit Debt: EmptyCatchBlock
source/KlocTools/Tools/ProcessTools.cs4.2MixedExplicit Debt: EmptyCatchBlock
source/UninstallTools/Factory/InfoAdders/MsiInfoAdder.cs4.3MixedExplicit Debt: EmptyCatchBlock
source/UninstallerAutomatizer/Automation/UninstallHandler.cs4.3MixedExplicit Debt: EmptyCatchBlock
source/KlocTools/Extensions/FormsExtensions.cs4.3MixedExplicit Debt: EmptyCatchBlock
source/UninstallTools/ApplicationUninstallerEntry.cs4.3MixedExplicit Debt: EmptyCatchBlock
REDACTED4.3MixedExplicit Debt: EmptyCatchBlock
REDACTED4.3MixedExplicit Debt: EmptyCatchBlock
source/BulkCrapUninstaller/Forms/Windows/JunkRemoveWindow.cs4.6MixedExplicit Debt: EmptyCatchBlock

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

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

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

Recorded, with no effect on how the codebase functions. Present so the survey is complete, not because it needs doing.

Could not be resolved — 5

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. 67 of 71 evaluated dimensions are computed purely by tools and static analysis (confidence 1.0); 4 documentation/naming judgement(s) are LLM-assisted and labelled advisory. Overall confidence is 0.9 — the weighted average across measured dimensions; it falls as more of the score leans on LLM-assisted judgement and rises when it's fully tool-backed.

Every figure here is one of three kinds, and we label which: ✓ Measured — a deterministic fact (LoC, complexity, coverage); ~ Modeled — an estimate from a stated model (cost, effort, value-at-risk), always a range with its assumptions, never a precise fact; ◐ Advisory — an LLM prose judgement. We never present a modelled estimate as if it were measured. Perfect or absent scores carry their provenance too (ADR-0011): ✓ Tool-verified means the property itself was measured across the surface; ○ Nothing flagged means the probes came back clean — a claim bounded by what a repository can show; ⊘ Not evidenced means a working control (a tested restore, an automated rollback) showed no positive evidence — absence of evidence is not evidence of a control, so it's excluded from the score rather than awarded a spurious 10; ◐ Sampled · advisory marks an LLM verdict over a bounded sample — advisory, never a deterministic measurement.

What we checked — 71 dimensions across the health lenses
D1D2D3D4D5D6D9D10D13D14D15D17D18D19D20D21D24D26D27D28D29D34D35D36AX10AX3AX4AX5AX6AX8C1C4C5GD1IC1M1M2M3M4P1P2P3P4P6PF3S1X1X12X13X14X15X16X17X18X19X2X20X21X22X23X24X25X26X27X28X29X3X30X32X4X5

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, 470 of 490 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 01a16795-cf3a-7d62-b3fd-2a05ff0a739b.

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.
  • D12 Dependency Hygiene — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. `dotnet list package` did not return usable output (restore or query failed); no outdated/vulnerable/deprecated data to assess. The tool said: `dotnet list package` exited 1 with no output.
  • D16 Bus Factor — not measured this run — This is a true statement about the repository that carries nothing for its owner to act on, so it is reported here rather than as a defect in their code. Single-maintainer repository — bus factor is not applicable (49 contributor(s) across 1711 commit(s) sampled, automation and bot accounts excluded). One of them holds 88% of the history; the other 48 hold 0.2% each on average, below the 5% at which there is somebody to hand the work to. That is a single maintainer with drive-by contributors, not a team whose knowledge has concentrated — so the bus factor is not applicable and there is nothing here for the owner to act on.
  • 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 'source/UninstallTools/UninstallTools.csproj' with message: The task "ResolveComReference" is not supported on the .NET Core version of MSBuild. Please use the .NET Framework version of MSBuild. See https://aka.ms/msbuild/MSB4803 for further details.
  • D18 Solution Shape — measured, with a gap in what it reached — Watchdog measured this, but not all of it. What it did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. `dotnet build` reported 3 error(s), and the diagnostics it printed were: MSB4803: The task "ResolveComReference" is not supported on the .NET Core version of MSBuild. Please use the .NET Framework version of MSBuild. See https://aka.ms/msbuild/MSB4803 for further details.. None of them is a .NET compiler diagnostic, which is the only signal this check reads as "the code does not compile", so the failure is recorded as a build-environment gap rather than a code defect. The usual causes are a project that targets a platform this run cannot build (a Windows-only target framework on a Linux worker) or a build step that shells out to a tool the image does not carry. Solution Shape is scored on structure and is NOT capped. Semantic analysis is independent of this build and covers every project that loaded — but a project whose restore did not complete has no resolved references, so treat its results as absent rather than clean. ★ The reach of that test, stated so this classification can be checked rather than taken on trust: it reads the C# (CS), Visual Basic (BC) and F# (FS) compiler series, and treats SDK, NuGet-restore and MSBuild codes (NETSDK, NU, MSB) as evidence that the build did not run rather than that the code is broken — read the diagnostics named above and judge for yourself. You can widen what we reach: if this build is meant to run off its own platform, without host tooling we do not carry, the diagnostics named above are what stopped it. If it is deliberately platform-bound — a Windows-only desktop product, say — there is nothing to do here: the note records our reach, not a defect in your build.
  • 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 (94,981 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. `source/HelperTools/LogWriter.cs`, `source/KlocTools/Forms/Tools/PremadeDialogs.cs`, `source/KlocTools/IO/MsiTools.cs`, `source/UninstallTools/Uninstaller/NoWayToUninstallException.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 own build of this repository failed for an ENVIRONMENT reason (exit 1) — MSBuild's engine or the CLR gave up, or our image does not carry the SDK band/targeting pack this repository needs. This is OUR limitation, not a defect in the repo, and it is not a statement that this repository fails to build. D18 owns the question of whether this repository builds; it was not answered here.
  • 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.
  • IC1 Incompleteness & stubs — measured, with a gap in what it reached — Watchdog measured this, but not all of it. What it did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. 241 further occurrence(s) are not listed individually; the score already reflects all 281.
  • P5 DR & Backup — not measured this run — This is a true statement about the repository that carries nothing for its owner to act on, so it is reported here rather than as a defect in their code. No backup/snapshot/replication config, RTO/RPO or restore-procedure documentation was found — and no production persistence was detected either (no data-access packages, no data-store services, no database resources), so there is nothing in this repository whose loss a DR control would recover. If this system's data lives in a platform or ops repo we can't see, that's where the DR evidence belongs.
  • X3 Exception handling — measured, with a gap in what it reached — Watchdog measured this, but not all of it. What it did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. 83 further occurrence(s) are not listed individually; the score already reflects all 123.

Repo exclusion declarations (.gitattributes linguist-generated/vendored, .editorconfig generated_code): none declared — every source file was scored.

Limitations & what we did not check

Watchdog assesses the repository exactly as committed, and only the repository. By design it does not reach outside the source tree: the live cloud account, the running CI/CD pipeline, the host's branch-protection and approval rules, the production configuration, or a restore actually exercised against a backup are all out of scope. That boundary is a feature, not a gap — a repo-relative, deterministic scan re-runs identically on any commit and every finding opens at a real file and line, where a live audit can neither be reproduced nor traced. The visible consequence is that controls which leave no in-repo evidence are reported as "not evidenced" and excluded from the score rather than awarded a number a static scan cannot justify.

Per-dimension blind spots

For each dimension that was measured, what a static, repo-only scan structurally cannot see — the honest edge of the measurement, not a failure of it.

  • D1 Cyclomatic Complexity: Cyclomatic complexity counts branches statically — it cannot tell an essential decision tree from accidental tangle, nor see complexity that lives in data or configuration (large switch-case token tables, DSL lexers/parsers, data-as-code rule tables) rather than control flow: a tokenizer's many single-character cases read as high complexity though each branch is trivial.
  • D2 Cognitive Complexity: Cognitive-complexity heuristics approximate how hard code is to follow; genuine domain difficulty and well-named intent that eases reading are not captured.
  • D3 God Classes: "God class" is sized by members and responsibilities visible in the type — a deliberately broad facade over a coherent subsystem can read the same as an accidental grab-bag. For front-end JS the file-length check is cohesion-aware (a single-responsibility module — one class/IIFE — earns a 3× threshold), but cohesion is approximated from top-level declarations, not true dependency structure.
  • D4 Code Duplication: Duplication is token-similarity — an in-process token-stream comparison over sliding windows, with type-aware normalization — so it finds copy-paste, not semantic duplication expressed differently. Committed machine-written code (scaffolded migrations, designer/codegen output, protobuf/OpenAPI stubs, model snapshots) is EXCLUDED — its repetition is the tool's, not the team's — so the score reflects hand-written duplication only.
  • D5 Coupling: Coupling is measured between projects/assemblies — runtime coupling through DI, reflection, messaging or shared databases is invisible to a static reference graph.
  • D6 Cohesion (LCOM4): LCOM4 cohesion is syntactic — it infers connectivity from which methods touch which fields/methods by name, not from real runtime behaviour or intent.
  • D9 Test Distribution: The test-pyramid shape is inferred from project/folder naming and references, with a single test host bucketed per-file by its path tier and content signals — a suite that names tiers unconventionally and gives no per-file signal can still be mis-bucketed.
  • D10 Test Quality: Assertion density is structural — it cannot tell a meaningful behavioural assertion from a trivial one, only that an assertion is present.
  • D13 Secret Scanning: Secret detection is signature- and entropy-based on the current tree — a secret that does not match a known pattern, or one already rotated, will not be flagged (a clean scan is "nothing matched", not "no secrets exist").
  • D14 License Compliance: License compatibility is checked against declared package metadata and a policy — mislabelled or missing license metadata, and obligations that depend on how you distribute, are not resolved here.
  • D15 Churn × Complexity Hotspots: Churn hotspots come from git history — a freshly imported or squashed repository has no churn signal, and recent rewrites can mask a historically risky file.
  • D17 Explicit Debt: Acknowledged-debt signals (TODO/FIXME, suppressions, dead code) are textual — undocumented debt that nobody marked, and debt that lives in design rather than annotations, is invisible. Committed machine-written code (scaffolded migrations, designer/codegen output, generated stubs) is excluded — it is never the team's dead code to delete.
  • 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.
  • AX10 Code composition: Role is inferred from namespace/folder convention, not semantics — a domain concept living in a folder named "Services" reads as application, and the split is lines-of-code, not business value. The business-logic-share score is a SOFT, FLOORED signal: it contributes to the Architecture lens but is floored at the Critical gate, so an infrastructure-heavy design (a gateway, an ETL, a driver) is legitimately low without being nuked to zero.
  • C4 Data Retention: This control is scored from in-repo evidence only — its real-world effectiveness, exercised only at runtime, is outside a static scan.
  • C5 Data-Subject Rights: This control is scored from in-repo evidence only — absence of evidence here means the scan found no in-repo trace, not that the control does not exist.
  • 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 Complexity6.9 / 10Adequate✓ 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 6.9 / 10 · rule-coverage 100% · ceiling Prevented

23 method(s) exceeded the cyclomatic complexity threshold of 15; the worst was BulkUninstallEntry.UninstallThread at 51. A further 3 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 Hresult.ConvertHresultToDetails at 259 — they are counted neither in the figure above nor in this dimension's score. 2 files carry no cyclomatic complexity row at all for this reason — every one of their over-threshold methods was excluded, so the exclusion is disclosed nowhere in the file itself: source/WinUpdateHelper/Hresult.cs (Hresult.ConvertHresultToDetails at 259), source/HelperTools/ResultWin32Extensions.cs (ResultWin32Extensions.ToException at 23). 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.

BulkUninstallEntry.UninstallThread (cyclomatic 51)source/UninstallTools/Uninstaller/BulkUninstallEntry.cs:283
Sift4.CommonDistance (cyclomatic 27)source/KlocTools/Tools/Sift4.cs:165
ApplicationEntryTools.AreEntriesRelated (cyclomatic 25)source/UninstallTools/Factory/ApplicationEntryTools.cs:32
ProcessTools.SeparateArgsFromCommand (cyclomatic 25)source/KlocTools/Tools/ProcessTools.cs:135
Sift4.GeneralDistance (cyclomatic 25)source/KlocTools/Tools/Sift4.cs:54

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

What to do

  1. Bring the 1 body over 30 down to 30 or less in Cyclomatic Complexity — start with BulkUninstallEntry.UninstallThread (cyclomatic 51). — Refactoring it lifts Cyclomatic Complexity from 6.9 to about 7.4/10.
  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.0 / 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.0 / 10 · rule-coverage 100% · ceiling Prevented

66 method(s) exceeded the cognitive complexity threshold of 15; the worst was BulkUninstallEntry.UninstallThread at 81.

BulkUninstallEntry.UninstallThread (cognitive 81)source/UninstallTools/Uninstaller/BulkUninstallEntry.cs:283
ComScanner.FindJunk (cognitive 75)source/UninstallTools/Junk/Finders/Registry/ComScanner.cs:34
Sift4.CommonDistance (cognitive 60)source/KlocTools/Tools/Sift4.cs:165
Sift4.GeneralDistance (cognitive 58)source/KlocTools/Tools/Sift4.cs:54
ProcessTools.SeparateArgsFromCommand (cognitive 50)source/KlocTools/Tools/ProcessTools.cs:135

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

What to do

  1. Bring the 2 bodies over 60 down to 60 or less in Cognitive Complexity — start with BulkUninstallEntry.UninstallThread (cognitive 81), ComScanner.FindJunk (cognitive 75). — This score is capped by its worst body, so a finding fixed alone moves it by almost nothing — the next one down takes its place. Refactoring these 2 together lifts Cognitive Complexity from 6.0 to about 6.4/10, projected with the scoring formula itself and assuming each lands exactly at 60; 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 Classes9.7 / 10Stronggated by 6 serious findings✓ 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 9.7 / 10 · rule-coverage 100% · ceiling Prevented

6 god class(es) detected.

TooManyMethods: MainWindow · ×2REDACTED
MethodTooLong: Tweaks.Tweaks(…) · ×2source/ScriptHelper/Tweaks.cs:36
FileTooLong: REDACTEDREDACTED
ClassTooLong: AppUninstallersource/BulkCrapUninstaller/Functions/AppUninstaller.cs

What to do

  1. Resolve the 2 TooManyMethods finding(s) in God Classes — start with REDACTED, MessageBoxes.cs. — One of this dimension's main actionable groups (2 warning-level).
  2. Resolve the 2 MethodTooLong finding(s) in God Classes — start with Tweaks.cs, BulkUninstallEntry.cs. — One of this dimension's main actionable groups (2 warning-level).
  3. Resolve the 1 FileTooLong finding(s) in God Classes — start with REDACTED. — One of this dimension's main actionable groups (1 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.9 / 10Stronggated by 17 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.9 / 10 · rule-coverage 100% · ceiling Verified

17 duplicated block group(s) detected.

Duplicated block (11 lines × 2) · ×2REDACTED:733
Duplicated block (9 lines × 2) · ×2source/BulkCrapUninstaller/Forms/Windows/UninstallProgressWindow.cs:340
Duplicated block (22 lines × 2)source/BulkCrapUninstaller/Functions/AppUninstaller.cs:476
Duplicated block (23 lines × 2)source/UninstallTools/Junk/Finders/Registry/AudioPolicyConfigScanner.cs:28
Duplicated block (21 lines × 2)source/UninstallTools/ApplicationEntrySerializer.cs:132

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

What to do

  1. Resolve the 2 Duplicated block (11 lines × 2) finding(s) in Code Duplication — start with REDACTED, Sift4.cs. — One of this dimension's main actionable groups (2 warning-level).
  2. Resolve the 2 Duplicated block (9 lines × 2) finding(s) in Code Duplication — start with UninstallProgressWindow.cs, FacebookButton.cs. — One of this dimension's main actionable groups (2 warning-level).
  3. Resolve the 1 Duplicated block (22 lines × 2) finding(s) in Code Duplication — start with AppUninstaller.cs. — One of this dimension's main actionable groups (1 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 · Coupling9.6 / 10Stronggated by 1 serious finding✓ 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 9.6 / 10 · rule-coverage 100% · ceiling Prevented

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

Off the main sequence: ObjectListViewsource/ObjectListView/ObjectListView.csproj:1

What to do

  1. Resolve the 1 Off the main sequence finding(s) in Coupling — start with ObjectListView.csproj. — One of this dimension's main actionable groups (1 warning-level).
  2. Enforce Coupling in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.

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

D6 · Cohesion (LCOM4)9.3 / 10Stronggated by 4 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.3 / 10 · rule-coverage 100% · ceiling Verified

4 of 68 classes have LCOM4 above 3.

Low cohesion: MainWindow (LCOM4 15) · ×4REDACTED:41

What to do

  1. Resolve the 4 Low cohesion finding(s) in Cohesion (LCOM4) — start with REDACTED (2), JunkRemoveWindow.cs, ApplicationUninstallerEntry.cs. — One of this dimension's main actionable groups (4 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

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

✓ On the Gold path — maintain.

Detailed fixes: d9_recommendation.md.

D10 · Test Quality10.0 / 10Exemplary✓ Tool-verified

What it measures: Whether the tests truly assert behaviour rather than just running the code.

Method: Per-test assertions, skips, and mock references analyzed via Roslyn; structured skip-reason tags (BUG:/ENV:) separate documented deferrals from debt. Deterministic.

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

0 skipped, 0 zero-assertion, no mocking-framework packages referenced (hand-written doubles or no mocking) across 53 tests.

✓ On the Gold path — maintain.

Detailed fixes: d10_recommendation.md.

D13 · Secret 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

Secret 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 129 packages use a banned license. ★ DEPTH: this repository's MSBuild projects declare 11 direct `PackageReference`(s), and 116 further package(s) were reached beyond them by closing the graph over nuget.org's own nuspec dependency graph — so a banned licence pulled in only by a dependency's OWN dependencies is inside this verdict. A package whose licence nuget.org could not be asked for is not graded, and version ranges are taken at their lower bound, so this is the closure as that graph states it rather than a restored consumer's exact resolution.

✓ On the Gold path — maintain.

Detailed fixes: d14_recommendation.md.

D15 · Churn × Complexity Hotspots10.0 / 10Exemplary✓ 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 10.0 / 10 · rule-coverage 100% · ceiling Documented

No churn × complexity hotspots in the window.

✓ On the Gold path — maintain.

Detailed fixes: d15_recommendation.md.

D17 · Explicit Debt7.9 / 10Adequategated by 91 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.9 / 10 · rule-coverage 100% · ceiling Prevented

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

EmptyCatchBlock · ×88source/BCU-console/Program.cs:118
NoWarnInCsproj · ×2source/BulkCrapUninstallerTests/BulkCrapUninstallerTests.csproj:6
InvertedExistenceGuardREDACTED:181
CommentedOutCode · ×23source/BulkCrapUninstaller/EntryPoint.cs:161
TodoComment · ×22source/BulkCrapUninstaller/Forms/Wizards/BeginUninstallTaskWizard.cs:119

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

What to do

  1. Resolve the 88 EmptyCatchBlock finding(s) in Explicit Debt — start with BulkUninstallEntry.cs (5), AdvancedFilters.cs (4), PathTools.cs (4). — One of this dimension's main actionable groups (88 issue-level).
  2. Resolve the 2 NoWarnInCsproj finding(s) in Explicit Debt — start with BulkCrapUninstallerTests.csproj (2). — One of this dimension's main actionable groups (2 issue-level).
  3. Resolve the 1 InvertedExistenceGuard finding(s) in Explicit Debt — start with REDACTED. — One of this dimension's main actionable groups (1 issue-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 Shape10.0 / 10Exemplary✓ 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 10.0 / 10 · rule-coverage 100% · ceiling Documented

18 projects, 570 source files, 95614 hand-written lines of code (94981 production / 633 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 19762 generated (machine-written code — designer, scaffolded and tool-emitted files — excluded from quality), 21 inter-project edges (build NOT measured — `dotnet build` did not complete in the analyzer, so the build half of this dimension is unmeasured rather than failed: the score above rests on structure alone and is not capped. The diagnostics that stopped it are named under Limitations.)

✓ On the Gold path — maintain.

Detailed fixes: d18_recommendation.md.

D19 · Documentation QualityStrong◐ 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 Strong / 10 · rule-coverage 100% · ceiling Documented

The root README and BCU_manual.html together provide a clear overview (what BCUninstaller does, its Apache 2.0 license, where to find the docs), download instructions, and an extensive table of contents for the architecture/design documentation. The BCU_manual.html is a well-structured reference guide covering installation, main window layout, uninstallation variants, concurrent/unstoppable uninstallers, advanced filtering/filter saving, custom scripts, command-line options, and more; it is clipped mid-table-of-contents at 'Bulk Crap Uninstaller v6', so the outline sections are present but not yet shown. The README itself is thin on installation/usage examples (only a brief overview of what each variant does) and lacks contribution guidance or licence, placing it in the root scope rather than the docs; its quality sits between the two.

XML-doc coverage: BulkCrapUninstaller · ×17source/BulkCrapUninstaller/BulkCrapUninstaller.csproj

What to do

  1. Improve Documentation Quality — currently 8.0/10. — The root README and BCU_manual.html together provide a clear overview (what BCUninstaller does, its Apache 2.0 license, where to find the docs), download instructions, and an extensive table of contents for the architecture/design documentation. The BCU_manual.html is a well-structured reference guide covering installation, main window layout, uninstallation variants, concurrent/unstoppable uninstallers, advanced filtering/filter saving, custom scripts, command-line options, and more; it is clipped mid-table-of-contents at 'Bulk Crap Uninstaller v6', so the outline sections are present but not yet shown. The README itself is thin on installation/usage examples (only a brief overview of what each variant does) and lacks contribution guidance or licence, placing it in the root scope rather than the docs; its quality sits between the two.

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

85 valuable / 0 redundant across 200 sampled comments.

✓ On the Gold path — maintain.

Detailed fixes: d24_recommendation.md.

D26 · Project Cohesion5.6 / 10Adequate✓ 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 5.6 / 10 · rule-coverage 100% · ceiling Documented

4 of 18 projects flagged as possibly oversized/incoherent.

Projects may be oversized for their cohesion

What to do

  1. Resolve the 1 Projects may be oversized for their cohesion finding(s) in Project Cohesion. — One of this dimension's main actionable groups (1 recommendation-level).

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

D27 · Navigability9.3 / 10Exemplary✓ 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 9.3 / 10 · rule-coverage 100% · ceiling Documented

96 % of calls cross a namespace and 2 % go through an interface, but 98 % of collaborators are co-located — so a call's collaborators sit together and tracing stays easy. Baseline: large — vertical-slice locality expected.

✓ On the Gold path — maintain.

Detailed fixes: d27_recommendation.md.

D28 · Secrets (history)8.0 / 10Adequategated by 2 critical findings✓ Tool-verified

What it measures: Whether any secrets were ever committed — scanned across the full git history, not just now.

Method: Secret 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 8.0 / 10 · rule-coverage 100% · ceiling Documented

2 finding(s): 0 critical, 2 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 2 High secret finding(s) in Secrets (history) — start with REDACTED, REDACTED. — One of this dimension's main actionable groups (2 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)1.4 / 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 1.4 / 10 · rule-coverage 100% · ceiling Documented

22 finding(s): 0 critical, 7 high, 15 medium, 0 low. semgrep hit a parse error in 4 file(s) — `source/HelperTools/LogWriter.cs` (lines 14–15, line 136), `source/KlocTools/Forms/Tools/PremadeDialogs.cs` (line 74), `source/KlocTools/IO/MsiTools.cs` (line 165), `source/UninstallTools/Uninstaller/NoWayToUninstallException.cs` (line 10) — 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 3 of those file(s) — `source/HelperTools/LogWriter.cs`, `source/KlocTools/Forms/Tools/PremadeDialogs.cs`, `source/UninstallTools/Uninstaller/NoWayToUninstallException.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) — `source/KlocTools/Forms/Tools/PremadeDialogs.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

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

What to do

  1. Resolve the 10 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (4), REDACTED, REDACTED. — One of this dimension's main actionable groups (10 warning-level).
  2. Resolve the 5 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (2), REDACTED, REDACTED. — One of this dimension's main actionable groups (5 issue-level).
  3. Resolve the 1 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).

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

D34 · Knowledge Freshness9.9 / 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.9 / 10 · rule-coverage 100% · ceiling Documented

1 of 196 significant source file(s) are orphaned — their living knowledge has decayed to nothing, so no one currently understands them. The largest is source/UninstallTools/Factory/Json/DynamicStringArrayConverter.cs. Counted over 196 of the 353 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.

Orphaned files with no living knowledge
Orphaned filesource/UninstallTools/Factory/Json/DynamicStringArrayConverter.cs:1

✓ On the Gold path — maintain.

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

D35 · Change Coupling10.0 / 10Exemplary✓ 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 10.0 / 10 · rule-coverage 100% · ceiling Documented

No strong hidden change-coupling between production files.

✓ On the Gold path — maintain.

Detailed fixes: d35_recommendation.md.

D36 · Supply-chain Provenance & Signing2.5 / 10Weak✓ 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 2.5 / 10 · rule-coverage 100% · ceiling Documented

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

REDACTED
REDACTED
REDACTED
REDACTED

What to do

  1. Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 recommendation-level).
  2. Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 recommendation-level).
  3. Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 recommendation-level).

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

Frontend & cross-cutting dimensions

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

AX10 · Code composition9.9 / 10Exemplary✓ 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.
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 UninstallTools ↔ UninstallTools.Factory ↔ UninstallTools.Factory.InfoAdders ↔ UninstallTools.Junk ↔ UninstallTools.Junk.Confidence ↔ UninstallTools.Junk.Containers ↔ UninstallTools.Startup depend on each other. The lightest dependency in the cycle is UninstallTools → UninstallTools.Factory (UninstallTools.UninstallToolsGlobalConfig → UninstallTools.Factory.ApplicationUninstallerFactoryCache, 1 type pair(s)); cut that one first, e.g. by moving the shared type to a namespace both can use or inverting it behind an interface. — source/UninstallTools/UninstallToolsGlobalConfig.cs:11
  • The namespaces BulkCrapUninstaller.Controls ↔ BulkCrapUninstaller.Controls.Settings ↔ BulkCrapUninstaller.Forms ↔ BulkCrapUninstaller.Functions ↔ BulkCrapUninstaller.Functions.ApplicationList ↔ BulkCrapUninstaller.Functions.Ratings ↔ BulkCrapUninstaller.Functions.Tools ↔ BulkCrapUninstaller.Properties depend on each other. The lightest dependency in the cycle is BulkCrapUninstaller.Controls → BulkCrapUninstaller.Properties (BulkCrapUninstaller.Controls.PropertiesSidebar → BulkCrapUninstaller.Properties.Settings, 1 type pair(s)); cut that one first, e.g. by moving the shared type to a namespace both can use or inverting it behind an interface. — source/BulkCrapUninstaller/Controls/Settings/PropertiesSidebar.cs:14

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 segregation10.0 / 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.

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 Protection3.5 / 10Weak✓ 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.

What to do

  • Strengthen data-at-rest protection: vault your keys (Azure Key Vault / AWS KMS / IDataProtector key ring) and encrypt the most sensitive columns (EF HasConversion encryption or provider-native column encryption) — partial coverage still leaves gaps.
  • Enforce HTTPS (UseHttpsRedirection / RequireHttpsMetadata) so data in transit is always encrypted.
C4 · Data Retention5.0 / 10Adequate✓ Tool-verified

Other · Security — Whether data has a defined lifetime — retention periods, TTLs, cleanup jobs (storage limitation).

Method: Roslyn scan: retention/TTL configuration presence in schema; CascadeDelete detected but not scored as retention control. Deterministic, gated by PII presence.

  • A retention mechanism is present, but the data-lifecycle is not yet complete — missing: an expiry limit — a declared maximum age / TTL after which the data is no longer kept, a scheduled purge / cleanup job (PurgeOlderThan / CleanupJob).

What to do

  • Complete the data-lifecycle story: an expiry limit (a declared maximum age for the stored data — a retention-age setting, or a store-level TTL where your storage offers one), a scheduled purge/cleanup job that enforces it, and a documented retention period covering the personal data.
C5 · Data-Subject Rights2.0 / 10Critical✓ Tool-verified

Other · Security — Whether GDPR data-subject requests are supported in code — erasure, export/portability, consent.

Method: Roslyn scan: GDPR data-subject-rights corroboration (erasure/export/consent vocabulary co-occurring with subject-id store crossing or explicit GDPR pattern). Deterministic, gated by PII.

  • Corroborated rights: erasure ✗ · export ✗ · consent ✓. Each tick means this scan found code in the repository implementing that right — a deletion/anonymisation path for erasure, a data-export or portability path for export, and consent state recorded alongside the personal data it authorises. A ✗ therefore means no such code was recognised HERE, not that the right is unsupported: a capability provided by a platform, a manual runbook, or code spelled in a way this scan does not match is not visible to it. Confirm before treating a cross as a gap; where it is one, the right has to be fulfilled manually.

What to do

  • Implement erasure ('right to be forgotten') over the data subject's records, tied to their subject/user id.
  • Implement data export/portability for a data subject (a machine-readable export of their personal data).
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. (×6) — source/UninstallTools/Factory/InfoAdders/InfoAdderManager.cs:141, source/UninstallTools/Factory/Json/DynamicStringArrayConverter.cs:84, source/UninstallTools/Factory/Json/PowerShellDateTimeOffsetConverter.cs:46, …

What to do

  • Finish or delete NotImplementedException stubs and replace placeholder literals before shipping.
IC1 · Incompleteness & stubs7.5 / 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.

  • `Pause` is a shipped member whose body only throws — and it is REACHED: source/UninstallerAutomatizer/Forms/MainWindow.cs:103 references it. This is not dead surface that can be deleted — anything taking that path throws at runtime. Implement the member, or remove the code that reaches it. — source/UninstallerAutomatizer/Automation/UninstallHandler.cs:34
  • `Resume` is a shipped member whose body only throws — and it is REACHED: source/UninstallerAutomatizer/Forms/MainWindow.cs:101 references it. This is not dead surface that can be deleted — anything taking that path throws at runtime. Implement the member, or remove the code that reaches it. — source/UninstallerAutomatizer/Automation/UninstallHandler.cs:39
  • The first 1 statement of the `if` and of the `else` are identical, so it runs on both paths regardless of the condition. Lift it above the `if` — leaving it duplicated inside makes the branches read as though they handled this differently. — source/NBug_custom/Settings.cs:736
  • `InsertObjects` is a shipped member whose whole body throws NotImplementedException — scaffolding that was never completed. Implement it or remove the dead surface. — source/ObjectListView/TreeListView.cs:1641
  • `TryAddFieldInformation` is a shipped member whose whole body throws NotImplementedException — scaffolding that was never completed. Implement it or remove the dead surface. — source/UninstallTools/Factory/InfoAdders/InfoAdderManager.cs:141
  • `Write` is a shipped member whose whole body throws NotImplementedException — scaffolding that was never completed. Implement it or remove the dead surface. (×2) — source/UninstallTools/Factory/Json/DynamicStringArrayConverter.cs:84, source/UninstallTools/Factory/Json/PowerShellDateTimeOffsetConverter.cs:46
  • A line of code has been commented out rather than removed — dead weight that rots and confuses. Delete it (version control remembers). (×31) — source/BulkCrapUninstaller/Controls/Settings/AdvancedFilters.cs:247, source/BulkCrapUninstaller/EntryPoint.cs:162, source/BulkCrapUninstaller/EntryPoint.cs:166, …
  • 4 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). — REDACTED:1126
  • 18 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). — REDACTED:1131

What to do

  • Finish or delete the unfinished stubs (NotImplementedException / empty / constant-returning bodies) — they are dead surface that looks live.
  • Clear the softer debt: remove commented-out code and dead branches, re-enable or delete skipped tests, and replace blanket warning suppressions with targeted ones.
M1 · Documentation (README)6.7 / 10Adequate✓ 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 18 of 18 project(s) that lack one — worth up to 2 pts.
M2 · Architecture documentation3.0 / 10Weak✓ 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.

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.
M3 · Folder & project structure6.0 / 10Adequate✓ 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.

  • Tests aren't grouped in a dedicated test folder — the test surface isn't separable from production code at a glance.
  • Only 2/18 projects share a common root namespace — the code's module identity is inconsistent.

What to do

  • Group tests in the folder your build system expects (tests/, test/, spec/, or your module's test source set) so the test surface is discoverable and CI can scope it.
  • Adopt a consistent root-namespace convention (a shared prefix, e.g. Acme.*); short project-file/directory names are fine as long as the RootNamespace is uniform.
M4 · Documentation accuracy9.6 / 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.

  • README.md names .NET 6, but the projects target .NET 8. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — README.md:43

What to do

  • Reconcile the README with reality: README.md names .NET 6, but the projects target .NET 8.
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.

P2 · Observability5.1 / 10Adequate✓ Tool-verified

Readiness · Readiness — Whether the code is diagnosable in production — structured logging, tracing/metrics, health checks.

Method: Filesystem/Roslyn scan: structured-logging frameworks (Serilog, NLog), OpenTelemetry, and health-check endpoint patterns. Exhaustive, deterministic.

  • Only 6/17 service-like projects use logging (pure contract/DTO projects are excluded — they have nothing to log). Of those 17, 10 ship a process this repository operates; the rest are libraries their consumer hosts, where the logging decision belongs to the host.
  • `REDACTED` reports through `Console.Write…` at line 169 although other files in its project log through a logger. Console lines carry no level, category or structured properties and never reach the log pipeline or its exporters. — REDACTED:169
  • `REDACTED` reports through `Console.Write…` at line 232 although other files in its project log through a logger. Console lines carry no level, category or structured properties and never reach the log pipeline or its exporters. — REDACTED:232
  • `REDACTED` reports through `Console.Write…` at line 251 although other files in its project log through a logger. Console lines carry no level, category or structured properties and never reach the log pipeline or its exporters. — REDACTED:251
  • `REDACTED` reports through `Console.Write…` at line 330 although other files in its project log through a logger. Console lines carry no level, category or structured properties and never reach the log pipeline or its exporters. — REDACTED:330
  • `REDACTED` reports through `Console.Write…` at line 351 although other files in its project log through a logger. Console lines carry no level, category or structured properties and never reach the log pipeline or its exporters. — REDACTED:351
  • `source/UninstallerAutomatizer/Automation/UninstallHandler.cs` reports through `Console.Write…` at line 189 although other files in its project log through a logger. Console lines carry no level, category or structured properties and never reach the log pipeline or its exporters. — source/UninstallerAutomatizer/Automation/UninstallHandler.cs:189
  • `source/UninstallerAutomatizer/Automation/UninstallHandler.cs` reports through `Console.Write…` at line 259 although other files in its project log through a logger. Console lines carry no level, category or structured properties and never reach the log pipeline or its exporters. — source/UninstallerAutomatizer/Automation/UninstallHandler.cs:259

What to do

  • Extend structured logging across the projects you operate, and give the library ones a diagnostics seam instead — an `EventSource`/`ActivitySource` the host can subscribe to, or an optional logger on your options object — rather than taking a logging dependency on your consumers' behalf.
  • Replace `Console.Write…` in service code with the project's injected `ILogger<T>` (message templates with named properties), so delivery outcomes and failures reach the log pipeline with a level and a category.
  • For more than a log file, an `ActivitySource`/`EventSource` the user can switch on gives you a structured trace to attach to a bug report. A health-check endpoint does not apply here: nothing orchestrates or load-balances a binary the user launches.
P3 · Security & performance tooling0.0 / 10Critical✓ 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 2777 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.
  • Enable Dependabot/Renovate or a dependency-review gate.
  • 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.
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 Hygiene0.0 / 10Critical✓ 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.

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.

  • `PutAsync` sends a `null` body, so the whole request travels in the URL — including the interpolated `userId` query parameter. Query strings are written verbatim to the server's and every intermediary's access logs, and to `Referer` headers; a request BODY is not, and HTTPS does not change that because the log line is written by whatever terminated the TLS. — source/BulkCrapUninstaller/Functions/Ratings/UninstallerRatingManager.cs:67
  • MD5/SHA1 is constructed here, and both are collision-broken. If this digest protects anything — a signature, an integrity or tamper check, a credential, or any value an attacker can influence — that is a real weakness: use SHA-256+ for content integrity, or a KDF (PBKDF2/Argon2/BCrypt) for password storage. If it only derives a non-security identifier (a cache key, a file or mutex name), collision resistance carries no security consequence here; make that intent explicit instead — a non-cryptographic hash such as `System.IO.Hashing.XxHash64`/`Crc32` says it in code — since the algorithm alone cannot distinguish the two uses. — source/BulkCrapUninstaller/Functions/Ratings/UninstallerRatingManager.Utils.cs:57
  • This type encrypts through `SymmetricAlgorithm`, whose every cipher mode (CBC/ECB/OFB/CFB/CTS) is unauthenticated, and no keyed MAC or AEAD cipher appears anywhere in it — so nothing establishes that the ciphertext it produced is the ciphertext it later reads back. Encryption alone provides confidentiality, not integrity: unauthenticated CBC is MALLEABLE, and an attacker who can modify stored or transmitted ciphertext can flip chosen plaintext bits in the following block by flipping ciphertext bits in the preceding one, without ever knowing the key. Where the decrypt path reports failure differently for a padding error than for a downstream one — a broad `catch` that returns null is the usual spelling — the same construction also answers the attacker's questions, which is the padding-oracle shape that recovers plaintext outright. Prefer an AEAD cipher: `AesGcm` or `ChaCha20Poly1305` authenticate the ciphertext as part of encrypting it, and give you an associated-data slot for the surrounding context. Where the format cannot change, MAC it with encrypt-then-MAC — HMAC-SHA256 over the IV and the ciphertext together, with a key derived separately from the encryption key — and verify that tag with `CryptographicOperations.FixedTimeEquals` BEFORE decrypting anything. — source/NBug_custom/Settings.cs:926
  • This encryption's initialisation vector is derived from `cipher`, the same key derivation as the key, so every message encrypted under the same key gets the same IV. An IV is not a secret and does not have to be one — its whole job is to be DIFFERENT each time, so that encrypting the same plaintext twice does not produce the same ciphertext. Fix it and CBC becomes an equality oracle: the mode XORs the IV into the first plaintext block and chains from there, so two messages encrypted with the same key and IV produce byte-identical ciphertext for exactly as long as their plaintexts agree. An observer who can see two ciphertexts — a repository of encrypted config files, a database column, a backup — learns that two records match and how many blocks in they diverge, without the key and without breaking anything. The same defect under a counter-based mode is worse and not recoverable by comparison: CTR and GCM XOR the plaintext against a keystream determined by the key and nonce, so a repeated nonce leaks the XOR of the two plaintexts outright, and under GCM it also forfeits the authentication key. Generate the IV with a cryptographic RNG for each message — `RandomNumberGenerator.Fill(iv)` in .NET, `crypto.randomBytes(16)` in Node — and write it alongside the ciphertext (prepending the block is the usual spelling); the receiver reads it back from there. Deriving the IV from the key material is the specific trap to avoid: it looks like rigour and produces a constant, because the derivation's inputs do not change between messages. — source/NBug_custom/Settings.cs:926
  • This code fixes PBKDF2-SHA-1 at 3 iterations. A key-derivation function's only defence is the cost of ONE guess, and that cost is this number — the algorithm choice does not set it. Current OWASP guidance is 1,300,000 PBKDF2 iterations with HMAC-SHA1, 600,000 with SHA-256 and 210,000 with SHA-512; scrypt at N=2^17, r=8, p=1 (or an equivalent N·r·p product); Argon2id at 19 MiB of memory and 2 iterations (or an equivalent row); bcrypt at a work factor of at least 10. This figure divides the attacker's work by a factor of tens or hundreds against the same stolen hash, on hardware they already own. Where what is derived is short or low-entropy — a PIN, a numeric parental code, a four-character token — the whole keyspace falls in the time this parameter buys, and no salt or constant-time comparison changes that. Raise the count to the current published figure for the PRF you use, measure it on the slowest hardware that must run it (a target of roughly 100 ms per derivation is the usual budget), and read the value from configuration so a deployment can raise it again without a rebuild. Where the derived value must interoperate with a format someone else fixed, the count cannot move — derive a SEPARATE value for anything you own rather than inheriting the external format's price. (×2) — source/NBug_custom/Settings.cs:887, source/NBug_custom/Settings.cs:923

What to do

  • Move the payload out of the URL and into the request body — pass real content (`new StringContent(...)` / `PostAsJsonAsync(uri, payload)`) instead of `null`, and keep only non-identifying routing parameters in the query string. A URL is logged verbatim by the receiving server and every proxy in front of it; a body is not.
  • Review each MD5/SHA1 use by what it protects: replace it with SHA-256+ (or a KDF for passwords) where the digest is security-relevant, and switch it to a non-cryptographic hash (`System.IO.Hashing.XxHash64`/`Crc32`) where it only derives an identifier such as a cache key or a mutex name.
  • Authenticate ciphertext, do not just encrypt it: move to an AEAD cipher (`AesGcm`, `ChaCha20Poly1305`), or where the wire format is fixed, add encrypt-then-MAC with HMAC-SHA256 over IV+ciphertext under a separately derived key and verify the tag with `CryptographicOperations.FixedTimeEquals` before decrypting. Unauthenticated CBC is malleable, and a decrypt path that distinguishes padding failures from other failures is a padding oracle.
  • Generate a fresh random IV for every encryption with `RandomNumberGenerator.Fill` and store or transmit it next to the ciphertext, rather than fixing it in the source or deriving it from the key material — a derived IV is constant, because its inputs do not vary between messages. An IV need not be secret, only unpredictable and unique per message; under CTR/GCM a repeated nonce is catastrophic rather than merely leaky.
  • Raise the cost parameter to current guidance — PBKDF2 at 1,300,000 (HMAC-SHA1), 600,000 (SHA-256) or 210,000 (SHA-512) iterations; scrypt at N=2^17, r=8, p=1; bcrypt at a work factor of 10 or more — or move to a memory-hard KDF (Argon2id, scrypt) where the platform offers one. Read the parameter from configuration and tune it to roughly 100 ms per derivation on the slowest hardware that must run it, so the price can be raised again without shipping new code. This repository constructs a key derivation priced below the floor at 2 sites, not one: `source/NBug_custom/Settings.cs:887` (PBKDF2-SHA-1, 3 iterations), `source/NBug_custom/Settings.cs:923` (PBKDF2-SHA-1, 3 iterations). Each is a separate decision — fixing only the line this row cites leaves the others in place.
X1 · Async correctness1.6 / 10Critical✓ 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.

  • Reading `.Result` of a task that has not completed blocks this thread until it does — the same block as `.Wait()`: under a synchronization context (Blazor, a UI thread, classic ASP.NET) it deadlocks, and on the thread pool it parks a thread for as long as the work runs. `await` the task instead (make the caller `async`); where a synchronous entry point must stay, keep the block in ONE documented bridge with a timeout. (×7) — source/BulkCrapUninstaller/Functions/Ratings/UninstallerRatingManager.cs:37, source/BulkCrapUninstaller/Functions/Ratings/UninstallerRatingManager.cs:41, source/BulkCrapUninstaller/Functions/Ratings/UninstallerRatingManager.cs:67, …
  • `Process.WaitForExit` blocks the thread on I/O while `Process.WaitForExitAsync` exists to wait without one — inside a method that is already `async`, await the twin. — REDACTED:134

What to do

  • Sync-over-async (deadlock risk) through `.Result`
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 reader3.5 / 10Weak✓ Tool-verified

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.

  • `centralSize` is read from the stream being parsed at line 846 (`ReadInt32`), then used to size an array at line 858 — and nowhere in this method is `centralSize` bounded from above — compared to a limit, clamped, or checked against the input that remains (a zero or sign test, or the loop that counts up to it, bounds nothing). A file the caller did not write therefore chooses the size directly: a value near `int.MaxValue` allocates until the process dies, and a value that overflows the cast to `int` goes negative and throws out of a parser whose failure path was written for malformed input, not for hostile input. Bound `centralSize` against the bytes actually remaining in the stream before spending it. — source/NBug_custom/Core/Util/Storage/ZipStorer.cs:858

What to do

  • Each finding names the read that takes the length from the input and the site that spends it, and states that the value is never compared in between. Confirm from the two, then bound the length against the remaining stream before using it.
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.4 / 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.

  • `MainWindow` implements `IDisposable` — so it has told every caller it holds something worth releasing — and it constructs `_uninstallerListConfigurator` itself (line 52), which makes that instance its own. But `_uninstallerListConfigurator` is named in none of the methods the disposal search covered: `Dispose` (line 443) — that is `Dispose` plus every method `Dispose` calls BY NAME, so a release reached through an interface, a delegate or a base class is not followed and is worth checking before acting. On what was read, the type's disposal releases everything except the one thing it owns. A disposable the owner never disposes is held until finalization if its type has a finalizer, and forever if it does not — which for a synchronisation primitive, a timer, a stream or a handle means the resource accumulates once per instance for the life of the process. Release it in `Dispose` (`_uninstallerListConfigurator?.Dispose();`), or, if it truly does not need releasing, drop `IDisposable` from the type so the claim and the behaviour agree. — REDACTED:52
  • `MainWindow` implements `IDisposable` — so it has told every caller it holds something worth releasing — and it constructs `_listLegendWindow` itself (line 54), which makes that instance its own. But `_listLegendWindow` is named in none of the methods the disposal search covered: `Dispose` (line 443) — that is `Dispose` plus every method `Dispose` calls BY NAME, so a release reached through an interface, a delegate or a base class is not followed and is worth checking before acting. On what was read, the type's disposal releases everything except the one thing it owns. A disposable the owner never disposes is held until finalization if its type has a finalizer, and forever if it does not — which for a synchronisation primitive, a timer, a stream or a handle means the resource accumulates once per instance for the life of the process. Release it in `Dispose` (`_listLegendWindow?.Dispose();`), or, if it truly does not need releasing, drop `IDisposable` from the type so the claim and the behaviour agree. — REDACTED:54
  • `MainWindow` implements `IDisposable` — so it has told every caller it holds something worth releasing — and it constructs `_debugWindow` itself (line 55), which makes that instance its own. But `_debugWindow` is named in none of the methods the disposal search covered: `Dispose` (line 443) — that is `Dispose` plus every method `Dispose` calls BY NAME, so a release reached through an interface, a delegate or a base class is not followed and is worth checking before acting. On what was read, the type's disposal releases everything except the one thing it owns. A disposable the owner never disposes is held until finalization if its type has a finalizer, and forever if it does not — which for a synchronisation primitive, a timer, a stream or a handle means the resource accumulates once per instance for the life of the process. Release it in `Dispose` (`_debugWindow?.Dispose();`), or, if it truly does not need releasing, drop `IDisposable` from the type so the claim and the behaviour agree. — REDACTED:55
  • `MainWindow` implements `IDisposable` — so it has told every caller it holds something worth releasing — and it constructs `_uninstallerListPostProcesser` itself (line 73), which makes that instance its own. But `_uninstallerListPostProcesser` is named in none of the methods the disposal search covered: `Dispose` (line 443) — that is `Dispose` plus every method `Dispose` calls BY NAME, so a release reached through an interface, a delegate or a base class is not followed and is worth checking before acting. On what was read, the type's disposal releases everything except the one thing it owns. A disposable the owner never disposes is held until finalization if its type has a finalizer, and forever if it does not — which for a synchronisation primitive, a timer, a stream or a handle means the resource accumulates once per instance for the life of the process. Release it in `Dispose` (`_uninstallerListPostProcesser?.Dispose();`), or, if it truly does not need releasing, drop `IDisposable` from the type so the claim and the behaviour agree. — REDACTED:73
  • `dialog` is a `FolderBrowserDialog`, which implements `IDisposable`, and it is created here (line 692). Every use of it in `SelectFolder` 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 dialog = …;`), which releases it at the end of the scope on every path including a throw. — source/BulkCrapUninstaller/Functions/MessageBoxes.cs:692
  • `dialog` is a `FolderBrowserDialog`, which implements `IDisposable`, and it is created here (line 705). Every use of it in `SelectFolder` 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 dialog = …;`), which releases it at the end of the scope on every path including a throw. — source/BulkCrapUninstaller/Functions/MessageBoxes.cs:705
  • `searcher` is a `ManagementObjectSearcher`, which implements `IDisposable`, and it is created here (line 42). Every use of it in `GetServiceEntries` 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 searcher = …;`), which releases it at the end of the scope on every path including a throw. — source/UninstallTools/Startup/Service/ServiceEntryFactory.cs:42
  • `BulkUninstallTask` implements `IDisposable` — so it has told every caller it holds something worth releasing — and it constructs `_client` itself (line 265), which makes that instance its own. But `_client` is named in none of the methods the disposal search covered: `Dispose` (line 75) — that is `Dispose` plus every method `Dispose` calls BY NAME, so a release reached through an interface, a delegate or a base class is not followed and is worth checking before acting. On what was read, the type's disposal releases everything except the one thing it owns. A disposable the owner never disposes is held until finalization if its type has a finalizer, and forever if it does not — which for a synchronisation primitive, a timer, a stream or a handle means the resource accumulates once per instance for the life of the process. Release it in `Dispose` (`_client?.Dispose();`), or, if it truly does not need releasing, drop `IDisposable` from the type so the claim and the behaviour agree. — source/UninstallTools/Uninstaller/BulkUninstallTask.cs:265
  • `BulkUninstallTask` implements `IDisposable` — so it has told every caller it holds something worth releasing — and it constructs `_writer` itself (line 266), which makes that instance its own. But `_writer` is named in none of the methods the disposal search covered: `Dispose` (line 75) — that is `Dispose` plus every method `Dispose` calls BY NAME, so a release reached through an interface, a delegate or a base class is not followed and is worth checking before acting. On what was read, the type's disposal releases everything except the one thing it owns. A disposable the owner never disposes is held until finalization if its type has a finalizer, and forever if it does not — which for a synchronisation primitive, a timer, a stream or a handle means the resource accumulates once per instance for the life of the process. Release it in `Dispose` (`_writer?.Dispose();`), or, if it truly does not need releasing, drop `IDisposable` from the type so the claim and the behaviour agree. — source/UninstallTools/Uninstaller/BulkUninstallTask.cs:266
  • `searcher` is a `ManagementObjectSearcher`, which implements `IDisposable`, and it is created here (line 22). Every use of it in `GetWindowsFeatures` 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 searcher = …;`), which releases it at the end of the scope on every path including a throw. — source/KlocTools/IO/WmiQueries.cs:22
  • `bw` is a `BinaryWriter`, which implements `IDisposable`, and it is created here (line 133). Every use of it in `IconFromImage` 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 bw = …;`), which releases it at the end of the scope on every path including a throw. — source/KlocTools/Tools/DrawingTools.cs:133
  • `searcher` is a `ManagementObjectSearcher`, which implements `IDisposable`, and it is created here (line 86). Every use of it in `PopulateVolumeIdLookup` 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 searcher = …;`), which releases it at the end of the scope on every path including a throw. — source/KlocTools/Tools/PathTools.cs:86
  • `opCompletedEvent` is a `ManualResetEvent`, which implements `IDisposable`, and it is created here (line 30). Every use of it in `UninstallApp` 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 opCompletedEvent = …;`), which releases it at the end of the scope on every path including a throw. — REDACTED:30
  • `DataSourceAdapter` declares a finalizer (line 64), but nothing in the type is unmanaged: no `IntPtr`/`UIntPtr` or pointer field, no `SafeHandle`, no `HandleRef`, no `extern`/`DllImport` member and no `Marshal`/`GCHandle`/`NativeMemory` use. A finalizer can only release what the garbage collector cannot, so on a purely-managed type it releases nothing and costs something: every instance is put on the finalizer queue, survives at least one extra collection, and is then finalized on a thread that is NOT the disposing one — where the managed objects it touches may already have been finalized themselves. Delete the finalizer (and the `GC.SuppressFinalize` that exists to defuse it); if a handle is added later, wrap it in a `SafeHandle`, which brings its own correct finalization. — source/ObjectListView/Implementation/DataSourceAdapter.cs:64
  • `ImageRenderer` implements `IDisposable` — so it has told every caller it holds something worth releasing — and it constructs `tickler` itself (line 2732), which makes that instance its own. But `tickler` is named in none of the methods the disposal search covered: `Dispose` (line 2391) — that is `Dispose` plus every method `Dispose` calls BY NAME, so a release reached through an interface, a delegate or a base class is not followed and is worth checking before acting. On what was read, the type's disposal releases everything except the one thing it owns. A disposable the owner never disposes is held until finalization if its type has a finalizer, and forever if it does not — which for a synchronisation primitive, a timer, a stream or a handle means the resource accumulates once per instance for the life of the process. Release it in `Dispose` (`tickler?.Dispose();`), or, if it truly does not need releasing, drop `IDisposable` from the type so the claim and the behaviour agree. — source/ObjectListView/Rendering/Renderers.cs:2732
  • `serviceController` is a `ServiceController`, which implements `IDisposable`, and it is created here (line 187). Every use of it in `RestartOculusService` 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 serviceController = …;`), which releases it at the end of the scope on every path including a throw. — source/OculusHelper/OculusManager.cs:187
  • `smtpClient` is a `SmtpClient`, which implements `IDisposable`, and it is created here (line 115). Every use of it in `Send` 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 smtpClient = …;`), which releases it at the end of the scope on every path including a throw. — source/NBug_custom/Core/Submission/Web/Mail.cs:115
  • `Storer` declares a finalizer (line 36), but nothing in the type is unmanaged: no `IntPtr`/`UIntPtr` or pointer field, no `SafeHandle`, no `HandleRef`, no `extern`/`DllImport` member and no `Marshal`/`GCHandle`/`NativeMemory` use. A finalizer can only release what the garbage collector cannot, so on a purely-managed type it releases nothing and costs something: every instance is put on the finalizer queue, survives at least one extra collection, and is then finalized on a thread that is NOT the disposing one — where the managed objects it touches may already have been finalized themselves. Delete the finalizer (and the `GC.SuppressFinalize` that exists to defuse it); if a handle is added later, wrap it in a `SafeHandle`, which brings its own correct finalization. — source/NBug_custom/Core/Util/Storage/Storer.cs:36
  • `br` is a `BinaryReader`, which implements `IDisposable`, and it is created here (line 836). Every use of it in `ReadFileInfo` 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 br = …;`), which releases it at the end of the scope on every path including a throw. — source/NBug_custom/Core/Util/Storage/ZipStorer.cs:836
  • `cipher` is a `Rfc2898DeriveBytes`, which implements `IDisposable`, and it is created here (line 887). Every use of it in `Decrypt` 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 cipher = …;`), which releases it at the end of the scope on every path including a throw. — source/NBug_custom/Settings.cs:887
  • `cipher` is a `Rfc2898DeriveBytes`, which implements `IDisposable`, and it is created here (line 923). Every use of it in `Encrypt` 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 cipher = …;`), which releases it at the end of the scope on every path including a throw. — source/NBug_custom/Settings.cs:923

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 propagation4.0 / 10Weak✓ 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 0/1 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. — REDACTED:97

What to do

  • Thread a CancellationToken through async methods so work stops promptly on cancellation.
X20 · Mistyped argument guard6.8 / 10Adequate✓ Tool-verified

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.

  • The guard on line 77 rejects `appKey` and line 78 reports that rejection as `ArgumentNullException` — but the condition's own test `string.IsNullOrEmpty(appKey)` is true of a value that is NOT null: it is satisfied by an EMPTY `appKey`, and on that path `appKey` was already proven non-null by the very expression that decided it (`||` short-circuits, so the null test to its left had to be false to get here). So a caller who passes a valid empty argument is told a parameter was null. That is not a wording problem: the exception type is the contract. A caller catching `ArgumentNullException` to handle a real null swallows the empty case with it, and whoever reads the stack trace later is told a failure the source disproves. .NET separates the two on purpose — `ArgumentNullException.ThrowIfNull` and `ArgumentException.ThrowIfNullOrEmpty` are two helpers because they are two failures. Throw `ArgumentException` for the empty case, or split the guard and throw each on its own condition. — source/BulkCrapUninstaller/Functions/Ratings/UninstallerRatingManager.cs:78
  • The guard on line 97 rejects `flags` and line 97 reports that rejection as `ArgumentNullException` — but the condition's own test `flags.Length == 0` is true of a value that is NOT null: it is satisfied by an EMPTY `flags`, and on that path `flags` was already proven non-null by the very expression that decided it (`||` short-circuits, so the null test to its left had to be false to get here). So a caller who passes a valid empty argument is told a parameter was null. That is not a wording problem: the exception type is the contract. A caller catching `ArgumentNullException` to handle a real null swallows the empty case with it, and whoever reads the stack trace later is told a failure the source disproves. .NET separates the two on purpose — `ArgumentNullException.ThrowIfNull` and `ArgumentException.ThrowIfNullOrEmpty` are two helpers because they are two failures. Throw `ArgumentException` for the empty case, or split the guard and throw each on its own condition. — source/ObjectListView/Filtering/FlagClusteringStrategy.cs:97
  • The guard on line 98 rejects `flagLabels` and line 98 reports that rejection as `ArgumentNullException` — but the condition's own test `flagLabels.Length == 0` is true of a value that is NOT null: it is satisfied by an EMPTY `flagLabels`, and on that path `flagLabels` was already proven non-null by the very expression that decided it (`||` short-circuits, so the null test to its left had to be false to get here). So a caller who passes a valid empty argument is told a parameter was null. That is not a wording problem: the exception type is the contract. A caller catching `ArgumentNullException` to handle a real null swallows the empty case with it, and whoever reads the stack trace later is told a failure the source disproves. .NET separates the two on purpose — `ArgumentNullException.ThrowIfNull` and `ArgumentException.ThrowIfNullOrEmpty` are two helpers because they are two failures. Throw `ArgumentException` for the empty case, or split the guard and throw each on its own condition. — source/ObjectListView/Filtering/FlagClusteringStrategy.cs:98

What to do

  • Each finding names the throw and the test in its own condition that is true of a NON-null value. Confirm from the two, then throw the exception that describes what was actually wrong: `ArgumentException` for a value that arrived empty, or the .NET 8 helpers that spell the whole guard in one line and pick the type for you — `ArgumentException.ThrowIfNullOrEmpty(s)` / `ThrowIfNullOrWhiteSpace(s)` for strings, `ArgumentNullException.ThrowIfNull(x)` followed by `ArgumentOutOfRangeException.ThrowIfZero(x.Count)` for a collection. Splitting the two conditions is usually clearer than picking one exception for both: they are different failures and the caller may want to handle them differently.
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 materialisation10.0 / 10Exemplary○ Nothing flagged

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.

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 handling4.8 / 10Weak✓ 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. (×32) — source/BulkCrapUninstaller/Controls/Settings/AdvancedFilters.cs:180, source/BulkCrapUninstaller/Controls/Settings/AdvancedFilters.cs:183, source/BulkCrapUninstaller/Controls/Settings/AdvancedFilters.cs:201, …
  • `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) — source/BulkCrapUninstaller/CultureConfigurator.cs:196, source/BulkCrapUninstaller/Forms/Windows/UninstallProgressWindow.cs:269, source/BulkCrapUninstaller/Functions/ApplicationList/ListViewDelegates.cs:137, …
  • 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). — REDACTED:459
  • `catch (IOException)` 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. — source/UninstallTools/Factory/DirectoryFactory.cs:207
  • `catch (UnauthorizedAccessException)` 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. — source/UninstallTools/Factory/DirectoryFactory.cs:211
  • `catch (ArgumentException)` 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. — source/UninstallTools/Factory/FactoryTools.cs:78

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 logging10.0 / 10Exemplary○ Nothing flagged

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.

X5 · Nullable reference types2.0 / 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 `otherBcu`: line 126 writes `otherBcu?.MainWindowHandle`, which says `otherBcu` can be null, but line 131 then dereferences it directly as `otherBcu.MainWindowHandle` 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 `otherBcu` truly cannot be null here, the `?.` is misleading. Settle it one way — test `otherBcu` once before the first use and handle the null case, or drop the `?.` — rather than leaving the two readings side by side. — source/BulkCrapUninstaller/EntryPoint.cs:131
  • This method contradicts itself about `result`: line 27 assigns it with `as bool?`, which hands back null rather than throwing when the value is not a `bool?`, but line 28 then dereferences it directly as `result.ToYesNo` 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 `result` once before the first use and handle the null case, or cast with `(bool?)` so the failure is reported where it happens — rather than leaving the two readings side by side. — source/BulkCrapUninstaller/Functions/ApplicationList/ListViewDelegates.cs:28
  • This method contradicts itself about `subKey`: line 193 writes `subKey?.GetStringSafe`, which says `subKey` can be null, but line 202 then dereferences it directly as `subKey.SetValue` 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 `subKey` truly cannot be null here, the `?.` is misleading. Settle it one way — test `subKey` once before the first use and handle the null case, or drop the `?.` — rather than leaving the two readings side by side. — REDACTED:202
  • This method contradicts itself about `x`: line 115 writes `x?.Name`, which says `x` can be null, but line 111 then dereferences it directly as `x.GetDirectories` 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 `x` truly cannot be null here, the `?.` is misleading. Settle it one way — test `x` once before the first use and handle the null case, or drop the `?.` — rather than leaving the two readings side by side. — source/UninstallTools/Factory/DirectoryFactory.cs:111
  • This method contradicts itself about `guidKey`: line 246 writes `guidKey?.`, which says `guidKey` can be null, but line 253 then dereferences it directly as `guidKey.OpenSubKey` 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 `guidKey` truly cannot be null here, the `?.` is misleading. Settle it one way — test `guidKey` once before the first use and handle the null case, or drop the `?.` — rather than leaving the two readings side by side. — source/UninstallTools/Junk/Finders/Registry/ComScanner.cs:253
  • This method contradicts itself about `subkey`: line 40 writes `subkey?.GetStringSafe`, which says `subkey` can be null, but line 43 then dereferences it directly as `subkey.Name` 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 `subkey` truly cannot be null here, the `?.` is misleading. Settle it one way — test `subkey` once before the first use and handle the null case, or drop the `?.` — rather than leaving the two readings side by side. — source/UninstallTools/Junk/Finders/Registry/EventLogScanner.cs:43
  • This method contradicts itself about `classKey`: line 72 writes `classKey?.GetStringSafe`, which says `classKey` can be null, but line 77 then dereferences it directly as `classKey.OpenSubKey` 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 `classKey` truly cannot be null here, the `?.` is misleading. Settle it one way — test `classKey` once before the first use and handle the null case, or drop the `?.` — rather than leaving the two readings side by side. — source/UninstallTools/Startup/Browser/BrowserEntryFactory.cs:77
  • This method contradicts itself about `defaultSetting`: line 947 assigns it with `as DefaultSettingValueAttribute`, which hands back null rather than throwing when the value is not a `DefaultSettingValueAttribute`, but line 953 then dereferences it directly as `defaultSetting.Value` 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 `defaultSetting` once before the first use and handle the null case, or cast with `(DefaultSettingValueAttribute)` so the failure is reported where it happens — rather than leaving the two readings side by side. — source/NBug_custom/Settings.cs:953
  • 0/17 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.

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 Health40%Weak — gated by X1, X5Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Architecture96%ExemplarySolid.
Maturity61%Adequate — gated by M2Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Readiness49%Weak — gated by P3Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Security22%Critical — gated by D29, D36, C1, C5, S1Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Performance100%ExemplaryStrongest area.
Unscored — 3 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.

  • SC1 Supply-chain hygiene — 1 observation(s) recorded · Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
  • X10 Duplicated predicate — 8 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
  • X7 Silent fallback defaults — 18 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
Not evidenced — 2 control(s) we could not find positive evidence for

These checks grade a working control, and the repository shows no evidence of one. That is deliberately not scored as a zero: a repository cannot show an ops runbook, a database TTL or an infrastructure-side audit log, so absence of evidence here is not evidence the control is missing. It is also not a statement that the check is irrelevant to this codebase — the thing it grades applies; we just could not see it. Excluded from the score either way.

  • C3 Audit Trail — Repo shows no audit-logging mechanism (IAuditable, an immutable audit log, an EF SaveChanges interceptor) for sensitive changes — absence of evidence is not evidence of a working control. Record an audit trail in code (or document where it lives) so this dimension can be scored.
  • P5 DR & Backup — not evidenced — repo shows no backup/RTO/RPO controls; absence of evidence is not evidence of a working control
Not included — 44 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.
  • AX1 Captive dependencies — no DI registrations detected
  • AX2 Stateful singletons — no singleton implementations detected
  • AX7 Slice cohesion — not applicable — not a vertical-slice architecture
  • AX9 CQS / query purity — no CQRS query handlers detected — query purity is not applicable to this codebase
  • AXB1 Runtime evidence locked — no reproducible boot — This repository has nothing the runtime tiers could boot or serve — no markup, no UI framework or web-server dependency, no UI component source, no native UI project and no API definition — nothing here is a surface to boot — so runtime a11y/egress/header evidence has no subject here. Not applicable: this is neither a gap in the scan nor a finding about your code.
  • 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
  • D12 Dependency Hygiene — Dependency hygiene not measured
  • D16 Bus Factor — single-maintainer repository — bus factor is not applicable
  • D22 Internal API Consistency — No intentionally-exposed public API to evaluate for consistency.
  • D23 Boundary Type-Coupling — Cross-context type coupling could not be assessed — this codebase's bounded contexts are neither declared nor inferable.
  • D25 ADR Conformance — no ADRs to check
  • D30 Dependency Vulnerabilities — nuget: the solution did not restore on the analyzer's .NET SDK (an SDK/target-framework/restore mismatch, common for an older codebase), so there was no restored dependency graph to scan
  • D31 IaC & Container Security — No Infrastructure-as-Code or container manifests found (Dockerfile, Docker Compose, Terraform, Kubernetes/Helm, CloudFormation, ARM, Bicep, Ansible); nothing to scan.
  • D32 Data Compliance (PII/GDPR) — 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.
  • D43 Malicious Dependencies — Not scored — no dependency manifest in a supported ecosystem was read for this repository. A gap in the analyzer's language coverage, NOT a finding that the repository is free of vulnerable dependencies (a Python pyproject.toml/requirements.txt (pip/uv/Poetry), a Swift Package.swift/Package.resolved, a Cargo manifest, a Go module (go.mod/go.sum), a Gradle version catalogue, a Maven POM, an sbt build (build.sbt), composer.json, package.json, a Dart pubspec.yaml, an Elixir mix.exs/mix.lock (Hex), a rebar.config / erlang.mk DEPS (Hex), a Ruby Gemfile/Gemfile.lock or .gemspec (Bundler/RubyGems) — not scanned yet).
  • 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 none of the 3 signals this lens looks for
  • ED1 Event-Driven — not scored — this repository shows none of the 3 signals this lens looks for
  • ED5 Idempotency — no mutating command handlers or message consumers detected — idempotency check not applicable
  • ES1 Event Sourcing — not scored — this repository shows none of the 3 signals this lens looks for
  • P12 CI test-gate honesty — Reported, not scored — and nothing was matched here. The coverage check applies to any stack, and the automatic-re-run check to any GitHub-Actions workflow, but the checks for excluded tests, skipped tests and sleep-based synchronisation currently recognise only some ecosystems' test-runner idioms, so on a repository built with another stack the zeros below mean 'not checked', not 'clean'.
  • P7 Outbound HTTP resilience — not applicable — 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
  • PF1 Benchmark discipline — Performance is assessed only for perf-relevant repos — a packaged library, one that ships benchmarks, or one already using allocation-aware APIs. This repo isn't one, so the Performance lens is not applicable and is excluded from the score.
  • PF2 Allocation hygiene — Performance is assessed only for perf-relevant repos — a packaged library, one that ships benchmarks, or one already using allocation-aware APIs. This repo isn't one, so the Performance lens is not applicable and is excluded from the score.
  • 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 — 104 finding(s)
D17 · Explicit Debt · EmptyCatchBlock · ×88
  • EmptyCatchBlock source/BCU-console/Program.cs:118 — 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 source/BulkCrapUninstaller/Controls/Settings/AdvancedFilters.cs:180 — 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 source/BulkCrapUninstaller/Controls/Settings/AdvancedFilters.cs:183 — 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 source/BulkCrapUninstaller/Controls/Settings/AdvancedFilters.cs:201 — 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 source/BulkCrapUninstaller/Controls/Settings/AdvancedFilters.cs:204 — 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 REDACTED:40 — 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 source/BulkCrapUninstaller/Forms/Helpers/ListLegendWindow.cs:67 — 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 source/BulkCrapUninstaller/Forms/Helpers/ListLegendWindow.cs:74 — 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 source/BulkCrapUninstaller/Forms/Windows/JunkRemoveWindow.cs:167 — 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 REDACTED:459 — 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 REDACTED:1406 — 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 source/BulkCrapUninstaller/Functions/AppUninstaller.cs:170 — 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 source/BulkCrapUninstaller/Functions/AppUninstaller.cs:465 — 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 source/BulkCrapUninstaller/Functions/ApplicationList/ListViewDelegates.cs:151 — 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 source/BulkCrapUninstaller/Functions/ApplicationList/UninstallerListViewUpdater.cs:204 — 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 source/BulkCrapUninstaller/Functions/Ratings/RatingManagerWrapper.cs:43 — 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 source/BulkCrapUninstaller/Functions/Ratings/RatingManagerWrapper.cs:184 — empty catch block — the error is discarded with nothing recorded, so a failure here leaves no trace anywhere. Record it through whatever this codebase already uses to report problems, or let it propagate. Where swallowing one specific failure really is correct — as it often is on a teardown/dispose path where throwing would mask the original failure — catch exactly that exception type and write down WHY in a comment on the catch. Both are needed: a comment on a catch-all still swallows every failure nobody anticipated, and a note that only restates the swallow ("ignored", "do nothing") is read as no explanation at all.
  • EmptyCatchBlock source/BulkCrapUninstaller/Functions/Tools/SettingTools.cs:62 — 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 source/BulkCrapUninstaller/Functions/Tools/SettingTools.cs:76 — 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 source/BulkCrapUninstaller/Functions/Tools/UpdateGrabber.cs:105 — 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 source/BulkCrapUninstaller/Functions/Tracking/EventHook.cs:49 — 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 REDACTED: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 REDACTED:116 — 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 source/KlocTools/Collections/ObservedList.cs:99 — 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 source/KlocTools/Extensions/FormsExtensions.cs:155 — 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.
  • + 63 more in this group — see findings.md.
D29 · Static Analysis (SAST) · REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
AX3 · Project dependency cycles · Namespace dependency cycle · ×2
  • Namespace dependency cycle source/UninstallTools/UninstallToolsGlobalConfig.cs:11 — The namespaces UninstallTools ↔ UninstallTools.Factory ↔ UninstallTools.Factory.InfoAdders ↔ UninstallTools.Junk ↔ UninstallTools.Junk.Confidence ↔ UninstallTools.Junk.Containers ↔ UninstallTools.Startup depend on each other. The lightest dependency in the cycle is UninstallTools → UninstallTools.Factory (UninstallTools.UninstallToolsGlobalConfig → UninstallTools.Factory.ApplicationUninstallerFactoryCache, 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 source/BulkCrapUninstaller/Controls/Settings/PropertiesSidebar.cs:14 — The namespaces BulkCrapUninstaller.Controls ↔ BulkCrapUninstaller.Controls.Settings ↔ BulkCrapUninstaller.Forms ↔ BulkCrapUninstaller.Functions ↔ BulkCrapUninstaller.Functions.ApplicationList ↔ BulkCrapUninstaller.Functions.Ratings ↔ BulkCrapUninstaller.Functions.Tools ↔ BulkCrapUninstaller.Properties depend on each other. The lightest dependency in the cycle is BulkCrapUninstaller.Controls → BulkCrapUninstaller.Properties (BulkCrapUninstaller.Controls.PropertiesSidebar → BulkCrapUninstaller.Properties.Settings, 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.
D17 · Explicit Debt · NoWarnInCsproj · ×2
  • NoWarnInCsproj source/BulkCrapUninstallerTests/BulkCrapUninstallerTests.csproj:6 — CA1707 — this warning is switched off for the WHOLE project, in every file it builds, including code written years from now: nothing at the call site records that the rule was ever silenced, so the next reader has no reason to look here. Fix what the rule is reporting and drop the code from the list, or — if some occurrences really are legitimate — narrow the suppression to those sites and give each one its reason, so the rule keeps protecting the rest of the project.
  • NoWarnInCsproj source/BulkCrapUninstallerTests/BulkCrapUninstallerTests.csproj:6 — CA1861 — this warning is switched off for the WHOLE project, in every file it builds, including code written years from now: nothing at the call site records that the rule was ever silenced, so the next reader has no reason to look here. Fix what the rule is reporting and drop the code from the list, or — if some occurrences really are legitimate — narrow the suppression to those sites and give each one its reason, so the rule keeps protecting the rest of the project.
D28 · Secrets (history) · High secret · ×2
  • REDACTED
  • REDACTED
IC1 · Incompleteness & stubs · Unfinished stub · ×2
  • Unfinished stub — throws NotImplementedException source/UninstallerAutomatizer/Automation/UninstallHandler.cs:34 — `Pause` is a shipped member whose body only throws — and it is REACHED: source/UninstallerAutomatizer/Forms/MainWindow.cs:103 references it. This is not dead surface that can be deleted — anything taking that path throws at runtime. Implement the member, or remove the code that reaches it.
  • Unfinished stub — throws NotImplementedException source/UninstallerAutomatizer/Automation/UninstallHandler.cs:39 — `Resume` is a shipped member whose body only throws — and it is REACHED: source/UninstallerAutomatizer/Forms/MainWindow.cs:101 references it. This is not dead surface that can be deleted — anything taking that path throws at runtime. Implement the member, or remove the code that reaches it.
D17 · Explicit Debt · InvertedExistenceGuard · ×1
  • InvertedExistenceGuard REDACTED:181 — if (!File.Exists(newPath)) File.Delete(newPath); — this branch is entered only in the state where the call it holds is documented to do nothing: deleting a path that does not exist, or creating a directory that already does. So the statement has no effect on any run, and the case it was written for — the path being there — is precisely the one that skips it, leaving whatever comes next to meet the file the author meant to have removed. Turn the condition around, so the work happens in the state that needs it; if the call really was meant to be unconditional, drop the guard instead, since these two calls are already safe to make either way.
D29 · Static Analysis (SAST) · REDACTED · ×1
  • REDACTED
S1 · Cryptographic Hygiene · Request payload sent in the URL query string · ×1
  • Request payload sent in the URL query string source/BulkCrapUninstaller/Functions/Ratings/UninstallerRatingManager.cs:67 — `PutAsync` sends a `null` body, so the whole request travels in the URL — including the interpolated `userId` query parameter. Query strings are written verbatim to the server's and every intermediary's access logs, and to `Referer` headers; a request BODY is not, and HTTPS does not change that because the log line is written by whatever terminated the TLS.
Serious — 283 finding(s)
X3 · Exception handling · Swallowed exception (empty catch) · ×33
  • Swallowed exception (empty catch) source/BulkCrapUninstaller/Controls/Settings/AdvancedFilters.cs:180 — 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) source/BulkCrapUninstaller/Controls/Settings/AdvancedFilters.cs:183 — 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) source/BulkCrapUninstaller/Controls/Settings/AdvancedFilters.cs:201 — 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) source/BulkCrapUninstaller/Controls/Settings/AdvancedFilters.cs:204 — 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) REDACTED:40 — 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) source/BulkCrapUninstaller/Forms/Helpers/ListLegendWindow.cs:67 — 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) source/BulkCrapUninstaller/Forms/Helpers/ListLegendWindow.cs:74 — 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) source/BulkCrapUninstaller/Forms/Windows/JunkRemoveWindow.cs:167 — 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) REDACTED:459 — 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) REDACTED:1406 — 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) source/BulkCrapUninstaller/Functions/ApplicationList/ListViewDelegates.cs:151 — 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) source/BulkCrapUninstaller/Functions/ApplicationList/UninstallerListViewUpdater.cs:204 — 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) source/BulkCrapUninstaller/Functions/AppUninstaller.cs:170 — 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) source/BulkCrapUninstaller/Functions/AppUninstaller.cs:465 — 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) source/BulkCrapUninstaller/Functions/Ratings/RatingManagerWrapper.cs:43 — 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) source/BulkCrapUninstaller/Functions/Ratings/RatingManagerWrapper.cs:184 — An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
  • Swallowed exception (empty catch) source/BulkCrapUninstaller/Functions/Tools/SettingTools.cs:62 — 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) source/BulkCrapUninstaller/Functions/Tools/SettingTools.cs:76 — 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) source/BulkCrapUninstaller/Functions/Tools/UpdateGrabber.cs:105 — 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) source/BulkCrapUninstaller/Functions/Tracking/EventHook.cs:49 — 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) REDACTED: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) REDACTED:116 — 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) source/UninstallTools/ApplicationUninstallerEntry.cs:532 — 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) source/UninstallTools/Controls/UninstallerIconGetter.cs:86 — 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) source/UninstallTools/Factory/ApplicationEntryTools.cs:171 — 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.
  • + 8 more in this group — see findings.md.
D17 · Explicit Debt · CommentedOutCode · ×23
  • CommentedOutCode source/BulkCrapUninstaller/EntryPoint.cs:161 — 3 consecutive commented-code lines
  • CommentedOutCode source/BulkCrapUninstaller/EntryPoint.cs:165 — 3 consecutive commented-code lines
  • CommentedOutCode REDACTED:1517 — 3 consecutive commented-code lines
  • CommentedOutCode source/KlocTools/Forms/CmbBasicSettings.cs:31 — 3 consecutive commented-code lines
  • CommentedOutCode source/KlocTools/Forms/CmbBasicSettings.cs:35 — 3 consecutive commented-code lines
  • CommentedOutCode source/KlocTools/Tools/WindowsTools.cs:597 — 3 consecutive commented-code lines
  • CommentedOutCode source/BulkCrapUninstaller/Forms/Helpers/DebugWindow.cs:83 — 9 consecutive commented-code lines
  • CommentedOutCode REDACTED:335 — 9 consecutive commented-code lines
  • CommentedOutCode source/UninstallTools/Uninstaller/BulkUninstallTask.cs:114 — 9 consecutive commented-code lines
  • CommentedOutCode REDACTED:1126 — 4 consecutive commented-code lines
  • CommentedOutCode source/UninstallTools/Factory/ScriptFactory.cs:33 — 4 consecutive commented-code lines
  • CommentedOutCode REDACTED:1131 — 18 consecutive commented-code lines
  • CommentedOutCode REDACTED:1498 — 5 consecutive commented-code lines
  • CommentedOutCode source/KlocTools/Forms/LoadingDialog.cs:69 — 5 consecutive commented-code lines
  • CommentedOutCode source/KlocTools/Forms/LoadingDialog.cs:75 — 5 consecutive commented-code lines
  • CommentedOutCode source/UninstallTools/ApplicationUninstallerEntry.cs:343 — 5 consecutive commented-code lines
  • CommentedOutCode source/BulkCrapUninstaller/Functions/MessageBoxes.cs:599 — 7 consecutive commented-code lines
  • CommentedOutCode REDACTED:156 — 7 consecutive commented-code lines
  • CommentedOutCode source/UninstallTools/Factory/ScriptFactory.cs:76 — 7 consecutive commented-code lines
  • CommentedOutCode source/ScriptHelper/Tweaks.cs:124 — 8 consecutive commented-code lines
  • CommentedOutCode source/UninstallTools/Factory/InfoAdders/AppExecutablesSearcher.cs:49 — 8 consecutive commented-code lines
  • CommentedOutCode source/UninstallTools/Uninstaller/BulkUninstallConfiguration.cs:10 — 8 consecutive commented-code lines
  • CommentedOutCode source/UninstallTools/Factory/InfoAdders/UninstallerTypeAdder.cs:102 — 6 consecutive commented-code lines
D17 · Explicit Debt · TodoComment · ×22
  • TodoComment source/BulkCrapUninstaller/Forms/Wizards/BeginUninstallTaskWizard.cs:119 — //todo show greeen text all closed? or skip when clicking next? slow — 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 source/BulkCrapUninstaller/Functions/Ratings/RatingManagerWrapper.cs:45 — //TODO: Handle this better? — 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:28 — //TODO This is a leftover class, extract the self installed detection logic and get rid of it — 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 source/KlocTools/Controls/EditableCheckedListView.cs:115 — //TODO fires before change happens — 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 source/KlocTools/IO/MsiTools.cs:125 — // TODO also include source? — 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 source/KlocTools/IO/MsiTools.cs:177 — // TODO: Might not be required? HKCR is virtualized and shows both 64 and 32 keys. Some 32bit apps might manage to put their keys in root too? — 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 source/KlocTools/IO/MsiTools.cs:208 — // TODO This is slow, on the order of ~8 seconds (4 with AsParallel) on an SSD. It could use caching of GetProductCode and _componentPathLookup — 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 source/KlocTools/IO/MsiTools.cs:231 — // TODO Use the lookups instead? Some products don't have any components though. — 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 source/KlocTools/Subsystems/GlobalHotkeys.cs:155 — //TODO does not work very well, need to ask for description at hotkey creation — 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 source/KlocTools/Subsystems/GlobalHotkeys.cs:170 — //TODO does not work very well, need to ask for description at hotkey creation — 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 source/SimpleTreeMap/TreeMap.cs:167 — // todo draw whole thing based on input, input is set by populate — 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 source/UninstallTools/Factory/InfoAdders/InfoAdderManager.cs:40 — // TODO Better sorting logic? If names change or props are added without uninstall in name they'll slip through — 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 source/UninstallTools/Factory/InfoAdders/InfoAdderManager.cs:58 — // TODO is this filtering neccessary? — 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 source/UninstallTools/Factory/InfoAdders/InfoAdderManager.cs:104 — //TODO prioritize ones with all values existing from same priority tier? — 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 source/UninstallTools/Factory/InfoAdders/InfoAdderManager.cs:143 — // TODO — 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 source/UninstallTools/Factory/InfoAdders/MsiInfoAdder.cs:43 — //nameof(ApplicationUninstallerEntry.SortedExecutables) // TODO: This works but is much too slow to run for every entry — 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 source/UninstallTools/Junk/Finders/JunkCreatorBase.cs:49 — // TODO overhaul — 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 source/UninstallTools/Junk/Finders/Registry/SoftwareRegKeyScanner.cs:146 — // TODO Add extra confidence if the key is, or will be empty after junk removal — 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 source/UninstallTools/Startup/Normal/StartupEntry.cs:142 — //TODO temporary hack — 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 source/UninstallTools/Startup/Normal/StartupEntry.cs:148 — //TODO temporary hack — 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 source/UninstallerAutomatizer/Automation/AutomatedUninstallManager.cs:423 — //todo check if this works — 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 source/UninstallerAutomatizer/Automation/UninstallHandler.cs:227 — // todo grace period / move to window? — 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.
X18 · Disposal-pattern correctness · Disposable created and abandoned in the method that made it · ×12
  • Disposable created and abandoned in the method that made it source/BulkCrapUninstaller/Functions/MessageBoxes.cs:692 — `dialog` is a `FolderBrowserDialog`, which implements `IDisposable`, and it is created here (line 692). Every use of it in `SelectFolder` 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 dialog = …;`), 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 source/BulkCrapUninstaller/Functions/MessageBoxes.cs:705 — `dialog` is a `FolderBrowserDialog`, which implements `IDisposable`, and it is created here (line 705). Every use of it in `SelectFolder` 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 dialog = …;`), 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 source/UninstallTools/Startup/Service/ServiceEntryFactory.cs:42 — `searcher` is a `ManagementObjectSearcher`, which implements `IDisposable`, and it is created here (line 42). Every use of it in `GetServiceEntries` 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 searcher = …;`), 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 source/KlocTools/IO/WmiQueries.cs:22 — `searcher` is a `ManagementObjectSearcher`, which implements `IDisposable`, and it is created here (line 22). Every use of it in `GetWindowsFeatures` 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 searcher = …;`), 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 source/KlocTools/Tools/DrawingTools.cs:133 — `bw` is a `BinaryWriter`, which implements `IDisposable`, and it is created here (line 133). Every use of it in `IconFromImage` 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 bw = …;`), 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 source/KlocTools/Tools/PathTools.cs:86 — `searcher` is a `ManagementObjectSearcher`, which implements `IDisposable`, and it is created here (line 86). Every use of it in `PopulateVolumeIdLookup` 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 searcher = …;`), 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 REDACTED:30 — `opCompletedEvent` is a `ManualResetEvent`, which implements `IDisposable`, and it is created here (line 30). Every use of it in `UninstallApp` 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 opCompletedEvent = …;`), 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 source/OculusHelper/OculusManager.cs:187 — `serviceController` is a `ServiceController`, which implements `IDisposable`, and it is created here (line 187). Every use of it in `RestartOculusService` 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 serviceController = …;`), 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 source/NBug_custom/Core/Submission/Web/Mail.cs:115 — `smtpClient` is a `SmtpClient`, which implements `IDisposable`, and it is created here (line 115). Every use of it in `Send` 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 smtpClient = …;`), 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 source/NBug_custom/Core/Util/Storage/ZipStorer.cs:836 — `br` is a `BinaryReader`, which implements `IDisposable`, and it is created here (line 836). Every use of it in `ReadFileInfo` 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 br = …;`), 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 source/NBug_custom/Settings.cs:887 — `cipher` is a `Rfc2898DeriveBytes`, which implements `IDisposable`, and it is created here (line 887). Every use of it in `Decrypt` 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 cipher = …;`), 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 source/NBug_custom/Settings.cs:923 — `cipher` is a `Rfc2898DeriveBytes`, which implements `IDisposable`, and it is created here (line 923). Every use of it in `Encrypt` 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 cipher = …;`), which releases it at the end of the scope on every path including a throw.
D29 · Static Analysis (SAST) · REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
X5 · Nullable reference types · Symbol treated as nullable, then dereferenced unguarded · ×8
  • Symbol treated as nullable, then dereferenced unguarded source/BulkCrapUninstaller/EntryPoint.cs:131 — This method contradicts itself about `otherBcu`: line 126 writes `otherBcu?.MainWindowHandle`, which says `otherBcu` can be null, but line 131 then dereferences it directly as `otherBcu.MainWindowHandle` 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 `otherBcu` truly cannot be null here, the `?.` is misleading. Settle it one way — test `otherBcu` 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 source/BulkCrapUninstaller/Functions/ApplicationList/ListViewDelegates.cs:28 — This method contradicts itself about `result`: line 27 assigns it with `as bool?`, which hands back null rather than throwing when the value is not a `bool?`, but line 28 then dereferences it directly as `result.ToYesNo` 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 `result` once before the first use and handle the null case, or cast with `(bool?)` so the failure is reported where it happens — rather than leaving the two readings side by side.
  • Symbol treated as nullable, then dereferenced unguarded REDACTED:202 — This method contradicts itself about `subKey`: line 193 writes `subKey?.GetStringSafe`, which says `subKey` can be null, but line 202 then dereferences it directly as `subKey.SetValue` 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 `subKey` truly cannot be null here, the `?.` is misleading. Settle it one way — test `subKey` 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 source/UninstallTools/Factory/DirectoryFactory.cs:111 — This method contradicts itself about `x`: line 115 writes `x?.Name`, which says `x` can be null, but line 111 then dereferences it directly as `x.GetDirectories` 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 `x` truly cannot be null here, the `?.` is misleading. Settle it one way — test `x` 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 source/UninstallTools/Junk/Finders/Registry/ComScanner.cs:253 — This method contradicts itself about `guidKey`: line 246 writes `guidKey?.`, which says `guidKey` can be null, but line 253 then dereferences it directly as `guidKey.OpenSubKey` 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 `guidKey` truly cannot be null here, the `?.` is misleading. Settle it one way — test `guidKey` 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 source/UninstallTools/Junk/Finders/Registry/EventLogScanner.cs:43 — This method contradicts itself about `subkey`: line 40 writes `subkey?.GetStringSafe`, which says `subkey` can be null, but line 43 then dereferences it directly as `subkey.Name` 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 `subkey` truly cannot be null here, the `?.` is misleading. Settle it one way — test `subkey` 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 source/UninstallTools/Startup/Browser/BrowserEntryFactory.cs:77 — This method contradicts itself about `classKey`: line 72 writes `classKey?.GetStringSafe`, which says `classKey` can be null, but line 77 then dereferences it directly as `classKey.OpenSubKey` 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 `classKey` truly cannot be null here, the `?.` is misleading. Settle it one way — test `classKey` 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 source/NBug_custom/Settings.cs:953 — This method contradicts itself about `defaultSetting`: line 947 assigns it with `as DefaultSettingValueAttribute`, which hands back null rather than throwing when the value is not a `DefaultSettingValueAttribute`, but line 953 then dereferences it directly as `defaultSetting.Value` 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 `defaultSetting` once before the first use and handle the null case, or cast with `(DefaultSettingValueAttribute)` so the failure is reported where it happens — rather than leaving the two readings side by side.
X1 · Async correctness · Sync-over-async (deadlock risk) through `.Result` · ×7
  • Sync-over-async (deadlock risk) through `.Result` source/BulkCrapUninstaller/Functions/Ratings/UninstallerRatingManager.cs:37 — Reading `.Result` of a task that has not completed blocks this thread until it does — the same block as `.Wait()`: under a synchronization context (Blazor, a UI thread, classic ASP.NET) it deadlocks, and on the thread pool it parks a thread for as long as the work runs. `await` the task instead (make the caller `async`); where a synchronous entry point must stay, keep the block in ONE documented bridge with a timeout.
  • Sync-over-async (deadlock risk) through `.Result` source/BulkCrapUninstaller/Functions/Ratings/UninstallerRatingManager.cs:41 — Reading `.Result` of a task that has not completed blocks this thread until it does — the same block as `.Wait()`: under a synchronization context (Blazor, a UI thread, classic ASP.NET) it deadlocks, and on the thread pool it parks a thread for as long as the work runs. `await` the task instead (make the caller `async`); where a synchronous entry point must stay, keep the block in ONE documented bridge with a timeout.
  • Sync-over-async (deadlock risk) through `.Result` source/BulkCrapUninstaller/Functions/Ratings/UninstallerRatingManager.cs:67 — Reading `.Result` of a task that has not completed blocks this thread until it does — the same block as `.Wait()`: under a synchronization context (Blazor, a UI thread, classic ASP.NET) it deadlocks, and on the thread pool it parks a thread for as long as the work runs. `await` the task instead (make the caller `async`); where a synchronous entry point must stay, keep the block in ONE documented bridge with a timeout.
  • Sync-over-async (deadlock risk) through `.Result` source/BulkCrapUninstaller/Functions/Tools/UpdateGrabber.cs:176 — Reading `.Result` of a task that has not completed blocks this thread until it does — the same block as `.Wait()`: under a synchronization context (Blazor, a UI thread, classic ASP.NET) it deadlocks, and on the thread pool it parks a thread for as long as the work runs. `await` the task instead (make the caller `async`); where a synchronous entry point must stay, keep the block in ONE documented bridge with a timeout.
  • Sync-over-async (deadlock risk) through `.Result` source/BulkCrapUninstaller/Functions/Tracking/DatabaseStatSender.cs:27 — Reading `.Result` of a task that has not completed blocks this thread until it does — the same block as `.Wait()`: under a synchronization context (Blazor, a UI thread, classic ASP.NET) it deadlocks, and on the thread pool it parks a thread for as long as the work runs. `await` the task instead (make the caller `async`); where a synchronous entry point must stay, keep the block in ONE documented bridge with a timeout.
  • Sync-over-async (deadlock risk) through `.Result` source/BulkCrapUninstaller/NBugConfigurator.cs:69 — Reading `.Result` of a task that has not completed blocks this thread until it does — the same block as `.Wait()`: under a synchronization context (Blazor, a UI thread, classic ASP.NET) it deadlocks, and on the thread pool it parks a thread for as long as the work runs. `await` the task instead (make the caller `async`); where a synchronous entry point must stay, keep the block in ONE documented bridge with a timeout.
  • Sync-over-async (deadlock risk) through `.Result` REDACTED:85 — Reading `.Result` of a task that has not completed blocks this thread until it does — the same block as `.Wait()`: under a synchronization context (Blazor, a UI thread, classic ASP.NET) it deadlocks, and on the thread pool it parks a thread for as long as the work runs. `await` the task instead (make the caller `async`); where a synchronous entry point must stay, keep the block in ONE documented bridge with a timeout.
X18 · Disposal-pattern correctness · Owned disposable field is never released · ×7
  • Owned disposable field is never released REDACTED:52 — `MainWindow` implements `IDisposable` — so it has told every caller it holds something worth releasing — and it constructs `_uninstallerListConfigurator` itself (line 52), which makes that instance its own. But `_uninstallerListConfigurator` is named in none of the methods the disposal search covered: `Dispose` (line 443) — that is `Dispose` plus every method `Dispose` calls BY NAME, so a release reached through an interface, a delegate or a base class is not followed and is worth checking before acting. On what was read, the type's disposal releases everything except the one thing it owns. A disposable the owner never disposes is held until finalization if its type has a finalizer, and forever if it does not — which for a synchronisation primitive, a timer, a stream or a handle means the resource accumulates once per instance for the life of the process. Release it in `Dispose` (`_uninstallerListConfigurator?.Dispose();`), or, if it truly does not need releasing, drop `IDisposable` from the type so the claim and the behaviour agree.
  • Owned disposable field is never released REDACTED:54 — `MainWindow` implements `IDisposable` — so it has told every caller it holds something worth releasing — and it constructs `_listLegendWindow` itself (line 54), which makes that instance its own. But `_listLegendWindow` is named in none of the methods the disposal search covered: `Dispose` (line 443) — that is `Dispose` plus every method `Dispose` calls BY NAME, so a release reached through an interface, a delegate or a base class is not followed and is worth checking before acting. On what was read, the type's disposal releases everything except the one thing it owns. A disposable the owner never disposes is held until finalization if its type has a finalizer, and forever if it does not — which for a synchronisation primitive, a timer, a stream or a handle means the resource accumulates once per instance for the life of the process. Release it in `Dispose` (`_listLegendWindow?.Dispose();`), or, if it truly does not need releasing, drop `IDisposable` from the type so the claim and the behaviour agree.
  • Owned disposable field is never released REDACTED:55 — `MainWindow` implements `IDisposable` — so it has told every caller it holds something worth releasing — and it constructs `_debugWindow` itself (line 55), which makes that instance its own. But `_debugWindow` is named in none of the methods the disposal search covered: `Dispose` (line 443) — that is `Dispose` plus every method `Dispose` calls BY NAME, so a release reached through an interface, a delegate or a base class is not followed and is worth checking before acting. On what was read, the type's disposal releases everything except the one thing it owns. A disposable the owner never disposes is held until finalization if its type has a finalizer, and forever if it does not — which for a synchronisation primitive, a timer, a stream or a handle means the resource accumulates once per instance for the life of the process. Release it in `Dispose` (`_debugWindow?.Dispose();`), or, if it truly does not need releasing, drop `IDisposable` from the type so the claim and the behaviour agree.
  • Owned disposable field is never released REDACTED:73 — `MainWindow` implements `IDisposable` — so it has told every caller it holds something worth releasing — and it constructs `_uninstallerListPostProcesser` itself (line 73), which makes that instance its own. But `_uninstallerListPostProcesser` is named in none of the methods the disposal search covered: `Dispose` (line 443) — that is `Dispose` plus every method `Dispose` calls BY NAME, so a release reached through an interface, a delegate or a base class is not followed and is worth checking before acting. On what was read, the type's disposal releases everything except the one thing it owns. A disposable the owner never disposes is held until finalization if its type has a finalizer, and forever if it does not — which for a synchronisation primitive, a timer, a stream or a handle means the resource accumulates once per instance for the life of the process. Release it in `Dispose` (`_uninstallerListPostProcesser?.Dispose();`), or, if it truly does not need releasing, drop `IDisposable` from the type so the claim and the behaviour agree.
  • Owned disposable field is never released source/UninstallTools/Uninstaller/BulkUninstallTask.cs:265 — `BulkUninstallTask` implements `IDisposable` — so it has told every caller it holds something worth releasing — and it constructs `_client` itself (line 265), which makes that instance its own. But `_client` is named in none of the methods the disposal search covered: `Dispose` (line 75) — that is `Dispose` plus every method `Dispose` calls BY NAME, so a release reached through an interface, a delegate or a base class is not followed and is worth checking before acting. On what was read, the type's disposal releases everything except the one thing it owns. A disposable the owner never disposes is held until finalization if its type has a finalizer, and forever if it does not — which for a synchronisation primitive, a timer, a stream or a handle means the resource accumulates once per instance for the life of the process. Release it in `Dispose` (`_client?.Dispose();`), or, if it truly does not need releasing, drop `IDisposable` from the type so the claim and the behaviour agree.
  • Owned disposable field is never released source/UninstallTools/Uninstaller/BulkUninstallTask.cs:266 — `BulkUninstallTask` implements `IDisposable` — so it has told every caller it holds something worth releasing — and it constructs `_writer` itself (line 266), which makes that instance its own. But `_writer` is named in none of the methods the disposal search covered: `Dispose` (line 75) — that is `Dispose` plus every method `Dispose` calls BY NAME, so a release reached through an interface, a delegate or a base class is not followed and is worth checking before acting. On what was read, the type's disposal releases everything except the one thing it owns. A disposable the owner never disposes is held until finalization if its type has a finalizer, and forever if it does not — which for a synchronisation primitive, a timer, a stream or a handle means the resource accumulates once per instance for the life of the process. Release it in `Dispose` (`_writer?.Dispose();`), or, if it truly does not need releasing, drop `IDisposable` from the type so the claim and the behaviour agree.
  • Owned disposable field is never released source/ObjectListView/Rendering/Renderers.cs:2732 — `ImageRenderer` implements `IDisposable` — so it has told every caller it holds something worth releasing — and it constructs `tickler` itself (line 2732), which makes that instance its own. But `tickler` is named in none of the methods the disposal search covered: `Dispose` (line 2391) — that is `Dispose` plus every method `Dispose` calls BY NAME, so a release reached through an interface, a delegate or a base class is not followed and is worth checking before acting. On what was read, the type's disposal releases everything except the one thing it owns. A disposable the owner never disposes is held until finalization if its type has a finalizer, and forever if it does not — which for a synchronisation primitive, a timer, a stream or a handle means the resource accumulates once per instance for the life of the process. Release it in `Dispose` (`tickler?.Dispose();`), or, if it truly does not need releasing, drop `IDisposable` from the type so the claim and the behaviour agree.
X3 · Exception handling · Swallowed exception (caught, then discarded) · ×7
  • Swallowed exception (caught, then discarded) source/BulkCrapUninstaller/CultureConfigurator.cs:196 — `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) source/BulkCrapUninstaller/Forms/Windows/UninstallProgressWindow.cs:269 — `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) source/BulkCrapUninstaller/Functions/ApplicationList/ListViewDelegates.cs:137 — `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) REDACTED:206 — `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) source/UninstallTools/Factory/DirectoryFactory.cs:207 — `catch (IOException)` 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) source/UninstallTools/Factory/DirectoryFactory.cs:211 — `catch (UnauthorizedAccessException)` 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) source/UninstallTools/Factory/FactoryTools.cs:78 — `catch (ArgumentException)` 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.
GD1 · Unfinished & placeholder code · Unfinished stub · ×6
  • Unfinished stub — throws NotImplementedException source/UninstallTools/Factory/InfoAdders/InfoAdderManager.cs:141 — A shipped member still throws NotImplementedException — generated scaffolding that was never completed. Implement it or remove the dead surface.
  • Unfinished stub — throws NotImplementedException source/UninstallTools/Factory/Json/DynamicStringArrayConverter.cs:84 — A shipped member still throws NotImplementedException — generated scaffolding that was never completed. Implement it or remove the dead surface.
  • Unfinished stub — throws NotImplementedException source/UninstallTools/Factory/Json/PowerShellDateTimeOffsetConverter.cs:46 — A shipped member still throws NotImplementedException — generated scaffolding that was never completed. Implement it or remove the dead surface.
  • Unfinished stub — throws NotImplementedException source/UninstallerAutomatizer/Automation/UninstallHandler.cs:34 — A shipped member still throws NotImplementedException — generated scaffolding that was never completed. Implement it or remove the dead surface.
  • Unfinished stub — throws NotImplementedException source/UninstallerAutomatizer/Automation/UninstallHandler.cs:39 — A shipped member still throws NotImplementedException — generated scaffolding that was never completed. Implement it or remove the dead surface.
  • Unfinished stub — throws NotImplementedException source/ObjectListView/TreeListView.cs:1641 — A shipped member still throws NotImplementedException — generated scaffolding that was never completed. Implement it or remove the dead surface.
D6 · Cohesion (LCOM4) · Low cohesion · ×4
  • Low cohesion: MainWindow (LCOM4 15) REDACTED:41 — MainWindow's methods fall into 15 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 15 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: JunkRemoveWindow (LCOM4 7) source/BulkCrapUninstaller/Forms/Windows/JunkRemoveWindow.cs:27 — JunkRemoveWindow's methods fall into 7 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 7 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: ApplicationUninstallerEntry (LCOM4 4) source/UninstallTools/ApplicationUninstallerEntry.cs:27 — ApplicationUninstallerEntry'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: MainWindow (LCOM4 4) source/UninstallerAutomatizer/Forms/MainWindow.cs:15 — MainWindow'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.
IC1 · Incompleteness & stubs · Unfinished stub · ×4
  • Unfinished stub — throws NotImplementedException source/ObjectListView/TreeListView.cs:1641 — `InsertObjects` is a shipped member whose whole body throws NotImplementedException — scaffolding that was never completed. Implement it or remove the dead surface.
  • Unfinished stub — throws NotImplementedException source/UninstallTools/Factory/InfoAdders/InfoAdderManager.cs:141 — `TryAddFieldInformation` is a shipped member whose whole body throws NotImplementedException — scaffolding that was never completed. Implement it or remove the dead surface.
  • Unfinished stub — throws NotImplementedException source/UninstallTools/Factory/Json/DynamicStringArrayConverter.cs:84 — `Write` is a shipped member whose whole body throws NotImplementedException — scaffolding that was never completed. Implement it or remove the dead surface.
  • Unfinished stub — throws NotImplementedException source/UninstallTools/Factory/Json/PowerShellDateTimeOffsetConverter.cs:46 — `Write` is a shipped member whose whole body throws NotImplementedException — scaffolding that was never completed. Implement it or remove the dead surface.
D17 · Explicit Debt · BareSuppressMessage · ×3
  • BareSuppressMessage source/BulkCrapUninstaller/Functions/ApplicationList/UninstallerListConfigurator.cs:66 — System.Diagnostics.CodeAnalysis.SuppressMessage — the suppression records no reason: either it carries no justification argument at all, or one that states nothing a reader can weigh ("OK", "By design"). 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. Write what makes this site legitimately different — the invariant that holds, the framework contract that forces the shape — or remove the suppression and fix what it hides.
  • BareSuppressMessage source/KlocTools/Forms/LoadingDialogInterface.cs:10 — System.Diagnostics.CodeAnalysis.SuppressMessage — the suppression records no reason: either it carries no justification argument at all, or one that states nothing a reader can weigh ("OK", "By design"). 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. Write what makes this site legitimately different — the invariant that holds, the framework contract that forces the shape — or remove the suppression and fix what it hides.
  • BareSuppressMessage source/KlocTools/Forms/SplashScreen.cs:27 — System.Diagnostics.CodeAnalysis.SuppressMessage — the suppression records no reason: either it carries no justification argument at all, or one that states nothing a reader can weigh ("OK", "By design"). 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. Write what makes this site legitimately different — the invariant that holds, the framework contract that forces the shape — or remove the suppression and fix what it hides.
X20 · Mistyped argument guard · Argument guard throws the exception its own condition disproves · ×3
  • Argument guard throws the exception its own condition disproves source/BulkCrapUninstaller/Functions/Ratings/UninstallerRatingManager.cs:78 — The guard on line 77 rejects `appKey` and line 78 reports that rejection as `ArgumentNullException` — but the condition's own test `string.IsNullOrEmpty(appKey)` is true of a value that is NOT null: it is satisfied by an EMPTY `appKey`, and on that path `appKey` was already proven non-null by the very expression that decided it (`||` short-circuits, so the null test to its left had to be false to get here). So a caller who passes a valid empty argument is told a parameter was null. That is not a wording problem: the exception type is the contract. A caller catching `ArgumentNullException` to handle a real null swallows the empty case with it, and whoever reads the stack trace later is told a failure the source disproves. .NET separates the two on purpose — `ArgumentNullException.ThrowIfNull` and `ArgumentException.ThrowIfNullOrEmpty` are two helpers because they are two failures. Throw `ArgumentException` for the empty case, or split the guard and throw each on its own condition.
  • Argument guard throws the exception its own condition disproves source/ObjectListView/Filtering/FlagClusteringStrategy.cs:97 — The guard on line 97 rejects `flags` and line 97 reports that rejection as `ArgumentNullException` — but the condition's own test `flags.Length == 0` is true of a value that is NOT null: it is satisfied by an EMPTY `flags`, and on that path `flags` was already proven non-null by the very expression that decided it (`||` short-circuits, so the null test to its left had to be false to get here). So a caller who passes a valid empty argument is told a parameter was null. That is not a wording problem: the exception type is the contract. A caller catching `ArgumentNullException` to handle a real null swallows the empty case with it, and whoever reads the stack trace later is told a failure the source disproves. .NET separates the two on purpose — `ArgumentNullException.ThrowIfNull` and `ArgumentException.ThrowIfNullOrEmpty` are two helpers because they are two failures. Throw `ArgumentException` for the empty case, or split the guard and throw each on its own condition.
  • Argument guard throws the exception its own condition disproves source/ObjectListView/Filtering/FlagClusteringStrategy.cs:98 — The guard on line 98 rejects `flagLabels` and line 98 reports that rejection as `ArgumentNullException` — but the condition's own test `flagLabels.Length == 0` is true of a value that is NOT null: it is satisfied by an EMPTY `flagLabels`, and on that path `flagLabels` was already proven non-null by the very expression that decided it (`||` short-circuits, so the null test to its left had to be false to get here). So a caller who passes a valid empty argument is told a parameter was null. That is not a wording problem: the exception type is the contract. A caller catching `ArgumentNullException` to handle a real null swallows the empty case with it, and whoever reads the stack trace later is told a failure the source disproves. .NET separates the two on purpose — `ArgumentNullException.ThrowIfNull` and `ArgumentException.ThrowIfNullOrEmpty` are two helpers because they are two failures. Throw `ArgumentException` for the empty case, or split the guard and throw each on its own condition.
D17 · Explicit Debt · BarePragmaDisable · ×2
  • BarePragmaDisable source/BulkCrapUninstaller/Functions/Tools/LocalizedX509Certificate.cs:49 — #pragma warning disable SYSLIB0027 — 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 source/BulkCrapUninstaller/Functions/Tools/LocalizedX509Certificate.cs:50 — #pragma warning disable SYSLIB0028 — 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.
D29 · Static Analysis (SAST) · REDACTED
  • REDACTED
  • REDACTED
D29 · Static Analysis (SAST) · REDACTED
  • REDACTED
  • REDACTED
D3 · God Classes · TooManyMethods · ×2
  • TooManyMethods: MainWindow REDACTED — TooManyMethods — 1013 significant lines (blank, comment-only and punctuation-only lines excluded), 131 methods. The bar is 30 methods; this is 101 over it, 4.37× 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: MessageBoxes source/BulkCrapUninstaller/Functions/MessageBoxes.cs — TooManyMethods — 430 significant lines (blank, comment-only and punctuation-only lines excluded), 53 methods. The bar is 30 methods; this is 23 over it, 1.77× the bar. 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.
D3 · God Classes · MethodTooLong · ×2
  • MethodTooLong: Tweaks.Tweaks(…) source/ScriptHelper/Tweaks.cs:36 — MethodTooLong — Tweaks(…) runs 127 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 27 over it, 1.27× 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: BulkUninstallEntry.UninstallThread source/UninstallTools/Uninstaller/BulkUninstallEntry.cs:283 — MethodTooLong — UninstallThread runs 108 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 8 over it, 1.08× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
D4 · Code Duplication · Duplicated block (11 lines × 2) · ×2
  • Duplicated block (11 lines × 2) REDACTED:733 — REDACTED:733-743 | REDACTED:1096-1106 — 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) source/KlocTools/Tools/Sift4.cs:77 — source/KlocTools/Tools/Sift4.cs:77-87 | source/KlocTools/Tools/Sift4.cs:185-195 — 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 `source/KlocTools/Tools/Sift4.cs:77` 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 (9 lines × 2) · ×2
  • Duplicated block (9 lines × 2) source/BulkCrapUninstaller/Forms/Windows/UninstallProgressWindow.cs:340 — source/BulkCrapUninstaller/Forms/Windows/UninstallProgressWindow.cs:340-348 | source/BulkCrapUninstaller/Forms/Windows/UninstallProgressWindow.cs:399-407 — 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 (9 lines × 2) source/KlocTools/Controls/FacebookButton.cs:36 — source/KlocTools/Controls/FacebookButton.cs:36-44 | source/KlocTools/Controls/FacebookStatusButton.cs:30-38 — 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.
S1 · Cryptographic Hygiene · Password key derivation is priced too cheaply · ×2
  • Password key derivation is priced too cheaply source/NBug_custom/Settings.cs:887 — This code fixes PBKDF2-SHA-1 at 3 iterations. A key-derivation function's only defence is the cost of ONE guess, and that cost is this number — the algorithm choice does not set it. Current OWASP guidance is 1,300,000 PBKDF2 iterations with HMAC-SHA1, 600,000 with SHA-256 and 210,000 with SHA-512; scrypt at N=2^17, r=8, p=1 (or an equivalent N·r·p product); Argon2id at 19 MiB of memory and 2 iterations (or an equivalent row); bcrypt at a work factor of at least 10. This figure divides the attacker's work by a factor of tens or hundreds against the same stolen hash, on hardware they already own. Where what is derived is short or low-entropy — a PIN, a numeric parental code, a four-character token — the whole keyspace falls in the time this parameter buys, and no salt or constant-time comparison changes that. Raise the count to the current published figure for the PRF you use, measure it on the slowest hardware that must run it (a target of roughly 100 ms per derivation is the usual budget), and read the value from configuration so a deployment can raise it again without a rebuild. Where the derived value must interoperate with a format someone else fixed, the count cannot move — derive a SEPARATE value for anything you own rather than inheriting the external format's price.
  • Password key derivation is priced too cheaply source/NBug_custom/Settings.cs:923 — This code fixes PBKDF2-SHA-1 at 3 iterations. A key-derivation function's only defence is the cost of ONE guess, and that cost is this number — the algorithm choice does not set it. Current OWASP guidance is 1,300,000 PBKDF2 iterations with HMAC-SHA1, 600,000 with SHA-256 and 210,000 with SHA-512; scrypt at N=2^17, r=8, p=1 (or an equivalent N·r·p product); Argon2id at 19 MiB of memory and 2 iterations (or an equivalent row); bcrypt at a work factor of at least 10. This figure divides the attacker's work by a factor of tens or hundreds against the same stolen hash, on hardware they already own. Where what is derived is short or low-entropy — a PIN, a numeric parental code, a four-character token — the whole keyspace falls in the time this parameter buys, and no salt or constant-time comparison changes that. Raise the count to the current published figure for the PRF you use, measure it on the slowest hardware that must run it (a target of roughly 100 ms per derivation is the usual budget), and read the value from configuration so a deployment can raise it again without a rebuild. Where the derived value must interoperate with a format someone else fixed, the count cannot move — derive a SEPARATE value for anything you own rather than inheriting the external format's price.
X18 · Disposal-pattern correctness · Finalizer on a type that owns no unmanaged resource · ×2
  • Finalizer on a type that owns no unmanaged resource source/ObjectListView/Implementation/DataSourceAdapter.cs:64 — `DataSourceAdapter` declares a finalizer (line 64), but nothing in the type is unmanaged: no `IntPtr`/`UIntPtr` or pointer field, no `SafeHandle`, no `HandleRef`, no `extern`/`DllImport` member and no `Marshal`/`GCHandle`/`NativeMemory` use. A finalizer can only release what the garbage collector cannot, so on a purely-managed type it releases nothing and costs something: every instance is put on the finalizer queue, survives at least one extra collection, and is then finalized on a thread that is NOT the disposing one — where the managed objects it touches may already have been finalized themselves. Delete the finalizer (and the `GC.SuppressFinalize` that exists to defuse it); if a handle is added later, wrap it in a `SafeHandle`, which brings its own correct finalization.
  • Finalizer on a type that owns no unmanaged resource source/NBug_custom/Core/Util/Storage/Storer.cs:36 — `Storer` declares a finalizer (line 36), but nothing in the type is unmanaged: no `IntPtr`/`UIntPtr` or pointer field, no `SafeHandle`, no `HandleRef`, no `extern`/`DllImport` member and no `Marshal`/`GCHandle`/`NativeMemory` use. A finalizer can only release what the garbage collector cannot, so on a purely-managed type it releases nothing and costs something: every instance is put on the finalizer queue, survives at least one extra collection, and is then finalized on a thread that is NOT the disposing one — where the managed objects it touches may already have been finalized themselves. Delete the finalizer (and the `GC.SuppressFinalize` that exists to defuse it); if a handle is added later, wrap it in a `SafeHandle`, which brings its own correct finalization.
D1 · Cyclomatic Complexity · BulkUninstallEntry.UninstallThread (cyclomatic 51) · ×1
  • BulkUninstallEntry.UninstallThread (cyclomatic 51) source/UninstallTools/Uninstaller/BulkUninstallEntry.cs:283 — BulkUninstallEntry.UninstallThread has cyclomatic complexity 51 (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 · Sift4.CommonDistance (cyclomatic 27) · ×1
  • Sift4.CommonDistance (cyclomatic 27) source/KlocTools/Tools/Sift4.cs:165 — Sift4.CommonDistance has cyclomatic complexity 27 (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 · ApplicationEntryTools.AreEntriesRelated (cyclomatic 25) · ×1
  • ApplicationEntryTools.AreEntriesRelated (cyclomatic 25) source/UninstallTools/Factory/ApplicationEntryTools.cs:32 — ApplicationEntryTools.AreEntriesRelated has cyclomatic complexity 25 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
D1 · Cyclomatic Complexity · ProcessTools.SeparateArgsFromCommand (cyclomatic 25) · ×1
  • ProcessTools.SeparateArgsFromCommand (cyclomatic 25) source/KlocTools/Tools/ProcessTools.cs:135 — ProcessTools.SeparateArgsFromCommand has cyclomatic complexity 25 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · Sift4.GeneralDistance (cyclomatic 25) · ×1
  • Sift4.GeneralDistance (cyclomatic 25) source/KlocTools/Tools/Sift4.cs:54 — Sift4.GeneralDistance has cyclomatic complexity 25 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · Program.ProcessCommandlineArguments (cyclomatic 25) · ×1
  • Program.ProcessCommandlineArguments (cyclomatic 25) source/SteamHelper/Program.cs:109 — Program.ProcessCommandlineArguments has cyclomatic complexity 25 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · Program.RunUninstall (cyclomatic 24) · ×1
  • Program.RunUninstall (cyclomatic 24) source/BCU-console/Program.cs:291 — Program.RunUninstall has cyclomatic complexity 24 (threshold 15). Of this number, 20 points are the body's own statements and 4 belong to 3 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 · ComScanner.FindJunk (cyclomatic 23) · ×1
  • ComScanner.FindJunk (cyclomatic 23) source/UninstallTools/Junk/Finders/Registry/ComScanner.cs:34 — ComScanner.FindJunk has cyclomatic complexity 23 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · UninstallerListConfigurator.ListViewFilter (cyclomatic 21) · ×1
  • UninstallerListConfigurator.ListViewFilter (cyclomatic 21) source/BulkCrapUninstaller/Functions/ApplicationList/UninstallerListConfigurator.cs:121 — UninstallerListConfigurator.ListViewFilter has cyclomatic complexity 21 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
D1 · Cyclomatic Complexity · AppUninstaller.RunUninstall (cyclomatic 21) · ×1
  • AppUninstaller.RunUninstall (cyclomatic 21) source/BulkCrapUninstaller/Functions/AppUninstaller.cs:179 — AppUninstaller.RunUninstall 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 · ProgramFilesOrphans.FindJunkRecursively (cyclomatic 21) · ×1
  • ProgramFilesOrphans.FindJunkRecursively (cyclomatic 21) source/UninstallTools/Junk/ProgramFilesOrphans.cs:42 — ProgramFilesOrphans.FindJunkRecursively 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 · MainWindow.UpdateUninstallListContextMenuStrip (cyclomatic 20) · ×1
  • MainWindow.UpdateUninstallListContextMenuStrip (cyclomatic 20) REDACTED:1305 — MainWindow.UpdateUninstallListContextMenuStrip 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 · OldStartupDisable.AddDisableInfo (cyclomatic 20) · ×1
  • OldStartupDisable.AddDisableInfo (cyclomatic 20) source/UninstallTools/Startup/Normal/OldStartupDisable.cs:50 — OldStartupDisable.AddDisableInfo 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 · UninstallManager.RunUninstaller (cyclomatic 20) · ×1
  • UninstallManager.RunUninstaller (cyclomatic 20) source/UninstallTools/Uninstaller/UninstallManager.cs:70 — UninstallManager.RunUninstaller has cyclomatic complexity 20 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
D1 · Cyclomatic Complexity · RegistryTools.GetKeyRoot (cyclomatic 20) · ×1
  • RegistryTools.GetKeyRoot (cyclomatic 20) REDACTED:284 — RegistryTools.GetKeyRoot 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 · UninstallerTypeAdder.GetUninstallerType (cyclomatic 19) · ×1
  • UninstallerTypeAdder.GetUninstallerType (cyclomatic 19) source/UninstallTools/Factory/InfoAdders/UninstallerTypeAdder.cs:55 — UninstallerTypeAdder.GetUninstallerType has cyclomatic complexity 19 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · WindowsUpdateFactory.GetUninstallerEntries (cyclomatic 19) · ×1
  • WindowsUpdateFactory.GetUninstallerEntries (cyclomatic 19) source/UninstallTools/Factory/WindowsUpdateFactory.cs:22 — WindowsUpdateFactory.GetUninstallerEntries has cyclomatic complexity 19 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · BulkUninstallTask.UninstallWorkerThread (cyclomatic 18) · ×1
  • BulkUninstallTask.UninstallWorkerThread (cyclomatic 18) source/UninstallTools/Uninstaller/BulkUninstallTask.cs:133 — BulkUninstallTask.UninstallWorkerThread has cyclomatic complexity 18 (threshold 15). Of this number, 12 points are the body's own statements and 6 belong to 2 function literals inside it that branch. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top. This is NOT this file's highest cyclomatic complexity: BulkUninstallTask.CheckForTypeCollisions (cyclomatic 20) is higher and carries no row of its own — it was excluded as a flat dispatcher (a long switch/match over independent cases: many branches, almost no nesting), which this dimension does not treat as a refactor obligation. It is named here so the ranking you see in this file is not mistaken for the whole of it; the excluded method is counted neither in this dimension's figures nor in its score.
D1 · Cyclomatic Complexity · AppUninstaller.UninstallFromDirectory (cyclomatic 17) · ×1
  • AppUninstaller.UninstallFromDirectory (cyclomatic 17) source/BulkCrapUninstaller/Functions/AppUninstaller.cs:527 — AppUninstaller.UninstallFromDirectory 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 · InfoAdderManager.CopyMissingInformation (cyclomatic 17) · ×1
  • InfoAdderManager.CopyMissingInformation (cyclomatic 17) source/UninstallTools/Factory/InfoAdders/InfoAdderManager.cs:159 — InfoAdderManager.CopyMissingInformation has cyclomatic complexity 17 (threshold 15). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
D1 · Cyclomatic Complexity · ScoopFactory.CreateUninstallerEntry (cyclomatic 17) · ×1
  • ScoopFactory.CreateUninstallerEntry (cyclomatic 17) REDACTED:288 — ScoopFactory.CreateUninstallerEntry has cyclomatic complexity 17 (threshold 15). Of this number, 16 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 · MsiTools.GetInstalledComponentPaths (cyclomatic 17) · ×1
  • MsiTools.GetInstalledComponentPaths (cyclomatic 17) source/KlocTools/IO/MsiTools.cs:137 — MsiTools.GetInstalledComponentPaths 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 · Sift4.SimplestDistance (cyclomatic 16) · ×1
  • Sift4.SimplestDistance (cyclomatic 16) source/KlocTools/Tools/Sift4.cs:272 — Sift4.SimplestDistance has cyclomatic complexity 16 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D17 · Explicit Debt · DeadPreprocessorBranch · ×1
  • DeadPreprocessorBranch source/KlocTools/IO/MsiTools.cs:164 — #if RELEASE — no definition of that symbol was found anywhere this analysis looks: not in a <DefineConstants> in any project file, props or targets under any condition, not on a build script's command line, not in a #define, and not in a project-template manifest; nor is it one the compiler or SDK defines itself. On that evidence the condition is decided the same way in every configuration this repository can build, and the code on the dead side of it never compiles — including the part a reader will assume is what ships. Either define the symbol in the configuration that is supposed to have it, or delete the branch and keep the behaviour you are actually shipping. If some other mechanism binds it, that mechanism is outside the list above and this row is a gap in what we read, not a fact about your code.
D2 · Cognitive Complexity · BulkUninstallEntry.UninstallThread (cognitive 81) · ×1
  • BulkUninstallEntry.UninstallThread (cognitive 81) source/UninstallTools/Uninstaller/BulkUninstallEntry.cs:283 — BulkUninstallEntry.UninstallThread has cognitive complexity 81 (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 · ComScanner.FindJunk (cognitive 75) · ×1
  • ComScanner.FindJunk (cognitive 75) source/UninstallTools/Junk/Finders/Registry/ComScanner.cs:34 — ComScanner.FindJunk has cognitive complexity 75 (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 · Sift4.CommonDistance (cognitive 60) · ×1
  • Sift4.CommonDistance (cognitive 60) source/KlocTools/Tools/Sift4.cs:165 — Sift4.CommonDistance has cognitive complexity 60 (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 · Sift4.GeneralDistance (cognitive 58) · ×1
  • Sift4.GeneralDistance (cognitive 58) source/KlocTools/Tools/Sift4.cs:54 — Sift4.GeneralDistance has cognitive complexity 58 (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 · ProcessTools.SeparateArgsFromCommand (cognitive 50) · ×1
  • ProcessTools.SeparateArgsFromCommand (cognitive 50) source/KlocTools/Tools/ProcessTools.cs:135 — ProcessTools.SeparateArgsFromCommand has cognitive complexity 50 (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 · AppUninstaller.UninstallFromDirectory (cognitive 38) · ×1
  • AppUninstaller.UninstallFromDirectory (cognitive 38) source/BulkCrapUninstaller/Functions/AppUninstaller.cs:527 — AppUninstaller.UninstallFromDirectory 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 · Program.RunUninstall (cognitive 37) · ×1
  • Program.RunUninstall (cognitive 37) source/BCU-console/Program.cs:291 — Program.RunUninstall has cognitive complexity 37 (threshold 15). Of this number, 32 points are the body's own statements and 5 belong to 3 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 · MainWindow.UpdateUninstallListContextMenuStrip (cognitive 36) · ×1
  • MainWindow.UpdateUninstallListContextMenuStrip (cognitive 36) REDACTED:1305 — MainWindow.UpdateUninstallListContextMenuStrip has cognitive complexity 36 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · ProgramFilesOrphans.FindJunkRecursively (cognitive 36) · ×1
  • ProgramFilesOrphans.FindJunkRecursively (cognitive 36) source/UninstallTools/Junk/ProgramFilesOrphans.cs:42 — ProgramFilesOrphans.FindJunkRecursively has cognitive complexity 36 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · ScoopFactory.CreateUninstallerEntry (cognitive 34) · ×1
  • ScoopFactory.CreateUninstallerEntry (cognitive 34) REDACTED:288 — ScoopFactory.CreateUninstallerEntry has cognitive complexity 34 (threshold 15). Of this number, 33 points are the body's own statements and 1 belongs to one function literal inside it that branches. To reduce it, 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 · JunkRemoveWindow.buttonAccept_Click (cognitive 32) · ×1
  • JunkRemoveWindow.buttonAccept_Click (cognitive 32) source/BulkCrapUninstaller/Forms/Windows/JunkRemoveWindow.cs:63 — JunkRemoveWindow.buttonAccept_Click has cognitive complexity 32 (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 · MsiInfoAdder.ApplyMsiInfo (cognitive 31) · ×1
  • MsiInfoAdder.ApplyMsiInfo (cognitive 31) source/UninstallTools/Factory/InfoAdders/MsiInfoAdder.cs:50 — MsiInfoAdder.ApplyMsiInfo has cognitive complexity 31 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · AppUninstaller.RunUninstall (cognitive 30) · ×1
  • AppUninstaller.RunUninstall (cognitive 30) source/BulkCrapUninstaller/Functions/AppUninstaller.cs:179 — AppUninstaller.RunUninstall has cognitive complexity 30 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · Program.ProcessCommandlineArguments (cognitive 30) · ×1
  • Program.ProcessCommandlineArguments (cognitive 30) source/SteamHelper/Program.cs:109 — Program.ProcessCommandlineArguments has cognitive complexity 30 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · FileTargeter.ProcessFiles (cognitive 29) · ×1
  • FileTargeter.ProcessFiles (cognitive 29) source/BulkCrapUninstaller/Controls/FileTargeter.cs:27 — FileTargeter.ProcessFiles has cognitive complexity 29 (threshold 15). Of this number, 27 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 · RegisteredApplicationsFinder.FindJunk (cognitive 29) · ×1
  • RegisteredApplicationsFinder.FindJunk (cognitive 29) source/UninstallTools/Junk/Finders/Registry/RegisteredApplicationsFinder.cs:85 — RegisteredApplicationsFinder.FindJunk has cognitive complexity 29 (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 · CommonDriveJunkScanner.FindJunkRecursively (cognitive 27) · ×1
  • CommonDriveJunkScanner.FindJunkRecursively (cognitive 27) source/UninstallTools/Junk/Finders/Drive/CommonDriveJunkScanner.cs:43 — CommonDriveJunkScanner.FindJunkRecursively has cognitive complexity 27 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · Sift4.SimplestDistance (cognitive 27) · ×1
  • Sift4.SimplestDistance (cognitive 27) source/KlocTools/Tools/Sift4.cs:272 — Sift4.SimplestDistance has cognitive complexity 27 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · ApplicationEntrySerializer.SanitizeForXmlExport (cognitive 26) · ×1
  • ApplicationEntrySerializer.SanitizeForXmlExport (cognitive 26) source/UninstallTools/ApplicationEntrySerializer.cs:128 — ApplicationEntrySerializer.SanitizeForXmlExport 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 · ChocolateyFactory.GetUninstallerEntries (cognitive 26) · ×1
  • ChocolateyFactory.GetUninstallerEntries (cognitive 26) source/UninstallTools/Factory/ChocolateyFactory.cs:38 — ChocolateyFactory.GetUninstallerEntries 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 · InfoAdderManager.AddMissingInformation (cognitive 26) · ×1
  • InfoAdderManager.AddMissingInformation (cognitive 26) source/UninstallTools/Factory/InfoAdders/InfoAdderManager.cs:76 — InfoAdderManager.AddMissingInformation has cognitive complexity 26 (threshold 15). Of this number, 25 points are the body's own statements and 1 belongs to one function literal inside it that branches. To reduce it, 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 · UninstallerTypeAdder.GetUninstallerType (cognitive 26) · ×1
  • UninstallerTypeAdder.GetUninstallerType (cognitive 26) source/UninstallTools/Factory/InfoAdders/UninstallerTypeAdder.cs:55 — UninstallerTypeAdder.GetUninstallerType 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 · WindowsUpdateFactory.GetUninstallerEntries (cognitive 26) · ×1
  • WindowsUpdateFactory.GetUninstallerEntries (cognitive 26) source/UninstallTools/Factory/WindowsUpdateFactory.cs:22 — WindowsUpdateFactory.GetUninstallerEntries 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 · OldStartupDisable.AddDisableInfo (cognitive 26) · ×1
  • OldStartupDisable.AddDisableInfo (cognitive 26) source/UninstallTools/Startup/Normal/OldStartupDisable.cs:50 — OldStartupDisable.AddDisableInfo 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 · UninstallHandler.DaemonThread (cognitive 26) · ×1
  • UninstallHandler.DaemonThread (cognitive 26) source/UninstallerAutomatizer/Automation/UninstallHandler.cs:116 — UninstallHandler.DaemonThread has cognitive complexity 26 (threshold 15). Of this number, 23 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 · UninstallManager.RunUninstaller (cognitive 25) · ×1
  • UninstallManager.RunUninstaller (cognitive 25) source/UninstallTools/Uninstaller/UninstallManager.cs:70 — UninstallManager.RunUninstaller has cognitive complexity 25 (threshold 15). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
D2 · Cognitive Complexity · ScoopFactory.GetUninstallerEntries (cognitive 23) · ×1
  • ScoopFactory.GetUninstallerEntries (cognitive 23) REDACTED:174 — ScoopFactory.GetUninstallerEntries has cognitive complexity 23 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · BulkUninstallTask.UninstallWorkerThread (cognitive 23) · ×1
  • BulkUninstallTask.UninstallWorkerThread (cognitive 23) source/UninstallTools/Uninstaller/BulkUninstallTask.cs:133 — BulkUninstallTask.UninstallWorkerThread has cognitive complexity 23 (threshold 15). Of this number, 14 points are the body's own statements and 9 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 · OculusManager.QueryOculusApps (cognitive 23) · ×1
  • OculusManager.QueryOculusApps (cognitive 23) source/OculusHelper/OculusManager.cs:78 — OculusManager.QueryOculusApps has cognitive complexity 23 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · RatingRenderer.Render (cognitive 22) · ×1
  • RatingRenderer.Render (cognitive 22) source/BulkCrapUninstaller/Functions/Ratings/RatingRenderer.cs:27 — RatingRenderer.Render has cognitive complexity 22 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · Misc.SeparateArgsFromCommand (cognitive 22) · ×1
  • Misc.SeparateArgsFromCommand (cognitive 22) source/SteamHelper/Misc.cs:17 — Misc.SeparateArgsFromCommand has cognitive complexity 22 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · OculusManager.FindOculusLibraryLocations (cognitive 22) · ×1
  • OculusManager.FindOculusLibraryLocations (cognitive 22) source/OculusHelper/OculusManager.cs:27 — OculusManager.FindOculusLibraryLocations has cognitive complexity 22 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · MainWindow.listView_ListRefreshIsRunningChanged (cognitive 21) · ×1
  • MainWindow.listView_ListRefreshIsRunningChanged (cognitive 21) REDACTED:1417 — MainWindow.listView_ListRefreshIsRunningChanged has cognitive complexity 21 (threshold 15). Of this number, 16 points are the body's own statements and 5 belong to one function literal inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · ApplicationEntryTools.AreEntriesRelated (cognitive 21) · ×1
  • ApplicationEntryTools.AreEntriesRelated (cognitive 21) source/UninstallTools/Factory/ApplicationEntryTools.cs:32 — ApplicationEntryTools.AreEntriesRelated 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.
D2 · Cognitive Complexity · ExecutableAttributeExtractor.FillInformationFromFileAttribs (cognitive 21) · ×1
  • ExecutableAttributeExtractor.FillInformationFromFileAttribs (cognitive 21) source/UninstallTools/Factory/InfoAdders/ExecutableAttributeExtractor.cs:44 — ExecutableAttributeExtractor.FillInformationFromFileAttribs 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 · DebugTracingScanner.FindJunk (cognitive 21) · ×1
  • DebugTracingScanner.FindJunk (cognitive 21) source/UninstallTools/Junk/Finders/Registry/DebugTracingScanner.cs:25 — DebugTracingScanner.FindJunk has cognitive 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, 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 · StringExtensions.ExtendedTrim (cognitive 21) · ×1
  • StringExtensions.ExtendedTrim (cognitive 21) source/KlocTools/Extensions/StringExtensions.cs:231 — StringExtensions.ExtendedTrim 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 · ProcessWaiterControl.updateTimer_Tick (cognitive 21) · ×1
  • ProcessWaiterControl.updateTimer_Tick (cognitive 21) source/KlocTools/Forms/ProcessWaiterControl.cs:170 — ProcessWaiterControl.updateTimer_Tick 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 · MsiTools.GetInstalledComponentPaths (cognitive 21) · ×1
  • MsiTools.GetInstalledComponentPaths (cognitive 21) source/KlocTools/IO/MsiTools.cs:137 — MsiTools.GetInstalledComponentPaths 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 · StartupManagerWindow.contextMenuStrip1_Opening (cognitive 20) · ×1
  • StartupManagerWindow.contextMenuStrip1_Opening (cognitive 20) source/UninstallTools/Dialogs/StartupManagerWindow.cs:89 — StartupManagerWindow.contextMenuStrip1_Opening 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 · StartupManager.AssignStartupEntries (cognitive 20) · ×1
  • StartupManager.AssignStartupEntries (cognitive 20) source/UninstallTools/Startup/StartupManager.cs:35 — StartupManager.AssignStartupEntries has cognitive complexity 20 (threshold 15). Most of this is not in the body itself: 4 of the 20 points are its own statements and the rest belongs to one function literal inside it that branches (line 49). 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 · Program.Main (cognitive 20) · ×1
  • Program.Main (cognitive 20) source/SteamHelper/Program.cs:36 — Program.Main has cognitive complexity 20 (threshold 15). Of this number, 16 points are the body's own statements and 4 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 · UninstallerListConfigurator.ListViewFilter (cognitive 19) · ×1
  • UninstallerListConfigurator.ListViewFilter (cognitive 19) source/BulkCrapUninstaller/Functions/ApplicationList/UninstallerListConfigurator.cs:121 — UninstallerListConfigurator.ListViewFilter 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 · CustomMessageBox.CustomMessageBox.ctor (cognitive 19) · ×1
  • CustomMessageBox.CustomMessageBox.ctor (cognitive 19) source/KlocTools/Forms/CustomMessageBox.cs:24 — CustomMessageBox.CustomMessageBox.ctor has cognitive complexity 19 (threshold 15). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
D2 · Cognitive Complexity · AppPropertiesGatherer.ConvertPropertiesIntoDataTable (cognitive 18) · ×1
  • AppPropertiesGatherer.ConvertPropertiesIntoDataTable (cognitive 18) source/BulkCrapUninstaller/Functions/AppPropertiesGatherer.cs:63 — AppPropertiesGatherer.ConvertPropertiesIntoDataTable 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 · DirectoryFactory.GetDirectoriesToScan (cognitive 18) · ×1
  • DirectoryFactory.GetDirectoriesToScan (cognitive 18) source/UninstallTools/Factory/DirectoryFactory.cs:43 — DirectoryFactory.GetDirectoriesToScan has cognitive complexity 18 (threshold 15). Of this number, 17 points are the body's own statements and 1 belongs to one function literal inside it that branches. To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · DirectoryFactory.CreateFromDirectoryHelper (cognitive 18) · ×1
  • DirectoryFactory.CreateFromDirectoryHelper (cognitive 18) source/UninstallTools/Factory/DirectoryFactory.cs:193 — DirectoryFactory.CreateFromDirectoryHelper 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 · AppExecutablesSearcher.ScanDirectory (cognitive 18) · ×1
  • AppExecutablesSearcher.ScanDirectory (cognitive 18) source/UninstallTools/Factory/InfoAdders/AppExecutablesSearcher.cs:78 — AppExecutablesSearcher.ScanDirectory 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 · StoreAppFactory.GetUninstallerEntries (cognitive 18) · ×1
  • StoreAppFactory.GetUninstallerEntries (cognitive 18) source/UninstallTools/Factory/StoreAppFactory.cs:38 — StoreAppFactory.GetUninstallerEntries 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 · BulkUninstallEntry.TestUninstallerForStalls (cognitive 18) · ×1
  • BulkUninstallEntry.TestUninstallerForStalls (cognitive 18) source/UninstallTools/Uninstaller/BulkUninstallEntry.cs:205 — BulkUninstallEntry.TestUninstallerForStalls has cognitive complexity 18 (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 · Program.ProcessCommandlineArguments (cognitive 18) · ×1
  • Program.ProcessCommandlineArguments (cognitive 18) source/WinUpdateHelper/Program.cs:70 — Program.ProcessCommandlineArguments 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 · ScriptFactory.GetUninstallerEntries (cognitive 17) · ×1
  • ScriptFactory.GetUninstallerEntries (cognitive 17) source/UninstallTools/Factory/ScriptFactory.cs:39 — ScriptFactory.GetUninstallerEntries 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 · FirewallRuleScanner.FindJunk (cognitive 17) · ×1
  • FirewallRuleScanner.FindJunk (cognitive 17) source/UninstallTools/Junk/Finders/Registry/FirewallRuleScanner.cs:21 — FirewallRuleScanner.FindJunk 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 · SoftwareRegKeyScanner.FindJunkRecursively (cognitive 17) · ×1
  • SoftwareRegKeyScanner.FindJunkRecursively (cognitive 17) source/UninstallTools/Junk/Finders/Registry/SoftwareRegKeyScanner.cs:126 — SoftwareRegKeyScanner.FindJunkRecursively 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 · ProcessWaiterControl.SetNodes (cognitive 17) · ×1
  • ProcessWaiterControl.SetNodes (cognitive 17) source/KlocTools/Forms/ProcessWaiterControl.cs:52 — ProcessWaiterControl.SetNodes has cognitive 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, 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 · UninstallProgressWindow.UninstallProgressWindow.ctor (cognitive 16) · ×1
  • UninstallProgressWindow.UninstallProgressWindow.ctor (cognitive 16) source/BulkCrapUninstaller/Forms/Windows/UninstallProgressWindow.cs:63 — UninstallProgressWindow.UninstallProgressWindow.ctor has cognitive complexity 16 (threshold 15). Most of this is not in the body itself: 1 of the 16 points is its own statement and the rest belongs to 4 function literals inside it that branch (lines 126, 116, 79, …). 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 · ApplicationUninstallerFactory.GetUninstallerEntries (cognitive 16) · ×1
  • ApplicationUninstallerFactory.GetUninstallerEntries (cognitive 16) source/UninstallTools/Factory/ApplicationUninstallerFactory.cs:25 — ApplicationUninstallerFactory.GetUninstallerEntries has cognitive complexity 16 (threshold 15). To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
D2 · Cognitive Complexity · BasicIconGetter.AddMissingInformation (cognitive 16) · ×1
  • BasicIconGetter.AddMissingInformation (cognitive 16) source/UninstallTools/Factory/InfoAdders/BasicIconGetter.cs:13 — BasicIconGetter.AddMissingInformation 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 · InfoAdderManager.CopyMissingInformation (cognitive 16) · ×1
  • InfoAdderManager.CopyMissingInformation (cognitive 16) source/UninstallTools/Factory/InfoAdders/InfoAdderManager.cs:159 — InfoAdderManager.CopyMissingInformation has cognitive complexity 16 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · ComScanner.GetClsidEntries (cognitive 16) · ×1
  • ComScanner.GetClsidEntries (cognitive 16) source/UninstallTools/Junk/Finders/Registry/ComScanner.cs:177 — ComScanner.GetClsidEntries 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 · FormsExtensions.SafeInvoke (cognitive 16) · ×1
  • FormsExtensions.SafeInvoke (cognitive 16) source/KlocTools/Extensions/FormsExtensions.cs:140 — FormsExtensions.SafeInvoke has cognitive complexity 16 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · LoadingDialogInterface.SetProgressInt (cognitive 16) · ×1
  • LoadingDialogInterface.SetProgressInt (cognitive 16) source/KlocTools/Forms/LoadingDialogInterface.cs:106 — LoadingDialogInterface.SetProgressInt 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 · NetFrameworkTools.GetNetFromKey (cognitive 16) · ×1
  • NetFrameworkTools.GetNetFromKey (cognitive 16) source/KlocTools/IO/NetFrameworkTools.cs:36 — NetFrameworkTools.GetNetFromKey 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 · WmiQueries.GetWindowsFeatures (cognitive 16) · ×1
  • WmiQueries.GetWindowsFeatures (cognitive 16) source/KlocTools/IO/WmiQueries.cs:18 — WmiQueries.GetWindowsFeatures 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 · RandomFilePicker.GetNextFolder (cognitive 16) · ×1
  • RandomFilePicker.GetNextFolder (cognitive 16) source/KlocTools/Subsystems/RandomFilePicker.cs:115 — RandomFilePicker.GetNextFolder 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 · AutomatedUninstallManager.ProcessRadioButtons (cognitive 16) · ×1
  • AutomatedUninstallManager.ProcessRadioButtons (cognitive 16) source/UninstallerAutomatizer/Automation/AutomatedUninstallManager.cs:361 — AutomatedUninstallManager.ProcessRadioButtons has cognitive complexity 16 (threshold 15). Of this number, 15 points are the body's own statements and 1 belongs to one function literal inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D29 · Static Analysis (SAST) · REDACTED · ×1
  • REDACTED
D3 · God Classes · FileTooLong · ×1
  • FileTooLong: REDACTED REDACTED — FileTooLong — 1046 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 546 over it, 2.09× 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 · ×1
  • ClassTooLong: AppUninstaller source/BulkCrapUninstaller/Functions/AppUninstaller.cs — ClassTooLong — 406 significant lines (blank, comment-only and punctuation-only lines excluded), 24 methods. The bar is 400 significant lines; this is 6 over it, 1.02× 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.
D4 · Code Duplication · Duplicated block (22 lines × 2) · ×1
  • Duplicated block (22 lines × 2) source/BulkCrapUninstaller/Functions/AppUninstaller.cs:476 — source/BulkCrapUninstaller/Functions/AppUninstaller.cs:476-497 | source/BulkCrapUninstaller/Functions/AppUninstaller.cs:735-756 — 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 `source/BulkCrapUninstaller/Functions/AppUninstaller.cs:476` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
D4 · Code Duplication · Duplicated block (23 lines × 2) · ×1
  • Duplicated block (23 lines × 2) source/UninstallTools/Junk/Finders/Registry/AudioPolicyConfigScanner.cs:28 — source/UninstallTools/Junk/Finders/Registry/AudioPolicyConfigScanner.cs:28-50 | source/UninstallTools/Junk/Finders/Registry/DebugTracingScanner.cs:27-49 — 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.
D4 · Code Duplication · Duplicated block (21 lines × 2) · ×1
  • Duplicated block (21 lines × 2) source/UninstallTools/ApplicationEntrySerializer.cs:132 — source/UninstallTools/ApplicationEntrySerializer.cs:132-152 | source/UninstallTools/ApplicationEntrySerializer.cs:156-176 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
D4 · Code Duplication · Duplicated block (16 lines × 2) · ×1
  • Duplicated block (16 lines × 2) source/ScriptHelper/Program.cs:48 — source/ScriptHelper/Program.cs:48-63 | source/SteamHelper/Program.cs:92-107 — 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 `source/ScriptHelper/Program.cs:48` 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 (15–16 lines × 2) · ×1
  • Duplicated block (15–16 lines × 2) REDACTED:960 — REDACTED:960-975 | source/BulkCrapUninstaller/Forms/Windows/UninstallProgressWindow.cs:322-336 — 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 `REDACTED:960` 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 (15 lines × 2) · ×1
  • Duplicated block (15 lines × 2) source/KlocTools/Controls/TwitterButton.cs:43 — source/KlocTools/Controls/TwitterButton.cs:43-57 | source/KlocTools/Controls/TwitterStatusButton.cs:36-50 — 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.
D4 · Code Duplication · Duplicated block (13 lines × 2) · ×1
  • Duplicated block (13 lines × 2) source/ScriptHelper/Program.cs:67 — source/ScriptHelper/Program.cs:67-79 | source/SteamHelper/Program.cs:111-123 — 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 `source/ScriptHelper/Program.cs:67` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
D4 · Code Duplication · Duplicated block (14 lines × 2) · ×1
  • Duplicated block (14 lines × 2) source/OculusHelper/Program.cs:26 — source/OculusHelper/Program.cs:26-39 | source/StoreAppHelper/Program.cs:28-41 — 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 `source/OculusHelper/Program.cs:26` 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. 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 × 3) · ×1
  • Duplicated block (10 lines × 3) REDACTED:1799 — REDACTED:1799-1808 | REDACTED:1855-1864 | REDACTED:1869-1878 — 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 `REDACTED:1799` 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 (8–9 lines × 2) · ×1
  • Duplicated block (8–9 lines × 2) source/BulkCrapUninstaller/Functions/AppUninstaller.cs:552 — source/BulkCrapUninstaller/Functions/AppUninstaller.cs:552-559 | source/BulkCrapUninstaller/Functions/AppUninstaller.cs:571-579 — 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 `source/BulkCrapUninstaller/Functions/AppUninstaller.cs:552` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `source/BulkCrapUninstaller/Functions/AppUninstaller.cs:559` calls `Remove` and `source/BulkCrapUninstaller/Functions/AppUninstaller.cs:579` does not — after which the two agree again for 3 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
D4 · Code Duplication · Duplicated block (6 lines × 2) · ×1
  • Duplicated block (6 lines × 2) source/UninstallTools/Junk/Finders/Registry/ComScanner.cs:200 — source/UninstallTools/Junk/Finders/Registry/ComScanner.cs:200-205 | source/UninstallTools/Junk/Finders/Registry/ComScanner.cs:256-261 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. 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 (5 lines × 2) · ×1
  • Duplicated block (5 lines × 2) source/KlocTools/Tools/PathTools.cs:358 — source/KlocTools/Tools/PathTools.cs:358-362 | source/KlocTools/Tools/PathTools.cs:367-371 — 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 (3–7 lines × 3) · ×1
  • Duplicated block (3–7 lines × 3) source/BCU-console/Program.cs:163 — source/BCU-console/Program.cs:163-169 | source/BCU-console/Program.cs:218-224 | source/BCU-console/Program.cs:264-266 — 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. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
D5 · Coupling · Off the main sequence · ×1
  • Off the main sequence: ObjectListView source/ObjectListView/ObjectListView.csproj:1 — ObjectListView: abstractness 0.10, instability 0.00, distance 0.90 — zone of pain — concrete and depended on by 2 project(s), so it's rigid to change.
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 · Both branches open with the same statements · ×1
  • Both branches open with the same statements — the condition does not decide them source/NBug_custom/Settings.cs:736 — The first 1 statement of the `if` and of the `else` are identical, so it runs on both paths regardless of the condition. Lift it above the `if` — leaving it duplicated inside makes the branches read as though they handled this differently.
S1 · Cryptographic Hygiene · Weak hash algorithm · ×1
  • Weak hash algorithm source/BulkCrapUninstaller/Functions/Ratings/UninstallerRatingManager.Utils.cs:57 — MD5/SHA1 is constructed here, and both are collision-broken. If this digest protects anything — a signature, an integrity or tamper check, a credential, or any value an attacker can influence — that is a real weakness: use SHA-256+ for content integrity, or a KDF (PBKDF2/Argon2/BCrypt) for password storage. If it only derives a non-security identifier (a cache key, a file or mutex name), collision resistance carries no security consequence here; make that intent explicit instead — a non-cryptographic hash such as `System.IO.Hashing.XxHash64`/`Crc32` says it in code — since the algorithm alone cannot distinguish the two uses.
S1 · Cryptographic Hygiene · Ciphertext is encrypted but not authenticated · ×1
  • Ciphertext is encrypted but not authenticated source/NBug_custom/Settings.cs:926 — This type encrypts through `SymmetricAlgorithm`, whose every cipher mode (CBC/ECB/OFB/CFB/CTS) is unauthenticated, and no keyed MAC or AEAD cipher appears anywhere in it — so nothing establishes that the ciphertext it produced is the ciphertext it later reads back. Encryption alone provides confidentiality, not integrity: unauthenticated CBC is MALLEABLE, and an attacker who can modify stored or transmitted ciphertext can flip chosen plaintext bits in the following block by flipping ciphertext bits in the preceding one, without ever knowing the key. Where the decrypt path reports failure differently for a padding error than for a downstream one — a broad `catch` that returns null is the usual spelling — the same construction also answers the attacker's questions, which is the padding-oracle shape that recovers plaintext outright. Prefer an AEAD cipher: `AesGcm` or `ChaCha20Poly1305` authenticate the ciphertext as part of encrypting it, and give you an associated-data slot for the surrounding context. Where the format cannot change, MAC it with encrypt-then-MAC — HMAC-SHA256 over the IV and the ciphertext together, with a key derived separately from the encryption key — and verify that tag with `CryptographicOperations.FixedTimeEquals` BEFORE decrypting anything.
S1 · Cryptographic Hygiene · The encryption IV is the same for every message · ×1
  • The encryption IV is the same for every message source/NBug_custom/Settings.cs:926 — This encryption's initialisation vector is derived from `cipher`, the same key derivation as the key, so every message encrypted under the same key gets the same IV. An IV is not a secret and does not have to be one — its whole job is to be DIFFERENT each time, so that encrypting the same plaintext twice does not produce the same ciphertext. Fix it and CBC becomes an equality oracle: the mode XORs the IV into the first plaintext block and chains from there, so two messages encrypted with the same key and IV produce byte-identical ciphertext for exactly as long as their plaintexts agree. An observer who can see two ciphertexts — a repository of encrypted config files, a database column, a backup — learns that two records match and how many blocks in they diverge, without the key and without breaking anything. The same defect under a counter-based mode is worse and not recoverable by comparison: CTR and GCM XOR the plaintext against a keystream determined by the key and nonce, so a repeated nonce leaks the XOR of the two plaintexts outright, and under GCM it also forfeits the authentication key. Generate the IV with a cryptographic RNG for each message — `RandomNumberGenerator.Fill(iv)` in .NET, `crypto.randomBytes(16)` in Node — and write it alongside the ciphertext (prepending the block is the usual spelling); the receiver reads it back from there. Deriving the IV from the key material is the specific trap to avoid: it looks like rigour and produces a constant, because the derivation's inputs do not change between messages.
SC1 · Supply-chain hygiene · NuGet dependencies are not locked · ×1
  • NuGet dependencies are not locked — No packages.lock.json and no central package management — restores aren't reproducible or pinned (SSDF PW.4.4). Enable <RestorePackagesWithLockFile>true</RestorePackagesWithLockFile> (commit the lockfile) or adopt Directory.Packages.props. Advisory — never scored.
X1 · Async correctness · Blocking `Process.WaitForExit` inside an `async` method · ×1
  • Blocking `Process.WaitForExit` inside an `async` method REDACTED:134 — `Process.WaitForExit` blocks the thread on I/O while `Process.WaitForExitAsync` exists to wait without one — inside a method that is already `async`, await the twin.
X15 · Unvalidated length from an untrusted reader · Length read from the parsed input is spent without ever being bounded · ×1
  • Length read from the parsed input is spent without ever being bounded source/NBug_custom/Core/Util/Storage/ZipStorer.cs:858 — `centralSize` is read from the stream being parsed at line 846 (`ReadInt32`), then used to size an array at line 858 — and nowhere in this method is `centralSize` bounded from above — compared to a limit, clamped, or checked against the input that remains (a zero or sign test, or the loop that counts up to it, bounds nothing). A file the caller did not write therefore chooses the size directly: a value near `int.MaxValue` allocates until the process dies, and a value that overflows the cast to `int` goes negative and throws out of a parser whose failure path was written for malformed input, not for hostile input. Bound `centralSize` against the bytes actually remaining in the stream before spending it.
X2 · Cancellation propagation · Async method without CancellationToken · ×1
  • Async method without CancellationToken: StartHelperAndReadOutput REDACTED:97 — No CancellationToken parameter — this work can't be stopped early once started.
Minor — 86 finding(s)
IC1 · Incompleteness & stubs · Commented-out code · ×33
  • Commented-out code source/BulkCrapUninstaller/Controls/Settings/AdvancedFilters.cs:247 — 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 source/BulkCrapUninstaller/EntryPoint.cs:162 — 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 source/BulkCrapUninstaller/EntryPoint.cs:166 — 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 source/BulkCrapUninstaller/Forms/Helpers/DebugWindow.cs:78 — 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 source/BulkCrapUninstaller/Forms/Helpers/DebugWindow.cs:83 — 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 source/BulkCrapUninstaller/Forms/Helpers/DebugWindow.cs:85 — 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 source/BulkCrapUninstaller/Forms/Helpers/DebugWindow.cs:89 — 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 source/BulkCrapUninstaller/Forms/Helpers/DebugWindow.cs:90 — 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: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 source/BulkCrapUninstaller/Forms/Windows/JunkRemoveWindow.cs:199 — 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 source/BulkCrapUninstaller/Forms/Windows/JunkRemoveWindow.cs:217 — 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:490 — 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:808 — 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:1126 — 4 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 REDACTED:1131 — 18 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 REDACTED:1263 — 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:1273 — 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:1500 — 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:1501 — 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:1517 — 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:1519 — 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 source/BulkCrapUninstaller/Forms/Windows/SettingsWindow.cs:118 — 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 source/BulkCrapUninstaller/Forms/Windows/SettingsWindow.cs:119 — 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 source/BulkCrapUninstaller/Forms/Wizards/BeginUninstallTaskWizard.cs:118 — 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 source/BulkCrapUninstaller/Forms/Wizards/FirstStartBox.cs:170 — A line of code has been commented out rather than removed — dead weight that rots and confuses. Delete it (version control remembers).
  • + 8 more in this group — see findings.md.
X7 · Silent fallback defaults · Silent fallback default in catch · ×17
  • Silent fallback default in catch source/BulkCrapUninstaller/Controls/FileTargeter.cs:107 — `ProcessFiles` swallows every exception into `return null;` — a data error becomes a silent behavior change with no trail. Log the failure or let validation throw.
  • Silent fallback default in catch source/BulkCrapUninstaller/EntryPoint.cs:121 — `HandleBeingSecondInstance` 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 source/BulkCrapUninstaller/Functions/Tracking/DatabaseStatSender.cs:30 — `SendData` 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 source/BulkCrapUninstaller/NBugConfigurator.cs:72 — `Send` 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 source/UninstallTools/ApplicationUninstallerEntry.cs:414 — `GetAboutUri` swallows every exception into `return null;` — a data error becomes a silent behavior change with no trail. Log the failure or let validation throw.
  • Silent fallback default in catch source/UninstallTools/ApplicationUninstallerEntry.cs:494 — `GetInstallDateString` swallows `SystemException` into `return string.Empty;` — a data error becomes a silent behavior change with no trail. Log the failure or let validation throw.
  • Silent fallback default in catch source/UninstallTools/Factory/FactoryTools.cs:78 — `CheckIsValid` swallows `ArgumentException` and sets `isPathRooted = false;` — a data error becomes a silent behavior change with no trail. Log the failure or let validation throw.
  • Silent fallback default in catch source/UninstallTools/Startup/Normal/OldStartupDisable.cs:246 — `StillExists` 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 source/UninstallTools/Startup/Service/ServiceEntry.cs:50 — `Disabled` swallows `ManagementException` 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 source/UninstallTools/Startup/Service/ServiceEntry.cs:70 — `StillExists` swallows `ManagementException` 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 source/KlocTools/Extensions/RegistryKeyExtensions.cs:41 — `TryGetValueNames` swallows `IOException` into `return Enumerable.Empty<string>();` — a data error becomes a silent behavior change with no trail. Log the failure or let validation throw.
  • Silent fallback default in catch source/KlocTools/IO/AdvancedFileInfo.cs:125 — `FromPath` swallows every exception and sets `fileVersionInfo = null;` — a data error becomes a silent behavior change with no trail. Log the failure or let validation throw.
  • Silent fallback default in catch source/KlocTools/Tools/SleepControls.cs:16 — `PreventSleepOrShutdown` swallows `SystemException` 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 source/KlocTools/Tools/SleepControls.cs:30 — `AllowSleepOrShutdown` swallows `SystemException` 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 source/KlocTools/Tools/SleepControls.cs:62 — `PutToSleep` swallows `SystemException` 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 source/UniversalUninstaller/TargetList.cs:79 — `SizeGetter` swallows every exception into `return FileSize.Empty;` — a data error becomes a silent behavior change with no trail. Log the failure or let validation throw.
  • Silent fallback default in catch source/BCU-console/Program.cs:153 — `Main` swallows `SystemException` into `return 13;` — a data error becomes a silent behavior change with no trail. Log the failure or let validation throw.
X10 · Duplicated predicate · Duplicated predicate · ×8
  • Duplicated predicate source/ObjectListView/ObjectListView.cs:10755 — `!lastItemBounds.IsEmpty && lastItemBounds.Bottom < columnBounds.Bottom` appears character-identically in 2 files — source/ObjectListView/ObjectListView.cs, source/ObjectListView/Rendering/Decorations.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 source/NBug_custom/Core/Reporting/BugReport.cs:130 — `Settings.StopReportingAfter < 0 || File.GetLastWriteTime(Settings.EntryAssembly.Location) .AddDays(Settings.StopReportingAfter) .CompareTo(D…` appears character-identically in 2 files — source/NBug_custom/Core/Reporting/BugReport.cs, source/NBug_custom/Core/Submission/Dispatcher.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 source/StoreAppHelper/Program.cs:23 — `args.Length == 1 && string.Equals(args[0], @"/query", StringComparison.OrdinalIgnoreCase)` appears character-identically in 2 files — source/OculusHelper/Program.cs, source/StoreAppHelper/Program.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 source/StoreAppHelper/Program.cs:44 — `args.Length == 2 && string.Equals(args[0], @"/uninstall", StringComparison.OrdinalIgnoreCase)` appears character-identically in 2 files — source/OculusHelper/Program.cs, source/StoreAppHelper/Program.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 source/ObjectListView/Implementation/OLVListItem.cs:166 — `decorations != null && decorations.Count > 0` appears character-identically in 2 files — source/ObjectListView/Implementation/OLVListItem.cs, source/ObjectListView/Implementation/OLVListSubItem.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 source/KlocTools/Controls/EditableCheckedListView.cs:86 — `string.IsNullOrEmpty(output) || Items.Contains(output)` appears character-identically in 2 files — source/KlocTools/Controls/EditableCheckedListView.cs, source/KlocTools/Controls/EditableListView.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 source/UninstallTools/Junk/Finders/Drive/UninstallerLocationScanner.cs:40 — `target.UninstallerKind == UninstallerType.Msiexec && !target.BundleProviderKey.IsEmpty()` appears character-identically in 2 files — source/UninstallTools/Junk/Finders/Drive/UninstallerLocationScanner.cs, source/UninstallTools/Junk/Finders/Registry/UninstallerKeySearcher.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 source/ObjectListView/ObjectListView.cs:2021 — `value == null && HeaderFormatStyle == null` appears character-identically in 2 files — source/ObjectListView/OLVColumn.cs, source/ObjectListView/ObjectListView.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.
P2 · Observability · Console output used as the logging channel · ×7
  • Console output used as the logging channel REDACTED:169 — `REDACTED` reports through `Console.Write…` at line 169 although other files in its project log through a logger. Console lines carry no level, category or structured properties and never reach the log pipeline or its exporters.
  • Console output used as the logging channel REDACTED:232 — `REDACTED` reports through `Console.Write…` at line 232 although other files in its project log through a logger. Console lines carry no level, category or structured properties and never reach the log pipeline or its exporters.
  • Console output used as the logging channel REDACTED:251 — `REDACTED` reports through `Console.Write…` at line 251 although other files in its project log through a logger. Console lines carry no level, category or structured properties and never reach the log pipeline or its exporters.
  • Console output used as the logging channel REDACTED:330 — `REDACTED` reports through `Console.Write…` at line 330 although other files in its project log through a logger. Console lines carry no level, category or structured properties and never reach the log pipeline or its exporters.
  • Console output used as the logging channel REDACTED:351 — `REDACTED` reports through `Console.Write…` at line 351 although other files in its project log through a logger. Console lines carry no level, category or structured properties and never reach the log pipeline or its exporters.
  • Console output used as the logging channel source/UninstallerAutomatizer/Automation/UninstallHandler.cs:189 — `source/UninstallerAutomatizer/Automation/UninstallHandler.cs` reports through `Console.Write…` at line 189 although other files in its project log through a logger. Console lines carry no level, category or structured properties and never reach the log pipeline or its exporters.
  • Console output used as the logging channel source/UninstallerAutomatizer/Automation/UninstallHandler.cs:259 — `source/UninstallerAutomatizer/Automation/UninstallHandler.cs` reports through `Console.Write…` at line 259 although other files in its project log through a logger. Console lines carry no level, category or structured properties and never reach the log pipeline or its exporters.
C4 · Data Retention · Partial data-retention evidence · ×1
  • Partial data-retention evidence — A retention mechanism is present, but the data-lifecycle is not yet complete — missing: an expiry limit — a declared maximum age / TTL after which the data is no longer kept, a scheduled purge / cleanup job (PurgeOlderThan / CleanupJob).
C5 · Data-Subject Rights · Partial data-subject-rights support · ×1
  • Partial data-subject-rights support — Corroborated rights: erasure ✗ · export ✗ · consent ✓. Each tick means this scan found code in the repository implementing that right — a deletion/anonymisation path for erasure, a data-export or portability path for export, and consent state recorded alongside the personal data it authorises. A ✗ therefore means no such code was recognised HERE, not that the right is unsupported: a capability provided by a platform, a manual runbook, or code spelled in a way this scan does not match is not visible to it. Confirm before treating a cross as a gap; where it is one, the right has to be fulfilled manually.
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 — 4 of 18 project(s) overshoot their size bounds, lowering Project Cohesion to 5.6/10. The most over is `ObjectListView` (50799 LoC, 246 public types across 2 namespaces). Review these for cohesion — split a project that spans unrelated responsibilities.
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 — 1 of 196 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; 196 of the 353 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: source/UninstallTools/Factory/Json/DynamicStringArrayConverter.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.
D34 · Knowledge Freshness · Orphaned file · ×1
  • Orphaned file source/UninstallTools/Factory/Json/DynamicStringArrayConverter.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.
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.
M3 · Folder & project structure · No tests/ separation · ×1
  • No tests/ separation — Tests aren't grouped in a dedicated test folder — the test surface isn't separable from production code at a glance.
M3 · Folder & project structure · Inconsistent root namespaces · ×1
  • Inconsistent root namespaces — Only 2/18 projects share a common root namespace — the code's module identity is inconsistent.
M4 · Documentation accuracy · README/code drift · ×1
  • README/code drift README.md:43 — README.md names .NET 6, but the projects target .NET 8. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
P2 · Observability · Logging is not universal · ×1
  • Logging is not universal — Only 6/17 service-like projects use logging (pure contract/DTO projects are excluded — they have nothing to log). Of those 17, 10 ship a process this repository operates; the rest are libraries their consumer hosts, where the logging decision belongs to the host.
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 2777 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.)
X2 · Cancellation propagation · Not all async methods take a CancellationToken · ×1
  • Not all async methods take a CancellationToken — Only 0/1 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.
X5 · Nullable reference types · Nullable reference types not enabled everywhere · ×1
  • Nullable reference types not enabled everywhere — 0/17 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.
X7 · Silent fallback defaults · Silent fallback default on parse failure · ×1
  • Silent fallback default on parse failure source/UninstallTools/Controls/FilterEditor.cs:70 — `SelectedTargetInfo` falls back to `ComparisonTargetInfo.AllTargetComparison` when `PropertyTargets.TryGetValue(selection, out c)` is false, with no log or throw — a malformed value silently becomes that default. Log the input or fail validation. If that constant is the correct answer to the test rather than a stand-in for a value that could not be read, this is not a silent default: say so in a comment on the member and the row stops firing.
Minor — 17 finding(s)
D19 · Documentation Quality · XML-doc coverage · ×17
  • XML-doc coverage: BulkCrapUninstaller source/BulkCrapUninstaller/BulkCrapUninstaller.csproj — BulkCrapUninstaller: 7 % XML-doc coverage (33/454).
  • XML-doc coverage: UninstallTools source/UninstallTools/UninstallTools.csproj — UninstallTools: 12 % XML-doc coverage (99/820).
  • XML-doc coverage: KlocTools source/KlocTools/KlocTools.csproj — KlocTools: 37 % XML-doc coverage (365/994).
  • XML-doc coverage: StoreAppHelper source/StoreAppHelper/StoreAppHelper.csproj — StoreAppHelper: 36 % XML-doc coverage (9/25).
  • XML-doc coverage: UninstallerAutomatizer source/UninstallerAutomatizer/UninstallerAutomatizer.csproj — UninstallerAutomatizer: 22 % XML-doc coverage (11/51).
  • XML-doc coverage: SteamHelper source/SteamHelper/SteamHelper.csproj — SteamHelper: 29 % XML-doc coverage (10/35).
  • XML-doc coverage: ObjectListView source/ObjectListView/ObjectListView.csproj — ObjectListView: 84 % XML-doc coverage (1799/2148).
  • XML-doc coverage: WinUpdateHelper source/WinUpdateHelper/WinUpdateHelper.csproj — WinUpdateHelper: 53 % XML-doc coverage (9/17).
  • XML-doc coverage: UniversalUninstaller source/UniversalUninstaller/UniversalUninstaller.csproj — UniversalUninstaller: 29 % XML-doc coverage (9/31).
  • XML-doc coverage: PortableSettingsProvider source/PortableSettingsProvider/PortableSettingsProvider.csproj — PortableSettingsProvider: 38 % XML-doc coverage (10/26).
  • XML-doc coverage: SimpleTreeMap source/SimpleTreeMap/SimpleTreeMap.csproj — SimpleTreeMap: 15 % XML-doc coverage (9/61).
  • XML-doc coverage: SimpleTreeMapTestApp source/SimpleTreeMapTests/SimpleTreeMapTestApp.csproj — SimpleTreeMapTestApp: 53 % XML-doc coverage (9/17).
  • XML-doc coverage: BCU-console source/BCU-console/BCU-console.csproj — BCU-console: 60 % XML-doc coverage (9/15).
  • XML-doc coverage: OculusHelper source/OculusHelper/OculusHelper.csproj — OculusHelper: 39 % XML-doc coverage (9/23).
  • XML-doc coverage: ScriptHelper source/ScriptHelper/ScriptHelper.csproj — ScriptHelper: 41 % XML-doc coverage (9/22).
  • XML-doc coverage: NetSettingBinder source/NetSettingBinder/NetSettingBinder.csproj — NetSettingBinder: 58 % XML-doc coverage (30/52).
  • XML-doc coverage: NBug source/NBug_custom/NBug.csproj — NBug: 18 % XML-doc coverage (70/392).

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-dba3c218509c43fba4cfcf05449ce938/history.json --exit-code 0 --source .0artifacts/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-dba3c218509c43fba4cfcf05449ce938/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 .22artifacts/raw/semgrep.json
D30 · Dependency Vulnerabilitiesnuget—nuget: not applicable — nuget: the solution did not restore on the analyzer's .NET SDK (an SDK/target-framework/restore mismatch, common for an older codebase), so there was no restored dependency graph to 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) — `source/HelperTools/LogWriter.cs`, `source/KlocTools/Forms/Tools/PremadeDialogs.cs`, `source/KlocTools/IO/MsiTools.cs`, `source/UninstallTools/Uninstaller/NoWayToUninstallException.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 Dependenciesnone (no readable dependency manifest)—none (no readable dependency manifest): not applicable — Not scored — no dependency manifest in a supported ecosystem was read for this repository. A gap in the analyzer's language coverage, NOT a finding that the repository is free of vulnerable dependencies (a Python pyproject.toml/requirements.txt (pip/uv/Poetry), a Swift Package.swift/Package.resolved, a Cargo manifest, a Go module (go.mod/go.sum), a Gradle version catalogue, a Maven POM, an sbt build (build.sbt), composer.json, package.json, a Dart pubspec.yaml, an Elixir mix.exs/mix.lock (Hex), a rebar.config / erlang.mk DEPS (Hex), a Ruby Gemfile/Gemfile.lock or .gemspec (Bundler/RubyGems) — not scanned yet).0—

Run 01a16795-cf3a-7d62-b3fd-2a05ff0a739b · 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 — 5 field(s) across 2 categories, 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 — 3 field(s)
  • AdvancedFileInfo.FullName source/KlocTools/IO/AdvancedFileInfo.cs:64
  • FontGrabber.ValidFontFamilyNames source/KlocTools/Subsystems/FontGrabber.cs:24
  • App.FullName source/StoreAppHelper/App.cs:16
Email — 2 field(s)
  • AccountData.emailField source/NBug_custom/Core/Submission/Tracker/Mantis/AccountData.cs:10
  • AccountData.email source/NBug_custom/Core/Submission/Tracker/Mantis/AccountData.cs:34

Issues: 104 · Warnings: 283 · Recommendations: 86 · Info: 17 — Appendix A · all findings · full markdown report.
Generated by Watchdog — deterministic code-health analysis. 23-10-2026 @ 07:07 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