Public report of DevToys-app/DevToys, published 22 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, 22 October 2026, 23:33 UTC · Survey ID cd_5f7bda437937412bb35acf878ad95523

DevToys-app/DevToys

Measured 22 October 2026, 23:29 UTC, at code version 2dbbc8a

No regression since the last survey Test reliability: not measuredBoundary Type-Coupling: not measuredSupply-chain provenance & signing: 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.

Test reliability is not measured: The repo's test suite did not build.

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

Supply-chain provenance & signing is not measured: Supply-chain provenance is not scored (this pipeline releases no artifact), but its build steps or GitHub Actions workflows have integrity defects, or nothing watches its dependency set for published advisories.

CAI score 42out of 100 At risk 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.

Security and Compliance 85 Adequate Architecture 72 Strong Performance 70 Adequate Code Health 58 Adequate Maturity 46 Weak Accessibility 38 Weak Production Readiness 35 Weak

A medium codebase: 42,184 lines of product code in 12 projects, tests not counted · Estimated rebuild effort: about 0.3 person-years · Weakest lens: Production Readiness, 35

Findings by how serious they are

57 critical 361 serious 229 minor

6 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
22 October 2026, 23:29 UTC

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

A critical security finding is open, such as a library with a known critical vulnerability or a password or key found in the code. The score itself is unchanged, but its band shows At risk until the finding is fixed. See the Security and Compliance lens.

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 ▸

86of 90 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.
616of 647 findings point to an exact file and line, so you can open each one in the code. The other 31 concern the repository as a whole, such as missing documentation.
90dimensions across 7 lenses, read from 42,184 lines of product code in 12 projects.
Chapters

Executive summary

DevToys-app/DevToys scores 42 out of 100, but it is rated At risk while a critical security finding is open; the score itself is unchanged.

The weakest lens counts most in the score, and here that is Production Readiness, which scores 35 and is rated Weak. Its Tooling dimension scores 0 out of 10, and until that reaches 4, Production Readiness can't be rated higher than Adequate. The first actions are to resolve the 1 No ADRs found finding(s) in ADR Quality and to 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, and if Production Readiness rose to 70, the score would rise from 42 to about 48.

57 findings are critical: 25 in Explicit Debt, 11 in Static Analysis (SAST), ten in Dependency Vulnerabilities, three in Page structure, three in Project dependency cycles, two in Keyboard semantics, one in ARIA correctness, one in Dependency direction and one in Text alternatives.

Watchdog couldn't measure 4 dimensions in this code, among them Code Coverage, Dependency Hygiene and IL Efficiency, so they are left out of the score. The product code is 42,184 lines, which would take an estimated 0.3 person-years, around €47,000, to rebuild.

Code Health 58 Adequate Architecture 72 Strong Maturity 46 Weak, capped by Knowledge Freshness and Architecture documentation Production Readiness 35 Weak, capped by Tooling, Security & performance tooling and Outbound HTTP resilience Security and Compliance 85 Adequate, capped by Dependency Vulnerabilities Accessibility 38 Weak, capped by Keyboard semantics and Visual & motion safety Performance 70 Adequate

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.
Production Readiness 35 · counts for 46%Accessibility 38 · counts for 25%Maturity 46 · counts for 14%Code Health 58 · counts for 8%Performance 70 · counts for 4%Architecture 72 · counts for 2%Security and Compliance 85 · counts for 1%

If Production Readiness rose from 35 to 70, the lowest score rated Strong, the score would rise from 42 to about 48.

Code composition: what the lines of code are
Business logic 30%Supporting code 55%Tests 7%Generated by tools 8%Code analyzers 0%
New since the last survey: 114 findings

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

  • Explicit Debt · EmptyCatchBlock src/app/dev/DevToys.Blazor/Components/JSStyledComponentBase.cs
  • Explicit Debt · EmptyCatchBlock src/app/dev/DevToys.Blazor/Components/Layout/Popover/Popover.razor.cs
  • Explicit Debt · EmptyCatchBlock src/app/dev/DevToys.Blazor/Core/Services/FontService.cs
  • Explicit Debt · EmptyCatchBlock src/app/dev/DevToys.Blazor/Core/Services/MonacoLanguageService.cs
  • Explicit Debt · EmptyCatchBlock src/app/dev/DevToys.Blazor/Core/Services/MonacoLanguageService.cs
  • Explicit Debt · EmptyCatchBlock src/app/dev/DevToys.Core/Logging/FileLoggerProvider.cs
  • Explicit Debt · EmptyCatchBlock src/app/dev/DevToys.Core/Logging/FileLoggerProvider.cs
  • Explicit Debt · EmptyCatchBlock src/app/dev/DevToys.Core/Logging/FileLoggerProvider.cs
  • Explicit Debt · EmptyCatchBlock src/app/dev/DevToys.Core/Mef/RecursiveDirectoryCatalog.cs
  • Explicit Debt · EmptyCatchBlock src/app/dev/DevToys.Core/Tools/GuiToolInstance.cs
  • Explicit Debt · EmptyCatchBlock src/app/dev/DevToys.Core/Tools/GuiToolInstance.cs
  • Explicit Debt · EmptyCatchBlock src/app/dev/DevToys.Core/Tools/GuiToolInstance.cs
  • Explicit Debt · EmptyCatchBlock src/app/dev/platforms/desktop/DevToys.Linux/Components/BlazorWebView/BlazorWebViewManager.cs
  • Static Analysis (SAST) · REDACTED
  • Supply-chain Provenance & Signing · REDACTED
  • Async correctness · Blocking `StreamWriter.Flush` inside an `async` method src/app/dev/DevToys.Api/Core/OneOfExtensions.cs
  • Async correctness · Sync-over-async (deadlock risk) through `.Result` src/app/dev/DevToys.Api/Core/Threading/AsyncLazy.cs
  • Async correctness · Sync-over-async (deadlock risk) through `.Wait(…)` src/app/dev/DevToys.Core/Logging/FileLoggerProvider.cs
  • Async correctness · Blocking `StreamWriter.Write` inside an `async` method src/app/dev/DevToys.Blazor/Components/UIElements/UITextInputWrapper.razor.cs
  • Cancellation propagation · Async method without CancellationToken: SaveAllSettingsAsync src/app/dev/platforms/desktop/DevToys.CLI/Core/Settings/SettingsStorage.cs
  • Cancellation propagation · Async method without CancellationToken: GetOptionsAsync src/app/dev/DevToys.Blazor/Components/Text/MonacoEditor/Monaco/TextModel.cs
  • Cancellation propagation · Async method without CancellationToken: GetVersionIdAsync src/app/dev/DevToys.Blazor/Components/Text/MonacoEditor/Monaco/TextModel.cs
  • Cancellation propagation · Async method without CancellationToken: GetAlternativeVersionIdAsync src/app/dev/DevToys.Blazor/Components/Text/MonacoEditor/Monaco/TextModel.cs
  • Cancellation propagation · Async method without CancellationToken: GetValueAsync src/app/dev/DevToys.Blazor/Components/Text/MonacoEditor/Monaco/TextModel.cs
  • Cancellation propagation · Async method without CancellationToken: GetValueLengthAsync src/app/dev/DevToys.Blazor/Components/Text/MonacoEditor/Monaco/TextModel.cs
  • Cancellation propagation · Async method without CancellationToken: GetValueInRangeAsync src/app/dev/DevToys.Blazor/Components/Text/MonacoEditor/Monaco/TextModel.cs
  • Cancellation propagation · Async method without CancellationToken: GetValueLengthInRangeAsync src/app/dev/DevToys.Blazor/Components/Text/MonacoEditor/Monaco/TextModel.cs
  • Cancellation propagation · Async method without CancellationToken: GetCharacterCountInRangeAsync src/app/dev/DevToys.Blazor/Components/Text/MonacoEditor/Monaco/TextModel.cs
  • Cancellation propagation · Async method without CancellationToken: GetLineCountAsync src/app/dev/DevToys.Blazor/Components/Text/MonacoEditor/Monaco/TextModel.cs
  • Cancellation propagation · Async method without CancellationToken: GetLineContentAsync src/app/dev/DevToys.Blazor/Components/Text/MonacoEditor/Monaco/TextModel.cs
  • Cancellation propagation · Async method without CancellationToken: GetLineLengthAsync src/app/dev/DevToys.Blazor/Components/Text/MonacoEditor/Monaco/TextModel.cs
  • Cancellation propagation · Async method without CancellationToken: GetLinesContentAsync src/app/dev/DevToys.Blazor/Components/Text/MonacoEditor/Monaco/TextModel.cs
  • Cancellation propagation · Async method without CancellationToken: GetEOLAsync src/app/dev/DevToys.Blazor/Components/Text/MonacoEditor/Monaco/TextModel.cs
  • Exception handling · Swallowed exception (empty catch) src/app/dev/DevToys.Core/Logging/FileLoggerProvider.cs
  • Exception handling · Swallowed exception (empty catch) src/app/dev/DevToys.Core/Logging/FileLoggerProvider.cs
  • Exception handling · Swallowed exception (empty catch) src/app/dev/DevToys.Core/Logging/FileLoggerProvider.cs
  • Exception handling · Swallowed exception (empty catch) src/app/dev/DevToys.Core/Logging/FileLoggerProvider.cs
  • Exception handling · Swallowed exception (empty catch) src/app/dev/DevToys.Core/Mef/RecursiveDirectoryCatalog.cs
  • Exception handling · Swallowed exception (empty catch) src/app/dev/DevToys.Core/Tools/GuiToolInstance.cs
  • Exception handling · Swallowed exception (empty catch) src/app/dev/DevToys.Core/Tools/GuiToolInstance.cs
  • Exception handling · Swallowed exception (empty catch) src/app/dev/DevToys.Core/Tools/GuiToolInstance.cs
  • Exception handling · Swallowed exception (empty catch) src/app/dev/DevToys.Blazor/Components/JSStyledComponentBase.cs
  • Exception handling · Swallowed exception (empty catch) src/app/dev/DevToys.Blazor/Components/Layout/Popover/Popover.razor.cs
  • Exception handling · Swallowed exception (empty catch) src/app/dev/DevToys.Blazor/Core/Services/FontService.cs
  • Exception handling · Swallowed exception (empty catch) src/app/dev/DevToys.Blazor/Core/Services/MonacoLanguageService.cs
  • Exception handling · Swallowed exception (empty catch) src/app/dev/DevToys.Blazor/Core/Services/MonacoLanguageService.cs
  • Exception handling · Swallowed exception (empty catch) src/app/dev/platforms/desktop/DevToys.Linux/Components/BlazorWebView/BlazorWebViewManager.cs
  • Dependency direction · Dependency-rule violation: DevToys.Core (Domain) → DevToys.Api (Web) src/app/dev/DevToys.Core/AppHelper.cs
  • Dependency direction · Dependency-rule violation: DevToys.Core (Domain) → DevToys.Api (Web) src/app/dev/DevToys.Core/ExtensionOrderer.cs
  • Dependency direction · Dependency-rule violation: DevToys.Core (Domain) → DevToys.Api (Web) src/app/dev/DevToys.Core/FileHelper.cs
  • Dependency direction · Dependency-rule violation: DevToys.Core (Domain) → DevToys.Api (Web) src/app/dev/DevToys.Core/Logging/FileLoggerProvider.cs
  • Dependency direction · Dependency-rule violation: DevToys.Core (Domain) → DevToys.Api (Web) src/app/dev/DevToys.Core/Logging/LoggingBuilderExtensions.cs
  • Dependency direction · Dependency-rule violation: DevToys.Core (Domain) → DevToys.Api (Web) src/app/dev/DevToys.Core/Mef/MefComposer.cs
  • Dependency direction · Dependency-rule violation: DevToys.Core (Domain) → DevToys.Api (Web) src/app/dev/DevToys.Core/Mef/MefProvider.cs
  • Dependency direction · Dependency-rule violation: DevToys.Core (Domain) → DevToys.Api (Web) src/app/dev/DevToys.Core/Mef/RecursiveDirectoryCatalog.cs
  • Dependency direction · Dependency-rule violation: DevToys.Core (Domain) → DevToys.Api (Web) src/app/dev/DevToys.Core/OSHelper.cs
  • Dependency direction · Dependency-rule violation: DevToys.Core (Domain) → DevToys.Api (Web) src/app/dev/DevToys.Core/Properties/AdditionGlobalUsings.cs
  • Dependency direction · Dependency-rule violation: DevToys.Core (Domain) → DevToys.Api (Web) src/app/dev/DevToys.Core/Settings/PredefinedSettings.cs
  • Dependency direction · Dependency-rule violation: DevToys.Core (Domain) → DevToys.Api (Web) src/app/dev/DevToys.Core/Settings/SettingsProvider.cs
  • Dependency direction · Dependency-rule violation: DevToys.Core (Domain) → DevToys.Api (Web) src/app/dev/DevToys.Core/Tools/GuiToolInstance.cs
  • Dependency direction · Dependency-rule violation: DevToys.Core (Domain) → DevToys.Api (Web) src/app/dev/DevToys.Core/Tools/GuiToolProvider.cs
  • Dependency direction · Dependency-rule violation: DevToys.Core (Domain) → DevToys.Api (Web) src/app/dev/DevToys.Core/Tools/Metadata/DataTypeDetectorMetadata.cs
  • Dependency direction · Dependency-rule violation: DevToys.Core (Domain) → DevToys.Api (Web) src/app/dev/DevToys.Core/Tools/Metadata/GuiToolGroupMetadata.cs
  • Dependency direction · Dependency-rule violation: DevToys.Core (Domain) → DevToys.Api (Web) src/app/dev/DevToys.Core/Tools/Metadata/GuiToolMetadata.cs
  • Dependency direction · Dependency-rule violation: DevToys.Core (Domain) → DevToys.Api (Web) src/app/dev/DevToys.Core/Tools/Metadata/LanguageServiceMetadata.cs
  • Dependency direction · Dependency-rule violation: DevToys.Core (Domain) → DevToys.Api (Web) src/app/dev/DevToys.Core/Tools/Metadata/ResourceAssemblyIdentifierMetadata.cs
  • Dependency direction · Dependency-rule violation: DevToys.Core (Domain) → DevToys.Api (Web) src/app/dev/DevToys.Core/Tools/SmartDetectionService.cs
  • Dependency direction · Dependency-rule violation: DevToys.Core (Domain) → DevToys.Api (Web) src/app/dev/DevToys.Core/Tools/ViewItems/GroupViewItem.cs
  • Dependency direction · Dependency-rule violation: DevToys.Core (Domain) → DevToys.Api (Web) src/app/dev/DevToys.Core/Tools/ViewItems/GuiToolViewItem.cs
  • Dependency direction · Dependency-rule violation: DevToys.Core (Domain) → DevToys.Api (Web) src/app/dev/DevToys.Core/Web/WebClientService.cs
  • Outbound HTTP resilience · Outbound HTTP without resilience src/app/dev/DevToys.Core/Web/WebClientService.cs
  • Visual & motion safety · Focus outline removed in CSS without a :focus replacement src/app/dev/DevToys.Blazor/Components/Text/TextBox/TextBox.razor.scss
  • Visual & motion safety · Focus outline removed in CSS without a :focus replacement src/app/dev/DevToys.Blazor/Components/Text/MonacoEditor/MonacoEditor.razor.scss
  • Visual & motion safety · Focus outline removed in CSS without a :focus replacement src/app/dev/DevToys.Blazor/Components/Menu/ContextMenu/ContextMenu.razor.scss
  • Visual & motion safety · Focus outline removed in CSS without a :focus replacement src/app/dev/DevToys.Blazor/Components/Menu/ContextMenu/ContextMenu.razor.scss
  • Visual & motion safety · Focus outline removed in CSS without a :focus replacement src/app/dev/DevToys.Blazor/Components/Layout/Popover/Popover.razor.scss
  • Visual & motion safety · Focus outline removed in CSS without a :focus replacement src/app/dev/DevToys.Blazor/Components/Feedback/ProgressRing/ProgressRing.razor.scss
  • Visual & motion safety · Focus outline removed in CSS without a :focus replacement src/app/dev/DevToys.Blazor/Components/Collections/ListBox/ListBoxItem.razor.scss
  • Visual & motion safety · Focus outline removed in CSS without a :focus replacement src/app/dev/DevToys.Blazor/Components/BasicInput/ToggleSwitch/ToggleSwitch.razor.scss
  • Visual & motion safety · Focus outline removed in CSS without a :focus replacement src/app/dev/DevToys.Blazor/Components/BasicInput/RadioButton/RadioButton.razor.scss
  • Visual & motion safety · Focus outline removed in CSS without a :focus replacement src/app/dev/DevToys.Blazor/Components/BasicInput/CheckBox/CheckBox.razor.scss
  • Visual & motion safety · Focus outline removed in CSS without a :focus replacement src/app/dev/DevToys.Blazor/Components/BasicInput/Button/Button.razor.scss
  • Visual & motion safety · Animation without a prefers-reduced-motion guard src/app/dev/DevToys.Blazor/wwwroot/css/devtoys.g.css
  • Visual & motion safety · Animation without a prefers-reduced-motion guard src/app/dev/DevToys.Blazor/wwwroot/css/devtoys.g.css
  • Visual & motion safety · Animation without a prefers-reduced-motion guard src/app/dev/DevToys.Blazor/wwwroot/css/devtoys.g.css
  • Visual & motion safety · Animation without a prefers-reduced-motion guard src/app/dev/DevToys.Blazor/wwwroot/css/devtoys.g.css
  • Visual & motion safety · Animation without a prefers-reduced-motion guard src/app/dev/DevToys.Blazor/wwwroot/css/devtoys.g.css
  • Visual & motion safety · Animation without a prefers-reduced-motion guard src/app/dev/DevToys.Blazor/wwwroot/css/devtoys.g.css
  • Visual & motion safety · Animation without a prefers-reduced-motion guard src/app/dev/DevToys.Blazor/wwwroot/css/devtoys.g.css
  • Visual & motion safety · Animation without a prefers-reduced-motion guard src/app/dev/DevToys.Blazor/wwwroot/css/devtoys.g.css
  • Visual & motion safety · Animation without a prefers-reduced-motion guard src/app/dev/DevToys.Blazor/wwwroot/css/devtoys.g.css
  • Visual & motion safety · Animation without a prefers-reduced-motion guard src/app/dev/DevToys.Blazor/wwwroot/css/devtoys.g.css
  • Visual & motion safety · Animation without a prefers-reduced-motion guard src/app/dev/DevToys.Blazor/wwwroot/css/devtoys.g.css
  • Visual & motion safety · Animation without a prefers-reduced-motion guard src/app/dev/DevToys.Blazor/wwwroot/css/devtoys.g.css
  • Visual & motion safety · Animation without a prefers-reduced-motion guard src/app/dev/DevToys.Blazor/wwwroot/css/devtoys.g.css
  • Visual & motion safety · Animation without a prefers-reduced-motion guard src/app/dev/DevToys.Blazor/wwwroot/css/devtoys.g.css
  • Visual & motion safety · Animation without a prefers-reduced-motion guard src/app/dev/DevToys.Blazor/wwwroot/css/devtoys.g.css
  • Visual & motion safety · Animation without a prefers-reduced-motion guard src/app/dev/DevToys.Blazor/wwwroot/css/devtoys.g.css
  • Visual & motion safety · Animation without a prefers-reduced-motion guard src/app/dev/DevToys.Blazor/wwwroot/css/devtoys.g.css
  • Visual & motion safety · Animation without a prefers-reduced-motion guard src/app/dev/DevToys.Blazor/wwwroot/css/devtoys.g.css

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

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

  • Dependency Hygiene · Vulnerable: SixLabors.ImageSharp
  • Dependency Hygiene · Deprecated: xunit
  • Dependency Hygiene · Prerelease dependency: System.CommandLine
  • Supply-chain Provenance & Signing REDACTED
  • Async correctness · Sync-over-async (deadlock risk) src/app/dev/platforms/desktop/DevToys.CLI/Program.cs
  • Cancellation propagation · Async method without CancellationToken: OpenMenuAsync src/app/dev/DevToys.Blazor/Components/Menu/ContextMenu/ContextMenu.razor.cs
  • Cancellation propagation · Async method without CancellationToken: CloseMenuAsync src/app/dev/DevToys.Blazor/Components/Menu/ContextMenu/ContextMenu.razor.cs
  • Cancellation propagation · Async method without CancellationToken: SetEventListenersAsync src/app/dev/DevToys.Blazor/Components/Text/MonacoEditor/MonacoEditorBase.cs
  • Cancellation propagation · Async method without CancellationToken: EventCallbackAsync src/app/dev/DevToys.Blazor/Components/Text/MonacoEditor/MonacoEditorBase.cs
  • Cancellation propagation · Async method without CancellationToken: CreateMonacoEditorInstanceAsync src/app/dev/DevToys.Blazor/Components/Text/MonacoEditor/MonacoEditorHelper.cs
  • Cancellation propagation · Async method without CancellationToken: CreateMonacoEditorDiffInstanceAsync src/app/dev/DevToys.Blazor/Components/Text/MonacoEditor/MonacoEditorHelper.cs
  • Cancellation propagation · Async method without CancellationToken: GetOptionsAsync src/app/dev/DevToys.Blazor/Components/Text/MonacoEditor/RicherMonacoEditorBase.cs
  • Cancellation propagation · Async method without CancellationToken: GetOptionAsync src/app/dev/DevToys.Blazor/Components/Text/MonacoEditor/RicherMonacoEditorBase.cs
  • Cancellation propagation · Async method without CancellationToken: DeltaDecorationsAsync src/app/dev/DevToys.Blazor/Components/Text/MonacoEditor/RicherMonacoEditorBase.cs
  • Cancellation propagation · Async method without CancellationToken: SetLanguageAsync src/app/dev/DevToys.Blazor/Components/Text/MonacoEditor/RicherMonacoEditorBase.cs
  • Cancellation propagation · Async method without CancellationToken: UpdateOptionsAsync src/app/dev/DevToys.Blazor/Components/Text/MonacoEditor/RicherMonacoEditorBase.cs
  • Cancellation propagation · Async method without CancellationToken: UpdateOptionsAsync src/app/dev/DevToys.Blazor/Components/Text/MonacoEditor/RicherMonacoEditorDiffBase.cs
  • Cancellation propagation · Async method without CancellationToken: UpdateContextMenuAsync src/app/dev/DevToys.Blazor/Components/Text/TextBox/TextBox.razor.cs
  • Cancellation propagation · Async method without CancellationToken: OnCutAsync src/app/dev/DevToys.Blazor/Components/Text/TextBox/TextBox.razor.cs
  • Cancellation propagation · Async method without CancellationToken: OnCopyAsync src/app/dev/DevToys.Blazor/Components/Text/TextBox/TextBox.razor.cs
  • Cancellation propagation · Async method without CancellationToken: OnPasteAsync src/app/dev/DevToys.Blazor/Components/Text/TextBox/TextBox.razor.cs
  • Cancellation propagation · Async method without CancellationToken: OnSelectAllAsync src/app/dev/DevToys.Blazor/Components/Text/TextBox/TextBox.razor.cs
  • Cancellation propagation · Async method without CancellationToken: GetSelectionAsync src/app/dev/DevToys.Blazor/Components/Text/TextBox/TextBox.razor.cs
  • Cancellation propagation · Async method without CancellationToken: UIMultiLineTextInput_TextChanged src/app/dev/DevToys.Blazor/Components/UIElements/UIDiffTextInputPresenter.razor.cs
  • Cancellation propagation · Async method without CancellationToken: UIDiffTextInput_RightTextChanged src/app/dev/DevToys.Blazor/Components/UIElements/UIDiffTextInputPresenter.razor.cs
  • Cancellation propagation · Async method without CancellationToken: UIMultiLineTextInput_IsReadOnlyChanged src/app/dev/DevToys.Blazor/Components/UIElements/UIDiffTextInputPresenter.razor.cs
  • Cancellation propagation · Async method without CancellationToken: UIDiffTextInput_InlineModeChanged src/app/dev/DevToys.Blazor/Components/UIElements/UIDiffTextInputPresenter.razor.cs
  • Cancellation propagation · Async method without CancellationToken: UIMultiLineTextInput_TextChanged src/app/dev/DevToys.Blazor/Components/UIElements/UIMultiLineTextInputPresenter.razor.cs
  • Cancellation propagation · Async method without CancellationToken: UIMultiLineTextInput_SyntaxColorizationLanguageNameChanged src/app/dev/DevToys.Blazor/Components/UIElements/UIMultiLineTextInputPresenter.razor.cs
  • Cancellation propagation · Async method without CancellationToken: UIMultiLineTextInput_IsReadOnlyChanged src/app/dev/DevToys.Blazor/Components/UIElements/UIMultiLineTextInputPresenter.razor.cs
  • Cancellation propagation · Async method without CancellationToken: UIMultiLineTextInput_SelectionChanged src/app/dev/DevToys.Blazor/Components/UIElements/UIMultiLineTextInputPresenter.razor.cs
  • Cancellation propagation · Async method without CancellationToken: ApplyAllDecorationsAsync src/app/dev/DevToys.Blazor/Components/UIElements/UIMultiLineTextInputPresenter.razor.cs
  • Cancellation propagation · Async method without CancellationToken: CreateModelDeltaDecorationAsync src/app/dev/DevToys.Blazor/Components/UIElements/UIMultiLineTextInputPresenter.razor.cs
  • Cancellation propagation · Async method without CancellationToken: LoadFileAsync src/app/dev/DevToys.Blazor/Components/UIElements/UITextInputWrapper.razor.cs
  • Cancellation propagation · Async method without CancellationToken: FocusOnTextEditorAsync src/app/dev/DevToys.Blazor/Components/UIElements/UITextInputWrapper.razor.cs
  • Cancellation propagation · Async method without CancellationToken: UpdateWebViewContentAsync src/app/dev/DevToys.Blazor/Components/UIElements/UIWebViewPresenter.razor.cs
  • Cancellation propagation · Async method without CancellationToken: InvokeVoidWithErrorHandlingAsync src/app/dev/DevToys.Blazor/Core/Extensions/IJSRuntimeExtensions.cs
  • Cancellation propagation · Async method without CancellationToken: InvokeVoidWithErrorHandlingAsync src/app/dev/DevToys.Blazor/Core/Extensions/IJSRuntimeExtensions.cs
  • Cancellation propagation · Async method without CancellationToken: SubscribeAsync src/app/dev/DevToys.Blazor/Core/Services/DocumentEventService.cs
  • Cancellation propagation · Async method without CancellationToken: UnsubscribeAsync src/app/dev/DevToys.Blazor/Core/Services/DocumentEventService.cs
  • Cancellation propagation · Async method without CancellationToken: RegisterCallBackAsync src/app/dev/DevToys.Blazor/Core/Services/DocumentEventService.cs
  • Cancellation propagation · Async method without CancellationToken: ImportThirdPartyFontsAsync src/app/dev/DevToys.Blazor/Core/Services/FontService.cs
  • Cancellation propagation · Async method without CancellationToken: GetFontDefinitionsAsync src/app/dev/DevToys.Blazor/Core/Services/FontService.cs
  • Cancellation propagation · Async method without CancellationToken: GetFontDefinitionsAsync src/app/dev/DevToys.Blazor/Core/Services/FontService.cs
  • Cancellation propagation · Async method without CancellationToken: GenerateCssForFontAsync src/app/dev/DevToys.Blazor/Core/Services/FontService.cs
  • Cancellation propagation · Async method without CancellationToken: ConvertFontToBase64Async src/app/dev/DevToys.Blazor/Core/Services/FontService.cs
  • Cancellation propagation · Async method without CancellationToken: RegisterLanguageAsync src/app/dev/DevToys.Blazor/Core/Services/MonacoLanguageService.cs
  • Cancellation propagation · Async method without CancellationToken: UpdateFragmentAsync src/app/dev/DevToys.Blazor/Core/Services/PopoverHandler.cs
  • Cancellation propagation · Async method without CancellationToken: Initialize src/app/dev/DevToys.Blazor/Core/Services/PopoverHandler.cs
  • Cancellation propagation · Async method without CancellationToken: Detach src/app/dev/DevToys.Blazor/Core/Services/PopoverHandler.cs
  • Cancellation propagation · Async method without CancellationToken: InitializeIfNeeded src/app/dev/DevToys.Blazor/Core/Services/PopoverService.cs
  • Cancellation propagation · Async method without CancellationToken: Unregister src/app/dev/DevToys.Blazor/Core/Services/PopoverService.cs
  • Cancellation propagation · Async method without CancellationToken: ViewModel_CheckForExtensionUpdateRequested src/app/dev/DevToys.Blazor/Pages/Index.razor.cs
  • Cancellation propagation · Async method without CancellationToken: ShowFirstStartAndOrWhatsNewDialogsAsync src/app/dev/DevToys.Blazor/Pages/Index.razor.cs
  • Cancellation propagation · Async method without CancellationToken: RunOnUIThreadAsync src/app/dev/platforms/desktop/DevToys.Windows/Core/Helpers/ThreadHelper.cs
  • Cancellation propagation · Async method without CancellationToken: RunOnUIThreadAsync src/app/dev/platforms/desktop/DevToys.Windows/Core/Helpers/ThreadHelper.cs
  • Cancellation propagation · Async method without CancellationToken: NotifyContentUpdatedAsync src/app/dev/platforms/desktop/DevToys.MacOS/Controls/BlazorWebView/StaticContentHotReloadManager.cs
  • Cancellation propagation · Async method without CancellationToken: GetClipboardDataAsync src/app/dev/platforms/desktop/DevToys.MacOS/Core/Clipboard.cs
  • Cancellation propagation · Async method without CancellationToken: GetClipboardTextAsync src/app/dev/platforms/desktop/DevToys.MacOS/Core/Clipboard.cs
  • Cancellation propagation · Async method without CancellationToken: GetClipboardFilesAsync src/app/dev/platforms/desktop/DevToys.MacOS/Core/Clipboard.cs
  • Cancellation propagation · Async method without CancellationToken: GetClipboardImageAsync src/app/dev/platforms/desktop/DevToys.MacOS/Core/Clipboard.cs
  • Cancellation propagation · Async method without CancellationToken: SetClipboardImageAsync src/app/dev/platforms/desktop/DevToys.MacOS/Core/Clipboard.cs
  • Cancellation propagation · Async method without CancellationToken: SetClipboardFilesAsync src/app/dev/platforms/desktop/DevToys.MacOS/Core/Clipboard.cs
  • Cancellation propagation · Async method without CancellationToken: SetClipboardTextAsync src/app/dev/platforms/desktop/DevToys.MacOS/Core/Clipboard.cs
  • Cancellation propagation · Async method without CancellationToken: GetClipboardFilesInternalAsync src/app/dev/platforms/desktop/DevToys.MacOS/Core/Clipboard.cs
  • Cancellation propagation · Async method without CancellationToken: GetImageFromClipboardInternalAsync src/app/dev/platforms/desktop/DevToys.MacOS/Core/Clipboard.cs
  • Cancellation propagation · Async method without CancellationToken: PickSaveFileAsync src/app/dev/platforms/desktop/DevToys.MacOS/Core/FileStorage.cs
  • Cancellation propagation · Async method without CancellationToken: PickOpenFileAsync src/app/dev/platforms/desktop/DevToys.MacOS/Core/FileStorage.cs
  • Cancellation propagation · Async method without CancellationToken: PickOpenFilesAsync src/app/dev/platforms/desktop/DevToys.MacOS/Core/FileStorage.cs
  • Cancellation propagation · Async method without CancellationToken: PickFolderAsync src/app/dev/platforms/desktop/DevToys.MacOS/Core/FileStorage.cs
  • Cancellation propagation · Async method without CancellationToken: RunOnUIThreadAsync src/app/dev/platforms/desktop/DevToys.MacOS/Core/Helpers/ThreadHelper.cs
  • Cancellation propagation · Async method without CancellationToken: RunOnUIThreadAsync src/app/dev/platforms/desktop/DevToys.MacOS/Core/Helpers/ThreadHelper.cs
  • Cancellation propagation · Async method without CancellationToken: UpdateSystemSettingsAndApplyThemeAsync src/app/dev/platforms/desktop/DevToys.MacOS/Core/ThemeListener.cs
  • Cancellation propagation · Async method without CancellationToken: ShowAsync src/app/dev/platforms/desktop/DevToys.MacOS/Views/MainWindow.cs
  • Cancellation propagation · Async method without CancellationToken: CutInWebViewAsync src/app/dev/platforms/desktop/DevToys.MacOS/Views/MainWindow.cs
  • Cancellation propagation · Async method without CancellationToken: CopyInWebViewAsync src/app/dev/platforms/desktop/DevToys.MacOS/Views/MainWindow.cs
  • Cancellation propagation · Async method without CancellationToken: PasteInWebViewAsync src/app/dev/platforms/desktop/DevToys.MacOS/Views/MainWindow.cs
  • Cancellation propagation · Async method without CancellationToken: SelectAllInWebViewAsync src/app/dev/platforms/desktop/DevToys.MacOS/Views/MainWindow.cs
  • Cancellation propagation · Async method without CancellationToken: SetPositionAndSizeAsync src/app/dev/platforms/desktop/DevToys.MacOS/Views/MainWindow.cs
  • Cancellation propagation · Async method without CancellationToken: SendMessagePump src/app/dev/platforms/desktop/DevToys.Linux/Components/BlazorWebView/BlazorWebViewManager.cs
  • Cancellation propagation · Async method without CancellationToken: NotifyContentUpdatedAsync src/app/dev/platforms/desktop/DevToys.Linux/Components/BlazorWebView/StaticContentHotReloadManager.cs
  • Cancellation propagation · Async method without CancellationToken: PickOpenFileInternalAsync src/app/dev/platforms/desktop/DevToys.Linux/Core/FileStorage.cs
  • Cancellation propagation · Async method without CancellationToken: Bash src/build/Restore/RestoreTask.cs
  • Exception handling · Swallowed exception (empty catch) src/app/dev/DevToys.Core/Logging/FileLoggerProvider.cs
  • Exception handling · Swallowed exception (caught, then discarded) src/app/dev/DevToys.Blazor/BuiltInDataTypeDetectors/Base64TextDataTypeDetector.cs
  • Exception handling · Swallowed exception (caught, then discarded) src/app/dev/platforms/desktop/DevToys.Windows/Core/Clipboard.cs
  • Outbound HTTP resilience · Outbound HTTP without resilience
Rebuild cost: about €47,000 · Estimate
Cost to rebuild€15,000 to €78,000, for 258 to 826 hours of work, about 0.3 person-years for one engineer
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 42. 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: 42,184 lines of product code
Comment linesThe estimate prices 33,144 lines. Comment lines count towards the size of 42,184 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
Resolve the 1 No ADRs found finding(s) in ADR Quality.
Raises the score by about 3 points · Low effort · ADR Quality
2
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.
Raises the score by about 4 points · Medium effort · Security & performance tooling
3
Add a test runner (vitest / jest / playwright) and eslint and `tsc --noEmit` as package.json scripts and run them in CI.
Raises the score by about 4 points · Medium effort · Tooling

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 €47,000 to build again, about 0.3 person-years of work. Its weakest lens is Production Readiness, at 35 (Weak). Production Readiness is about whether the product is ready to run in production and to change without breaking. Because the weakest lens counts most in the score, work on Production Readiness also moves the score most.
Based on: the rebuild estimate · the Production Readiness grade · how much each lens counts
What to do: Start with the Production Readiness actions in Top priorities.
If you do one thing first · First action
Resolve the 1 No ADRs found finding(s) in ADR Quality. Of all the actions in this report, it raises the score most for the work it takes: about 3 points for low effort, because it clears the 1 ADR Quality findings. 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 DevToys.Api Api DevToys.Blazor Blazor DevToys.Blazor->DevToys.Api DevToys.Business Business DevToys.Blazor->DevToys.Business DevToys.Core Core DevToys.Blazor->DevToys.Core DevToys.Localization Localization DevToys.Blazor->DevToys.Localization DevToys.Business->DevToys.Api DevToys.Business->DevToys.Core DevToys.Business->DevToys.Localization DevToys.CLI CLI DevToys.CLI->DevToys.Api DevToys.CLI->DevToys.Core DevToys.Core->DevToys.Api DevToys.Core->DevToys.Localization DevToys.Linux Linux DevToys.Linux->DevToys.Blazor DevToys.Linux->DevToys.Localization DevToys.Localization->DevToys.Api DevToys.MacOS MacOS DevToys.MacOS->DevToys.Blazor DevToys.MacOS->DevToys.Localization DevToys.Windows Windows DevToys.Windows->DevToys.Blazor DevToys.Windows->DevToys.Localization _build _build

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.

76 modules, with 100 dependencies between them. 3 loops run through 10 of the modules, marked above the diagonal.

The table shows the 40 modules with the most connections; 36 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 Api2 CLI.Core3 Core.Version4 Core.Web5 Blazor.BuiltInDataTypeDetectors6 Blazor.BuiltInGroups7 Blazor.BuiltInTools8 Blazor.BuiltInTools.ExtensionsManager9 Blazor.BuiltInTools.Settings10 Blazor.BuiltInTools.SupportDevelopment11 Blazor.Components.Monaco.Editor12 Blazor.Core13 Blazor.Core.Extensions14 Business.Models15 CLI16 CLI.Core.FileStorage17 Core18 Core.Mef19 Core.Settings20 Core.Tools.Metadata21 Blazor.Components.Monaco22 CLI.Core.Settings23 Core.Tools.ViewItems24 Blazor.Components.Monaco.Languages25 Core.Tools26 Blazor.Components.UIElements27 Business.Services28 Core.Models29 Blazor.Core.Services30 Business.ViewModels31 Blazor.Components32 Linux.Core33 MacOS.Core34 Windows.Core35 Blazor.Pages.Dialogs36 Linux37 Windows.Controls38 Blazor.Pages39 Windows40 Blazor.Pages.SubPages
1 Api
2 CLI.Core
3 Core.Version
4 Core.Web
5 Blazor.BuiltInDataTypeDetectors26
6 Blazor.BuiltInGroups7
7 Blazor.BuiltInTools2
8 Blazor.BuiltInTools.ExtensionsManager82
9 Blazor.BuiltInTools.Settings9
10 Blazor.BuiltInTools.SupportDevelopment2
11 Blazor.Components.Monaco.Editor181
12 Blazor.Core2
13 Blazor.Core.Extensions1
14 Business.Models1
15 CLI51
16 CLI.Core.FileStorage2
17 Core111
18 Core.Mef2
19 Core.Settings6
20 Core.Tools.Metadata5
21 Blazor.Components.Monaco11
22 CLI.Core.Settings11
23 Core.Tools.ViewItems241
24 Blazor.Components.Monaco.Languages1
25 Core.Tools1263
26 Blazor.Components.UIElements44522124
27 Business.Services11
28 Core.Models2
29 Blazor.Core.Services92111
30 Business.ViewModels311361
31 Blazor.Components25531310
32 Linux.Core1112
33 MacOS.Core1
34 Windows.Core101211
35 Blazor.Pages.Dialogs16
36 Linux31111
37 Windows.Controls11
38 Blazor.Pages7111115152
39 Windows111
40 Blazor.Pages.SubPages2112271
Uses a module listed above itPart of a loopThe module itself
1 Api2 CLI.Core3 Core.Version4 Core.Web5 Blazor.BuiltInDataTypeDetectors6 Blazor.BuiltInGroups7 Blazor.BuiltInTools8 Blazor.BuiltInTools.ExtensionsManager9 Blazor.BuiltInTools.Settings10 Blazor.BuiltInTools.SupportDevelopment11 Blazor.Components.Monaco.Editor12 Blazor.Core13 Blazor.Core.Extensions14 Business.Models15 CLI16 CLI.Core.FileStorage17 Core18 Core.Mef19 Core.Settings20 Core.Tools.Metadata21 Blazor.Components.Monaco22 CLI.Core.Settings23 Core.Tools.ViewItems24 Blazor.Components.Monaco.Languages25 Core.Tools26 Blazor.Components.UIElements27 Business.Services28 Core.Models29 Blazor.Core.Services30 Business.ViewModels31 Blazor.Components32 Linux.Core33 MacOS.Core34 Windows.Core35 Blazor.Pages.Dialogs36 Linux37 Windows.Controls38 Blazor.Pages39 Windows40 Blazor.Pages.SubPagesApi1CLI.Core2Core.Version3Core.Web4Blazor.BuiltInDataTypeDetectors5Blazor.BuiltInGroups6Blazor.BuiltInTools7Blazor.BuiltInTools.ExtensionsManager8Blazor.BuiltInTools.Settings9Blazor.BuiltInTools.SupportDevelopment10Blazor.Components.Monaco.Editor11Blazor.Core12Blazor.Core.Extensions13Business.Models14CLI15CLI.Core.FileStorage16Core17Core.Mef18Core.Settings19Core.Tools.Metadata20Blazor.Components.Monaco21CLI.Core.Settings22Core.Tools.ViewItems23Blazor.Components.Monaco.Languages24Core.Tools25Blazor.Components.UIElements26Business.Services27Core.Models28Blazor.Core.Services29Business.ViewModels30Blazor.Components31Linux.Core32MacOS.Core33Windows.Core34Blazor.Pages.Dialogs35Linux36Windows.Controls37Blazor.Pages38Windows39Blazor.Pages.SubPages40267282921812115121112651111241112634452212411292111311361255313101112110121116311111171111151521112112271+36 more modules (most-connected shown)

At a glance — Code Health · 58% · Adequate ·

The Good
D3 · .NET / C# God Classes 9.2 D4 · .NET / C# Code Duplication 9.4 D17 · .NET / C# Explicit Debt 8.4 D18 · .NET / C# Solution Shape 10.0 GD1 · Repo Unfinished & placeholder code 10.0 IC1 · Repo Incompleteness & stubs 8.5 R10 · React / TS Code Duplication 8.4 R2 · React / TS Cyclomatic Complexity 9.8 R3 · React / TS Large Files 7.8 R7 · React / TS Dead Code 10.0 X12 · Repo Unreachable branch 10.0 X13 · Repo Undrained process stream 10.0 X16 · Repo Unfloored truncation loop 10.0 X19 · Repo Unrestored process-global state 10.0 X20 · Repo Mistyped argument guard 10.0 X21 · Repo Side-effecting pattern guard 10.0 X22 · Repo Contradicted release guard 10.0 X23 · Repo Unguarded diagnostic materialisation 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 X5 · Repo Nullable reference types 8.5
The Bad
D1 · .NET / C# Cyclomatic Complexity 6.6 D2 · .NET / C# Cognitive Complexity 5.9 R1 · React / TS Type Safety 5.0 X1 · Repo Async correctness 5.4 X18 · Repo Disposal-pattern correctness 7.0 X4 · Repo Structured logging 6.8
The Ugly
X2 · Repo Cancellation propagation 4.4 X3 · Repo Exception handling 5.0

At a glance — Architecture · 72% · Strong ·

The Good
D5 · .NET / C# Coupling 9.3 D6 · .NET / C# Cohesion (LCOM4) 9.6 D26 · .NET / C# Project Cohesion 8.3 D27 · .NET / C# Navigability 9.7 D35 · .NET / C# Change Coupling 10.0 AX1 · Repo Captive dependencies 10.0 AX10 · Repo Code composition 7.4 AX3 · Repo Project dependency cycles 10.0 AX5 · Repo Architecture & structure 10.0 AX6 · Repo Interface segregation 9.9 AX8 · Repo Test isolation 10.0 R9 · React / TS Circular Imports 10.0
The Bad
AX4 · Repo Dependency direction 5.7
The Ugly
AX2 · Repo Stateful singletons 4.8

At a glance — Maturity · 46% · Weak · gated by D34, M2 ·

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

At a glance — Readiness · 35% · Weak · gated by R6, P3, P7 ·

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 P2 · Repo Observability 7.0 P6 · Repo Release Hygiene 8.0 R8 · React / TS Dependency Hygiene 10.0
The Bad
P10 · Repo Library API & versioning 6.0
The Ugly
P3 · Repo Security & performance tooling 0.0 P7 · Repo Outbound HTTP resilience 3.0 R6 · React / TS Tooling 0.0

At a glance — Security · 85% · Adequate · gated by D30 ·

The Good
D28 · .NET / C# Secrets (history) 10.0 D37 · .NET / C# Vulnerability-disclosure Policy 10.0 D43 · .NET / C# Malicious Dependencies 10.0 D44 · .NET / C# Platform End-of-Life 10.0 X14 · Repo Bypassable address classification 10.0 X15 · Repo Unvalidated length from an untrusted reader 10.0 X17 · Repo Uncapped recursion over a caller-supplied document 10.0
The Bad
D29 · .NET / C# Static Analysis (SAST) 6.8
The Ugly
D30 · .NET / C# Dependency Vulnerabilities 2.8 X24 · Repo Document value interpolated into markup unescaped 1.8

At a glance — Accessibility · 38% · Weak · gated by AC4, AC6 ·

The Good
AC2 · Repo Forms & labels 10.0
The Bad
AC5 · Repo ARIA correctness 6.4
The Ugly
AC1 · Repo Text alternatives 4.3 AC3 · Repo Page structure 4.1 AC4 · Repo Keyboard semantics 3.0 AC6 · Repo Visual & motion safety 2.1 AC7 · Repo A11y enforcement 4.0

At a glance — Performance · 70% · Adequate ·

The Good
PF2 · Repo Allocation hygiene 10.0
The Bad
PF1 · Repo Benchmark discipline 6.0 PF3 · Repo Async & latency hygiene 6.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 — Injection15High / Critical
A03:2025 — Software Supply Chain Failures13High / Critical
A08:2025 — Software or Data Integrity Failures1Medium

Roadmap

First, integrate automated security scanning and a comprehensive test, lint, and type-checking suite into the CI pipeline to prevent regressions and ensure code quality. Next, address the 162 orphaned files, prioritizing those in core components like FileStorage and Clipboard, to maintain codebase freshness. Finally, establish a structured documentation process by creating an ADR folder to record significant design decisions and their consequences, ensuring architectural knowledge is preserved and accessible.

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

Do thisHelpsEffortDimension
Resolve the 1 No ADRs found finding(s) in ADR Quality.+2.5 ptsLowADR Quality
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.+3.7 ptsMediumSecurity & performance tooling
Add a test runner (vitest / jest / playwright) and eslint and `tsc --noEmit` as package.json scripts and run them in CI.+3.7 ptsMediumTooling
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.+2.6 ptsMediumArchitecture documentation
Give every outbound call a bound the caller can rely on: set an explicit `HttpClient.Timeout` (or pass a `CancellationToken` from a `CancellationTokenSource` with a deadline) and flow the caller's own `CancellationToken` through, so a slow endpoint fails fast instead of hanging.+2.5 ptsMediumOutbound HTTP resilience
Keep a visible focus style (don't remove the outline without a replacement), guard animation with prefers-reduced-motion, and raise low-contrast colour pairs to at least 4.5:1.+2.3 ptsMediumVisual & motion safety
Resolve the 1 NoWarnInCsproj finding(s) in Explicit Debt — start with _build.csproj.+1.2 ptsLowExplicit Debt
Make custom controls keyboard-operable (role + tabindex + key handler), drop positive tabindex, and give anchors a real href.+1.8 ptsMediumKeyboard semantics

File quality

Per-file score 0–10 — a quality signature. Of 78 files carrying findings, judged against the Production bar: 1% slop · 62% mixed · 37% near-clean.

FileScoreBandWorst signal
REDACTED0.8SlopStatic Analysis (SAST): High: REDACTED
REDACTED4.8MixedStatic Analysis (SAST): High: REDACTED
src/app/dev/platforms/desktop/DevToys.Linux/Components/BlazorWebView/BlazorWebViewManager.cs4.9MixedExplicit Debt: EmptyCatchBlock
src/app/dev/platforms/desktop/DevToys.Windows/Controls/MicaWindowWithOverlay.xaml.cs4.9MixedExplicit Debt: EmptyCatchBlock
REDACTED5.1MixedDependency Vulnerabilities: Critical CVE: REDACTED
src/app/dev/DevToys.Core/Logging/FileLoggerProvider.cs5.5MixedExplicit Debt: EmptyCatchBlock
src/app/dev/DevToys.Core/Tools/GuiToolInstance.cs5.8MixedExplicit Debt: EmptyCatchBlock
src/app/dev/DevToys.Core/Tools/GuiToolProvider.cs6.0MixedExplicit Debt: TodoComment
src/build/Build.cs6.0MixedExplicit Debt: HackComment
src/app/dev/platforms/desktop/DevToys.CLI/Core/OneOfParser.cs6.1MixedExplicit Debt: EmptyCatchBlock
src/app/dev/DevToys.Blazor/Components/Text/MonacoEditor/MonacoEditorBase.cs6.1MixedExplicit Debt: EmptyCatchBlock
REDACTED6.4MixedStatic Analysis (SAST): Medium: REDACTED
src/app/dev/DevToys.Blazor/Core/Services/MonacoLanguageService.cs6.4MixedExplicit Debt: EmptyCatchBlock
src/app/dev/DevToys.Core/FileHelper.cs6.4MixedExplicit Debt: EmptyCatchBlock
src/app/dev/DevToys.Blazor/Components/UIElements/UITextInputWrapper.razor.cs6.6MixedExplicit Debt: TodoComment
src/app/dev/DevToys.Blazor/wwwroot/js/require.js7.0MixedCyclomatic Complexity: require.newContext (cyclomatic 84)
src/app/dev/platforms/desktop/DevToys.MacOS/Core/WindowService.cs7.0MixedCode Duplication: Duplicated block (8 lines × 2)
src/app/dev/DevToys.Blazor/wwwroot/js/simplebar-modified.js7.0MixedCyclomatic Complexity: (anonymous)::(anonymous)::SimpleBarCore::drag (cyclomatic 31)
src/app/dev/platforms/desktop/DevToys.Linux/Components/BlazorWebView/BlazorWebView.cs7.1MixedCode Duplication: Duplicated block (43–44 lines × 2)
src/app/dev/DevToys.Blazor/Assets/javascript/popover.ts7.1MixedCyclomatic Complexity: Popover.placePopover (cyclomatic 67)

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

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

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

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

Could not be resolved — 6

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

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

What we checked — 90 dimensions across the health lenses
D1D2D3D4D5D6D9D10D13D14D15D17D18D19D20D21D24D26D27D28D29D30D34D35D37D43D44AC1AC2AC3AC4AC5AC6AC7AX1AX10AX2AX3AX4AX5AX6AX8GD1IC1M1M2M3M4P1P10P2P3P6P7PF1PF2PF3R1R10R2R3R6R7R8R9X1X12X13X14X15X16X17X18X19X2X20X21X22X23X24X25X26X27X28X29X3X30X32X4X5

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, 616 of 647 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 01a165f3-1b36-7c02-8973-49eb0f43c2e6.

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.

  • D8 Code Coverage — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Coverage NOT MEASURED: the analyzer environment could not build/run the test suite (a target framework / SDK band or targeting pack the analyzer image doesn't carry). This is OUR limitation, not a defect in the repo — coverage is excluded from the score rather than counted as a near-zero. We track the analyzer-image gap so it can be closed; in the meantime, no coverage collector was found in your CI either, so there is no existing report to hand us — add a collector to your test run and commit (or publish into the working tree) its Cobertura/OpenCover/lcov output, and real coverage will be read. You can widen what we reach: optional: add a coverage collector to your test run and commit (or publish into the working tree) its Cobertura/OpenCover/lcov output, and the real number is read on the next scan.
  • 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: /usr/share/dotnet/sdk/10.0.400/Sdks/Microsoft.NET.Sdk/targets/Microsoft.NET.Sdk.ImportWorkloads.targets(38,5): error NETSDK1147: To build this project, the following workloads must be installed: macos wasm-tools-net8 [src/app/dev/platforms/desktop….
  • 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 (80 contributor(s) across 1084 commit(s) sampled, automation and bot accounts excluded). One of them holds 82% of the history; the other 79 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 'src/app/dev/platforms/desktop/DevToys.Windows/DevToys.Windows.csproj' with message: Project file must include the .NET Framework assembly 'PresentationCore, PresentationFramework' in the reference list.
  • 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 310 error(s), and the diagnostics it printed were: TS2503: Build:Cannot find namespace 'DotNet'.; TS6053: Build:File 'src/app/dev/DevToys.Blazor/node_modules/monaco-editor/monaco.d.ts' not found.; TS2503: Build:Cannot find namespace 'monaco'.; TS2304: Build:Cannot find name 'monaco'.; TS6053: Build:File 'src/app/dev/DevToys.Blazor/node_modules/split-grid/index.d.ts' not found.. 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 (37,853 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"]`.
  • D28 Secrets (history) — 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. D28's config-credential rule (WD-SECRET-0002) parses each committed `.json` config as a document and reads credential-named values; `src/app/dev/platforms/desktop/DevToys.MacOS/Assets.xcassets/Contents.json` did not parse (JSON5, a template, several concatenated documents), so a credential bound there is UNMEASURED by that rule. gitleaks still scanned the same files as text.
  • D30 Dependency Vulnerabilities — measured, with a gap in what it reached — This is a true statement about the repository that carries nothing for its owner to act on, so it is reported here rather than as a defect in their code. The scanner produced no output at all, so no dependency was actually scanned. 2 of 3 declared ecosystem(s) (npm,nuget) WERE scanned and every vulnerability they reported is included in this result; REDACTED was not, so this dimension's score covers less than the dependency surface this repository declares, and nothing here is evidence that REDACTED is free of known-vulnerable dependencies.
  • 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. `src/app/dev/DevToys.Blazor/Assets/javascript/monacoEditor.ts`, `src/app/dev/DevToys.Blazor/Assets/javascript/popover.ts`, `src/app/dev/platforms/desktop/DevToys.Linux/Components/BlazorWebView/BlazorWebView.cs`, `src/app/dev/platforms/desktop/DevToys.MacOS/Controls/BlazorWebView/BlazorWKWebView.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.
  • D43 Malicious Dependencies — measured, with a gap in what it reached — This is a true statement about the repository that carries nothing for its owner to act on, so it is reported here rather than as a defect in their code. The scanner produced no output at all, so no dependency was actually scanned. 1 of 2 declared ecosystem(s) (npm) WERE scanned and every vulnerability they reported is included in this result; REDACTED was not, so this dimension's score covers less than the dependency surface this repository declares, and nothing here is evidence that REDACTED is free of known-vulnerable dependencies.
  • AC6 Visual & motion safety — 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. 5 further occurrence(s) are not listed individually; the score already reflects all 45.
  • AXB1 Runtime evidence locked — no reproducible boot — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Subject: 73 markup document(s) — HTML, Razor, JSX, Vue, Svelte or server templates. The Runtime Evidence tier boots an app only via docker-compose, an Aspire AppHost, a Dockerfile, an npm dev script, a web service's own toolchain entry point (cargo, go, dotnet, Python, Spring Boot), or an Android app's own Gradle wrapper (run on an emulator); an Apple or Flutter app needs a host it lacks. None applied, so no live runtime a11y/egress/header evidence was collected. You can widen what we reach: add a docker-compose.yml (or an Aspire AppHost) that brings the app up with its dependencies. Watchdog then boots it in an isolated sandbox and gathers real runtime evidence — you change nothing in your pipeline (no CI step, no SDK).
  • 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.
  • X2 Cancellation propagation — measured, with a gap in what it reached — Watchdog measured this, but not all of it. What it did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. 155 further occurrence(s) are not listed individually; the score already reflects all 195.
  • X8 JS interop contract — 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. 47 further occurrence(s) are not listed individually; the score already reflects all 87.
  • Package restore incomplete — third-party types were unresolved in part of the solution — NuGet restore did not complete for src/app/dev/platforms/desktop/DevToys.MacOS/DevToys.MacOS.csproj, so those projects were analysed with framework references only: every check keyed on a third-party type saw an error type there and reported nothing. Findings on those projects are a lower bound; run `dotnet restore` on them and rescan.

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").
  • D30 Dependency Vulnerabilities: CVE matching depends on accurate package/version metadata and on the advisory databases — a vulnerability with no published advisory, or in code not declared as a dependency, is not seen. Coverage needs a RESOLVED graph: an unpinned requirements.txt, or a pom without a resolved build, yields partial coverage rather than a clean verdict. An ecosystem the analyzer cannot scan is reported as unmeasured, never as clean.
  • D34 Knowledge Freshness: Freshness is decayed commit RECENCY, not comprehension — code read often but rarely committed reads as orphaned, and stable code that genuinely needs no changes is penalised the same as forgotten code; bot/squash commits distort it like the bus factor.
  • D35 Change Coupling: Change coupling is co-change in COMMITS — files split across separate commits, or coupled only through a shared config/build step, read as uncoupled, and a sweeping commit (rename/format) is excluded so it doesn't couple everything. It shows that files change together, not WHY: a high coupling can be a healthy cohesive pair as readily as a hidden leak.
  • D43 Malicious Dependencies: Only packages some vulnerability database has already NAMED as malicious are seen — a compromise published in the last hours, or never reported at all, is invisible here, and this dimension reading 10 is not evidence that a dependency is trustworthy. There is no typosquat or dependency-confusion analysis: a package nobody has reported is simply absent from the feeds. Coverage is the dependency scan's: an ecosystem that could not be scanned is disclosed as unmeasured, never as clean.
  • D44 Platform End-of-Life: The support table is FROZEN, so it goes out of date by losing RECALL: a release that ended support after the table was written is missed until the table is refreshed, and this dimension reading 10 is not evidence that a platform is current. Only platforms the repository DECLARES in a place this pass reads are seen — a runtime named only in a Dockerfile (D31's subject), in a CI workflow (D29's), or in a file this pass does not parse (go.mod, a Gemfile ruby directive) is invisible here, which is why a repository declaring none of them abstains rather than scoring. Only frameworks with a PUBLISHED support policy are tracked: React, Flask and Express publish none, so their age cannot be judged and their absence from a report is not a statement that they are supported.
  • AC1 Text alternatives: Alt-text is detected structurally — the scan sees that an alternative EXISTS, not whether it meaningfully describes the image, and decorative-vs-missing is judged by attribute shape; runtime-injected images and a non-role=img decorative svg are out of scope. This is accessibility readiness, never a WCAG conformance claim.
  • AC2 Forms & labels: Label association is read from static markup — a label wired up at runtime (JS-set aria-labelledby, framework-injected ids) reads as missing, a present label says nothing about whether its text is correct. A known UI-library field component (e.g. a JSX <TextField>) is now checked conservatively — flagged only when it carries NO label/aria-label/aria-labelledby/id/name — but wrapper/context-labelled libraries (Chakra/Radix FormControl+FormLabel) aren't statically visible (possible false positive) and non-JSX lowercased components are still skipped. A click handler on a plain element is now asked for a name too (it is a control the author declared), but the subtree test that answers it is deliberately generous: any DYNAMIC text expression in the subtree counts as a name, so an icon chosen by a ternary ({cond ? <IconA/> : <IconB/>}) reads as named, and a glyph component from a library the icon-import list does not know still names its parent. A clean result is "no unlabelled control found", not a labelling proof.
  • AC3 Page structure: Page structure is read from the static markup tree — landmarks, headings and lang injected at runtime aren't seen, heading ORDER is checked structurally (not against the rendered visual hierarchy), and lang/title/main fire only on full documents, never partials, and the data-table check sees header-cell presence (a <th> exists), not whether each header correctly associates with its cells. Static readiness, not conformance.
  • AC4 Keyboard semantics: Keyboard semantics are inferred from markup attributes — interactivity wired purely in script, focus managed at runtime, and component-level handlers are invisible. A clean result means "no static keyboard-trap shape", not a keyboard-operability proof.
  • AC5 ARIA correctness: ARIA correctness is checked against the static role/attribute shape — roles/attributes set dynamically aren't seen, a valid role says nothing about whether it matches the element's real behaviour, and required-state checks are suppressed when a JSX spread could supply them. The two-branch toggle check (a control whose state is conveyed only by which of two mutually exclusive branches renders) reads CONDITIONALS THAT ARE ATTRIBUTES — Vue v-if/v-else/v-show and Alpine x-if/x-show — so the same toggle written as a Svelte {#if} block or a JSX ternary is control flow the markup model never projects as a branch and is not seen at all.
  • AC6 Visual & motion safety: Contrast and motion safety are PARTIAL by construction — literal colours (hex/rgb/hsl/named) in inline styles, in-repo <style> blocks, in-repo .css files, var() tokens, Tailwind neutral utilities and CSS-in-JS top-level declarations are read (same-rule/same-element colour+background pairs only); computed/runtime/theme colour, external-CDN stylesheets, CSS-in-JS dynamic (${…}) and nested-selector colours, cross-element pairs and image contrast stay out of reach, so a clean result is bounded by what the static CSS itself shows.
  • AC7 A11y enforcement: Enforcement is scored from in-repo config/CI evidence only — an a11y gate enforced in external tooling with no in-repo trace can't be credited, and a configured linter is presence, not proof the rules actually run or block a merge.
  • AX10 Code composition: Role is inferred from namespace/folder convention, not semantics — a domain concept living in a folder named "Services" reads as application, and the split is lines-of-code, not business value. The business-logic-share score is a SOFT, FLOORED signal: it contributes to the Architecture lens but is floored at the Critical gate, so an infrastructure-heavy design (a gateway, an ETL, a driver) is legitimately low without being nuked to zero.
  • M4 Documentation accuracy: Onboarding quality is an LLM read of the docs/setup present — it cannot run the onboarding or measure how long a real new joiner takes; the verdict is sampled and advisory.
  • 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.6 / 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.6 / 10 · rule-coverage 100% · ceiling Prevented

20 method(s) exceeded the cyclomatic complexity threshold of 15; the worst was require.newContext at 84. A further 2 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 MonacoEditor.setEventListener at 32 — 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: src/app/dev/DevToys.Blazor/Assets/javascript/monacoEditor.ts (MonacoEditor.setEventListener at 32), src/app/dev/DevToys.Blazor/Components/UIElements/UIImageViewerPresenter.razor.cs (UIImageViewerPresenter.DisplayImageAsync at 20). 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.

(anonymous)::(anonymous)::SimpleBarCore::drag (cyclomatic 31) · ×5src/app/dev/DevToys.Blazor/wwwroot/js/simplebar-modified.js:899
require.newContext::q (cyclomatic 27) · ×2src/app/dev/DevToys.Blazor/wwwroot/js/require.js:5
require.newContext (cyclomatic 84)src/app/dev/DevToys.Blazor/wwwroot/js/require.js:5
Popover.placePopover (cyclomatic 67)src/app/dev/DevToys.Blazor/Assets/javascript/popover.ts:328
RicherMonacoEditorBase.EventCallbackAsync (cyclomatic 38)src/app/dev/DevToys.Blazor/Components/Text/MonacoEditor/RicherMonacoEditorBase.cs:326

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

What to do

  1. Bring the 4 bodies over 30 down to 30 or less in Cyclomatic Complexity — start with require.newContext (cyclomatic 84), Popover.placePopover (cyclomatic 67), RicherMonacoEditorBase.EventCallbackAsync (cyclomatic 38). — This score is capped by its worst body, so a finding fixed alone moves it by almost nothing — the next one down takes its place. Refactoring these 4 together lifts Cyclomatic Complexity from 6.6 to about 7.7/10, projected with the scoring formula itself and assuming each lands exactly at 30; a cleaner split scores higher.
  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 Complexity5.9 / 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 5.9 / 10 · rule-coverage 100% · ceiling Prevented

34 method(s) exceeded the cognitive complexity threshold of 15; the worst was Popover.placePopover at 113.

(anonymous)::(anonymous)::SimpleBarCore::drag (cognitive 33) · ×4src/app/dev/DevToys.Blazor/wwwroot/js/simplebar-modified.js:899
newContext::check (cognitive 75) · ×3src/app/dev/DevToys.Blazor/wwwroot/js/require.js:5
Popover.placePopover (cognitive 113)src/app/dev/DevToys.Blazor/Assets/javascript/popover.ts:328
require.newContext (cognitive 83)src/app/dev/DevToys.Blazor/wwwroot/js/require.js:5
Popover.callback (cognitive 49)src/app/dev/DevToys.Blazor/Assets/javascript/popover.ts:72

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

What to do

  1. Bring the 6 bodies over 30 down to 30 or less in Cognitive Complexity — start with Popover.placePopover (cognitive 113), require.newContext (cognitive 83), newContext::check (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 6 together lifts Cognitive Complexity from 5.9 to about 7.3/10, projected with the scoring formula itself and assuming each lands exactly at 30; a cleaner split scores higher.
  2. Enforce Cognitive Complexity in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.

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

D3 · God Classes9.2 / 10Stronggated by 8 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.2 / 10 · rule-coverage 100% · ceiling Prevented

8 god class(es) detected.

TooManyMethods: MonacoEditor · ×6src/app/dev/DevToys.Blazor/Assets/javascript/monacoEditor.ts:14
ClassTooLong: MonacoEditorsrc/app/dev/DevToys.Blazor/Assets/javascript/monacoEditor.ts:14
FileTooLong: javascript/monacoEditor.tssrc/app/dev/DevToys.Blazor/Assets/javascript/monacoEditor.ts

What to do

  1. Resolve the 6 TooManyMethods finding(s) in God Classes — start with monacoEditor.ts, TextModel.cs, RicherMonacoEditorBase.cs. — One of this dimension's main actionable groups (6 warning-level).
  2. Resolve the 1 ClassTooLong finding(s) in God Classes — start with monacoEditor.ts. — One of this dimension's main actionable groups (1 warning-level).
  3. Resolve the 1 FileTooLong finding(s) in God Classes — start with monacoEditor.ts. — 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.4 / 10Stronggated by 46 serious findings✓ Tool-verified

What it measures: Copy-pasted code that should be shared instead.

Method: Code duplication via token-stream sliding windows with type-aware normalization (locals masked, type names preserved), density-scored per KLoC of production code. Deterministic.

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

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

Duplicated block (11 lines × 2) · ×4src/app/dev/platforms/desktop/DevToys.Linux/Core/ThemeListener.cs:100
Duplicated block (15 lines × 2) · ×3src/app/dev/DevToys.Api/Core/ObservableHashSet.cs:248
Duplicated block (12 lines × 2) · ×3src/app/dev/platforms/desktop/DevToys.MacOS/AppDelegate.cs:134
Duplicated block (10 lines × 2) · ×3src/build/Build.cs:299
Duplicated block (17 lines × 2) · ×2src/app/dev/DevToys.Blazor/Components/Text/MonacoEditor/Monaco/Editor/EditorUpdateOptions.cs:10

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

What to do

  1. Resolve the 4 Duplicated block (11 lines × 2) finding(s) in Code Duplication — start with ThemeListener.cs, IUIStack.cs, REDACTED. — One of this dimension's main actionable groups (4 warning-level).
  2. Resolve the 3 Duplicated block (15 lines × 2) finding(s) in Code Duplication — start with ObservableHashSet.cs, FileStorage.cs, BlazorWebView.cs. — One of this dimension's main actionable groups (3 warning-level).
  3. Resolve the 3 Duplicated block (12 lines × 2) finding(s) in Code Duplication — start with AppDelegate.cs, MonacoEditor.razor.cs, BlazorWebView.cs. — One of this dimension's main actionable groups (3 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.3 / 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.3 / 10 · rule-coverage 100% · ceiling Prevented

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

Off the main sequence: DevToys.Localizationsrc/app/dev/DevToys.Localization/DevToys.Localization.csproj:1

What to do

  1. Resolve the 1 Off the main sequence finding(s) in Coupling — start with DevToys.Localization.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.6 / 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.6 / 10 · rule-coverage 100% · ceiling Verified

4 of 109 classes have LCOM4 above 3.

Low cohesion: WindowService (LCOM4 6) · ×4src/app/dev/platforms/desktop/DevToys.MacOS/Core/WindowService.cs:8

What to do

  1. Resolve the 4 Low cohesion finding(s) in Cohesion (LCOM4) — start with WindowService.cs, SettingsGuiTool.cs, GuiToolProvider.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

90 test methods: 90 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, 1 mock references across 90 tests.

Mock framework: Moq

✓ On the Gold path — maintain.

Detailed fixes: d10_recommendation.md · top locations in Appendix A, every location in findings.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 7 packages use a banned license. ★ DEPTH: every package graded here is one this repository's MSBuild projects declare as a direct `PackageReference` (32 declared), and nothing beyond them was reached — this is the DECLARATION-SITE set, NOT the transitive closure. .NET has no lockfile a checkout is guaranteed to carry and this pass grades an unrestored tree, so a banned licence that only a direct dependency's OWN dependencies pull in is outside this verdict, exactly as the JVM arm's declaration-site verdict is.

✓ 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 Debt8.4 / 10Adequategated by 25 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 8.4 / 10 · rule-coverage 100% · ceiling Prevented

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

EmptyCatchBlock · ×24src/app/dev/DevToys.Blazor/Components/JSStyledComponentBase.cs:67
NoWarnInCsproj — 6 warning codes suppressed in one elementsrc/build/_build.csproj:8
TodoComment · ×20src/app/dev/DevToys.Blazor/BuiltInTools/SupportDevelopment/SupportDevelopmentGuidTools.cs:22
HackComment · ×2src/app/dev/DevToys.Core/OSHelper.cs:49
BarePragmaDisablesrc/app/dev/DevToys.Blazor/Components/Text/MonacoEditor/RicherMonacoEditorDiffBase.cs:212

What to do

  1. Resolve the 24 EmptyCatchBlock finding(s) in Explicit Debt — start with FileLoggerProvider.cs (4), GuiToolInstance.cs (3), MonacoLanguageService.cs (2). — One of this dimension's main actionable groups (24 issue-level).
  2. Resolve the 1 NoWarnInCsproj finding(s) in Explicit Debt — start with _build.csproj. — One of this dimension's main actionable groups (1 issue-level).
  3. Resolve the 20 TodoComment finding(s) in Explicit Debt — start with UITextInputWrapper.razor.cs (4), UIInfoBarPresenter.razor.cs (2), UIImageViewerPresenter.razor.cs (2). — One of this dimension's main actionable groups (20 warning-level).
  4. Enforce Explicit Debt in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.

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

D18 · Solution 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

12 projects, 600 source files, 40077 hand-written lines of code (37853 production / 2224 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 2770 generated (machine-written code — designer, scaffolded and tool-emitted files — excluded from quality), 23 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.) Measured across 4 solutions loaded as one workspace: `src/DevToys-Windows.sln`, `src/DevToys-MacOS.sln`, `src/DevToys-Linux.sln`, `src/Build.sln`.

✓ On the Gold path — maintain.

Detailed fixes: d18_recommendation.md.

D19 · Documentation QualityAdequate◐ Sampled · advisory

What it measures: Whether the project's documentation is clear, complete, and useful.

Method: Judged by language model at low temperature (0.0-0.1) on a deterministic doc sample (READMEs plus first 25 architecture docs), with two-pass stability filtering. Advisory, sampled.

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

The repository's root README is clear and well-structured (Introduction, Rate on Microsoft Store as of 5/7/2024, Contribute, Privacy Policy, Third-Party Softwares, License, Special Thanks), but the chocolatey/README.md and assets/font/README.md are directory-level documentation that do not describe what the repository is doing — they document only their own directories (Chocolatey packaging, font glyph editing). The READMEs all have a strong overview section; none of them lack installation, usage, or contribution guidance.

XML-doc coverage: DevToys.CLI · ×11src/app/dev/platforms/desktop/DevToys.CLI/DevToys.CLI.csproj

What to do

  1. Improve Documentation Quality — currently 6.0/10. — The repository's root README is clear and well-structured (Introduction, Rate on Microsoft Store as of 5/7/2024, Contribute, Privacy Policy, Third-Party Softwares, License, Special Thanks), but the chocolatey/README.md and assets/font/README.md are directory-level documentation that do not describe what the repository is doing — they document only their own directories (Chocolatey packaging, font glyph editing). The READMEs all have a strong overview section; none of them lack installation, usage, or contribution guidance.

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

83 valuable / 0 redundant across 200 sampled comments.

✓ On the Gold path — maintain.

Detailed fixes: d24_recommendation.md.

D26 · Project Cohesion8.3 / 10Strong✓ 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 8.3 / 10 · rule-coverage 100% · ceiling Documented

1 of 12 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.7 / 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.7 / 10 · rule-coverage 100% · ceiling Documented

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

✓ On the Gold path — maintain.

Detailed fixes: d27_recommendation.md.

D28 · Secrets (history)10.0 / 10Exemplary○ Nothing flagged

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 10.0 / 10 · rule-coverage 100% · ceiling Documented

gitleaks scanned the full history AND the current working tree and found no secrets.

✓ On the Gold path — maintain.

Detailed fixes: d28_recommendation.md.

D29 · Static Analysis (SAST)6.8 / 10Adequate✓ 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 6.8 / 10 · rule-coverage 100% · ceiling Documented

15 finding(s): 0 critical, 11 high, 4 medium, 0 low. 10 unpinned-GitHub-Actions row(s) are reported here but scored by D36 (supply-chain provenance), which measures that posture as `pinned_actions` — one pinning decision is charged once, not once per lens. semgrep hit a parse error in 4 file(s) — `src/app/dev/DevToys.Blazor/Assets/javascript/monacoEditor.ts` (lines 19–21, lines 26–33, line 56, …), `src/app/dev/DevToys.Blazor/Assets/javascript/popover.ts` (line 61, line 62, line 67, …), `src/app/dev/platforms/desktop/DevToys.Linux/Components/BlazorWebView/BlazorWebView.cs` (line 29, line 33, lines 35–39, …), `src/app/dev/platforms/desktop/DevToys.MacOS/Controls/BlazorWebView/BlazorWKWebView.cs` (line 22, line 25, line 32, …) — 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.

REDACTED
REDACTED
REDACTED
REDACTED
REDACTED

What to do

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

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

D30 · Dependency Vulnerabilities2.8 / 10Weak✓ Tool-verified

What it measures: Whether any dependency has a known published vulnerability (CVE), direct or transitive, in ANY ecosystem the repository declares — Dart pub, Elixir and Erlang via Hex, Go modules, Java and Kotlin via Maven/Gradle, JavaScript/npm, .NET/NuGet, PHP/Composer, Python/PyPI, RubyGems, Rust/Cargo and Swift.

Method: Dependency-CVE scan across every ecosystem the repository declares, scored ONCE. Three sources are unioned and deduplicated by advisory identity (rule id + alias closure, CVE<->GHSA) scoped to package+version, keeping the worst severity: `osv-scanner --recursive` over REDACTED.dev for Dart pub, Elixir/Hex (and Erlang, whose `rebar.lock` syft first converts to a CycloneDX SBOM the scanner reads, with rows attributed back to the lock), Go, Java and Kotlin via Maven/Gradle (and Scala, whose sbt build's pinned direct declarations are written into a CycloneDX SBOM the scanner reads, with rows attributed back to the build file), npm, PHP/Composer, Python/PyPI, RubyGems, Rust/Cargo and Swift; `trivy fs --scanners vuln` for npm lockfiles; and `dotnet list package --vulnerable --include-transitive` for NuGet (with per-advisory collapse of the project x target-framework fan-out), plus a DECLARED-dependency arm that resolves a published gem's gemspec against rubygems.org where no Gemfile.lock is committed. `SeverityScore(c,h,m,l, normalizer 8.0)`. NotApplicable only when NO ecosystem is readable; if any applicable ecosystem could not be scanned the findings are REPORTED and the score is withheld. Supersedes the npm and OSV arms, retired 2026-09-05.

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

12 finding(s): 1 critical, 9 high, 2 medium, 0 low. Partial dependency scan: 2 of 3 declared ecosystem(s) were scanned (npm,nuget), and the findings above are real and complete for them. REDACTED was not scanned (REDACTED: the scanner produced no output at all, so no dependency was actually scanned), so this is not the whole dependency surface and the result is reported at reduced confidence.

REDACTED
REDACTED
REDACTED
REDACTED

What to do

  1. Resolve the 9 High CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (2). — One of this dimension's main actionable groups (9 issue-level).
  2. Resolve the 1 Critical CVE finding(s) in Dependency Vulnerabilities — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
  3. Resolve the 2 Medium CVE finding(s) in Dependency Vulnerabilities. — One of this dimension's main actionable groups (2 warning-level).

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

D34 · Knowledge Freshness0.1 / 10Critical✓ 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 0.1 / 10 · rule-coverage 100% · ceiling Documented

165 of 167 significant source file(s) are orphaned — their living knowledge has decayed to nothing, so no one currently understands them. The largest is src/app/dev/DevToys.Core/Tools/GuiToolProvider.cs. Counted over 167 of the 538 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.

Orphaned file · ×162src/app/dev/DevToys.Blazor/Components/Text/MonacoEditor/Monaco/Editor/EditorOptions.cs:1
Most significant orphaned file · ×3src/app/dev/DevToys.Core/Tools/GuiToolProvider.cs:1
Concentrated knowledge decay

What to do

  1. Resolve the 162 Orphaned file finding(s) in Knowledge Freshness — start with FileStorage.cs (4), Clipboard.cs (3), ThemeListener.cs (3). — One of this dimension's main actionable groups (162 recommendation-level).
  2. Resolve the 3 Most significant orphaned file finding(s) in Knowledge Freshness — start with GuiToolProvider.cs, RicherMonacoEditorBase.cs, TextModel.cs. — One of this dimension's main actionable groups (3 recommendation-level).
  3. Resolve the 1 Concentrated knowledge decay finding(s) in Knowledge Freshness. — One of this dimension's main actionable groups (1 recommendation-level).

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.

D37 · Vulnerability-disclosure Policy10.0 / 10Exemplary✓ Tool-verified

What it measures: Whether the repository publishes a coordinated-vulnerability-disclosure policy (SECURITY.md or security.txt) with a reporting contact, so finders know how to report a vulnerability. Presence of a policy file with a contact, not whether the policy is adequate or honoured.

Method: Vulnerability-disclosure policy read deterministically from the repo: a SECURITY.md (root/.github/docs) or .well-known/security.txt / security.txt, regex-checked for a reporting contact (email / URL / mailto). Present + contact → 10; present without a contact → 4; NotApplicable when no policy file exists (it may live off-repo). Detects the policy file's presence + contact, not its adequacy.

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

A vulnerability-disclosure policy (SECURITY.md) is published with a reporting contact.

✓ On the Gold path — maintain.

Detailed fixes: d37_recommendation.md.

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

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

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

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

No known-vulnerable dependencies in the 1 ecosystem(s) that were scanned (npm). Partial dependency scan: 1 of 2 declared ecosystem(s) were scanned (npm), and the findings above are real and complete for them. REDACTED was not scanned (REDACTED: the scanner produced no output at all, so no dependency was actually scanned), so this is not the whole dependency surface and the result is reported at reduced confidence.

REDACTED

✓ On the Gold path — maintain.

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

D44 · Platform End-of-Life10.0 / 10Exemplary✓ Tool-verified

What it measures: Whether anyone still ships security patches for the platform this repository RUNS ON — the runtime it pins and the framework majors its own constraints hold it to. Separate from D12 because the question differs: a current Django on an end-of-life Python is perfectly up to date and completely unsupported, and the fix is a migration rather than a version bump. What the repository says it merely SUPPORTS is never charged.

Method: End-of-life PLATFORM read from the repository's own declarations and graded against a FROZEN, dated table of vendor support dates — no network, no feed, no API, so this dimension answers identically inside a closed scan fence. Two subjects: a RUNTIME the project pins (a single or all-end-of-life TargetFramework, a .nvmrc or .python-version, a requires-python CAP) and a FRAMEWORK major a dependency constraint cannot move off (a caret, tilde or exact version; `vue@^2.7.16` pins Vue 2). A FLOOR is deliberately never charged — `requires-python = ">=3.8"` states what a package SUPPORTS, not what it runs on — and a multi-target project is charged only when EVERY target is out of support. Runtime 4.0/product capped 8.0, framework 1.5 capped 4.5. The table is safe to freeze because a statement about support that ended in the past cannot become false: it loses recall as it ages, never precision, and a test asserts every entry predates the freeze date. Disjoint from D31 (a container image's OS layer) and D29 (the toolchain a CI workflow installs). Abstains when the repository declares no platform this pass reads — never scores it clean.

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

0 end-of-life runtime(s) and 0 end-of-life framework(s), read from 12 platform declaration(s) and 0 dependency declaration(s). This dimension reads what the repository says about ITSELF — a pinned target framework, a version file, a capped requires-python, a Rust toolchain pin, a framework major a constraint cannot move off. A FLOOR is deliberately never charged: `requires-python = ">=3.8"` states what the package SUPPORTS, not what it runs on, and a well-maintained library declares exactly that while running its own CI on a current release. The end-of-life facts are FROZEN and dated, so this dimension needs no network and answers identically inside a closed scan fence; as the table ages it loses recall and never precision, because a statement about support that ended in the past cannot become false. The OS layer of a container image is D31's question and the toolchain a CI workflow installs is D29's; this row is neither.

✓ On the Gold path — maintain.

Detailed fixes: d44_recommendation.md.

Frontend & cross-cutting dimensions

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

AC1 · Text alternatives4.3 / 10Weak✓ Tool-verified

Other · Accessibility — Whether non-text content carries a text alternative — img/area/input[type=image] have alt, a meaningful svg has a title or aria-label, video has a captions track, and object/embed/canvas have a name or fallback content. Static markup readiness, not a WCAG conformance claim.

Method: Static markup-model scan: every img/area/input[type=image] checked for alt, svg[role=img] for a title/aria-label, video for a captions <track>. Components skipped, spreads suppressed. Deterministic, hard fact per element.

Coverage: Population: image/media elements — img, area, input[type=image], svg, video, object, embed, canvas — across the PARSED MARKUP files only (.html/.htm/.cshtml/.razor/.vue/.svelte/.jsx/.tsx); components, hidden subtrees and dynamic-attribute elements are skipped. Markup built in script — tagged-template (html`…`) UIs and hyperscript DOM factories — is NOT read by any producer, so it contributes no element to this population; where such a frontend is present the card discloses it as an analyzer gap rather than scoring around it.

  • An image with no alt (and no aria-label/aria-labelledby) is unreadable to assistive tech. Add alt — alt="" if it's purely decorative. — src/app/dev/DevToys.Blazor/Components/UIElements/UITextInputWrapper.razor:120

What to do

  • Add a text alternative — alt on images (alt="" for purely decorative ones), a title or aria-label on meaningful svg, an aria-label or inner fallback content on canvas, and a captions <track> on video.
AC2 · Forms & labels10.0 / 10Exemplary○ Nothing flagged

Other · Accessibility — Whether form controls have a programmatic label (an associated label, aria-label or aria-labelledby), buttons have text, links have an accessible name, a click handler on a plain element names the control it declares, fieldsets have a non-empty legend, known UI-library field components carry a label prop, and a placeholder isn't used as the only label. Static markup readiness, not a WCAG conformance claim.

Method: Static markup-model scan: inputs/selects/textareas checked for an associated label[for]/wrapping label/aria-label/aria-labelledby (per document), buttons for accessible text, fieldsets for a legend; placeholder-only labelling flagged. Deterministic, hard fact per control.

Coverage: Population: form controls, buttons, links, fieldsets and known UI-library field components in the PARSED MARKUP files only (.html/.htm/.cshtml/.razor/.vue/.svelte/.jsx/.tsx); components, hidden subtrees and spread/dynamic-attribute elements are skipped, so a control whose label arrives through a spread or a runtime expression is deliberately not judged. Markup built in script — tagged-template (html`…`) UIs and hyperscript DOM factories — is not read at all.

AC3 · Page structure4.1 / 10Weak✓ Tool-verified

Other · Accessibility — Whether pages declare a language (well-formed BCP-47) and a non-empty title, expose exactly one main landmark and a sane heading order with non-empty headings, keep zoom enabled, title their iframes, give data tables header cells, and avoid meta-refresh. Static markup readiness, not a WCAG conformance claim.

Method: Static markup-model scan: html lang, document <title>, a main landmark and heading order on full documents only, plus zoom-disabling viewports, untitled iframes and meta-refresh anywhere. Deterministic, per structural checkpoint.

Coverage: Population: the PARSED MARKUP documents (.html/.htm/.cshtml/.razor/.vue/.svelte/.jsx/.tsx). The page-level checks — lang, title, single main landmark — fire ONCE PER FULL DOCUMENT (an <html> root) and never on a partial or component fragment, so a repo of fragments is assessed only on the per-element checks (heading order, table headers, iframe titles, meta-refresh, zoom). Markup built in script — tagged-template (html`…`) UIs and hyperscript DOM factories — is not read at all.

  • An iframe with no title (or an empty one) is announced only as "frame". Add a non-empty title describing its content, or an aria-label. — src/app/dev/DevToys.Blazor/Components/UIElements/UIWebViewPresenter.razor:32
  • A route with no <PageTitle> gives no name in the tab, history or screen-reader page list — the host's <HeadOutlet /> projects whatever title the routed component supplies, and this one supplies none. Add a <PageTitle> to this component (a literal <title> in the host document would be overwritten by the outlet). — src/app/dev/DevToys.Blazor/Pages/Index.razor:12
  • user-scalable=no/0 or a maximum-scale below 2 stops low-vision users zooming to 200%. Remove the zoom restriction from the viewport meta. — src/app/dev/platforms/desktop/DevToys.Windows/wwwroot/index.html:5

What to do

  • Declare <html lang>, a document <title> and a <main> landmark, keep headings in order, leave zoom enabled, title iframes and drop meta-refresh.
AC4 · Keyboard semantics3.0 / 10Weak✓ Tool-verified

Other · Accessibility — Whether interactive behaviour is keyboard-reachable — no click handler on a non-interactive element lacking a role, tabindex and key handler, no element the repo's own CSS styles `cursor: pointer` without giving it any of the three, no unfocusable element whose only binding is a mouse enter/leave pair or a double-click, no positive tabindex, no href-less anchor, no placeholder-href (#/javascript) link acting as a button. Static markup readiness, not a WCAG conformance claim.

Method: Static markup-model scan: click handlers on non-interactive elements lacking role+tabindex+key handler, positive tabindex values, and href-less anchors. Components skipped, spreads suppressed. Deterministic, hard fact per element.

Coverage: Population: elements that pose a keyboard-semantics question, in the PARSED MARKUP files only (.html/.htm/.cshtml/.razor/.vue/.svelte/.jsx/.tsx) — a non-natively-interactive element carrying a click handler, a double-click or hover enter/leave binding, a pointer-only gesture on a tabindex="0" element, or `cursor: pointer` from the repo's own CSS; an href-less or placeholder-href (#, javascript:) anchor; and any element with a positive tabindex. Natively interactive elements used correctly (<button>, <a href>, form controls) are NOT in the population — there is nothing to judge — so a page of nothing but correct controls gives AC4 nothing to measure. Keyboard reachability is judged from the markup, never from a rendered page. ★ An interactive element declared in a tagged-template (html`…`) or hyperscript frontend is NOT in this population — no producer reads either — so an empty population is reported as an analyzer gap, never as "this repository has no interactive elements".

  • This <div> binds mouse-enter and mouse-leave and nothing else — no click, no key handler, no focus handler, and no tabindex="0", so it cannot even take focus. A keyboard user cannot hover, so whatever the pair reveals or highlights is reachable with a mouse only. Bind the same state to focus/blur as well, and add tabindex="0"="0" so the element can receive that focus. — src/app/dev/DevToys.Blazor/Components/Collections/DataGrid/DataGridColumnHeader.razor:12
  • A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabindex="0" + a key handler. — src/app/dev/DevToys.Blazor/Components/Layout/Overlay/Overlay.razor:6
  • An <a> with no href, role or tabindex isn't focusable or keyboard-activatable. Give it a real href, or use a <button> for an action. — src/app/dev/platforms/desktop/DevToys.Windows/wwwroot/index.html:35

What to do

  • Make custom controls keyboard-operable (role + tabindex + key handler), drop positive tabindex, and give anchors a real href.
AC5 · ARIA correctness6.4 / 10Adequate✓ Tool-verified

Other · Accessibility — Whether ARIA is used correctly — valid non-abstract roles, the ARIA state a role requires, valid (non-misspelled) aria-* attribute names, in-enum values for token-typed aria-* attributes, and no aria-hidden on (or wrapping) a focusable element. Static markup readiness, not a WCAG conformance claim.

Method: Static markup-model scan: role values checked against the WAI-ARIA role set (abstract/invalid flagged), required ARIA state for a role, and aria-hidden on a focusable element. Deterministic, role/attribute level.

Coverage: Population: elements in the PARSED MARKUP files (.html/.htm/.cshtml/.razor/.vue/.svelte/.jsx/.tsx) that carry a role or an aria-* attribute; roles and token values are checked against the ARIA enums exhaustively within that set. An expression-valued (dynamic) role or aria-* value is skipped rather than guessed, and markup built in script — tagged-template (html`…`) UIs and hyperscript DOM factories — is not read at all.

  • A plain <div> has the implicit role "generic", which supports no ARIA states, so this aria-expanded is dropped and assistive tech is never told the state at all. Put aria-expanded on the element that owns the behaviour (the button or control the user operates), or give this <div> a role that supports aria-expanded. — src/app/dev/DevToys.Blazor/Components/Layout/Expander/Expander.razor:38

What to do

  • Use valid, non-abstract roles, supply the ARIA state each role requires, and never put aria-hidden on a focusable element.
AC6 · Visual & motion safety2.1 / 10Critical✓ Tool-verified

Other · Accessibility — Whether focus outlines aren't removed without a replacement, motion respects prefers-reduced-motion, and literal CSS colour pairs meet contrast — PARTIAL: inline styles, in-repo <style> blocks, in-repo .css files, var() tokens, Tailwind neutral utilities and CSS-in-JS literals are read (hex/rgb/hsl/named), never computed/runtime/external-CDN colour. Static markup readiness, not a WCAG conformance claim.

Method: Static markup/CSS scan: inline outline:none/0, literal inline colour/background contrast against the 4.5:1 AA floor, and <style>-block animation without a prefers-reduced-motion guard. Deterministic but PARTIAL — only inline styles and in-repo CSS literals are visible.

Coverage: Population: styled elements in the PARSED MARKUP files (.html/.htm/.cshtml/.razor/.vue/.svelte/.jsx/.tsx), plus in-repo <style> blocks, in-repo .css files and CSS-in-JS literals. Colour contrast is computed from LITERAL colour pairs only (hex/rgb/hsl/named, including var() tokens and Tailwind neutral utilities) — computed, runtime-themed and external-CDN colour is never resolved, so this is a partial read of contrast by construction. Markup built in script — tagged-template (html`…`) UIs and hyperscript DOM factories — is not read at all.

  • `.checkbox` sets color: rgb(255, 255, 255) on background-color: rgb(204, 204, 204) — 1.6:1, below the 4.5:1 WCAG AA minimum for normal text. This is a MINIFIED, build-generated sheet — editing the literal here is undone by the next vendor drop or rebuild, so override the rule in your own stylesheet (or fix it upstream / in the source the bundle is built from). — src/app/dev/DevToys.Blazor/wwwroot/css/devtoys.g.css:1
  • `.text-box` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible. — src/app/dev/DevToys.Blazor/Components/Text/TextBox/TextBox.razor.scss:7
  • `.monaco-editor-standalone` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible. — src/app/dev/DevToys.Blazor/Components/Text/MonacoEditor/MonacoEditor.razor.scss:7
  • `.context-menu-list-box .list-box:focus` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible. — src/app/dev/DevToys.Blazor/Components/Menu/ContextMenu/ContextMenu.razor.scss:17
  • `.context-menu-list-box .context-menu-item.selected` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible. — src/app/dev/DevToys.Blazor/Components/Menu/ContextMenu/ContextMenu.razor.scss:39
  • `.popover` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible. — src/app/dev/DevToys.Blazor/Components/Layout/Popover/Popover.razor.scss:2
  • `.progress-ring` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible. — src/app/dev/DevToys.Blazor/Components/Feedback/ProgressRing/ProgressRing.razor.scss:19
  • `.list-box-item` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible. — src/app/dev/DevToys.Blazor/Components/Collections/ListBox/ListBoxItem.razor.scss:11
  • `.toggle-switch` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible. — src/app/dev/DevToys.Blazor/Components/BasicInput/ToggleSwitch/ToggleSwitch.razor.scss:13
  • `.radio-button` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible. — src/app/dev/DevToys.Blazor/Components/BasicInput/RadioButton/RadioButton.razor.scss:12
  • `.checkbox` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible. — src/app/dev/DevToys.Blazor/Components/BasicInput/CheckBox/CheckBox.razor.scss:10
  • `button` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible. — src/app/dev/DevToys.Blazor/Components/BasicInput/Button/Button.razor.scss:13
  • `.combo-box-button .arrow-down-icon` moves (`transition-property: transform`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce. — src/app/dev/DevToys.Blazor/wwwroot/css/devtoys.g.css:1
  • `.drop-down-list-button .arrow-down-icon` moves (`transition-property: transform`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce. — src/app/dev/DevToys.Blazor/wwwroot/css/devtoys.g.css:1
  • `.toggle-switch::before` moves (`transition: transform 167ms ease-in-out,height 167ms cubic-bezier(0,0,0,1),width 167ms cubic-bezier(0,0,0,1),margin 167ms cubic-bezier(0,0,0,1),background 167ms linear`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce. — src/app/dev/DevToys.Blazor/wwwroot/css/devtoys.g.css:1
  • `.list-box-item::before` moves (`transition: transform 167ms cubic-bezier(0,0,0,1)`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce. — src/app/dev/DevToys.Blazor/wwwroot/css/devtoys.g.css:1
  • `.progress-bar.indeterminate .progress-bar-track:first-of-type` moves (`animation: 2s infinite indeterminate-1`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce. — src/app/dev/DevToys.Blazor/wwwroot/css/devtoys.g.css:1
  • `.progress-bar.indeterminate .progress-bar-track:nth-of-type(2)` moves (`animation: 2s infinite indeterminate-2`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce. — src/app/dev/DevToys.Blazor/wwwroot/css/devtoys.g.css:1
  • `.progress-ring.indeterminate circle` moves (`animation: 2s linear infinite progress-ring-indeterminate`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce. — src/app/dev/DevToys.Blazor/wwwroot/css/devtoys.g.css:1
  • `.dialog` moves (`animation: .25s cubic-bezier(.25,.1,.25,1) both dialog-open-animation`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce. — src/app/dev/DevToys.Blazor/wwwroot/css/devtoys.g.css:1
  • `.expander .card[data-expanded=true] .expander-expand-button .font-icon` moves (`transition: transform .2s ease-in-out`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce. — src/app/dev/DevToys.Blazor/wwwroot/css/devtoys.g.css:1
  • `.expander .card.expander-card .expander-expand-button .font-icon` moves (`transition: transform .2s ease-in-out`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce. — src/app/dev/DevToys.Blazor/wwwroot/css/devtoys.g.css:1
  • `.expander .expander-content-anchor` moves (`transition: max-height linear 250ms`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce. — src/app/dev/DevToys.Blazor/wwwroot/css/devtoys.g.css:1
  • `.expander .expander-content-anchor .expander-content` moves (`transition: transform 250ms cubic-bezier(1,1,0,1)`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce. — src/app/dev/DevToys.Blazor/wwwroot/css/devtoys.g.css:1
  • `.expander .expander-content-anchor[aria-expanded=true] .expander-content` moves (`transition: transform 250ms cubic-bezier(0,0,0,1)`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce. — src/app/dev/DevToys.Blazor/wwwroot/css/devtoys.g.css:1
  • `.simplebar-track.simplebar-vertical` moves (`transition: width .2s ease-in-out`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce. — src/app/dev/DevToys.Blazor/wwwroot/css/devtoys.g.css:1
  • `.simplebar-track.simplebar-horizontal` moves (`transition: height .2s ease-in-out`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce. — src/app/dev/DevToys.Blazor/wwwroot/css/devtoys.g.css:1
  • `.nav-bar-root nav.transition` moves (`transition: left .2s ease-in-out,width .2s ease-in-out,max-width .2s ease-in-out,box-shadow .2s ease-in-out`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce. — src/app/dev/DevToys.Blazor/wwwroot/css/devtoys.g.css:1
  • `nav .list-box-item .sidebar-expand-group-button` moves (`transition-property: transform`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce. (×2) — src/app/dev/DevToys.Blazor/wwwroot/css/devtoys.g.css:1, src/app/dev/DevToys.Blazor/Components/Menu/NavBar/NavBarItem.razor.scss:32
  • `.entrance-theme-transition` moves (`animation-name: entrance-theme-transition-key-frames`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce. — src/app/dev/DevToys.Blazor/wwwroot/css/devtoys.g.css:1
  • `div[data-uselessanimations] .entrance-theme-transition` moves (`animation-name: entrance-theme-transition-key-frames`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce. — src/app/dev/DevToys.Blazor/wwwroot/css/devtoys.g.css:1
  • `.hero::before` moves (`animation: 1s cubic-bezier(.7,1,.8,1) forwards hero-bg-scrolling`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce. — src/app/dev/DevToys.Blazor/wwwroot/css/devtoys.g.css:1
  • `.hero::before` moves (`animation: hero-bg-scrolling 1s`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce. — src/app/dev/DevToys.Blazor/Pages/SubPages/ToolGroup.razor.scss:48
  • `.simplebar-track.simplebar-vertical` moves (`transition: width 0.2s ease-in-out`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce. — src/app/dev/DevToys.Blazor/Components/Layout/ScrollViewer/ScrollViewer.razor.scss:229
  • `.simplebar-track.simplebar-horizontal` moves (`transition: height 0.2s ease-in-out`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce. — src/app/dev/DevToys.Blazor/Components/Layout/ScrollViewer/ScrollViewer.razor.scss:243
  • `.dialog` moves (`animation: dialog-open-animation 0.25s cubic-bezier(0.25, 0.1, 0.25, 1) both`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce. — src/app/dev/DevToys.Blazor/Components/Layout/Dialog/Dialog.razor.scss:7
  • `.progress-ring.indeterminate circle` moves (`animation: progress-ring-indeterminate 2s linear infinite`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce. — src/app/dev/DevToys.Blazor/Components/Feedback/ProgressRing/ProgressRing.razor.scss:38
  • `.progress-bar.indeterminate .progress-bar-track:first-of-type` moves (`animation: 2s ease 0s infinite normal none running indeterminate-1`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce. — src/app/dev/DevToys.Blazor/Components/Feedback/ProgressBar/ProgressBar.razor.scss:72
  • `.progress-bar.indeterminate .progress-bar-track:nth-of-type(2)` moves (`animation: 2s ease 0s infinite normal none running indeterminate-2`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce. — src/app/dev/DevToys.Blazor/Components/Feedback/ProgressBar/ProgressBar.razor.scss:79

What to do

  • Keep a visible focus style (don't remove the outline without a replacement), guard animation with prefers-reduced-motion, and raise low-contrast colour pairs to at least 4.5:1.
AC7 · A11y enforcement4.0 / 10Weak✓ Tool-verified

Other · Accessibility — Whether accessibility is ENFORCED in the toolchain — an accessibility checker configured over the markup (an a11y lint rule set, e.g. eslint-plugin-jsx-a11y or vuejs-accessibility where the project lints JavaScript) and an automated accessibility assertion wired into tests or CI (axe/pa11y/Lighthouse or an equivalent) — on the Documented→Verified→Prevented ladder.

Method: Repo config/CI scan: an accessibility checker configured over the markup (an a11y lint rule set such as eslint-plugin-jsx-a11y / vuejs-accessibility where JavaScript is linted) and an automated accessibility assertion in tests or CI (axe/pa11y/Lighthouse or equivalent), graded on the Documented→Verified→Prevented rungs. Deterministic, presence/rung detection.

Coverage: Population: the repository's own tooling configuration — lint config, test and CI files — NOT the markup. It is read for a configured accessibility checker and an automated accessibility assertion (axe/pa11y/Lighthouse, or a native-toolkit equivalent), and it credits an INVOCATION, never a mention: a licence filename, an import comment or a doc reference earns no rung. Enforcement configured entirely outside the repository leaves no evidence here and cannot be credited.

  • No accessibility enforcement found — no a11y linter (an accessibility check that can read your UI — no component framework was detected and your pages are rendered by server-side templates, which neither the JSX/Vue ESLint plugins nor the HTML-template linters can parse; run axe/pa11y over the rendered pages, or assert the accessibility invariants over that rendered HTML in the test suite you already have) and no axe/pa11y/Lighthouse in tests or CI. Start by running that check over your rendered pages in CI. What was searched, so you can tell an absence from a miss: the 73 markup file(s) this pass actually assessed, the linter configuration checked in beside them, and this repository's test and CI files — matched by name against the accessibility checkers this dimension carries. An audit run outside the repository, a hosted scanner, or a check whose name is not one of those, is not seen here.

What to do

  • Enforce accessibility in the toolchain: add an accessibility check that can read your UI — no component framework was detected and your pages are rendered by server-side templates, which neither the JSX/Vue ESLint plugins nor the HTML-template linters can parse; run axe/pa11y over the rendered pages, or assert the accessibility invariants over that rendered HTML in the test suite you already have, then assert with your test runner's axe binding (jest-axe, vitest-axe, cypress-axe or @axe-core/playwright) in tests, then gate axe/pa11y/Lighthouse in CI.
AX1 · Captive dependencies10.0 / 10Exemplary✓ Tool-verified

Other · Architecture — Whether any singleton service captures a scoped/transient dependency — a silent lifetime/threading bug.

Method: Roslyn scan: DI registrations parsed from AddSingleton/Scoped/Transient; each singleton checked for captured shorter-lifetime dependencies. Exhaustive, deterministic.

AX10 · Code composition7.4 / 10Strong✓ Tool-verified

Other · Architecture — How the codebase splits by code ROLE — domain, application, infrastructure, test, generated. The significance map behind the knowledge/coupling weighting, and a DDD signal in its own right: a thin domain core under fat infrastructure is the anemic-domain smell, quantified. How each file's role is decided, because the split is only as good as that: a generated name or a build-output tree makes it Generated, a test project makes it Test, and otherwise the file's NAMESPACE and PATH words are matched against fixed vocabularies in a fixed ORDER — domain, then infrastructure, then application — so a file whose words hit two layers is counted under the earlier one. A production file matching none of them counts as application, so that share reads 'application or unclassified' rather than a measured application layer. Roles come from naming convention, never from what the code does.

Method: Roslyn line-count by code ROLE: every source file classified Domain/Application/Infrastructure/Test/Generated by namespace + path convention (the shared CodeRoleClassifier), then significant lines summed per role. Deterministic; the advisory score is the business-logic (domain+application) share of production code.

Coverage: Population: ALL source files, each bucketed into ONE of five roles (Domain/Application/Infrastructure/Test/Generated) by namespace + path convention — a file whose layer isn't named in the convention falls to Application (the neutral default), and the split is line-count, not semantic depth or business value.

What to do

  • The domain core is a small share of production code, but most of the rest matched no layer vocabulary at all — so this is not yet an anemic-domain finding. The namespace/path convention could not place that code, which makes the composition above a statement about the naming, not about the design. Name the layers (or check that the repository's conventions differ from the ones this check knows) before reading a thin domain into it.
AX2 · Stateful singletons4.8 / 10Weak✓ Tool-verified

Other · Architecture — Whether singleton services avoid mutable shared instance state that concurrent callers would race on.

Method: Roslyn scan: singleton field mutations unguarded by lock or Interlocked, per type; syntax-based guard detection. Deterministic, traceable per field.

  • `WindowService` is a singleton (one shared instance) but mutates instance state outside any lock (_isCompactOverlayMode, _window, _nonCompactOverlayModeWindowState, _compactOverlayModeWindowState; e.g. `_isCompactOverlayMode` at line 30). — src/app/dev/platforms/desktop/DevToys.Windows/Core/WindowService.cs:9

What to do

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

Other · Architecture — Whether the project-reference graph is acyclic (cycles block independent build/deploy and signal eroding boundaries).

Method: Project reference cycles via elementary-DFS over real .csproj references, using the engine shared with D5/D7; cyclic versus acyclic. Exhaustive, deterministic.

  • The namespaces DevToys.Core.Tools ↔ DevToys.Core.Tools.ViewItems depend on each other. The lightest dependency in the cycle is DevToys.Core.Tools.ViewItems → DevToys.Core.Tools (DevToys.Core.Tools.ViewItems.GuiToolViewItem → DevToys.Core.Tools.GuiToolInstance, 1 type pair(s)); cut that one first, e.g. by moving the shared type to a namespace both can use or inverting it behind an interface. — src/app/dev/DevToys.Core/Tools/ViewItems/GuiToolViewItem.cs:8
  • The namespaces DevToys.Blazor.Components ↔ DevToys.Blazor.Components.Monaco ↔ DevToys.Blazor.Components.Monaco.Editor ↔ DevToys.Blazor.Components.Monaco.Languages ↔ DevToys.Blazor.Components.UIElements ↔ DevToys.Blazor.Core.Services depend on each other. The lightest dependency in the cycle is DevToys.Blazor.Components.Monaco.Editor → DevToys.Blazor.Components (DevToys.Blazor.Components.Monaco.Editor.ActionDescriptor → DevToys.Blazor.Components.RicherMonacoEditorBase, 1 type pair(s)); cut that one first, e.g. by moving the shared type to a namespace both can use or inverting it behind an interface. — src/app/dev/DevToys.Blazor/Components/Text/MonacoEditor/Monaco/Editor/ActionDescriptor.cs:12
  • The namespaces DevToys.Windows.Controls ↔ DevToys.Windows.Core depend on each other. The lightest dependency in the cycle is DevToys.Windows.Controls → DevToys.Windows.Core (DevToys.Windows.Controls.MicaWindowWithOverlay → DevToys.Windows.Core.EfficiencyModeService, 1 type pair(s)); cut that one first, e.g. by moving the shared type to a namespace both can use or inverting it behind an interface. — src/app/dev/platforms/desktop/DevToys.Windows/Controls/MicaWindowWithOverlay.xaml.cs:11

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 direction5.7 / 10Adequate✓ 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.

  • `DevToys.Core` is a Domain project but references `DevToys.Api`, a Web project. The clean-architecture rule is that dependencies point INWARD — the domain/application core must not depend on outer layers (infrastructure/web). Invert it: define the abstraction in the inner layer and implement it in the outer one. — src/app/dev/DevToys.Core/DevToys.Core.csproj:6
  • This Domain file depends on the Web project `DevToys.Api`: it names `LoggingExtensions`. The inward dependency rule is broken here. Depend on an abstraction the inner layer owns, implemented in the outer one. (×4) — src/app/dev/DevToys.Core/AppHelper.cs:143, src/app/dev/DevToys.Core/FileHelper.cs:8, src/app/dev/DevToys.Core/Mef/RecursiveDirectoryCatalog.cs:44, …
  • This Domain file depends on the Web project `DevToys.Api`: it names `IOrderableMetadata`. The inward dependency rule is broken here. It is named again on lines 31, 37, 87. Depend on an abstraction the inner layer owns, implemented in the outer one. — src/app/dev/DevToys.Core/ExtensionOrderer.cs:17
  • This Domain file depends on the Web project `DevToys.Api`: it names `IFileStorage`. The inward dependency rule is broken here. It is named again on line 18. Depend on an abstraction the inner layer owns, implemented in the outer one. — src/app/dev/DevToys.Core/Logging/FileLoggerProvider.cs:14
  • This Domain file depends on the Web project `DevToys.Api`: it names `IFileStorage`. The inward dependency rule is broken here. Depend on an abstraction the inner layer owns, implemented in the outer one. — src/app/dev/DevToys.Core/Logging/LoggingBuilderExtensions.cs:11
  • This Domain file depends on the Web project `DevToys.Api`: it names `IMefProvider`, `LoggingExtensions`. The inward dependency rule is broken here. It is named again on lines 28, 40, 105. Depend on an abstraction the inner layer owns, implemented in the outer one. — src/app/dev/DevToys.Core/Mef/MefComposer.cs:22
  • This Domain file depends on the Web project `DevToys.Api`: it names `IMefProvider`. The inward dependency rule is broken here. It is named again on line 6. Depend on an abstraction the inner layer owns, implemented in the outer one. — src/app/dev/DevToys.Core/Mef/MefProvider.cs:5
  • This Domain file depends on the Web project `DevToys.Api`: it names `Platform`. The inward dependency rule is broken here. It is named again on lines 9, 12, 16, 20. Depend on an abstraction the inner layer owns, implemented in the outer one. — src/app/dev/DevToys.Core/OSHelper.cs:5
  • This Domain file depends on the Web project `DevToys.Api`: it names `DevToys.Api`. The inward dependency rule is broken here. Depend on an abstraction the inner layer owns, implemented in the outer one. — src/app/dev/DevToys.Core/Properties/AdditionGlobalUsings.cs:1
  • This Domain file depends on the Web project `DevToys.Api`: it names `SettingDefinition`, `AvailableApplicationTheme`, `UITextEndOfLinePreference`. The inward dependency rule is broken here. It is named again on lines 52, 60, 68, 71, 76, 84, 92, 100, …. Depend on an abstraction the inner layer owns, implemented in the outer one. — src/app/dev/DevToys.Core/Settings/PredefinedSettings.cs:43
  • This Domain file depends on the Web project `DevToys.Api`: it names `ISettingsProvider`, `LoggingExtensions`, `SettingChangedEventArgs`, `SettingDefinition`. The inward dependency rule is broken here. It is named again on lines 9, 17, 21, 23, 64, 92, 95, 99. Depend on an abstraction the inner layer owns, implemented in the outer one. — src/app/dev/DevToys.Core/Settings/SettingsProvider.cs:8
  • This Domain file depends on the Web project `DevToys.Api`: it names `UIToolView`, `IGuiTool`, `LoggingExtensions`, `MenuPlacement`, `GUI`, `IResourceAssemblyIdentifier`. The inward dependency rule is broken here. It is named again on lines 14, 15, 23, 25, 37, 74, 82, 145, …. Depend on an abstraction the inner layer owns, implemented in the outer one. — src/app/dev/DevToys.Core/Tools/GuiToolInstance.cs:12
  • This Domain file depends on the Web project `DevToys.Api`: it names `IGuiTool`, `IResourceAssemblyIdentifier`, `GuiToolGroup`, `ISettingsProvider`, `LoggingExtensions`, `SettingDefinition`, `TextSpan`, `ObservableCollectionExtensions`, …. The inward dependency rule is broken here. It is named again on lines 41, 42, 43, 57, 58, 59, 60, 62, …. Depend on an abstraction the inner layer owns, implemented in the outer one. — src/app/dev/DevToys.Core/Tools/GuiToolProvider.cs:25
  • This Domain file depends on the Web project `DevToys.Api`: it names `DictionaryExtensions`, `DataTypeNameAttribute`, `TargetPlatformAttribute`, `Platform`. The inward dependency rule is broken here. It is named again on lines 9, 10, 18. Depend on an abstraction the inner layer owns, implemented in the outer one. — src/app/dev/DevToys.Core/Tools/Metadata/DataTypeDetectorMetadata.cs:8
  • This Domain file depends on the Web project `DevToys.Api`: it names `IOrderableMetadata`, `DictionaryExtensions`, `NameAttribute`, `OrderAttribute`. The inward dependency rule is broken here. It is named again on lines 14, 15, 16. Depend on an abstraction the inner layer owns, implemented in the outer one. — src/app/dev/DevToys.Core/Tools/Metadata/GuiToolGroupMetadata.cs:4
  • This Domain file depends on the Web project `DevToys.Api`: it names `IOrderableMetadata`, `NameAttribute`, `ToolDisplayInformationAttribute`, `DictionaryExtensions`, `OrderAttribute`, `NotSearchableAttribute`, `NotFavorableAttribute`, `NoCompactOverlaySupportAttribute`, …. The inward dependency rule is broken here. It is named again on lines 19, 20, 21, 22, 23, 24, 25, 26, …. Depend on an abstraction the inner layer owns, implemented in the outer one. — src/app/dev/DevToys.Core/Tools/Metadata/GuiToolMetadata.cs:4
  • This Domain file depends on the Web project `DevToys.Api`: it names `DictionaryExtensions`, `NameAttribute`. The inward dependency rule is broken here. Depend on an abstraction the inner layer owns, implemented in the outer one. (×2) — src/app/dev/DevToys.Core/Tools/Metadata/LanguageServiceMetadata.cs:10, src/app/dev/DevToys.Core/Tools/Metadata/ResourceAssemblyIdentifierMetadata.cs:10
  • This Domain file depends on the Web project `DevToys.Api`: it names `IDataTypeDetector`, `ISettingsProvider`, `LoggingExtensions`, `TaskSchedulerAwaiter`, `DataDetectionResult`, `CancellationTokenExtension`. The inward dependency rule is broken here. It is named again on lines 16, 19, 55, 59, 64, 110, 114, 116, …. Depend on an abstraction the inner layer owns, implemented in the outer one. — src/app/dev/DevToys.Core/Tools/SmartDetectionService.cs:15
  • This Domain file depends on the Web project `DevToys.Api`: it names `GuiToolGroup`. The inward dependency rule is broken here. Depend on an abstraction the inner layer owns, implemented in the outer one. — src/app/dev/DevToys.Core/Tools/ViewItems/GroupViewItem.cs:17
  • This Domain file depends on the Web project `DevToys.Api`: it names `TextSpan`. The inward dependency rule is broken here. It is named again on line 30. Depend on an abstraction the inner layer owns, implemented in the outer one. — src/app/dev/DevToys.Core/Tools/ViewItems/GuiToolViewItem.cs:13

What to do

  • Keep dependencies pointing inward: domain/application define interfaces, infrastructure/web implement them (Dependency Inversion).
AX5 · Architecture & structure10.0 / 10Exemplary✓ Tool-verified

Other · Architecture — Whether the codebase has a recognisable, scale-appropriate structure (a named architectural style, or modular enough for its size) rather than being an ad-hoc ball of mud.

Method: Roslyn plus csproj analysis: architecture style detection (DDD, clean, vertical-slice, CQRS) and structure fitness for repo size. Deterministic.

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

Other · Architecture — Whether interfaces stay focused rather than fat — the Interface-Segregation principle (SOLID 'I').

Method: Roslyn scan: public interface declared-member counts (accessors fold into their property/event); fat-interface threshold (over 15 declared members) flagged per type. Each finding also reports the distinct-OPERATION count — members counted by name, so an overload group counts once — which decides whether it states the caller-side ISP harm or the implementer-side burden of an overload set. TypeScript: exported interfaces that declare behaviour, counted over their REQUIRED operations (method signatures and function-typed properties with no `?`, once per signature) — data-shape interfaces and ambient .d.ts declarations are outside the population; JavaScript declares no interfaces and is not applicable. Deterministic, type-level.

  • `IUIInfoBar` declares 20 members: `IsOpened`, `IsClosable`, `IsIconVisible`, `Title`, `Description`, `ActionButtonText`, `IsActionButtonAccent`, `Severity`, `OnCloseAction`, `OnActionButtonClick`, `IsOpenedChanged`, `IsClosableChanged`, `IsIconVisibleChanged`, `TitleChanged`, `DescriptionChanged`, `ActionButtonTextChanged`, `IsActionButtonAccentChanged`, `SeverityChanged`, `OnCloseActionChanged`, `OnActionButtonClickChanged`. Counted as the author wrote them — a property is ONE member and its get/set accessors are not counted separately, and an event counts once. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces. — src/app/dev/DevToys.Api/Tool/GUI/Components/IUIInfoBar.cs:6
  • `IUIMultiLineTextInput` declares 16 members: `HighlightedSpans`, `HoverTooltips`, `TextInputToSynchronizeScrollBarWith`, `SyntaxColorizationLanguageName`, `IsExtendableToFullScreen`, `WrapMode`, `LineNumberMode`, `Selection`, `HoverTooltipChanged`, `HighlightedSpansChanged`, `TextInputToSynchronizeScrollBarWithChanged`, `SyntaxColorizationLanguageNameChanged`, `IsExtendableToFullScreenChanged`, `WrapModeChanged`, `LineNumberModeChanged`, `SelectionChanged`. Counted as the author wrote them — a property is ONE member and its get/set accessors are not counted separately, and an event counts once. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces. — src/app/dev/DevToys.Api/Tool/GUI/Components/IUIMultiLineTextInput.cs:6

What to do

  • Split fat interfaces into focused role-interfaces so clients depend only on what they use.
AX8 · Test isolation10.0 / 10Exemplary✓ Tool-verified

Other · Architecture — Whether production projects stay free of references to test projects — tests may depend on production, never the reverse.

Method: Csproj graph: each production project checked for references to test projects (identified by test-framework presence, not name). Zero violations is clean. Deterministic.

GD1 · Unfinished & placeholder code10.0 / 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. (×3) — src/app/dev/DevToys.Localization/DevToysLocalizationResourceManagerAssemblyIdentifier.cs:9, REDACTED:136, src/app/dev/DevToys.Blazor/Core/Converters/PolymorphicConverter.cs:8

What to do

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

  • `OnDataReceived` is a shipped member whose whole body throws NotImplementedException — scaffolding that was never completed. Implement it or remove the dead surface. — REDACTED:136
  • `GetFontDefinitionsAsync` is a shipped member whose whole body throws NotImplementedException — scaffolding that was never completed. Implement it or remove the dead surface. — src/app/dev/DevToys.Localization/DevToysLocalizationResourceManagerAssemblyIdentifier.cs:9
  • A line of code has been commented out rather than removed — dead weight that rots and confuses. Delete it (version control remembers). (×6) — src/app/dev/DevToys.Blazor/Components/UIElements/UITextInputWrapper.razor.cs:263, src/app/dev/DevToys.Blazor/Components/UIElements/UITextInputWrapper.razor.cs:327, src/app/dev/platforms/desktop/DevToys.MacOS/Controls/BlazorWebView/BlazorWebViewManager.cs:265, …

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.8 / 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

  • Add a build/run (quick start) section to the root README — the first thing a newcomer needs.
  • 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 a README to the 11 of 12 project(s) that lack one — worth up to 1.8 pts.
M2 · Architecture documentation0.0 / 10Critical✓ Tool-verified

Maturity · Maturity — Whether key decisions (ADRs) and the high-level shape (C4/diagrams) are written down.

Method: Filesystem scan: ADR folder/naming conventions or content, plus Mermaid/PlantUML/C4/architecture.md discovery. Exhaustive, deterministic.

  • No Architecture Decision Records found — no conventional ADR directory, no numbered `NNNN-title` documents in any markup this check reads, and nothing ADR-shaped by content. Design rationale recorded elsewhere (a design-notes tree, a mailing list, pull-request discussion) is not visible to this check and is not re-findable per decision, so a future maintainer cannot ask why one choice was made and get an answer.
  • No C4/Structurizr/PlantUML/Mermaid/Graphviz/D2 diagram, no drawn diagram named for the architecture, no file named `architecture` or `design` in any markup this check reads, and nothing in the README, docs or contributor guides that announces the shape — no `## Architecture` heading, no "architecture overview"/"high-level design" phrasing, no "the architecture is …" introduction, no guided code tour. A shape laid out in prose that never names itself as the architecture is not visible to this check, and neither is one kept outside the repository, so this row reports the absence of a re-findable shape document — not evidence that nobody wrote the shape down.

What to do

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

M4 · Documentation accuracy8.0 / 10Strong◐ 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 claims a Dockerfile but the evidence shows no Docker-related project — searched for: `Dockerfile`. Each was matched case- and separator-insensitively against file and directory NAMES anywhere in the tree, and against the CONTENTS of manifest and configuration files (package.json and other *.json, *.csproj, *.props, *.sln/*.slnx, *.yml, *.toml, *.config, tool configs such as eslint.config.js, Dockerfile); the README's own prose never counts, so a claim is never refuted by merely being made. Nothing outside that search was read — a footprint living only in a submodule, in a file type not listed here, or under a name none of those terms matches is not seen, and this row is then wrong. — README.md:1
  • CONTRIBUTING.md runs `dotnet build src/DevToys.Tools/DevToys.Tools.csproj -c Debug`, but `src/DevToys.Tools/DevToys.Tools.csproj` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — CONTRIBUTING.md:141

What to do

  • Reconcile the README with reality: README claims a Dockerfile but the evidence shows no Docker-related project; CONTRIBUTING.md runs `dotnet build src/DevToys.Tools/DevToys.Tools.csproj -c Debug`, but `src/DevToys.Tools/DevToys.Tools.csproj` does not exist.
P1 · CI/CD gates10.0 / 10Exemplary○ Nothing flagged

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

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

P10 · Library API & versioning6.0 / 10Adequate✓ Tool-verified

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

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

  • 117/163 types (72%) are public. For a library, every public type is a stability contract — make internal-by-default and expose only the intended API.

What to do

  • Make types internal by default; expose only the deliberate public API so internals can change without breaking consumers.
P2 · Observability7.0 / 10Strong✓ 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.

What to do

  • Consider OpenTelemetry tracing/metrics and a health-check endpoint for operability.
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 2435 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.
P6 · Release Hygiene8.0 / 10Strong✓ 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.

  • The changelog this check read carries 0 versioned entries, against a bar of 3. Counted as either the distinct `x.y.z` versions it names (a link's target is not counted) or its version-shaped section headings (`## [1.2.0]`, `## V14.x.x`, `## Updates in 8.0.x`), whichever is the larger — so a log sectioned by minor series counts its sections, not its individual patch numbers. Entries recorded somewhere this check does not read — release notes generated at tag time from a generator config it did not recognise, or a log kept outside the repository — are not counted here, and this row is about what is re-findable in the tree rather than about how often you release.

What to do

  • Keep the changelog current — add a versioned entry (Keep-a-Changelog ## [x.y.z]) for each release so the history isn't a stub.
P7 · Outbound HTTP resilience3.0 / 10Weak✓ Tool-verified

Readiness · Readiness — Whether outbound HTTP calls are wrapped in resilience (retry/timeout/circuit-breaker) so a failing dependency doesn't cascade.

Method: Source scan: outbound HTTP clients and what bounds them — resilience handlers (Polly, AddStandardResilienceHandler) on .NET; on Go, the JVM, Python, JavaScript/TypeScript, Ruby, PHP, Rust, Elixir, Swift, Dart and Erlang, a timeout, deadline, retry or breaker beside each call, or a process-wide client default (a framework-wide deadline such as Drupal core's, Laravel's or actix's awc counts). Exhaustive, deterministic.

  • `new()` builds an outbound HTTP client and nothing bounds it: no timeout is set on it and no retry or resilience policy wraps its calls in the type that owns it. This codebase ships libraries/tools rather than a service it operates, so the failure lands as a hung caller — a build step, a CLI run, a UI thread — with no way out. — src/app/dev/DevToys.Core/Web/WebClientService.cs:9

What to do

  • Give every outbound call a bound the caller can rely on: set an explicit `HttpClient.Timeout` (or pass a `CancellationToken` from a `CancellationTokenSource` with a deadline) and flow the caller's own `CancellationToken` through, so a slow endpoint fails fast instead of hanging.
PF1 · Benchmark discipline6.0 / 10Adequate✓ Tool-verified

Readiness · Performance — Whether the code protects its performance with benchmarks — a benchmark suite, allocation/memory measurement, and (ideally) a CI gate. Presence is credited as a bonus, never a deduction.

Method: Repo + source scan: BenchmarkDotNet referenced (csproj/source), [Benchmark]/[MemoryDiagnoser] attribute counts, and a benchmark step in CI; off .NET, the same ladder over Go testing.B, Rust criterion/#[bench]/divan, JMH/kotlinx-benchmark, pytest-benchmark/asv/pyperf, tinybench/mitata/vitest bench/benchmark.js and Swift package-benchmark — scored as a bonus ladder (absence is neutral, never a deduction). Deterministic, presence detection.

  • No benchmark suite was found by the two searches this check runs. FIRST, a BenchmarkDotNet package reference in any project file — every project the workspace loaded, plus a walk of project files on disk that never loaded, because a benchmark suite is exactly the project a partial load drops. SECOND, a script harness: a file whose name contains `benchmark` and ends `.py`, `.sh`, `.ps1`, `.bash`, `.rb`, `.js` or `.mjs`, credited ONLY when this repository's CI text also mentions benchmarks — a harness no pipeline runs is read as a fixture, deliberately. Neither search can see a benchmark suite in another ecosystem's idiom (a Go `testing.B` file, a JMH or criterion project, a pytest-benchmark run), so this is 'no benchmark found by those two searches', not a verdict that the repository has none. Where code is performance-sensitive, a benchmark guards against silent regressions — but it's a bonus here, not a deduction.

What to do

  • Add a benchmarking harness for the hot paths and run it in CI to catch regressions (for .NET, a BenchmarkDotNet project with [MemoryDiagnoser] to track allocations).
PF2 · Allocation hygiene10.0 / 10Exemplary✓ Tool-verified

Readiness · Performance — Whether the code is written to minimise allocations so it doesn't pressure its host's memory manager — buffer/slice views over copies, object pooling, stack or value-type allocation, and buffer writers. Reward-only: credited where present, never penalised where a simpler style is fine.

Method: Production-source scan: density (per 1k LoC) of allocation-aware APIs — in .NET Span/Memory, ArrayPool/ObjectPool, stackalloc, ValueTask, value-type structs, IBufferWriter, string.Create, SkipLocalsInit; off .NET, with comments and strings blanked, Go's sync.Pool, preallocated slices/maps, Grow, strconv.Append* and buf[:0] reuse; the JVM's NIO buffer views, MemorySegment, primitive collections, pools and literal presizes (plus Kotlin primitive arrays and value classes, Scala AnyVal and @specialized); Swift's reserveCapacity, ContiguousArray, withUnsafe* access and ~Copyable. Activated off .NET on the same floor (400 lines, and benchmarks or 8 uses); Rust and garbage-collected scripting languages are not applicable. Reward-only. Deterministic, syntax/text detection.

PF3 · Async & latency hygiene6.0 / 10Adequate✓ 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.

  • 4 blocking call(s) on async work (.Wait()/.GetAwaiter().GetResult()) — these waste a thread and can deadlock wherever a synchronization context is in play (a UI thread, or a caller that has one).
  • `.GetAwaiter().GetResult()` blocks this thread until the async work completes — it wastes a thread-pool thread for as long as the work runs and can deadlock wherever a synchronization context is in play (a UI thread, or a caller that has one). (×2) — src/app/dev/DevToys.Api/Core/Threading/TaskExtensions.cs:82, src/app/dev/DevToys.Api/Core/Threading/TaskExtensions.cs:93
  • `.GetAwaiter() .GetResult()` blocks this thread until the async work completes — it wastes a thread-pool thread for as long as the work runs and can deadlock wherever a synchronization context is in play (a UI thread, or a caller that has one). (×2) — src/app/dev/platforms/desktop/DevToys.MacOS/Controls/BlazorWebView/BlazorWKWebView.cs:110, src/app/dev/platforms/desktop/DevToys.Linux/Components/BlazorWebView/BlazorWebView.cs:140

What to do

  • Make the call chain async end-to-end and await it — never block on a Task with .Wait()/.GetAwaiter().GetResult().
R1 · Type Safety5.0 / 10Adequate✓ Tool-verified

React / JS · Code Health — How much of the frontend is typed TypeScript vs untyped JavaScript.

Method: Frontend file inventory: the share of typed TypeScript vs untyped JavaScript across the source tree. Deterministic, exhaustive over frontend files.

  • 18 typed · 18 plain JS — the untyped files are src/app/dev/DevToys.Blazor/Assets/javascript/dom.js, src/app/dev/DevToys.Blazor/Assets/javascript/index.esm.js, src/app/dev/DevToys.Blazor/Assets/javascript/monacoEditor.js, src/app/dev/DevToys.Blazor/Assets/javascript/monacoEditorLanguage.js, src/app/dev/DevToys.Blazor/Assets/javascript/popover.js, src/app/dev/DevToys.Blazor/Components/Collections/DataGrid/DataGrid.razor.js (+12 more). 0 production file(s) opt out entirely with @ts-nocheck · 3 @ts-ignore suppression(s).

What to do

  • Migrate the remaining .js/.jsx files to TypeScript.
R10 · Code Duplication8.4 / 10Strong✓ Tool-verified

React / JS · Code Health — Near-exact copy-pasted blocks of substantial extent across the frontend (the D4 clone algorithm over JS/TS tokens, D-386): a block is reported only where its copies still agree on most of their own identifiers and literals, or were renamed as they were pasted but kept most of their constants, and where the copies carry enough code to stand on their own or the copied extent reaches 30 lines — so a re-implementation sharing neither names nor values, and a small pasted declaration, are both found and deliberately not reported, and a clean R10 is not a claim that nothing was copied.

Method: Near-exact copy-pasted blocks of substantial extent across the frontend (the D4 clone algorithm run over JS/TS tokens). Masking finds the candidates; a block is reported when its copies still agree on most of their own identifiers and literals, or when a renamed copy still agrees on most of its constants, AND the copies carry enough code to stand on their own — or when the copied extent reaches 30 lines. So a re-implementation sharing neither names nor values, and a small pasted declaration, are deliberately not counted. Deterministic.

  • src/app/dev/DevToys.Blazor/Components/UIElements/UIFileSelectorPresenter.razor.ts:26 · src/app/dev/DevToys.Blazor/Components/UIElements/UITextInputWrapper.razor.ts:40 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — src/app/dev/DevToys.Blazor/Components/UIElements/UIFileSelectorPresenter.razor.ts:26
  • src/app/dev/DevToys.Blazor/Assets/javascript/monacoEditor.ts:935 · src/app/dev/DevToys.Blazor/Assets/javascript/monacoEditor.ts:954 — all 2 copies are in the same file, and the SHAPE of this repetition could not be determined. It is not a run of declarations, a listing, a declaration header, a type body or a slice through a construct — and it was not measured as a run of executable statements either, so this row cannot tell you whether a function can stand where these lines are. Read the two spans before acting, because the move is opposite in the two cases. Where they are statements, the ordinary answer holds: give the shared part one home and call it from each site. Where they turn out to be declarations, a literal's entries, or the cases of an enumeration, there is no call site to call anything from, and collapsing them would delete what each copy pins — a shared base type, a generated set, or one exported constant each site refers to is the move instead, and sometimes the honest answer is that there is nothing to extract at all. Reported because the copies drift apart the first time only one of them is edited, which is true whichever of those they are. — src/app/dev/DevToys.Blazor/Assets/javascript/monacoEditor.ts:935
  • src/app/dev/DevToys.Blazor/Assets/javascript/monacoEditor.ts:728 · src/app/dev/DevToys.Blazor/Assets/javascript/monacoEditor.ts:742 — 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. — src/app/dev/DevToys.Blazor/Assets/javascript/monacoEditor.ts:728
  • src/app/dev/DevToys.Blazor/Assets/javascript/dom.ts:59 · src/app/dev/DevToys.Blazor/Assets/javascript/dom.ts:105 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — src/app/dev/DevToys.Blazor/Assets/javascript/dom.ts:59
  • src/app/dev/DevToys.Blazor/Assets/javascript/dom.ts:36 · src/app/dev/DevToys.Blazor/Assets/javascript/dom.ts:64 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — src/app/dev/DevToys.Blazor/Assets/javascript/dom.ts:36
  • src/app/dev/DevToys.Blazor/Assets/javascript/dom.ts:81 · src/app/dev/DevToys.Blazor/Assets/javascript/dom.ts:122 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — src/app/dev/DevToys.Blazor/Assets/javascript/dom.ts:81
  • src/app/dev/DevToys.Blazor/Assets/javascript/monacoEditor.ts:831 · src/app/dev/DevToys.Blazor/Assets/javascript/monacoEditor.ts:856 · src/app/dev/DevToys.Blazor/Assets/javascript/monacoEditor.ts:866 — all 3 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — src/app/dev/DevToys.Blazor/Assets/javascript/monacoEditor.ts:831
  • src/app/dev/DevToys.Blazor/Assets/javascript/monacoEditor.ts:487 · src/app/dev/DevToys.Blazor/Assets/javascript/monacoEditor.ts:497 · src/app/dev/DevToys.Blazor/Assets/javascript/monacoEditor.ts:507 · src/app/dev/DevToys.Blazor/Assets/javascript/monacoEditor.ts:517 — all 4 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — src/app/dev/DevToys.Blazor/Assets/javascript/monacoEditor.ts:487

What to do

  • Act on each finding's own remediation rather than one rule: the move depends on what recurs. Where the copies are executable blocks, give the shared part one home and call it from each site; where they are declarations, a listing, a specialisation already delegating to its base, or one shape repeated per entity, there is no call site and the move is a shared type, a generated set or a factory — sometimes there is nothing to extract.
R2 · Cyclomatic Complexity9.8 / 10Exemplary✓ Tool-verified

React / JS · Code Health — Per-function cyclomatic/cognitive complexity from the token-level function scanner (D-386) — real branching, not a regex heuristic.

Method: Per-function cyclomatic/cognitive complexity from a token-level function scanner (real branching, not a regex heuristic), computed over every frontend function. Deterministic.

  • placePopover has cyclomatic complexity 67 and cognitive complexity 113; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — src/app/dev/DevToys.Blazor/Assets/javascript/popover.ts:328
  • calculatePopoverPosition has cyclomatic complexity 19 and cognitive complexity 18; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — src/app/dev/DevToys.Blazor/Assets/javascript/popover.ts:237
  • callback has cyclomatic complexity 15 and cognitive complexity 49; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — src/app/dev/DevToys.Blazor/Assets/javascript/popover.ts:72

What to do

  • Break down the listed branch-heavy functions; aim P95 cyclomatic ≤ 5.
R3 · Large Files7.8 / 10Strong✓ Tool-verified

React / JS · Code Health — How many source files exceed the large-file threshold.

Method: Components/modules exceeding the large-file threshold, counted exhaustively across the frontend source tree. Deterministic.

  • src/app/dev/DevToys.Blazor/Assets/javascript/monacoEditor.ts has 887 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — src/app/dev/DevToys.Blazor/Assets/javascript/monacoEditor.ts:1
  • src/app/dev/DevToys.Blazor/Assets/javascript/popover.ts has 418 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — src/app/dev/DevToys.Blazor/Assets/javascript/popover.ts:1

What to do

  • Split each oversized file along the responsibilities already in it, into smaller focused modules in the same package.
R6 · Tooling0.0 / 10Critical✓ Tool-verified

React / JS · Readiness — Whether the project wires up test, lint and typecheck — detected from each package.json script's COMMAND (eslint / tsc / vitest / jest / playwright), not just its name, and corroborated against CI-workflow invocations so a tool run only in CI still counts.

Method: package.json scanned for test/lint/typecheck script wiring. Deterministic presence check.

  • test ✗ · lint ✗ · typecheck ✗ — read from this repository's package.json scripts and corroborated against its CI workflows. A script counts when its name or command matches the step: `test` for the suite, `lint` or `prettier` for linting, `typecheck`/`type-check`/`tsc` for type checking. ✗ therefore means no script or CI step under those names was found, NOT that the step is absent from your pipeline — a task invoked by a runner this check does not read, or named something else entirely, is not seen and is worth confirming before acting on a cross. A ✓ means the wiring is DECLARED — a script or CI step under those names exists. It is not a statement that the step passes, or that it runs at all: nothing here installs a dependency or executes a suite.

What to do

  • Add a test runner (vitest / jest / playwright) and eslint and `tsc --noEmit` as package.json scripts and run them in CI.
R7 · Dead Code10.0 / 10Exemplary✓ Tool-verified

React / JS · Code Health — Files unreachable from every application/tooling/test entry point, and exports nothing imports (module-graph reachability, D-386).

Method: Dead code: files unreachable from every application/tooling/test entry point plus exports nothing imports, via module-graph reachability. Deterministic, exhaustive over the import graph.

R8 · Dependency Hygiene10.0 / 10Exemplary✓ Tool-verified

React / JS · Readiness — npm dependency truthfulness (D-386): unused dependencies, imports not declared anywhere, and type-/test-only packages shipped as production deps.

Method: npm dependency truthfulness: unused dependencies, imports declared nowhere, and type-/test-only packages shipped as production deps — from the manifest + import graph. Deterministic.

R9 · Circular Imports10.0 / 10Exemplary✓ Tool-verified

React / JS · Architecture — Import cycles in the module graph (D-386) — files that can only be understood and changed together.

Method: Import cycles in the module graph, detected exhaustively over JS/TS imports (the same cycle detection as the .NET coupling dimension). Deterministic.

X1 · Async correctness5.4 / 10Adequate✓ Tool-verified

Other · Code Health — Whether the code avoids sync-over-async (deadlock-prone blocking on tasks) and async void.

Method: Roslyn syntax scan: async methods scanned for .Wait()/.GetAwaiter().GetResult() and async-void outside event handlers. Deterministic, hard fact per invocation.

  • `StreamWriter.Flush` blocks the thread on I/O while `StreamWriter.FlushAsync` exists to wait without one — inside a method that is already `async`, await the twin. — src/app/dev/DevToys.Api/Core/OneOfExtensions.cs:62
  • 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. — src/app/dev/DevToys.Api/Core/Threading/AsyncLazy.cs:85
  • Blocking on a Task with `.Wait()`/`.GetAwaiter().GetResult()` can deadlock (and wastes a thread). Prefer awaiting it: make the caller `async` and `await` instead. Where a synchronous entry point must stay — a public sync API you cannot break, or a process entry point that must not return until the work finishes — the block belongs in ONE documented bridge and never inside code that is already async; and where it already is that bridge, give the wait a TIMEOUT so a hung task fails the call instead of hanging the process. (×2) — src/app/dev/DevToys.Api/Core/Threading/TaskExtensions.cs:82, src/app/dev/DevToys.Api/Core/Threading/TaskExtensions.cs:93
  • `.Wait(…)` blocks this thread until the task completes or the bound expires — sync-over-async: it can deadlock under a synchronization context and it parks a thread while it waits. `await` the task (with `.WaitAsync(timeout, token)` where the bound matters). — src/app/dev/DevToys.Core/Logging/FileLoggerProvider.cs:48
  • `async void` can't be awaited and its exceptions crash the process instead of propagating. Return `Task` — or, where the delegate contract requires void (timer/event/callback registrations), make this a thin void shim that awaits a Task-returning inner method inside try/catch so exceptions are contained. (×9) — src/app/dev/DevToys.Blazor/Components/UIElements/UIDiffTextInputPresenter.razor.cs:85, src/app/dev/DevToys.Blazor/Components/UIElements/UIDiffTextInputPresenter.razor.cs:91, src/app/dev/DevToys.Blazor/Components/UIElements/UIDiffTextInputPresenter.razor.cs:97, …
  • `StreamWriter.Write` blocks the thread on I/O while `StreamWriter.WriteAsync` exists to wait without one — inside a method that is already `async`, await the twin. — src/app/dev/DevToys.Blazor/Components/UIElements/UITextInputWrapper.razor.cs:239
  • Blocking on a Task with `.Wait()`/`.GetAwaiter().GetResult()` wastes a thread and, if the task needs a context this one is holding, deadlocks. `Dispose()` returns void by contract, so it cannot simply `await`: signal the work to stop first (cancel its token, set its stop flag) so the wait is short, give the wait a TIMEOUT so a hung task cannot hang shutdown, and — where callers can use it — add an awaitable teardown (`DisposeAsync`/`StopAsync`) beside the synchronous one and let `Dispose()` remain the bounded fallback. (×2) — src/app/dev/platforms/desktop/DevToys.MacOS/Controls/BlazorWebView/BlazorWKWebView.cs:108, src/app/dev/platforms/desktop/DevToys.Linux/Components/BlazorWebView/BlazorWebView.cs:138

What to do

  • Blocking `StreamWriter.Flush` inside an `async` method
X12 · Unreachable branch10.0 / 10Exemplary○ Nothing flagged

Other · Code Health — Whether any branch is dead by construction — a switch arm whose label can never equal a case-normalised subject, or an `else if` whose predicate the arm above has already swallowed.

Method: Roslyn syntax + semantics: switch labels compared against the subject's own case normaliser, and if/else-if chains checked for a literal an earlier arm's containment test already swallows. Deterministic, provable per finding. Advisory.

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

Other · Code Health — Whether a child process that has BOTH standard streams redirected drains both — reading one to the end while the other is never read deadlocks once the child fills the unread pipe.

Method: Roslyn syntax + semantics: ProcessStartInfo launches with both streams redirected, checked for a drain of each stream across the enclosing type. On a repository with no .NET source it reads JavaScript/TypeScript off the engine’s own token stream (test, vendored and minified paths not) with the same rule: a `spawn` imported from `child_process` whose stdout and stderr are both pipes (no options, no `stdio`, or `stdio` of `'pipe'`), bound to a local that never leaves its scope, where exactly one of the two streams is read, the other never, and the child’s `close`/`exit` (or the read stream’s end) is awaited; a shell redirect in the call’s arguments or a `kill` of the child suppresses it. The same rule reads Python’s `subprocess.Popen`, Dart’s `Process.start`, Ruby’s `Open3.popen3`, and Scala’s JDK process starts (`new ProcessBuilder(…).start()` with no `redirectErrorStream`/`redirectError`/`redirectOutput`/`inheritIO`, `Runtime.getRuntime.exec`) where one of `getInputStream`/`getErrorStream` is read and the other never while `waitFor()` is called or the read stream is read to its end. Deterministic, provable per finding. Advisory.

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

Other · Security — Whether a hand-rolled public/private IP check can be walked past — a method that unwraps IPv4-mapped IPv6 but returns the opposite verdict for the same host written as IPv4-compatible, 6to4 or NAT64.

Method: Roslyn syntax + semantics: methods that unwrap IPv4-mapped IPv6 and hand-roll IPv4 range carve-outs, checked for whether the IPv6 branch also accounts for the IPv4-compatible, 6to4 and NAT64 embeddings. Deterministic, provable per finding. Advisory.

X15 · Unvalidated length from an untrusted reader10.0 / 10Exemplary○ Nothing flagged

Other · Security — Whether a length read out of the stream being parsed is bounded before it is allocated or read — an unchecked count taken from the input lets the input choose the allocation.

Method: Roslyn syntax + semantics: integer lengths read from a BinaryReader and spent on a bulk read or an array allocation, checked for any comparison or bounding call on the value anywhere in the method. Deterministic, provable per finding. Advisory.

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

Other · Code Health — Whether a loop that shortens a string until it fits a length budget has a floor — one with none grinds the value down to the empty string, or past it into a negative-length `Substring`.

Method: Roslyn syntax + semantics: while/do loops whose body's only effect on a string is to drop its last character, checked for whether anything — a direct comparison on the length, a body guard, a break — bounds that length below. On a repository with no .NET source it reads JavaScript/TypeScript off the engine’s own token stream (test, vendored and minified paths not) with the same rule: a `while`/`do` loop whose body’s one assignment to a value is `x = x.slice(0, -1)` or `x = x.slice|substring|substr(0, x.length - 1)`, driven by a condition that reads `x.length` only as a term of a larger expression — never compared directly, never tested for truthiness, and with no other read of `x` — and whose body has no `break`, `return`, `throw` or `if` naming `x`. Deterministic, provable per finding. Advisory.

X17 · Uncapped recursion over a caller-supplied document10.0 / 10Exemplary○ Nothing flagged

Other · Security — Whether a walk that recurses through a JSON/XML tree handed in by its caller bounds how deep it will go — an uncapped walk lets the document's nesting choose the stack depth, and the resulting StackOverflowException cannot be caught.

Method: Roslyn syntax + semantics: methods that take a JSON/XML document node and call themselves with a child of it, reachable from an externally-callable member of the same type that accepts a document, checked for any depth parameter, descent counter or threaded arithmetic anywhere in the walk. On a repository with no .NET source it reads TypeScript off the engine’s own token stream (test, vendored, generated and minified paths and `.d.ts` not) with the same rule: a function or method with a parameter typed as a document value — `unknown`, `any`, `object`, `Record<string, unknown|any>`, a JSON alias (`JsonValue`, `JSONObject`, …) or a DOM node global the file does not rebind — that calls itself (bare, or through `this` for a method, or hands itself to a call over the value as in `value.map(walk)`) with something it took out of that value and never through an ancestor accessor such as `closest()` or `parentElement`, that is exported or reached from an exported function (a public method of the same exported class) taking such a value, and that names no depth, level, nesting, recursion, remaining or budget anywhere and threads no `+`/`-` arithmetic through a self-call. Plain JavaScript is not read: with no annotation nothing tells a parsed document from a tree the code built itself. Deterministic, provable per finding. Advisory.

X18 · Disposal-pattern correctness7.0 / 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.

  • `mefComposer` is a `MefComposer`, which implements `IDisposable`, and it is created here (line 74). Every use of it in `MainAsync` 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 mefComposer = …;`), which releases it at the end of the scope on every path including a throw. — src/app/dev/platforms/desktop/DevToys.CLI/Program.cs:74
  • `UIMultiLineTextInputPresenter` implements `IDisposable` — so it has told every caller it holds something worth releasing — and it constructs `_semaphore` itself (line 11), which makes that instance its own. But `_semaphore` is named in none of the methods the disposal search covered: `DisposeAsync` (line 41) — 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` (`_semaphore?.Dispose();`), or, if it truly does not need releasing, drop `IDisposable` from the type so the claim and the behaviour agree. — src/app/dev/DevToys.Blazor/Components/UIElements/UIMultiLineTextInputPresenter.razor.cs:11
  • `PopoverService` implements `IDisposable` — so it has told every caller it holds something worth releasing — and it constructs `_semaphore` itself (line 5), which makes that instance its own. But `_semaphore` is named in none of the methods the disposal search covered: `DisposeAsync` (line 20) — 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` (`_semaphore?.Dispose();`), or, if it truly does not need releasing, drop `IDisposable` from the type so the claim and the behaviour agree. — src/app/dev/DevToys.Blazor/Core/Services/PopoverService.cs:5

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.4 / 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 15/207 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. (×36) — src/app/dev/platforms/desktop/DevToys.CLI/Core/Settings/SettingsStorage.cs:77, src/app/dev/platforms/desktop/DevToys.CLI/Program.cs:64, src/app/dev/DevToys.Api/Tool/GUI/Components/UIToolView.cs:135, …
  • No CancellationToken parameter — the body observes an ambient token instead (a field or a context object), so the work does stop on cancellation, but a caller cannot cancel this call independently of the owner that created that token. (×3) — src/app/dev/DevToys.Core/Debugger/DebuggerHelper.cs:5, src/app/dev/DevToys.Business/ViewModels/MainWindowViewModel.cs:207, src/app/dev/DevToys.Business/ViewModels/MainWindowViewModel.cs:373

What to do

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

Other · Code Health — Whether an argument guard throws the exception its own condition describes — a guard that rejects a value for being EMPTY and reports it as `ArgumentNullException` tells the caller a parameter was null when it provably was not.

Method: Roslyn syntax: `throw new ArgumentNullException(nameof(p))` statements controlled by an `if`, whose condition is read for a test that is true of a NON-null `p` — an emptiness test that dereferences it (`p.Count == 0`, `!p.Any()`) or a BCL predicate documented true of the empty value (`string.IsNullOrEmpty(p)`). Deterministic, provable per finding. Advisory.

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

Other · Code Health — Whether a `when` guard is free of side effects — a guard that increments a counter or assigns while deciding whether its arm matches applies that change during PATTERN MATCHING, on an arm that may not be selected, and skips it entirely when a short-circuit to its left answers first.

Method: Roslyn syntax: `when` guards on case labels and switch-expression arms, read for a mutation (`++`/`--`/assignment) sitting in a position the guard's own `&&`/`||`/`??`/`?:`/`?.` can skip. Deterministic, provable per finding. Advisory.

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

Other · Code Health — Whether a method that TAKES a lock or semaphore and gives it back from a flag-guarded `finally` returns the value that flag implies — reporting success while the guard hands the primitive back admits a second caller the exclusion was there to keep out, and reporting failure while the guard keeps it leaves nothing to ever give it back.

Method: Roslyn syntax: `try` statements whose `finally` releases a synchronisation primitive under a bare local-bool guard, where the method also TOOK that same primitive before the `try`, checked for a `return` of a bool literal whose value disagrees with the flag state the method's own straight-line assignments put it in. Deterministic, provable per finding. Advisory.

X23 · Unguarded diagnostic 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 unescaped1.8 / 10Critical✓ Tool-verified

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.

  • `ReleaseNotesHtml` is text this program did not author, and it is written into the text of an element through Blazor's `MarkupString` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup. — src/app/dev/DevToys.Blazor/Pages/Dialogs/WhatsNewDialog.razor:11
  • `fontDefinition` is text this program did not author, and it is written into the text of an element through `innerHTML` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup. (×2) — src/app/dev/DevToys.Blazor/Assets/javascript/dom.js:110, src/app/dev/DevToys.Blazor/Assets/javascript/dom.ts:131
  • `html` is text this program did not author, and it is written into the text of an element through `innerHTML` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup. (×2) — src/app/dev/DevToys.Blazor/Components/UIElements/UIWebViewPresenter.razor.js:6, src/app/dev/DevToys.Blazor/Components/UIElements/UIWebViewPresenter.razor.ts:7

What to do

  • Each finding names the expression, the attribute it lands in and the line. Confirm the value's origin from the read this analyzer traced, then escape it at the sink or validate it against the shape the attribute accepts before interpolating.
X25 · Inert configuration knob10.0 / 10Exemplary○ Nothing flagged

Other · Code Health — Whether a value the caller is invited to supply is the value the type actually uses — a constructor parameter stored in a private field that nothing ever reads while the default it was given is spelled out a second time at the site that should have read it, a keyed lookup that falls back to a different setting than the one its key names while the same type falls back to the matching one for that same key, or a culture-sensitive parse given no format provider by a type that feeds its own settable culture to the same kind of parse elsewhere, or a number an entry point writes to standard output under the host's culture while the same entry point formats with the invariant culture elsewhere. Either way, every caller who supplies a value silently gets something else.

Method: Roslyn syntax: private instance fields of a non-partial type assigned in a constructor from one of its own parameters with a `??` fallback, checked for whether anything in the type body reads the field and whether that same fallback expression is spelled out again outside the constructor; and `??` fallbacks onto a member access from a lookup call carrying exactly one string literal, grouped by that key across the type and checked for a fallback member whose folded name disagrees with the key while a sibling site for the same key agrees with it. On a repository with no .NET source the first two arms read JavaScript/TypeScript off the engine’s own token stream (tests included, bundles and vendored paths not): a `#x`, `private` or `private` parameter-property instance field filled in the constructor from a parameter (or one member of one) through `??`/`||` or a parameter default, never read anywhere in the file by name, whose constructed default is spelled again in the class body; and `lookup("key") ?? s.member` grouped by key per class, or per module outside every class. The culture arm has no JavaScript counterpart: its parses take no locale. Deterministic, provable per finding. Advisory.

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

Other · Code Health — Whether a value handed from a callback to the body that waits on it crosses on something built to be crossed — a `Queue<T>`/`List<T>`/`Dictionary<K,V>` written inside an event handler and read back outside it is mutated by two flows at once, and the semaphore or completion source beside it orders how MANY items exist while leaving the collection's own head, tail and backing array unprotected.

Method: Roslyn syntax: method, accessor, local-function and lambda bodies that declare BOTH a non-thread-safe generic collection (`Queue`/`Stack`/`List`/`Dictionary`/`HashSet`/`Sorted*`/`LinkedList`) and a synchronisation primitive (`SemaphoreSlim`/`TaskCompletionSource`/`ManualResetEvent(Slim)`/`AutoResetEvent`/`CountdownEvent`) as locals, then read for a `+=`-registered lambda that raises that primitive while the body outside every lambda waits on it — and, in that scope, a mutating call on the collection inside the lambda paired with a mention of it outside. Any `lock` in the scope abstains it. On a repository with no .NET source the same handoff is read in Java off the engine’s own token stream (test source sets, vendored and demonstration paths not): an `ArrayList`/`LinkedList`/`ArrayDeque`/`PriorityQueue`/`Hash*`/`LinkedHash*`/`Tree*` local and a `CountDownLatch`/`Semaphore`/`CompletableFuture` local, a lambda or anonymous class that raises the primitive and mutates the collection, and a wait outside it; any `synchronized` or `lock()` abstains the body. Because each of those primitives orders what the callback wrote before raising it, only a touch that provably overlaps the callback is convicted: one after the registration and before the next wait, or one in a loop registered-before, waiting on every pass and not declaring the collection. Deterministic, provable per finding. Advisory.

X27 · Collection changed while being enumerated10.0 / 10Exemplary○ Nothing flagged

Other · Code Health — Whether a `foreach` leaves the collection it is walking alone — a body that adds to or removes from the very collection the loop is enumerating invalidates the enumerator it is holding, so the next `MoveNext` throws `InvalidOperationException` and the remaining items are never seen.

Method: Roslyn syntax + semantics: `foreach` statements whose body calls a structural mutator (`Add`/`Remove`/`Clear`/`Insert`/…) on the very expression the loop is enumerating. Two arms. ARM A — the source is a concrete fragile BCL collection, or a live `Keys`/`Values` view over one, and the mutator resolves to that same collection's own member; concurrent and immutable collections and arrays are outside the population by construction, since their enumerators survive a structural change. ARM B — the source is an argument-less accessor CALL on a receiver whose body is in source: the accessor must return a stored field VERBATIM and a sibling member must structurally change that same field, both read off the implementations rather than from the members' names. A mutation the loop provably exits immediately after (`break`/`return`/`throw`/`goto`), or one written inside a nested loop or a lambda, is counted and never reported. Deterministic, provable per finding. Advisory.

X28 · Index access outside its own emptiness guard10.0 / 10Exemplary○ Nothing flagged

Other · Code Health — Whether a condition that tests a value for emptiness indexes that same value only where the test holds — an `||` written one parenthesis too far to the left leaves an index access outside the guard beside it, so the empty case the guard exists to anticipate reaches the index and throws.

Method: Roslyn syntax only, no semantic model: the OUTERMOST `&&`/`||` of every boolean condition, read for a symbol the condition tests for emptiness (`string.IsNullOrEmpty`/`IsNullOrWhiteSpace`, a `Length`/`Count` comparison against a literal, `Any()`, a `Length`/`Count` pattern, or a comparison against `""`) and ALSO indexes. Each `symbol[...]` access is placed by a boolean-reachability walk from the access up to the outermost connective: an access is COVERED when some enclosing step has it in the right operand and the left operand, under the truth value that step forces, proves the symbol non-empty — a recursion over `&&`/`||` whose true- and false-directions are asymmetric. A finding needs BOTH an uncovered access and a covered one on the same symbol in the same condition, which is the agreeing twin that separates a misplaced parenthesis from an unrelated length test. Bare index accesses with no emptiness test in the condition are neither counted nor reported; a non-identifier receiver and a lambda nested inside the condition are outside the population. Deterministic, provable per finding. Advisory.

X29 · Per-element action decided by a fixed element10.0 / 10Exemplary○ Nothing flagged

Other · Code Health — Whether a decision taken once per element is taken ABOUT that element — a test inside a counted loop that reads a fixed subscript of the very collection its guarded statement indexes by the loop variable applies element zero's answer to all of them, so the elements that differ from it are all handled wrongly, and in the same direction.

Method: Roslyn syntax only, no semantic model: every `for` statement declaring exactly ONE loop variable, and every `if` inside its body that is not under a nested loop or a lambda. A site enters the population when the `if`’s condition never mentions the loop variable while the statement it guards indexes some collection by that variable ALONE (`c[i]`; `c[i + 1]` and `c[i, j]` are outside it). A finding additionally needs the AGREEING TWIN at the same-collection grain: the condition must read THAT SAME collection at a subscript that does not move — written into the condition, or reached through a local declared BEFORE the loop, so an alias bound inside the body is not followed. Both collection expressions must be simple identifiers. On a repository with no .NET source the same rule reads JavaScript/TypeScript off the engine’s own token stream (tests included, bundles and vendored paths not): a `for (let|var|const x = …; …; …)` with one declarator and a braced body, an alias followed only when it is declared before the loop in a block that encloses it and never assigned inside the loop. Deterministic, provable per finding. Advisory.

X3 · Exception handling5.0 / 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. (×18) — src/app/dev/platforms/desktop/DevToys.CLI/Core/OneOfParser.cs:324, src/app/dev/DevToys.Core/FileHelper.cs:46, src/app/dev/DevToys.Core/FileHelper.cs:66, …
  • 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). (×6) — src/app/dev/DevToys.Core/Logging/FileLoggerProvider.cs:51, src/app/dev/DevToys.Core/Tools/GuiToolInstance.cs:92, src/app/dev/DevToys.Blazor/Components/JSStyledComponentBase.cs:67, …
  • `catch (Exception)` does nothing with the exception it caught — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch. Log it through whatever this codebase already uses to report problems, or let it propagate; if one specific failure genuinely cannot matter, catch exactly that exception type and say why in a comment on the catch. — src/app/dev/DevToys.Blazor/Components/UIElements/UIImageViewerPresenter.razor.cs:259

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 logging6.8 / 10Adequate✓ Tool-verified

Other · Code Health — Whether log calls use message templates (queryable) rather than interpolated strings.

Method: Roslyn syntax scan: every log call-site counted; interpolated-string first-argument violations flagged. Population is all log calls, not estimated. On a repository with no .NET source it reads JavaScript/TypeScript off the engine’s own token stream (test, vendored and minified paths not) with the same rule: a `trace`/`debug`/`info`/`warn`/`error`/`fatal`/`verbose`/`silly`/`http`/`log` call on a receiver named for a logger, in a package whose own or an enclosing `package.json` declares a logger that carries values as fields (pino, pino-http, nestjs-pino, Fastify, winston, bunyan, tslog, LogTape, roarr), whose first deciding argument is a template literal with substitutions; an object-literal fields argument is stepped over, a plain string message clears the call. Python is read the same way: a `debug`/`info`/`warning`/`error`/`exception`/`critical`/`log` call on a logger in a file that imports the standard library’s `logging` or structlog (loguru, which formats at the call, is not judged), whose message is a whole f-string with a non-constant field; a `%`-formatted, `.format()`-ed or concatenated message is not convicted, as in C#. PHP is read the same way: a PSR-3 level call (`emergency`…`debug`, `log`) on a logger (`$logger`, `$this->logger`, Laravel’s `Log::`, `logger()`, `\Drupal::logger()`) in a package whose `composer.json` requires a PSR-3 logger or a framework that hands one out (psr/log, Monolog, Laravel, Symfony, Drupal, CakePHP), or a file that imports one, whose message is a double-quoted string interpolating a variable; a single-quoted message clears the call, and `sprintf` or `.` concatenation is not convicted, as in C#. Dart is read the same way: a `trace`/`debug`/`info`/`warn`/`error`/`fatal` call on Sentry’s structured logger (`Sentry.logger`) whose message is a whole string literal interpolating a value (`$name`, `${…}`); the `Sentry.logger.fmt` template API clears the call. Dart that logs only through loggers with one message and no fields (package:logging, package:logger, talker, dart:developer) is not applicable rather than a reach gap. Ruby is read the same way: a `trace`/`debug`/`info`/`warn`/`error`/`fatal` call on the console gem’s `Console` (declared by a Gemfile, gemspec or Gemfile.lock, or required) or, where SemanticLogger, Ougai or dry-logger is declared or required, on a receiver named for a logger (`logger`, `@logger`, `Rails.logger`, `log`), whose first deciding argument is, as the whole argument, a double-quoted string interpolating a non-constant value (`#{…}`, `#@ivar`); a plain literal clears the call, keyword arguments are the fields, and a block, `%`-format or `+` concatenation is not convicted. Ruby that logs only through the standard Logger (Rails.logger) is not applicable rather than a reach gap. Deterministic.

  • Logging an interpolated string (`$"..."`) collapses the event to plain text — you lose the named, queryable properties structured logging exists for. Use a message template with placeholders: `LogInformation("User {UserId} did {Action}", id, action)`. If these calls go through a logging wrapper that only accepts a pre-formatted string, give the wrapper a template+args overload that forwards to the underlying logger, then migrate call sites to it. (×2) — src/app/dev/DevToys.Blazor/Core/Extensions/IJSRuntimeExtensions.cs:47, src/app/dev/DevToys.Blazor/Core/Extensions/IJSRuntimeExtensions.cs:90

What to do

  • Interpolated log message defeats structured logging
X5 · Nullable reference types8.5 / 10Strong✓ 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.

  • ~1.8 `!` suppressions per 1k syntax nodes — 247 suppression(s) across the 134823 syntax node(s) in code where nullable warnings are ENABLED, which is the only code a `!` can suppress anything in (a `!` under `#nullable disable` is inert and is not counted, and its file's nodes are not in the denominator). Each one tells the compiler to trust you about null, suppressing the very safety NRTs provide.

What to do

  • Enable <Nullable>enable</Nullable> across all projects and resolve warnings rather than suppressing with `!`.

WCAG coverage — what static analysis assessed

Statically assessed 15 of 55 WCAG 2.2 Level A/AA success criteria (27%; ≈30% of the 50 WCAG 2.1 AA criteria for EN 301 549). The other 40 require runtime or manual evaluation. Partial signal only (a clean result is necessary, not sufficient; static analysis fully verifies none). This is accessibility readiness, not a conformance claim — a WCAG conformance claim requires manual evaluation (WCAG-EM 1.0).

DimensionWCAG 2.2 A/AA criteriaCoverage
AC1 · Text alternatives1.1.1, 1.2.2, 1.2.5Partial signal
AC2 · Forms & labels1.3.1, 3.3.2, 4.1.2Partial signal
AC3 · Page structure1.4.4, 2.2.1, 2.4.1, 2.4.2, 3.1.1, 4.1.2Partial signal
AC4 · Keyboard semantics2.1.1, 2.4.3Partial signal
AC5 · ARIA correctness4.1.2Partial signal
AC6 · Visual & motion safety1.4.3, 2.4.7Partial — literal CSS only
AC7 · A11y enforcementenforcement — no page criterionEnforcement posture (process)

Not statically assessed — these 40 Level A/AA criteria need runtime or manual evaluation (WCAG-EM): 1.2.1, 1.2.3, 1.2.4, 1.3.2, 1.3.3, 1.3.4, 1.3.5, 1.4.1, 1.4.2, 1.4.5, 1.4.10, 1.4.11, 1.4.12, 1.4.13, 2.1.2, 2.1.4, 2.2.2, 2.3.1, 2.4.4, 2.4.5, 2.4.6, 2.4.11, 2.5.1, 2.5.2, 2.5.3, 2.5.4, 2.5.7, 2.5.8, 3.1.2, 3.2.1, 3.2.2, 3.2.3, 3.2.4, 3.2.6, 3.3.1, 3.3.3, 3.3.4, 3.3.7, 3.3.8, 4.1.3.

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 Health58%AdequateAcceptable, with room to improve.
Architecture72%StrongStrongest area.
Maturity46%Weak — gated by D34, M2Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Readiness35%Weak — gated by R6, P3, P7Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Security85%Adequate — gated by D30Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Accessibility38%Weak — gated by AC4, AC6Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Performance70%AdequateAcceptable, with room to improve.
Unscored — 4 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.

  • D36 Supply-chain Provenance & Signing — 1 observation(s) recorded · The CI pipeline builds and tests but publishes no released artifact — no package publish, container push, GitHub release or deployment step. Supply-chain provenance, signing and SBOM attest RELEASED artifacts, so there is nothing to attest here. Add them to the release pipeline when this repo starts shipping artifacts (a published package, a container image, a deployed service or a tagged release). Build integrity and workflow-token hygiene are reported below: they describe what the CI runs and the token it runs with, neither of which is affected by whether the pipeline ships an artifact.
  • SC1 Supply-chain hygiene — 1 observation(s) recorded · Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
  • X10 Duplicated predicate — 25 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
  • X8 JS interop contract — 40 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
Not evidenced — 2 control(s) we could not find positive evidence for

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

  • P4 Deployment & Rollback — not evidenced — no deploy/rollback/approval signal in the repo; absence of evidence is not evidence of a manual release
  • P5 DR & Backup — not evidenced — repo shows no backup/RTO/RPO controls; absence of evidence is not evidence of a working control
Not included — 37 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.

  • AX7 Slice cohesion — not applicable — not a vertical-slice architecture
  • AX9 CQS / query purity — no CQRS query handlers detected — query purity is not applicable to this codebase
  • AXB1 Runtime evidence locked — no reproducible boot — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
  • AXB2 Runtime readiness — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
  • C1 Data Protection — No personal data detected in the analyzed source — no PII-typed entity/column names (Email, FirstName, DateOfBirth, …), no ASP.NET Identity / user-account model, and no stored user credentials. GDPR data-protection controls are therefore N/A here. If this is intentional, record the no-PII posture in an ADR; if the app does process personal data, name those fields conventionally so this dimension activates.
  • C2 Access Controls — No access-control surface detected in the analyzed source — no web/app surface to authorize (no HTTP API or web-UI project) and no authorization code at all (no [Authorize]/policies, no imperative guard methods). Access control is therefore N/A here — this is a library/CLI, which is authorized by its CALLER, not by itself. If this codebase grows request handlers, the dimension reactivates and a default-deny posture is expected then.
  • C3 Audit Trail — No personal data detected in the analyzed source — no PII-typed entity/column names (Email, FirstName, DateOfBirth, …), no ASP.NET Identity / user-account model, and no stored user credentials. GDPR data-protection controls are therefore N/A here. If this is intentional, record the no-PII posture in an ADR; if the app does process personal data, name those fields conventionally so this dimension activates.
  • C4 Data Retention — No personal data detected in the analyzed source — no PII-typed entity/column names (Email, FirstName, DateOfBirth, …), no ASP.NET Identity / user-account model, and no stored user credentials. GDPR data-protection controls are therefore N/A here. If this is intentional, record the no-PII posture in an ADR; if the app does process personal data, name those fields conventionally so this dimension activates.
  • C5 Data-Subject Rights — No personal data detected in the analyzed source — no PII-typed entity/column names (Email, FirstName, DateOfBirth, …), no ASP.NET Identity / user-account model, and no stored user credentials. GDPR data-protection controls are therefore N/A here. If this is intentional, record the no-PII posture in an ADR; if the app does process personal data, name those fields conventionally so this dimension activates.
  • D11 Test Reliability — Test reliability NOT MEASURED: this repository did not build in our analyzer environment (a C#/MSBuild compiler error), so no test ever ran and flakiness could not be exercised. It is excluded from the score rather than counted as a defect. We did not read WHERE the failing diagnostic is, so this does not claim the fault is in your test code — a repository written for an older SDK band can compile for you and not for us. Run `dotnet build` on this commit: if it succeeds, the gap is ours and nothing here is a defect in your code.
  • 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
  • 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
  • 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.
  • D7 Architectural Integrity — no checkable ADRs and no dependency cycles — architectural integrity not assessed
  • D8 Code Coverage — Coverage not measured — analyzer environment
  • DM1 Domain Modelling — not scored — this repository shows 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'.
  • 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
  • R11 Import Boundaries — No recognizable feature-sliced/layered src layout — boundary rules not applicable.
  • R4 Test Coverage — the JS/TS workspace (17 production file(s)) has no JavaScript/TypeScript test, but it is 14.42% of this repository's production source and the other 85.58% carries 2,220 line(s) of test code this pass cannot read — an incidental frontend's reachability is not the repository's test posture, so it is not scored as one
  • R5 Dependency Freshness — no package-lock.json — dependency freshness not measured (would require an npm lockfile); JS/npm CVEs are scored in D30 (Dependency Vulnerabilities), which answers every ecosystem
  • S1 Web-Security Posture — No web surface detected in the analyzed source — no HTTP API or web-UI project (no controllers/minimal-API endpoints, no Razor/Blazor views) and no web middleware (HTTPS redirection, HSTS, security headers, cookies). Transport security, security headers, secure cookies, CSRF/input-validation and middleware-order controls are therefore N/A here — this is a library/CLI/worker, not a web app. Crypto hygiene was still checked and found nothing to flag. If this codebase becomes web-facing, the dimension reactivates automatically.
  • X6 Hand-rolled structured-format parsing — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
  • X7 Silent fallback defaults — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
  • X9 Subsumed condition operand — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.

Appendix A — Findings (grouped)

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 — 57 finding(s)
D17 · Explicit Debt · EmptyCatchBlock · ×24
  • EmptyCatchBlock src/app/dev/DevToys.Blazor/Components/JSStyledComponentBase.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 src/app/dev/DevToys.Blazor/Components/Layout/Popover/Popover.razor.cs:129 — empty catch block — the error is discarded with nothing recorded, so a failure here leaves no trace anywhere. Record it through whatever this codebase already uses to report problems, or let it propagate. Where swallowing one specific failure really is correct — as it often is on a teardown/dispose path where throwing would mask the original failure — catch exactly that exception type and write down WHY in a comment on the catch. Both are needed: a comment on a catch-all still swallows every failure nobody anticipated, and a note that only restates the swallow ("ignored", "do nothing") is read as no explanation at all.
  • EmptyCatchBlock src/app/dev/DevToys.Blazor/Components/Text/MonacoEditor/MonacoEditorBase.cs:126 — empty catch block — the error is discarded with nothing recorded, so a failure here leaves no trace anywhere. Record it through whatever this codebase already uses to report problems, or let it propagate. Where swallowing one specific failure really is correct — as it often is on a teardown/dispose path where throwing would mask the original failure — catch exactly that exception type and write down WHY in a comment on the catch. Both are needed: a comment on a catch-all still swallows every failure nobody anticipated, and a note that only restates the swallow ("ignored", "do nothing") is read as no explanation at all.
  • EmptyCatchBlock src/app/dev/DevToys.Blazor/Components/Text/TextBox/TextBox.razor.cs:128 — empty catch block — the error is discarded with nothing recorded, so a failure here leaves no trace anywhere. Record it through whatever this codebase already uses to report problems, or let it propagate. Where swallowing one specific failure really is correct — as it often is on a teardown/dispose path where throwing would mask the original failure — catch exactly that exception type and write down WHY in a comment on the catch. Both are needed: a comment on a catch-all still swallows every failure nobody anticipated, and a note that only restates the swallow ("ignored", "do nothing") is read as no explanation at all.
  • EmptyCatchBlock src/app/dev/DevToys.Blazor/Core/Services/DocumentEventService.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 src/app/dev/DevToys.Blazor/Core/Services/FontService.cs:87 — empty catch block — the error is discarded with nothing recorded, so a failure here leaves no trace anywhere. Record it through whatever this codebase already uses to report problems, or let it propagate. Where swallowing one specific failure really is correct — as it often is on a teardown/dispose path where throwing would mask the original failure — catch exactly that exception type and write down WHY in a comment on the catch. Both are needed: a comment on a catch-all still swallows every failure nobody anticipated, and a note that only restates the swallow ("ignored", "do nothing") is read as no explanation at all.
  • EmptyCatchBlock src/app/dev/DevToys.Blazor/Core/Services/MonacoLanguageService.cs:110 — empty catch block — the error is discarded with nothing recorded, so a failure here leaves no trace anywhere. Record it through whatever this codebase already uses to report problems, or let it propagate. Where swallowing one specific failure really is correct — as it often is on a teardown/dispose path where throwing would mask the original failure — catch exactly that exception type and write down WHY in a comment on the catch. Both are needed: a comment on a catch-all still swallows every failure nobody anticipated, and a note that only restates the swallow ("ignored", "do nothing") is read as no explanation at all.
  • EmptyCatchBlock src/app/dev/DevToys.Blazor/Core/Services/MonacoLanguageService.cs:185 — empty catch block — the error is discarded with nothing recorded, so a failure here leaves no trace anywhere. Record it through whatever this codebase already uses to report problems, or let it propagate. Where swallowing one specific failure really is correct — as it often is on a teardown/dispose path where throwing would mask the original failure — catch exactly that exception type and write down WHY in a comment on the catch. Both are needed: a comment on a catch-all still swallows every failure nobody anticipated, and a note that only restates the swallow ("ignored", "do nothing") is read as no explanation at all.
  • EmptyCatchBlock src/app/dev/DevToys.Core/FileHelper.cs:46 — empty catch block — the error is discarded with nothing recorded, so a failure here leaves no trace anywhere. Record it through whatever this codebase already uses to report problems, or let it propagate. Where swallowing one specific failure really is correct — as it often is on a teardown/dispose path where throwing would mask the original failure — catch exactly that exception type and write down WHY in a comment on the catch. Both are needed: a comment on a catch-all still swallows every failure nobody anticipated, and a note that only restates the swallow ("ignored", "do nothing") is read as no explanation at all.
  • EmptyCatchBlock src/app/dev/DevToys.Core/FileHelper.cs:66 — empty catch block — the error is discarded with nothing recorded, so a failure here leaves no trace anywhere. Record it through whatever this codebase already uses to report problems, or let it propagate. Where swallowing one specific failure really is correct — as it often is on a teardown/dispose path where throwing would mask the original failure — catch exactly that exception type and write down WHY in a comment on the catch. Both are needed: a comment on a catch-all still swallows every failure nobody anticipated, and a note that only restates the swallow ("ignored", "do nothing") is read as no explanation at all.
  • EmptyCatchBlock src/app/dev/DevToys.Core/Logging/FileLoggerProvider.cs:51 — empty catch block — the error is discarded with nothing recorded, so a failure here leaves no trace anywhere. Record it through whatever this codebase already uses to report problems, or let it propagate. Where swallowing one specific failure really is correct — as it often is on a teardown/dispose path where throwing would mask the original failure — catch exactly that exception type and write down WHY in a comment on the catch. Both are needed: a comment on a catch-all still swallows every failure nobody anticipated, and a note that only restates the swallow ("ignored", "do nothing") is read as no explanation at all.
  • EmptyCatchBlock src/app/dev/DevToys.Core/Logging/FileLoggerProvider.cs:66 — empty catch block — the error is discarded with nothing recorded, so a failure here leaves no trace anywhere. Record it through whatever this codebase already uses to report problems, or let it propagate. Where swallowing one specific failure really is correct — as it often is on a teardown/dispose path where throwing would mask the original failure — catch exactly that exception type and write down WHY in a comment on the catch. Both are needed: a comment on a catch-all still swallows every failure nobody anticipated, and a note that only restates the swallow ("ignored", "do nothing") is read as no explanation at all.
  • EmptyCatchBlock src/app/dev/DevToys.Core/Logging/FileLoggerProvider.cs:108 — empty catch block — the error is discarded with nothing recorded, so a failure here leaves no trace anywhere. Record it through whatever this codebase already uses to report problems, or let it propagate. Where swallowing one specific failure really is correct — as it often is on a teardown/dispose path where throwing would mask the original failure — catch exactly that exception type and write down WHY in a comment on the catch. Both are needed: a comment on a catch-all still swallows every failure nobody anticipated, and a note that only restates the swallow ("ignored", "do nothing") is read as no explanation at all.
  • EmptyCatchBlock src/app/dev/DevToys.Core/Logging/FileLoggerProvider.cs:129 — empty catch block — the error is discarded with nothing recorded, so a failure here leaves no trace anywhere. Record it through whatever this codebase already uses to report problems, or let it propagate. Where swallowing one specific failure really is correct — as it often is on a teardown/dispose path where throwing would mask the original failure — catch exactly that exception type and write down WHY in a comment on the catch. Both are needed: a comment on a catch-all still swallows every failure nobody anticipated, and a note that only restates the swallow ("ignored", "do nothing") is read as no explanation at all.
  • EmptyCatchBlock src/app/dev/DevToys.Core/Mef/RecursiveDirectoryCatalog.cs:139 — empty catch block — the error is discarded with nothing recorded, so a failure here leaves no trace anywhere. Record it through whatever this codebase already uses to report problems, or let it propagate. Where swallowing one specific failure really is correct — as it often is on a teardown/dispose path where throwing would mask the original failure — catch exactly that exception type and write down WHY in a comment on the catch. Both are needed: a comment on a catch-all still swallows every failure nobody anticipated, and a note that only restates the swallow ("ignored", "do nothing") is read as no explanation at all.
  • EmptyCatchBlock src/app/dev/DevToys.Core/Tools/GuiToolInstance.cs:92 — empty catch block — the error is discarded with nothing recorded, so a failure here leaves no trace anywhere. Record it through whatever this codebase already uses to report problems, or let it propagate. Where swallowing one specific failure really is correct — as it often is on a teardown/dispose path where throwing would mask the original failure — catch exactly that exception type and write down WHY in a comment on the catch. Both are needed: a comment on a catch-all still swallows every failure nobody anticipated, and a note that only restates the swallow ("ignored", "do nothing") is read as no explanation at all.
  • EmptyCatchBlock src/app/dev/DevToys.Core/Tools/GuiToolInstance.cs:113 — empty catch block — the error is discarded with nothing recorded, so a failure here leaves no trace anywhere. Record it through whatever this codebase already uses to report problems, or let it propagate. Where swallowing one specific failure really is correct — as it often is on a teardown/dispose path where throwing would mask the original failure — catch exactly that exception type and write down WHY in a comment on the catch. Both are needed: a comment on a catch-all still swallows every failure nobody anticipated, and a note that only restates the swallow ("ignored", "do nothing") is read as no explanation at all.
  • EmptyCatchBlock src/app/dev/DevToys.Core/Tools/GuiToolInstance.cs:138 — empty catch block — the error is discarded with nothing recorded, so a failure here leaves no trace anywhere. Record it through whatever this codebase already uses to report problems, or let it propagate. Where swallowing one specific failure really is correct — as it often is on a teardown/dispose path where throwing would mask the original failure — catch exactly that exception type and write down WHY in a comment on the catch. Both are needed: a comment on a catch-all still swallows every failure nobody anticipated, and a note that only restates the swallow ("ignored", "do nothing") is read as no explanation at all.
  • EmptyCatchBlock src/app/dev/platforms/desktop/DevToys.CLI/Core/OneOfParser.cs:324 — empty catch block — the error is discarded with nothing recorded, so a failure here leaves no trace anywhere. Record it through whatever this codebase already uses to report problems, or let it propagate. Where swallowing one specific failure really is correct — as it often is on a teardown/dispose path where throwing would mask the original failure — catch exactly that exception type and write down WHY in a comment on the catch. Both are needed: a comment on a catch-all still swallows every failure nobody anticipated, and a note that only restates the swallow ("ignored", "do nothing") is read as no explanation at all.
  • EmptyCatchBlock src/app/dev/platforms/desktop/DevToys.Linux/Components/BlazorWebView/BlazorWebViewManager.cs:110 — empty catch block — the error is discarded with nothing recorded, so a failure here leaves no trace anywhere. Record it through whatever this codebase already uses to report problems, or let it propagate. Where swallowing one specific failure really is correct — as it often is on a teardown/dispose path where throwing would mask the original failure — catch exactly that exception type and write down WHY in a comment on the catch. Both are needed: a comment on a catch-all still swallows every failure nobody anticipated, and a note that only restates the swallow ("ignored", "do nothing") is read as no explanation at all.
  • EmptyCatchBlock src/app/dev/platforms/desktop/DevToys.Linux/Components/BlazorWebView/BlazorWebViewManager.cs:153 — empty catch block — the error is discarded with nothing recorded, so a failure here leaves no trace anywhere. Record it through whatever this codebase already uses to report problems, or let it propagate. Where swallowing one specific failure really is correct — as it often is on a teardown/dispose path where throwing would mask the original failure — catch exactly that exception type and write down WHY in a comment on the catch. Both are needed: a comment on a catch-all still swallows every failure nobody anticipated, and a note that only restates the swallow ("ignored", "do nothing") is read as no explanation at all.
  • EmptyCatchBlock src/app/dev/platforms/desktop/DevToys.Linux/Core/FileStorage.cs:103 — empty catch block — the error is discarded with nothing recorded, so a failure here leaves no trace anywhere. Record it through whatever this codebase already uses to report problems, or let it propagate. Where swallowing one specific failure really is correct — as it often is on a teardown/dispose path where throwing would mask the original failure — catch exactly that exception type and write down WHY in a comment on the catch. Both are needed: a comment on a catch-all still swallows every failure nobody anticipated, and a note that only restates the swallow ("ignored", "do nothing") is read as no explanation at all.
  • EmptyCatchBlock src/app/dev/platforms/desktop/DevToys.Windows/Controls/MicaWindowWithOverlay.xaml.cs:243 — empty catch block — the error is discarded with nothing recorded, so a failure here leaves no trace anywhere. Record it through whatever this codebase already uses to report problems, or let it propagate. Where swallowing one specific failure really is correct — as it often is on a teardown/dispose path where throwing would mask the original failure — catch exactly that exception type and write down WHY in a comment on the catch. Both are needed: a comment on a catch-all still swallows every failure nobody anticipated, and a note that only restates the swallow ("ignored", "do nothing") is read as no explanation at all.
  • EmptyCatchBlock src/app/dev/platforms/desktop/DevToys.Windows/Controls/MicaWindowWithOverlay.xaml.cs:281 — 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.
D29 · Static Analysis (SAST) · REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
D30 · Dependency Vulnerabilities · High CVE · ×9
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
AX3 · Project dependency cycles · Namespace dependency cycle · ×3
  • Namespace dependency cycle src/app/dev/DevToys.Core/Tools/ViewItems/GuiToolViewItem.cs:8 — The namespaces DevToys.Core.Tools ↔ DevToys.Core.Tools.ViewItems depend on each other. The lightest dependency in the cycle is DevToys.Core.Tools.ViewItems → DevToys.Core.Tools (DevToys.Core.Tools.ViewItems.GuiToolViewItem → DevToys.Core.Tools.GuiToolInstance, 1 type pair(s)); cut that one first, e.g. by moving the shared type to a namespace both can use or inverting it behind an interface.
  • Namespace dependency cycle src/app/dev/DevToys.Blazor/Components/Text/MonacoEditor/Monaco/Editor/ActionDescriptor.cs:12 — The namespaces DevToys.Blazor.Components ↔ DevToys.Blazor.Components.Monaco ↔ DevToys.Blazor.Components.Monaco.Editor ↔ DevToys.Blazor.Components.Monaco.Languages ↔ DevToys.Blazor.Components.UIElements ↔ DevToys.Blazor.Core.Services depend on each other. The lightest dependency in the cycle is DevToys.Blazor.Components.Monaco.Editor → DevToys.Blazor.Components (DevToys.Blazor.Components.Monaco.Editor.ActionDescriptor → DevToys.Blazor.Components.RicherMonacoEditorBase, 1 type pair(s)); cut that one first, e.g. by moving the shared type to a namespace both can use or inverting it behind an interface.
  • Namespace dependency cycle src/app/dev/platforms/desktop/DevToys.Windows/Controls/MicaWindowWithOverlay.xaml.cs:11 — The namespaces DevToys.Windows.Controls ↔ DevToys.Windows.Core depend on each other. The lightest dependency in the cycle is DevToys.Windows.Controls → DevToys.Windows.Core (DevToys.Windows.Controls.MicaWindowWithOverlay → DevToys.Windows.Core.EfficiencyModeService, 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.
AC1 · Text alternatives · <img> without a text alternative · ×1
  • <img> without a text alternative src/app/dev/DevToys.Blazor/Components/UIElements/UITextInputWrapper.razor:120 — An image with no alt (and no aria-label/aria-labelledby) is unreadable to assistive tech. Add alt — alt="" if it's purely decorative.
AC3 · Page structure · <iframe> without a title · ×1
  • <iframe> without a title src/app/dev/DevToys.Blazor/Components/UIElements/UIWebViewPresenter.razor:32 — An iframe with no title (or an empty one) is announced only as "frame". Add a non-empty title describing its content, or an aria-label.
AC3 · Page structure · Routed page without a <PageTitle> · ×1
  • Routed page without a <PageTitle> src/app/dev/DevToys.Blazor/Pages/Index.razor:12 — A route with no <PageTitle> gives no name in the tab, history or screen-reader page list — the host's <HeadOutlet /> projects whatever title the routed component supplies, and this one supplies none. Add a <PageTitle> to this component (a literal <title> in the host document would be overwritten by the outlet).
AC3 · Page structure · Viewport restricts zoom · ×1
  • Viewport restricts zoom src/app/dev/platforms/desktop/DevToys.Windows/wwwroot/index.html:5 — user-scalable=no/0 or a maximum-scale below 2 stops low-vision users zooming to 200%. Remove the zoom restriction from the viewport meta.
AC4 · Keyboard semantics · Hover-only interaction on <div> · ×1
  • Hover-only interaction on <div> src/app/dev/DevToys.Blazor/Components/Collections/DataGrid/DataGridColumnHeader.razor:12 — This <div> binds mouse-enter and mouse-leave and nothing else — no click, no key handler, no focus handler, and no tabindex="0", so it cannot even take focus. A keyboard user cannot hover, so whatever the pair reveals or highlights is reachable with a mouse only. Bind the same state to focus/blur as well, and add tabindex="0"="0" so the element can receive that focus.
AC4 · Keyboard semantics · Click handler on a non-interactive <div> · ×1
  • Click handler on a non-interactive <div> src/app/dev/DevToys.Blazor/Components/Layout/Overlay/Overlay.razor:6 — A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabindex="0" + a key handler.
AC5 · ARIA correctness · aria-expanded on a <div> with no role to carry it · ×1
  • aria-expanded on a <div> with no role to carry it src/app/dev/DevToys.Blazor/Components/Layout/Expander/Expander.razor:38 — A plain <div> has the implicit role "generic", which supports no ARIA states, so this aria-expanded is dropped and assistive tech is never told the state at all. Put aria-expanded on the element that owns the behaviour (the button or control the user operates), or give this <div> a role that supports aria-expanded.
AX4 · Dependency direction · Dependency-rule violation · ×1
  • Dependency-rule violation: DevToys.Core (Domain) → DevToys.Api (Web) src/app/dev/DevToys.Core/DevToys.Core.csproj:6 — `DevToys.Core` is a Domain project but references `DevToys.Api`, a Web project. The clean-architecture rule is that dependencies point INWARD — the domain/application core must not depend on outer layers (infrastructure/web). Invert it: define the abstraction in the inner layer and implement it in the outer one.
D17 · Explicit Debt · NoWarnInCsproj · ×1
  • NoWarnInCsproj — 6 warning codes suppressed in one element src/build/_build.csproj:8 — A single <NoWarn> suppresses 6 warning codes (CS0649;CS0169;CA1050;CA1822;CA2211;IDE1006) in one stroke — one team-wide decision, not 6 independent debts. Review the set centrally rather than code-by-code; each code you can re-enable is one less blanket suppression. (Every code still counts toward the score and metrics.)
D29 · Static Analysis (SAST) · REDACTED · ×1
  • REDACTED
D30 · Dependency Vulnerabilities · Critical CVE · ×1
  • REDACTED
Serious — 361 finding(s)
X8 · JS interop contract · Unresolved JS interop binding · ×40
  • Unresolved JS interop binding src/app/dev/DevToys.Blazor/Components/Collections/DataGrid/DataGrid.razor.cs:87 — `getActualHeight` is invoked from C# here, and no definition of that name was found by the search this dimension ran: 4 first-party JavaScript file(s) (.js/.mjs/.cjs, vendored trees excluded) plus 74 markup file(s) scanned for inline <script> blocks (.html/.cshtml/.razor). NOT searched: scripts fetched or injected at runtime, and vendored/dynamically-loaded bundles — a definition living in one of those is invisible here. To settle it, grep the repository for `getActualHeight`. If it is defined nowhere, this call throws or silently no-ops at runtime, and a swallowed interop catch will hide it — define it, or invoke a wrapper that exists.
  • Unresolved JS interop binding src/app/dev/DevToys.Blazor/Components/Collections/DataGrid/DataGridColumnHeader.razor.cs:68 — `getActualWidth` is invoked from C# here, and no definition of that name was found by the search this dimension ran: 4 first-party JavaScript file(s) (.js/.mjs/.cjs, vendored trees excluded) plus 74 markup file(s) scanned for inline <script> blocks (.html/.cshtml/.razor). NOT searched: scripts fetched or injected at runtime, and vendored/dynamically-loaded bundles — a definition living in one of those is invisible here. To settle it, grep the repository for `getActualWidth`. If it is defined nowhere, this call throws or silently no-ops at runtime, and a swallowed interop catch will hide it — define it, or invoke a wrapper that exists.
  • Unresolved JS interop binding src/app/dev/DevToys.Blazor/Components/Text/MonacoEditor/Monaco/TextModel.cs:32 — `devtoys.MonacoEditor.TextModel.getVersionId` is invoked from C# here, and no definition of that name was found by the search this dimension ran: 4 first-party JavaScript file(s) (.js/.mjs/.cjs, vendored trees excluded) plus 74 markup file(s) scanned for inline <script> blocks (.html/.cshtml/.razor). NOT searched: scripts fetched or injected at runtime, and vendored/dynamically-loaded bundles — a definition living in one of those is invisible here. To settle it, grep the repository for `devtoys.MonacoEditor.TextModel.getVersionId`. If it is defined nowhere, this call throws or silently no-ops at runtime, and a swallowed interop catch will hide it — define it, or invoke a wrapper that exists.
  • Unresolved JS interop binding src/app/dev/DevToys.Blazor/Components/Text/MonacoEditor/Monaco/TextModel.cs:40 — `devtoys.MonacoEditor.TextModel.getAlternativeVersionId` is invoked from C# here, and no definition of that name was found by the search this dimension ran: 4 first-party JavaScript file(s) (.js/.mjs/.cjs, vendored trees excluded) plus 74 markup file(s) scanned for inline <script> blocks (.html/.cshtml/.razor). NOT searched: scripts fetched or injected at runtime, and vendored/dynamically-loaded bundles — a definition living in one of those is invisible here. To settle it, grep the repository for `devtoys.MonacoEditor.TextModel.getAlternativeVersionId`. If it is defined nowhere, this call throws or silently no-ops at runtime, and a swallowed interop catch will hide it — define it, or invoke a wrapper that exists.
  • Unresolved JS interop binding src/app/dev/DevToys.Blazor/Components/Text/MonacoEditor/Monaco/TextModel.cs:55 — `devtoys.MonacoEditor.TextModel.getValue` is invoked from C# here, and no definition of that name was found by the search this dimension ran: 4 first-party JavaScript file(s) (.js/.mjs/.cjs, vendored trees excluded) plus 74 markup file(s) scanned for inline <script> blocks (.html/.cshtml/.razor). NOT searched: scripts fetched or injected at runtime, and vendored/dynamically-loaded bundles — a definition living in one of those is invisible here. To settle it, grep the repository for `devtoys.MonacoEditor.TextModel.getValue`. If it is defined nowhere, this call throws or silently no-ops at runtime, and a swallowed interop catch will hide it — define it, or invoke a wrapper that exists.
  • Unresolved JS interop binding src/app/dev/DevToys.Blazor/Components/Text/MonacoEditor/Monaco/TextModel.cs:61 — `devtoys.MonacoEditor.TextModel.getValueLength` is invoked from C# here, and no definition of that name was found by the search this dimension ran: 4 first-party JavaScript file(s) (.js/.mjs/.cjs, vendored trees excluded) plus 74 markup file(s) scanned for inline <script> blocks (.html/.cshtml/.razor). NOT searched: scripts fetched or injected at runtime, and vendored/dynamically-loaded bundles — a definition living in one of those is invisible here. To settle it, grep the repository for `devtoys.MonacoEditor.TextModel.getValueLength`. If it is defined nowhere, this call throws or silently no-ops at runtime, and a swallowed interop catch will hide it — define it, or invoke a wrapper that exists.
  • Unresolved JS interop binding src/app/dev/DevToys.Blazor/Components/Text/MonacoEditor/Monaco/TextModel.cs:70 — `devtoys.MonacoEditor.TextModel.getValueInRange` is invoked from C# here, and no definition of that name was found by the search this dimension ran: 4 first-party JavaScript file(s) (.js/.mjs/.cjs, vendored trees excluded) plus 74 markup file(s) scanned for inline <script> blocks (.html/.cshtml/.razor). NOT searched: scripts fetched or injected at runtime, and vendored/dynamically-loaded bundles — a definition living in one of those is invisible here. To settle it, grep the repository for `devtoys.MonacoEditor.TextModel.getValueInRange`. If it is defined nowhere, this call throws or silently no-ops at runtime, and a swallowed interop catch will hide it — define it, or invoke a wrapper that exists.
  • Unresolved JS interop binding src/app/dev/DevToys.Blazor/Components/Text/MonacoEditor/Monaco/TextModel.cs:78 — `devtoys.MonacoEditor.TextModel.getValueLengthInRange` is invoked from C# here, and no definition of that name was found by the search this dimension ran: 4 first-party JavaScript file(s) (.js/.mjs/.cjs, vendored trees excluded) plus 74 markup file(s) scanned for inline <script> blocks (.html/.cshtml/.razor). NOT searched: scripts fetched or injected at runtime, and vendored/dynamically-loaded bundles — a definition living in one of those is invisible here. To settle it, grep the repository for `devtoys.MonacoEditor.TextModel.getValueLengthInRange`. If it is defined nowhere, this call throws or silently no-ops at runtime, and a swallowed interop catch will hide it — define it, or invoke a wrapper that exists.
  • Unresolved JS interop binding src/app/dev/DevToys.Blazor/Components/Text/MonacoEditor/Monaco/TextModel.cs:85 — `devtoys.MonacoEditor.TextModel.getCharacterCountInRange` is invoked from C# here, and no definition of that name was found by the search this dimension ran: 4 first-party JavaScript file(s) (.js/.mjs/.cjs, vendored trees excluded) plus 74 markup file(s) scanned for inline <script> blocks (.html/.cshtml/.razor). NOT searched: scripts fetched or injected at runtime, and vendored/dynamically-loaded bundles — a definition living in one of those is invisible here. To settle it, grep the repository for `devtoys.MonacoEditor.TextModel.getCharacterCountInRange`. If it is defined nowhere, this call throws or silently no-ops at runtime, and a swallowed interop catch will hide it — define it, or invoke a wrapper that exists.
  • Unresolved JS interop binding src/app/dev/DevToys.Blazor/Components/Text/MonacoEditor/Monaco/TextModel.cs:91 — `devtoys.MonacoEditor.TextModel.getLineCount` is invoked from C# here, and no definition of that name was found by the search this dimension ran: 4 first-party JavaScript file(s) (.js/.mjs/.cjs, vendored trees excluded) plus 74 markup file(s) scanned for inline <script> blocks (.html/.cshtml/.razor). NOT searched: scripts fetched or injected at runtime, and vendored/dynamically-loaded bundles — a definition living in one of those is invisible here. To settle it, grep the repository for `devtoys.MonacoEditor.TextModel.getLineCount`. If it is defined nowhere, this call throws or silently no-ops at runtime, and a swallowed interop catch will hide it — define it, or invoke a wrapper that exists.
  • Unresolved JS interop binding src/app/dev/DevToys.Blazor/Components/Text/MonacoEditor/Monaco/TextModel.cs:97 — `devtoys.MonacoEditor.TextModel.getLineContent` is invoked from C# here, and no definition of that name was found by the search this dimension ran: 4 first-party JavaScript file(s) (.js/.mjs/.cjs, vendored trees excluded) plus 74 markup file(s) scanned for inline <script> blocks (.html/.cshtml/.razor). NOT searched: scripts fetched or injected at runtime, and vendored/dynamically-loaded bundles — a definition living in one of those is invisible here. To settle it, grep the repository for `devtoys.MonacoEditor.TextModel.getLineContent`. If it is defined nowhere, this call throws or silently no-ops at runtime, and a swallowed interop catch will hide it — define it, or invoke a wrapper that exists.
  • Unresolved JS interop binding src/app/dev/DevToys.Blazor/Components/Text/MonacoEditor/Monaco/TextModel.cs:103 — `devtoys.MonacoEditor.TextModel.getLineLength` is invoked from C# here, and no definition of that name was found by the search this dimension ran: 4 first-party JavaScript file(s) (.js/.mjs/.cjs, vendored trees excluded) plus 74 markup file(s) scanned for inline <script> blocks (.html/.cshtml/.razor). NOT searched: scripts fetched or injected at runtime, and vendored/dynamically-loaded bundles — a definition living in one of those is invisible here. To settle it, grep the repository for `devtoys.MonacoEditor.TextModel.getLineLength`. If it is defined nowhere, this call throws or silently no-ops at runtime, and a swallowed interop catch will hide it — define it, or invoke a wrapper that exists.
  • Unresolved JS interop binding src/app/dev/DevToys.Blazor/Components/Text/MonacoEditor/Monaco/TextModel.cs:109 — `devtoys.MonacoEditor.TextModel.getLinesContent` is invoked from C# here, and no definition of that name was found by the search this dimension ran: 4 first-party JavaScript file(s) (.js/.mjs/.cjs, vendored trees excluded) plus 74 markup file(s) scanned for inline <script> blocks (.html/.cshtml/.razor). NOT searched: scripts fetched or injected at runtime, and vendored/dynamically-loaded bundles — a definition living in one of those is invisible here. To settle it, grep the repository for `devtoys.MonacoEditor.TextModel.getLinesContent`. If it is defined nowhere, this call throws or silently no-ops at runtime, and a swallowed interop catch will hide it — define it, or invoke a wrapper that exists.
  • Unresolved JS interop binding src/app/dev/DevToys.Blazor/Components/Text/MonacoEditor/Monaco/TextModel.cs:116 — `devtoys.MonacoEditor.TextModel.getEOL` is invoked from C# here, and no definition of that name was found by the search this dimension ran: 4 first-party JavaScript file(s) (.js/.mjs/.cjs, vendored trees excluded) plus 74 markup file(s) scanned for inline <script> blocks (.html/.cshtml/.razor). NOT searched: scripts fetched or injected at runtime, and vendored/dynamically-loaded bundles — a definition living in one of those is invisible here. To settle it, grep the repository for `devtoys.MonacoEditor.TextModel.getEOL`. If it is defined nowhere, this call throws or silently no-ops at runtime, and a swallowed interop catch will hide it — define it, or invoke a wrapper that exists.
  • Unresolved JS interop binding src/app/dev/DevToys.Blazor/Components/Text/MonacoEditor/Monaco/TextModel.cs:122 — `devtoys.MonacoEditor.TextModel.getEndOfLineSequence` is invoked from C# here, and no definition of that name was found by the search this dimension ran: 4 first-party JavaScript file(s) (.js/.mjs/.cjs, vendored trees excluded) plus 74 markup file(s) scanned for inline <script> blocks (.html/.cshtml/.razor). NOT searched: scripts fetched or injected at runtime, and vendored/dynamically-loaded bundles — a definition living in one of those is invisible here. To settle it, grep the repository for `devtoys.MonacoEditor.TextModel.getEndOfLineSequence`. If it is defined nowhere, this call throws or silently no-ops at runtime, and a swallowed interop catch will hide it — define it, or invoke a wrapper that exists.
  • Unresolved JS interop binding src/app/dev/DevToys.Blazor/Components/Text/MonacoEditor/Monaco/TextModel.cs:128 — `devtoys.MonacoEditor.TextModel.getLineMinColumn` is invoked from C# here, and no definition of that name was found by the search this dimension ran: 4 first-party JavaScript file(s) (.js/.mjs/.cjs, vendored trees excluded) plus 74 markup file(s) scanned for inline <script> blocks (.html/.cshtml/.razor). NOT searched: scripts fetched or injected at runtime, and vendored/dynamically-loaded bundles — a definition living in one of those is invisible here. To settle it, grep the repository for `devtoys.MonacoEditor.TextModel.getLineMinColumn`. If it is defined nowhere, this call throws or silently no-ops at runtime, and a swallowed interop catch will hide it — define it, or invoke a wrapper that exists.
  • Unresolved JS interop binding src/app/dev/DevToys.Blazor/Components/Text/MonacoEditor/Monaco/TextModel.cs:134 — `devtoys.MonacoEditor.TextModel.getLineMaxColumn` is invoked from C# here, and no definition of that name was found by the search this dimension ran: 4 first-party JavaScript file(s) (.js/.mjs/.cjs, vendored trees excluded) plus 74 markup file(s) scanned for inline <script> blocks (.html/.cshtml/.razor). NOT searched: scripts fetched or injected at runtime, and vendored/dynamically-loaded bundles — a definition living in one of those is invisible here. To settle it, grep the repository for `devtoys.MonacoEditor.TextModel.getLineMaxColumn`. If it is defined nowhere, this call throws or silently no-ops at runtime, and a swallowed interop catch will hide it — define it, or invoke a wrapper that exists.
  • Unresolved JS interop binding src/app/dev/DevToys.Blazor/Components/Text/MonacoEditor/Monaco/TextModel.cs:141 — `devtoys.MonacoEditor.TextModel.getLineFirstNonWhitespaceColumn` is invoked from C# here, and no definition of that name was found by the search this dimension ran: 4 first-party JavaScript file(s) (.js/.mjs/.cjs, vendored trees excluded) plus 74 markup file(s) scanned for inline <script> blocks (.html/.cshtml/.razor). NOT searched: scripts fetched or injected at runtime, and vendored/dynamically-loaded bundles — a definition living in one of those is invisible here. To settle it, grep the repository for `devtoys.MonacoEditor.TextModel.getLineFirstNonWhitespaceColumn`. If it is defined nowhere, this call throws or silently no-ops at runtime, and a swallowed interop catch will hide it — define it, or invoke a wrapper that exists.
  • Unresolved JS interop binding src/app/dev/DevToys.Blazor/Components/Text/MonacoEditor/Monaco/TextModel.cs:148 — `devtoys.MonacoEditor.TextModel.getLineLastNonWhitespaceColumn` is invoked from C# here, and no definition of that name was found by the search this dimension ran: 4 first-party JavaScript file(s) (.js/.mjs/.cjs, vendored trees excluded) plus 74 markup file(s) scanned for inline <script> blocks (.html/.cshtml/.razor). NOT searched: scripts fetched or injected at runtime, and vendored/dynamically-loaded bundles — a definition living in one of those is invisible here. To settle it, grep the repository for `devtoys.MonacoEditor.TextModel.getLineLastNonWhitespaceColumn`. If it is defined nowhere, this call throws or silently no-ops at runtime, and a swallowed interop catch will hide it — define it, or invoke a wrapper that exists.
  • Unresolved JS interop binding src/app/dev/DevToys.Blazor/Components/Text/MonacoEditor/Monaco/TextModel.cs:154 — `devtoys.MonacoEditor.TextModel.validatePosition` is invoked from C# here, and no definition of that name was found by the search this dimension ran: 4 first-party JavaScript file(s) (.js/.mjs/.cjs, vendored trees excluded) plus 74 markup file(s) scanned for inline <script> blocks (.html/.cshtml/.razor). NOT searched: scripts fetched or injected at runtime, and vendored/dynamically-loaded bundles — a definition living in one of those is invisible here. To settle it, grep the repository for `devtoys.MonacoEditor.TextModel.validatePosition`. If it is defined nowhere, this call throws or silently no-ops at runtime, and a swallowed interop catch will hide it — define it, or invoke a wrapper that exists.
  • Unresolved JS interop binding src/app/dev/DevToys.Blazor/Components/Text/MonacoEditor/Monaco/TextModel.cs:167 — `devtoys.MonacoEditor.TextModel.modifyPosition` is invoked from C# here, and no definition of that name was found by the search this dimension ran: 4 first-party JavaScript file(s) (.js/.mjs/.cjs, vendored trees excluded) plus 74 markup file(s) scanned for inline <script> blocks (.html/.cshtml/.razor). NOT searched: scripts fetched or injected at runtime, and vendored/dynamically-loaded bundles — a definition living in one of those is invisible here. To settle it, grep the repository for `devtoys.MonacoEditor.TextModel.modifyPosition`. If it is defined nowhere, this call throws or silently no-ops at runtime, and a swallowed interop catch will hide it — define it, or invoke a wrapper that exists.
  • Unresolved JS interop binding src/app/dev/DevToys.Blazor/Components/Text/MonacoEditor/Monaco/TextModel.cs:173 — `devtoys.MonacoEditor.TextModel.validateRange` is invoked from C# here, and no definition of that name was found by the search this dimension ran: 4 first-party JavaScript file(s) (.js/.mjs/.cjs, vendored trees excluded) plus 74 markup file(s) scanned for inline <script> blocks (.html/.cshtml/.razor). NOT searched: scripts fetched or injected at runtime, and vendored/dynamically-loaded bundles — a definition living in one of those is invisible here. To settle it, grep the repository for `devtoys.MonacoEditor.TextModel.validateRange`. If it is defined nowhere, this call throws or silently no-ops at runtime, and a swallowed interop catch will hide it — define it, or invoke a wrapper that exists.
  • Unresolved JS interop binding src/app/dev/DevToys.Blazor/Components/Text/MonacoEditor/Monaco/TextModel.cs:184 — `devtoys.MonacoEditor.TextModel.getOffsetAt` is invoked from C# here, and no definition of that name was found by the search this dimension ran: 4 first-party JavaScript file(s) (.js/.mjs/.cjs, vendored trees excluded) plus 74 markup file(s) scanned for inline <script> blocks (.html/.cshtml/.razor). NOT searched: scripts fetched or injected at runtime, and vendored/dynamically-loaded bundles — a definition living in one of those is invisible here. To settle it, grep the repository for `devtoys.MonacoEditor.TextModel.getOffsetAt`. If it is defined nowhere, this call throws or silently no-ops at runtime, and a swallowed interop catch will hide it — define it, or invoke a wrapper that exists.
  • Unresolved JS interop binding src/app/dev/DevToys.Blazor/Components/Text/MonacoEditor/Monaco/TextModel.cs:193 — `devtoys.MonacoEditor.TextModel.getPositionAt` is invoked from C# here, and no definition of that name was found by the search this dimension ran: 4 first-party JavaScript file(s) (.js/.mjs/.cjs, vendored trees excluded) plus 74 markup file(s) scanned for inline <script> blocks (.html/.cshtml/.razor). NOT searched: scripts fetched or injected at runtime, and vendored/dynamically-loaded bundles — a definition living in one of those is invisible here. To settle it, grep the repository for `devtoys.MonacoEditor.TextModel.getPositionAt`. If it is defined nowhere, this call throws or silently no-ops at runtime, and a swallowed interop catch will hide it — define it, or invoke a wrapper that exists.
  • Unresolved JS interop binding src/app/dev/DevToys.Blazor/Components/Text/MonacoEditor/Monaco/TextModel.cs:199 — `devtoys.MonacoEditor.TextModel.getFullModelRange` is invoked from C# here, and no definition of that name was found by the search this dimension ran: 4 first-party JavaScript file(s) (.js/.mjs/.cjs, vendored trees excluded) plus 74 markup file(s) scanned for inline <script> blocks (.html/.cshtml/.razor). NOT searched: scripts fetched or injected at runtime, and vendored/dynamically-loaded bundles — a definition living in one of those is invisible here. To settle it, grep the repository for `devtoys.MonacoEditor.TextModel.getFullModelRange`. If it is defined nowhere, this call throws or silently no-ops at runtime, and a swallowed interop catch will hide it — define it, or invoke a wrapper that exists.
  • + 15 more in this group — see findings.md.
X2 · Cancellation propagation · Async method without CancellationToken · ×36
  • Async method without CancellationToken: SaveAllSettingsAsync src/app/dev/platforms/desktop/DevToys.CLI/Core/Settings/SettingsStorage.cs:77 — No CancellationToken parameter — this work can't be stopped early once started.
  • Async method without CancellationToken: MainAsync src/app/dev/platforms/desktop/DevToys.CLI/Program.cs:64 — No CancellationToken parameter — this work can't be stopped early once started.
  • Async method without CancellationToken: OpenDialogAsync src/app/dev/DevToys.Api/Tool/GUI/Components/UIToolView.cs:135 — No CancellationToken parameter — this work can't be stopped early once started.
  • Async method without CancellationToken: InstallExtensionAsync src/app/dev/DevToys.Blazor/BuiltInTools/ExtensionsManager/ExtensionInstallationManager.cs:88 — No CancellationToken parameter — this work can't be stopped early once started.
  • Async method without CancellationToken: CheckForAnyUpdateAsync src/app/dev/DevToys.Blazor/BuiltInTools/ExtensionsManager/ExtensionInstallationManager.cs:133 — No CancellationToken parameter — this work can't be stopped early once started.
  • Async method without CancellationToken: CheckForUpdateAsync src/app/dev/DevToys.Blazor/BuiltInTools/ExtensionsManager/ExtensionInstallationManager.cs:160 — No CancellationToken parameter — this work can't be stopped early once started.
  • Async method without CancellationToken: OnInstallExtensionButtonClickAsync REDACTED:151 — No CancellationToken parameter — this work can't be stopped early once started.
  • Async method without CancellationToken: LoadExtensionListAsync REDACTED:192 — No CancellationToken parameter — this work can't be stopped early once started.
  • Async method without CancellationToken: ShowWarningUseThirdPartyExtensionMessageBoxAsync REDACTED:297 — No CancellationToken parameter — this work can't be stopped early once started.
  • Async method without CancellationToken: ShowExtensionAlreadyInstalledMessageBoxAsync REDACTED:346 — No CancellationToken parameter — this work can't be stopped early once started.
  • Async method without CancellationToken: ShowExtensionErrorMessageBoxAsync REDACTED:372 — No CancellationToken parameter — this work can't be stopped early once started.
  • Async method without CancellationToken: OnCopyVersionNumberButtonClickAsync src/app/dev/DevToys.Blazor/BuiltInTools/Settings/SettingsGuiTool.cs:334 — No CancellationToken parameter — this work can't be stopped early once started.
  • Async method without CancellationToken: GetActualHeightAsync src/app/dev/DevToys.Blazor/Components/Collections/DataGrid/DataGrid.razor.cs:82 — No CancellationToken parameter — this work can't be stopped early once started.
  • Async method without CancellationToken: UpdateColumnWidthAsync src/app/dev/DevToys.Blazor/Components/Collections/DataGrid/DataGridColumnHeader.razor.cs:45 — No CancellationToken parameter — this work can't be stopped early once started.
  • Async method without CancellationToken: GetCurrentCellWidthAsync src/app/dev/DevToys.Blazor/Components/Collections/DataGrid/DataGridColumnHeader.razor.cs:63 — No CancellationToken parameter — this work can't be stopped early once started.
  • Async method without CancellationToken: StartResizeColumn src/app/dev/DevToys.Blazor/Components/Collections/DataGrid/DataGridColumnResizeService.cs:39 — No CancellationToken parameter — this work can't be stopped early once started.
  • Async method without CancellationToken: OnApplicationMouseMove src/app/dev/DevToys.Blazor/Components/Collections/DataGrid/DataGridColumnResizeService.cs:83 — No CancellationToken parameter — this work can't be stopped early once started.
  • Async method without CancellationToken: OnApplicationMouseUp src/app/dev/DevToys.Blazor/Components/Collections/DataGrid/DataGridColumnResizeService.cs:88 — No CancellationToken parameter — this work can't be stopped early once started.
  • Async method without CancellationToken: ResizeColumn src/app/dev/DevToys.Blazor/Components/Collections/DataGrid/DataGridColumnResizeService.cs:117 — No CancellationToken parameter — this work can't be stopped early once started.
  • Async method without CancellationToken: ResizeColumns src/app/dev/DevToys.Blazor/Components/Collections/DataGrid/DataGridColumnResizeService.cs:170 — No CancellationToken parameter — this work can't be stopped early once started.
  • Async method without CancellationToken: ToggleFullScreenModeAsync src/app/dev/DevToys.Blazor/Components/Layout/FullScreenContainer/FullScreenContainer.razor.cs:19 — No CancellationToken parameter — this work can't be stopped early once started.
  • Async method without CancellationToken: ForceQuitFullScreenModeAsync src/app/dev/DevToys.Blazor/Components/Layout/FullScreenContainer/FullScreenContainer.razor.cs:49 — No CancellationToken parameter — this work can't be stopped early once started.
  • Async method without CancellationToken: ScrollToAsync src/app/dev/DevToys.Blazor/Components/Layout/ScrollViewer/ScrollViewer.razor.cs:87 — No CancellationToken parameter — this work can't be stopped early once started.
  • Async method without CancellationToken: GetOptionsAsync src/app/dev/DevToys.Blazor/Components/Text/MonacoEditor/Monaco/TextModel.cs:23 — No CancellationToken parameter — this work can't be stopped early once started.
  • Async method without CancellationToken: GetVersionIdAsync src/app/dev/DevToys.Blazor/Components/Text/MonacoEditor/Monaco/TextModel.cs:31 — No CancellationToken parameter — this work can't be stopped early once started.
  • + 11 more in this group — see findings.md.
AC6 · Visual & motion safety · Animation without a prefers-reduced-motion guard · ×28
  • Animation without a prefers-reduced-motion guard src/app/dev/DevToys.Blazor/wwwroot/css/devtoys.g.css:1 — `.combo-box-button .arrow-down-icon` moves (`transition-property: transform`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce.
  • Animation without a prefers-reduced-motion guard src/app/dev/DevToys.Blazor/wwwroot/css/devtoys.g.css:1 — `.drop-down-list-button .arrow-down-icon` moves (`transition-property: transform`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce.
  • Animation without a prefers-reduced-motion guard src/app/dev/DevToys.Blazor/wwwroot/css/devtoys.g.css:1 — `.toggle-switch::before` moves (`transition: transform 167ms ease-in-out,height 167ms cubic-bezier(0,0,0,1),width 167ms cubic-bezier(0,0,0,1),margin 167ms cubic-bezier(0,0,0,1),background 167ms linear`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce.
  • Animation without a prefers-reduced-motion guard src/app/dev/DevToys.Blazor/wwwroot/css/devtoys.g.css:1 — `.list-box-item::before` moves (`transition: transform 167ms cubic-bezier(0,0,0,1)`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce.
  • Animation without a prefers-reduced-motion guard src/app/dev/DevToys.Blazor/wwwroot/css/devtoys.g.css:1 — `.progress-bar.indeterminate .progress-bar-track:first-of-type` moves (`animation: 2s infinite indeterminate-1`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce.
  • Animation without a prefers-reduced-motion guard src/app/dev/DevToys.Blazor/wwwroot/css/devtoys.g.css:1 — `.progress-bar.indeterminate .progress-bar-track:nth-of-type(2)` moves (`animation: 2s infinite indeterminate-2`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce.
  • Animation without a prefers-reduced-motion guard src/app/dev/DevToys.Blazor/wwwroot/css/devtoys.g.css:1 — `.progress-ring.indeterminate circle` moves (`animation: 2s linear infinite progress-ring-indeterminate`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce.
  • Animation without a prefers-reduced-motion guard src/app/dev/DevToys.Blazor/wwwroot/css/devtoys.g.css:1 — `.dialog` moves (`animation: .25s cubic-bezier(.25,.1,.25,1) both dialog-open-animation`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce.
  • Animation without a prefers-reduced-motion guard src/app/dev/DevToys.Blazor/wwwroot/css/devtoys.g.css:1 — `.expander .card[data-expanded=true] .expander-expand-button .font-icon` moves (`transition: transform .2s ease-in-out`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce.
  • Animation without a prefers-reduced-motion guard src/app/dev/DevToys.Blazor/wwwroot/css/devtoys.g.css:1 — `.expander .card.expander-card .expander-expand-button .font-icon` moves (`transition: transform .2s ease-in-out`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce.
  • Animation without a prefers-reduced-motion guard src/app/dev/DevToys.Blazor/wwwroot/css/devtoys.g.css:1 — `.expander .expander-content-anchor` moves (`transition: max-height linear 250ms`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce.
  • Animation without a prefers-reduced-motion guard src/app/dev/DevToys.Blazor/wwwroot/css/devtoys.g.css:1 — `.expander .expander-content-anchor .expander-content` moves (`transition: transform 250ms cubic-bezier(1,1,0,1)`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce.
  • Animation without a prefers-reduced-motion guard src/app/dev/DevToys.Blazor/wwwroot/css/devtoys.g.css:1 — `.expander .expander-content-anchor[aria-expanded=true] .expander-content` moves (`transition: transform 250ms cubic-bezier(0,0,0,1)`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce.
  • Animation without a prefers-reduced-motion guard src/app/dev/DevToys.Blazor/wwwroot/css/devtoys.g.css:1 — `.simplebar-track.simplebar-vertical` moves (`transition: width .2s ease-in-out`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce.
  • Animation without a prefers-reduced-motion guard src/app/dev/DevToys.Blazor/wwwroot/css/devtoys.g.css:1 — `.simplebar-track.simplebar-horizontal` moves (`transition: height .2s ease-in-out`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce.
  • Animation without a prefers-reduced-motion guard src/app/dev/DevToys.Blazor/wwwroot/css/devtoys.g.css:1 — `.nav-bar-root nav.transition` moves (`transition: left .2s ease-in-out,width .2s ease-in-out,max-width .2s ease-in-out,box-shadow .2s ease-in-out`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce.
  • Animation without a prefers-reduced-motion guard src/app/dev/DevToys.Blazor/wwwroot/css/devtoys.g.css:1 — `nav .list-box-item .sidebar-expand-group-button` moves (`transition-property: transform`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce.
  • Animation without a prefers-reduced-motion guard src/app/dev/DevToys.Blazor/wwwroot/css/devtoys.g.css:1 — `.entrance-theme-transition` moves (`animation-name: entrance-theme-transition-key-frames`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce.
  • Animation without a prefers-reduced-motion guard src/app/dev/DevToys.Blazor/wwwroot/css/devtoys.g.css:1 — `div[data-uselessanimations] .entrance-theme-transition` moves (`animation-name: entrance-theme-transition-key-frames`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce.
  • Animation without a prefers-reduced-motion guard src/app/dev/DevToys.Blazor/wwwroot/css/devtoys.g.css:1 — `.hero::before` moves (`animation: 1s cubic-bezier(.7,1,.8,1) forwards hero-bg-scrolling`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce.
  • Animation without a prefers-reduced-motion guard src/app/dev/DevToys.Blazor/Pages/SubPages/ToolGroup.razor.scss:48 — `.hero::before` moves (`animation: hero-bg-scrolling 1s`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce.
  • Animation without a prefers-reduced-motion guard src/app/dev/DevToys.Blazor/Components/Menu/NavBar/NavBarItem.razor.scss:32 — `nav .list-box-item .sidebar-expand-group-button` moves (`transition-property: transform`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce.
  • Animation without a prefers-reduced-motion guard src/app/dev/DevToys.Blazor/Components/Layout/ScrollViewer/ScrollViewer.razor.scss:229 — `.simplebar-track.simplebar-vertical` moves (`transition: width 0.2s ease-in-out`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce.
  • Animation without a prefers-reduced-motion guard src/app/dev/DevToys.Blazor/Components/Layout/ScrollViewer/ScrollViewer.razor.scss:243 — `.simplebar-track.simplebar-horizontal` moves (`transition: height 0.2s ease-in-out`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce.
  • Animation without a prefers-reduced-motion guard src/app/dev/DevToys.Blazor/Components/Layout/Dialog/Dialog.razor.scss:7 — `.dialog` moves (`animation: dialog-open-animation 0.25s cubic-bezier(0.25, 0.1, 0.25, 1) both`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce.
  • + 3 more in this group — see findings.md.
X3 · Exception handling · Swallowed exception (empty catch) · ×24
  • Swallowed exception (empty catch) src/app/dev/platforms/desktop/DevToys.CLI/Core/OneOfParser.cs:324 — An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
  • Swallowed exception (empty catch) src/app/dev/DevToys.Core/FileHelper.cs:46 — An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
  • Swallowed exception (empty catch) src/app/dev/DevToys.Core/FileHelper.cs:66 — An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
  • Swallowed exception (empty catch) src/app/dev/DevToys.Core/Logging/FileLoggerProvider.cs:51 — 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) src/app/dev/DevToys.Core/Logging/FileLoggerProvider.cs:66 — An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
  • Swallowed exception (empty catch) src/app/dev/DevToys.Core/Logging/FileLoggerProvider.cs:108 — An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
  • Swallowed exception (empty catch) src/app/dev/DevToys.Core/Logging/FileLoggerProvider.cs:129 — An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
  • Swallowed exception (empty catch) src/app/dev/DevToys.Core/Mef/RecursiveDirectoryCatalog.cs:139 — An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
  • Swallowed exception (empty catch) src/app/dev/DevToys.Core/Tools/GuiToolInstance.cs:92 — 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) src/app/dev/DevToys.Core/Tools/GuiToolInstance.cs:113 — An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
  • Swallowed exception (empty catch) src/app/dev/DevToys.Core/Tools/GuiToolInstance.cs:138 — An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
  • Swallowed exception (empty catch) src/app/dev/DevToys.Blazor/Components/JSStyledComponentBase.cs:67 — 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) src/app/dev/DevToys.Blazor/Components/Layout/Popover/Popover.razor.cs:129 — 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) src/app/dev/DevToys.Blazor/Components/Text/MonacoEditor/MonacoEditorBase.cs:126 — 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) src/app/dev/DevToys.Blazor/Components/Text/TextBox/TextBox.razor.cs:128 — 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) src/app/dev/DevToys.Blazor/Core/Services/DocumentEventService.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) src/app/dev/DevToys.Blazor/Core/Services/FontService.cs:87 — An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
  • Swallowed exception (empty catch) src/app/dev/DevToys.Blazor/Core/Services/MonacoLanguageService.cs:110 — An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
  • Swallowed exception (empty catch) src/app/dev/DevToys.Blazor/Core/Services/MonacoLanguageService.cs:185 — An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
  • Swallowed exception (empty catch) src/app/dev/platforms/desktop/DevToys.Windows/Controls/MicaWindowWithOverlay.xaml.cs:243 — An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
  • Swallowed exception (empty catch) src/app/dev/platforms/desktop/DevToys.Windows/Controls/MicaWindowWithOverlay.xaml.cs:281 — An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
  • Swallowed exception (empty catch) src/app/dev/platforms/desktop/DevToys.Linux/Components/BlazorWebView/BlazorWebViewManager.cs:110 — An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
  • Swallowed exception (empty catch) src/app/dev/platforms/desktop/DevToys.Linux/Components/BlazorWebView/BlazorWebViewManager.cs:153 — An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
  • Swallowed exception (empty catch) src/app/dev/platforms/desktop/DevToys.Linux/Core/FileStorage.cs:103 — An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
AX4 · Dependency direction · Dependency-rule violation · ×23
  • Dependency-rule violation: DevToys.Core (Domain) → DevToys.Api (Web) src/app/dev/DevToys.Core/AppHelper.cs:143 — This Domain file depends on the Web project `DevToys.Api`: it names `LoggingExtensions`. The inward dependency rule is broken here. Depend on an abstraction the inner layer owns, implemented in the outer one.
  • Dependency-rule violation: DevToys.Core (Domain) → DevToys.Api (Web) src/app/dev/DevToys.Core/ExtensionOrderer.cs:17 — This Domain file depends on the Web project `DevToys.Api`: it names `IOrderableMetadata`. The inward dependency rule is broken here. It is named again on lines 31, 37, 87. Depend on an abstraction the inner layer owns, implemented in the outer one.
  • Dependency-rule violation: DevToys.Core (Domain) → DevToys.Api (Web) src/app/dev/DevToys.Core/FileHelper.cs:8 — This Domain file depends on the Web project `DevToys.Api`: it names `LoggingExtensions`. The inward dependency rule is broken here. Depend on an abstraction the inner layer owns, implemented in the outer one.
  • Dependency-rule violation: DevToys.Core (Domain) → DevToys.Api (Web) src/app/dev/DevToys.Core/Logging/FileLoggerProvider.cs:14 — This Domain file depends on the Web project `DevToys.Api`: it names `IFileStorage`. The inward dependency rule is broken here. It is named again on line 18. Depend on an abstraction the inner layer owns, implemented in the outer one.
  • Dependency-rule violation: DevToys.Core (Domain) → DevToys.Api (Web) src/app/dev/DevToys.Core/Logging/LoggingBuilderExtensions.cs:11 — This Domain file depends on the Web project `DevToys.Api`: it names `IFileStorage`. The inward dependency rule is broken here. Depend on an abstraction the inner layer owns, implemented in the outer one.
  • Dependency-rule violation: DevToys.Core (Domain) → DevToys.Api (Web) src/app/dev/DevToys.Core/Mef/MefComposer.cs:22 — This Domain file depends on the Web project `DevToys.Api`: it names `IMefProvider`, `LoggingExtensions`. The inward dependency rule is broken here. It is named again on lines 28, 40, 105. Depend on an abstraction the inner layer owns, implemented in the outer one.
  • Dependency-rule violation: DevToys.Core (Domain) → DevToys.Api (Web) src/app/dev/DevToys.Core/Mef/MefProvider.cs:5 — This Domain file depends on the Web project `DevToys.Api`: it names `IMefProvider`. The inward dependency rule is broken here. It is named again on line 6. Depend on an abstraction the inner layer owns, implemented in the outer one.
  • Dependency-rule violation: DevToys.Core (Domain) → DevToys.Api (Web) src/app/dev/DevToys.Core/Mef/RecursiveDirectoryCatalog.cs:44 — This Domain file depends on the Web project `DevToys.Api`: it names `LoggingExtensions`. The inward dependency rule is broken here. Depend on an abstraction the inner layer owns, implemented in the outer one.
  • Dependency-rule violation: DevToys.Core (Domain) → DevToys.Api (Web) src/app/dev/DevToys.Core/OSHelper.cs:5 — This Domain file depends on the Web project `DevToys.Api`: it names `Platform`. The inward dependency rule is broken here. It is named again on lines 9, 12, 16, 20. Depend on an abstraction the inner layer owns, implemented in the outer one.
  • Dependency-rule violation: DevToys.Core (Domain) → DevToys.Api (Web) src/app/dev/DevToys.Core/Properties/AdditionGlobalUsings.cs:1 — This Domain file depends on the Web project `DevToys.Api`: it names `DevToys.Api`. The inward dependency rule is broken here. Depend on an abstraction the inner layer owns, implemented in the outer one.
  • Dependency-rule violation: DevToys.Core (Domain) → DevToys.Api (Web) src/app/dev/DevToys.Core/Settings/PredefinedSettings.cs:43 — This Domain file depends on the Web project `DevToys.Api`: it names `SettingDefinition`, `AvailableApplicationTheme`, `UITextEndOfLinePreference`. The inward dependency rule is broken here. It is named again on lines 52, 60, 68, 71, 76, 84, 92, 100, …. Depend on an abstraction the inner layer owns, implemented in the outer one.
  • Dependency-rule violation: DevToys.Core (Domain) → DevToys.Api (Web) src/app/dev/DevToys.Core/Settings/SettingsProvider.cs:8 — This Domain file depends on the Web project `DevToys.Api`: it names `ISettingsProvider`, `LoggingExtensions`, `SettingChangedEventArgs`, `SettingDefinition`. The inward dependency rule is broken here. It is named again on lines 9, 17, 21, 23, 64, 92, 95, 99. Depend on an abstraction the inner layer owns, implemented in the outer one.
  • Dependency-rule violation: DevToys.Core (Domain) → DevToys.Api (Web) src/app/dev/DevToys.Core/Tools/GuiToolInstance.cs:12 — This Domain file depends on the Web project `DevToys.Api`: it names `UIToolView`, `IGuiTool`, `LoggingExtensions`, `MenuPlacement`, `GUI`, `IResourceAssemblyIdentifier`. The inward dependency rule is broken here. It is named again on lines 14, 15, 23, 25, 37, 74, 82, 145, …. Depend on an abstraction the inner layer owns, implemented in the outer one.
  • Dependency-rule violation: DevToys.Core (Domain) → DevToys.Api (Web) src/app/dev/DevToys.Core/Tools/GuiToolProvider.cs:25 — This Domain file depends on the Web project `DevToys.Api`: it names `IGuiTool`, `IResourceAssemblyIdentifier`, `GuiToolGroup`, `ISettingsProvider`, `LoggingExtensions`, `SettingDefinition`, `TextSpan`, `ObservableCollectionExtensions`, …. The inward dependency rule is broken here. It is named again on lines 41, 42, 43, 57, 58, 59, 60, 62, …. Depend on an abstraction the inner layer owns, implemented in the outer one.
  • Dependency-rule violation: DevToys.Core (Domain) → DevToys.Api (Web) src/app/dev/DevToys.Core/Tools/Metadata/DataTypeDetectorMetadata.cs:8 — This Domain file depends on the Web project `DevToys.Api`: it names `DictionaryExtensions`, `DataTypeNameAttribute`, `TargetPlatformAttribute`, `Platform`. The inward dependency rule is broken here. It is named again on lines 9, 10, 18. Depend on an abstraction the inner layer owns, implemented in the outer one.
  • Dependency-rule violation: DevToys.Core (Domain) → DevToys.Api (Web) src/app/dev/DevToys.Core/Tools/Metadata/GuiToolGroupMetadata.cs:4 — This Domain file depends on the Web project `DevToys.Api`: it names `IOrderableMetadata`, `DictionaryExtensions`, `NameAttribute`, `OrderAttribute`. The inward dependency rule is broken here. It is named again on lines 14, 15, 16. Depend on an abstraction the inner layer owns, implemented in the outer one.
  • Dependency-rule violation: DevToys.Core (Domain) → DevToys.Api (Web) src/app/dev/DevToys.Core/Tools/Metadata/GuiToolMetadata.cs:4 — This Domain file depends on the Web project `DevToys.Api`: it names `IOrderableMetadata`, `NameAttribute`, `ToolDisplayInformationAttribute`, `DictionaryExtensions`, `OrderAttribute`, `NotSearchableAttribute`, `NotFavorableAttribute`, `NoCompactOverlaySupportAttribute`, …. The inward dependency rule is broken here. It is named again on lines 19, 20, 21, 22, 23, 24, 25, 26, …. Depend on an abstraction the inner layer owns, implemented in the outer one.
  • Dependency-rule violation: DevToys.Core (Domain) → DevToys.Api (Web) src/app/dev/DevToys.Core/Tools/Metadata/LanguageServiceMetadata.cs:10 — This Domain file depends on the Web project `DevToys.Api`: it names `DictionaryExtensions`, `NameAttribute`. The inward dependency rule is broken here. Depend on an abstraction the inner layer owns, implemented in the outer one.
  • Dependency-rule violation: DevToys.Core (Domain) → DevToys.Api (Web) src/app/dev/DevToys.Core/Tools/Metadata/ResourceAssemblyIdentifierMetadata.cs:10 — This Domain file depends on the Web project `DevToys.Api`: it names `DictionaryExtensions`, `NameAttribute`. The inward dependency rule is broken here. Depend on an abstraction the inner layer owns, implemented in the outer one.
  • Dependency-rule violation: DevToys.Core (Domain) → DevToys.Api (Web) src/app/dev/DevToys.Core/Tools/SmartDetectionService.cs:15 — This Domain file depends on the Web project `DevToys.Api`: it names `IDataTypeDetector`, `ISettingsProvider`, `LoggingExtensions`, `TaskSchedulerAwaiter`, `DataDetectionResult`, `CancellationTokenExtension`. The inward dependency rule is broken here. It is named again on lines 16, 19, 55, 59, 64, 110, 114, 116, …. Depend on an abstraction the inner layer owns, implemented in the outer one.
  • Dependency-rule violation: DevToys.Core (Domain) → DevToys.Api (Web) src/app/dev/DevToys.Core/Tools/ViewItems/GroupViewItem.cs:17 — This Domain file depends on the Web project `DevToys.Api`: it names `GuiToolGroup`. The inward dependency rule is broken here. Depend on an abstraction the inner layer owns, implemented in the outer one.
  • Dependency-rule violation: DevToys.Core (Domain) → DevToys.Api (Web) src/app/dev/DevToys.Core/Tools/ViewItems/GuiToolViewItem.cs:13 — This Domain file depends on the Web project `DevToys.Api`: it names `TextSpan`. The inward dependency rule is broken here. It is named again on line 30. Depend on an abstraction the inner layer owns, implemented in the outer one.
  • Dependency-rule violation: DevToys.Core (Domain) → DevToys.Api (Web) src/app/dev/DevToys.Core/Web/WebClientService.cs:14 — This Domain file depends on the Web project `DevToys.Api`: it names `LoggingExtensions`. The inward dependency rule is broken here. Depend on an abstraction the inner layer owns, implemented in the outer one.
D17 · Explicit Debt · TodoComment · ×20
  • TodoComment src/app/dev/DevToys.Blazor/BuiltInTools/SupportDevelopment/SupportDevelopmentGuidTools.cs:22 — // TODO: Finish this tool. — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
  • TodoComment src/app/dev/DevToys.Blazor/Components/Menu/ContextMenu/ContextMenuItem.cs:5 — // TODO: Actually handle keyboard shortcuts? — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
  • TodoComment src/app/dev/DevToys.Blazor/Components/UIElements/UIButtonPresenter.razor.cs:13 — // TODO: Try Catch and log? — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
  • TodoComment src/app/dev/DevToys.Blazor/Components/UIElements/UIInfoBarPresenter.razor.cs:13 — // TODO: Try Catch and log? — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
  • TodoComment src/app/dev/DevToys.Blazor/Components/UIElements/UIInfoBarPresenter.razor.cs:24 — // TODO: Try Catch and log? — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
  • TodoComment src/app/dev/DevToys.Blazor/Components/UIElements/UIImageViewerPresenter.razor.cs:1 — // TODO: Add logs. — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
  • TodoComment src/app/dev/DevToys.Blazor/Components/UIElements/UIImageViewerPresenter.razor.cs:262 — // TODO: Log this. Also, maybe display a message to the user that the image cannot be displayed? — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
  • TodoComment src/app/dev/DevToys.Blazor/Components/UIElements/UIMultiLineTextInputPresenter.razor.cs:227 — // TODO: if language is plain text, then should we hide line numbers and few other things? — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
  • TodoComment src/app/dev/DevToys.Blazor/Components/UIElements/UITextInputWrapper.razor.cs:252 — // TODO: Display ContentDialog — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
  • TodoComment src/app/dev/DevToys.Blazor/Components/UIElements/UITextInputWrapper.razor.cs:316 — // TODO: Display ContentDialog — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
  • TodoComment src/app/dev/DevToys.Blazor/Components/UIElements/UITextInputWrapper.razor.cs:294 — // TODO: Detect encoding. — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
  • TodoComment src/app/dev/DevToys.Blazor/Components/UIElements/UITextInputWrapper.razor.cs:296 — // TODO: Perf risk. Read in chunks. — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
  • TodoComment src/app/dev/DevToys.Core/Tools/GuiToolProvider.cs:436 — // TODO: We should let the user know that something went wrong. — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
  • TodoComment src/app/dev/DevToys.Core/Tools/GuiToolProvider.cs:625 — // TODO: We should let the user know that something went wrong. — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
  • TodoComment src/app/dev/platforms/desktop/DevToys.MacOS/Controls/BlazorWebView/BlazorWebViewManager.cs:264 — // TODO: Determine whether this is needed — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
  • TodoComment src/app/dev/platforms/desktop/DevToys.MacOS/Controls/BlazorWebView/BlazorWebViewManager.cs:273 — // TODO: Determine whether this is needed — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
  • TodoComment src/app/dev/platforms/desktop/DevToys.MacOS/Core/ThemeListener.cs:140 — // TODO: Detect high contrast — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
  • TodoComment src/app/dev/platforms/desktop/DevToys.MacOS/Views/AppMenuBar.cs:25 — // TODO: Localize — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
  • TodoComment src/app/tests/DevToys.UnitTests/Mocks/MockIFileStorage.cs:33 — // TODO: prompt the user to type in the console a relative or absolute file path that has one of the file types indicated. — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
  • TodoComment src/app/tests/DevToys.UnitTests/Mocks/MockIFileStorage.cs:39 — // TODO: prompt the user to type in the console a relative or absolute file path that has one of the file types indicated. — 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.
AC6 · Visual & motion safety · Focus outline removed in CSS without a · ×11
  • Focus outline removed in CSS without a :focus replacement src/app/dev/DevToys.Blazor/Components/Text/TextBox/TextBox.razor.scss:7 — `.text-box` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible.
  • Focus outline removed in CSS without a :focus replacement src/app/dev/DevToys.Blazor/Components/Text/MonacoEditor/MonacoEditor.razor.scss:7 — `.monaco-editor-standalone` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible.
  • Focus outline removed in CSS without a :focus replacement src/app/dev/DevToys.Blazor/Components/Menu/ContextMenu/ContextMenu.razor.scss:17 — `.context-menu-list-box .list-box:focus` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible.
  • Focus outline removed in CSS without a :focus replacement src/app/dev/DevToys.Blazor/Components/Menu/ContextMenu/ContextMenu.razor.scss:39 — `.context-menu-list-box .context-menu-item.selected` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible.
  • Focus outline removed in CSS without a :focus replacement src/app/dev/DevToys.Blazor/Components/Layout/Popover/Popover.razor.scss:2 — `.popover` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible.
  • Focus outline removed in CSS without a :focus replacement src/app/dev/DevToys.Blazor/Components/Feedback/ProgressRing/ProgressRing.razor.scss:19 — `.progress-ring` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible.
  • Focus outline removed in CSS without a :focus replacement src/app/dev/DevToys.Blazor/Components/Collections/ListBox/ListBoxItem.razor.scss:11 — `.list-box-item` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible.
  • Focus outline removed in CSS without a :focus replacement src/app/dev/DevToys.Blazor/Components/BasicInput/ToggleSwitch/ToggleSwitch.razor.scss:13 — `.toggle-switch` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible.
  • Focus outline removed in CSS without a :focus replacement src/app/dev/DevToys.Blazor/Components/BasicInput/RadioButton/RadioButton.razor.scss:12 — `.radio-button` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible.
  • Focus outline removed in CSS without a :focus replacement src/app/dev/DevToys.Blazor/Components/BasicInput/CheckBox/CheckBox.razor.scss:10 — `.checkbox` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible.
  • Focus outline removed in CSS without a :focus replacement src/app/dev/DevToys.Blazor/Components/BasicInput/Button/Button.razor.scss:13 — `button` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible.
X1 · Async correctness · async void method · ×9
  • async void method: UIMultiLineTextInput_TextChanged src/app/dev/DevToys.Blazor/Components/UIElements/UIDiffTextInputPresenter.razor.cs:85 — `async void` can't be awaited and its exceptions crash the process instead of propagating. Return `Task` — or, where the delegate contract requires void (timer/event/callback registrations), make this a thin void shim that awaits a Task-returning inner method inside try/catch so exceptions are contained.
  • async void method: UIDiffTextInput_RightTextChanged src/app/dev/DevToys.Blazor/Components/UIElements/UIDiffTextInputPresenter.razor.cs:91 — `async void` can't be awaited and its exceptions crash the process instead of propagating. Return `Task` — or, where the delegate contract requires void (timer/event/callback registrations), make this a thin void shim that awaits a Task-returning inner method inside try/catch so exceptions are contained.
  • async void method: UIMultiLineTextInput_IsReadOnlyChanged src/app/dev/DevToys.Blazor/Components/UIElements/UIDiffTextInputPresenter.razor.cs:97 — `async void` can't be awaited and its exceptions crash the process instead of propagating. Return `Task` — or, where the delegate contract requires void (timer/event/callback registrations), make this a thin void shim that awaits a Task-returning inner method inside try/catch so exceptions are contained.
  • async void method: UIDiffTextInput_InlineModeChanged src/app/dev/DevToys.Blazor/Components/UIElements/UIDiffTextInputPresenter.razor.cs:113 — `async void` can't be awaited and its exceptions crash the process instead of propagating. Return `Task` — or, where the delegate contract requires void (timer/event/callback registrations), make this a thin void shim that awaits a Task-returning inner method inside try/catch so exceptions are contained.
  • async void method: UIMultiLineTextInput_TextChanged src/app/dev/DevToys.Blazor/Components/UIElements/UIMultiLineTextInputPresenter.razor.cs:55 — `async void` can't be awaited and its exceptions crash the process instead of propagating. Return `Task` — or, where the delegate contract requires void (timer/event/callback registrations), make this a thin void shim that awaits a Task-returning inner method inside try/catch so exceptions are contained.
  • async void method: UIMultiLineTextInput_SyntaxColorizationLanguageNameChanged src/app/dev/DevToys.Blazor/Components/UIElements/UIMultiLineTextInputPresenter.razor.cs:67 — `async void` can't be awaited and its exceptions crash the process instead of propagating. Return `Task` — or, where the delegate contract requires void (timer/event/callback registrations), make this a thin void shim that awaits a Task-returning inner method inside try/catch so exceptions are contained.
  • async void method: UIMultiLineTextInput_IsReadOnlyChanged src/app/dev/DevToys.Blazor/Components/UIElements/UIMultiLineTextInputPresenter.razor.cs:76 — `async void` can't be awaited and its exceptions crash the process instead of propagating. Return `Task` — or, where the delegate contract requires void (timer/event/callback registrations), make this a thin void shim that awaits a Task-returning inner method inside try/catch so exceptions are contained.
  • async void method: UIMultiLineTextInput_SelectionChanged src/app/dev/DevToys.Blazor/Components/UIElements/UIMultiLineTextInputPresenter.razor.cs:85 — `async void` can't be awaited and its exceptions crash the process instead of propagating. Return `Task` — or, where the delegate contract requires void (timer/event/callback registrations), make this a thin void shim that awaits a Task-returning inner method inside try/catch so exceptions are contained.
  • async void method: ViewModel_CheckForExtensionUpdateRequested src/app/dev/DevToys.Blazor/Pages/Index.razor.cs:119 — `async void` can't be awaited and its exceptions crash the process instead of propagating. Return `Task` — or, where the delegate contract requires void (timer/event/callback registrations), make this a thin void shim that awaits a Task-returning inner method inside try/catch so exceptions are contained.
D3 · God Classes · TooManyMethods · ×6
  • TooManyMethods: MonacoEditor src/app/dev/DevToys.Blazor/Assets/javascript/monacoEditor.ts:14 — TooManyMethods — 83 methods. The bar is 30 methods; this is 53 over it, 2.77× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
  • TooManyMethods: TextModel src/app/dev/DevToys.Blazor/Components/Text/MonacoEditor/Monaco/TextModel.cs — TooManyMethods — 105 significant lines (blank, comment-only and punctuation-only lines excluded), 51 methods. The bar is 30 methods; this is 21 over it, 1.70× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
  • TooManyMethods: RicherMonacoEditorBase src/app/dev/DevToys.Blazor/Components/Text/MonacoEditor/RicherMonacoEditorBase.cs — TooManyMethods — 316 significant lines (blank, comment-only and punctuation-only lines excluded), 41 methods. The bar is 30 methods; this is 11 over it, 1.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: GUI src/app/dev/DevToys.Api/Tool/GUI/Components/IUIDropDownButton.cs — TooManyMethods — 128 significant lines (blank, comment-only and punctuation-only lines excluded), 41 methods, declared across 13 files: Components/IUIDropDownButton.cs (6), Components/IUIUtf32IconButton.cs (5), Components/IUIUtf32IconDropDownButton.cs (5), Components/IUIDataGridRow.cs (4), +9 more file(s). The bar is 30 methods; this is 11 over it, 1.37× the bar. The type holds no instance state, so there is no shared data to group its members by. To reduce it, split it by area instead: give each cohesive family of members its own smaller type, so no one type has to be read whole to change one of them.
  • TooManyMethods: ObservableHashSet src/app/dev/DevToys.Api/Core/ObservableHashSet.cs — TooManyMethods — 141 significant lines (blank, comment-only and punctuation-only lines excluded), 34 methods. The bar is 30 methods; this is 4 over it, 1.13× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
  • TooManyMethods: MonacoEditorBase src/app/dev/DevToys.Blazor/Components/Text/MonacoEditor/MonacoEditorBase.cs — TooManyMethods — 124 significant lines (blank, comment-only and punctuation-only lines excluded), 33 methods. The bar is 30 methods; this is 3 over it, 1.10× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
D1 · Cyclomatic Complexity · (anonymous) · ×5
  • (anonymous)::(anonymous)::SimpleBarCore::drag (cyclomatic 31) src/app/dev/DevToys.Blazor/wwwroot/js/simplebar-modified.js:899 — (anonymous)::(anonymous)::SimpleBarCore::drag has cyclomatic complexity 31 (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.
  • (anonymous)::(anonymous)::positionScrollbar (cyclomatic 22) src/app/dev/DevToys.Blazor/wwwroot/js/simplebar-modified.js:1235 — (anonymous)::(anonymous)::positionScrollbar has cyclomatic complexity 22 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
  • (anonymous)::(anonymous)::recalculate (cyclomatic 20) src/app/dev/DevToys.Blazor/wwwroot/js/simplebar-modified.js:1149 — (anonymous)::(anonymous)::recalculate has cyclomatic complexity 20 (threshold 15). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
  • (anonymous)::(anonymous)::SimpleBarCore::onPointerEvent (cyclomatic 17) src/app/dev/DevToys.Blazor/wwwroot/js/simplebar-modified.js:853 — (anonymous)::(anonymous)::SimpleBarCore::onPointerEvent 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.
  • (anonymous)::(anonymous)::onTrackClick (cyclomatic 16) src/app/dev/DevToys.Blazor/wwwroot/js/simplebar-modified.js:1383 — (anonymous)::(anonymous)::onTrackClick has cyclomatic complexity 16 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
PF3 · Async & latency hygiene · Sync-over-async blocking · ×5
  • Sync-over-async blocking — 4 blocking call(s) on async work (.Wait()/.GetAwaiter().GetResult()) — these waste a thread and can deadlock wherever a synchronization context is in play (a UI thread, or a caller that has one).
  • Sync-over-async blocking src/app/dev/DevToys.Api/Core/Threading/TaskExtensions.cs:82 — `.GetAwaiter().GetResult()` blocks this thread until the async work completes — it wastes a thread-pool thread for as long as the work runs and can deadlock wherever a synchronization context is in play (a UI thread, or a caller that has one).
  • Sync-over-async blocking src/app/dev/DevToys.Api/Core/Threading/TaskExtensions.cs:93 — `.GetAwaiter().GetResult()` blocks this thread until the async work completes — it wastes a thread-pool thread for as long as the work runs and can deadlock wherever a synchronization context is in play (a UI thread, or a caller that has one).
  • Sync-over-async blocking src/app/dev/platforms/desktop/DevToys.MacOS/Controls/BlazorWebView/BlazorWKWebView.cs:110 — `.GetAwaiter() .GetResult()` blocks this thread until the async work completes — it wastes a thread-pool thread for as long as the work runs and can deadlock wherever a synchronization context is in play (a UI thread, or a caller that has one).
  • Sync-over-async blocking src/app/dev/platforms/desktop/DevToys.Linux/Components/BlazorWebView/BlazorWebView.cs:140 — `.GetAwaiter() .GetResult()` blocks this thread until the async work completes — it wastes a thread-pool thread for as long as the work runs and can deadlock wherever a synchronization context is in play (a UI thread, or a caller that has one).
X24 · Document value interpolated into markup unescaped · Untrusted text written into markup unescaped · ×5
  • Untrusted text written into markup unescaped src/app/dev/DevToys.Blazor/Pages/Dialogs/WhatsNewDialog.razor:11 — `ReleaseNotesHtml` is text this program did not author, and it is written into the text of an element through Blazor's `MarkupString` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup.
  • Untrusted text written into markup unescaped src/app/dev/DevToys.Blazor/Assets/javascript/dom.js:110 — `fontDefinition` is text this program did not author, and it is written into the text of an element through `innerHTML` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup.
  • Untrusted text written into markup unescaped src/app/dev/DevToys.Blazor/Assets/javascript/dom.ts:131 — `fontDefinition` is text this program did not author, and it is written into the text of an element through `innerHTML` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup.
  • Untrusted text written into markup unescaped src/app/dev/DevToys.Blazor/Components/UIElements/UIWebViewPresenter.razor.js:6 — `html` is text this program did not author, and it is written into the text of an element through `innerHTML` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup.
  • Untrusted text written into markup unescaped src/app/dev/DevToys.Blazor/Components/UIElements/UIWebViewPresenter.razor.ts:7 — `html` is text this program did not author, and it is written into the text of an element through `innerHTML` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup.
D2 · Cognitive Complexity · (anonymous) · ×4
  • (anonymous)::(anonymous)::SimpleBarCore::drag (cognitive 33) src/app/dev/DevToys.Blazor/wwwroot/js/simplebar-modified.js:899 — (anonymous)::(anonymous)::SimpleBarCore::drag has cognitive complexity 33 (threshold 15). Drivers by points: ternaries 13 (15 pts), boolean chains 14, if/else 4 (nesting depth added 2). 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.
  • (anonymous)::(anonymous)::SimpleBarCore::onPointerEvent (cognitive 27) src/app/dev/DevToys.Blazor/wwwroot/js/simplebar-modified.js:853 — (anonymous)::(anonymous)::SimpleBarCore::onPointerEvent has cognitive complexity 27 (threshold 15). Drivers by points: if/else 11 (22 pts), boolean chains 5 (nesting depth added 11). 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.
  • (anonymous)::(anonymous)::positionScrollbar (cognitive 22) src/app/dev/DevToys.Blazor/wwwroot/js/simplebar-modified.js:1235 — (anonymous)::(anonymous)::positionScrollbar has cognitive complexity 22 (threshold 15). Drivers by points: boolean chains 10, ternaries 7 (9 pts), if/else 3 (nesting depth added 2). 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.
  • (anonymous)::(anonymous)::recalculate (cognitive 19) src/app/dev/DevToys.Blazor/wwwroot/js/simplebar-modified.js:1149 — (anonymous)::(anonymous)::recalculate has cognitive complexity 19 (threshold 15). Drivers by points: boolean chains 10, ternaries 6, if/else 3. 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.
D4 · Code Duplication · Duplicated block (11 lines × 2) · ×4
  • Duplicated block (11 lines × 2) src/app/dev/platforms/desktop/DevToys.Linux/Core/ThemeListener.cs:100 — src/app/dev/platforms/desktop/DevToys.Linux/Core/ThemeListener.cs:100-110 | src/app/dev/platforms/desktop/DevToys.MacOS/Core/ThemeListener.cs:106-116 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
  • Duplicated block (11 lines × 2) src/app/dev/DevToys.Api/Tool/GUI/Components/IUIStack.cs:66 — src/app/dev/DevToys.Api/Tool/GUI/Components/IUIStack.cs:66-76 | src/app/dev/DevToys.Api/Tool/GUI/Components/IUIWrap.cs:43-53 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
  • Duplicated block (11 lines × 2) REDACTED:23 — REDACTED:23-33 | src/app/dev/DevToys.Blazor/BuiltInDataTypeDetectors/XsdDataTypeDetector.cs:24-34 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
  • Duplicated block (11 lines × 2) src/app/dev/platforms/desktop/DevToys.Linux/Components/BlazorWebView/StaticContentHotReloadManager.cs:49 — src/app/dev/platforms/desktop/DevToys.Linux/Components/BlazorWebView/StaticContentHotReloadManager.cs:49-59 | src/app/dev/platforms/desktop/DevToys.MacOS/Controls/BlazorWebView/StaticContentHotReloadManager.cs:47-57 — before extracting anything, compare `src/app/dev/platforms/desktop/DevToys.Linux/Components/BlazorWebView/StaticContentHotReloadManager.cs` and `src/app/dev/platforms/desktop/DevToys.MacOS/Controls/BlazorWebView/StaticContentHotReloadManager.cs` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 94 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. 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.
D6 · Cohesion (LCOM4) · Low cohesion · ×4
  • Low cohesion: WindowService (LCOM4 6) src/app/dev/platforms/desktop/DevToys.MacOS/Core/WindowService.cs:8 — WindowService's methods fall into 6 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 6 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
  • Low cohesion: SettingsGuiTool (LCOM4 5) src/app/dev/DevToys.Blazor/BuiltInTools/Settings/SettingsGuiTool.cs:9 — SettingsGuiTool's methods fall into 5 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 5 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
  • Low cohesion: GuiToolProvider (LCOM4 4) src/app/dev/DevToys.Core/Tools/GuiToolProvider.cs:19 — GuiToolProvider'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: MicaWindowWithOverlay (LCOM4 4) src/app/dev/platforms/desktop/DevToys.Windows/Controls/MicaWindowWithOverlay.xaml.cs:27 — MicaWindowWithOverlay'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.
X1 · Async correctness · Sync-over-async (deadlock risk) · ×4
  • Sync-over-async (deadlock risk) src/app/dev/DevToys.Api/Core/Threading/TaskExtensions.cs:82 — Blocking on a Task with `.Wait()`/`.GetAwaiter().GetResult()` can deadlock (and wastes a thread). Prefer awaiting it: make the caller `async` and `await` instead. Where a synchronous entry point must stay — a public sync API you cannot break, or a process entry point that must not return until the work finishes — the block belongs in ONE documented bridge and never inside code that is already async; and where it already is that bridge, give the wait a TIMEOUT so a hung task fails the call instead of hanging the process.
  • Sync-over-async (deadlock risk) src/app/dev/DevToys.Api/Core/Threading/TaskExtensions.cs:93 — Blocking on a Task with `.Wait()`/`.GetAwaiter().GetResult()` can deadlock (and wastes a thread). Prefer awaiting it: make the caller `async` and `await` instead. Where a synchronous entry point must stay — a public sync API you cannot break, or a process entry point that must not return until the work finishes — the block belongs in ONE documented bridge and never inside code that is already async; and where it already is that bridge, give the wait a TIMEOUT so a hung task fails the call instead of hanging the process.
  • Sync-over-async (deadlock risk) src/app/dev/platforms/desktop/DevToys.MacOS/Controls/BlazorWebView/BlazorWKWebView.cs:108 — Blocking on a Task with `.Wait()`/`.GetAwaiter().GetResult()` wastes a thread and, if the task needs a context this one is holding, deadlocks. `Dispose()` returns void by contract, so it cannot simply `await`: signal the work to stop first (cancel its token, set its stop flag) so the wait is short, give the wait a TIMEOUT so a hung task cannot hang shutdown, and — where callers can use it — add an awaitable teardown (`DisposeAsync`/`StopAsync`) beside the synchronous one and let `Dispose()` remain the bounded fallback.
  • Sync-over-async (deadlock risk) src/app/dev/platforms/desktop/DevToys.Linux/Components/BlazorWebView/BlazorWebView.cs:138 — Blocking on a Task with `.Wait()`/`.GetAwaiter().GetResult()` wastes a thread and, if the task needs a context this one is holding, deadlocks. `Dispose()` returns void by contract, so it cannot simply `await`: signal the work to stop first (cancel its token, set its stop flag) so the wait is short, give the wait a TIMEOUT so a hung task cannot hang shutdown, and — where callers can use it — add an awaitable teardown (`DisposeAsync`/`StopAsync`) beside the synchronous one and let `Dispose()` remain the bounded fallback.
D2 · Cognitive Complexity · newContext · ×3
  • newContext::check (cognitive 75) src/app/dev/DevToys.Blazor/wwwroot/js/require.js:5 — newContext::check has cognitive complexity 75 (threshold 15). Drivers by points: if/else 12 (36 pts), ternaries 3 (21 pts), boolean chains 12, error handling 1 (6 pts) (nesting depth added 47). To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
  • newContext::completeLoad (cognitive 20) src/app/dev/DevToys.Blazor/wwwroot/js/require.js:5 — newContext::completeLoad has cognitive complexity 20 (threshold 15). Drivers by points: if/else 5 (9 pts), boolean chains 7, ternaries 1 (3 pts), loops 1 (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
  • newContext::nameToUrl (cognitive 19) src/app/dev/DevToys.Blazor/wwwroot/js/require.js:5 — newContext::nameToUrl has cognitive complexity 19 (threshold 15). Drivers by points: boolean chains 6, if/else 4 (6 pts), ternaries 3 (5 pts), loops 1 (2 pts) (nesting depth added 5). 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.
D4 · Code Duplication · Duplicated block (15 lines × 2) · ×3
  • Duplicated block (15 lines × 2) src/app/dev/DevToys.Api/Core/ObservableHashSet.cs:248 — src/app/dev/DevToys.Api/Core/ObservableHashSet.cs:248-262 | src/app/dev/DevToys.Api/Core/ObservableHashSet.cs:274-288 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/app/dev/DevToys.Api/Core/ObservableHashSet.cs:248` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (15 lines × 2) src/app/dev/platforms/desktop/DevToys.MacOS/Core/FileStorage.cs:106 — src/app/dev/platforms/desktop/DevToys.MacOS/Core/FileStorage.cs:106-120 | src/app/dev/platforms/desktop/DevToys.MacOS/Core/FileStorage.cs:148-162 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/app/dev/platforms/desktop/DevToys.MacOS/Core/FileStorage.cs:106` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
  • Duplicated block (15 lines × 2) src/app/dev/platforms/desktop/DevToys.Linux/Components/BlazorWebView/BlazorWebView.cs:133 — src/app/dev/platforms/desktop/DevToys.Linux/Components/BlazorWebView/BlazorWebView.cs:133-147 | src/app/dev/platforms/desktop/DevToys.MacOS/Controls/BlazorWebView/BlazorWKWebView.cs:103-117 — before extracting anything, compare `src/app/dev/platforms/desktop/DevToys.Linux/Components/BlazorWebView/BlazorWebView.cs` and `src/app/dev/platforms/desktop/DevToys.MacOS/Controls/BlazorWebView/BlazorWKWebView.cs` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 113 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
D4 · Code Duplication · Duplicated block (12 lines × 2) · ×3
  • Duplicated block (12 lines × 2) src/app/dev/platforms/desktop/DevToys.MacOS/AppDelegate.cs:134 — src/app/dev/platforms/desktop/DevToys.MacOS/AppDelegate.cs:134-145 | src/app/dev/platforms/desktop/DevToys.Windows/MainWindow.xaml.cs:180-191 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
  • Duplicated block (12 lines × 2) src/app/dev/DevToys.Blazor/Components/Text/MonacoEditor/MonacoEditor.razor.cs:125 — src/app/dev/DevToys.Blazor/Components/Text/MonacoEditor/MonacoEditor.razor.cs:125-136 | src/app/dev/DevToys.Blazor/Components/Text/MonacoEditor/MonacoEditorDiff.razor.cs:113-124 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
  • Duplicated block (12 lines × 2) src/app/dev/platforms/desktop/DevToys.Linux/Components/BlazorWebView/BlazorWebView.cs:420 — src/app/dev/platforms/desktop/DevToys.Linux/Components/BlazorWebView/BlazorWebView.cs:420-431 | src/app/dev/platforms/desktop/DevToys.MacOS/Controls/BlazorWebView/BlazorWKWebView.cs:391-402 — before extracting anything, compare `src/app/dev/platforms/desktop/DevToys.Linux/Components/BlazorWebView/BlazorWebView.cs` and `src/app/dev/platforms/desktop/DevToys.MacOS/Controls/BlazorWebView/BlazorWKWebView.cs` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 113 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. 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 (10 lines × 2) · ×3
  • Duplicated block (10 lines × 2) src/build/Build.cs:299 — src/build/Build.cs:299-308 | src/build/Build.cs:343-352 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
  • Duplicated block (10 lines × 2) src/app/dev/DevToys.Blazor/Components/Collections/ListBox/SelectBase.cs:106 — src/app/dev/DevToys.Blazor/Components/Collections/ListBox/SelectBase.cs:106-115 | src/app/dev/DevToys.Blazor/Components/Text/AutoSuggestBox/AutoSuggestBox.razor.cs:43-52 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
  • Duplicated block (10 lines × 2) src/build/AppVersion/CSharpUpdater.cs:23 — src/build/AppVersion/CSharpUpdater.cs:23-32 | src/build/AppVersion/ProjectUpdater.cs:21-30 — 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.
GD1 · Unfinished & placeholder code · Unfinished stub · ×3
  • Unfinished stub — throws NotImplementedException src/app/dev/DevToys.Localization/DevToysLocalizationResourceManagerAssemblyIdentifier.cs:9 — A shipped member still throws NotImplementedException — generated scaffolding that was never completed. Implement it or remove the dead surface.
  • Unfinished stub — throws NotImplementedException REDACTED:136 — A shipped member still throws NotImplementedException — generated scaffolding that was never completed. Implement it or remove the dead surface.
  • Unfinished stub — throws NotImplementedException src/app/dev/DevToys.Blazor/Core/Converters/PolymorphicConverter.cs:8 — A shipped member still throws NotImplementedException — generated scaffolding that was never completed. Implement it or remove the dead surface.
D1 · Cyclomatic Complexity · require.newContext · ×2
  • require.newContext::q (cyclomatic 27) src/app/dev/DevToys.Blazor/wwwroot/js/require.js:5 — require.newContext::q has cyclomatic complexity 27 (threshold 15). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators. This shape REPEATS in the file: 2 other methods here (require.newContext, require.newContext::R) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 3 times rather than 3 independent problems. Splitting this body alone leaves the other 2 exactly as they are. Where these are variations on one operation, the change that clears all 3 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
  • require.newContext::R (cyclomatic 17) src/app/dev/DevToys.Blazor/wwwroot/js/require.js:5 — require.newContext::R 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. This shape REPEATS in the file: 2 other methods here (require.newContext, require.newContext::q) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 3 times rather than 3 independent problems. Splitting this body alone leaves the other 2 exactly as they are. Where these are variations on one operation, the change that clears all 3 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
D17 · Explicit Debt · HackComment · ×2
  • HackComment src/app/dev/DevToys.Core/OSHelper.cs:49 — // hack because of this: https://github.com/dotnet/corefx/issues/10361 — a workaround marked in source: record what it is compensating for and what would allow its removal (the upstream fix, the API it is waiting on, the invariant it restores), so the next reader can judge whether it is still needed rather than rediscovering why it is there.
  • HackComment src/build/Build.cs:208 — // HACK: Required for MacOS. However, <LinkMode>None</LinkMode> in the CSPROJ disables trimming. — a workaround marked in source: record what it is compensating for and what would allow its removal (the upstream fix, the API it is waiting on, the invariant it restores), so the next reader can judge whether it is still needed rather than rediscovering why it is there.
D29 · Static Analysis (SAST) · REDACTED
  • REDACTED
  • REDACTED
D30 · Dependency Vulnerabilities · Medium CVE · ×2
  • REDACTED
  • REDACTED
D4 · Code Duplication · Duplicated block (17 lines × 2) · ×2
  • Duplicated block (17 lines × 2) src/app/dev/DevToys.Blazor/Components/Text/MonacoEditor/Monaco/Editor/EditorUpdateOptions.cs:10 — src/app/dev/DevToys.Blazor/Components/Text/MonacoEditor/Monaco/Editor/EditorUpdateOptions.cs:10-26 | src/app/dev/DevToys.Blazor/Components/Text/MonacoEditor/Monaco/Editor/StandaloneEditorConstructionOptions.cs:52-68 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
  • Duplicated block (17 lines × 2) src/app/dev/platforms/desktop/DevToys.Linux/Components/BlazorWebView/BlazorWebViewManager.cs:79 — src/app/dev/platforms/desktop/DevToys.Linux/Components/BlazorWebView/BlazorWebViewManager.cs:79-95 | src/app/dev/platforms/desktop/DevToys.MacOS/Controls/BlazorWebView/BlazorWebViewManager.cs:75-91 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
D4 · Code Duplication · Duplicated block (8 lines × 2) · ×2
  • Duplicated block (8 lines × 2) src/app/dev/DevToys.Core/Tools/SmartDetectionService.cs:69 — src/app/dev/DevToys.Core/Tools/SmartDetectionService.cs:69-76 | src/app/dev/DevToys.Core/Tools/SmartDetectionService.cs:86-93 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/app/dev/DevToys.Core/Tools/SmartDetectionService.cs:69` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (8 lines × 2) src/app/dev/platforms/desktop/DevToys.MacOS/Core/WindowService.cs:92 — src/app/dev/platforms/desktop/DevToys.MacOS/Core/WindowService.cs:92-99 | src/app/dev/platforms/desktop/DevToys.MacOS/Core/WindowService.cs:134-141 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/app/dev/platforms/desktop/DevToys.MacOS/Core/WindowService.cs:92` 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 (7 lines × 2) · ×2
  • Duplicated block (7 lines × 2) src/app/dev/DevToys.Blazor/Components/Collections/DataGrid/DataGrid.razor.cs:280 — src/app/dev/DevToys.Blazor/Components/Collections/DataGrid/DataGrid.razor.cs:280-286 | src/app/dev/DevToys.Blazor/Components/Collections/ListBox/SelectBase.cs:221-227 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `src/app/dev/DevToys.Blazor/Components/Collections/DataGrid/DataGrid.razor.cs:280` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (7 lines × 2) src/build/AppVersion/CSharpUpdater.cs:50 — src/build/AppVersion/CSharpUpdater.cs:50-56 | src/build/AppVersion/ProjectUpdater.cs:48-54 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `src/build/AppVersion/CSharpUpdater.cs:50` 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 first that the copies are not typed on the same thing: the declarations holding them bind `rule` to `CSharpVersionUpdateRule` in one and `ProjectVersionUpdateRule` in another, and the duplicated lines use it. The extracted unit therefore needs a parameter type that fits BOTH — their common supertype where they have one, or a new abstraction over them where they do not — and settling that is the step that comes BEFORE the extraction above. Where the two types are deliberately unrelated, the duplication is the price of that separation and the honest resolution is to record the decision rather than to extract.
D4 · Code Duplication · Duplicated block (9 lines × 2) · ×2
  • Duplicated block (9 lines × 2) src/app/dev/DevToys.Blazor/Components/BasicInput/CheckBox/CheckBox.razor.cs:28 — src/app/dev/DevToys.Blazor/Components/BasicInput/CheckBox/CheckBox.razor.cs:28-36 | src/app/dev/DevToys.Blazor/Components/BasicInput/RadioButton/RadioButton.razor.cs:34-42 — `src/app/dev/DevToys.Blazor/Components/BasicInput/CheckBox/CheckBox.razor.cs` and `src/app/dev/DevToys.Blazor/Components/BasicInput/RadioButton/RadioButton.razor.cs` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 1 separate duplicated blocks between them, totalling at least 9 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own.
  • Duplicated block (9 lines × 2) src/app/dev/platforms/desktop/DevToys.Linux/Components/BlazorWebView/BlazorWebView.cs:435 — src/app/dev/platforms/desktop/DevToys.Linux/Components/BlazorWebView/BlazorWebView.cs:435-443 | src/app/dev/platforms/desktop/DevToys.MacOS/Controls/BlazorWebView/BlazorWKWebView.cs:406-414 — before extracting anything, compare `src/app/dev/platforms/desktop/DevToys.Linux/Components/BlazorWebView/BlazorWebView.cs` and `src/app/dev/platforms/desktop/DevToys.MacOS/Controls/BlazorWebView/BlazorWKWebView.cs` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 113 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. 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.
IC1 · Incompleteness & stubs · Unfinished stub · ×2
  • Unfinished stub — throws NotImplementedException REDACTED:136 — `OnDataReceived` is a shipped member whose whole body throws NotImplementedException — scaffolding that was never completed. Implement it or remove the dead surface.
  • Unfinished stub — throws NotImplementedException src/app/dev/DevToys.Localization/DevToysLocalizationResourceManagerAssemblyIdentifier.cs:9 — `GetFontDefinitionsAsync` is a shipped member whose whole body throws NotImplementedException — scaffolding that was never completed. Implement it or remove the dead surface.
X18 · Disposal-pattern correctness · Owned disposable field is never released · ×2
  • Owned disposable field is never released src/app/dev/DevToys.Blazor/Components/UIElements/UIMultiLineTextInputPresenter.razor.cs:11 — `UIMultiLineTextInputPresenter` implements `IDisposable` — so it has told every caller it holds something worth releasing — and it constructs `_semaphore` itself (line 11), which makes that instance its own. But `_semaphore` is named in none of the methods the disposal search covered: `DisposeAsync` (line 41) — 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` (`_semaphore?.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 src/app/dev/DevToys.Blazor/Core/Services/PopoverService.cs:5 — `PopoverService` implements `IDisposable` — so it has told every caller it holds something worth releasing — and it constructs `_semaphore` itself (line 5), which makes that instance its own. But `_semaphore` is named in none of the methods the disposal search covered: `DisposeAsync` (line 20) — 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` (`_semaphore?.Dispose();`), or, if it truly does not need releasing, drop `IDisposable` from the type so the claim and the behaviour agree.
AC4 · Keyboard semantics · Anchor without href · ×1
  • Anchor without href src/app/dev/platforms/desktop/DevToys.Windows/wwwroot/index.html:35 — An <a> with no href, role or tabindex isn't focusable or keyboard-activatable. Give it a real href, or use a <button> for an action.
AC6 · Visual & motion safety · Low contrast colour pair in CSS (1.6 · ×1
  • Low contrast colour pair in CSS (1.6:1) src/app/dev/DevToys.Blazor/wwwroot/css/devtoys.g.css:1 — `.checkbox` sets color: rgb(255, 255, 255) on background-color: rgb(204, 204, 204) — 1.6:1, below the 4.5:1 WCAG AA minimum for normal text. This is a MINIFIED, build-generated sheet — editing the literal here is undone by the next vendor drop or rebuild, so override the rule in your own stylesheet (or fix it upstream / in the source the bundle is built from).
AC7 · A11y enforcement · Accessibility enforcement below the top rung · ×1
  • Accessibility enforcement below the top rung — No accessibility enforcement found — no a11y linter (an accessibility check that can read your UI — no component framework was detected and your pages are rendered by server-side templates, which neither the JSX/Vue ESLint plugins nor the HTML-template linters can parse; run axe/pa11y over the rendered pages, or assert the accessibility invariants over that rendered HTML in the test suite you already have) and no axe/pa11y/Lighthouse in tests or CI. Start by running that check over your rendered pages in CI. What was searched, so you can tell an absence from a miss: the 73 markup file(s) this pass actually assessed, the linter configuration checked in beside them, and this repository's test and CI files — matched by name against the accessibility checkers this dimension carries. An audit run outside the repository, a hosted scanner, or a check whose name is not one of those, is not seen here.
AX2 · Stateful singletons · Stateful singleton · ×1
  • Stateful singleton: WindowService src/app/dev/platforms/desktop/DevToys.Windows/Core/WindowService.cs:9 — `WindowService` is a singleton (one shared instance) but mutates instance state outside any lock (_isCompactOverlayMode, _window, _nonCompactOverlayModeWindowState, _compactOverlayModeWindowState; e.g. `_isCompactOverlayMode` at line 30).
D1 · Cyclomatic Complexity · require.newContext (cyclomatic 84) · ×1
  • require.newContext (cyclomatic 84) src/app/dev/DevToys.Blazor/wwwroot/js/require.js:5 — require.newContext has cyclomatic complexity 84 (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. This shape REPEATS in the file: 2 other methods here (require.newContext::q, require.newContext::R) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 3 times rather than 3 independent problems. Splitting this body alone leaves the other 2 exactly as they are. Where these are variations on one operation, the change that clears all 3 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
D1 · Cyclomatic Complexity · Popover.placePopover (cyclomatic 67) · ×1
  • Popover.placePopover (cyclomatic 67) src/app/dev/DevToys.Blazor/Assets/javascript/popover.ts:328 — Popover.placePopover has cyclomatic complexity 67 (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 · RicherMonacoEditorBase.EventCallbackAsync (cyclomatic 38) · ×1
  • RicherMonacoEditorBase.EventCallbackAsync (cyclomatic 38) src/app/dev/DevToys.Blazor/Components/Text/MonacoEditor/RicherMonacoEditorBase.cs:326 — RicherMonacoEditorBase.EventCallbackAsync has cyclomatic complexity 38 (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 · RicherMonacoEditorBase.SetEventListenersAsync (cyclomatic 28) · ×1
  • RicherMonacoEditorBase.SetEventListenersAsync (cyclomatic 28) src/app/dev/DevToys.Blazor/Components/Text/MonacoEditor/RicherMonacoEditorBase.cs:186 — RicherMonacoEditorBase.SetEventListenersAsync has cyclomatic complexity 28 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
D1 · Cyclomatic Complexity · newContext · ×1
  • newContext::check (cyclomatic 26) src/app/dev/DevToys.Blazor/wwwroot/js/require.js:5 — newContext::check has cyclomatic complexity 26 (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 · Base64TextDataTypeDetector.IsBase64DataStrict (cyclomatic 20) · ×1
  • Base64TextDataTypeDetector.IsBase64DataStrict (cyclomatic 20) src/app/dev/DevToys.Blazor/BuiltInDataTypeDetectors/Base64TextDataTypeDetector.cs:29 — Base64TextDataTypeDetector.IsBase64DataStrict has cyclomatic complexity 20 (threshold 15). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
D1 · Cyclomatic Complexity · Popover.calculatePopoverPosition (cyclomatic 19) · ×1
  • Popover.calculatePopoverPosition (cyclomatic 19) src/app/dev/DevToys.Blazor/Assets/javascript/popover.ts:237 — Popover.calculatePopoverPosition has cyclomatic complexity 19 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
D1 · Cyclomatic Complexity · MainWindowViewModel.RunSmartDetectionAsync (cyclomatic 18) · ×1
  • MainWindowViewModel.RunSmartDetectionAsync (cyclomatic 18) src/app/dev/DevToys.Business/ViewModels/MainWindowViewModel.cs:207 — MainWindowViewModel.RunSmartDetectionAsync has cyclomatic complexity 18 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · (anonymous) (cyclomatic 18) · ×1
  • (anonymous) (cyclomatic 18) src/app/dev/DevToys.Blazor/wwwroot/js/require.js:5 — (anonymous) has cyclomatic complexity 18 (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 · GuiToolMetadata.GuiToolMetadata.ctor (cyclomatic 17) · ×1
  • GuiToolMetadata.GuiToolMetadata.ctor (cyclomatic 17) src/app/dev/DevToys.Core/Tools/Metadata/GuiToolMetadata.cs:30 — GuiToolMetadata.GuiToolMetadata.ctor has cyclomatic complexity 17 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · ExtensionInstallationManager.GetPathToExclude (cyclomatic 16) · ×1
  • ExtensionInstallationManager.GetPathToExclude (cyclomatic 16) src/app/dev/DevToys.Blazor/BuiltInTools/ExtensionsManager/ExtensionInstallationManager.cs:189 — ExtensionInstallationManager.GetPathToExclude has cyclomatic complexity 16 (threshold 15). To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Where every arm is uniform — the same kind of value, with no behaviour of its own — a table keyed by the case is the shorter form; wherever the arms carry different data or different behaviour, keep them as cases, because collapsing those trades an explicit, reviewable set of cases for nothing.
D1 · Cyclomatic Complexity · split-grid.Gutter.drag (cyclomatic 16) · ×1
  • split-grid.Gutter.drag (cyclomatic 16) src/app/dev/DevToys.Blazor/wwwroot/lib/split-grid/split-grid.js:379 — split-grid.Gutter.drag has cyclomatic complexity 16 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
D11 · Test Reliability · Test reliability not measured · ×1
  • Test reliability not measured — test suite did not build — Test reliability NOT MEASURED: this repository did not build in our analyzer environment (a C#/MSBuild compiler error), so no test ever ran and flakiness could not be exercised. It is excluded from the score rather than counted as a defect. We did not read WHERE the failing diagnostic is, so this does not claim the fault is in your test code — a repository written for an older SDK band can compile for you and not for us. Run `dotnet build` on this commit: if it succeeds, the gap is ours and nothing here is a defect in your code.
D17 · Explicit Debt · BarePragmaDisable · ×1
  • BarePragmaDisable src/app/dev/DevToys.Blazor/Components/Text/MonacoEditor/RicherMonacoEditorDiffBase.cs:212 — #pragma warning disable BL0005 — 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.
D2 · Cognitive Complexity · Popover.placePopover (cognitive 113) · ×1
  • Popover.placePopover (cognitive 113) src/app/dev/DevToys.Blazor/Assets/javascript/popover.ts:328 — Popover.placePopover has cognitive complexity 113 (threshold 15). Drivers by points: if/else 40 (93 pts), boolean chains 20 (nesting depth added 53). To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
D2 · Cognitive Complexity · require.newContext (cognitive 83) · ×1
  • require.newContext (cognitive 83) src/app/dev/DevToys.Blazor/wwwroot/js/require.js:5 — require.newContext has cognitive complexity 83 (threshold 15). Drivers by points: boolean chains 133, if/else 7 (15 pts), loops 3 (7 pts), ternaries 6 (7 pts) (nesting depth added 13). 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. This shape REPEATS in the file: one other method here (require.newContext::q) has the same decision points, in the same order, at the same nesting depths — so this is one pattern written twice rather than two separate problems. Splitting this body alone leaves the other exactly as it is. Where these are variations on one operation, the change that clears both is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
D2 · Cognitive Complexity · Popover.callback (cognitive 49) · ×1
  • Popover.callback (cognitive 49) src/app/dev/DevToys.Blazor/Assets/javascript/popover.ts:72 — Popover.callback has cognitive complexity 49 (threshold 15). Drivers by points: if/else 10 (39 pts), loops 3 (9 pts), boolean chains 1 (nesting depth added 35). 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 · RicherMonacoEditorBase.EventCallbackAsync (cognitive 33) · ×1
  • RicherMonacoEditorBase.EventCallbackAsync (cognitive 33) src/app/dev/DevToys.Blazor/Components/Text/MonacoEditor/RicherMonacoEditorBase.cs:326 — RicherMonacoEditorBase.EventCallbackAsync has cognitive complexity 33 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · require.newContext · ×1
  • require.newContext::q (cognitive 30) src/app/dev/DevToys.Blazor/wwwroot/js/require.js:5 — require.newContext::q has cognitive complexity 30 (threshold 15). Drivers by points: boolean chains 15, if/else 3 (9 pts), loops 2 (6 pts) (nesting depth added 10). 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. This shape REPEATS in the file: one other method here (require.newContext) has the same decision points, in the same order, at the same nesting depths — so this is one pattern written twice rather than two separate problems. Splitting this body alone leaves the other exactly as it is. Where these are variations on one operation, the change that clears both is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
D2 · Cognitive Complexity · GUI.Handle (cognitive 29) · ×1
  • GUI.Handle (cognitive 29) src/app/dev/DevToys.Api/Tool/GUI/Components/IUISetting.cs:404 — GUI.Handle has cognitive complexity 29 (threshold 15). Most of this is not in the body itself: 6 of the 29 points are its own statements and the rest belongs to 2 function literals inside it that branch (lines 456, 433). 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 · SmartDetectionService.DetectAsync (cognitive 28) · ×1
  • SmartDetectionService.DetectAsync (cognitive 28) src/app/dev/DevToys.Core/Tools/SmartDetectionService.cs:45 — SmartDetectionService.DetectAsync has cognitive complexity 28 (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 · GuiToolProvider.SetToolIsFavorite (cognitive 27) · ×1
  • GuiToolProvider.SetToolIsFavorite (cognitive 27) src/app/dev/DevToys.Core/Tools/GuiToolProvider.cs:187 — GuiToolProvider.SetToolIsFavorite has cognitive complexity 27 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · RicherMonacoEditorBase.SetEventListenersAsync (cognitive 27) · ×1
  • RicherMonacoEditorBase.SetEventListenersAsync (cognitive 27) src/app/dev/DevToys.Blazor/Components/Text/MonacoEditor/RicherMonacoEditorBase.cs:186 — RicherMonacoEditorBase.SetEventListenersAsync has cognitive complexity 27 (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 · UIFileSelectorPresenter.TreatSelectedFiles (cognitive 26) · ×1
  • UIFileSelectorPresenter.TreatSelectedFiles (cognitive 26) src/app/dev/DevToys.Blazor/Components/UIElements/UIFileSelectorPresenter.razor.cs:297 — UIFileSelectorPresenter.TreatSelectedFiles has cognitive complexity 26 (threshold 15). Of this number, 24 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 · MainWindowViewModel.RunSmartDetectionAsync (cognitive 25) · ×1
  • MainWindowViewModel.RunSmartDetectionAsync (cognitive 25) src/app/dev/DevToys.Business/ViewModels/MainWindowViewModel.cs:207 — MainWindowViewModel.RunSmartDetectionAsync has cognitive complexity 25 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · ExtensionInstallationManager.UninstallExtensionsScheduledForRemoval (cognitive 21) · ×1
  • ExtensionInstallationManager.UninstallExtensionsScheduledForRemoval (cognitive 21) src/app/dev/DevToys.Blazor/BuiltInTools/ExtensionsManager/ExtensionInstallationManager.cs:17 — ExtensionInstallationManager.UninstallExtensionsScheduledForRemoval 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 · FileStorage.PickOpenFilesAsync (cognitive 20) · ×1
  • FileStorage.PickOpenFilesAsync (cognitive 20) src/app/dev/platforms/desktop/DevToys.CLI/Core/FileStorage/FileStorage.cs:122 — FileStorage.PickOpenFilesAsync 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 · GuiToolMetadata.GuiToolMetadata.ctor (cognitive 20) · ×1
  • GuiToolMetadata.GuiToolMetadata.ctor (cognitive 20) src/app/dev/DevToys.Core/Tools/Metadata/GuiToolMetadata.cs:30 — GuiToolMetadata.GuiToolMetadata.ctor 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 · GuiToolProvider.WeightMatch (cognitive 19) · ×1
  • GuiToolProvider.WeightMatch (cognitive 19) src/app/dev/DevToys.Core/Tools/GuiToolProvider.cs:702 — GuiToolProvider.WeightMatch has cognitive complexity 19 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · split-grid.Gutter.drag (cognitive 19) · ×1
  • split-grid.Gutter.drag (cognitive 19) src/app/dev/DevToys.Blazor/wwwroot/lib/split-grid/split-grid.js:379 — split-grid.Gutter.drag has cognitive complexity 19 (threshold 15). Drivers by points: if/else 17 (19 pts) (nesting depth added 2). 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 · (anonymous) (cognitive 19) · ×1
  • (anonymous) (cognitive 19) src/app/dev/DevToys.Blazor/wwwroot/js/require.js:5 — (anonymous) has cognitive complexity 19 (threshold 15). Drivers by points: boolean chains 10, if/else 3 (6 pts), ternaries 2 (3 pts) (nesting depth added 4). 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.
D2 · Cognitive Complexity · OptionToICommandLineToolMap.ParseArgument (cognitive 18) · ×1
  • OptionToICommandLineToolMap.ParseArgument (cognitive 18) src/app/dev/platforms/desktop/DevToys.CLI/OptionToICommandLineToolMap.cs:183 — OptionToICommandLineToolMap.ParseArgument 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 · Popover.calculatePopoverPosition (cognitive 18) · ×1
  • Popover.calculatePopoverPosition (cognitive 18) src/app/dev/DevToys.Blazor/Assets/javascript/popover.ts:237 — Popover.calculatePopoverPosition has cognitive complexity 18 (threshold 15). Drivers by points: if/else 18. 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 · AppHelper.CheckForUpdateAsync (cognitive 17) · ×1
  • AppHelper.CheckForUpdateAsync (cognitive 17) src/app/dev/DevToys.Core/AppHelper.cs:82 — AppHelper.CheckForUpdateAsync has cognitive 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, 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 · GuiToolProvider.GetViewItemFromTool (cognitive 17) · ×1
  • GuiToolProvider.GetViewItemFromTool (cognitive 17) src/app/dev/DevToys.Core/Tools/GuiToolProvider.cs:267 — GuiToolProvider.GetViewItemFromTool 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 · MainWindowViewModel.SelectedMenuItem.set (cognitive 17) · ×1
  • MainWindowViewModel.SelectedMenuItem.set (cognitive 17) src/app/dev/DevToys.Business/ViewModels/MainWindowViewModel.cs:84 — MainWindowViewModel.SelectedMenuItem.set has cognitive complexity 17 (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 · OneOfParser.SelectBestMatch (cognitive 16) · ×1
  • OneOfParser.SelectBestMatch (cognitive 16) src/app/dev/platforms/desktop/DevToys.CLI/Core/OneOfParser.cs:363 — OneOfParser.SelectBestMatch 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 · SmartDetectionService.BuildDataTypeToToolInstanceMap (cognitive 16) · ×1
  • SmartDetectionService.BuildDataTypeToToolInstanceMap (cognitive 16) src/app/dev/DevToys.Core/Tools/SmartDetectionService.cs:242 — SmartDetectionService.BuildDataTypeToToolInstanceMap 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 · Base64TextDataTypeDetector.IsBase64DataStrict (cognitive 16) · ×1
  • Base64TextDataTypeDetector.IsBase64DataStrict (cognitive 16) src/app/dev/DevToys.Blazor/BuiltInDataTypeDetectors/Base64TextDataTypeDetector.cs:29 — Base64TextDataTypeDetector.IsBase64DataStrict 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 · UIFileSelectorPresenter.OnBrowseFoldersButtonClickAsync (cognitive 16) · ×1
  • UIFileSelectorPresenter.OnBrowseFoldersButtonClickAsync (cognitive 16) src/app/dev/DevToys.Blazor/Components/UIElements/UIFileSelectorPresenter.razor.cs:113 — UIFileSelectorPresenter.OnBrowseFoldersButtonClickAsync has cognitive complexity 16 (threshold 15). To reduce it, break up the iteration: give each loop body a named function, and split a multi-phase loop into one function per phase so no single body carries the whole pipeline.
D29 · Static Analysis (SAST) · REDACTED · ×1
  • REDACTED
D29 · Static Analysis (SAST) · REDACTED · ×1
  • REDACTED
D3 · God Classes · ClassTooLong · ×1
  • ClassTooLong: MonacoEditor src/app/dev/DevToys.Blazor/Assets/javascript/monacoEditor.ts:14 — ClassTooLong — 677 significant lines (blank, comment-only and punctuation-only lines excluded), 83 methods. The bar is 400 significant lines; this is 277 over it, 1.69× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
D3 · God Classes · FileTooLong · ×1
  • FileTooLong: javascript/monacoEditor.ts src/app/dev/DevToys.Blazor/Assets/javascript/monacoEditor.ts — FileTooLong — 684 significant lines (blank, comment-only and punctuation-only lines excluded), about 99% of them inside a single declaration: MonacoEditor (14-1078). The bar is 500 significant lines; this is 184 over it, 1.37× the bar. Moving the declarations that sit BESIDE it into sibling files will not shorten this file. Extract from INSIDE that declaration instead: lift each cohesive group of its body — the parts that share the same inputs and are named together — into its own unit in a sibling file, and have the original call them.
D36 · Supply-chain Provenance & Signing REDACTED · ×1
  • REDACTED
D4 · Code Duplication · Edited copy of a member (12 corresponding lines) · ×1
  • Edited copy of a member (12 corresponding lines) src/build/Build.cs:266 — src/build/Build.cs:266-309 | src/build/Build.cs:337-357 — These two members are one piece of code written twice and then edited apart: 12 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Members sharing a duplicated core (4 members, 50+ identical tokens) · ×1
  • Members sharing a duplicated core (4 members, 50+ identical tokens) src/app/dev/platforms/desktop/DevToys.CLI/Core/FileStorage/FileStorage.cs:44 — src/app/dev/platforms/desktop/DevToys.CLI/Core/FileStorage/FileStorage.cs:44-62 | src/app/dev/platforms/desktop/DevToys.Linux/Core/FileStorage.cs:41-59 | src/app/dev/platforms/desktop/DevToys.MacOS/Core/FileStorage.cs:41-59 | src/app/dev/platforms/desktop/DevToys.Windows/Core/FileStorage.cs:43-61 — These 4 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 4 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 4 times.
D4 · Code Duplication · Duplicated block (23–110 lines × 2) · ×1
  • Duplicated block (23–110 lines × 2) src/app/dev/DevToys.Api/Tool/GUI/LanguageService/AutoCompletionItemKind.cs:8 — src/app/dev/DevToys.Api/Tool/GUI/LanguageService/AutoCompletionItemKind.cs:8-117 | src/app/dev/DevToys.Blazor/Components/Text/MonacoEditor/Monaco/Languages/CompletionItemKind.cs:8-30 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `src/app/dev/DevToys.Api/Tool/GUI/LanguageService/AutoCompletionItemKind.cs:8` 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 (43–44 lines × 2) · ×1
  • Duplicated block (43–44 lines × 2) src/app/dev/platforms/desktop/DevToys.Linux/Components/BlazorWebView/BlazorWebView.cs:259 — src/app/dev/platforms/desktop/DevToys.Linux/Components/BlazorWebView/BlazorWebView.cs:259-302 | src/app/dev/platforms/desktop/DevToys.MacOS/Controls/BlazorWebView/BlazorWKWebView.cs:228-270 — before extracting anything, compare `src/app/dev/platforms/desktop/DevToys.Linux/Components/BlazorWebView/BlazorWebView.cs` and `src/app/dev/platforms/desktop/DevToys.MacOS/Controls/BlazorWebView/BlazorWKWebView.cs` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 113 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
D4 · Code Duplication · Duplicated block (30 lines × 2) · ×1
  • Duplicated block (30 lines × 2) src/app/dev/DevToys.Blazor/Core/Extensions/IJSRuntimeExtensions.cs:21 — src/app/dev/DevToys.Blazor/Core/Extensions/IJSRuntimeExtensions.cs:21-50 | src/app/dev/DevToys.Blazor/Core/Extensions/IJSRuntimeExtensions.cs:64-93 — 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 (28 lines × 2) · ×1
  • Duplicated block (28 lines × 2) src/app/dev/DevToys.Core/Tools/Metadata/GuiToolGroupMetadata.cs:29 — src/app/dev/DevToys.Core/Tools/Metadata/GuiToolGroupMetadata.cs:29-56 | src/app/dev/DevToys.Core/Tools/Metadata/GuiToolMetadata.cs:75-102 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `src/app/dev/DevToys.Core/Tools/Metadata/GuiToolGroupMetadata.cs:29` 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 (26 lines × 3) · ×1
  • Duplicated block (26 lines × 3) src/app/dev/platforms/desktop/DevToys.CLI/Core/Settings/SettingsStorage.cs:50 — src/app/dev/platforms/desktop/DevToys.CLI/Core/Settings/SettingsStorage.cs:50-75 | src/app/dev/platforms/desktop/DevToys.Linux/Core/SettingsStorage.cs:50-75 | src/app/dev/platforms/desktop/DevToys.Windows/Core/SettingsStorage.cs:51-76 — before extracting anything, compare `src/app/dev/platforms/desktop/DevToys.CLI/Core/Settings/SettingsStorage.cs` and `src/app/dev/platforms/desktop/DevToys.Linux/Core/SettingsStorage.cs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 49 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. 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 (24 lines × 2) · ×1
  • Duplicated block (24 lines × 2) src/app/dev/platforms/desktop/DevToys.Linux/Components/BlazorWebView/StaticContentHotReloadManager.cs:19 — src/app/dev/platforms/desktop/DevToys.Linux/Components/BlazorWebView/StaticContentHotReloadManager.cs:19-42 | src/app/dev/platforms/desktop/DevToys.MacOS/Controls/BlazorWebView/StaticContentHotReloadManager.cs:17-40 — before extracting anything, compare `src/app/dev/platforms/desktop/DevToys.Linux/Components/BlazorWebView/StaticContentHotReloadManager.cs` and `src/app/dev/platforms/desktop/DevToys.MacOS/Controls/BlazorWebView/StaticContentHotReloadManager.cs` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 94 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/app/dev/platforms/desktop/DevToys.Linux/Components/BlazorWebView/StaticContentHotReloadManager.cs:19` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (23–24 lines × 2) · ×1
  • Duplicated block (23–24 lines × 2) src/app/dev/platforms/desktop/DevToys.Linux/Components/BlazorWebView/StaticContentHotReloadManager.cs:149 — src/app/dev/platforms/desktop/DevToys.Linux/Components/BlazorWebView/StaticContentHotReloadManager.cs:149-172 | src/app/dev/platforms/desktop/DevToys.MacOS/Controls/BlazorWebView/StaticContentHotReloadManager.cs:147-169 — before extracting anything, compare `src/app/dev/platforms/desktop/DevToys.Linux/Components/BlazorWebView/StaticContentHotReloadManager.cs` and `src/app/dev/platforms/desktop/DevToys.MacOS/Controls/BlazorWebView/StaticContentHotReloadManager.cs` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 94 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
D4 · Code Duplication · Duplicated block (23 lines × 2) · ×1
  • Duplicated block (23 lines × 2) src/app/dev/DevToys.Blazor/Components/UIElements/UIFileSelectorPresenter.razor.cs:213 — src/app/dev/DevToys.Blazor/Components/UIElements/UIFileSelectorPresenter.razor.cs:213-235 | src/app/dev/DevToys.Blazor/Components/UIElements/UIFileSelectorPresenter.razor.cs:240-262 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/app/dev/DevToys.Blazor/Components/UIElements/UIFileSelectorPresenter.razor.cs:213` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (21 lines × 2) · ×1
  • Duplicated block (21 lines × 2) src/app/dev/platforms/desktop/DevToys.Linux/Components/BlazorWebView/BlazorWebView.cs:163 — src/app/dev/platforms/desktop/DevToys.Linux/Components/BlazorWebView/BlazorWebView.cs:163-183 | src/app/dev/platforms/desktop/DevToys.MacOS/Controls/BlazorWebView/BlazorWKWebView.cs:127-147 — before extracting anything, compare `src/app/dev/platforms/desktop/DevToys.Linux/Components/BlazorWebView/BlazorWebView.cs` and `src/app/dev/platforms/desktop/DevToys.MacOS/Controls/BlazorWebView/BlazorWKWebView.cs` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 113 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. 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 (17–20 lines × 2) · ×1
  • Duplicated block (17–20 lines × 2) src/app/dev/DevToys.Blazor/Components/Layout/Card/Card.razor.cs:5 — src/app/dev/DevToys.Blazor/Components/Layout/Card/Card.razor.cs:5-21 | src/app/dev/DevToys.Blazor/Components/Layout/Expander/Expander.razor.cs:9-28 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
D4 · Code Duplication · Duplicated block (19 lines × 2) · ×1
  • Duplicated block (19 lines × 2) src/app/dev/platforms/desktop/DevToys.Linux/Components/BlazorWebView/StaticContentHotReloadManager.cs:76 — src/app/dev/platforms/desktop/DevToys.Linux/Components/BlazorWebView/StaticContentHotReloadManager.cs:76-94 | src/app/dev/platforms/desktop/DevToys.MacOS/Controls/BlazorWebView/StaticContentHotReloadManager.cs:74-92 — before extracting anything, compare `src/app/dev/platforms/desktop/DevToys.Linux/Components/BlazorWebView/StaticContentHotReloadManager.cs` and `src/app/dev/platforms/desktop/DevToys.MacOS/Controls/BlazorWebView/StaticContentHotReloadManager.cs` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 94 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. 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 (18 lines × 4) · ×1
  • Duplicated block (18 lines × 4) src/app/dev/platforms/desktop/DevToys.CLI/Core/FileStorage/FileStorage.cs:45 — src/app/dev/platforms/desktop/DevToys.CLI/Core/FileStorage/FileStorage.cs:45-62 | src/app/dev/platforms/desktop/DevToys.Linux/Core/FileStorage.cs:42-59 | src/app/dev/platforms/desktop/DevToys.MacOS/Core/FileStorage.cs:42-59 | src/app/dev/platforms/desktop/DevToys.Windows/Core/FileStorage.cs:44-61 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 4 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 4 times. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
D4 · Code Duplication · Duplicated block (18 lines × 2) · ×1
  • Duplicated block (18 lines × 2) src/app/dev/DevToys.Blazor/Components/Feedback/ProgressBar/ProgressBar.razor.cs:21 — src/app/dev/DevToys.Blazor/Components/Feedback/ProgressBar/ProgressBar.razor.cs:21-38 | src/app/dev/DevToys.Blazor/Components/Feedback/ProgressRing/ProgressRing.razor.cs:27-44 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
D4 · Code Duplication · Duplicated block (16 lines × 2) · ×1
  • Duplicated block (16 lines × 2) src/app/dev/platforms/desktop/DevToys.Linux/Components/BlazorWebView/StaticContentHotReloadManager.cs:99 — src/app/dev/platforms/desktop/DevToys.Linux/Components/BlazorWebView/StaticContentHotReloadManager.cs:99-114 | src/app/dev/platforms/desktop/DevToys.MacOS/Controls/BlazorWebView/StaticContentHotReloadManager.cs:97-112 — before extracting anything, compare `src/app/dev/platforms/desktop/DevToys.Linux/Components/BlazorWebView/StaticContentHotReloadManager.cs` and `src/app/dev/platforms/desktop/DevToys.MacOS/Controls/BlazorWebView/StaticContentHotReloadManager.cs` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 94 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. 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 (14 lines × 3) · ×1
  • Duplicated block (14 lines × 3) src/app/dev/platforms/desktop/DevToys.CLI/Core/Settings/SettingsStorage.cs:79 — src/app/dev/platforms/desktop/DevToys.CLI/Core/Settings/SettingsStorage.cs:79-92 | src/app/dev/platforms/desktop/DevToys.Linux/Core/SettingsStorage.cs:79-92 | src/app/dev/platforms/desktop/DevToys.Windows/Core/SettingsStorage.cs:80-93 — before extracting anything, compare `src/app/dev/platforms/desktop/DevToys.CLI/Core/Settings/SettingsStorage.cs` and `src/app/dev/platforms/desktop/DevToys.Linux/Core/SettingsStorage.cs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 49 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
D4 · Code Duplication · Duplicated block (12 lines × 3) · ×1
  • Duplicated block (12 lines × 3) src/app/dev/platforms/desktop/DevToys.MacOS/Core/FileStorage.cs:66 — src/app/dev/platforms/desktop/DevToys.MacOS/Core/FileStorage.cs:66-77 | src/app/dev/platforms/desktop/DevToys.MacOS/Core/FileStorage.cs:105-116 | src/app/dev/platforms/desktop/DevToys.MacOS/Core/FileStorage.cs:147-158 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
D4 · Code Duplication · Duplicated block (8–12 lines × 2) · ×1
  • Duplicated block (8–12 lines × 2) src/app/dev/platforms/desktop/DevToys.Linux/Components/BlazorWebView/BlazorWebView.cs:313 — src/app/dev/platforms/desktop/DevToys.Linux/Components/BlazorWebView/BlazorWebView.cs:313-324 | src/app/dev/platforms/desktop/DevToys.MacOS/Controls/BlazorWebView/BlazorWKWebView.cs:280-287 — before extracting anything, compare `src/app/dev/platforms/desktop/DevToys.Linux/Components/BlazorWebView/BlazorWebView.cs` and `src/app/dev/platforms/desktop/DevToys.MacOS/Controls/BlazorWebView/BlazorWKWebView.cs` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 113 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
D4 · Code Duplication · Duplicated block (5–7 lines × 2) · ×1
  • Duplicated block (5–7 lines × 2) src/app/dev/platforms/desktop/DevToys.Linux/LinuxProgram.cs:77 — src/app/dev/platforms/desktop/DevToys.Linux/LinuxProgram.cs:77-81 | src/app/dev/platforms/desktop/DevToys.MacOS/AppDelegate.cs:81-87 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
D4 · Code Duplication · Duplicated block (7 lines × 4) · ×1
  • Duplicated block (7 lines × 4) src/app/dev/platforms/desktop/DevToys.CLI/Core/FileStorage/FileStorage.cs:20 — src/app/dev/platforms/desktop/DevToys.CLI/Core/FileStorage/FileStorage.cs:20-26 | src/app/dev/platforms/desktop/DevToys.Linux/Core/FileStorage.cs:17-23 | src/app/dev/platforms/desktop/DevToys.MacOS/Core/FileStorage.cs:16-22 | src/app/dev/platforms/desktop/DevToys.Windows/Core/FileStorage.cs:19-25 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 4 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 4 times. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
D4 · Code Duplication · Duplicated block (13 lines × 4) · ×1
  • Duplicated block (13 lines × 4) src/app/dev/platforms/desktop/DevToys.CLI/Core/FileStorage/FileStorage.cs:29 — src/app/dev/platforms/desktop/DevToys.CLI/Core/FileStorage/FileStorage.cs:29-41 | src/app/dev/platforms/desktop/DevToys.Linux/Core/FileStorage.cs:26-38 | src/app/dev/platforms/desktop/DevToys.MacOS/Core/FileStorage.cs:25-38 | src/app/dev/platforms/desktop/DevToys.Windows/Core/FileStorage.cs:28-40 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 4 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 4 times. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
D4 · Code Duplication · Duplicated block (9 lines × 3) · ×1
  • Duplicated block (9 lines × 3) src/app/dev/platforms/desktop/DevToys.CLI/Core/Settings/SettingsStorage.cs:32 — src/app/dev/platforms/desktop/DevToys.CLI/Core/Settings/SettingsStorage.cs:32-40 | src/app/dev/platforms/desktop/DevToys.Linux/Core/SettingsStorage.cs:32-40 | src/app/dev/platforms/desktop/DevToys.Windows/Core/SettingsStorage.cs:33-41 — before extracting anything, compare `src/app/dev/platforms/desktop/DevToys.CLI/Core/Settings/SettingsStorage.cs` and `src/app/dev/platforms/desktop/DevToys.Linux/Core/SettingsStorage.cs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 49 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. 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 (5 lines × 3) · ×1
  • Duplicated block (5 lines × 3) src/app/dev/DevToys.Blazor/Components/UIElements/UIDataGridPresenter.razor.cs:77 — src/app/dev/DevToys.Blazor/Components/UIElements/UIDataGridPresenter.razor.cs:77-81 | src/app/dev/DevToys.Blazor/Components/UIElements/UIDiffTextInputPresenter.razor.cs:134-138 | src/app/dev/DevToys.Blazor/Components/UIElements/UITextInputWrapper.razor.cs:334-338 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from all 3 call sites, so a change lands once. 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 (7 lines × 3) · ×1
  • Duplicated block (7 lines × 3) src/app/dev/platforms/desktop/DevToys.Linux/Core/ThemeListener.cs:122 — src/app/dev/platforms/desktop/DevToys.Linux/Core/ThemeListener.cs:122-128 | src/app/dev/platforms/desktop/DevToys.MacOS/Core/ThemeListener.cs:148-154 | src/app/dev/platforms/desktop/DevToys.Windows/Core/ThemeListener.cs:123-129 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 3 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 3 times. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
D5 · Coupling · Off the main sequence · ×1
  • Off the main sequence: DevToys.Localization src/app/dev/DevToys.Localization/DevToys.Localization.csproj:1 — DevToys.Localization: abstractness 0.00, instability 0.14, distance 0.86 — zone of pain — concrete and depended on by 3 project(s), so it's rigid to change.
P7 · Outbound HTTP resilience · Outbound HTTP without resilience · ×1
  • Outbound HTTP without resilience src/app/dev/DevToys.Core/Web/WebClientService.cs:9 — `new()` builds an outbound HTTP client and nothing bounds it: no timeout is set on it and no retry or resilience policy wraps its calls in the type that owns it. This codebase ships libraries/tools rather than a service it operates, so the failure lands as a hung caller — a build step, a CLI run, a UI thread — with no way out.
R1 · Type Safety · Type Safety · ×1
  • Type Safety — 18 typed · 18 plain JS — the untyped files are src/app/dev/DevToys.Blazor/Assets/javascript/dom.js, src/app/dev/DevToys.Blazor/Assets/javascript/index.esm.js, src/app/dev/DevToys.Blazor/Assets/javascript/monacoEditor.js, src/app/dev/DevToys.Blazor/Assets/javascript/monacoEditorLanguage.js, src/app/dev/DevToys.Blazor/Assets/javascript/popover.js, src/app/dev/DevToys.Blazor/Components/Collections/DataGrid/DataGrid.razor.js (+12 more). 0 production file(s) opt out entirely with @ts-nocheck · 3 @ts-ignore suppression(s).
R10 · Code Duplication · Duplicated block (43 lines × 2 locations) · ×1
  • Duplicated block (43 lines × 2 locations) src/app/dev/DevToys.Blazor/Components/UIElements/UIFileSelectorPresenter.razor.ts:26 — src/app/dev/DevToys.Blazor/Components/UIElements/UIFileSelectorPresenter.razor.ts:26 · src/app/dev/DevToys.Blazor/Components/UIElements/UITextInputWrapper.razor.ts:40 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
R10 · Code Duplication · Duplicated block (18 lines × 2 locations) · ×1
  • Duplicated block (18 lines × 2 locations) src/app/dev/DevToys.Blazor/Assets/javascript/monacoEditor.ts:935 — src/app/dev/DevToys.Blazor/Assets/javascript/monacoEditor.ts:935 · src/app/dev/DevToys.Blazor/Assets/javascript/monacoEditor.ts:954 — all 2 copies are in the same file, and the SHAPE of this repetition could not be determined. It is not a run of declarations, a listing, a declaration header, a type body or a slice through a construct — and it was not measured as a run of executable statements either, so this row cannot tell you whether a function can stand where these lines are. Read the two spans before acting, because the move is opposite in the two cases. Where they are statements, the ordinary answer holds: give the shared part one home and call it from each site. Where they turn out to be declarations, a literal's entries, or the cases of an enumeration, there is no call site to call anything from, and collapsing them would delete what each copy pins — a shared base type, a generated set, or one exported constant each site refers to is the move instead, and sometimes the honest answer is that there is nothing to extract at all. Reported because the copies drift apart the first time only one of them is edited, which is true whichever of those they are.
R10 · Code Duplication · Duplicated block (13 lines × 2 locations) · ×1
  • Duplicated block (13 lines × 2 locations) src/app/dev/DevToys.Blazor/Assets/javascript/monacoEditor.ts:728 — src/app/dev/DevToys.Blazor/Assets/javascript/monacoEditor.ts:728 · src/app/dev/DevToys.Blazor/Assets/javascript/monacoEditor.ts:742 — 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.
R10 · Code Duplication · Duplicated block (10 lines × 2 locations) · ×1
  • Duplicated block (10 lines × 2 locations) src/app/dev/DevToys.Blazor/Assets/javascript/dom.ts:59 — src/app/dev/DevToys.Blazor/Assets/javascript/dom.ts:59 · src/app/dev/DevToys.Blazor/Assets/javascript/dom.ts:105 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
R10 · Code Duplication · Duplicated block (9 lines × 2 locations) · ×1
  • Duplicated block (9 lines × 2 locations) src/app/dev/DevToys.Blazor/Assets/javascript/dom.ts:36 — src/app/dev/DevToys.Blazor/Assets/javascript/dom.ts:36 · src/app/dev/DevToys.Blazor/Assets/javascript/dom.ts:64 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
R10 · Code Duplication · Duplicated block (8 lines × 2 locations) · ×1
  • Duplicated block (8 lines × 2 locations) src/app/dev/DevToys.Blazor/Assets/javascript/dom.ts:81 — src/app/dev/DevToys.Blazor/Assets/javascript/dom.ts:81 · src/app/dev/DevToys.Blazor/Assets/javascript/dom.ts:122 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
R10 · Code Duplication · Duplicated block (8 lines × 3 locations) · ×1
  • Duplicated block (8 lines × 3 locations) src/app/dev/DevToys.Blazor/Assets/javascript/monacoEditor.ts:831 — src/app/dev/DevToys.Blazor/Assets/javascript/monacoEditor.ts:831 · src/app/dev/DevToys.Blazor/Assets/javascript/monacoEditor.ts:856 · src/app/dev/DevToys.Blazor/Assets/javascript/monacoEditor.ts:866 — all 3 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
R10 · Code Duplication · Duplicated block (7 lines × 4 locations) · ×1
  • Duplicated block (7 lines × 4 locations) src/app/dev/DevToys.Blazor/Assets/javascript/monacoEditor.ts:487 — src/app/dev/DevToys.Blazor/Assets/javascript/monacoEditor.ts:487 · src/app/dev/DevToys.Blazor/Assets/javascript/monacoEditor.ts:497 · src/app/dev/DevToys.Blazor/Assets/javascript/monacoEditor.ts:507 · src/app/dev/DevToys.Blazor/Assets/javascript/monacoEditor.ts:517 — all 4 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
R2 · Cyclomatic Complexity · Complex function placePopover (cyclomatic 67, cognitive 113) · ×1
  • Complex function placePopover (cyclomatic 67, cognitive 113) src/app/dev/DevToys.Blazor/Assets/javascript/popover.ts:328 — placePopover has cyclomatic complexity 67 and cognitive complexity 113; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
R2 · Cyclomatic Complexity · Complex function calculatePopoverPosition (cyclomatic 19, cognitive 18) · ×1
  • Complex function calculatePopoverPosition (cyclomatic 19, cognitive 18) src/app/dev/DevToys.Blazor/Assets/javascript/popover.ts:237 — calculatePopoverPosition has cyclomatic complexity 19 and cognitive complexity 18; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
R2 · Cyclomatic Complexity · Complex function callback (cyclomatic 15, cognitive 49) · ×1
  • Complex function callback (cyclomatic 15, cognitive 49) src/app/dev/DevToys.Blazor/Assets/javascript/popover.ts:72 — callback has cyclomatic complexity 15 and cognitive complexity 49; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
R3 · Large Files · src/app/dev/DevToys.Blazor/Assets/javascript/monacoEditor.ts · ×1
  • src/app/dev/DevToys.Blazor/Assets/javascript/monacoEditor.ts: 887 lines of code src/app/dev/DevToys.Blazor/Assets/javascript/monacoEditor.ts:1 — src/app/dev/DevToys.Blazor/Assets/javascript/monacoEditor.ts has 887 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files · src/app/dev/DevToys.Blazor/Assets/javascript/popover.ts · ×1
  • src/app/dev/DevToys.Blazor/Assets/javascript/popover.ts: 418 lines of code src/app/dev/DevToys.Blazor/Assets/javascript/popover.ts:1 — src/app/dev/DevToys.Blazor/Assets/javascript/popover.ts has 418 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R6 · Tooling · No test, lint or typecheck script · ×1
  • No test, lint or typecheck script — test ✗ · lint ✗ · typecheck ✗ — read from this repository's package.json scripts and corroborated against its CI workflows. A script counts when its name or command matches the step: `test` for the suite, `lint` or `prettier` for linting, `typecheck`/`type-check`/`tsc` for type checking. ✗ therefore means no script or CI step under those names was found, NOT that the step is absent from your pipeline — a task invoked by a runner this check does not read, or named something else entirely, is not seen and is worth confirming before acting on a cross. A ✓ means the wiring is DECLARED — a script or CI step under those names exists. It is not a statement that the step passes, or that it runs at all: nothing here installs a dependency or executes a suite.
SC1 · Supply-chain hygiene · JavaScript dependencies are not locked · ×1
  • JavaScript dependencies are not locked — No package-lock.json / yarn.lock / pnpm-lock.yaml / bun.lock — JS installs aren't reproducible (SSDF PW.4.4). Commit your package manager's lockfile and install from it (`npm ci`, `yarn --immutable`, `pnpm i --frozen-lockfile` or `bun i --frozen-lockfile`). Advisory — never scored.
X1 · Async correctness · Blocking `StreamWriter.Flush` inside an `async` method · ×1
  • Blocking `StreamWriter.Flush` inside an `async` method src/app/dev/DevToys.Api/Core/OneOfExtensions.cs:62 — `StreamWriter.Flush` blocks the thread on I/O while `StreamWriter.FlushAsync` exists to wait without one — inside a method that is already `async`, await the twin.
X1 · Async correctness · Sync-over-async (deadlock risk) through `.Result` · ×1
  • Sync-over-async (deadlock risk) through `.Result` src/app/dev/DevToys.Api/Core/Threading/AsyncLazy.cs: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.
X1 · Async correctness · Sync-over-async (deadlock risk) through `.Wait(…)` · ×1
  • Sync-over-async (deadlock risk) through `.Wait(…)` src/app/dev/DevToys.Core/Logging/FileLoggerProvider.cs:48 — `.Wait(…)` blocks this thread until the task completes or the bound expires — sync-over-async: it can deadlock under a synchronization context and it parks a thread while it waits. `await` the task (with `.WaitAsync(timeout, token)` where the bound matters).
X1 · Async correctness · Blocking `StreamWriter.Write` inside an `async` method · ×1
  • Blocking `StreamWriter.Write` inside an `async` method src/app/dev/DevToys.Blazor/Components/UIElements/UITextInputWrapper.razor.cs:239 — `StreamWriter.Write` blocks the thread on I/O while `StreamWriter.WriteAsync` exists to wait without one — inside a method that is already `async`, await the twin.
X18 · Disposal-pattern correctness · Disposable created and abandoned in the method that made it · ×1
  • Disposable created and abandoned in the method that made it src/app/dev/platforms/desktop/DevToys.CLI/Program.cs:74 — `mefComposer` is a `MefComposer`, which implements `IDisposable`, and it is created here (line 74). Every use of it in `MainAsync` 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 mefComposer = …;`), which releases it at the end of the scope on every path including a throw.
X3 · Exception handling · Swallowed exception (caught, then discarded) · ×1
  • Swallowed exception (caught, then discarded) src/app/dev/DevToys.Blazor/Components/UIElements/UIImageViewerPresenter.razor.cs:259 — `catch (Exception)` does nothing with the exception it caught — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch. Log it through whatever this codebase already uses to report problems, or let it propagate; if one specific failure genuinely cannot matter, catch exactly that exception type and say why in a comment on the catch.
Minor — 217 finding(s)
D34 · Knowledge Freshness · Orphaned file · ×162
  • Orphaned file src/app/dev/DevToys.Blazor/Components/Text/MonacoEditor/Monaco/Editor/EditorOptions.cs:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file src/app/dev/DevToys.Blazor/BuiltInTools/Settings/SettingsGuiTool.cs:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file src/app/dev/DevToys.Api/Tool/GUI/Components/IUISetting.cs:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file src/app/dev/platforms/desktop/DevToys.Windows/Controls/MicaWindowWithOverlay.xaml.cs:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file src/app/dev/DevToys.Business/ViewModels/MainWindowViewModel.cs:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file src/app/dev/DevToys.Api/Core/ObservableHashSet.cs:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file src/app/dev/DevToys.Blazor/Components/UIElements/UITextInputWrapper.razor.cs:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file src/build/Build.cs:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file REDACTED:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file src/app/dev/DevToys.Blazor/Components/Text/MonacoEditor/RicherMonacoEditorDiffBase.cs:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file src/app/dev/DevToys.Core/Tools/SmartDetectionService.cs:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file src/app/dev/DevToys.Api/Tool/GUI/Components/IUIMultiLineTextInput.cs:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file src/app/dev/DevToys.Blazor/Components/Text/MonacoEditor/MonacoEditorBase.cs:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file src/app/dev/DevToys.Blazor/Components/UIElements/UIFileSelectorPresenter.razor.cs:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file src/app/dev/platforms/desktop/DevToys.CLI/Core/OneOfParser.cs:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file src/app/dev/DevToys.Blazor/Components/UIElements/UIMultiLineTextInputPresenter.razor.cs:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file src/app/dev/DevToys.Api/Tool/GUI/Components/IUIInfoBar.cs:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file src/app/dev/DevToys.Blazor/BuiltInTools/ExtensionsManager/ExtensionInstallationManager.cs:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file src/app/dev/DevToys.Blazor/Components/UIElements/UIImageViewerPresenter.razor.cs:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file src/app/dev/platforms/desktop/DevToys.Windows/MainWindow.xaml.cs:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file src/app/dev/DevToys.Blazor/Pages/Index.razor.cs:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file src/app/dev/DevToys.Api/Tool/GUI/Components/IUISettingGroup.cs:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file src/app/dev/platforms/desktop/DevToys.MacOS/Controls/BlazorWebView/BlazorWebViewManager.cs:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file src/app/dev/DevToys.Api/Tool/GUI/Components/IUIDataGrid.cs:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file src/app/dev/DevToys.Blazor/Components/Text/TextBox/TextBox.razor.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.
  • + 137 more in this group — see findings.md.
X10 · Duplicated predicate · Duplicated predicate · ×25
  • Duplicated predicate src/app/dev/platforms/desktop/DevToys.CLI/Core/FileStorage/FileStorage.cs:50 — `File.Exists(relativeOrAbsoluteFilePath) && replaceIfExist` appears character-identically in 4 files — src/app/dev/platforms/desktop/DevToys.CLI/Core/FileStorage/FileStorage.cs, src/app/dev/platforms/desktop/DevToys.Linux/Core/FileStorage.cs, src/app/dev/platforms/desktop/DevToys.MacOS/Core/FileStorage.cs, src/app/dev/platforms/desktop/DevToys.Windows/Core/FileStorage.cs. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate src/app/dev/platforms/desktop/DevToys.MacOS/Controls/BlazorWebView/BlazorWKWebView.cs:229 — `HostPage == null || _webViewManager != null` appears character-identically in 2 files — src/app/dev/platforms/desktop/DevToys.Linux/Components/BlazorWebView/BlazorWebView.cs, src/app/dev/platforms/desktop/DevToys.MacOS/Controls/BlazorWebView/BlazorWKWebView.cs. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate src/app/dev/DevToys.Blazor/Components/BasicInput/ComboBox/ComboBox.razor.cs:55 — `IsActuallyEnabled && ContextMenuService.TryOpenContextMenu()` appears character-identically in 2 files — src/app/dev/DevToys.Blazor/Components/BasicInput/ComboBox/ComboBox.razor.cs, src/app/dev/DevToys.Blazor/Components/BasicInput/DropDownButton/DropDownButton.razor.cs. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate src/app/dev/DevToys.Blazor/Components/Feedback/ProgressBar/ProgressBar.razor.cs:21 — `IsIndeterminate && AdditionalAttributes is not null` appears character-identically in 2 files — src/app/dev/DevToys.Blazor/Components/Feedback/ProgressBar/ProgressBar.razor.cs, src/app/dev/DevToys.Blazor/Components/Feedback/ProgressRing/ProgressRing.razor.cs. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate src/app/dev/DevToys.Core/OSHelper.cs:18 — `OperatingSystem.IsLinux() || OperatingSystem.IsFreeBSD()` appears character-identically in 2 files — src/app/dev/DevToys.Blazor/BuiltInTools/ExtensionsManager/ExtensionInstallationManager.cs, src/app/dev/DevToys.Core/OSHelper.cs. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate src/app/dev/DevToys.Blazor/Components/Collections/DataGrid/DataGrid.razor.cs:115 — `SelectedIndex == -1 || SelectedIndex == 0` appears character-identically in 2 files — src/app/dev/DevToys.Blazor/Components/Collections/DataGrid/DataGrid.razor.cs, src/app/dev/DevToys.Blazor/Components/Collections/ListBox/SelectBase.cs. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate src/build/AppVersion/CSharpUpdater.cs:52 — `VersionString.TryParse(g.Value, out VersionString? v) && v is not null` appears character-identically in 2 files — src/build/AppVersion/CSharpUpdater.cs, src/build/AppVersion/ProjectUpdater.cs. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate src/app/dev/DevToys.Blazor/Components/BasicInput/DropDownButton/DropDownButton.razor.cs:121 — `_listBox is not null && _listBox.SelectedItem is not null && _listBox.SelectedItem.IsEnabled` appears character-identically in 2 files — src/app/dev/DevToys.Blazor/Components/BasicInput/DropDownButton/DropDownButton.razor.cs, src/app/dev/DevToys.Blazor/Components/Menu/ContextMenu/ContextMenu.razor.cs. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate src/app/dev/DevToys.Blazor/Components/Menu/NavBar/NavBar.razor.js:22 — `(event.ctrlKey || event.metaKey) && event.key === "f"` appears character-identically in 2 files — src/app/dev/DevToys.Blazor/Components/Menu/NavBar/NavBar.razor.js, src/app/dev/DevToys.Blazor/Components/Menu/NavBar/NavBar.razor.ts. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate src/app/dev/DevToys.Blazor/Assets/javascript/popover.js:90 — `childNode.id && childNode.id.startsWith("popover-")` appears character-identically in 2 files — src/app/dev/DevToys.Blazor/Assets/javascript/popover.js, src/app/dev/DevToys.Blazor/Assets/javascript/popover.ts. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate src/app/dev/DevToys.Blazor/Assets/javascript/popover.js:261 — `classList.contains("popover-overflow-flip-onopen") || classList.contains("popover-overflow-flip-always")` appears character-identically in 2 files — src/app/dev/DevToys.Blazor/Assets/javascript/popover.js, src/app/dev/DevToys.Blazor/Assets/javascript/popover.ts. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate src/app/dev/DevToys.Blazor/Assets/javascript/popover.js:288 — `deltaBottom < graceMargin && deltaToLeft < graceMargin && spaceToTop >= selfRect.height && deltaToRight >= selfRect.width` appears character-identically in 2 files — src/app/dev/DevToys.Blazor/Assets/javascript/popover.js, src/app/dev/DevToys.Blazor/Assets/javascript/popover.ts. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate src/app/dev/DevToys.Blazor/Assets/javascript/popover.js:272 — `deltaBottom < graceMargin && deltaToRight < graceMargin && spaceToTop >= selfRect.height && deltaToLeft >= selfRect.width` appears character-identically in 2 files — src/app/dev/DevToys.Blazor/Assets/javascript/popover.js, src/app/dev/DevToys.Blazor/Assets/javascript/popover.ts. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate src/app/dev/DevToys.Blazor/Assets/javascript/popover.js:275 — `deltaBottom < graceMargin && spaceToTop >= selfRect.height` appears character-identically in 2 files — src/app/dev/DevToys.Blazor/Assets/javascript/popover.js, src/app/dev/DevToys.Blazor/Assets/javascript/popover.ts. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate src/app/dev/DevToys.Blazor/Assets/javascript/popover.js:294 — `deltaToLeft < graceMargin && deltaToRight >= selfRect.width` appears character-identically in 2 files — src/app/dev/DevToys.Blazor/Assets/javascript/popover.js, src/app/dev/DevToys.Blazor/Assets/javascript/popover.ts. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate src/app/dev/DevToys.Blazor/Assets/javascript/popover.js:278 — `deltaToRight < graceMargin && deltaToLeft >= selfRect.width` appears character-identically in 2 files — src/app/dev/DevToys.Blazor/Assets/javascript/popover.js, src/app/dev/DevToys.Blazor/Assets/javascript/popover.ts. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate src/app/dev/DevToys.Blazor/Assets/javascript/popover.js:312 — `deltaTop < graceMargin && deltaBottom >= 0` appears character-identically in 2 files — src/app/dev/DevToys.Blazor/Assets/javascript/popover.js, src/app/dev/DevToys.Blazor/Assets/javascript/popover.ts. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate src/app/dev/DevToys.Blazor/Assets/javascript/popover.js:325 — `deltaTop < graceMargin && deltaToLeft < graceMargin && deltaBottom >= 0 && deltaToRight >= selfRect.width` appears character-identically in 2 files — src/app/dev/DevToys.Blazor/Assets/javascript/popover.js, src/app/dev/DevToys.Blazor/Assets/javascript/popover.ts. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate src/app/dev/DevToys.Blazor/Assets/javascript/popover.js:309 — `deltaTop < graceMargin && deltaToRight < graceMargin && deltaBottom >= 0 && deltaToLeft >= selfRect.width` appears character-identically in 2 files — src/app/dev/DevToys.Blazor/Assets/javascript/popover.js, src/app/dev/DevToys.Blazor/Assets/javascript/popover.ts. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate src/app/dev/DevToys.Blazor/Components/UIElements/UITextInputWrapper.razor.js:44 — `e.dataTransfer.items.length === 1 && e.dataTransfer.items[0].kind === "file"` appears character-identically in 2 files — src/app/dev/DevToys.Blazor/Components/UIElements/UITextInputWrapper.razor.js, src/app/dev/DevToys.Blazor/Components/UIElements/UITextInputWrapper.razor.ts. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate src/app/dev/DevToys.Blazor/Components/UIElements/UIFileSelectorPresenter.razor.js:33 — `e.dataTransfer.items.length > 0 && e.dataTransfer.items[0].kind === "file"` appears character-identically in 2 files — src/app/dev/DevToys.Blazor/Components/UIElements/UIFileSelectorPresenter.razor.js, src/app/dev/DevToys.Blazor/Components/UIElements/UIFileSelectorPresenter.razor.ts. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate src/app/dev/DevToys.Blazor/Components/Text/TextBox/TextBox.razor.js:35 — `e.key === "ArrowDown" || e.key === "ArrowUp"` appears character-identically in 2 files — src/app/dev/DevToys.Blazor/Components/Text/TextBox/TextBox.razor.js, src/app/dev/DevToys.Blazor/Components/Text/TextBox/TextBox.razor.ts. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate src/app/dev/DevToys.Blazor/Components/UIElements/UIFileSelectorPresenter.razor.js:45 — `e.x > rect.left + rect.width || e.x < rect.left || e.y > rect.top + rect.height || e.y < rect.top` appears character-identically in 4 files — src/app/dev/DevToys.Blazor/Components/UIElements/UIFileSelectorPresenter.razor.js, src/app/dev/DevToys.Blazor/Components/UIElements/UIFileSelectorPresenter.razor.ts, src/app/dev/DevToys.Blazor/Components/UIElements/UITextInputWrapper.razor.js, src/app/dev/DevToys.Blazor/Components/UIElements/UITextInputWrapper.razor.ts. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate src/app/dev/DevToys.Blazor/Assets/javascript/dom.js:35 — `focusedElement && (focusedElement.tagName.toLowerCase() === 'input')` appears character-identically in 2 files — src/app/dev/DevToys.Blazor/Assets/javascript/dom.js, src/app/dev/DevToys.Blazor/Assets/javascript/dom.ts. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate src/app/dev/DevToys.Blazor/Components/UIElements/UIWebViewPresenter.razor.js:5 — `iframe.contentDocument || iframe.contentWindow.document` appears character-identically in 2 files — src/app/dev/DevToys.Blazor/Components/UIElements/UIWebViewPresenter.razor.js, src/app/dev/DevToys.Blazor/Components/UIElements/UIWebViewPresenter.razor.ts. 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.
IC1 · Incompleteness & stubs · Commented-out code · ×6
  • Commented-out code src/app/dev/DevToys.Blazor/Components/UIElements/UITextInputWrapper.razor.cs:263 — 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 src/app/dev/DevToys.Blazor/Components/UIElements/UITextInputWrapper.razor.cs:327 — 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 src/app/dev/platforms/desktop/DevToys.MacOS/Controls/BlazorWebView/BlazorWebViewManager.cs:265 — 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 src/app/dev/platforms/desktop/DevToys.MacOS/Controls/BlazorWebView/BlazorWebViewManager.cs:274 — 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 src/app/dev/platforms/desktop/DevToys.Windows/Core/Helpers/ImageHelper.cs:124 — 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 src/generators/ResxHelperGenerator/CultureHelperGenerator.cs:28 — A line of code has been commented out rather than removed — dead weight that rots and confuses. Delete it (version control remembers).
D34 · Knowledge Freshness · Most significant orphaned file · ×3
  • Most significant orphaned file src/app/dev/DevToys.Core/Tools/GuiToolProvider.cs:1 — One of the orphaned files carrying the most lost knowledge — ranked by size weighted by the file's role in the codebase, the same weighting behind the score above, so core code outranks equally large plumbing. A reasonable place to start a read-through before the aggregate risk above bites.
  • Most significant orphaned file src/app/dev/DevToys.Blazor/Components/Text/MonacoEditor/RicherMonacoEditorBase.cs:1 — One of the orphaned files carrying the most lost knowledge — ranked by size weighted by the file's role in the codebase, the same weighting behind the score above, so core code outranks equally large plumbing. A reasonable place to start a read-through before the aggregate risk above bites.
  • Most significant orphaned file src/app/dev/DevToys.Blazor/Components/Text/MonacoEditor/Monaco/TextModel.cs:1 — One of the orphaned files carrying the most lost knowledge — ranked by size weighted by the file's role in the codebase, the same weighting behind the score above, so core code outranks equally large plumbing. A reasonable place to start a read-through before the aggregate risk above bites.
AX6 · Interface segregation · Fat interface · ×2
  • Fat interface: IUIInfoBar (20 members) src/app/dev/DevToys.Api/Tool/GUI/Components/IUIInfoBar.cs:6 — `IUIInfoBar` declares 20 members: `IsOpened`, `IsClosable`, `IsIconVisible`, `Title`, `Description`, `ActionButtonText`, `IsActionButtonAccent`, `Severity`, `OnCloseAction`, `OnActionButtonClick`, `IsOpenedChanged`, `IsClosableChanged`, `IsIconVisibleChanged`, `TitleChanged`, `DescriptionChanged`, `ActionButtonTextChanged`, `IsActionButtonAccentChanged`, `SeverityChanged`, `OnCloseActionChanged`, `OnActionButtonClickChanged`. Counted as the author wrote them — a property is ONE member and its get/set accessors are not counted separately, and an event counts once. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces.
  • Fat interface: IUIMultiLineTextInput (16 members) src/app/dev/DevToys.Api/Tool/GUI/Components/IUIMultiLineTextInput.cs:6 — `IUIMultiLineTextInput` declares 16 members: `HighlightedSpans`, `HoverTooltips`, `TextInputToSynchronizeScrollBarWith`, `SyntaxColorizationLanguageName`, `IsExtendableToFullScreen`, `WrapMode`, `LineNumberMode`, `Selection`, `HoverTooltipChanged`, `HighlightedSpansChanged`, `TextInputToSynchronizeScrollBarWithChanged`, `SyntaxColorizationLanguageNameChanged`, `IsExtendableToFullScreenChanged`, `WrapModeChanged`, `LineNumberModeChanged`, `SelectionChanged`. Counted as the author wrote them — a property is ONE member and its get/set accessors are not counted separately, and an event counts once. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces.
M4 · Documentation accuracy · README/code drift · ×2
  • README/code drift README.md:1 — README claims a Dockerfile but the evidence shows no Docker-related project — searched for: `Dockerfile`. Each was matched case- and separator-insensitively against file and directory NAMES anywhere in the tree, and against the CONTENTS of manifest and configuration files (package.json and other *.json, *.csproj, *.props, *.sln/*.slnx, *.yml, *.toml, *.config, tool configs such as eslint.config.js, Dockerfile); the README's own prose never counts, so a claim is never refuted by merely being made. Nothing outside that search was read — a footprint living only in a submodule, in a file type not listed here, or under a name none of those terms matches is not seen, and this row is then wrong.
  • README/code drift CONTRIBUTING.md:141 — CONTRIBUTING.md runs `dotnet build src/DevToys.Tools/DevToys.Tools.csproj -c Debug`, but `src/DevToys.Tools/DevToys.Tools.csproj` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
X4 · Structured logging · Interpolated log message defeats structured logging · ×2
  • Interpolated log message defeats structured logging src/app/dev/DevToys.Blazor/Core/Extensions/IJSRuntimeExtensions.cs:47 — Logging an interpolated string (`$"..."`) collapses the event to plain text — you lose the named, queryable properties structured logging exists for. Use a message template with placeholders: `LogInformation("User {UserId} did {Action}", id, action)`. If these calls go through a logging wrapper that only accepts a pre-formatted string, give the wrapper a template+args overload that forwards to the underlying logger, then migrate call sites to it.
  • Interpolated log message defeats structured logging src/app/dev/DevToys.Blazor/Core/Extensions/IJSRuntimeExtensions.cs:90 — Logging an interpolated string (`$"..."`) collapses the event to plain text — you lose the named, queryable properties structured logging exists for. Use a message template with placeholders: `LogInformation("User {UserId} did {Action}", id, action)`. If these calls go through a logging wrapper that only accepts a pre-formatted string, give the wrapper a template+args overload that forwards to the underlying logger, then migrate call sites to it.
D20 · ADR Quality · No ADRs found · ×1
  • No ADRs found — No ADRs found. No recognised ADR directory (`docs/adr/`, `docs/decisions/`, `adr/`, `docs/rfcs/`, an `ADR0001/` folder, or their siblings) exists anywhere in this tree. What was searched, so you can tell an empty log from a search that missed one: every directory under the tree (build output, dependencies and VCS metadata excepted), for a document that is either any non-index page inside a recognised ADR directory, whatever its name and however deeply nested (`docs/adr/use-postgres.md`, `docs/adr/2024/0001-x.md`); or a file anywhere whose name is ADR-shaped (`0001-use-postgres.md`, `adr-012-caching.md`); or, when neither turned anything up, a document carrying the decision-record signature (an "Architecture Decision Record" heading, or Status / Context / Decision / Consequences as section headings). A decision log that clears none of these — unnumbered files outside any recognised directory, without those headings — is not seen by this check and this row is then wrong. If that is your case, say so rather than renaming anything; otherwise, consider recording architectural decisions in `docs/adr/`.
D26 · Project Cohesion · Projects may be oversized for their cohesion · ×1
  • Projects may be oversized for their cohesion — 1 of 12 project(s) overshoot their size bounds, lowering Project Cohesion to 8.3/10. The most over is `DevToys.Blazor` (15519 LoC, 246 public types across 14 namespaces). Review these for cohesion — split a project that spans unrelated responsibilities.
D30 · Dependency Vulnerabilities · Scanner failed to run · ×1
  • REDACTED
D34 · Knowledge Freshness · Concentrated knowledge decay · ×1
  • Concentrated knowledge decay — 165 of 167 significant files have no living knowledge, while the repository is still being changed at a low rate (3 commit(s) in the last 90 days) — so this is one repo-wide knowledge-decay state, not 165 separate risks. Counted over 167 of the 538 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over. The code moved on without the people who understood these files: document them or schedule a read-through before the next change lands in them.
D36 · Supply-chain Provenance & Signing · REDACTED · ×1
  • REDACTED
D36 · Supply-chain Provenance & Signing · REDACTED · ×1
  • REDACTED
D43 · Malicious Dependencies · Scanner failed to run · ×1
  • REDACTED
M2 · Architecture documentation · No ADRs · ×1
  • No ADRs — No Architecture Decision Records found — no conventional ADR directory, no numbered `NNNN-title` documents in any markup this check reads, and nothing ADR-shaped by content. Design rationale recorded elsewhere (a design-notes tree, a mailing list, pull-request discussion) is not visible to this check and is not re-findable per decision, so a future maintainer cannot ask why one choice was made and get an answer.
M2 · Architecture documentation · No architecture diagram/doc · ×1
  • No architecture diagram/doc — No C4/Structurizr/PlantUML/Mermaid/Graphviz/D2 diagram, no drawn diagram named for the architecture, no file named `architecture` or `design` in any markup this check reads, and nothing in the README, docs or contributor guides that announces the shape — no `## Architecture` heading, no "architecture overview"/"high-level design" phrasing, no "the architecture is …" introduction, no guided code tour. A shape laid out in prose that never names itself as the architecture is not visible to this check, and neither is one kept outside the repository, so this row reports the absence of a re-findable shape document — not evidence that nobody wrote the shape down.
P10 · Library API & versioning · Large public API surface · ×1
  • Large public API surface — 117/163 types (72%) are public. For a library, every public type is a stability contract — make internal-by-default and expose only the intended API.
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 2435 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 · Changelog looks stale/thin · ×1
  • Changelog looks stale/thin — The changelog this check read carries 0 versioned entries, against a bar of 3. Counted as either the distinct `x.y.z` versions it names (a link's target is not counted) or its version-shaped section headings (`## [1.2.0]`, `## V14.x.x`, `## Updates in 8.0.x`), whichever is the larger — so a log sectioned by minor series counts its sections, not its individual patch numbers. Entries recorded somewhere this check does not read — release notes generated at tag time from a generator config it did not recognise, or a log kept outside the repository — are not counted here, and this row is about what is re-findable in the tree rather than about how often you release.
PF1 · Benchmark discipline · No performance benchmarks · ×1
  • No performance benchmarks — No benchmark suite was found by the two searches this check runs. FIRST, a BenchmarkDotNet package reference in any project file — every project the workspace loaded, plus a walk of project files on disk that never loaded, because a benchmark suite is exactly the project a partial load drops. SECOND, a script harness: a file whose name contains `benchmark` and ends `.py`, `.sh`, `.ps1`, `.bash`, `.rb`, `.js` or `.mjs`, credited ONLY when this repository's CI text also mentions benchmarks — a harness no pipeline runs is read as a fixture, deliberately. Neither search can see a benchmark suite in another ecosystem's idiom (a Go `testing.B` file, a JMH or criterion project, a pytest-benchmark run), so this is 'no benchmark found by those two searches', not a verdict that the repository has none. Where code is performance-sensitive, a benchmark guards against silent regressions — but it's a bonus here, not a deduction.
X2 · Cancellation propagation · Not all async methods take a CancellationToken · ×1
  • Not all async methods take a CancellationToken — Only 15/207 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 · Null-forgiving operator (`!`) suppressions reduce the NRT score · ×1
  • Null-forgiving operator (`!`) suppressions reduce the NRT score — ~1.8 `!` suppressions per 1k syntax nodes — 247 suppression(s) across the 134823 syntax node(s) in code where nullable warnings are ENABLED, which is the only code a `!` can suppress anything in (a `!` under `#nullable disable` is inert and is not counted, and its file's nodes are not in the denominator). Each one tells the compiler to trust you about null, suppressing the very safety NRTs provide.
Minor — 12 finding(s)
D19 · Documentation Quality · XML-doc coverage · ×11
  • XML-doc coverage: DevToys.CLI src/app/dev/platforms/desktop/DevToys.CLI/DevToys.CLI.csproj — DevToys.CLI: 0 % XML-doc coverage (0/20).
  • XML-doc coverage: DevToys.Api src/app/dev/DevToys.Api/DevToys.Api.csproj — DevToys.Api: 72 % XML-doc coverage (655/915).
  • XML-doc coverage: DevToys.Core src/app/dev/DevToys.Core/DevToys.Core.csproj — DevToys.Core: 36 % XML-doc coverage (70/193).
  • XML-doc coverage: DevToys.Localization src/app/dev/DevToys.Localization/DevToys.Localization.csproj — DevToys.Localization: 98 % XML-doc coverage (110/112).
  • XML-doc coverage: ResxHelperGenerator src/generators/ResxHelperGenerator/ResxHelperGenerator.csproj — ResxHelperGenerator: 0 % XML-doc coverage (0/3).
  • XML-doc coverage: DevToys.Business src/app/dev/DevToys.Business/DevToys.Business.csproj — DevToys.Business: 33 % XML-doc coverage (1/3).
  • XML-doc coverage: DevToys.Blazor src/app/dev/DevToys.Blazor/DevToys.Blazor.csproj — DevToys.Blazor: 47 % XML-doc coverage (671/1427).
  • XML-doc coverage: DevToys.Windows src/app/dev/platforms/desktop/DevToys.Windows/DevToys.Windows.csproj — DevToys.Windows: 6 % XML-doc coverage (5/88).
  • XML-doc coverage: DevToys.MacOS src/app/dev/platforms/desktop/DevToys.MacOS/DevToys.MacOS.csproj — DevToys.MacOS: 4 % XML-doc coverage (3/75).
  • XML-doc coverage: DevToys.Linux src/app/dev/platforms/desktop/DevToys.Linux/DevToys.Linux.csproj — DevToys.Linux: 6 % XML-doc coverage (3/51).
  • XML-doc coverage: _build src/build/_build.csproj — _build: 4 % XML-doc coverage (1/26).
D10 · Test Quality · Mock framework · ×1
  • Mock framework: Moq — DevToys.UnitTests references Moq.

Appendix B — Reproduction & audit trail

Every external tool invocation behind a deep-scan dimension — the tool, its captured version, the exact command, how many findings it yielded, and a link to the retained raw output. To reproduce any finding: check out the same commit and run the command shown (repo-relative — never an absolute scratch path). The complete raw scanner output is retained verbatim under artifacts/raw/ (indexed in artifacts/raw/index.json); per-invocation exit codes and wall-clock durations are in sidecar.json — kept out of this table so the rendered report stays byte-identical across runs of the same commit.

DimensionToolVersionCommandFindingsRaw output
D28 · Secrets (history)gitleaks—gitleaks detect --no-banner --config /opt/gitleaks-rules/watchdog-gitleaks.toml --report-format json --report-path /tmp/watchdog-gitleaks-c4abbf0e75cf4d76ac8074deddb25a8c/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-c4abbf0e75cf4d76ac8074deddb25a8c/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 .15artifacts/raw/semgrep.json
D30 · Dependency Vulnerabilitiesdotnet—dotnet list src/DevToys-Windows.sln package --vulnerable --include-transitive --format json12artifacts/raw/dotnet-vulnerable.json
D30 · Dependency Vulnerabilitiesosv-scanner—osv-scanner --format json --recursive --experimental-disable-plugins transitivedependency/requirements --experimental-disable-plugins dotnet/csproj --experimental-disable-plugins dotnet/nugetcpm .0—
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) — `src/app/dev/DevToys.Blazor/Assets/javascript/monacoEditor.ts`, `src/app/dev/DevToys.Blazor/Assets/javascript/popover.ts`, `src/app/dev/platforms/desktop/DevToys.Linux/Components/BlazorWebView/BlazorWebView.cs`, `src/app/dev/platforms/desktop/DevToys.MacOS/Controls/BlazorWebView/BlazorWKWebView.cs` — so the PII/GDPR sweep did not cover the unparsed regions of them; rows reported elsewhere in those files are real.0—
D40 · Network Egress Confinementruntime-hardening—runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here.0—
D41 · Kernel & Syscall Confinementruntime-hardening—runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here.0—
D42 · Runtime Threat Enforcementruntime-hardening—runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here.0—
D43 · Malicious Dependenciesosv-scanner—osv-scanner --format json --recursive --experimental-disable-plugins transitivedependency/requirements --experimental-disable-plugins dotnet/csproj --experimental-disable-plugins dotnet/nugetcpm .0—
D43 · Malicious Dependenciestrivy—trivy fs --scanners vuln --format json --quiet --severity CRITICAL,HIGH,MEDIUM,LOW --skip-dirs **/bin/** --skip-dirs **/obj/** . --skip-db-update0artifacts/raw/trivy-fs.json

Run 01a165f3-1b36-7c02-8973-49eb0f43c2e6 · every finding is also locatable in findings.md, and the complete scoring record (with exit codes + durations) in sidecar.json.

Issues: 57 · Warnings: 361 · Recommendations: 217 · Info: 12 — Appendix A · all findings · full markdown report.
Generated by Watchdog — deterministic code-health analysis. 22-10-2026 @ 23:29 UTC.

Downloadable artifacts

Machine-readable and reproducible from this commit + frozen rubric — drop them straight into a contract appendix, a CRA dossier, or a downstream SCA / VEX tool.

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