Public report of ElectronNET/Electron.NET, published 12 November 2026. It has the same score, grades and number of
findings as the full report. The details of security findings (where they are in the code, which known
vulnerabilities and which passwords or keys were found) are left out, so nobody can use them against the project.
Public
Executive reportMeasured under the Code Assurance Index, an open standard for code quality, using its published scoring rules (rubric version 2026.11.3). Assert 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, 12 November 2026, 02:33 UTC · Survey ID cd_206f513a2d184fe080c6c5fe0fbe42c7
ElectronNET/Electron.NET
Measured 12 November 2026, 02:32 UTC, at code version 87cc6f9
Code coverage is not measured: No coverage collector is wired up.
Test reliability is not measured: The repo's test suite did not build.
CAI scoreWeak
CriticalWeakAdequateStrongExemplary
Up 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.
A medium codebase: 21,423 lines of product code in 18 projects, tests not counted · Estimated rebuild effort: about 0.1 person-years · Weakest lens: Production Readiness, 43
Findings by how serious they are
72 critical207 serious140 minor
6 dimensions are left out of the score. For each one, we either couldn't measure it in this code, or found no evidence of the safeguard we look 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
Canine Code Analyzer
Producer
Canine Development
Analyzer
Canine Code Analyzer engine 1.0.0
Measured
12 November 2026, 02:32 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 the Canine Code Analyzer. It is open to any tool that
implements it, and today the Canine Code Analyzer is the only one that does.
The score is deterministic, which means the same code always gets the same score. We work 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 ▸
80of 80 dimensions measured by tools.
392of 419 findings point to an exact file and line, so you can open each one in the code. The other 27 concern the repository as a whole, such as missing documentation.
80dimensions across 7 lenses, read from 21,423 lines of product code in 18 projects.
ElectronNET/Electron.NET falls short of our standard for production, in part because we found no automated security scanning of the code, its secrets or its dependencies. It scores 47 out of 100 and is rated Weak, and 49 of its 72 critical findings are security problems.
Production Readiness, at 43, is the weakest lens and counts most in the score. The best first steps are adding automated security scanning and adding tests for the code no test reaches, each worth about 4 points. Raising Production Readiness to 70 would lift the score to about 52.
Nineteen pipeline tools are referenced by a changeable name, so the build pipeline can be tampered with. Fourteen known security holes in the packages the code depends on can be used by attackers, and seven secrets can leak from the build pipeline. Pinning each tool to an exact version, updating the vulnerable packages and limiting each secret to its own step would close these risks. Fixing the weaknesses the scanner points to would fix the five security weaknesses in the code, and the two checks for vulnerable packages switched off need switching back on. The 13 sets of compiler warnings switched off in projects need turning back on in the build file.
The product code is 21,423 lines, about €17,000 to rebuild.
A lens is capped at Adequate while one of its dimensions scores below 4 out of 10, however well the rest of the lens does. That way a serious problem in one place always shows in the lens's rating.
How the score is built: what each lens counts forThe lenses don't count equally. The weakest lens counts most, the next weakest a little less, and so on, so a weak area pulls the score down instead of being averaged away. In the bar below, each part's width shows how much that lens counts and its colour shows its rating. Improving the widest part moves the score most, and as that lens improves, it counts for less, because another lens becomes the weakest.
We compare 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: 40 findings
These 40 critical or serious findings were in the previous survey, on 23 October 2026, and are gone from this one.
Dependency Vulnerabilities · High CVE: [GHSA redacted] REDACTED
Dependency Vulnerabilities · High CVE: [CVE redacted] REDACTED
Dependency Vulnerabilities · High CVE: REDACTED REDACTED
Dependency Vulnerabilities · High CVE: REDACTED REDACTED
Cancellation propagation · Async method without CancellationToken: ElectronBootstrap src/ElectronNET.WebApp/Program.cs
Cancellation propagation · Async method without CancellationToken: On src/ElectronNET.API/API/App.cs
Cancellation propagation · Async method without CancellationToken: Once src/ElectronNET.API/API/App.cs
Cancellation propagation · Async method without CancellationToken: ShowMessageBoxAsync src/ElectronNET.API/API/Dialog.cs
Cancellation propagation · Async method without CancellationToken: ShowMessageBoxAsync src/ElectronNET.API/API/Dialog.cs
Cancellation propagation · Async method without CancellationToken: ShowMessageBoxAsync src/ElectronNET.API/API/Dialog.cs
Cancellation propagation · Async method without CancellationToken: On src/ElectronNET.API/API/IpcMain.cs
Cancellation propagation · Async method without CancellationToken: Show src/ElectronNET.API/API/Tray.cs
Cancellation propagation · Async method without CancellationToken: Show src/ElectronNET.API/API/Tray.cs
Cancellation propagation · Async method without CancellationToken: SetMenuItems src/ElectronNET.API/API/Tray.cs
Cancellation propagation · Async method without CancellationToken: Show src/ElectronNET.API/API/Tray.cs
Cancellation propagation · Async method without CancellationToken: Destroy src/ElectronNET.API/API/Tray.cs
Cancellation propagation · Async method without CancellationToken: SetImage src/ElectronNET.API/API/Tray.cs
Cancellation propagation · Async method without CancellationToken: SetPressedImage src/ElectronNET.API/API/Tray.cs
Cancellation propagation · Async method without CancellationToken: SetToolTip src/ElectronNET.API/API/Tray.cs
Cancellation propagation · Async method without CancellationToken: SetTitle src/ElectronNET.API/API/Tray.cs
Cancellation propagation · Async method without CancellationToken: DisplayBalloon src/ElectronNET.API/API/Tray.cs
Cancellation propagation · Async method without CancellationToken: IsDestroyedAsync src/ElectronNET.API/API/Tray.cs
Cancellation propagation · Async method without CancellationToken: On src/ElectronNET.API/API/Tray.cs
Cancellation propagation · Async method without CancellationToken: Once src/ElectronNET.API/API/Tray.cs
Cancellation propagation · Async method without CancellationToken: CreateWindowAsync src/ElectronNET.API/API/WindowManager.cs
Cancellation propagation · Async method without CancellationToken: CreateWindowAsync src/ElectronNET.API/API/WindowManager.cs
Cancellation propagation · Async method without CancellationToken: CreateBrowserViewAsync src/ElectronNET.API/API/WindowManager.cs
Cancellation propagation · Async method without CancellationToken: On src/ElectronNET.API/Bridge/Events.cs
Cancellation propagation · Async method without CancellationToken: On src/ElectronNET.API/Bridge/Events.cs
Cancellation propagation · Async method without CancellationToken: Once src/ElectronNET.API/Bridge/Events.cs
Cancellation propagation · Async method without CancellationToken: Once src/ElectronNET.API/Bridge/Events.cs
Cancellation propagation · Async method without CancellationToken: Stop src/ElectronNET.API/Runtime/Services/LifetimeServiceBase.cs
Cancellation propagation · Async method without CancellationToken: RunReadyCallback src/ElectronNET.AspNet/Runtime/Controllers/RuntimeControllerAspNetBase.cs
Cancellation propagation · Async method without CancellationToken: ElectronBootstrap src/ElectronNET.ConsoleApp/Program.cs
Cancellation propagation · Async method without CancellationToken: Index src/ElectronNET.Samples.ElectronHostHook/Controllers/HomeController.cs
A11y enforcement · Accessibility enforcement below the top rung
Rebuild cost: about €17,000 · Estimate
Cost to rebuild
€5,600 to €28,000, for 93 to 294 hours of work, about 0.1 person-years for one engineer
Difficulty of the problem
Standard, judged from the kind of software and how it is built. Code that solves a harder problem, such as payments or medical bookings, costs more per line to write.
Quality factor
×0.7 at a score of 47. Better code takes more work to write, so the factor is ×1.0 at a score of 70, lower below it and higher above it.
Size
Medium: 21,423 lines of product code
Comment lines
The estimate prices 14,444 lines. Comment lines count towards the size of 21,423 lines but aren't priced as work.
What it is not
Not a quotation: nobody has offered to build it for that. Not a valuation: it says nothing about what the business is worth. Not a certified figure: no professional has signed it as one.
How the estimate is made: We price 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
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.
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 €17,000 to build again, about 0.1 person-years of work. Its weakest lens is Production Readiness, at 43 (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
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. Of all the actions in this report, it raises the score most for the work it takes: about 4 points for medium effort. The next survey will show the change in the score.
Based on: the ranked actions in Top priorities, by score gain and effort
Architecture — module dependency graph
Project dependencies, layered top-to-bottom; arrows show direction. Any dashed red edge points upward or sideways, which only happens where the projects form a dependency cycle. A graph without cycles has none.
Architecture: which parts of the code depend on which
The code is divided into modules, groups of code that each handle one part of the product, and a module depends on another when it uses code from it. The table lists the modules both down the side and across the top, in an order where each module should only use modules listed above it. A number in a cell means the module on that row uses the module in that column, and it counts the pairs of building blocks (types) that connect them. The one thing to look for is a mark above the diagonal line. It means two or more modules use each other in a loop (a dependency cycle), so none of them can be changed, tested or released on its own.
35 modules, with 34 dependencies between them. One loop runs through 2 of the modules, marked above the diagonal.
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.
81 pairs of types, where a type in ElectronNET.API uses a type in ElectronNET.API.Entities. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
ElectronNET.API uses ElectronNET.API.Entities, so a change to ElectronNET.API.Entities can break ElectronNET.API, while a change to ElectronNET.API can't break ElectronNET.API.Entities.
Position
Below the diagonal: ElectronNET.API uses a module listed above it, which is the healthy direction.
ElectronNET.API.Converter uses ElectronNET.API.Entities, so a change to ElectronNET.API.Entities can break ElectronNET.API.Converter, while a change to ElectronNET.API.Converter can't break ElectronNET.API.Entities.
Position
Below the diagonal: ElectronNET.API.Converter uses a module listed above it, which is the healthy direction.
ElectronNET.API.Extensions uses ElectronNET.API.Entities, so a change to ElectronNET.API.Entities can break ElectronNET.API.Extensions, while a change to ElectronNET.API.Extensions can't break ElectronNET.API.Entities.
Position
Below the diagonal: ElectronNET.API.Extensions uses a module listed above it, which is the healthy direction.
ElectronNET.AspNet.Middleware uses ElectronNET.AspNet.Services, so a change to ElectronNET.AspNet.Services can break ElectronNET.AspNet.Middleware, while a change to ElectronNET.AspNet.Middleware can't break ElectronNET.AspNet.Services.
Position
Below the diagonal: ElectronNET.AspNet.Middleware uses a module listed above it, which is the healthy direction.
ElectronNET.Converter uses ElectronNET.API.Entities, so a change to ElectronNET.API.Entities can break ElectronNET.Converter, while a change to ElectronNET.Converter can't break ElectronNET.API.Entities.
Position
Below the diagonal: ElectronNET.Converter uses a module listed above it, which is the healthy direction.
ElectronNET.Runtime.Services uses ElectronNET.Runtime.Data, so a change to ElectronNET.Runtime.Data can break ElectronNET.Runtime.Services, while a change to ElectronNET.Runtime.Services can't break ElectronNET.Runtime.Data.
Position
Below the diagonal: ElectronNET.Runtime.Services uses a module listed above it, which is the healthy direction.
src.ElectronNET_Host.ElectronHostHook uses src.ElectronNET_Host.ElectronHostHook.connector, so a change to src.ElectronNET_Host.ElectronHostHook.connector can break src.ElectronNET_Host.ElectronHostHook, while a change to src.ElectronNET_Host.ElectronHostHook can't break src.ElectronNET_Host.ElectronHostHook.connector.
Position
Below the diagonal: src.ElectronNET_Host.ElectronHostHook uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in src.ElectronNET_Samples_ElectronHostHook.ElectronHostHook uses a type in src.ElectronNET_Host.ElectronHostHook.connector.
src.ElectronNET_Samples_ElectronHostHook.ElectronHostHook uses src.ElectronNET_Host.ElectronHostHook.connector, so a change to src.ElectronNET_Host.ElectronHostHook.connector can break src.ElectronNET_Samples_ElectronHostHook.ElectronHostHook, while a change to src.ElectronNET_Samples_ElectronHostHook.ElectronHostHook can't break src.ElectronNET_Host.ElectronHostHook.connector.
Position
Below the diagonal: src.ElectronNET_Samples_ElectronHostHook.ElectronHostHook uses a module listed above it, which is the healthy direction.
src.ElectronNET_WebApp.ElectronHostHook uses src.ElectronNET_Host.ElectronHostHook.connector, so a change to src.ElectronNET_Host.ElectronHostHook.connector can break src.ElectronNET_WebApp.ElectronHostHook, while a change to src.ElectronNET_WebApp.ElectronHostHook can't break src.ElectronNET_Host.ElectronHostHook.connector.
Position
Below the diagonal: src.ElectronNET_WebApp.ElectronHostHook uses a module listed above it, which is the healthy direction.
ElectronNET.API.Serialization uses ElectronNET.API.Entities, so a change to ElectronNET.API.Entities can break ElectronNET.API.Serialization, while a change to ElectronNET.API.Serialization can't break ElectronNET.API.Entities.
Position
Below the diagonal: ElectronNET.API.Serialization uses a module listed above it, which is the healthy direction.
ElectronNET.API.Serialization uses ElectronNET.API, so a change to ElectronNET.API can break ElectronNET.API.Serialization, while a change to ElectronNET.API.Serialization can't break ElectronNET.API.
Position
Below the diagonal: ElectronNET.API.Serialization uses a module listed above it, which is the healthy direction.
ElectronNET.Common uses ElectronNET.Runtime.Data, so a change to ElectronNET.Runtime.Data can break ElectronNET.Common, while a change to ElectronNET.Common can't break ElectronNET.Runtime.Data.
Position
Below the diagonal: ElectronNET.Common uses a module listed above it, which is the healthy direction.
ElectronNET.Common uses ElectronNET.Runtime.Services, so a change to ElectronNET.Runtime.Services can break ElectronNET.Common, while a change to ElectronNET.Common can't break ElectronNET.Runtime.Services.
Position
Below the diagonal: ElectronNET.Common uses a module listed above it, which is the healthy direction.
ElectronNET.Runtime.Services.SocketBridge uses ElectronNET.API, so a change to ElectronNET.API can break ElectronNET.Runtime.Services.SocketBridge, while a change to ElectronNET.Runtime.Services.SocketBridge can't break ElectronNET.API.
Position
Below the diagonal: ElectronNET.Runtime.Services.SocketBridge uses a module listed above it, which is the healthy direction.
ElectronNET.Runtime.Services.SocketBridge uses ElectronNET.Runtime.Services, so a change to ElectronNET.Runtime.Services can break ElectronNET.Runtime.Services.SocketBridge, while a change to ElectronNET.Runtime.Services.SocketBridge can't break ElectronNET.Runtime.Services.
Position
Below the diagonal: ElectronNET.Runtime.Services.SocketBridge uses a module listed above it, which is the healthy direction.
ElectronNET.Runtime.Services.ElectronProcess uses ElectronNET.Runtime.Services, so a change to ElectronNET.Runtime.Services can break ElectronNET.Runtime.Services.ElectronProcess, while a change to ElectronNET.Runtime.Services.ElectronProcess can't break ElectronNET.Runtime.Services.
Position
Below the diagonal: ElectronNET.Runtime.Services.ElectronProcess uses a module listed above it, which is the healthy direction.
ElectronNET.Runtime.Services.ElectronProcess uses ElectronNET.Common, so a change to ElectronNET.Common can break ElectronNET.Runtime.Services.ElectronProcess, while a change to ElectronNET.Runtime.Services.ElectronProcess can't break ElectronNET.Common.
Position
Below the diagonal: ElectronNET.Runtime.Services.ElectronProcess uses a module listed above it, which is the healthy direction.
ElectronNET.Runtime.Controllers uses ElectronNET.API, so a change to ElectronNET.API can break ElectronNET.Runtime.Controllers, while a change to ElectronNET.Runtime.Controllers can't break ElectronNET.API.
Position
Below the diagonal: ElectronNET.Runtime.Controllers uses a module listed above it, which is the healthy direction.
ElectronNET.Runtime.Controllers uses ElectronNET.Runtime.Services, so a change to ElectronNET.Runtime.Services can break ElectronNET.Runtime.Controllers, while a change to ElectronNET.Runtime.Controllers can't break ElectronNET.Runtime.Services.
Position
Below the diagonal: ElectronNET.Runtime.Controllers uses a module listed above it, which is the healthy direction.
ElectronNET.Runtime.Controllers uses ElectronNET.Runtime.Services.SocketBridge, so a change to ElectronNET.Runtime.Services.SocketBridge can break ElectronNET.Runtime.Controllers, while a change to ElectronNET.Runtime.Controllers can't break ElectronNET.Runtime.Services.SocketBridge.
Position
Below the diagonal: ElectronNET.Runtime.Controllers uses a module listed above it, which is the healthy direction.
ElectronNET.Runtime.Controllers uses ElectronNET.Runtime.Services.ElectronProcess, so a change to ElectronNET.Runtime.Services.ElectronProcess can break ElectronNET.Runtime.Controllers, while a change to ElectronNET.Runtime.Controllers can't break ElectronNET.Runtime.Services.ElectronProcess.
Position
Below the diagonal: ElectronNET.Runtime.Controllers uses a module listed above it, which is the healthy direction.
32→34 ElectronNET.Runtime.Controllers uses ElectronNET.Runtimepart of a loop✕
Connections
1 pair of types, where a type in ElectronNET.Runtime.Controllers uses a type in ElectronNET.Runtime.
ElectronNET.Runtime.Controllers uses ElectronNET.Runtime, so a change to ElectronNET.Runtime can break ElectronNET.Runtime.Controllers, while a change to ElectronNET.Runtime.Controllers can't break ElectronNET.Runtime.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
ElectronNET.AspNet.Runtime uses ElectronNET.AspNet.Services, so a change to ElectronNET.AspNet.Services can break ElectronNET.AspNet.Runtime, while a change to ElectronNET.AspNet.Runtime can't break ElectronNET.AspNet.Services.
Position
Below the diagonal: ElectronNET.AspNet.Runtime uses a module listed above it, which is the healthy direction.
ElectronNET.AspNet.Runtime uses ElectronNET.API, so a change to ElectronNET.API can break ElectronNET.AspNet.Runtime, while a change to ElectronNET.AspNet.Runtime can't break ElectronNET.API.
Position
Below the diagonal: ElectronNET.AspNet.Runtime uses a module listed above it, which is the healthy direction.
ElectronNET.AspNet.Runtime uses ElectronNET.Runtime.Services, so a change to ElectronNET.Runtime.Services can break ElectronNET.AspNet.Runtime, while a change to ElectronNET.AspNet.Runtime can't break ElectronNET.Runtime.Services.
Position
Below the diagonal: ElectronNET.AspNet.Runtime uses a module listed above it, which is the healthy direction.
ElectronNET.AspNet.Runtime uses ElectronNET.Runtime.Services.SocketBridge, so a change to ElectronNET.Runtime.Services.SocketBridge can break ElectronNET.AspNet.Runtime, while a change to ElectronNET.AspNet.Runtime can't break ElectronNET.Runtime.Services.SocketBridge.
Position
Below the diagonal: ElectronNET.AspNet.Runtime uses a module listed above it, which is the healthy direction.
ElectronNET.AspNet.Runtime uses ElectronNET.Runtime.Services.ElectronProcess, so a change to ElectronNET.Runtime.Services.ElectronProcess can break ElectronNET.AspNet.Runtime, while a change to ElectronNET.AspNet.Runtime can't break ElectronNET.Runtime.Services.ElectronProcess.
Position
Below the diagonal: ElectronNET.AspNet.Runtime uses a module listed above it, which is the healthy direction.
ElectronNET.AspNet.Runtime uses ElectronNET.Runtime.Controllers, so a change to ElectronNET.Runtime.Controllers can break ElectronNET.AspNet.Runtime, while a change to ElectronNET.AspNet.Runtime can't break ElectronNET.Runtime.Controllers.
Position
Below the diagonal: ElectronNET.AspNet.Runtime uses a module listed above it, which is the healthy direction.
ElectronNET.Runtime uses ElectronNET.Runtime.Data, so a change to ElectronNET.Runtime.Data can break ElectronNET.Runtime, while a change to ElectronNET.Runtime can't break ElectronNET.Runtime.Data.
Position
Below the diagonal: ElectronNET.Runtime uses a module listed above it, which is the healthy direction.
ElectronNET.Runtime uses ElectronNET.Runtime.Controllers, so a change to ElectronNET.Runtime.Controllers can break ElectronNET.Runtime, while a change to ElectronNET.Runtime can't break ElectronNET.Runtime.Controllers.
Position
Below the diagonal: ElectronNET.Runtime uses a module listed above it, which is the healthy direction.
ElectronNET uses ElectronNET.Runtime.Data, so a change to ElectronNET.Runtime.Data can break ElectronNET, while a change to ElectronNET can't break ElectronNET.Runtime.Data.
Position
Below the diagonal: ElectronNET uses a module listed above it, which is the healthy direction.
ElectronNET uses ElectronNET.Runtime.Controllers, so a change to ElectronNET.Runtime.Controllers can break ElectronNET, while a change to ElectronNET can't break ElectronNET.Runtime.Controllers.
Position
Below the diagonal: ElectronNET uses a module listed above it, which is the healthy direction.
ElectronNET uses ElectronNET.Runtime, so a change to ElectronNET.Runtime can break ElectronNET, while a change to ElectronNET can't break ElectronNET.Runtime.
Position
Below the diagonal: ElectronNET uses a module listed above it, which is the healthy direction.
At a glance — Code Health · 54% · Adequate · gated by X5 ·
Findings mapped to OWASP categories; the specific CVEs/secrets are in the Security dimension cards below and findings.md (redacted only on the public version of this report).
OWASP category
Findings
Severity
A05:2025 — Injection
36
High / Critical
A03:2025 — Software Supply Chain Failures
25
High / Critical
Roadmap
Top priorities: Add a SAST step to CI running what this repository's stack ships: CodeQL's csharp pack, or a .NET security analyzer package — or `semgrep --config=auto`, which runs on any language — so a security regression fails the build instead of landing; Add tests that import the unreached modules (directly or through their public entry); Make custom controls keyboard-operable (role + tabindex + key handler), drop positive tabindex, and give anchors a real href.
Ranked by impact ÷ effort. "Helps" is the estimated gain on the 0–100 health score.
Do this
Helps
Effort
Dimension
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.
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.
Extend structured logging across the projects you operate, and give the library ones a diagnostics seam instead — an `EventSource`/`ActivitySource` the host can subscribe to, or an optional logger on your options object — rather than taking a logging dependency on your consumers' behalf.
Per-file score 0–10 — a quality signature. Of 50 files carrying findings, judged against the Production bar: 14% slop · 58% mixed · 28% near-clean.
File
Score
Band
Worst signal
REDACTED
1.0
Slop
Explicit Debt: NoWarnInCsproj
src/ElectronNET.API/Common/ProcessRunner.cs
2.2
Slop
Explicit Debt: EmptyCatchBlock
REDACTED
2.4
Slop
Dependency Vulnerabilities: High CVE: REDACTED
REDACTED
2.4
Slop
Dependency Vulnerabilities: High CVE: REDACTED
REDACTED
2.7
Slop
Static Analysis (SAST): High: REDACTED
REDACTED
3.0
Slop
Static Analysis (SAST): High: REDACTED
REDACTED
3.7
Slop
Static Analysis (SAST): High: REDACTED
REDACTED
4.4
Mixed
Static Analysis (SAST): High: REDACTED
REDACTED
4.4
Mixed
Static Analysis (SAST): High: REDACTED
src/ElectronNET.AspNet/ElectronNET.AspNet.csproj
4.8
Mixed
Explicit Debt: NoWarnInCsproj
REDACTED
5.0
Mixed
Static Analysis (SAST): High: REDACTED
nuke/ReleaseNotesParser.cs
5.6
Mixed
Explicit Debt: WriteOnlyPrivateField
REDACTED
5.7
Mixed
Static Analysis (SAST): Medium: REDACTED
REDACTED
5.8
Mixed
Static Analysis (SAST): High: REDACTED
REDACTED
5.8
Mixed
Dependency Vulnerabilities: High CVE: REDACTED
src/ElectronNET.API/API/BrowserWindow.cs
6.0
Mixed
Explicit Debt: CommentedOutCode
src/ElectronNET.API/API/ApiBase.cs
6.0
Mixed
Explicit Debt: BareSuppressMessage
nuke/_build.csproj
6.4
Mixed
Explicit Debt: NoWarnInCsproj
src/ElectronNET.API/Common/TimeSpanExtensions.cs
6.6
Mixed
Explicit Debt: BareSuppressMessage
src/ElectronNET.API/API/WebContents.cs
7.0
Mixed
God Classes: TooManyMethods: WebContents
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 — 72
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 — 207
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 — 140
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
This survey is a deep, periodic assessment — run each sprint, monthly, or quarterly, taking the time to go wider and deeper than a quick check and surfacing in one coherent report what you'd otherwise piece together from a dozen separate tools. It scores deterministically: the same commit yields the same score, every run. All 80 evaluated dimensions are computed by tools and static analysis; no language model sets or judges any of them. Overall confidence is 0.9, the weighted average across measured dimensions.
Every figure here is one of two 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. 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.
What we checked — 80 dimensions across the health lenses
Each chip is a dimension scored from real signals across architecture, testing, dependencies, security & compliance, documentation, git-history and code quality — in one coherent pass. A surface report typically covers a handful.
How to trust any code-health report — three questions
Can you open the finding? Real findings cite a repo-relative file and line you can open at the cited line — never an absolute scratch path. Here, 392 of 419 do; the remainder are repo-wide signals — a dimension-level measurement, not a single line. (Every path in this report is repo-relative by construction: paths are normalized at the producer and the report is rejected if any rooted path leaks through.)
Is there a tool behind the number? Every score below names the method that produced it: Roslyn, git or a scanner, not a narrative.
Does re-running give the same result? Run it again on the same commit and the score — and this report, byte for byte — is identical. A report whose numbers move between runs is describing the run, not the code.
This report answers yes to all three. That's the bar to hold any assessment to.
Tools & methods
The actual versions used this run (captured at analysis time) — re-run on the same commit for the identical score.
Method
Backs
Version
Evaluator
Roslyn static analysis
Complexity, cohesion, coupling, dead code, API surface, layering
What ran differently this time — a tool absent, degraded, or that fell back to an estimate. Named openly, not folded silently into the scores. A degraded run also records its exact cause in diagnostics.md.
D8 Code Coverage — not measured this run — 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. Coverage NOT MEASURED: `--collect:"XPlat Code Coverage"` names a data collector that ships in the `coverlet.collector` package, and this repository wires up none — no test project references it and no runsettings declares one. The absence of coverage here is therefore not evidence about the suite or about our analyzer environment: without a collector, `--collect` produces nothing even from a suite that builds and passes. Add a `coverlet.collector` PackageReference to the test project(s) (or commit the Cobertura/OpenCover/lcov report your CI produces) and real coverage will be measured. It is excluded from the score rather than counted as a near-zero defect. You can widen what we reach: add the `coverlet.collector` package to the test projects to enable coverage (or commit the Cobertura/OpenCover/lcov report your CI produces).
D12 Dependency Hygiene — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. `dotnet list package` did not return usable output (restore or query failed); no outdated/vulnerable/deprecated data to assess. The tool said: `dotnet list package` exited 1 with no output.
D17 Explicit Debt — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. The C# workspace loaded this repository's projects but reported a load failure, and the dead-code reference search is unreliable over a graph that did not load cleanly, so it was skipped. The other debt markers on this row were read; dead symbols were not, and their absence from the score is not a finding that the code has none. First load diagnostic: Failure: Cannot open project 'docs/Docs.shproj' because the file extension '.shproj' is not associated with a language.
D18 Solution Shape — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. `dotnet build` reported 5 error(s), and the diagnostics it printed were: MSB3073: The command "npm install" exited with code 1.; MSB3030: Could not copy the file "src/ElectronNET.Host/**/*.json" because it was not found.; MSB3030: Could not copy the file "src/ElectronNET.Host/**/*.html" because it was not found.; MSB3030: Could not copy the file "src/ElectronNET.Host/**/*.js" because it was 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.
D19 Documentation Quality — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. This kind did not reach the 95 % precision gate in three adjudicated runs (docs/plans/deterministic-engine/adjudication/D19-sample3-v3.md), so by the pre-registered fallback it publishes no row until a re-measurement shows it does. The candidates are counted here, not reported as findings, and the score does not include them.
D21 Naming Consistency — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. D21's deterministic naming rules are gated on C# first (docs/plans/deterministic-engine.md, P5): each other language is switched on only after its own concept suite and A/B gate pass. Until then its declarations carry no naming verdict this run — this says nothing about whether its names are consistent.
D21 Naming Consistency — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. PREREGISTRATION version 20's fallback (adjudication D21-sample3-v3): this rule kind was adjudicated below the 95 % precision gate, so its candidates are counted here and not published, and the score covers only the acronym-spelling and awaitable-suffix rules. The kind returns as rows only after it shows a measured precision; this says nothing about whether these names are consistent.
D21 Naming Consistency — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. PREREGISTRATION version 20's fallback (adjudication D21-sample3-v3): this rule kind was adjudicated below the 95 % precision gate, so its candidates are counted here and not published, and the score covers only the acronym-spelling and awaitable-suffix rules. The kind returns as rows only after it shows a measured precision; this says nothing about whether these names are consistent.
D22 Internal API Consistency — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. D22's deterministic call-shape rules are gated on C# first (docs/plans/deterministic-engine.md, P5): each other language is switched on only after its own concept suite and A/B gate pass. This says nothing about whether that surface is consistent.
D24 Comment Value — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. Each source language's comment syntax, and the code a comment annotates in it, needs its own proof before D24 judges it. Until then those comments are left unread, not counted as clean.
D28 Secrets (history) — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. D28's config-credential rule (WD-SECRET-0002) parses each committed `.json` config as a document and reads credential-named values; `src/testEnvironments.json`, `src/ElectronNET.WebApp/appsettings.Development.json`, `src/ElectronNET.WebApp/appsettings.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.
AXB2 Runtime readiness — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. `npm run` found no package.json in the folder where our sandbox ran it. This is a limit of our sandbox, not of your repository. (rule: no-root-manifest). The renderer reported: the dev server (`npm run start`) exited before it served a page. Likely cause (our sandbox): `npm run` found no package.json in the folder where our sandbox ran it. This is a limit of our sandbox, not of your repository. Last output: "npm error code ENOENT / npm error syscall open / npm error path <repo>/package.json / npm error errno -2 / npm error enoent Could not read package.json: Error: ENOENT: no such file or directory, open '<repo>/package.json' / npm error enoent This is related to npm not being able to find a file. / npm error enoent / npm error A complete log of this run can be found in: <path>" No runtime evidence was gathered.
AXR1 Runtime accessibility — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Render strategy: boot via DevServer (start). the dev server (`npm run start`) exited before it served a page. Likely cause (our sandbox): `npm run` found no package.json in the folder where our sandbox ran it. This is a limit of our sandbox, not of your repository. Last output: "npm error code ENOENT / npm error syscall open / npm error path <repo>/package.json / npm error errno -2 / npm error enoent Could not read package.json: Error: ENOENT: no such file or directory, open '<repo>/package.json' / npm error enoent This is related to npm not being able to find a file. / npm error enoent / npm error A complete log of this run can be found in: <path>" No runtime evidence was gathered.
M4 Documentation accuracy — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. M4 checks only the claim kinds adjudicated at or above 95 % precision: links and versions (PREREGISTRATION version 9), and artefact counts an order of magnitude off. Paths, command arguments, installs, environment variables, settings, projects, packages, routes, cd targets, infrastructure products and removed modules are read but not checked, and none of them is reported or counted.
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.
Repo exclusion declarations (.gitattributes linguist-generated/vendored, .editorconfig generated_code): none declared — every source file was scored.
Limitations & what we did not check
We assess the repository exactly as committed, and only the repository. By design we do not reach outside the source tree: the live cloud account, the running CI/CD pipeline, the host's branch-protection and approval rules, the production configuration, or a restore actually exercised against a backup are all out of scope. That boundary is a feature, not a gap — a repo-relative, deterministic scan re-runs identically on any commit and every finding opens at a real file and line, where a live audit can neither be reproduced nor traced. The visible consequence is that controls which leave no in-repo evidence are reported as "not evidenced" and excluded from the score rather than awarded a number a static scan cannot justify.
Per-dimension blind spots
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.
D10 Test Quality: Assertion density is structural — it cannot tell a meaningful behavioural assertion from a trivial one, only that an assertion is present.
D13 Secret Scanning: Secret detection is signature- and entropy-based on the current tree — a secret that does not match a known pattern, or one already rotated, will not be flagged (a clean scan is "nothing matched", not "no secrets exist").
D14 License Compliance: License compatibility is checked against declared package metadata and a policy — mislabelled or missing license metadata, and obligations that depend on how you distribute, are not resolved here.
D15 Churn × Complexity Hotspots: Churn hotspots come from git history — a freshly imported or squashed repository has no churn signal, and recent rewrites can mask a historically risky file.
D16 Bus Factor: Bus-factor is a time-decayed model of commit attribution (who has recently, repeatedly worked a file), not comprehension — pairing, review and reading-without-committing spread knowledge it can't see; bot commits and shared accounts still distort it.
D17 Explicit Debt: Acknowledged-debt signals (TODO/FIXME, suppressions, dead code) are textual — undocumented debt that nobody marked, and debt that lives in design rather than annotations, is invisible. Committed machine-written code (scaffolded migrations, designer/codegen output, generated stubs) is excluded — it is never the team's dead code to delete.
D18 Solution Shape: Build integrity reflects whether the solution compiled in this environment — a build that needs a private feed, a specific SDK, or a generated file absent from the repo can read as broken when it is merely unreproducible here.
D19 Documentation Quality: Documentation quality publishes two things only: a runnable or packaged unit with no example, and a multi-project root README that maps none of its parts. It does not judge clarity, and its other checks (overview, licence, boilerplate, structure, empty sections, XML-doc coverage) are withheld after adjudication: their candidates are counted in the card's gaps, not shown as rows. A false statement in a document is M4's; units are .NET projects only.
D20 ADR Quality: ADR quality checks the structure of the decision records present: it cannot know about decisions made and never recorded, and it does not judge how well a record argues its case. Records in a language the section lexicon does not cover are not evaluated.
D24 Comment Value: Comment value is measured as redundancy only: a comment that repeats its code's words is found, but a paraphrase in other words, a vague comment, or one the code contradicts is not, and whether a comment is valuable is not claimed. Comments in other scripts or languages, and outside C#, are not judged.
D26 Project Cohesion: Project focus is sized from members/namespaces per project — a project that is broad by deliberate design reads the same as one that has sprawled.
D27 Navigability: Indirection/navigability is structural — it measures hops to follow a call, not whether that indirection buys real flexibility or just ceremony.
D28 Secrets (history): Secret-history scanning sweeps the git log for known patterns — a secret that predates the available history, or never matched a signature, is not found (clean means "nothing matched in the history we can see").
D29 Static Analysis (SAST): SAST findings are pattern-based (semgrep) — it finds classes of bug it has rules for; logic flaws, auth/authorization gaps and issues needing runtime context are out of reach (and clean means "no rule matched").
D30 Dependency Vulnerabilities: CVE matching depends on accurate package/version metadata and on the advisory databases — a vulnerability with no published advisory, or in code not declared as a dependency, is not seen. Coverage needs a RESOLVED graph: an unpinned requirements.txt, or a pom without a resolved build, yields partial coverage rather than a clean verdict. An ecosystem the analyzer cannot scan is reported as unmeasured, never as clean.
D34 Knowledge Freshness: Freshness is decayed commit RECENCY, not comprehension — code read often but rarely committed reads as orphaned, and stable code that genuinely needs no changes is penalised the same as forgotten code; bot/squash commits distort it like the bus factor.
D35 Change Coupling: Change coupling is co-change in COMMITS — files split across separate commits, or coupled only through a shared config/build step, read as uncoupled, and a sweeping commit (rename/format) is excluded so it doesn't couple everything. It shows that files change together, not WHY: a high coupling can be a healthy cohesive pair as readily as a hidden leak.
D43 Malicious Dependencies: Only packages some vulnerability database has already NAMED as malicious are seen — a compromise published in the last hours, or never reported at all, is invisible here, and this dimension reading 10 is not evidence that a dependency is trustworthy. There is no typosquat or dependency-confusion analysis: a package nobody has reported is simply absent from the feeds. Coverage is the dependency scan's: an ecosystem that could not be scanned is disclosed as unmeasured, never as clean.
D44 Platform End-of-Life: The support table is FROZEN, so it goes out of date by losing RECALL: a release that ended support after the table was written is missed until the table is refreshed, and this dimension reading 10 is not evidence that a platform is current. Only platforms the repository DECLARES in a place this pass reads are seen — a runtime named only in a Dockerfile (D31's subject), in a CI workflow (D29's), or in a file this pass does not parse (go.mod, a Gemfile ruby directive) is invisible here, which is why a repository declaring none of them abstains rather than scoring. Only frameworks with a PUBLISHED support policy are tracked: React, Flask and Express publish none, so their age cannot be judged and their absence from a report is not a statement that they are supported.
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.
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: Documentation accuracy checks links, versions and artefact counts against the tree: other claims (paths, commands, settings, routes) are read but not checked, and it cannot run the onboarding or measure how long a real new joiner takes.
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.
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.
Bring the 5 bodies over 15 down to 15 or less in Cyclomatic Complexity — start with main.startSocketApiBridge (cyclomatic 36), tray.default (cyclomatic 25), browserWindows.default::createWindow (cyclomatic 24). — 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 5 together lifts Cyclomatic Complexity from 8.6 to about 10.0/10, projected with the scoring formula itself and assuming each lands exactly at 15.
Detailed fixes: d1_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: How hard the code is for a person to follow, beyond raw branching.
Method: Cognitive complexity per method (Sonar-style nesting-penalized score), computed exhaustively over production code, excluding test projects. Deterministic.
+ 4 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Bring the 9 bodies over 15 down to 15 or less in Cognitive Complexity — start with main.startSocketApiBridge (cognitive 34), JsonToBoxedPrimitivesConverter.ReadValue (cognitive 31), tray.default (cognitive 28). — 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 9 together lifts Cognitive Complexity from 8.3 to about 10.0/10, projected with the scoring formula itself and assuming each lands exactly at 15.
Detailed fixes: d2_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D3 · God Classes8.7 / 10Strong✓ Tool-verified
What it measures: Over-large classes that try to do too much ("god classes").
Method: God-class detection by line and method-count thresholds per logical type (partial classes unified), filtered for generated code and registration/contract false positives. Deterministic.
Resolve the 3 TooManyMethods finding(s) in God Classes — start with BrowserWindow.cs, App.cs, WebContents.cs. — One of this dimension's main actionable groups (3 warning-level).
Resolve the 1 FunctionTooLong finding(s) in God Classes — start with autoUpdater.ts. — One of this dimension's main actionable groups (1 warning-level).
Resolve the 1 FileTooLong finding(s) in God Classes — start with browserWindows.ts. — One of this dimension's main actionable groups (1 warning-level).
Detailed fixes: d3_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Copy-pasted code that should be shared instead.
Method: Code duplication via token-stream sliding windows with type-aware normalization (locals masked, type names preserved), density-scored per KLoC of production code. Deterministic.
8 duplicated block group(s) detected. A further 49 rows report members as variants of one another; they aggregate block groups already counted above and are not themselves counted.
Edited copy of a member (9 corresponding lines) · ×4src/ElectronNET.API/API/Cookies.cs:75
Edited copy of a member (12 corresponding lines) · ×2src/ElectronNET.API/API/IpcMain.cs:115
Edited copy of a member (14 corresponding lines) · ×2src/ElectronNET.API/Runtime/Controllers/RuntimeControllerDotNetFirst.cs:84
Edited copy of a member (28 corresponding lines)REDACTED:360
Edited copy of a member (19 corresponding lines)src/ElectronNET.API/API/ApiBase.cs:147
+ 15 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Resolve the 4 Edited copy of a member (9 corresponding lines) finding(s) in Code Duplication — start with Session.cs (2), Cookies.cs, IpcMain.cs. — One of this dimension's main actionable groups (4 warning-level).
Resolve the 2 Edited copy of a member (12 corresponding lines) finding(s) in Code Duplication — start with IpcMain.cs, BrowserWindow.cs. — One of this dimension's main actionable groups (2 warning-level).
Resolve the 2 Edited copy of a member (14 corresponding lines) finding(s) in Code Duplication — start with RuntimeControllerDotNetFirst.cs, Program.cs. — One of this dimension's main actionable groups (2 warning-level).
Detailed fixes: d4_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D5 · Coupling9.6 / 10Stronggated by 1 serious finding✓ Tool-verified
What it measures: Whether volatile projects sit underneath others that depend on them (so their churn ripples upward), and whether project dependencies form cycles. A widely-depended-on but stable shared/kernel project is healthy, not penalised.
Method: Dependency cycles via elementary-DFS over real .csproj references, plus Martin instability (afferent/efferent) per project. Exhaustive over the reference graph, deterministic.
Coverage: Exhaustive · type-level: afferent/efferent coupling + cycles computed over every production type — the population is all types, not a name convention.
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.
D10 · Test Quality10.0 / 10Exemplary✓ Tool-verified
What it measures: Whether the tests truly assert behaviour rather than just running the code.
Method: Per-test assertions, skips, and mock references analyzed via Roslyn; structured skip-reason tags (BUG:/ENV:) separate documented deferrals from debt. Deterministic.
What it measures: Whether any secrets (keys, tokens, passwords) have leaked into the code.
Method: In-process native secret scanner (entropy plus signature patterns) across all tracked files; no external tool. A clean result is a measured 10, not no-data zero. Deterministic.
What it measures: Whether the licenses of third-party packages are compatible with your policy.
Method: Third-party package licenses resolved from declared package metadata and checked against the configured policy (allow/deny/copyleft). Deterministic; clean = no incompatible license found at metadata depth.
0 of 209 packages use a banned license. ★ DEPTH: this repository's MSBuild projects declare 17 direct `PackageReference`(s), and 183 further package(s) were reached beyond them by closing the graph over nuget.org's own nuspec dependency graph — so a banned licence pulled in only by a dependency's OWN dependencies is inside this verdict. A package whose licence nuget.org could not be asked for is not graded, and version ranges are taken at their lower bound, so this is the closure as that graph states it rather than a restored consumer's exact resolution.
What it measures: Files that change often and are also complex — the riskiest hotspots.
Method: Per production file churn times cyclomatic complexity over a rolling window, computed from git and Roslyn/JS/Razor analysis. Exhaustive, deterministic per commit date.
Resolve the 2 Hotspot finding(s) in Churn × Complexity Hotspots — start with browserWindows.ts, webContents.ts. — One of this dimension's main actionable groups (2 warning-level).
Detailed fixes: d15_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D16 · Bus Factor9.5 / 10Exemplary✓ Tool-verified
What it measures: Whether knowledge is concentrated in too few people (the "bus factor").
Method: Living knowledge per author via time-decayed commit attribution (6-month half-life, focus weighting) across largest source files. Deterministic, avoids blame's mechanical-refactor false positives.
4 source file(s) have their living knowledge concentrated in one author (≥90% of recent, decayed contribution). The largest is src/ElectronNET.API/API/Menu.cs. Counted over 72 of the 227 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.
Off-boarding risk: anonymized user #1
Further sole-owners (lower concentration)
✓ On the Gold path — maintain.
Detailed fixes: d16_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Acknowledged debt left in the code — TODOs, dead code, suppressed warnings.
Method: Roslyn syntactic debt markers (suppressions/TODO/FIXME/HACK/empty-catch/commented-code/Obsolete) plus SymbolFinder dead-code analysis; weighted-debt-per-KLoC density deducted 2.0x per unit. Deterministic, exhaustive.
31 deducted debt markers + unmeasured dead symbols across 17919 LoC in the .NET projects (1.1/KLoC) → score 7.8. Dead code not measured: the solution did not load cleanly, so the reference search was skipped.
+ 2 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Resolve the 13 NoWarnInCsproj finding(s) in Explicit Debt — start with REDACTED (5), ElectronNET.AspNet.csproj (5), _build.csproj (2). — One of this dimension's main actionable groups (13 issue-level).
Resolve the 4 EmptyCatchBlock finding(s) in Explicit Debt — start with ProcessRunner.cs (4). — One of this dimension's main actionable groups (4 issue-level).
Resolve the 1 WriteOnlyPrivateField finding(s) in Explicit Debt — start with ReleaseNotesParser.cs. — One of this dimension's main actionable groups (1 issue-level).
Detailed fixes: d17_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether the solution is laid out in a sensible, conventional structure.
Method: Solution structure: project count, decomposition, shell-project detection, build success (confirmed failures cap the score); traced to actual .sln files and binaries. Deterministic.
18 projects, 650 source files, 20216 hand-written lines of code (17919 production / 2297 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), 15 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 2 solutions loaded as one workspace: `src/ElectronNET.sln`, `src/ElectronNET.Samples.AuthMiddleware/ElectronNET.Samples.AuthMiddleware.sln`.
What it measures: Whether the project's documentation is clear, complete, and useful.
Method: Every README, docs/ document and root guide parsed by its markup and measured in Unicode letters. Published: a runnable or packaged .NET project whose README (or a document it links, or a root guide) shows no example, and a root README naming none of three or more projects. Overview, licence, boilerplate, wall-of-text, empty-section and XML-doc rows are measured and withheld (counted in gaps) after adjudication. Deterministic, exhaustive, advisory.
2 of 2 documentation facets pass in full. 35 document(s) read across 15 unit(s).
✓ On the Gold path — maintain.
Detailed fixes: d19_recommendation.md.
Do you agree with this assessment?
D20 · ADR Quality0.0 / 10Critical✓ Tool-verified
What it measures: Whether architecture decisions are recorded well (context, decision, consequences).
Method: Every ADR read by its section structure: nine located rules (a missing Decision, Context or Consequences section, a stale status, two records deciding the same question, a dangling supersede link, a number-only title, a single option, no named cost, no status where the log uses one, no enforcement field where the log adopted one), each a fixed deduction from 10; the score is the mean over evaluated records. Deterministic, no model. Advisory.
What it measures: Whether comments are worth it — explaining WHY (valuable) rather than WHAT (redundant).
Method: Every inline C# comment compared word by word with the identifiers, literals and constructs of the code it annotates (taken from the syntax); a comment whose words that code already contains is redundant, as are closing-brace labels and generator template text. Comments giving a reason or a reference are kept; other scripts and languages are not judged. Deterministic, exhaustive, advisory.
1 of 12 projects flagged as possibly oversized/incoherent.
Projects may be oversized for their cohesionREDACTED:1
What to do
Resolve the 1 Projects may be oversized for their cohesion finding(s) in Project Cohesion — start with REDACTED. — 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.
Do you agree with this assessment?
D27 · Navigability7.0 / 10Adequate✓ 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.
50 % of calls cross a namespace and 28 % go through an interface, but 95 % of collaborators are co-located — so following a call takes several hops. Baseline: medium — clean/modular boundaries expected.
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.
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).
36 finding(s): 0 critical, 33 high, 3 medium, 0 low. 19 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 2 file(s) — `src/ElectronNET.IntegrationTests/Tests/ElectronCleanTargetsTests.cs` (line 77), `src/ElectronNET.IntegrationTests/Tests/ElectronIconTargetsTests.cs` (line 88) — so no absence of findings in the named regions is evidence of anything; rows reported elsewhere in those files are real. Fix the syntax error (or exclude the file deliberately) and re-scan to cover them. Separately, one or more rules could not re-parse an embedded snippet in 3 file(s) (e.g. a workflow `run:` block read as shell). Those files WERE scanned and their other rows are unaffected; only those rules' view of those snippets is missing.
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
+ 6 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Resolve the 4 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (3), REDACTED. — One of this dimension's main actionable groups (4 issue-level).
Resolve the 4 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (2), REDACTED, REDACTED. — One of this dimension's main actionable groups (4 issue-level).
No action in Static Analysis (SAST) — all 19 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 (19 issue-level, 0 of them charged here).
Detailed fixes: d29_recommendation.md · top locations in Appendix A, every location in findings.md.
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 osv.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. Advisory since rubric-2026.11.2 (CAI decision 0006): every row is a match against a vulnerability database that changes daily, so the reading is shown and never moves a scored dimension, lens or the headline.
Resolve the 14 High CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (14). — One of this dimension's main actionable groups (14 issue-level).
Resolve the 2 Medium CVE finding(s) in Dependency Vulnerabilities — start with REDACTED, REDACTED. — One of this dimension's main actionable groups (2 warning-level).
Resolve the 1 Medium vulnerability finding(s) in Dependency Vulnerabilities — start with REDACTED. — One of this dimension's main actionable groups (1 warning-level).
Detailed fixes: d30_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether anyone still has living knowledge of each file, or it has been orphaned — last understood long ago by someone now gone quiet. The sibling of the bus factor: D16 asks who owns it, D34 asks whether anyone still knows it.
Method: File orphaning as total living-knowledge decay below one focused-commit's worth within a year, computed per-file from the D16 decay model. Exhaustive, deterministic over fixed history.
52 of 72 significant source file(s) are orphaned — their living knowledge has decayed to nothing, so no one currently understands them. The largest is src/ElectronNET.API/API/App.cs. Counted over 72 of the 227 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.
Most significant orphaned filesrc/ElectronNET.API/API/App.cs:1
What to do
Resolve the 51 Orphaned file finding(s) in Knowledge Freshness — start with Session.cs, REDACTED, ApiBase.cs. — One of this dimension's main actionable groups (51 recommendation-level).
Resolve the 1 Concentrated knowledge decay finding(s) in Knowledge Freshness. — One of this dimension's main actionable groups (1 recommendation-level).
Resolve the 1 Most significant orphaned file finding(s) in Knowledge Freshness — start with App.cs. — 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.
What it measures: Whether files that change together actually belong together — pairs that repeatedly co-change in git history despite having no explicit code dependency, surfacing the hidden/logical coupling (and boundaries in the wrong place) a static scan can't see.
Method: Pairwise co-occurrence over the per-commit file sets in git history (production source only — tests and generated dropped): Degree-of-Coupling = shared ÷ min individual revisions, reported above noise floors (each file ≥10 revisions, ≥5 shared commits, ≥50% strength); sweeping commits excluded. Deterministic over fixed history.
Coverage: Population: PRODUCTION source files only — test and generated files are dropped before pairing, so a class co-changing with its own test (trivially ~100%) can't drown the real production↔production coupling. Pairs ranked by Degree-of-Coupling. A non-source file is never a coupling PARTICIPANT either: documentation, schemas, config and data files are dropped with the rest, so a code↔docs pair — a command and the reference page that restates it — is not reported however strongly the two co-change; nor is coupling that runs THROUGH a build step or config file.
Resolve the 4 Change coupling finding(s) in Change Coupling — start with WindowManager.cs (2), WebContents.cs, ElectronProcessActive.cs. — One of this dimension's main actionable groups (4 warning-level).
Detailed fixes: d35_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether the build pipeline provides supply-chain integrity — generated provenance/attestation, signed artifacts (cosign/sigstore), an SBOM, and pinned build actions. Presence of the configuration, not a runtime guarantee.
Method: Supply-chain provenance/signing read deterministically from CI/build config (.github/workflows, .gitlab-ci.yml, azure-pipelines, Jenkinsfile, .circleci) + the release surface: four signals — generated provenance/attestation (SLSA/in-toto/actions-attest), artifact signing (cosign/sigstore/gitsign), an SBOM (syft/sbom-action/*.spdx.json/*.cdx.json), and SHA-pinned build actions — scored 10·present/denom. NotApplicable without a build pipeline. Detects configuration presence, not runtime enforcement.
+ 3 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 warning-level).
Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing — start with REDACTED. — One of this dimension's main actionable groups (1 warning-level).
Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing — start with REDACTED. — One of this dimension's main actionable groups (1 warning-level).
Detailed fixes: d36_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether 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. Reported 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. Advisory since rubric-2026.11.2 (CAI decision 0006): the malicious-package feed is a database that changes daily, so the reading is shown and never moves a scored dimension, lens or the headline.
What it measures: Whether anyone still ships security patches for the platform this repository RUNS ON — the runtime it pins and the framework majors its own constraints hold it to. Separate from D12 because the question differs: a current Django on an end-of-life Python is perfectly up to date and completely unsupported, and the fix is a migration rather than a version bump. What the repository says it merely SUPPORTS is never charged.
Method: End-of-life PLATFORM read from the repository's own declarations and graded against a FROZEN, dated table of vendor support dates — no network, no feed, no API, so this dimension answers identically inside a closed scan fence. Two subjects: a RUNTIME the project pins (a single or all-end-of-life TargetFramework, a .nvmrc or .python-version, a requires-python CAP) and a FRAMEWORK major a dependency constraint cannot move off (a caret, tilde or exact version; `vue@^2.7.16` pins Vue 2). A FLOOR is deliberately never charged — `requires-python = ">=3.8"` states what a package SUPPORTS, not what it runs on — and a multi-target project is charged only when EVERY target is out of support. Runtime 4.0/product capped 8.0, framework 1.5 capped 4.5. The table is safe to freeze because a statement about support that ended in the past cannot become false: it loses recall as it ages, never precision, and a test asserts every entry predates the freeze date. Disjoint from D31 (a container image's OS layer) and D29 (the toolchain a CI workflow installs). Abstains when the repository declares no platform this pass reads — never scores it clean.
0 end-of-life runtime(s) and 0 end-of-life framework(s), read from 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.
Do you agree with this assessment?
Frontend & cross-cutting dimensions
R = React/JS · M = Maturity · P = Readiness.
AC1 · Text alternatives10.0 / 10Exemplary○ Nothing flagged
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.
Do you agree with this assessment?
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.
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.
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/ElectronNET.Samples.AuthMiddleware/Components/Pages/NotFound.razor:4
No <main> (or role="main") means no "skip to content" target and a weaker landmark map. Wrap the primary content in <main>. — src/ElectronNET.Samples.ElectronHostHook/Views/Home/Index.cshtml:7
A page with no <title> gives no name in the tab, history or screen-reader page list. Add a descriptive <title> in <head>. — src/ElectronNET.WebApp/Views/Home/Index.cshtml:2
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.
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".
The repo's own CSS styles .dismiss with `cursor: pointer`, so this <span> is a control — but it has no role, no tabindex="0" and no key handler, so it can only be reached with a mouse. Use a <button>, or add role + tabindex="0" + a key handler. — src/ElectronNET.Samples.AuthMiddleware/Components/Layout/MainLayout.razor:22
A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabindex="0" + a key handler. — src/ElectronNET.Samples.AuthMiddleware/Components/Layout/NavMenu.razor:9
What to do
Make custom controls keyboard-operable (role + tabindex + key handler), drop positive tabindex, and give anchors a real href.
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.
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.
`body` sets color: #fff on background-color: #8aba87 — 2.2:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them. (×3) — src/ElectronNET.WebApp/Views/CrashHang/ProcessCrash.cshtml:2, src/ElectronNET.WebApp/Views/CrashHang/ProcessHang.cshtml:2, src/ElectronNET.WebApp/Views/Windows/DemoWindow.cshtml:2
`#components-reconnect-modal button` sets color: white on background-color: #6b9ed2 — 2.8:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them. — src/ElectronNET.Samples.AuthMiddleware/Components/Layout/ReconnectModal.razor.css:91
`a.list-group-item-success:focus, a.list-group-item-success:hover, button.list-group-item-success:focus, button.list-group-item-success:hover` sets color: #3c763d on background-color: #d0e9c6 — 4.2:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them. — docs/md-styles.css:5617
`a.list-group-item-info:focus, a.list-group-item-info:hover, button.list-group-item-info:focus, button.list-group-item-info:hover` sets color: #31708f on background-color: #c4e3f3 — 4.1:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them. — docs/md-styles.css:5641
`a.list-group-item-warning:focus, a.list-group-item-warning:hover, button.list-group-item-warning:focus, button.list-group-item-warning:hover` sets color: #8a6d3b on background-color: #faf2cc — 4.3:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them. — docs/md-styles.css:5665
`a.list-group-item-danger:focus, a.list-group-item-danger:hover, button.list-group-item-danger:focus, button.list-group-item-danger:hover` sets color: #a94442 on background-color: #ebcccc — 3.9:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them. — docs/md-styles.css:5689
`.alert-info > h5` sets color: #1976d2 on background-color: #e3f2fd — 4.0:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them. — docs/md-styles.css:7369
`.alert-warning > h5` sets color: #f57f17 on background-color: #fff3e0 — 2.4:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them. — docs/md-styles.css:7375
`.alert-danger > h5` sets color: #d32f2f on background-color: #ffebee — 4.4:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them. — docs/md-styles.css:7381
`.demo-toggle-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/ElectronNET.WebApp/wwwroot/assets/css/demo.css:39
`a` 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/ElectronNET.WebApp/wwwroot/assets/css/nativize.css:41
`.nav-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/ElectronNET.WebApp/wwwroot/assets/css/nav.css:79
`.nav-footer a` 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/ElectronNET.WebApp/wwwroot/assets/css/nav.css:116
`.nav-footer-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/ElectronNET.WebApp/wwwroot/assets/css/nav.css:132
`.dropdown-toggle: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. — docs/md-styles.css:3719
`.dropdown-menu > .active > a` 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. — docs/md-styles.css:3775
`.open > a` 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. — docs/md-styles.css:3794
`.btn-group.open .dropdown-toggle` 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. — docs/md-styles.css:3910
`.navbar-toggle: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. — docs/md-styles.css:4524
`.modal` 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. — docs/md-styles.css:6106
`.modal-content` 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. — docs/md-styles.css:6146
`.carousel-control: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. — docs/md-styles.css:6628
`.about` moves (`transition: visibility 0s .12s linear , opacity .12s ease-in, transform .12s ease-in`) 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/ElectronNET.WebApp/wwwroot/assets/css/about.css:21
`.about.is-shown` moves (`transition: visibility 0s 0s linear , opacity .24s ease-out, transform .24s ease-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/ElectronNET.WebApp/wwwroot/assets/css/about.css:28
`.demo-toggle-button:before` moves (`transition: transform .2s cubic-bezier(.4,.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/ElectronNET.WebApp/wwwroot/assets/css/demo.css:50
`.is-open .demo-box` moves (`animation: demo-box-fade-in .2s cubic-bezier(0, .20, .20, .96)`) 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/ElectronNET.WebApp/wwwroot/assets/css/demo.css:112
`.section` moves (`transition: visibility 0s .12s linear , opacity .12s ease-in, transform .12s ease-in`) 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/ElectronNET.WebApp/wwwroot/assets/css/section.css:18
`.section.is-shown` moves (`transition: visibility 0s 0s linear , opacity .36s ease-out, transform .36s ease-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/ElectronNET.WebApp/wwwroot/assets/css/section.css:25
`#components-reconnect-modal[open]` moves (`animation: components-reconnect-modal-slideUp 1.5s cubic-bezier(.05, .89, .25, 1.02) 0.3s, components-reconnect-modal-fadeInOpacity 0.5s ease-in-out 0.3s`) 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/ElectronNET.Samples.AuthMiddleware/Components/Layout/ReconnectModal.razor.css:37
`.components-rejoining-animation div` moves (`animation: components-rejoining-animation 1.5s cubic-bezier(0, 0.2, 0.8, 1) 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/ElectronNET.Samples.AuthMiddleware/Components/Layout/ReconnectModal.razor.css:118
`.collapsing` moves (`transition-property: height,visibility`) 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. — docs/md-styles.css:3694
`.progress-bar` moves (`transition: width .6s`) 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. — docs/md-styles.css:5418
`.progress-bar.active` moves (`animation: 2s linear infinite progress-bar-stripes`) 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. — docs/md-styles.css:5432
`.modal.fade .modal-dialog` moves (`transition: transform .3s ease-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. — docs/md-styles.css:6116
`.modal.fade .modal-dialog` moves (`transition: transform .3s ease-out,-webkit-transform .3s ease-out,-o-transform .3s ease-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. — docs/md-styles.css:6117
`.carousel-inner > .item` moves (`transition: left .6s 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. — docs/md-styles.css:6521
`.carousel-inner > .item` moves (`transition: transform .6s 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. — docs/md-styles.css:6532
`.carousel-inner > .item` moves (`transition: transform .6s ease-in-out,-webkit-transform .6s ease-in-out,-o-transform .6s 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. — docs/md-styles.css:6533
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.
Other · Architecture — Whether any singleton service captures a scoped/transient dependency — a silent lifetime/threading bug.
Method: Roslyn scan: DI registrations parsed from AddSingleton/Scoped/Transient; each singleton checked for captured shorter-lifetime dependencies. Exhaustive, deterministic.
Other · Architecture — How the codebase splits by code ROLE — domain, application, infrastructure, test, generated. The significance map behind the knowledge/coupling weighting, and a DDD signal in its own right: a thin domain core under fat infrastructure is the anemic-domain smell, quantified. How each file's role is decided, because the split is only as good as that: a generated name or a build-output tree makes it Generated, a test project makes it Test, and otherwise the file's NAMESPACE and PATH words are matched against fixed vocabularies in a fixed ORDER — domain, then infrastructure, then application — so a file whose words hit two layers is counted under the earlier one. A production file matching none of them counts as application, so that share reads 'application or unclassified' rather than a measured application layer. Roles come from naming convention, never from what the code does.
Method: Roslyn line-count by code ROLE: every source file classified Domain/Application/Infrastructure/Test/Generated by namespace + path convention (the shared CodeRoleClassifier), then significant lines summed per role. Deterministic; the advisory score is the business-logic (domain+application) share of production code.
Coverage: Population: ALL source files, each bucketed into ONE of five roles (Domain/Application/Infrastructure/Test/Generated) by namespace + path convention — a file whose layer isn't named in the convention falls to Application (the neutral default), and the split is line-count, not semantic depth or business value.
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.
`Dock` is a singleton (one shared instance) but mutates instance state outside any lock (_items; e.g. `_items` at line 174). — src/ElectronNET.API/API/Dock.cs:13
`GlobalShortcut` is a singleton (one shared instance) but mutates instance state outside any lock (_shortcuts; e.g. `_shortcuts` at line 53). — src/ElectronNET.API/API/GlobalShortcut.cs:11
`Tray` is a singleton (one shared instance) but mutates instance state outside any lock (_items; e.g. `_items` at line 220). — src/ElectronNET.API/API/Tray.cs:18
`Menu` is a singleton (one shared instance) but mutates instance state outside any lock (_menuItems, _contextMenuItems, ContextMenuItems; e.g. `_menuItems` at line 64). — src/ElectronNET.API/API/Menu.cs:14
`WindowManager` is a singleton (one shared instance) but mutates instance state outside any lock (_isQuitOnWindowAllClosed, _browserWindows, _browserViews; e.g. `_isQuitOnWindowAllClosed` at line 56). — src/ElectronNET.API/API/WindowManager.cs:15
`App` is a singleton (one shared instance) but mutates instance state outside any lock (_preventQuit, _isReady; e.g. `_preventQuit` at line 81). — src/ElectronNET.API/API/App.cs:17
`RuntimeControllerAspNetElectronFirst` is a singleton (one shared instance) but mutates instance state outside any lock (electronProcess; e.g. `electronProcess` at line 32). — src/ElectronNET.AspNet/Runtime/Controllers/RuntimeControllerAspNetElectronFirst.cs:10
`RuntimeControllerAspNetDotnetFirst` is a singleton (one shared instance) but mutates instance state outside any lock (electronProcess; e.g. `electronProcess` at line 30). — src/ElectronNET.AspNet/Runtime/Controllers/RuntimeControllerAspNetDotnetFirst.cs:13
`ElectronProcessPassive` is not registered, but the singleton `RuntimeControllerAspNetElectronFirst` creates it and keeps it in `electronProcess`, so one instance outlives every request and is shared by every caller that reaches it — and it mutates instance state outside any lock (process; e.g. `process` at line 27). — src/ElectronNET.API/Runtime/Services/ElectronProcess/ElectronProcessPassive.cs:12
`ElectronProcessActive` is not registered, but the singleton `RuntimeControllerAspNetDotnetFirst` creates it and keeps it in `electronProcess`, so one instance outlives every request and is shared by every caller that reaches it — and it mutates instance state outside any lock (process; e.g. `process` at line 212). — src/ElectronNET.API/Runtime/Services/ElectronProcess/ElectronProcessActive.cs:19
`App` keeps one instance of itself in the static `_app`, so that one instance serves the whole process and is shared by every thread that reaches it — and it mutates instance state outside any lock (_preventQuit, _isReady; e.g. `_preventQuit` at line 81). — src/ElectronNET.API/API/App.cs:17
`Dock` keeps one instance of itself in the static `_dock`, so that one instance serves the whole process and is shared by every thread that reaches it — and it mutates instance state outside any lock (_items; e.g. `_items` at line 174). — src/ElectronNET.API/API/Dock.cs:13
`GlobalShortcut` keeps one instance of itself in the static `_globalShortcut`, so that one instance serves the whole process and is shared by every thread that reaches it — and it mutates instance state outside any lock (_shortcuts; e.g. `_shortcuts` at line 53). — src/ElectronNET.API/API/GlobalShortcut.cs:11
`Menu` keeps one instance of itself in the static `_menu`, so that one instance serves the whole process and is shared by every thread that reaches it — and it mutates instance state outside any lock (_menuItems, _contextMenuItems, ContextMenuItems; e.g. `_menuItems` at line 64). — src/ElectronNET.API/API/Menu.cs:14
`Tray` keeps one instance of itself in the static `_tray`, so that one instance serves the whole process and is shared by every thread that reaches it — and it mutates instance state outside any lock (_items; e.g. `_items` at line 220). — src/ElectronNET.API/API/Tray.cs:18
`WindowManager` keeps one instance of itself in the static `_windowManager`, so that one instance serves the whole process and is shared by every thread that reaches it — and it mutates instance state outside any lock (_isQuitOnWindowAllClosed, _browserWindows, _browserViews; e.g. `_isQuitOnWindowAllClosed` at line 56). — src/ElectronNET.API/API/WindowManager.cs:15
`BrowserWindow` is not registered, but the singleton `WindowManager` creates it and keeps it in `_browserWindows`, so one instance outlives every request and is shared by every caller that reaches it — and it mutates instance state outside any lock (_items, _thumbarButtons; e.g. `_items` at line 920). — src/ElectronNET.API/API/BrowserWindow.cs:17
`Notification` keeps mutable `static` state — one slot for the whole process, shared by every thread that reaches the type however its instances are created — and mutates it outside any lock (_notificationOptions; e.g. `_notificationOptions` at line 112). Concurrent callers lose updates, and a collection that is not built for concurrent writers can corrupt. — src/ElectronNET.API/API/Notification.cs:12
What to do
Keep singletons stateless or back their state with thread-safe types (Concurrent*/Immutable*); otherwise concurrent callers race.
A `static` field is one slot for the whole process, however its type is created: back it with a thread-safe type (ConcurrentDictionary, Interlocked), take a lock around every write, or move it into a registered singleton that does.
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 ElectronNET.Runtime ↔ ElectronNET.Runtime.Controllers depend on each other. The lightest dependency in the cycle is ElectronNET.Runtime → ElectronNET.Runtime.Controllers (ElectronNET.Runtime.StartupManager → ElectronNET.Runtime.Controllers.RuntimeControllerBase, 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/ElectronNET.API/Runtime/StartupManager.cs:8
What to do
Break namespace cycles inside a project by moving the shared type to a namespace both sides can use, or by inverting the back edge behind an interface.
Other · Architecture — Whether 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.
Other · Architecture — Whether the codebase has a recognisable, scale-appropriate structure (a named architectural style, or modular enough for its size) rather than being an ad-hoc ball of mud.
Method: Roslyn plus csproj analysis: architecture style detection (DDD, clean, vertical-slice, CQRS) and structure fitness for repo size. Deterministic.
Other · Architecture — Whether interfaces stay focused rather than fat — the Interface-Segregation principle (SOLID 'I').
Method: Roslyn scan: public interface declared-member counts (accessors fold into their property/event); fat-interface threshold (over 15 declared members) flagged per type. Each finding also reports the distinct-OPERATION count — members counted by name, so an overload group counts once — which decides whether it states the caller-side ISP harm or the implementer-side burden of an overload set. TypeScript: exported interfaces that declare behaviour, counted over their REQUIRED operations (method signatures and function-typed properties with no `?`, once per signature) — data-shape interfaces and ambient .d.ts declarations are outside the population; JavaScript declares no interfaces and is not applicable. Deterministic, type-level.
Do you agree with this assessment?
AX8 · Test isolation10.0 / 10Exemplary✓ Tool-verified
Other · Architecture — Whether production projects stay free of references to test projects — tests may depend on production, never the reverse.
Method: Csproj graph: each production project checked for references to test projects (identified by test-framework presence, not name). Zero violations is clean. Deterministic.
Do you agree with this assessment?
C2 · Access Controls7.0 / 10Strong✓ Tool-verified
Other · Security — Whether access is authorized by default — a framework authorization attribute/decorator or policy, or imperative guard methods (throw-on-violation) called from handlers.
Method: Roslyn scan: [Authorize] usage and authorization policies, plus imperative throw-on-violation guard methods detected via syntax. Deterministic.
Authorization IS enforced here (by an auth-gate middleware that short-circuits unauthorized requests) — this is NOT a claim that the code is unprotected. What's missing is a NAMED rule set: the middleware encodes the access rules inline, so the rules can't be listed, reviewed or tested apart from the middleware body that applies them. Recommendation, not a defect.
What to do
Name the access rules — give each one a named predicate/policy object your middleware consults, so the rule set can be reviewed and unit-tested independently of the pipeline that enforces it.
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.
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.
A line of code has been commented out rather than removed — dead weight that rots and confuses. Delete it (version control remembers). (×12) — src/ElectronNET.API/API/BrowserWindow.cs:734, src/ElectronNET.API/API/BrowserWindow.cs:751, src/ElectronNET.API/API/WebRequest.cs:40, …
A test is skipped ("Cookie set/get requires navigation to domain; skipping until test harness serves page") — coverage that looks present but never runs in any gate. If it's an opt-in suite, document how it runs; otherwise re-enable or delete it. — src/ElectronNET.IntegrationTests/Tests/CookiesTests.cs:13
A test is skipped ("Requires HostHook setup; skipping") — coverage that looks present but never runs in any gate. If it's an opt-in suite, document how it runs; otherwise re-enable or delete it. — src/ElectronNET.IntegrationTests/Tests/HostHookTests.cs:13
A test is skipped ("This can keep the test process hanging until the e-mail window is closed") — coverage that looks present but never runs in any gate. If it's an opt-in suite, document how it runs; otherwise re-enable or delete it. — src/ElectronNET.IntegrationTests/Tests/ShellTests.cs:13
What to do
Clear the softer debt: remove commented-out code and dead branches, re-enable or delete skipped tests, and replace blanket warning suppressions with targeted ones.
Maturity · Maturity — Whether the repository and its projects have a README, and whether it is substantive.
Method: Filesystem scan: README presence, word count, and headings for depth; git history for staleness. Exhaustive across root and project dirs, deterministic.
What to do
Explain in the README how to run the tests. Add a section called Testing to the README in the repository's top folder, saying how to run the test suite.
Add an 'Architecture' / 'How it works' section to the root README — the high-level shape.
Describe the projects a newcomer cannot place from the root README: 11 of 11 have no README of their own, in their folder or in their family's project (`src/ElectronNET.WebApp`, `src/ElectronNET.API`, `src/ElectronNET.Build`, `src/ElectronNET`, `src/ElectronNET.AspNet` and 6 more).
Maturity · Maturity — Whether key decisions (ADRs) and the high-level shape (C4/diagrams) are written down.
Method: Filesystem scan: ADR folder/naming conventions or content, plus Mermaid/PlantUML/C4/architecture.md discovery. Exhaustive, deterministic.
No Architecture Decision Records found — no conventional ADR directory, no numbered `NNNN-title` documents in any markup this check reads, and nothing ADR-shaped by content. Design rationale recorded elsewhere (a design-notes tree, a mailing list, pull-request discussion) is not visible to this check and is not re-findable per decision, so a future maintainer cannot ask why one choice was made and get an answer.
What to do
Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them.
Maturity · Maturity — Whether the repository is organised deliberately: production code and tests are set apart in a way its ecosystem or the repository itself declares.
Method: Filesystem scan: src/test folder separation and namespace-prefix consistency (majority RootNamespace agreement). Exhaustive across projects, deterministic.
Maturity · Maturity — Whether the project's current-state documentation describes the code that exists.
Method: Every current-state document's checkable claims looked up in the tree (links, versions, and artefact counts an order of magnitude off), plus two README checks: an advertised infrastructure product with no footprint, and a module the CHANGELOG records as removed. Deterministic, no model. Advisory.
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.
Do you agree with this assessment?
P10 · Library API & versioning9.7 / 10Exemplary✓ 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's code 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.
`ElectronNET.API.Electron` (src/ElectronNET.API/API/Electron.cs:6) is public, and the library's own code uses it, but no other project in this repository uses it (read: `ElectronNET(net6.0)`, `ElectronNET.AspNet(net6.0)`) and no public member of the library exposes it. Consumers outside this repository are not visible here; if they rely on it, it is API and should be documented as such. — src/ElectronNET.API/API/Electron.cs:6
`ElectronNET.API.Electron` (src/ElectronNET.API/API/Electron.cs:6) is public, and the library's own code uses it, but no other project in this repository uses it (read: `ElectronNET(net8.0)`, `ElectronNET.AspNet(net8.0)`) and no public member of the library exposes it. Consumers outside this repository are not visible here; if they rely on it, it is API and should be documented as such. — src/ElectronNET.API/API/Electron.cs:6
`ElectronNET.Common.ProcessRunner` (src/ElectronNET.API/Common/ProcessRunner.cs:22) is public, and the library's own code uses it, but no other project in this repository uses it (read: `ElectronNET(net6.0)`, `ElectronNET.AspNet(net6.0)`) and no public member of the library exposes it. Consumers outside this repository are not visible here; if they rely on it, it is API and should be documented as such. — src/ElectronNET.API/Common/ProcessRunner.cs:22
`ElectronNET.Common.ProcessRunner` (src/ElectronNET.API/Common/ProcessRunner.cs:22) is public, and the library's own code uses it, but no other project in this repository uses it (read: `ElectronNET(net8.0)`, `ElectronNET.AspNet(net8.0)`) and no public member of the library exposes it. Consumers outside this repository are not visible here; if they rely on it, it is API and should be documented as such. — src/ElectronNET.API/Common/ProcessRunner.cs:22
`ElectronNET.Common.ProcessRunner` (src/ElectronNET.API/Common/ProcessRunner.cs:22) is public, and the library's own code uses it, but no other project in this repository uses it (read: `ElectronNET(net10.0)`, `ElectronNET.AspNet(net10.0)`, `ElectronNET.ConsoleApp`, `ElectronNET.IntegrationTests`, `ElectronNET.Samples.AuthMiddleware`, `ElectronNET.Samples.ElectronHostHook`, `ElectronNET.WebApp`) and no public member of the library exposes it. Consumers outside this repository are not visible here; if they rely on it, it is API and should be documented as such. — src/ElectronNET.API/Common/ProcessRunner.cs:22
`ElectronNET.Converter.ModifierTypeListConverter` (src/ElectronNET.API/Converter/ModifierTypeListConverter.cs:12) is public, and the library's own code uses it, but no other project in this repository uses it (read: `ElectronNET(net6.0)`, `ElectronNET.AspNet(net6.0)`) and no public member of the library exposes it. Consumers outside this repository are not visible here; if they rely on it, it is API and should be documented as such. — src/ElectronNET.API/Converter/ModifierTypeListConverter.cs:12
`ElectronNET.Converter.ModifierTypeListConverter` (src/ElectronNET.API/Converter/ModifierTypeListConverter.cs:12) is public, and the library's own code uses it, but no other project in this repository uses it (read: `ElectronNET(net8.0)`, `ElectronNET.AspNet(net8.0)`) and no public member of the library exposes it. Consumers outside this repository are not visible here; if they rely on it, it is API and should be documented as such. — src/ElectronNET.API/Converter/ModifierTypeListConverter.cs:12
`ElectronNET.Converter.ModifierTypeListConverter` (src/ElectronNET.API/Converter/ModifierTypeListConverter.cs:12) is public, and the library's own code uses it, but no other project in this repository uses it (read: `ElectronNET(net10.0)`, `ElectronNET.AspNet(net10.0)`, `ElectronNET.ConsoleApp`, `ElectronNET.IntegrationTests`, `ElectronNET.Samples.AuthMiddleware`, `ElectronNET.Samples.ElectronHostHook`, `ElectronNET.WebApp`) and no public member of the library exposes it. Consumers outside this repository are not visible here; if they rely on it, it is API and should be documented as such. — src/ElectronNET.API/Converter/ModifierTypeListConverter.cs:12
`ElectronNET.Converter.PageSizeConverter` (src/ElectronNET.API/Converter/PageSizeConverter.cs:9) is public, and the library's own code uses it, but no other project in this repository uses it (read: `ElectronNET(net6.0)`, `ElectronNET.AspNet(net6.0)`) and no public member of the library exposes it. Consumers outside this repository are not visible here; if they rely on it, it is API and should be documented as such. — src/ElectronNET.API/Converter/PageSizeConverter.cs:9
`ElectronNET.Converter.PageSizeConverter` (src/ElectronNET.API/Converter/PageSizeConverter.cs:9) is public, and the library's own code uses it, but no other project in this repository uses it (read: `ElectronNET(net8.0)`, `ElectronNET.AspNet(net8.0)`) and no public member of the library exposes it. Consumers outside this repository are not visible here; if they rely on it, it is API and should be documented as such. — src/ElectronNET.API/Converter/PageSizeConverter.cs:9
`ElectronNET.Converter.PageSizeConverter` (src/ElectronNET.API/Converter/PageSizeConverter.cs:9) is public, and the library's own code uses it, but no other project in this repository uses it (read: `ElectronNET(net10.0)`, `ElectronNET.AspNet(net10.0)`, `ElectronNET.ConsoleApp`, `ElectronNET.IntegrationTests`, `ElectronNET.Samples.AuthMiddleware`, `ElectronNET.Samples.ElectronHostHook`, `ElectronNET.WebApp`) and no public member of the library exposes it. Consumers outside this repository are not visible here; if they rely on it, it is API and should be documented as such. — src/ElectronNET.API/Converter/PageSizeConverter.cs:9
`ElectronNET.API.Converter.ReleaseNotesConverter` (src/ElectronNET.API/Converter/ReleaseNotesConverter.cs:19) is public, and the library's own code uses it, but no other project in this repository uses it (read: `ElectronNET(net6.0)`, `ElectronNET.AspNet(net6.0)`) and no public member of the library exposes it. Consumers outside this repository are not visible here; if they rely on it, it is API and should be documented as such. — src/ElectronNET.API/Converter/ReleaseNotesConverter.cs:19
`ElectronNET.API.Converter.ReleaseNotesConverter` (src/ElectronNET.API/Converter/ReleaseNotesConverter.cs:19) is public, and the library's own code uses it, but no other project in this repository uses it (read: `ElectronNET(net8.0)`, `ElectronNET.AspNet(net8.0)`) and no public member of the library exposes it. Consumers outside this repository are not visible here; if they rely on it, it is API and should be documented as such. — src/ElectronNET.API/Converter/ReleaseNotesConverter.cs:19
`ElectronNET.API.Converter.ReleaseNotesConverter` (src/ElectronNET.API/Converter/ReleaseNotesConverter.cs:19) is public, and the library's own code uses it, but no other project in this repository uses it (read: `ElectronNET(net10.0)`, `ElectronNET.AspNet(net10.0)`, `ElectronNET.ConsoleApp`, `ElectronNET.IntegrationTests`, `ElectronNET.Samples.AuthMiddleware`, `ElectronNET.Samples.ElectronHostHook`, `ElectronNET.WebApp`) and no public member of the library exposes it. Consumers outside this repository are not visible here; if they rely on it, it is API and should be documented as such. — src/ElectronNET.API/Converter/ReleaseNotesConverter.cs:19
`ElectronNET.Converter.TitleBarOverlayConverter` (src/ElectronNET.API/Converter/TitleBarOverlayConverter.cs:9) is public, and the library's own code uses it, but no other project in this repository uses it (read: `ElectronNET(net6.0)`, `ElectronNET.AspNet(net6.0)`) and no public member of the library exposes it. Consumers outside this repository are not visible here; if they rely on it, it is API and should be documented as such. — src/ElectronNET.API/Converter/TitleBarOverlayConverter.cs:9
`ElectronNET.Converter.TitleBarOverlayConverter` (src/ElectronNET.API/Converter/TitleBarOverlayConverter.cs:9) is public, and the library's own code uses it, but no other project in this repository uses it (read: `ElectronNET(net8.0)`, `ElectronNET.AspNet(net8.0)`) and no public member of the library exposes it. Consumers outside this repository are not visible here; if they rely on it, it is API and should be documented as such. — src/ElectronNET.API/Converter/TitleBarOverlayConverter.cs:9
`ElectronNET.Converter.TitleBarOverlayConverter` (src/ElectronNET.API/Converter/TitleBarOverlayConverter.cs:9) is public, and the library's own code uses it, but no other project in this repository uses it (read: `ElectronNET(net10.0)`, `ElectronNET.AspNet(net10.0)`, `ElectronNET.ConsoleApp`, `ElectronNET.IntegrationTests`, `ElectronNET.Samples.AuthMiddleware`, `ElectronNET.Samples.ElectronHostHook`, `ElectronNET.WebApp`) and no public member of the library exposes it. Consumers outside this repository are not visible here; if they rely on it, it is API and should be documented as such. — src/ElectronNET.API/Converter/TitleBarOverlayConverter.cs:9
`ElectronNET.Serialization.JsonToBoxedPrimitivesConverter` (src/ElectronNET.API/Serialization/JsonToBoxedPrimitivesConverter.cs:8) is public, and the library's own code uses it, but no other project in this repository uses it (read: `ElectronNET(net6.0)`, `ElectronNET.AspNet(net6.0)`) and no public member of the library exposes it. Consumers outside this repository are not visible here; if they rely on it, it is API and should be documented as such. — src/ElectronNET.API/Serialization/JsonToBoxedPrimitivesConverter.cs:8
`ElectronNET.Serialization.JsonToBoxedPrimitivesConverter` (src/ElectronNET.API/Serialization/JsonToBoxedPrimitivesConverter.cs:8) is public, and the library's own code uses it, but no other project in this repository uses it (read: `ElectronNET(net8.0)`, `ElectronNET.AspNet(net8.0)`) and no public member of the library exposes it. Consumers outside this repository are not visible here; if they rely on it, it is API and should be documented as such. — src/ElectronNET.API/Serialization/JsonToBoxedPrimitivesConverter.cs:8
`ElectronNET.Serialization.JsonToBoxedPrimitivesConverter` (src/ElectronNET.API/Serialization/JsonToBoxedPrimitivesConverter.cs:8) is public, and the library's own code uses it, but no other project in this repository uses it (read: `ElectronNET(net10.0)`, `ElectronNET.AspNet(net10.0)`, `ElectronNET.ConsoleApp`, `ElectronNET.IntegrationTests`, `ElectronNET.Samples.AuthMiddleware`, `ElectronNET.Samples.ElectronHostHook`, `ElectronNET.WebApp`) and no public member of the library exposes it. Consumers outside this repository are not visible here; if they rely on it, it is API and should be documented as such. — src/ElectronNET.API/Serialization/JsonToBoxedPrimitivesConverter.cs:8
What to do
Make `ElectronNET.API.Electron` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ElectronNET.API.Electron` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ElectronNET.Common.ProcessRunner` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ElectronNET.Common.ProcessRunner` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ElectronNET.Common.ProcessRunner` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ElectronNET.Converter.ModifierTypeListConverter` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ElectronNET.Converter.ModifierTypeListConverter` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ElectronNET.Converter.ModifierTypeListConverter` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ElectronNET.Converter.PageSizeConverter` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ElectronNET.Converter.PageSizeConverter` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ElectronNET.Converter.PageSizeConverter` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ElectronNET.API.Converter.ReleaseNotesConverter` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ElectronNET.API.Converter.ReleaseNotesConverter` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ElectronNET.API.Converter.ReleaseNotesConverter` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ElectronNET.Converter.TitleBarOverlayConverter` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ElectronNET.Converter.TitleBarOverlayConverter` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ElectronNET.Converter.TitleBarOverlayConverter` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ElectronNET.Serialization.JsonToBoxedPrimitivesConverter` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ElectronNET.Serialization.JsonToBoxedPrimitivesConverter` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Make `ElectronNET.Serialization.JsonToBoxedPrimitivesConverter` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
Do you agree with this assessment?
P2 · Observability5.5 / 10Adequate✓ Tool-verified
Readiness · Readiness — Whether the code is diagnosable in production — structured logging, tracing/metrics, health checks.
Only 4/8 service-like projects use logging (pure contract/DTO projects are excluded — they have nothing to log). Of those 8, 6 ship a process this repository operates; the rest are libraries their consumer hosts, where the logging decision belongs to the host.
`src/ElectronNET.WebApp/Controllers/HomeController.cs` reports through `Console.Write…` at line 15 although other files in its project log through a logger. Console lines carry no level, category or structured properties and never reach the log pipeline or its exporters. — src/ElectronNET.WebApp/Controllers/HomeController.cs:15
`src/ElectronNET.WebApp/Controllers/HomeController.cs` reports through `Console.Write…` at line 17 although other files in its project log through a logger. Console lines carry no level, category or structured properties and never reach the log pipeline or its exporters. — src/ElectronNET.WebApp/Controllers/HomeController.cs:17
`src/ElectronNET.WebApp/Controllers/HomeController.cs` reports through `Console.Write…` at line 19 although other files in its project log through a logger. Console lines carry no level, category or structured properties and never reach the log pipeline or its exporters. — src/ElectronNET.WebApp/Controllers/HomeController.cs:19
`src/ElectronNET.WebApp/Controllers/HomeController.cs` reports through `Console.Write…` at line 21 although other files in its project log through a logger. Console lines carry no level, category or structured properties and never reach the log pipeline or its exporters. — src/ElectronNET.WebApp/Controllers/HomeController.cs:21
`src/ElectronNET.WebApp/Controllers/HomeController.cs` reports through `Console.Write…` at line 23 although other files in its project log through a logger. Console lines carry no level, category or structured properties and never reach the log pipeline or its exporters. — src/ElectronNET.WebApp/Controllers/HomeController.cs:23
`src/ElectronNET.WebApp/Controllers/HomeController.cs` reports through `Console.Write…` at line 25 although other files in its project log through a logger. Console lines carry no level, category or structured properties and never reach the log pipeline or its exporters. — src/ElectronNET.WebApp/Controllers/HomeController.cs:25
`src/ElectronNET.AspNet/Runtime/Controllers/RuntimeControllerAspNetBase.cs` reports through `Console.Write…` at line 137 although other files in its project log through a logger. Console lines carry no level, category or structured properties and never reach the log pipeline or its exporters. — src/ElectronNET.AspNet/Runtime/Controllers/RuntimeControllerAspNetBase.cs:137
`src/ElectronNET.AspNet/Runtime/Controllers/RuntimeControllerAspNetBase.cs` reports through `Console.Write…` at line 147 although other files in its project log through a logger. Console lines carry no level, category or structured properties and never reach the log pipeline or its exporters. — src/ElectronNET.AspNet/Runtime/Controllers/RuntimeControllerAspNetBase.cs:147
What to do
Extend structured logging across the projects you operate, and give the library ones a diagnostics seam instead — an `EventSource`/`ActivitySource` the host can subscribe to, or an optional logger on your options object — rather than taking a logging dependency on your consumers' behalf.
Replace `Console.Write…` in service code with the project's injected `ILogger<T>` (message templates with named properties), so delivery outcomes and failures reach the log pipeline with a level and a category.
Consider OpenTelemetry tracing/metrics and a health-check endpoint for operability.
Readiness · Readiness — Whether SAST, secret/dependency scanning and performance benchmarking are wired in (presence, not runtime).
Method: Filesystem scan: SAST configuration, dependency-update automation, secret scanning, and a benchmark harness or benchmark step — in this repository's own ecosystem. Exhaustive, deterministic.
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 7 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. — REDACTED:3
`nuke/_build.csproj` declares packages, and nothing in the repository keeps them current: no Dependabot or Renovate configuration that schedules updates, and no dependency-review gate on pull requests. A pinned dependency stays at the version it was added at until someone notices — including after an advisory is published against it. Add a `.github/dependabot.yml` with one `package-ecosystem` entry per ecosystem the tree uses (or an enabled `renovate.json`), and gate pull requests with `actions/dependency-review-action`. — nuke/_build.csproj:14
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.
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 each language's code 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.
1 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). — src/ElectronNET.API/Bridge/SocketIOConnection.cs:65
`await listener(arg)` resumes on the caller's captured context. In library code that context belongs to the host application, so a host that blocks on this call (or runs on a UI thread) can stall or deadlock — append `.ConfigureAwait(false)`. (×3) — src/ElectronNET.API/API/IpcMain.cs:122, src/ElectronNET.API/API/IpcMain.cs:212, src/ElectronNET.API/API/IpcMain.cs:249
`await chmodRunner.WaitForExitAsync().ConfigureAwait(true)` resumes on the caller's captured context. In library code that context belongs to the host application, so a host that blocks on this call (or runs on a UI thread) can stall or deadlock — append `.ConfigureAwait(false)`. — src/ElectronNET.API/Runtime/Services/ElectronProcess/ElectronProcessActive.cs:64
`await _next(context)` resumes on the caller's captured context. In library code that context belongs to the host application, so a host that blocks on this call (or runs on a UI thread) can stall or deadlock — append `.ConfigureAwait(false)`. (×2) — src/ElectronNET.AspNet/Middleware/ElectronAuthenticationMiddleware.cs:49, src/ElectronNET.AspNet/Middleware/ElectronAuthenticationMiddleware.cs:81
`await context.Response.WriteAsync("Unauthorized: Invalid authentication")` resumes on the caller's captured context. In library code that context belongs to the host application, so a host that blocks on this call (or runs on a UI thread) can stall or deadlock — append `.ConfigureAwait(false)`. (×2) — src/ElectronNET.AspNet/Middleware/ElectronAuthenticationMiddleware.cs:57, src/ElectronNET.AspNet/Middleware/ElectronAuthenticationMiddleware.cs:89
`await context.Response.WriteAsync("Unauthorized: Authentication required")` resumes on the caller's captured context. In library code that context belongs to the host application, so a host that blocks on this call (or runs on a UI thread) can stall or deadlock — append `.ConfigureAwait(false)`. — src/ElectronNET.AspNet/Middleware/ElectronAuthenticationMiddleware.cs:97
What to do
Make the call chain async end-to-end and await it — never block on a Task with .Wait()/.GetAwaiter().GetResult().
Do you agree with this assessment?
R1 · Type Safety4.9 / 10Weak✓ 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.
26 typed · 27 plain JS — the untyped files are src/ElectronNET.Host/ElectronHostHook/connector.js, src/ElectronNET.Host/ElectronHostHook/index.js, src/ElectronNET.Host/api/app.js, src/ElectronNET.Host/api/autoUpdater.js, REDACTED, REDACTED (+21 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.
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.
REDACTED:437 · REDACTED:469 — 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. — REDACTED:437
src/ElectronNET.Samples.ElectronHostHook/ElectronHostHook/connector.ts:3 · src/ElectronNET.WebApp/ElectronHostHook/connector.ts:3 — the 2 copies are spread across 2 directories, so the shared home is a decision rather than an obvious spot: check first whether one of them already owns this behaviour, and otherwise put the extracted module somewhere all of the sites already reach rather than making one of them depend on another. — src/ElectronNET.Samples.ElectronHostHook/ElectronHostHook/connector.ts:3
src/ElectronNET.Host/ElectronHostHook/connector.ts:6 · src/ElectronNET.Samples.ElectronHostHook/ElectronHostHook/connector.ts:4 · src/ElectronNET.WebApp/ElectronHostHook/connector.ts:5 — the 3 copies are spread across 3 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/ElectronNET.Host/ElectronHostHook/connector.ts:6
src/ElectronNET.Host/api/autoUpdater.ts:152 · src/ElectronNET.Host/api/autoUpdater.ts:170 — 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/ElectronNET.Host/api/autoUpdater.ts:152
src/ElectronNET.Host/api/browserWindows.ts:735 · src/ElectronNET.Host/api/dock.ts:65 · src/ElectronNET.Host/api/menu.ts:76 — the 3 copies are spread across 3 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/ElectronNET.Host/api/browserWindows.ts:735
src/ElectronNET.Host/api/tray.ts:14 · src/ElectronNET.Host/api/tray.ts:26 — 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/ElectronNET.Host/api/tray.ts:14
src/ElectronNET.Host/api/ipc.ts:58 · src/ElectronNET.Host/api/ipc.ts:70 — 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/ElectronNET.Host/api/ipc.ts:58
src/ElectronNET.Host/api/tray.ts:125 · src/ElectronNET.Host/api/tray.ts:137 — 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/ElectronNET.Host/api/tray.ts:125
src/ElectronNET.Host/api/app.ts:319 · src/ElectronNET.Host/api/app.ts:329 — 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/ElectronNET.Host/api/app.ts:319
src/ElectronNET.Host/api/ipc.ts:7 · src/ElectronNET.Host/api/ipc.ts:24 — 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/ElectronNET.Host/api/ipc.ts:7
src/ElectronNET.Host/api/webContents.ts:267 · src/ElectronNET.Host/api/webContents.ts:277 — 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/ElectronNET.Host/api/webContents.ts:267
src/ElectronNET.Host/api/clipboard.ts:1 · src/ElectronNET.Host/api/dock.ts:1 — the 2 copies are spread across 2 files, 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/ElectronNET.Host/api/clipboard.ts:1
src/ElectronNET.Host/api/ipc.ts:44 · src/ElectronNET.Host/api/webContents.ts:509 — 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/ElectronNET.Host/api/ipc.ts:44
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.
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.
(anonymous) has cyclomatic complexity 25 and cognitive complexity 24; 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. — REDACTED:344
createWindow has cyclomatic complexity 24 and cognitive complexity 27; 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/ElectronNET.Host/api/browserWindows.ts:238
What to do
Break down the listed branch-heavy functions; aim P95 cyclomatic ≤ 5.
Do you agree with this assessment?
R3 · Large Files7.7 / 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/ElectronNET.Host/api/browserWindows.ts has 766 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/ElectronNET.Host/api/browserWindows.ts:1
src/ElectronNET.Host/api/webContents.ts has 623 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/ElectronNET.Host/api/webContents.ts:1
REDACTED has 427 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — REDACTED:1
What to do
Split each oversized file along the responsibilities already in it, into smaller focused modules in the same package.
Do you agree with this assessment?
R4 · Test Coverage0.0 / 10Critical✓ Tool-verified
React / JS · Readiness — Static test reachability (D-386): the share of production files reachable from any test via the import graph — measured without running anything.
Method: Static test reachability: the share of production files reachable from any test via the import graph — measured without running anything. Deterministic.
0% of 29 production file(s) reachable from 0 test file(s) via the import graph — 'production' here is the RESIDUE: every source file left once tests, tooling, generated output, config, declarations and declaration-only modules, fixture corpora, type fixtures, behaviour-free data modules, re-export barrels, registration/constant data modules and service workers are set aside, so the percentage is taken over a smaller denominator than the workspace's file count
What to do
Add tests that import the unreached modules (directly or through their public entry).
React / JS · Readiness — How outdated the npm dependencies are (a maturity signal). JS/npm CVEs are scored separately in D30 (JS/npm Dependency Vulnerabilities).
Method: npm dependency staleness from manifest/registry metadata (a maturity signal; JS/npm CVEs are scored separately in D30, which answers dependency vulnerabilities for every ecosystem). Deterministic.
What to do
Bump outdated dependencies to current versions to limit upgrade debt.
Do you agree with this assessment?
R6 · Tooling6.7 / 10Adequate✓ 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 eslint as package.json scripts and run them in CI.
Do you agree with this assessment?
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.
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.
Declared in src/ElectronNET.Host/package.json but never imported anywhere in that package or its workspace members — no static import reaches it. Usually that is dead weight and attack surface, but two shapes are indistinguishable from source and are NOT dead: an optional or native peer that another dependency loads dynamically at runtime, and a package a build, docs or test step installs and invokes separately. Confirm which of the three this is before removing it.
Declared in src/ElectronNET.WebApp/ElectronHostHook/package.json but never imported anywhere in that package or its workspace members — no static import reaches it. Usually that is dead weight and attack surface, but two shapes are indistinguishable from source and are NOT dead: an optional or native peer that another dependency loads dynamically at runtime, and a package a build, docs or test step installs and invokes separately. Confirm which of the three this is before removing it.
What to do
Remove unused dependencies, declare unlisted imports explicitly, and demote type-/test-only packages to devDependencies.
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.
Other · Security — Transport security, security headers, secure cookies, input validation, middleware order and crypto hygiene (presence, not runtime).
Method: Roslyn plus filesystem scan: HSTS/security headers, secure cookies, input validation, middleware order, weak crypto (MD5/SHA1/DES); HTTPS-metadata context-aware. On a repository with no .NET source it reads JavaScript/TypeScript, Dart, Ruby, Scala, Rust or Elixir source itself (test, vendored, generated and minified paths not) for the arms that hold whether or not the code serves HTTP: a weak hash or cipher, key material fixed in the source, a TLS client that accepts any certificate, and (JavaScript/TypeScript, Ruby, Scala, Rust and Elixir) an obsolete TLS version; the server controls are not assessed there, and a Dart, Ruby, Scala, Rust or Elixir repository that serves no HTTP of its own is N/A on them. Deterministic.
None of the 11 security response headers the OWASP Secure Headers Project recommends (Content-Security-Policy, Strict-Transport-Security, X-Content-Type-Options, X-Frame-Options, …) is configured — defense in depth, even when a reverse proxy could set them. (−2.0 on this card.)
This web host's pipeline is composed here and adds no security response header (Content-Security-Policy, Strict-Transport-Security, X-Content-Type-Options, a frame policy) to what it serves. (×3) — src/ElectronNET.Samples.AuthMiddleware/Program.cs:9, src/ElectronNET.Samples.ElectronHostHook/Program.cs:11, src/ElectronNET.WebApp/Program.cs:20
No ModelState/[ApiController]/FluentValidation signal — inbound payloads reach handlers unvalidated. (−2.0 on this card.)
A cookie (`Cookies.Append`) carries who is signed in, and it is set without Secure. Without Secure the browser also sends it over plain http://, where anyone on the same network can read it. (−1.5 on this card.) — src/ElectronNET.AspNet/Middleware/ElectronAuthenticationMiddleware.cs:72
What to do
Add security response headers (Content-Security-Policy first, then Strict-Transport-Security, X-Content-Type-Options and a frame policy) — defense in depth, even when a reverse proxy could set them.
Validate inbound models (ModelState/[ApiController]/FluentValidation) to reduce injection and bad-data risk.
Lock down every session and sign-in cookie: `new CookieOptions { HttpOnly = true, Secure = true, SameSite = SameSiteMode.Lax }` on `Response.Cookies.Append`, leave `Cookie.HttpOnly` on and set `Cookie.SecurePolicy = CookieSecurePolicy.Always` in `AddCookie`/`AddSession`, or force both for every cookie with `app.UseCookiePolicy(new CookiePolicyOptions { HttpOnly = HttpOnlyPolicy.Always, Secure = CookieSecurePolicy.Always })`.
Other · Code Health — Whether the code avoids sync-over-async (deadlock-prone blocking on tasks) and async void.
Method: Roslyn syntax scan: async methods scanned for .Wait()/.GetAwaiter().GetResult() and async-void outside event handlers. Deterministic, hard fact per invocation.
`async void` can't be awaited and its exceptions crash the process instead of propagating. Return `Task` — or, where the delegate contract requires void (timer/event/callback registrations), make this a thin void shim that awaits a Task-returning inner method inside try/catch so exceptions are contained. — src/ElectronNET.WebApp/Controllers/WindowsController.cs:53
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. (×12) — src/ElectronNET.API/API/App.cs:354, src/ElectronNET.API/API/App.cs:1266, src/ElectronNET.API/API/AutoUpdater.cs:26, …
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. — src/ElectronNET.API/Bridge/SocketIOConnection.cs:65
Other · Code Health — Whether any branch is dead by construction — a switch arm whose label can never equal a case-normalised subject, or an `else if` whose predicate the arm above has already swallowed.
Method: Roslyn syntax + semantics: switch labels compared against the subject's own case normaliser, and if/else-if chains checked for a literal an earlier arm's containment test already swallows. Deterministic, provable per finding. Advisory.
Do you agree with this assessment?
X13 · Undrained process 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.
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.
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.
`ProcessRunner` implements `IDisposable` — so it has told every caller it holds something worth releasing — and it constructs `stdOutEvent` itself (line 31), which makes that instance its own. But `stdOutEvent` is named in none of the methods the disposal search covered: `Dispose` (line 454), `Close` (line 427), `OnDispose` (line 450) — 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` (`stdOutEvent?.Dispose();`), or, if it truly does not need releasing, drop `IDisposable` from the type so the claim and the behaviour agree. — src/ElectronNET.API/Common/ProcessRunner.cs:31
`ProcessRunner` implements `IDisposable` — so it has told every caller it holds something worth releasing — and it constructs `stdErrEvent` itself (line 32), which makes that instance its own. But `stdErrEvent` is named in none of the methods the disposal search covered: `Dispose` (line 454), `Close` (line 427), `OnDispose` (line 450) — 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` (`stdErrEvent?.Dispose();`), or, if it truly does not need releasing, drop `IDisposable` from the type so the claim and the behaviour agree. — src/ElectronNET.API/Common/ProcessRunner.cs:32
`timeoutSource` is a `CancellationTokenSource`, which implements `IDisposable`, and it is created here (line 323). Every use of it in `WaitForExitAsync` 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 timeoutSource = …;`), which releases it at the end of the scope on every path including a throw. — src/ElectronNET.API/Common/ProcessRunner.cs:323
`linkedSource` is a `CancellationTokenSource`, which implements `IDisposable`, and it is created here (line 324). Every use of it in `WaitForExitAsync` 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 linkedSource = …;`), which releases it at the end of the scope on every path including a throw. — src/ElectronNET.API/Common/ProcessRunner.cs:324
What to do
Each finding names the value and the span that decides who owns it — the `new` that created it, or the constructor parameter that handed it over. Confirm ownership from that span, then make the disposal match it: release what this type created, leave what it was injected with to whoever created THAT, and drop a finalizer whose type holds nothing unmanaged to release.
Other · Code Health — Whether a method that temporarily changes state belonging to the whole process — the working directory, an environment variable — puts it back on EVERY path: a restore reached only when nothing throws leaks the change to the rest of the process.
Method: Roslyn syntax + semantics: method bodies that write the process working directory or an environment variable and write it back in the same body, checked for whether that restore sits in a `finally`/`catch` or only on the straight-line path. On a repository with no .NET source the same rule reads production JavaScript/TypeScript off the engine’s own token stream (test, vendored and minified paths not): `process.chdir`, `process.env.NAME =`/`["NAME"] =` and `delete process.env.NAME`, and Deno’s `Deno.chdir`/`Deno.env.set`/`Deno.env.delete`, paired per function body (a nested function or arrow is its own body, and module top-level code is none), where the last write puts back a local the body captured from the same global or deletes a variable the first write set, with at least one statement between them; a write in a `catch`/`finally` of that body silences it. Deterministic, provable per finding. Advisory.
Other · Code Health — Whether async methods accept a CancellationToken so work can be cancelled (adoption curve).
Method: Roslyn scan: every async method (excluding framework-fixed overrides/Blazor handlers) checked for CancellationToken parameter presence. Deterministic, adoption percentage. On a repository with no .NET source it reads JavaScript/TypeScript off the engine’s own token stream (test, vendored and minified paths not) with the same question: every named async function that itself makes a request an AbortSignal can cancel (global `fetch`, axios and its file-local instances, ky, ofetch) counts, and it is compliant when its parameters or body name a signal or it hands one of its own parameters to the request as options; signatures a framework fixes (JSX event handlers, route and lifecycle exports, request-first handlers, `override`, `'use server'` modules, TanStack `mutationFn`) are exempt unless they take a signal. Deterministic, adoption percentage.
Only 34/48 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. (×12) — src/ElectronNET.WebApp/Controllers/WindowsController.cs:53, src/ElectronNET.API/API/ApiBase.cs:123, src/ElectronNET.API/API/BrowserWindow.cs:1166, …
Neither takes a CancellationToken nor reads the one of the function it sits in, while it calls something that takes one — this work can't be stopped early once started. Take the token, or pass on the enclosing one. — src/ElectronNET.Templates/templates/blazor/Program.cs:37
1 async method(s) await work their caller's cancellation cannot reach: a CancellationToken they hold (a parameter, or the one a framework-fixed signature carries) is never passed on, or the call is handed CancellationToken.None, default or an already-cancelled token. Forward the caller's token to that call.
Its signature is fixed by the framework, and the token it carries (`context.RequestAborted`) reaches none of the calls here that take one — so an aborted request or a stopping host still waits for that work. Pass `context.RequestAborted` to them. — src/ElectronNET.AspNet/Middleware/ElectronAuthenticationMiddleware.cs:37
What to do
Thread a CancellationToken through async methods so work stops promptly on cancellation.
Other · Code Health — Whether an argument guard throws the exception its own condition describes — a guard that rejects a value for being EMPTY and reports it as `ArgumentNullException` tells the caller a parameter was null when it provably was not.
Method: Roslyn syntax: `throw new ArgumentNullException(nameof(p))` statements controlled by an `if`, whose condition is read for a test that is true of a NON-null `p` — an emptiness test that dereferences it (`p.Count == 0`, `!p.Any()`) or a BCL predicate documented true of the empty value (`string.IsNullOrEmpty(p)`). Deterministic, provable per finding. Advisory.
Other · Code Health — Whether the work a diagnostic log line costs is paid only when that line is wanted — C# evaluates a call's arguments BEFORE the call, so a trace/debug message joined or projected out of a collection is built in full on every pass, and then discarded by a sink the shipped configuration leaves switched off.
Method: Roslyn syntax: log calls at a diagnostic level (a `Log`-prefixed method naming Trace/Debug/Verbose, or a bare `Debug`/`Trace`/`Verbose` on a receiver named for a logger), whose argument list is read for a call whose cost scales with a sequence — a LINQ operator, a materialisation, `string.Join`, a serializer — with no enclosing level check or conditional-compilation region. On a repository with no .NET source it reads JavaScript/TypeScript off the engine’s own token stream (test, vendored and minified paths not) with the same rule: a `debug`/`trace`/`verbose` call on a receiver named for a logger, or a `log`-prefixed method naming the level, whose argument calls an array operator (`map`/`filter`/`reduce`/`sort`/…), `Array.from`, `Object.keys/values/entries`, `JSON.stringify`/`util.inspect` over anything but a literal, or an array `join` — outside any arrow or function passed as an argument, which the logger calls only when the level is on — with no enclosing `if`, `&&` or `?:` whose condition names a level, a level string, or the `NODE_ENV`/`__DEV__`/`DEV` build switch. Deterministic, provable per finding. Advisory.
Do you agree with this assessment?
X24 · Document value interpolated into markup unescaped10.0 / 10Exemplary○ Nothing flagged
Other · Security — Whether text read out of the document being converted is escaped before it is written into generated markup — a value the document's author chose, interpolated into an attribute the surrounding literal delimits, can close that attribute and open another.
Method: Roslyn semantic model over the whole compilation: a string-typed `Value`/`InnerText`/`InnerXml`/`Text` member declared inside `DocumentFormat.OpenXml` or `System.Xml` is a taint SOURCE, propagated through assignments, returns, arguments, tuple elements and string composition to its transitive closure, then read at interpolated-string holes that sit in a markup position the surrounding literal itself delimits. Escaper/encoder calls and enclosing validator conditions cut the flow. Flow- and container-insensitive by construction. A second arm needs no provenance at all and reports a type that CONTRADICTS ITSELF — the same expression escaped at one delimited markup hole and interpolated raw at another hole in the same markup position of the same type, which the type's own escaping proves is a defect without knowing where the value came from. On a repository with no .NET source it reads JavaScript/TypeScript off the token stream with the same rule: a DOM read of raw document text (`getAttribute`, `textContent`, `innerText`, `nodeValue`) is the source, propagated through local bindings and string composition, and judged at template-literal and concatenation holes in the same two delimited markup positions; escapers and validating conditions cut it, and documentation-site, test, vendored and minified scripts are not read. Deterministic, provable per finding. Advisory.
Do you agree with this assessment?
X27 · Collection changed while being enumerated10.0 / 10Exemplary○ Nothing flagged
Other · Code Health — Whether a `foreach` leaves the collection it is walking alone — a body that adds to or removes from the very collection the loop is enumerating invalidates the enumerator it is holding, so the next `MoveNext` throws `InvalidOperationException` and the remaining items are never seen.
Method: Roslyn syntax + semantics: `foreach` statements whose body calls a structural mutator (`Add`/`Remove`/`Clear`/`Insert`/…) on the very expression the loop is enumerating. Two arms. ARM A — the source is a concrete fragile BCL collection, or a live `Keys`/`Values` view over one, and the mutator resolves to that same collection's own member; concurrent and immutable collections and arrays are outside the population by construction, since their enumerators survive a structural change. ARM B — the source is an argument-less accessor CALL on a receiver whose body is in source: the accessor must return a stored field VERBATIM and a sibling member must structurally change that same field, both read off the implementations rather than from the members' names. A mutation the loop provably exits immediately after (`break`/`return`/`throw`/`goto`), or one written inside a nested loop or a lambda, is counted and never reported. Deterministic, provable per finding. Advisory.
Do you agree with this assessment?
X28 · Index access outside its own emptiness guard10.0 / 10Exemplary○ Nothing flagged
Other · Code Health — Whether a condition that tests a value for emptiness indexes that same value only where the test holds — an `||` written one parenthesis too far to the left leaves an index access outside the guard beside it, so the empty case the guard exists to anticipate reaches the index and throws.
Method: Roslyn syntax only, no semantic model: the OUTERMOST `&&`/`||` of every boolean condition, read for a symbol the condition tests for emptiness (`string.IsNullOrEmpty`/`IsNullOrWhiteSpace`, a `Length`/`Count` comparison against a literal, `Any()`, a `Length`/`Count` pattern, or a comparison against `""`) and ALSO indexes. Each `symbol[...]` access is placed by a boolean-reachability walk from the access up to the outermost connective: an access is COVERED when some enclosing step has it in the right operand and the left operand, under the truth value that step forces, proves the symbol non-empty — a recursion over `&&`/`||` whose true- and false-directions are asymmetric. A finding needs BOTH an uncovered access and a covered one on the same symbol in the same condition, which is the agreeing twin that separates a misplaced parenthesis from an unrelated length test. Bare index accesses with no emptiness test in the condition are neither counted nor reported; a non-identifier receiver and a lambda nested inside the condition are outside the population. Deterministic, provable per finding. Advisory.
Do you agree with this assessment?
X29 · Per-element action decided by a fixed element10.0 / 10Exemplary○ Nothing flagged
Other · Code Health — Whether a decision taken once per element is taken ABOUT that element — a test inside a counted loop that reads a fixed subscript of the very collection its guarded statement indexes by the loop variable applies element zero's answer to all of them, so the elements that differ from it are all handled wrongly, and in the same direction.
Method: Roslyn syntax only, no semantic model: every `for` statement declaring exactly ONE loop variable, and every `if` inside its body that is not under a nested loop or a lambda. A site enters the population when the `if`’s condition never mentions the loop variable while the statement it guards indexes some collection by that variable ALONE (`c[i]`; `c[i + 1]` and `c[i, j]` are outside it). A finding additionally needs the AGREEING TWIN at the same-collection grain: the condition must read THAT SAME collection at a subscript that does not move — written into the condition, or reached through a local declared BEFORE the loop, so an alias bound inside the body is not followed. Both collection expressions must be simple identifiers. On a repository with no .NET source the same rule reads JavaScript/TypeScript off the engine’s own token stream (tests included, bundles and vendored paths not): a `for (let|var|const x = …; …; …)` with one declarator and a braced body, an alias followed only when it is declared before the loop in a block that encloses it and never assigned inside the loop. Deterministic, provable per finding. Advisory.
Other · Code Health — Whether exceptions are handled rather than silently swallowed or rethrown with lost stack traces.
Method: Roslyn syntax scan: every catch clause counted; empty catches and bare rethrows flagged. Population is all catch clauses, not estimated. Deterministic, hard fact.
An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it. (×4) — src/ElectronNET.API/Common/ProcessRunner.cs:398, src/ElectronNET.API/Common/ProcessRunner.cs:538, src/ElectronNET.API/Common/ProcessRunner.cs:571, …
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/ElectronNET.Build/PrintItemMetadata.cs:20, src/ElectronNET.Build/PrintItemMetadata.cs:26
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.
2/9 NRT-eligible project(s) enable <Nullable>enable</Nullable> (projects targeting a pre-C#-8 framework are excluded — NRTs aren't available there). NRTs catch a whole class of null-deref bugs at compile time.
What to do
Enable <Nullable>enable</Nullable> across all projects and resolve warnings rather than suppressing with `!`.
Do you agree with this assessment?
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).
The score is the rank-weighted fold of these lenses (worst-heaviest), each including its meta-dimensions; a lens with a Critical contributor is capped at Fair (its band reads "gated by …") and is never the strongest area however high its average.
Unscored — 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.
P12 CI test-gate honesty — 3 observation(s) recorded · Reported, not scored — this card publishes what the CI gate does with the test inventory rather than grading it. The findings above are its output.
SC1 Supply-chain hygiene — 2 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
X10 Duplicated predicate — 13 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
X7 Silent fallback defaults — 1 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 — 43 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
AXB2 Runtime readiness — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
AXR1 Runtime accessibility — the dev server (`npm run start`) exited before it served a page. Likely cause (our sandbox): `npm run` found no package.json in the folder where our sandbox ran it. This is a limit of our sandbox, not of your repository. Last output: "npm error code ENOENT / npm error syscall open / npm error path <repo>/package.json / npm error errno -2 / npm error enoent Could not read package.json: Error: ENOENT: no such file or directory, open '<repo>/package.json' / npm error enoent This is related to npm not being able to find a file. / npm error enoent / npm error A complete log of this run can be found in: <path>" No runtime evidence was gathered. This is a statement about this run, not a statement about your application: nothing here says the surface is inaccessible, only that it was never rendered.
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.
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
D21 Naming Consistency — Naming consistency is measured on C# and TypeScript only; JavaScript not measured.
D22 Internal API Consistency — API consistency is measured on C# only; the exposed TypeScript surface was not measured.
D23 Boundary Type-Coupling — small single-context codebase (17,919 production LoC in the .NET projects) — bounded contexts are not needed at this size No bounded-context organisation was detected either — neither a context-shaped layout, nor 2+ sibling source directories each declaring an aggregate root, nor 2+ sibling projects each declaring an entity of their own or taking another project's integration events. Declaring this codebase's bounded contexts (≥2) would let cross-boundary type coupling be assessed. Declare them in `.codehealth/config.yaml` at the repository root (create it if absent), mapping each context name to the module-path or namespace prefixes that belong to it — e.g. `architecture:` → `contexts:` → `Billing: ["src/billing", "Acme.Billing"]`, `Catalog: ["src/catalog", "Acme.Catalog"]`.
D25 ADR Conformance — no ADRs to check
D31 IaC & Container Security — No Infrastructure-as-Code or container manifests found (Dockerfile, Docker Compose, Terraform, Kubernetes/Helm, CloudFormation, ARM, Bicep, Ansible); nothing to scan.
D32 Data Compliance (PII/GDPR) — 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.
D37 Vulnerability-disclosure Policy — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed.
D40 Network Egress Confinement — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here.
D41 Kernel & Syscall Confinement — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here.
D42 Runtime Threat Enforcement — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here.
D7 Architectural Integrity — no checkable ADRs and no dependency cycles — architectural integrity not assessed
D8 Code Coverage — Coverage not measured — no coverage collector is wired up
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
P7 Outbound HTTP resilience — no outbound HTTP usage detected — no HttpClient/IHttpClientFactory/AddHttpClient in source, and no Refit/RestSharp/Flurl.Http namespace or package reference
P8 Schema migrations — no EF Core usage detected
P9 Domain vs controller coverage — no coverage report found on disk — produce a coverage report in a standard format (Cobertura — `dotnet test --collect:"XPlat Code Coverage"` with a `coverlet.collector` PackageReference) and commit it — a hosted scan measures a clone of the repository, so a report that exists only in a working tree, a CI runner's or your own, never reaches it; the artefact is commonly gitignored, so `git add -f` that one file (or un-ignore its path) and commit it alongside the code it measures, or wire coverage collection into CI, to enable this cross-layer check
PF1 Benchmark discipline — Not applicable: no benchmark suite was found by the two searches this check runs — a BenchmarkDotNet package reference in any project file (loaded, or on disk), and a script whose name contains `benchmark` that this repository's CI runs. Neither can see a suite in another ecosystem's idiom, so this is not a verdict that the repository has none. Benchmarks are credited as a bonus, so their absence is neither scored nor deducted, and nothing is asked of a repository that has none.
PF2 Allocation hygiene — Not scored: this check counted allocation-aware idioms (Span, pools, stackalloc) per line, which describes what kind of code a repository is rather than whether it has an allocation problem, so it was withdrawn. Nothing here is a finding about your code.
R11 Import Boundaries — No recognizable feature-sliced/layered src layout — boundary rules not applicable.
X14 Bypassable address classification — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X15 Unvalidated length from an untrusted reader — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X17 Uncapped recursion over a caller-supplied document — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X21 Side-effecting pattern guard — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X22 Contradicted release guard — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X25 Inert configuration knob — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X26 Unsynchronised callback handoff — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X30 Support guard that admits what it rejects — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X32 Type resolved by simple name across every loaded assembly — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X6 Hand-rolled structured-format parsing — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
X9 Subsumed condition operand — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
Appendix A — Findings (grouped)
The findings behind the scores, grouped by severity, then by dimension and kind. The high-severity issues are enumerated in full below; items per group are capped at 25 with any overflow stated explicitly per group, never silently truncated. The complete machine-readable list of every finding (all severities) is the companion findings.md in this report's bundle.
NoWarnInCsproj nuke/_build.csproj:7— CS0649 — this warning is switched off for the WHOLE project, in every file it builds, including code written years from now: nothing at the call site records that the rule was ever silenced, so the next reader has no reason to look here. Fix what the rule is reporting and drop the code from the list, or — if some occurrences really are legitimate — narrow the suppression to those sites and give each one its reason, so the rule keeps protecting the rest of the project.
NoWarnInCsproj nuke/_build.csproj:7— CS0169 — this warning is switched off for the WHOLE project, in every file it builds, including code written years from now: nothing at the call site records that the rule was ever silenced, so the next reader has no reason to look here. Fix what the rule is reporting and drop the code from the list, or — if some occurrences really are legitimate — narrow the suppression to those sites and give each one its reason, so the rule keeps protecting the rest of the project.
NoWarnInCsproj REDACTED:16— 1701 — this warning is switched off for the WHOLE project, in every file it builds, including code written years from now: nothing at the call site records that the rule was ever silenced, so the next reader has no reason to look here. Fix what the rule is reporting and drop the code from the list, or — if some occurrences really are legitimate — narrow the suppression to those sites and give each one its reason, so the rule keeps protecting the rest of the project.
NoWarnInCsproj src/ElectronNET.AspNet/ElectronNET.AspNet.csproj:16— 1701 — this warning is switched off for the WHOLE project, in every file it builds, including code written years from now: nothing at the call site records that the rule was ever silenced, so the next reader has no reason to look here. Fix what the rule is reporting and drop the code from the list, or — if some occurrences really are legitimate — narrow the suppression to those sites and give each one its reason, so the rule keeps protecting the rest of the project.
NoWarnInCsproj REDACTED:16— 1702 — this warning is switched off for the WHOLE project, in every file it builds, including code written years from now: nothing at the call site records that the rule was ever silenced, so the next reader has no reason to look here. Fix what the rule is reporting and drop the code from the list, or — if some occurrences really are legitimate — narrow the suppression to those sites and give each one its reason, so the rule keeps protecting the rest of the project.
NoWarnInCsproj src/ElectronNET.AspNet/ElectronNET.AspNet.csproj:16— 1702 — this warning is switched off for the WHOLE project, in every file it builds, including code written years from now: nothing at the call site records that the rule was ever silenced, so the next reader has no reason to look here. Fix what the rule is reporting and drop the code from the list, or — if some occurrences really are legitimate — narrow the suppression to those sites and give each one its reason, so the rule keeps protecting the rest of the project.
NoWarnInCsproj REDACTED:16— 4014 — this warning is switched off for the WHOLE project, in every file it builds, including code written years from now: nothing at the call site records that the rule was ever silenced, so the next reader has no reason to look here. Fix what the rule is reporting and drop the code from the list, or — if some occurrences really are legitimate — narrow the suppression to those sites and give each one its reason, so the rule keeps protecting the rest of the project.
NoWarnInCsproj src/ElectronNET.AspNet/ElectronNET.AspNet.csproj:16— 4014 — this warning is switched off for the WHOLE project, in every file it builds, including code written years from now: nothing at the call site records that the rule was ever silenced, so the next reader has no reason to look here. Fix what the rule is reporting and drop the code from the list, or — if some occurrences really are legitimate — narrow the suppression to those sites and give each one its reason, so the rule keeps protecting the rest of the project.
NoWarnInCsproj REDACTED:16— CA1416 — this warning is switched off for the WHOLE project, in every file it builds, including code written years from now: nothing at the call site records that the rule was ever silenced, so the next reader has no reason to look here. Fix what the rule is reporting and drop the code from the list, or — if some occurrences really are legitimate — narrow the suppression to those sites and give each one its reason, so the rule keeps protecting the rest of the project.
NoWarnInCsproj src/ElectronNET.AspNet/ElectronNET.AspNet.csproj:16— CA1416 — this warning is switched off for the WHOLE project, in every file it builds, including code written years from now: nothing at the call site records that the rule was ever silenced, so the next reader has no reason to look here. Fix what the rule is reporting and drop the code from the list, or — if some occurrences really are legitimate — narrow the suppression to those sites and give each one its reason, so the rule keeps protecting the rest of the project.
NoWarnInCsproj REDACTED:16— CS1591 — this project generates an XML documentation file as a build output, so its documentation is something it PUBLISHES to whoever consumes the assembly, and this entry switches off a rule whose only job is to report that documentation missing or malformed. The two decisions sit in the same file and the quiet one wins: the documentation this project ships has holes exactly where the rule would have pointed, no build says so, and the people who meet the gap are downstream — in their editor, at the moment they are trying to use the member. Write the documentation the rule is asking for and drop the code from the list; where only some elements genuinely cannot carry it, narrow the suppression to those sites and give each one its reason, so the rest of the API stays covered. If the documentation was never meant to be consumed, the honest fix is the other line — stop generating the file, so the project no longer publishes something it is choosing not to check.
NoWarnInCsproj src/ElectronNET.AspNet/ElectronNET.AspNet.csproj:16— CS1591 — this project generates an XML documentation file as a build output, so its documentation is something it PUBLISHES to whoever consumes the assembly, and this entry switches off a rule whose only job is to report that documentation missing or malformed. The two decisions sit in the same file and the quiet one wins: the documentation this project ships has holes exactly where the rule would have pointed, no build says so, and the people who meet the gap are downstream — in their editor, at the moment they are trying to use the member. Write the documentation the rule is asking for and drop the code from the list; where only some elements genuinely cannot carry it, narrow the suppression to those sites and give each one its reason, so the rest of the API stays covered. If the documentation was never meant to be consumed, the honest fix is the other line — stop generating the file, so the project no longer publishes something it is choosing not to check.
NoWarnInCsproj src/ElectronNET.Templates/ElectronNET.Templates.csproj:21— NU5128 — this warning is switched off for the WHOLE project, including builds years from now. It is raised by the build itself — the packaging, restore or SDK step — about the project as a whole, not by the compiler or an analyzer at a line of code, so there is no call site to narrow it to and no per-site directive that could carry a reason: this element is the only place the decision can be recorded. Say WHY here, in a comment on the entry, or fix what the rule is reporting and drop the code from the list.
EmptyCatchBlock src/ElectronNET.API/Common/ProcessRunner.cs:398— 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/ElectronNET.API/Common/ProcessRunner.cs:538— 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/ElectronNET.API/Common/ProcessRunner.cs:571— 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/ElectronNET.API/Common/ProcessRunner.cs:606— 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.
AC3 · Page structure· Routed page without a <PageTitle> · ×1
Routed page without a <PageTitle> src/ElectronNET.Samples.AuthMiddleware/Components/Pages/NotFound.razor:4— 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· Document without a <title> · ×1
Document without a <title> src/ElectronNET.WebApp/Views/Home/Index.cshtml:2— A page with no <title> gives no name in the tab, history or screen-reader page list. Add a descriptive <title> in <head>.
AC4 · Keyboard semantics· Clickable element isn't keyboard-operable · ×1
Clickable element isn't keyboard-operable src/ElectronNET.Samples.AuthMiddleware/Components/Layout/MainLayout.razor:22— The repo's own CSS styles .dismiss with `cursor: pointer`, so this <span> is a control — but it has no role, no tabindex="0" and no key handler, so it can only be reached with a mouse. Use a <button>, or add role + tabindex="0" + a key handler.
AC4 · Keyboard semantics· Click handler on a non-interactive <div> · ×1
Click handler on a non-interactive <div> src/ElectronNET.Samples.AuthMiddleware/Components/Layout/NavMenu.razor:9— A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabindex="0" + a key handler.
Namespace dependency cycle src/ElectronNET.API/Runtime/StartupManager.cs:8— The namespaces ElectronNET.Runtime ↔ ElectronNET.Runtime.Controllers depend on each other. The lightest dependency in the cycle is ElectronNET.Runtime → ElectronNET.Runtime.Controllers (ElectronNET.Runtime.StartupManager → ElectronNET.Runtime.Controllers.RuntimeControllerBase, 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.
WriteOnlyPrivateField nuke/ReleaseNotesParser.cs:20— private Regex _versionRegex — assigned 1 time(s), read never — this field is written and never read anywhere its type can be reached from, so the state it keeps answers no question: every assignment to it computes a value that nothing observes, on every instance, for the lifetime of each one. It reads as a flag the code branches on, and nothing branches on it. Delete the field and its assignments — or, if the value was MEANT to be consulted, the missing read is the defect this row is pointing at, and the branch that should have depended on it is not there.
AC6 · Visual & motion safety· Animation without a prefers-reduced-motion guard · ×16
Animation without a prefers-reduced-motion guard src/ElectronNET.WebApp/wwwroot/assets/css/about.css:21— `.about` moves (`transition: visibility 0s .12s linear , opacity .12s ease-in, transform .12s ease-in`) 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/ElectronNET.WebApp/wwwroot/assets/css/about.css:28— `.about.is-shown` moves (`transition: visibility 0s 0s linear , opacity .24s ease-out, transform .24s ease-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/ElectronNET.WebApp/wwwroot/assets/css/demo.css:50— `.demo-toggle-button:before` moves (`transition: transform .2s cubic-bezier(.4,.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/ElectronNET.WebApp/wwwroot/assets/css/demo.css:112— `.is-open .demo-box` moves (`animation: demo-box-fade-in .2s cubic-bezier(0, .20, .20, .96)`) 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/ElectronNET.WebApp/wwwroot/assets/css/section.css:18— `.section` moves (`transition: visibility 0s .12s linear , opacity .12s ease-in, transform .12s ease-in`) 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/ElectronNET.WebApp/wwwroot/assets/css/section.css:25— `.section.is-shown` moves (`transition: visibility 0s 0s linear , opacity .36s ease-out, transform .36s ease-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/ElectronNET.Samples.AuthMiddleware/Components/Layout/ReconnectModal.razor.css:37— `#components-reconnect-modal[open]` moves (`animation: components-reconnect-modal-slideUp 1.5s cubic-bezier(.05, .89, .25, 1.02) 0.3s, components-reconnect-modal-fadeInOpacity 0.5s ease-in-out 0.3s`) 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/ElectronNET.Samples.AuthMiddleware/Components/Layout/ReconnectModal.razor.css:118— `.components-rejoining-animation div` moves (`animation: components-rejoining-animation 1.5s cubic-bezier(0, 0.2, 0.8, 1) 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.
Animation without a prefers-reduced-motion guard docs/md-styles.css:3694— `.collapsing` moves (`transition-property: height,visibility`) 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 docs/md-styles.css:5418— `.progress-bar` moves (`transition: width .6s`) 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 docs/md-styles.css:5432— `.progress-bar.active` moves (`animation: 2s linear infinite progress-bar-stripes`) 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 docs/md-styles.css:6116— `.modal.fade .modal-dialog` moves (`transition: transform .3s ease-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 docs/md-styles.css:6117— `.modal.fade .modal-dialog` moves (`transition: transform .3s ease-out,-webkit-transform .3s ease-out,-o-transform .3s ease-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 docs/md-styles.css:6521— `.carousel-inner > .item` moves (`transition: left .6s 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 docs/md-styles.css:6532— `.carousel-inner > .item` moves (`transition: transform .6s 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 docs/md-styles.css:6533— `.carousel-inner > .item` moves (`transition: transform .6s ease-in-out,-webkit-transform .6s ease-in-out,-o-transform .6s 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.
AC6 · Visual & motion safety· Focus outline removed in CSS without a · ×13
Focus outline removed in CSS without a :focus replacement src/ElectronNET.WebApp/wwwroot/assets/css/demo.css:39— `.demo-toggle-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/ElectronNET.WebApp/wwwroot/assets/css/nativize.css:41— `a` 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/ElectronNET.WebApp/wwwroot/assets/css/nav.css:79— `.nav-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/ElectronNET.WebApp/wwwroot/assets/css/nav.css:116— `.nav-footer a` 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/ElectronNET.WebApp/wwwroot/assets/css/nav.css:132— `.nav-footer-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 docs/md-styles.css:3719— `.dropdown-toggle: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 docs/md-styles.css:3775— `.dropdown-menu > .active > a` 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 docs/md-styles.css:3794— `.open > a` 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 docs/md-styles.css:3910— `.btn-group.open .dropdown-toggle` 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 docs/md-styles.css:4524— `.navbar-toggle: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 docs/md-styles.css:6106— `.modal` 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 docs/md-styles.css:6146— `.modal-content` 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 docs/md-styles.css:6628— `.carousel-control: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.
Sync-over-async (deadlock risk) through `.Result` src/ElectronNET.API/API/App.cs:354— Reading `.Result` of a task that has not completed blocks this thread until it does — the same block as `.Wait()`: under a synchronization context (Blazor, a UI thread, classic ASP.NET) it deadlocks, and on the thread pool it parks a thread for as long as the work runs. `await` the task instead (make the caller `async`); where a synchronous entry point must stay, keep the block in ONE documented bridge with a timeout.
Sync-over-async (deadlock risk) through `.Result` src/ElectronNET.API/API/App.cs:1266— Reading `.Result` of a task that has not completed blocks this thread until it does — the same block as `.Wait()`: under a synchronization context (Blazor, a UI thread, classic ASP.NET) it deadlocks, and on the thread pool it parks a thread for as long as the work runs. `await` the task instead (make the caller `async`); where a synchronous entry point must stay, keep the block in ONE documented bridge with a timeout.
Sync-over-async (deadlock risk) through `.Result` src/ElectronNET.API/API/AutoUpdater.cs:26— Reading `.Result` of a task that has not completed blocks this thread until it does — the same block as `.Wait()`: under a synchronization context (Blazor, a UI thread, classic ASP.NET) it deadlocks, and on the thread pool it parks a thread for as long as the work runs. `await` the task instead (make the caller `async`); where a synchronous entry point must stay, keep the block in ONE documented bridge with a timeout.
Sync-over-async (deadlock risk) through `.Result` src/ElectronNET.API/API/AutoUpdater.cs:43— Reading `.Result` of a task that has not completed blocks this thread until it does — the same block as `.Wait()`: under a synchronization context (Blazor, a UI thread, classic ASP.NET) it deadlocks, and on the thread pool it parks a thread for as long as the work runs. `await` the task instead (make the caller `async`); where a synchronous entry point must stay, keep the block in ONE documented bridge with a timeout.
Sync-over-async (deadlock risk) through `.Result` src/ElectronNET.API/API/AutoUpdater.cs:61— Reading `.Result` of a task that has not completed blocks this thread until it does — the same block as `.Wait()`: under a synchronization context (Blazor, a UI thread, classic ASP.NET) it deadlocks, and on the thread pool it parks a thread for as long as the work runs. `await` the task instead (make the caller `async`); where a synchronous entry point must stay, keep the block in ONE documented bridge with a timeout.
Sync-over-async (deadlock risk) through `.Result` src/ElectronNET.API/API/AutoUpdater.cs:77— Reading `.Result` of a task that has not completed blocks this thread until it does — the same block as `.Wait()`: under a synchronization context (Blazor, a UI thread, classic ASP.NET) it deadlocks, and on the thread pool it parks a thread for as long as the work runs. `await` the task instead (make the caller `async`); where a synchronous entry point must stay, keep the block in ONE documented bridge with a timeout.
Sync-over-async (deadlock risk) through `.Result` src/ElectronNET.API/API/AutoUpdater.cs:94— Reading `.Result` of a task that has not completed blocks this thread until it does — the same block as `.Wait()`: under a synchronization context (Blazor, a UI thread, classic ASP.NET) it deadlocks, and on the thread pool it parks a thread for as long as the work runs. `await` the task instead (make the caller `async`); where a synchronous entry point must stay, keep the block in ONE documented bridge with a timeout.
Sync-over-async (deadlock risk) through `.Result` src/ElectronNET.API/API/AutoUpdater.cs:109— Reading `.Result` of a task that has not completed blocks this thread until it does — the same block as `.Wait()`: under a synchronization context (Blazor, a UI thread, classic ASP.NET) it deadlocks, and on the thread pool it parks a thread for as long as the work runs. `await` the task instead (make the caller `async`); where a synchronous entry point must stay, keep the block in ONE documented bridge with a timeout.
Sync-over-async (deadlock risk) through `.Result` src/ElectronNET.API/API/AutoUpdater.cs:133— Reading `.Result` of a task that has not completed blocks this thread until it does — the same block as `.Wait()`: under a synchronization context (Blazor, a UI thread, classic ASP.NET) it deadlocks, and on the thread pool it parks a thread for as long as the work runs. `await` the task instead (make the caller `async`); where a synchronous entry point must stay, keep the block in ONE documented bridge with a timeout.
Sync-over-async (deadlock risk) through `.Result` src/ElectronNET.API/API/BrowserView.cs:34— Reading `.Result` of a task that has not completed blocks this thread until it does — the same block as `.Wait()`: under a synchronization context (Blazor, a UI thread, classic ASP.NET) it deadlocks, and on the thread pool it parks a thread for as long as the work runs. `await` the task instead (make the caller `async`); where a synchronous entry point must stay, keep the block in ONE documented bridge with a timeout.
Sync-over-async (deadlock risk) through `.Result` src/ElectronNET.API/API/WebContents.cs:207— Reading `.Result` of a task that has not completed blocks this thread until it does — the same block as `.Wait()`: under a synchronization context (Blazor, a UI thread, classic ASP.NET) it deadlocks, and on the thread pool it parks a thread for as long as the work runs. `await` the task instead (make the caller `async`); where a synchronous entry point must stay, keep the block in ONE documented bridge with a timeout.
Sync-over-async (deadlock risk) through `.Result` src/ElectronNET.API/API/WebContents.cs:216— 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.
X2 · Cancellation propagation· Async method without CancellationToken · ×12
Async method without CancellationToken: UpdateReply src/ElectronNET.WebApp/Controllers/WindowsController.cs:53— No CancellationToken parameter — this work can't be stopped early once started.
Async method without CancellationToken: InvokeAsyncWithTimeout src/ElectronNET.API/API/ApiBase.cs:123— No CancellationToken parameter — this work can't be stopped early once started.
Async method without CancellationToken: GetParentWindowAsync src/ElectronNET.API/API/BrowserWindow.cs:1166— No CancellationToken parameter — this work can't be stopped early once started.
Async method without CancellationToken: GetChildWindowsAsync src/ElectronNET.API/API/BrowserWindow.cs:1177— No CancellationToken parameter — this work can't be stopped early once started.
Async method without CancellationToken: WriteAsync src/ElectronNET.API/Common/ProcessRunner.cs:215— No CancellationToken parameter — this work can't be stopped early once started.
Async method without CancellationToken: WaitAndKillAsync src/ElectronNET.API/Common/ProcessRunner.cs:304— No CancellationToken parameter — this work can't be stopped early once started.
Async method without CancellationToken: StartCore src/ElectronNET.API/Runtime/Services/ElectronProcess/ElectronProcessActive.cs:43— No CancellationToken parameter — this work can't be stopped early once started.
Async method without CancellationToken: StartInternal src/ElectronNET.API/Runtime/Services/ElectronProcess/ElectronProcessActive.cs:163— No CancellationToken parameter — this work can't be stopped early once started.
Async method without CancellationToken: StartCore src/ElectronNET.API/Runtime/Services/ElectronProcess/ElectronProcessPassive.cs:25— No CancellationToken parameter — this work can't be stopped early once started.
Async method without CancellationToken: Start src/ElectronNET.API/Runtime/Services/LifetimeServiceBase.cs:43— No CancellationToken parameter — this work can't be stopped early once started.
Async method without CancellationToken: StartCore REDACTED:38— No CancellationToken parameter — this work can't be stopped early once started.
Async method without CancellationToken: StartCore src/ElectronNET.AspNet/Runtime/Controllers/RuntimeControllerAspNetElectronFirst.cs:20— No CancellationToken parameter — this work can't be stopped early once started.
Stateful shared instance: ElectronProcessPassive src/ElectronNET.API/Runtime/Services/ElectronProcess/ElectronProcessPassive.cs:12— `ElectronProcessPassive` is not registered, but the singleton `RuntimeControllerAspNetElectronFirst` creates it and keeps it in `electronProcess`, so one instance outlives every request and is shared by every caller that reaches it — and it mutates instance state outside any lock (process; e.g. `process` at line 27).
Stateful shared instance: ElectronProcessActive src/ElectronNET.API/Runtime/Services/ElectronProcess/ElectronProcessActive.cs:19— `ElectronProcessActive` is not registered, but the singleton `RuntimeControllerAspNetDotnetFirst` creates it and keeps it in `electronProcess`, so one instance outlives every request and is shared by every caller that reaches it — and it mutates instance state outside any lock (process; e.g. `process` at line 212).
Stateful shared instance: App src/ElectronNET.API/API/App.cs:17— `App` keeps one instance of itself in the static `_app`, so that one instance serves the whole process and is shared by every thread that reaches it — and it mutates instance state outside any lock (_preventQuit, _isReady; e.g. `_preventQuit` at line 81).
Stateful shared instance: Dock src/ElectronNET.API/API/Dock.cs:13— `Dock` keeps one instance of itself in the static `_dock`, so that one instance serves the whole process and is shared by every thread that reaches it — and it mutates instance state outside any lock (_items; e.g. `_items` at line 174).
Stateful shared instance: GlobalShortcut src/ElectronNET.API/API/GlobalShortcut.cs:11— `GlobalShortcut` keeps one instance of itself in the static `_globalShortcut`, so that one instance serves the whole process and is shared by every thread that reaches it — and it mutates instance state outside any lock (_shortcuts; e.g. `_shortcuts` at line 53).
Stateful shared instance: Menu src/ElectronNET.API/API/Menu.cs:14— `Menu` keeps one instance of itself in the static `_menu`, so that one instance serves the whole process and is shared by every thread that reaches it — and it mutates instance state outside any lock (_menuItems, _contextMenuItems, ContextMenuItems; e.g. `_menuItems` at line 64).
Stateful shared instance: Tray src/ElectronNET.API/API/Tray.cs:18— `Tray` keeps one instance of itself in the static `_tray`, so that one instance serves the whole process and is shared by every thread that reaches it — and it mutates instance state outside any lock (_items; e.g. `_items` at line 220).
Stateful shared instance: WindowManager src/ElectronNET.API/API/WindowManager.cs:15— `WindowManager` keeps one instance of itself in the static `_windowManager`, so that one instance serves the whole process and is shared by every thread that reaches it — and it mutates instance state outside any lock (_isQuitOnWindowAllClosed, _browserWindows, _browserViews; e.g. `_isQuitOnWindowAllClosed` at line 56).
Stateful shared instance: BrowserWindow src/ElectronNET.API/API/BrowserWindow.cs:17— `BrowserWindow` is not registered, but the singleton `WindowManager` creates it and keeps it in `_browserWindows`, so one instance outlives every request and is shared by every caller that reaches it — and it mutates instance state outside any lock (_items, _thumbarButtons; e.g. `_items` at line 920).
Awaits without ConfigureAwait(false) src/ElectronNET.API/API/IpcMain.cs:122— `await listener(arg)` resumes on the caller's captured context. In library code that context belongs to the host application, so a host that blocks on this call (or runs on a UI thread) can stall or deadlock — append `.ConfigureAwait(false)`.
Awaits without ConfigureAwait(false) src/ElectronNET.API/API/IpcMain.cs:212— `await listener(arg)` resumes on the caller's captured context. In library code that context belongs to the host application, so a host that blocks on this call (or runs on a UI thread) can stall or deadlock — append `.ConfigureAwait(false)`.
Awaits without ConfigureAwait(false) src/ElectronNET.API/API/IpcMain.cs:249— `await listener(arg)` resumes on the caller's captured context. In library code that context belongs to the host application, so a host that blocks on this call (or runs on a UI thread) can stall or deadlock — append `.ConfigureAwait(false)`.
Awaits without ConfigureAwait(false) src/ElectronNET.API/Runtime/Services/ElectronProcess/ElectronProcessActive.cs:64— `await chmodRunner.WaitForExitAsync().ConfigureAwait(true)` resumes on the caller's captured context. In library code that context belongs to the host application, so a host that blocks on this call (or runs on a UI thread) can stall or deadlock — append `.ConfigureAwait(false)`.
Awaits without ConfigureAwait(false) src/ElectronNET.AspNet/Middleware/ElectronAuthenticationMiddleware.cs:49— `await _next(context)` resumes on the caller's captured context. In library code that context belongs to the host application, so a host that blocks on this call (or runs on a UI thread) can stall or deadlock — append `.ConfigureAwait(false)`.
Awaits without ConfigureAwait(false) src/ElectronNET.AspNet/Middleware/ElectronAuthenticationMiddleware.cs:57— `await context.Response.WriteAsync("Unauthorized: Invalid authentication")` resumes on the caller's captured context. In library code that context belongs to the host application, so a host that blocks on this call (or runs on a UI thread) can stall or deadlock — append `.ConfigureAwait(false)`.
Awaits without ConfigureAwait(false) src/ElectronNET.AspNet/Middleware/ElectronAuthenticationMiddleware.cs:81— `await _next(context)` resumes on the caller's captured context. In library code that context belongs to the host application, so a host that blocks on this call (or runs on a UI thread) can stall or deadlock — append `.ConfigureAwait(false)`.
Awaits without ConfigureAwait(false) src/ElectronNET.AspNet/Middleware/ElectronAuthenticationMiddleware.cs:89— `await context.Response.WriteAsync("Unauthorized: Invalid authentication")` resumes on the caller's captured context. In library code that context belongs to the host application, so a host that blocks on this call (or runs on a UI thread) can stall or deadlock — append `.ConfigureAwait(false)`.
Awaits without ConfigureAwait(false) src/ElectronNET.AspNet/Middleware/ElectronAuthenticationMiddleware.cs:97— `await context.Response.WriteAsync("Unauthorized: Authentication required")` resumes on the caller's captured context. In library code that context belongs to the host application, so a host that blocks on this call (or runs on a UI thread) can stall or deadlock — append `.ConfigureAwait(false)`.
Stateful singleton: Dock src/ElectronNET.API/API/Dock.cs:13— `Dock` is a singleton (one shared instance) but mutates instance state outside any lock (_items; e.g. `_items` at line 174).
Stateful singleton: GlobalShortcut src/ElectronNET.API/API/GlobalShortcut.cs:11— `GlobalShortcut` is a singleton (one shared instance) but mutates instance state outside any lock (_shortcuts; e.g. `_shortcuts` at line 53).
Stateful singleton: Tray src/ElectronNET.API/API/Tray.cs:18— `Tray` is a singleton (one shared instance) but mutates instance state outside any lock (_items; e.g. `_items` at line 220).
Stateful singleton: Menu src/ElectronNET.API/API/Menu.cs:14— `Menu` is a singleton (one shared instance) but mutates instance state outside any lock (_menuItems, _contextMenuItems, ContextMenuItems; e.g. `_menuItems` at line 64).
Stateful singleton: WindowManager src/ElectronNET.API/API/WindowManager.cs:15— `WindowManager` is a singleton (one shared instance) but mutates instance state outside any lock (_isQuitOnWindowAllClosed, _browserWindows, _browserViews; e.g. `_isQuitOnWindowAllClosed` at line 56).
Stateful singleton: App src/ElectronNET.API/API/App.cs:17— `App` is a singleton (one shared instance) but mutates instance state outside any lock (_preventQuit, _isReady; e.g. `_preventQuit` at line 81).
Stateful singleton: RuntimeControllerAspNetElectronFirst src/ElectronNET.AspNet/Runtime/Controllers/RuntimeControllerAspNetElectronFirst.cs:10— `RuntimeControllerAspNetElectronFirst` is a singleton (one shared instance) but mutates instance state outside any lock (electronProcess; e.g. `electronProcess` at line 32).
Stateful singleton: RuntimeControllerAspNetDotnetFirst src/ElectronNET.AspNet/Runtime/Controllers/RuntimeControllerAspNetDotnetFirst.cs:13— `RuntimeControllerAspNetDotnetFirst` is a singleton (one shared instance) but mutates instance state outside any lock (electronProcess; e.g. `electronProcess` at line 30).
BareSuppressMessage src/ElectronNET.API/API/ApiBase.cs:334— SuppressMessage — the suppression records no reason: either it carries no justification argument at all, or one that states nothing a reader can weigh ("OK", "By design"). A suppression is a decision somebody made, and without the reason the next reader cannot tell a considered exception from an unexamined one, so it is never revisited. Write what makes this site legitimately different — the invariant that holds, the framework contract that forces the shape — or remove the suppression and fix what it hides.
BareSuppressMessage src/ElectronNET.API/Common/ProcessRunner.cs:22— SuppressMessage — the suppression records no reason: either it carries no justification argument at all, or one that states nothing a reader can weigh ("OK", "By design"). A suppression is a decision somebody made, and without the reason the next reader cannot tell a considered exception from an unexamined one, so it is never revisited. Write what makes this site legitimately different — the invariant that holds, the framework contract that forces the shape — or remove the suppression and fix what it hides.
BareSuppressMessage src/ElectronNET.API/Common/TimeSpanExtensions.cs:13— SuppressMessage — the suppression records no reason: either it carries no justification argument at all, or one that states nothing a reader can weigh ("OK", "By design"). A suppression is a decision somebody made, and without the reason the next reader cannot tell a considered exception from an unexamined one, so it is never revisited. Write what makes this site legitimately different — the invariant that holds, the framework contract that forces the shape — or remove the suppression and fix what it hides.
BareSuppressMessage src/ElectronNET.API/Common/TimeSpanExtensions.cs:14— SuppressMessage — the suppression records no reason: either it carries no justification argument at all, or one that states nothing a reader can weigh ("OK", "By design"). A suppression is a decision somebody made, and without the reason the next reader cannot tell a considered exception from an unexamined one, so it is never revisited. Write what makes this site legitimately different — the invariant that holds, the framework contract that forces the shape — or remove the suppression and fix what it hides.
BareSuppressMessage src/ElectronNET.API/Common/TimeSpanExtensions.cs:15— SuppressMessage — the suppression records no reason: either it carries no justification argument at all, or one that states nothing a reader can weigh ("OK", "By design"). A suppression is a decision somebody made, and without the reason the next reader cannot tell a considered exception from an unexamined one, so it is never revisited. Write what makes this site legitimately different — the invariant that holds, the framework contract that forces the shape — or remove the suppression and fix what it hides.
BareSuppressMessage src/ElectronNET.API/Common/TimeSpanExtensions.cs:16— SuppressMessage — the suppression records no reason: either it carries no justification argument at all, or one that states nothing a reader can weigh ("OK", "By design"). A suppression is a decision somebody made, and without the reason the next reader cannot tell a considered exception from an unexamined one, so it is never revisited. Write what makes this site legitimately different — the invariant that holds, the framework contract that forces the shape — or remove the suppression and fix what it hides.
BareSuppressMessage src/ElectronNET.IntegrationTests/ElectronFixture.cs:10— SuppressMessage — the suppression records no reason: either it carries no justification argument at all, or one that states nothing a reader can weigh ("OK", "By design"). A suppression is a decision somebody made, and without the reason the next reader cannot tell a considered exception from an unexamined one, so it is never revisited. Write what makes this site legitimately different — the invariant that holds, the framework contract that forces the shape — or remove the suppression and fix what it hides.
Change coupling: WebContents.cs ↔ webContents.ts src/ElectronNET.API/API/WebContents.cs:1— `src/ElectronNET.API/API/WebContents.cs` and `src/ElectronNET.Host/api/webContents.ts` change together 67% of the time (14 of the 21 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) and are written in DIFFERENT LANGUAGES, so no import can join them and they cannot be co-located into one unit — they compile and ship as separate artifacts. What binds them is a CONTRACT across that boundary — an event or message name, a route, a serialised shape — that each side currently spells out on its own, which is exactly why a change to one drags the other. Declare that contract once where both sides read it (a shared schema, a generated constants file, an interface-definition file) so a change on one side fails the other's build instead of drifting silently; where the surface is too small to be worth that, name the counterpart in a comment on both sides so the next reader finds it. There is nothing here to merge. You can check this without leaving the row: of the 14 shared commits counted here, the most recent 3 are `a04ca0b9` Completed APIs from #956; `fffd7dfb` Added more missing APIs; `98c72af3` Updated zoom level — run `git show` on any of them.
Change coupling: WindowManager.cs ↔ REDACTED src/ElectronNET.API/API/WindowManager.cs:1— `src/ElectronNET.API/API/WindowManager.cs` and `REDACTED` change together 58% of the time (7 of the 12 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) and are written in DIFFERENT LANGUAGES, so no import can join them and they cannot be co-located into one unit — they compile and ship as separate artifacts. What binds them is a CONTRACT across that boundary — an event or message name, a route, a serialised shape — that each side currently spells out on its own, which is exactly why a change to one drags the other. Declare that contract once where both sides read it (a shared schema, a generated constants file, an interface-definition file) so a change on one side fails the other's build instead of drifting silently; where the surface is too small to be worth that, name the counterpart in a comment on both sides so the next reader finds it. There is nothing here to merge. You can check this without leaving the row: of the 7 shared commits counted here, the most recent 3 are `7af2e954` Fixed 1040; `87668f56` removing '-event' suffix from event names to normalise naming convention; `0657a274` Add socket.io client csharp package (at that commit the files were still `ElectronNET.API/WindowManager.cs` and `REDACTED`) — run `git show` on any of them.
Change coupling: WindowManager.cs ↔ browserWindows.ts src/ElectronNET.API/API/WindowManager.cs:1— `src/ElectronNET.API/API/WindowManager.cs` and `src/ElectronNET.Host/api/browserWindows.ts` change together 50% of the time (6 of the 12 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) and are written in DIFFERENT LANGUAGES, so no import can join them and they cannot be co-located into one unit — they compile and ship as separate artifacts. What binds them is a CONTRACT across that boundary — an event or message name, a route, a serialised shape — that each side currently spells out on its own, which is exactly why a change to one drags the other. Declare that contract once where both sides read it (a shared schema, a generated constants file, an interface-definition file) so a change on one side fails the other's build instead of drifting silently; where the surface is too small to be worth that, name the counterpart in a comment on both sides so the next reader finds it. There is nothing here to merge. You can check this without leaving the row: of the 6 shared commits counted here, the most recent 3 are `7af2e954` Fixed 1040; `3a2c997e` Ensure windows are not retained after being destroyed #1008; `a619b6e5` Implemented BrowserView API #371 (at that commit the files were still `ElectronNET.API/WindowManager.cs` and `ElectronNET.Host/api/browserWindows.ts`) — run `git show` on any of them.
Change coupling: ElectronProcessActive.cs ↔ StartupManager.cs src/ElectronNET.API/Runtime/Services/ElectronProcess/ElectronProcessActive.cs:1— `src/ElectronNET.API/Runtime/Services/ElectronProcess/ElectronProcessActive.cs` and `src/ElectronNET.API/Runtime/StartupManager.cs` change together 50% of the time (5 of the 10 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets). They sit in different directories, but in this ecosystem the namespace is declared in the FILE, not by the folder — so the two may well share one namespace and reference each other with no import for this pass to see. Read the pair before acting: if one derives from or overrides the other, the dependency is explicit in the type declaration and the co-change is definitional; if one registers itself into the other through a hook or an initialiser, the missing dependency is DELIBERATE and the thing to add is a comment saying so; if they simply belong together, co-locate them; if none of these holds, the coupling is hidden and worth breaking. You can check this without leaving the row: of the 5 shared commits counted here, the most recent 3 are `7cd552a7` Finished #1106; `01407497` Fixed #1103; `11f71fee` Automatic Port Selection and Secured Communication (#1038) — run `git show` on any of them.
D4 · Code Duplication· Edited copy of a member (9 corresponding lines) · ×4
Edited copy of a member (9 corresponding lines) src/ElectronNET.API/API/Cookies.cs:75— src/ElectronNET.API/API/Cookies.cs:75-83 | src/ElectronNET.API/API/Dialog.cs:49-60 — These two members are one piece of code written twice and then edited apart: 9 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.
Edited copy of a member (9 corresponding lines) src/ElectronNET.API/API/Session.cs:179— src/ElectronNET.API/API/Session.cs:179-187 | src/ElectronNET.API/API/Session.cs:209-217 — These two members are one piece of code written twice and then edited apart: 9 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.
Edited copy of a member (9 corresponding lines) src/ElectronNET.API/API/IpcMain.cs:225— src/ElectronNET.API/API/IpcMain.cs:225-233 | src/ElectronNET.API/API/IpcMain.cs:242-253 — These two members are one piece of code written twice and then edited apart: 9 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.
Edited copy of a member (9 corresponding lines) src/ElectronNET.API/API/Session.cs:49— src/ElectronNET.API/API/Session.cs:49-57 | src/ElectronNET.API/API/Session.cs:63-71 — These two members are one piece of code written twice and then edited apart: 9 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.
Swallowed exception (empty catch) src/ElectronNET.API/Common/ProcessRunner.cs:398— 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/ElectronNET.API/Common/ProcessRunner.cs:538— 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/ElectronNET.API/Common/ProcessRunner.cs:571— 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/ElectronNET.API/Common/ProcessRunner.cs:606— 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.
Low contrast colour pair in CSS (2.2:1) src/ElectronNET.WebApp/Views/CrashHang/ProcessCrash.cshtml:2— `body` sets color: #fff on background-color: #8aba87 — 2.2:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them.
Low contrast colour pair in CSS (2.2:1) src/ElectronNET.WebApp/Views/CrashHang/ProcessHang.cshtml:2— `body` sets color: #fff on background-color: #8aba87 — 2.2:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them.
Low contrast colour pair in CSS (2.2:1) src/ElectronNET.WebApp/Views/Windows/DemoWindow.cshtml:2— `body` sets color: #fff on background-color: #8aba87 — 2.2:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them.
TooManyMethods: BrowserWindow src/ElectronNET.API/API/BrowserWindow.cs— TooManyMethods — 306 significant lines (blank, comment-only and punctuation-only lines excluded), 106 methods. The bar is 30 methods; this is 76 over it, 3.53× 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: App src/ElectronNET.API/API/App.cs— TooManyMethods — 383 significant lines (blank, comment-only and punctuation-only lines excluded), 57 methods. The bar is 30 methods; this is 27 over it, 1.90× 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: WebContents src/ElectronNET.API/API/WebContents.cs— TooManyMethods — 185 significant lines (blank, comment-only and punctuation-only lines excluded), 54 methods. The bar is 30 methods; this is 24 over it, 1.80× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
Hotspot: src/ElectronNET.Host/api/browserWindows.ts src/ElectronNET.Host/api/browserWindows.ts:19— src/ElectronNET.Host/api/browserWindows.ts changed 3 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 56 in browserWindows.default at line 19. 1 of those changes was a fix/bug commit, and the other 2 changed it for other reasons — this file is under both repair and feature pressure. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-06-09..2026-09-07, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-06-09 10:00:41 +02:00' --until='2026-09-07 10:00:41 +02:00' --full-history --no-merges -- src/ElectronNET.Host/api/browserWindows.ts`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: src/ElectronNET.Host/api/webContents.ts src/ElectronNET.Host/api/webContents.ts:9— src/ElectronNET.Host/api/webContents.ts changed 3 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 15 in webContents.default at line 9. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-06-09..2026-09-07, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-06-09 10:00:41 +02:00' --until='2026-09-07 10:00:41 +02:00' --full-history --no-merges -- src/ElectronNET.Host/api/webContents.ts`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
D4 · Code Duplication· Edited copy of a member (12 corresponding lines) · ×2
Edited copy of a member (12 corresponding lines) src/ElectronNET.API/API/IpcMain.cs:115— src/ElectronNET.API/API/IpcMain.cs:115-126 | src/ElectronNET.API/API/IpcMain.cs:205-216 — 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.
Edited copy of a member (12 corresponding lines) src/ElectronNET.API/API/BrowserWindow.cs:917— src/ElectronNET.API/API/BrowserWindow.cs:917-928 | src/ElectronNET.API/API/Dock.cs:171-182 — 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· Edited copy of a member (14 corresponding lines) · ×2
Edited copy of a member (14 corresponding lines) src/ElectronNET.API/Runtime/Controllers/RuntimeControllerDotNetFirst.cs:84— src/ElectronNET.API/Runtime/Controllers/RuntimeControllerDotNetFirst.cs:84-97 | src/ElectronNET.API/Runtime/Controllers/RuntimeControllerElectronFirst.cs:81-94 — These two members are one piece of code written twice and then edited apart: 14 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.
Edited copy of a member (14 corresponding lines) src/ElectronNET.WebApp/Program.cs:27— src/ElectronNET.WebApp/Program.cs:27-40 | src/ElectronNET.ConsoleApp/Program.cs:35-48 — These two members are one piece of code written twice and then edited apart: 14 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.
P12 · CI test-gate honesty· Test failure does not fail the CI gate · ×2
Test failure does not fail the CI gate REDACTED:88— `continue-on-error: true` lets the step or job that runs `dotnet test src/ElectronNET.IntegrationTests/ElectronNET.IntegrationTests.csproj -c Release --no-build -r ${{ matrix.rid }} -p:RuntimeIde…` fail without failing the pipeline — the suite can go red and the change still merges. Remove it from the test step, or quarantine the specific failing tests instead.
Test failure does not fail the CI gate REDACTED:96— `continue-on-error: true` lets the step or job that runs `dotnet test src/ElectronNET.IntegrationTests/ElectronNET.IntegrationTests.csproj -c Release --no-build -r ${{ matrix.rid }} -p:RuntimeIde…` fail without failing the pipeline — the suite can go red and the change still merges. Remove it from the test step, or quarantine the specific failing tests instead.
Sync-over-async blocking — 1 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/ElectronNET.API/Bridge/SocketIOConnection.cs:65— `.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).
Duplicated block (10 lines × 2 locations) src/ElectronNET.Host/api/ipc.ts:58— src/ElectronNET.Host/api/ipc.ts:58 · src/ElectronNET.Host/api/ipc.ts:70 — 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.
Duplicated block (10 lines × 2 locations) src/ElectronNET.Host/api/tray.ts:125— src/ElectronNET.Host/api/tray.ts:125 · src/ElectronNET.Host/api/tray.ts:137 — 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.
Duplicated block (8 lines × 2 locations) src/ElectronNET.Host/api/ipc.ts:7— src/ElectronNET.Host/api/ipc.ts:7 · src/ElectronNET.Host/api/ipc.ts:24 — 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.
Duplicated block (8 lines × 2 locations) src/ElectronNET.Host/api/webContents.ts:267— src/ElectronNET.Host/api/webContents.ts:267 · src/ElectronNET.Host/api/webContents.ts:277 — 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.
X18 · Disposal-pattern correctness· Owned disposable field is never released · ×2
Owned disposable field is never released src/ElectronNET.API/Common/ProcessRunner.cs:31— `ProcessRunner` implements `IDisposable` — so it has told every caller it holds something worth releasing — and it constructs `stdOutEvent` itself (line 31), which makes that instance its own. But `stdOutEvent` is named in none of the methods the disposal search covered: `Dispose` (line 454), `Close` (line 427), `OnDispose` (line 450) — 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` (`stdOutEvent?.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/ElectronNET.API/Common/ProcessRunner.cs:32— `ProcessRunner` implements `IDisposable` — so it has told every caller it holds something worth releasing — and it constructs `stdErrEvent` itself (line 32), which makes that instance its own. But `stdErrEvent` is named in none of the methods the disposal search covered: `Dispose` (line 454), `Close` (line 427), `OnDispose` (line 450) — 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` (`stdErrEvent?.Dispose();`), or, if it truly does not need releasing, drop `IDisposable` from the type so the claim and the behaviour agree.
X18 · Disposal-pattern correctness· Disposable created and abandoned in the method that made it · ×2
Disposable created and abandoned in the method that made it src/ElectronNET.API/Common/ProcessRunner.cs:323— `timeoutSource` is a `CancellationTokenSource`, which implements `IDisposable`, and it is created here (line 323). Every use of it in `WaitForExitAsync` 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 timeoutSource = …;`), which releases it at the end of the scope on every path including a throw.
Disposable created and abandoned in the method that made it src/ElectronNET.API/Common/ProcessRunner.cs:324— `linkedSource` is a `CancellationTokenSource`, which implements `IDisposable`, and it is created here (line 324). Every use of it in `WaitForExitAsync` 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 linkedSource = …;`), which releases it at the end of the scope on every path including a throw.
AC3 · Page structure· Page without a main landmark · ×1
Page without a main landmark src/ElectronNET.Samples.ElectronHostHook/Views/Home/Index.cshtml:7— No <main> (or role="main") means no "skip to content" target and a weaker landmark map. Wrap the primary content in <main>.
Low contrast colour pair in CSS (2.8:1) src/ElectronNET.Samples.AuthMiddleware/Components/Layout/ReconnectModal.razor.css:91— `#components-reconnect-modal button` sets color: white on background-color: #6b9ed2 — 2.8:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them.
Low contrast colour pair in CSS (4.2:1) docs/md-styles.css:5617— `a.list-group-item-success:focus, a.list-group-item-success:hover, button.list-group-item-success:focus, button.list-group-item-success:hover` sets color: #3c763d on background-color: #d0e9c6 — 4.2:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them.
Low contrast colour pair in CSS (4.1:1) docs/md-styles.css:5641— `a.list-group-item-info:focus, a.list-group-item-info:hover, button.list-group-item-info:focus, button.list-group-item-info:hover` sets color: #31708f on background-color: #c4e3f3 — 4.1:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them.
Low contrast colour pair in CSS (4.3:1) docs/md-styles.css:5665— `a.list-group-item-warning:focus, a.list-group-item-warning:hover, button.list-group-item-warning:focus, button.list-group-item-warning:hover` sets color: #8a6d3b on background-color: #faf2cc — 4.3:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them.
Low contrast colour pair in CSS (3.9:1) docs/md-styles.css:5689— `a.list-group-item-danger:focus, a.list-group-item-danger:hover, button.list-group-item-danger:focus, button.list-group-item-danger:hover` sets color: #a94442 on background-color: #ebcccc — 3.9:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them.
Low contrast colour pair in CSS (4.0:1) docs/md-styles.css:7369— `.alert-info > h5` sets color: #1976d2 on background-color: #e3f2fd — 4.0:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them.
Low contrast colour pair in CSS (2.4:1) docs/md-styles.css:7375— `.alert-warning > h5` sets color: #f57f17 on background-color: #fff3e0 — 2.4:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them.
Low contrast colour pair in CSS (4.4:1) docs/md-styles.css:7381— `.alert-danger > h5` sets color: #d32f2f on background-color: #ffebee — 4.4:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them.
AX2 · Stateful singletons· Process-global static state · ×1
Process-global static state: Notification src/ElectronNET.API/API/Notification.cs:12— `Notification` keeps mutable `static` state — one slot for the whole process, shared by every thread that reaches the type however its instances are created — and mutates it outside any lock (_notificationOptions; e.g. `_notificationOptions` at line 112). Concurrent callers lose updates, and a collection that is not built for concurrent writers can corrupt.
main.startSocketApiBridge (cyclomatic 36) REDACTED:295— main.startSocketApiBridge has cyclomatic complexity 36 (threshold 15). Most of this is not in the body itself: 1 of the 36 points is its own statement and the rest belongs to 6 function literals inside it that branch (lines 344, 313, 327, …). 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.
tray.default (cyclomatic 25) src/ElectronNET.Host/api/tray.ts:10— tray.default has cyclomatic complexity 25 (threshold 15). Most of this is not in the body itself: 1 of the 25 points is its own statement and the rest belongs to 20 function literals inside it that branch (lines 162, 85, 12, …). 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.
browserWindows.default::createWindow (cyclomatic 24) src/ElectronNET.Host/api/browserWindows.ts:238— browserWindows.default::createWindow has cyclomatic complexity 24 (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.
JsonToBoxedPrimitivesConverter.ReadValue (cyclomatic 21) src/ElectronNET.API/Serialization/JsonToBoxedPrimitivesConverter.cs:15— JsonToBoxedPrimitivesConverter.ReadValue has cyclomatic complexity 21 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
LifetimeServiceBase.TransitionState (cyclomatic 16) src/ElectronNET.API/Runtime/Services/LifetimeServiceBase.cs:79— LifetimeServiceBase.TransitionState has cyclomatic complexity 16 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
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.
TodoComment src/ElectronNET.API/API/Tray.cs:163— // TODO: Implement macOS Events — 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.
main.startSocketApiBridge (cognitive 34) REDACTED:295— main.startSocketApiBridge has cognitive complexity 34 (threshold 15). Drivers by points: if/else 28, boolean chains 4, error handling 2. None of this is in the body itself: all 34 points belong to 6 function literals inside it that branch (lines 344, 313, 327, …). 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.
JsonToBoxedPrimitivesConverter.ReadValue (cognitive 31) src/ElectronNET.API/Serialization/JsonToBoxedPrimitivesConverter.cs:15— JsonToBoxedPrimitivesConverter.ReadValue has cognitive complexity 31 (threshold 15). The drivers above price the dispatch low by construction — a dispatch is charged once however many cases it lists, while each branch inside an arm is charged in full — so most of this count is what the case bodies hold, and the arms are where it can be reduced. To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident.
tray.default (cognitive 28) src/ElectronNET.Host/api/tray.ts:10— tray.default has cognitive complexity 28 (threshold 15). Drivers by points: if/else 23 (25 pts), boolean chains 3 (nesting depth added 2). None of this is in the body itself: all 28 points belong to 20 function literals inside it that branch (lines 162, 85, 131, …). 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.
browserWindows.default::createWindow (cognitive 27) src/ElectronNET.Host/api/browserWindows.ts:238— browserWindows.default::createWindow has cognitive complexity 27 (threshold 15). Drivers by points: if/else 14 (18 pts), boolean chains 6, error handling 1 (3 pts) (nesting depth added 6). 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.
webContents.default (cognitive 24) src/ElectronNET.Host/api/webContents.ts:9— webContents.default has cognitive complexity 24 (threshold 15). Drivers by points: if/else 14 (18 pts), error handling 1 (2 pts), loops 1 (2 pts), boolean chains 1, ternaries 1 (nesting depth added 6). None of this is in the body itself: all 24 points belong to 7 function items inside it that branch (a function literal at line 503, a function literal at line 208, a function literal at line 151, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
App.BeforeQuit.add (cognitive 21) src/ElectronNET.API/API/App.cs:71— App.BeforeQuit.add has cognitive complexity 21 (threshold 15). Most of this is not in the body itself: 1 of the 21 points is its own statement and the rest belongs to one function literal inside it that branches (line 75). The decisions are inside the literal, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literal's work into a named function or method at the enclosing scope and have the literal call it, then reduce whichever part then reads as the largest.
SemVersion.CompareTo (cognitive 17) nuke/SemVersion.cs:205— SemVersion.CompareTo 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.
StartupManager.CollectProcessData (cognitive 16) src/ElectronNET.API/Runtime/StartupManager.cs:78— StartupManager.CollectProcessData 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.
ReleaseNotesParser.ParseComplexFormat (cognitive 16) nuke/ReleaseNotesParser.cs:61— ReleaseNotesParser.ParseComplexFormat 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.
FunctionTooLong: autoUpdater.default src/ElectronNET.Host/api/autoUpdater.ts:16— FunctionTooLong — default runs 109 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 9 over it, 1.09× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FileTooLong: api/browserWindows.ts src/ElectronNET.Host/api/browserWindows.ts— FileTooLong — 531 significant lines (blank, comment-only and punctuation-only lines excluded), about 98% of them inside a single declaration: proxyToCredentialsMap (15-968). The bar is 500 significant lines; this is 31 over it, 1.06× 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.
D30 · Dependency Vulnerabilities· Medium vulnerability · ×1
D4 · Code Duplication· Edited copy of a member (28 corresponding lines) · ×1
Edited copy of a member (28 corresponding lines) REDACTED:360— REDACTED:360-387 | REDACTED:390-418 — These two members are one piece of code written twice and then edited apart: 28 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· Edited copy of a member (19 corresponding lines) · ×1
Edited copy of a member (19 corresponding lines) src/ElectronNET.API/API/ApiBase.cs:147— src/ElectronNET.API/API/ApiBase.cs:147-165 | src/ElectronNET.API/API/ApiBase.cs:184-202 — These two members are one piece of code written twice and then edited apart: 19 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· Edited copy of a member (27 corresponding lines) · ×1
Edited copy of a member (27 corresponding lines) src/ElectronNET.API/Runtime/Helpers/LaunchOrderDetector.cs:11— src/ElectronNET.API/Runtime/Helpers/LaunchOrderDetector.cs:11-37 | src/ElectronNET.API/Runtime/Helpers/UnpackagedDetector.cs:12-43 — These two members are one piece of code written twice and then edited apart: 27 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· Edited copy of a member (32 corresponding lines) · ×1
Edited copy of a member (32 corresponding lines) src/ElectronNET.API/Common/ProcessRunner.cs:547— src/ElectronNET.API/Common/ProcessRunner.cs:547-578 | src/ElectronNET.API/Common/ProcessRunner.cs:581-613 — These two members are one piece of code written twice and then edited apart: 32 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· Edited copy of a member (13 corresponding lines) · ×1
Edited copy of a member (13 corresponding lines) src/ElectronNET.API/API/App.cs:1047— src/ElectronNET.API/API/App.cs:1047-1059 | src/ElectronNET.API/API/Dock.cs:53-65 — These two members are one piece of code written twice and then edited apart: 13 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· Edited copy of a member (11 corresponding lines) · ×1
Edited copy of a member (11 corresponding lines) src/ElectronNET.API/API/ApiBase.cs:93— src/ElectronNET.API/API/ApiBase.cs:93-103 | src/ElectronNET.API/API/ApiBase.cs:106-116 — These two members are one piece of code written twice and then edited apart: 11 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· Edited copy of a member (7 corresponding lines) · ×1
Edited copy of a member (7 corresponding lines) src/ElectronNET.API/Bridge/Events.cs:48— src/ElectronNET.API/Bridge/Events.cs:48-54 | src/ElectronNET.API/Bridge/Events.cs:64-70 — These two members are one piece of code written twice and then edited apart: 7 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· Edited copy of a member (6 corresponding lines) · ×1
Edited copy of a member (6 corresponding lines) src/ElectronNET.API/Bridge/Events.cs:77— src/ElectronNET.API/Bridge/Events.cs:77-82 | src/ElectronNET.API/Bridge/Events.cs:92-97 — These two members are one piece of code written twice and then edited apart: 6 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· Edited copy of a member (17 corresponding lines) · ×1
Edited copy of a member (17 corresponding lines) src/ElectronNET.API/API/Extensions/MenuItemExtensions.cs:11— src/ElectronNET.API/API/Extensions/MenuItemExtensions.cs:11-27 | src/ElectronNET.API/API/Extensions/MenuItemExtensions.cs:53-69 — These two members are one piece of code written twice and then edited apart: 17 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.
Duplicated block (18 lines × 2) src/ElectronNET.API/API/App.cs:91— src/ElectronNET.API/API/App.cs:91-108 | src/ElectronNET.API/API/App.cs:150-167 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (20 lines × 2) src/ElectronNET.API/API/Entities/LoginItemSettingsOptions.cs:13— src/ElectronNET.API/API/Entities/LoginItemSettingsOptions.cs:13-32 | src/ElectronNET.API/API/Entities/LoginSettings.cs:28-48 — 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `src/ElectronNET.API/API/Entities/LoginSettings.cs:22` calls `SupportedOSPlatform` and `src/ElectronNET.API/API/Entities/LoginItemSettingsOptions.cs:9` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (13 lines × 2) src/ElectronNET.API/API/ApiBase.cs:169— src/ElectronNET.API/API/ApiBase.cs:169-181 | src/ElectronNET.API/API/ApiBase.cs:206-218 — 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/ElectronNET.API/API/ApiBase.cs:148— src/ElectronNET.API/API/ApiBase.cs:148-157 | src/ElectronNET.API/API/ApiBase.cs:185-194 — 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/ElectronNET.API/API/ApiBase.cs:148` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (7–9 lines × 2) REDACTED:374— REDACTED:374-382 | REDACTED:408-414 — 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 `REDACTED:374` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (6 lines × 2) src/ElectronNET.API/Bridge/Events.cs:49— src/ElectronNET.API/Bridge/Events.cs:49-54 | src/ElectronNET.API/Bridge/Events.cs:65-70 — 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 (7 lines × 2) src/ElectronNET.API/Runtime/StartupManager.cs:84— src/ElectronNET.API/Runtime/StartupManager.cs:84-91 | src/ElectronNET.API/Runtime/StartupManager.cs:110-116 — 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/ElectronNET.API/Runtime/StartupManager.cs:84` 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 (5 lines × 2) src/ElectronNET.API/Bridge/Events.cs:78— src/ElectronNET.API/Bridge/Events.cs:78-82 | src/ElectronNET.API/Bridge/Events.cs:93-97 — 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.
Off the main sequence: ElectronNET.API(net6.0) REDACTED:1— ElectronNET.API(net6.0): abstractness 0.05, instability 0.00, distance 0.95 — zone of pain — concrete and depended on by 2 project(s), so it's rigid to change.
Duplicated block (24 lines × 2 locations) REDACTED:437— REDACTED:437 · REDACTED:469 — 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.
Duplicated block (18 lines × 2 locations) src/ElectronNET.Samples.ElectronHostHook/ElectronHostHook/connector.ts:3— src/ElectronNET.Samples.ElectronHostHook/ElectronHostHook/connector.ts:3 · src/ElectronNET.WebApp/ElectronHostHook/connector.ts:3 — the 2 copies are spread across 2 directories, so the shared home is a decision rather than an obvious spot: check first whether one of them already owns this behaviour, and otherwise put the extracted module somewhere all of the sites already reach rather than making one of them depend on another.
Duplicated block (16 lines × 3 locations) src/ElectronNET.Host/ElectronHostHook/connector.ts:6— src/ElectronNET.Host/ElectronHostHook/connector.ts:6 · src/ElectronNET.Samples.ElectronHostHook/ElectronHostHook/connector.ts:4 · src/ElectronNET.WebApp/ElectronHostHook/connector.ts:5 — the 3 copies are spread across 3 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.
Duplicated block (14 lines × 2 locations) src/ElectronNET.Host/api/autoUpdater.ts:152— src/ElectronNET.Host/api/autoUpdater.ts:152 · src/ElectronNET.Host/api/autoUpdater.ts:170 — 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.
Duplicated block (14 lines × 3 locations) src/ElectronNET.Host/api/browserWindows.ts:735— src/ElectronNET.Host/api/browserWindows.ts:735 · src/ElectronNET.Host/api/dock.ts:65 · src/ElectronNET.Host/api/menu.ts:76 — the 3 copies are spread across 3 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.
Duplicated block (11 lines × 2 locations) src/ElectronNET.Host/api/tray.ts:14— src/ElectronNET.Host/api/tray.ts:14 · src/ElectronNET.Host/api/tray.ts:26 — 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.
Duplicated block (9 lines × 2 locations) src/ElectronNET.Host/api/app.ts:319— src/ElectronNET.Host/api/app.ts:319 · src/ElectronNET.Host/api/app.ts:329 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (7 lines × 2 locations) src/ElectronNET.Host/api/clipboard.ts:1— src/ElectronNET.Host/api/clipboard.ts:1 · src/ElectronNET.Host/api/dock.ts:1 — the 2 copies are spread across 2 files, 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.
Duplicated block (6 lines × 2 locations) src/ElectronNET.Host/api/ipc.ts:44— src/ElectronNET.Host/api/ipc.ts:44 · src/ElectronNET.Host/api/webContents.ts:509 — 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.
Complex function (anonymous) (cyclomatic 25, cognitive 24) REDACTED:344— (anonymous) has cyclomatic complexity 25 and cognitive complexity 24; 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.
Complex function createWindow (cyclomatic 24, cognitive 27) src/ElectronNET.Host/api/browserWindows.ts:238— createWindow has cyclomatic complexity 24 and cognitive complexity 27; 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/ElectronNET.Host/api/browserWindows.ts · ×1
src/ElectronNET.Host/api/browserWindows.ts: 766 lines of code src/ElectronNET.Host/api/browserWindows.ts:1— src/ElectronNET.Host/api/browserWindows.ts has 766 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/ElectronNET.Host/api/webContents.ts · ×1
src/ElectronNET.Host/api/webContents.ts: 623 lines of code src/ElectronNET.Host/api/webContents.ts:1— src/ElectronNET.Host/api/webContents.ts has 623 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
REDACTED: 427 lines of code REDACTED:1— REDACTED has 427 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
Test Coverage — 0% of 29 production file(s) reachable from 0 test file(s) via the import graph — 'production' here is the RESIDUE: every source file left once tests, tooling, generated output, config, declarations and declaration-only modules, fixture corpora, type fixtures, behaviour-free data modules, re-export barrels, registration/constant data modules and service workers are set aside, so the percentage is taken over a smaller denominator than the workspace's file count
No lint 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.
Unused dependency 'dasherize' — Declared in src/ElectronNET.Host/package.json but never imported anywhere in that package or its workspace members — no static import reaches it. Usually that is dead weight and attack surface, but two shapes are indistinguishable from source and are NOT dead: an optional or native peer that another dependency loads dynamically at runtime, and a package a build, docs or test step installs and invokes separately. Confirm which of the three this is before removing it.
Unused dependency 'archiver-utils' — Declared in src/ElectronNET.WebApp/ElectronHostHook/package.json but never imported anywhere in that package or its workspace members — no static import reaches it. Usually that is dead weight and attack surface, but two shapes are indistinguishable from source and are NOT dead: an optional or native peer that another dependency loads dynamically at runtime, and a package a build, docs or test step installs and invokes separately. Confirm which of the three this is before removing it.
Secure cookie flags not detected src/ElectronNET.AspNet/Middleware/ElectronAuthenticationMiddleware.cs:72— A cookie (`Cookies.Append`) carries who is signed in, and it is set without Secure. Without Secure the browser also sends it over plain http://, where anyone on the same network can read it. (−1.5 on this card.)
SC1 · Supply-chain hygiene· NuGet dependencies are not locked · ×1
NuGet dependencies are not locked — No packages.lock.json and no central package management — restores aren't reproducible or pinned (SSDF PW.4.4). Enable <RestorePackagesWithLockFile>true</RestorePackagesWithLockFile> (commit the lockfile) or adopt Directory.Packages.props. Advisory — never scored.
SC1 · Supply-chain hygiene· JavaScript dependencies are not locked · ×1
JavaScript dependencies are not locked src/ElectronNET.Samples.ElectronHostHook/ElectronHostHook/package.json:6— src/ElectronNET.Samples.ElectronHostHook/ElectronHostHook/package.json declares dependencies that no committed lockfile resolves — there is no REDACTED / yarn.lock / pnpm-lock.yaml / bun.lock beside it, and no locked workspace above it names it — so its installs aren't reproducible (SSDF PW.4.4). Commit its package manager's lockfile (or add it to the locked workspace) and install from it (`npm ci`, `yarn --immutable`, `pnpm i --frozen-lockfile` or `bun i --frozen-lockfile`). Advisory — never scored.
async void method: UpdateReply src/ElectronNET.WebApp/Controllers/WindowsController.cs:53— `async void` can't be awaited and its exceptions crash the process instead of propagating. Return `Task` — or, where the delegate contract requires void (timer/event/callback registrations), make this a thin void shim that awaits a Task-returning inner method inside try/catch so exceptions are contained.
Sync-over-async (deadlock risk) src/ElectronNET.API/Bridge/SocketIOConnection.cs:65— 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.
X2 · Cancellation propagation· Async local function without CancellationToken · ×1
Async local function without CancellationToken: ElectronAppReady src/ElectronNET.Templates/templates/blazor/Program.cs:37— Neither takes a CancellationToken nor reads the one of the function it sits in, while it calls something that takes one — this work can't be stopped early once started. Take the token, or pass on the enclosing one.
Async method drops its ambient CancellationToken: InvokeAsync src/ElectronNET.AspNet/Middleware/ElectronAuthenticationMiddleware.cs:37— Its signature is fixed by the framework, and the token it carries (`context.RequestAborted`) reaches none of the calls here that take one — so an aborted request or a stopping host still waits for that work. Pass `context.RequestAborted` to them.
Orphaned file src/ElectronNET.API/API/Session.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/ElectronNET.API/API/ApiBase.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/ElectronNET.API/API/AutoUpdater.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/ElectronNET.API/API/Tray.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/ElectronNET.API/API/Entities/WebPreferences.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/ElectronNET.API/API/IpcMain.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/ElectronNET.API/API/Dialog.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/ElectronNET.API/API/Dock.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/ElectronNET.API/API/Entities/NotificationOptions.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/ElectronNET.API/API/Clipboard.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/ElectronNET.API/API/NativeTheme.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/ElectronNET.API/API/Entities/MenuRole.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/ElectronNET.API/API/Shell.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/ElectronNET.API/API/Entities/InputEvent.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/ElectronNET.WebApp/Controllers/MenusController.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/ElectronNET.API/API/Screen.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/ElectronNET.API/API/Entities/MenuItem.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/ElectronNET.API/API/Electron.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/ElectronNET.API/API/Notification.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/ElectronNET.API/Runtime/Services/LifetimeServiceBase.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/ElectronNET.API/API/CommandLine.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/ElectronNET.API/API/Menu.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/ElectronNET.API/Common/RunnerParams.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/ElectronNET.API/API/Entities/MessageBoxOptions.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.
+ 26 more in this group — see findings.md.
P10 · Library API & versioning· Public type used only inside its own library · ×20
Public type used only inside its own library src/ElectronNET.API/API/Electron.cs:6— `ElectronNET.API.Electron` (src/ElectronNET.API/API/Electron.cs:6) is public, and the library's own code uses it, but no other project in this repository uses it (read: `ElectronNET(net6.0)`, `ElectronNET.AspNet(net6.0)`) and no public member of the library exposes it. Consumers outside this repository are not visible here; if they rely on it, it is API and should be documented as such.
Public type used only inside its own library src/ElectronNET.API/API/Electron.cs:6— `ElectronNET.API.Electron` (src/ElectronNET.API/API/Electron.cs:6) is public, and the library's own code uses it, but no other project in this repository uses it (read: `ElectronNET(net8.0)`, `ElectronNET.AspNet(net8.0)`) and no public member of the library exposes it. Consumers outside this repository are not visible here; if they rely on it, it is API and should be documented as such.
Public type used only inside its own library src/ElectronNET.API/Common/ProcessRunner.cs:22— `ElectronNET.Common.ProcessRunner` (src/ElectronNET.API/Common/ProcessRunner.cs:22) is public, and the library's own code uses it, but no other project in this repository uses it (read: `ElectronNET(net6.0)`, `ElectronNET.AspNet(net6.0)`) and no public member of the library exposes it. Consumers outside this repository are not visible here; if they rely on it, it is API and should be documented as such.
Public type used only inside its own library src/ElectronNET.API/Common/ProcessRunner.cs:22— `ElectronNET.Common.ProcessRunner` (src/ElectronNET.API/Common/ProcessRunner.cs:22) is public, and the library's own code uses it, but no other project in this repository uses it (read: `ElectronNET(net8.0)`, `ElectronNET.AspNet(net8.0)`) and no public member of the library exposes it. Consumers outside this repository are not visible here; if they rely on it, it is API and should be documented as such.
Public type used only inside its own library src/ElectronNET.API/Common/ProcessRunner.cs:22— `ElectronNET.Common.ProcessRunner` (src/ElectronNET.API/Common/ProcessRunner.cs:22) is public, and the library's own code uses it, but no other project in this repository uses it (read: `ElectronNET(net10.0)`, `ElectronNET.AspNet(net10.0)`, `ElectronNET.ConsoleApp`, `ElectronNET.IntegrationTests`, `ElectronNET.Samples.AuthMiddleware`, `ElectronNET.Samples.ElectronHostHook`, `ElectronNET.WebApp`) and no public member of the library exposes it. Consumers outside this repository are not visible here; if they rely on it, it is API and should be documented as such.
Public type used only inside its own library src/ElectronNET.API/Converter/ModifierTypeListConverter.cs:12— `ElectronNET.Converter.ModifierTypeListConverter` (src/ElectronNET.API/Converter/ModifierTypeListConverter.cs:12) is public, and the library's own code uses it, but no other project in this repository uses it (read: `ElectronNET(net6.0)`, `ElectronNET.AspNet(net6.0)`) and no public member of the library exposes it. Consumers outside this repository are not visible here; if they rely on it, it is API and should be documented as such.
Public type used only inside its own library src/ElectronNET.API/Converter/ModifierTypeListConverter.cs:12— `ElectronNET.Converter.ModifierTypeListConverter` (src/ElectronNET.API/Converter/ModifierTypeListConverter.cs:12) is public, and the library's own code uses it, but no other project in this repository uses it (read: `ElectronNET(net8.0)`, `ElectronNET.AspNet(net8.0)`) and no public member of the library exposes it. Consumers outside this repository are not visible here; if they rely on it, it is API and should be documented as such.
Public type used only inside its own library src/ElectronNET.API/Converter/ModifierTypeListConverter.cs:12— `ElectronNET.Converter.ModifierTypeListConverter` (src/ElectronNET.API/Converter/ModifierTypeListConverter.cs:12) is public, and the library's own code uses it, but no other project in this repository uses it (read: `ElectronNET(net10.0)`, `ElectronNET.AspNet(net10.0)`, `ElectronNET.ConsoleApp`, `ElectronNET.IntegrationTests`, `ElectronNET.Samples.AuthMiddleware`, `ElectronNET.Samples.ElectronHostHook`, `ElectronNET.WebApp`) and no public member of the library exposes it. Consumers outside this repository are not visible here; if they rely on it, it is API and should be documented as such.
Public type used only inside its own library src/ElectronNET.API/Converter/PageSizeConverter.cs:9— `ElectronNET.Converter.PageSizeConverter` (src/ElectronNET.API/Converter/PageSizeConverter.cs:9) is public, and the library's own code uses it, but no other project in this repository uses it (read: `ElectronNET(net6.0)`, `ElectronNET.AspNet(net6.0)`) and no public member of the library exposes it. Consumers outside this repository are not visible here; if they rely on it, it is API and should be documented as such.
Public type used only inside its own library src/ElectronNET.API/Converter/PageSizeConverter.cs:9— `ElectronNET.Converter.PageSizeConverter` (src/ElectronNET.API/Converter/PageSizeConverter.cs:9) is public, and the library's own code uses it, but no other project in this repository uses it (read: `ElectronNET(net8.0)`, `ElectronNET.AspNet(net8.0)`) and no public member of the library exposes it. Consumers outside this repository are not visible here; if they rely on it, it is API and should be documented as such.
Public type used only inside its own library src/ElectronNET.API/Converter/PageSizeConverter.cs:9— `ElectronNET.Converter.PageSizeConverter` (src/ElectronNET.API/Converter/PageSizeConverter.cs:9) is public, and the library's own code uses it, but no other project in this repository uses it (read: `ElectronNET(net10.0)`, `ElectronNET.AspNet(net10.0)`, `ElectronNET.ConsoleApp`, `ElectronNET.IntegrationTests`, `ElectronNET.Samples.AuthMiddleware`, `ElectronNET.Samples.ElectronHostHook`, `ElectronNET.WebApp`) and no public member of the library exposes it. Consumers outside this repository are not visible here; if they rely on it, it is API and should be documented as such.
Public type used only inside its own library src/ElectronNET.API/Converter/ReleaseNotesConverter.cs:19— `ElectronNET.API.Converter.ReleaseNotesConverter` (src/ElectronNET.API/Converter/ReleaseNotesConverter.cs:19) is public, and the library's own code uses it, but no other project in this repository uses it (read: `ElectronNET(net6.0)`, `ElectronNET.AspNet(net6.0)`) and no public member of the library exposes it. Consumers outside this repository are not visible here; if they rely on it, it is API and should be documented as such.
Public type used only inside its own library src/ElectronNET.API/Converter/ReleaseNotesConverter.cs:19— `ElectronNET.API.Converter.ReleaseNotesConverter` (src/ElectronNET.API/Converter/ReleaseNotesConverter.cs:19) is public, and the library's own code uses it, but no other project in this repository uses it (read: `ElectronNET(net8.0)`, `ElectronNET.AspNet(net8.0)`) and no public member of the library exposes it. Consumers outside this repository are not visible here; if they rely on it, it is API and should be documented as such.
Public type used only inside its own library src/ElectronNET.API/Converter/ReleaseNotesConverter.cs:19— `ElectronNET.API.Converter.ReleaseNotesConverter` (src/ElectronNET.API/Converter/ReleaseNotesConverter.cs:19) is public, and the library's own code uses it, but no other project in this repository uses it (read: `ElectronNET(net10.0)`, `ElectronNET.AspNet(net10.0)`, `ElectronNET.ConsoleApp`, `ElectronNET.IntegrationTests`, `ElectronNET.Samples.AuthMiddleware`, `ElectronNET.Samples.ElectronHostHook`, `ElectronNET.WebApp`) and no public member of the library exposes it. Consumers outside this repository are not visible here; if they rely on it, it is API and should be documented as such.
Public type used only inside its own library src/ElectronNET.API/Converter/TitleBarOverlayConverter.cs:9— `ElectronNET.Converter.TitleBarOverlayConverter` (src/ElectronNET.API/Converter/TitleBarOverlayConverter.cs:9) is public, and the library's own code uses it, but no other project in this repository uses it (read: `ElectronNET(net6.0)`, `ElectronNET.AspNet(net6.0)`) and no public member of the library exposes it. Consumers outside this repository are not visible here; if they rely on it, it is API and should be documented as such.
Public type used only inside its own library src/ElectronNET.API/Converter/TitleBarOverlayConverter.cs:9— `ElectronNET.Converter.TitleBarOverlayConverter` (src/ElectronNET.API/Converter/TitleBarOverlayConverter.cs:9) is public, and the library's own code uses it, but no other project in this repository uses it (read: `ElectronNET(net8.0)`, `ElectronNET.AspNet(net8.0)`) and no public member of the library exposes it. Consumers outside this repository are not visible here; if they rely on it, it is API and should be documented as such.
Public type used only inside its own library src/ElectronNET.API/Converter/TitleBarOverlayConverter.cs:9— `ElectronNET.Converter.TitleBarOverlayConverter` (src/ElectronNET.API/Converter/TitleBarOverlayConverter.cs:9) is public, and the library's own code uses it, but no other project in this repository uses it (read: `ElectronNET(net10.0)`, `ElectronNET.AspNet(net10.0)`, `ElectronNET.ConsoleApp`, `ElectronNET.IntegrationTests`, `ElectronNET.Samples.AuthMiddleware`, `ElectronNET.Samples.ElectronHostHook`, `ElectronNET.WebApp`) and no public member of the library exposes it. Consumers outside this repository are not visible here; if they rely on it, it is API and should be documented as such.
Public type used only inside its own library src/ElectronNET.API/Serialization/JsonToBoxedPrimitivesConverter.cs:8— `ElectronNET.Serialization.JsonToBoxedPrimitivesConverter` (src/ElectronNET.API/Serialization/JsonToBoxedPrimitivesConverter.cs:8) is public, and the library's own code uses it, but no other project in this repository uses it (read: `ElectronNET(net6.0)`, `ElectronNET.AspNet(net6.0)`) and no public member of the library exposes it. Consumers outside this repository are not visible here; if they rely on it, it is API and should be documented as such.
Public type used only inside its own library src/ElectronNET.API/Serialization/JsonToBoxedPrimitivesConverter.cs:8— `ElectronNET.Serialization.JsonToBoxedPrimitivesConverter` (src/ElectronNET.API/Serialization/JsonToBoxedPrimitivesConverter.cs:8) is public, and the library's own code uses it, but no other project in this repository uses it (read: `ElectronNET(net8.0)`, `ElectronNET.AspNet(net8.0)`) and no public member of the library exposes it. Consumers outside this repository are not visible here; if they rely on it, it is API and should be documented as such.
Public type used only inside its own library src/ElectronNET.API/Serialization/JsonToBoxedPrimitivesConverter.cs:8— `ElectronNET.Serialization.JsonToBoxedPrimitivesConverter` (src/ElectronNET.API/Serialization/JsonToBoxedPrimitivesConverter.cs:8) is public, and the library's own code uses it, but no other project in this repository uses it (read: `ElectronNET(net10.0)`, `ElectronNET.AspNet(net10.0)`, `ElectronNET.ConsoleApp`, `ElectronNET.IntegrationTests`, `ElectronNET.Samples.AuthMiddleware`, `ElectronNET.Samples.ElectronHostHook`, `ElectronNET.WebApp`) and no public member of the library exposes it. Consumers outside this repository are not visible here; if they rely on it, it is API and should be documented as such.
Duplicated predicate REDACTED:45— `!obj || !obj.hasOwnProperty(childNames[i])` appears character-identically in 2 files — REDACTED, REDACTED. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate REDACTED:294— `app.commandLine.hasSwitch("clear-cache") && app.commandLine.getSwitchValue("clear-cache")` appears character-identically in 2 files — REDACTED, src/ElectronNET.Host/api/browserWindows.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 REDACTED:239— `app.commandLine.hasSwitch("watch") && app["mainWindowURL"] === loadUrl && app["mainWindow"] && !app["mainWindow"].isDestroyed()` appears character-identically in 2 files — REDACTED, src/ElectronNET.Host/api/browserWindows.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 REDACTED:300— `app["mainWindowURL"] == undefined || app["mainWindowURL"] == ""` appears character-identically in 2 files — REDACTED, src/ElectronNET.Host/api/browserWindows.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 REDACTED:581— `item.submenu && item.submenu.items.length > 0` appears character-identically in 8 files — REDACTED, src/ElectronNET.Host/api/browserWindows.ts, src/ElectronNET.Host/api/dock.js, src/ElectronNET.Host/api/dock.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 REDACTED:24— `options.proxy && options.proxyCredentials` appears character-identically in 4 files — REDACTED, REDACTED, REDACTED, src/ElectronNET.Host/api/browserWindows.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 REDACTED:217— `options.webPreferences && !("nodeIntegration" in options.webPreferences)` appears character-identically in 2 files — REDACTED, src/ElectronNET.Host/api/browserWindows.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/ElectronNET.Host/api/app.js:11— `process.platform !== "darwin" && isQuitWindowAllClosed` appears character-identically in 2 files — src/ElectronNET.Host/api/app.js, src/ElectronNET.Host/api/app.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 REDACTED:49— `proxy in proxyToCredentialsMap && proxyToCredentialsMap[proxy].split(":").length === 2` appears character-identically in 2 files — REDACTED, src/ElectronNET.Host/api/browserWindows.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 REDACTED:277— `url.hostname === "localhost" || url.hostname === "127.0.0.1" || url.hostname === "::1"` appears character-identically in 2 files — REDACTED, src/ElectronNET.Host/api/browserWindows.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 REDACTED:538— `win && typeof win.getRepresentedFilename === "function"` appears character-identically in 2 files — REDACTED, src/ElectronNET.Host/api/browserWindows.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 REDACTED:526— `win && typeof win.setRepresentedFilename === "function"` appears character-identically in 2 files — REDACTED, src/ElectronNET.Host/api/browserWindows.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 REDACTED:728— `windowId === null || !runtimeWindowIds.has(windowId)` appears character-identically in 2 files — REDACTED, src/ElectronNET.Host/api/browserWindows.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.
Commented-out code src/ElectronNET.API/API/BrowserWindow.cs:734— 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/ElectronNET.API/API/BrowserWindow.cs:751— 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/ElectronNET.API/API/WebRequest.cs:40— 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/ElectronNET.API/Runtime/Services/ElectronProcess/ElectronProcessPassive.cs:49— A line of code has been commented out rather than removed — dead weight that rots and confuses. Delete it (version control remembers).
Commented-out code src/ElectronNET.Build/ReplaceMsBuildPropertiesTask.cs:25— 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/ElectronNET.Build/ReplaceMsBuildPropertiesTask.cs:30— 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/ElectronNET.Build/ReplaceMsBuildPropertiesTask.cs:32— 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/ElectronNET.Build/ReplaceMsBuildPropertiesTask.cs:33— 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/ElectronNET.Build/ReplaceMsBuildPropertiesTask.cs:36— 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/ElectronNET.Build/ReplaceMsBuildPropertiesTask.cs:39— 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/ElectronNET.ConsoleApp/Program.cs:36— 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/ElectronNET.WebApp/Program.cs:28— A line of code has been commented out rather than removed — dead weight that rots and confuses. Delete it (version control remembers).
P2 · Observability· Console output used as the logging channel · ×8
Console output used as the logging channel src/ElectronNET.WebApp/Controllers/HomeController.cs:15— `src/ElectronNET.WebApp/Controllers/HomeController.cs` reports through `Console.Write…` at line 15 although other files in its project log through a logger. Console lines carry no level, category or structured properties and never reach the log pipeline or its exporters.
Console output used as the logging channel src/ElectronNET.WebApp/Controllers/HomeController.cs:17— `src/ElectronNET.WebApp/Controllers/HomeController.cs` reports through `Console.Write…` at line 17 although other files in its project log through a logger. Console lines carry no level, category or structured properties and never reach the log pipeline or its exporters.
Console output used as the logging channel src/ElectronNET.WebApp/Controllers/HomeController.cs:19— `src/ElectronNET.WebApp/Controllers/HomeController.cs` reports through `Console.Write…` at line 19 although other files in its project log through a logger. Console lines carry no level, category or structured properties and never reach the log pipeline or its exporters.
Console output used as the logging channel src/ElectronNET.WebApp/Controllers/HomeController.cs:21— `src/ElectronNET.WebApp/Controllers/HomeController.cs` reports through `Console.Write…` at line 21 although other files in its project log through a logger. Console lines carry no level, category or structured properties and never reach the log pipeline or its exporters.
Console output used as the logging channel src/ElectronNET.WebApp/Controllers/HomeController.cs:23— `src/ElectronNET.WebApp/Controllers/HomeController.cs` reports through `Console.Write…` at line 23 although other files in its project log through a logger. Console lines carry no level, category or structured properties and never reach the log pipeline or its exporters.
Console output used as the logging channel src/ElectronNET.WebApp/Controllers/HomeController.cs:25— `src/ElectronNET.WebApp/Controllers/HomeController.cs` reports through `Console.Write…` at line 25 although other files in its project log through a logger. Console lines carry no level, category or structured properties and never reach the log pipeline or its exporters.
Console output used as the logging channel src/ElectronNET.AspNet/Runtime/Controllers/RuntimeControllerAspNetBase.cs:137— `src/ElectronNET.AspNet/Runtime/Controllers/RuntimeControllerAspNetBase.cs` reports through `Console.Write…` at line 137 although other files in its project log through a logger. Console lines carry no level, category or structured properties and never reach the log pipeline or its exporters.
Console output used as the logging channel src/ElectronNET.AspNet/Runtime/Controllers/RuntimeControllerAspNetBase.cs:147— `src/ElectronNET.AspNet/Runtime/Controllers/RuntimeControllerAspNetBase.cs` reports through `Console.Write…` at line 147 although other files in its project log through a logger. Console lines carry no level, category or structured properties and never reach the log pipeline or its exporters.
No security response headers detected — None of the 11 security response headers the OWASP Secure Headers Project recommends (Content-Security-Policy, Strict-Transport-Security, X-Content-Type-Options, X-Frame-Options, …) is configured — defense in depth, even when a reverse proxy could set them. (−2.0 on this card.)
No security response headers detected src/ElectronNET.Samples.AuthMiddleware/Program.cs:9— This web host's pipeline is composed here and adds no security response header (Content-Security-Policy, Strict-Transport-Security, X-Content-Type-Options, a frame policy) to what it serves.
No security response headers detected src/ElectronNET.Samples.ElectronHostHook/Program.cs:11— This web host's pipeline is composed here and adds no security response header (Content-Security-Policy, Strict-Transport-Security, X-Content-Type-Options, a frame policy) to what it serves.
No security response headers detected src/ElectronNET.WebApp/Program.cs:20— This web host's pipeline is composed here and adds no security response header (Content-Security-Policy, Strict-Transport-Security, X-Content-Type-Options, a frame policy) to what it serves.
Disabled test src/ElectronNET.IntegrationTests/Tests/CookiesTests.cs:13— A test is skipped ("Cookie set/get requires navigation to domain; skipping until test harness serves page") — coverage that looks present but never runs in any gate. If it's an opt-in suite, document how it runs; otherwise re-enable or delete it.
Disabled test src/ElectronNET.IntegrationTests/Tests/HostHookTests.cs:13— A test is skipped ("Requires HostHook setup; skipping") — coverage that looks present but never runs in any gate. If it's an opt-in suite, document how it runs; otherwise re-enable or delete it.
Disabled test src/ElectronNET.IntegrationTests/Tests/ShellTests.cs:13— A test is skipped ("This can keep the test process hanging until the e-mail window is closed") — coverage that looks present but never runs in any gate. If it's an opt-in suite, document how it runs; otherwise re-enable or delete it.
DuplicateNoWarn REDACTED:16— NoWarn CS4014 is listed more than once for the same build configuration — remove the duplicate.
DuplicateNoWarn src/ElectronNET.AspNet/ElectronNET.AspNet.csproj:16— NoWarn CS4014 is listed more than once for the same build configuration — remove the duplicate.
Interpolated log message defeats structured logging src/ElectronNET.Build/PrintItemMetadata.cs:20— 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/ElectronNET.Build/PrintItemMetadata.cs:26— 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.
C2 · Access Controls· No named authorization policies · ×1
No named authorization policies — Authorization IS enforced here (by an auth-gate middleware that short-circuits unauthorized requests) — this is NOT a claim that the code is unprotected. What's missing is a NAMED rule set: the middleware encodes the access rules inline, so the rules can't be listed, reviewed or tested apart from the middleware body that applies them. Recommendation, not a defect.
Off-boarding risk: anonymized user #1 — If anonymized user #1 becomes unavailable, 2 significant file(s) lose their only recent owner: src/ElectronNET.WebApp/Program.cs, src/ElectronNET.WebApp/Controllers/WindowsController.cs. Pair on, review, or document these before any departure.
D16 · Bus Factor· Further sole-owners (lower concentration) · ×1
Further sole-owners (lower concentration) — 2 other contributor(s) are each the sole owner of a small amount of code below the off-boarding threshold — folded into the bus-factor score and metrics (4 single-owned of 72 analysed files in total, counted over production source files of roughly 2,400 bytes or more, excluding vendored, generated, example/demo and scaffolding-template trees and test files identified by path convention, largest first; 72 of the 227 production source files in this repository met that bar). They are anonymized user #2 (1 file(s)), anonymized user #3 (1 file(s)) — spread or document their files in the same way, at lower priority than the named off-boarding risks above. The files folded here: src/ElectronNET.Samples.AuthMiddleware/Program.cs, src/ElectronNET.API/API/Menu.cs.
No ADRs found — No ADRs found. No recognised ADR directory (`docs/adr/`, `docs/decisions/`, `adr/`, `docs/rfcs/`, an `ADR0001/` folder, or their siblings) exists anywhere in this tree. What was searched, so you can tell an empty log from a search that missed one: every directory under the tree (build output, dependencies and VCS metadata excepted), for a document that is either any non-index page inside a recognised ADR directory, whatever its name and however deeply nested (`docs/adr/use-postgres.md`, `docs/adr/2024/0001-x.md`); or a file anywhere whose name is ADR-shaped (`0001-use-postgres.md`, `adr-012-caching.md`); or, when neither turned anything up, a document carrying the decision-record signature (an "Architecture Decision Record" heading, or Status / Context / Decision / Consequences as section headings). A decision log that clears none of these — unnumbered files outside any recognised directory, without those headings — is not seen by this check and this row is then wrong. If that is your case, say so rather than renaming anything; otherwise, consider recording architectural decisions in `docs/adr/`.
redundant comment nuke/ReleaseNotesParser.cs:152— "Add the release notes to the result." repeats the code it sits on: 4 of its 4 words (add, release, notes, result) are already in `result.Add(new ReleaseNotes(semVer, new[] { line }, line));`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
D26 · Project Cohesion· Projects may be oversized for their cohesion · ×1
Projects may be oversized for their cohesion REDACTED:1— `ElectronNET.API(net6.0)` overshoots its size bounds (15050 LoC, 166 public types across 10 namespaces). 1 of 12 project(s) overshoot their size bounds, lowering Project Cohesion to 8.3/10. Size alone is no reason to split a project: where its type references show a separable part, a Split row names it.
Concentrated knowledge decay — 52 of 72 significant files have no living knowledge, while the repository is still being changed at a low rate (27 commit(s) in the last 90 days) — so this is one repo-wide knowledge-decay state, not 52 separate risks. Counted over 72 of the 227 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.
D34 · Knowledge Freshness· Most significant orphaned file · ×1
Most significant orphaned file src/ElectronNET.API/API/App.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.
No ADRs — No Architecture Decision Records found — no conventional ADR directory, no numbered `NNNN-title` documents in any markup this check reads, and nothing ADR-shaped by content. Design rationale recorded elsewhere (a design-notes tree, a mailing list, pull-request discussion) is not visible to this check and is not re-findable per decision, so a future maintainer cannot ask why one choice was made and get an answer.
P12 · CI test-gate honesty· Sleep-based test synchronization · ×1
Sleep-based test synchronization — 68 Task.Delay/Thread.Sleep call(s) in test code synchronize with background work by sleeping — a known flakiness precursor on slow runners. Prefer polling with a deadline or completion signals.
Logging is not universal — Only 4/8 service-like projects use logging (pure contract/DTO projects are excluded — they have nothing to log). Of those 8, 6 ship a process this repository operates; the rest are libraries their consumer hosts, where the logging decision belongs to the host.
No SAST REDACTED:3— 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 7 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.
No dependency-update automation nuke/_build.csproj:14— `nuke/_build.csproj` declares packages, and nothing in the repository keeps them current: no Dependabot or Renovate configuration that schedules updates, and no dependency-review gate on pull requests. A pinned dependency stays at the version it was added at until someone notices — including after an advisory is published against it. Add a `.github/dependabot.yml` with one `package-ecosystem` entry per ecosystem the tree uses (or an enabled `renovate.json`), and gate pull requests with `actions/dependency-review-action`.
S1 · Web-Security Posture· No inbound model validation detected · ×1
No inbound model validation detected — No ModelState/[ApiController]/FluentValidation signal — inbound payloads reach handlers unvalidated. (−2.0 on this card.)
X2 · Cancellation propagation· Not all async methods take a CancellationToken · ×1
Not all async methods take a CancellationToken — Only 34/48 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.
X2 · Cancellation propagation· Some async methods drop the CancellationToken they accept · ×1
Some async methods drop the CancellationToken they accept — 1 async method(s) await work their caller's cancellation cannot reach: a CancellationToken they hold (a parameter, or the one a framework-fixed signature carries) is never passed on, or the call is handed CancellationToken.None, default or an already-cancelled token. Forward the caller's token to that call.
Nullable reference types not enabled everywhere — 2/9 NRT-eligible project(s) enable <Nullable>enable</Nullable> (projects targeting a pre-C#-8 framework are excluded — NRTs aren't available there). NRTs catch a whole class of null-deref bugs at compile time.
Silent fallback default in catch src/ElectronNET.API/Common/ProcessRunner.cs:73— `IsRunning` swallows every exception into `return false;` — a data error becomes a silent behavior change with no trail. Log the failure or let validation throw.
doc comments repeat the names src/ElectronNET.API/API/App.cs:460— 65 of 361 documented parameters and 130 of 1492 summaries in `ElectronNET.API(net6.0)` only repeat the member or parameter name (e.g. "Options for the relaunch." for `relaunchOptions`). 276 documentation tag(s) are empty. Delete the restating tags, or add what the name does not say.
doc comments repeat the names src/ElectronNET.AspNet/API/ServiceCollectionExtensions.cs:5— 0 of 27 documented parameters and 0 of 19 summaries in `ElectronNET.AspNet(net6.0)` only repeat the member or parameter name (e.g. "" for `ServiceCollectionExtensions`). 1 documentation tag(s) are empty. Delete the restating tags, or add what the name does not say.
doc comments repeat the names nuke/Extensions/StringExtensions.cs:17— 4 of 28 documented parameters and 6 of 38 summaries in `_build` only repeat the member or parameter name (e.g. "Quotes the specified ." for `Quote`). Delete the restating tags, or add what the name does not say.
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.
trivy: not applicable — No Infrastructure-as-Code or container manifests found (Dockerfile, Docker Compose, Terraform, Kubernetes/Helm, CloudFormation, ARM, Bicep, Ansible); nothing to scan.
semgrep: not applicable — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that.
disclosure: not applicable — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed.
runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here.
runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here.
runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here.
Run 01a1cd99-aaa5-7544-bb1c-46971b3545c5 · every finding is also locatable in findings.md, and the complete scoring record (with exit codes + durations) in sidecar.json.
Issues: 72 · Warnings: 207 · Recommendations: 137 · Info: 3 — Appendix A · all findings · full markdown report.
Generated by the Canine Code Analyzer: deterministic code-health analysis. 12-11-2026 @ 02:32 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.