Public report of pal-tamas/rask, published 8 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.2). 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, 8 November 2026, 21:18 UTC · Survey ID cd_5a78d66e2339407cb9cdb4ce93e60bf2
pal-tamas/rask
Measured 8 November 2026, 21:15 UTC, at code version 00d5ba0
CAI scoreAdequate
CriticalWeakAdequateStrongExemplary
Up 11 since the last survey
The score is built from these lenses. Each lens grades one area of the code, such as how easy it is to change or how well it is protected. The weakest lens counts most, so one weak area pulls the score down instead of being averaged away.
A large codebase: 292,421 lines of product code in 141 projects, tests not counted · Estimated rebuild effort: about 6.9 person-years · Weakest lens: Production Readiness, 47
Findings by how serious they are
183 critical1055 serious207 minor
5 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
8 November 2026, 21:15 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 ▸
108of 108 dimensions measured by tools.
1428of 1445 findings point to an exact file and line, so you can open each one in the code. The other 17 concern the repository as a whole, such as missing documentation.
108dimensions across 8 lenses, read from 292,421 lines of product code in 141 projects.
pal-tamas/rask falls short of our standard for a preview release, in part because two passwords or keys sit in the current code. It scores 54 out of 100 and is rated Adequate, and 50 of its 183 critical findings are security problems.
Production Readiness, at 47, is the weakest lens and counts most in the score. The best first step is replacing the two exposed passwords or keys and switching the old ones off, worth about 6 points. Protecting outgoing calls with timeouts comes next, worth about 3 points. Raising Production Readiness to 62 would lift the score to about 59.
Thirty-eight pipeline tools are referenced by a changeable name, so the build pipeline can be tampered with. Five weaknesses in the code could be used by an attacker, and twenty-seven errors are caught and ignored, so failures can go unnoticed. Pinning each tool to an exact version, fixing the weaknesses the scanner points to and handling or logging the ignored errors would close these risks. Setting a waiting period for automatic updates would fix the automatic dependency update that takes a new release at once, and the two passwords or keys in the code need replacing, with the old ones switched off. The 67 warnings switched off for a whole file need narrowing to the lines that need them.
The product code is 292,421 lines, about €1,000,000 to rebuild.
A lens is capped at Adequate while one of its dimensions scores below 4 out of 10, however well the rest of the lens does. That way a serious problem in one place always shows in the lens's rating.
How the score is built: what each lens counts forThe lenses don't count equally. The weakest lens counts most, the next weakest a little less, and so on, so a weak area pulls the score down instead of being averaged away. In the bar below, each part's width shows how much that lens counts and its colour shows its rating. Improving the widest part moves the score most, and as that lens improves, it counts for less, because another lens becomes the weakest.
If Production Readiness rose from 47 to 62, the lowest score rated Strong, the score would rise from 54 to about 59.
Code composition: what the lines of code are
Business logic 16%Supporting code 18%Tests 61%Code analyzers 5%
New since the last survey: 376 findings
These 376 critical or serious findings weren't in the previous survey, on 22 October 2026. The first 100 are listed here, and the findings file in the download package lists them all.
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: 1080 findings
These 1080 critical or serious findings were in the previous survey, on 22 October 2026, and are gone from this one. The first 100 are listed here.
God Classes · TooManyMethods: ModelInputGenerator src/Rask.Batteries.Generators/ModelInputGenerator.WriteRules.cs
God Classes · FunctionTooLong: parity-editor.transcript scripts/flux/parity-editor.mjs
God Classes · TooManyMethods: UiKitDataInputDemo src/Rask.Site/Features/UiKit/UiKitDataInputDemo.cs
God Classes · FileTooLong: extractor/extract-props.ts src/Rask.External/extractor/extract-props.ts
God Classes · ClassTooLong: Ui src/Rask.Ui/Ui.ThemeName.cs
God Classes · FunctionTooLong: parity-carousel.walk scripts/flux/parity-carousel.mjs
God Classes · FileTooLong: External/ExternalGenerator.cs src/Rask.Generators/External/ExternalGenerator.cs
God Classes · FunctionTooLong: client.httpTransport src/Rask.Spa.Hosting/client/client.ts
God Classes · TooManyMethods: ExternalGenerator src/Rask.Generators/External/ExternalGenerator.cs
God Classes · FileTooLong: flux/parity-modal.mjs scripts/flux/parity-modal.mjs
Rebuild cost: about €1,000,000 · Estimate
Cost to rebuild
€330,000 to €1,700,000, for 5,538 to 17,805 hours of work, about 6.9 person-years for 4 to 14 engineers
Difficulty of the problem
High, 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 54. Better code takes more work to write, so the factor is ×1.0 at a score of 70, lower below it and higher above it.
Size
Large: 292,421 lines of product code
Comment lines
The estimate prices 224,314 lines. Comment lines count towards the size of 292,421 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
Resolve the 2 Leaked secret finding(s) in Secret Scanning — start with REDACTED, REDACTED.
Raises the score by about 6 points · Low effort · Secret Scanning
2
Add `AddStandardResilienceHandler()` (or a Polly policy and an explicit timeout) to each client registration flagged here, so a flaky dependency can't take the app down.
Replace each EnsureCreated() in production code with the migrations the rest of the repository already uses (`Database.Migrate()` or a migrations bundle), so every database gets its schema from the one versioned path.
Raises the score by about 3 points · Medium effort · Schema migrations
Diagnosis: what the measurements show together
Each conclusion below combines several dimensions into one point that no single dimension shows, and lists the measurements it rests on.
Where the investment is most exposed · Value at risk
This code would cost about €1,000,000 to build again, about 6.9 person-years of work. Its weakest lens is Production Readiness, at 47 (Weak). Production Readiness is about whether the product is ready to run in production and to change without breaking. Because the weakest lens counts most in the score, work on Production Readiness also moves the score most.
Based on: the rebuild estimate · the Production Readiness grade · how much each lens counts
What to do: Start with the Production Readiness actions in Top priorities.
If you do one thing first · First action
Resolve the 2 Leaked secret finding(s) in Secret Scanning. Of all the actions in this report, it raises the score most for the work it takes: about 6 points for low effort, because it clears the 2 Secret Scanning findings. The next survey will show the change in the score.
Based on: the ranked actions in Top priorities, by score gain and effort
Architecture — bounded-context dependency graph
Each box is a bounded context (its layer projects grouped, or a project count when large); arrows show dependencies between contexts. A shared kernel is where many arrows converge.
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.
201 modules, with 314 dependencies between them. 4 loops run through 40 of the modules, marked above the diagonal.
The table shows the 40 modules with the most connections; 161 more are left out to keep it readable.
Which modules use which. The module on each row uses the module in each column, and the number counts the pairs of types that connect them. A cell above the diagonal is part of a loop.
68 pairs of types, where a type in Rask.Cli.Commands uses a type in Rask.Cli. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
Rask.Core.Authentication uses Rask.Wire, so a change to Rask.Wire can break Rask.Core.Authentication, while a change to Rask.Core.Authentication can't break Rask.Wire.
Position
Below the diagonal: Rask.Core.Authentication uses a module listed above it, which is the healthy direction.
10→17 Rask.Core.HeadAssets uses Rask.Core.Livepart of a loop✕
Connections
1 pair of types, where a type in Rask.Core.HeadAssets uses a type in Rask.Core.Live.
Rask.Core.HeadAssets uses Rask.Core.Live, so a change to Rask.Core.Live can break Rask.Core.HeadAssets, while a change to Rask.Core.HeadAssets can't break Rask.Core.Live.
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.
10→21 Rask.Core.HeadAssets uses Rask.Corepart of a loop✕
Connections
1 pair of types, where a type in Rask.Core.HeadAssets uses a type in Rask.Core.
Rask.Core.HeadAssets uses Rask.Core, so a change to Rask.Core can break Rask.Core.HeadAssets, while a change to Rask.Core.HeadAssets can't break Rask.Core.
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.
11→13 Rask.Core.Routing uses Rask.Core.Globalizationpart of a loop✕
Connections
1 pair of types, where a type in Rask.Core.Routing uses a type in Rask.Core.Globalization.
Rask.Core.Routing uses Rask.Core.Globalization, so a change to Rask.Core.Globalization can break Rask.Core.Routing, while a change to Rask.Core.Routing can't break Rask.Core.Globalization.
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.
11→17 Rask.Core.Routing uses Rask.Core.Livepart of a loop✕
Connections
2 pairs of types, where a type in Rask.Core.Routing uses a type in Rask.Core.Live.
Rask.Core.Routing uses Rask.Core.Live, so a change to Rask.Core.Live can break Rask.Core.Routing, while a change to Rask.Core.Routing can't break Rask.Core.Live.
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.
11→21 Rask.Core.Routing uses Rask.Corepart of a loop✕
Connections
8 pairs of types, where a type in Rask.Core.Routing uses a type in Rask.Core.
Rask.Core.Globalization uses Rask.Core.Routing, so a change to Rask.Core.Routing can break Rask.Core.Globalization, while a change to Rask.Core.Globalization can't break Rask.Core.Routing.
Position
Below the diagonal: Rask.Core.Globalization uses a module listed above it, which is the healthy direction.
Rask.Core.Messaging uses Rask.Wire, so a change to Rask.Wire can break Rask.Core.Messaging, while a change to Rask.Core.Messaging can't break Rask.Wire.
Position
Below the diagonal: Rask.Core.Messaging uses a module listed above it, which is the healthy direction.
Rask.Core.Messaging uses Rask.Core.Routing, so a change to Rask.Core.Routing can break Rask.Core.Messaging, while a change to Rask.Core.Messaging can't break Rask.Core.Routing.
Position
Below the diagonal: Rask.Core.Messaging uses a module listed above it, which is the healthy direction.
14→21 Rask.Core.Messaging uses Rask.Corepart of a loop✕
Connections
2 pairs of types, where a type in Rask.Core.Messaging uses a type in Rask.Core.
Rask.Core.Messaging uses Rask.Core, so a change to Rask.Core can break Rask.Core.Messaging, while a change to Rask.Core.Messaging can't break Rask.Core.
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.
Rask.Core.Forms uses Rask.Core.Globalization, so a change to Rask.Core.Globalization can break Rask.Core.Forms, while a change to Rask.Core.Forms can't break Rask.Core.Globalization.
Position
Below the diagonal: Rask.Core.Forms uses a module listed above it, which is the healthy direction.
15→17 Rask.Core.Forms uses Rask.Core.Livepart of a loop✕
Connections
2 pairs of types, where a type in Rask.Core.Forms uses a type in Rask.Core.Live.
Rask.Core.Forms uses Rask.Core.Live, so a change to Rask.Core.Live can break Rask.Core.Forms, while a change to Rask.Core.Forms can't break Rask.Core.Live.
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.
15→21 Rask.Core.Forms uses Rask.Corepart of a loop✕
Connections
11 pairs of types, where a type in Rask.Core.Forms uses a type in Rask.Core.
Rask.Server.Prerender uses Rask.Core.Routing, so a change to Rask.Core.Routing can break Rask.Server.Prerender, while a change to Rask.Server.Prerender can't break Rask.Core.Routing.
Position
Below the diagonal: Rask.Server.Prerender uses a module listed above it, which is the healthy direction.
Rask.Server.Prerender uses Rask.Core.Globalization, so a change to Rask.Core.Globalization can break Rask.Server.Prerender, while a change to Rask.Server.Prerender can't break Rask.Core.Globalization.
Position
Below the diagonal: Rask.Server.Prerender uses a module listed above it, which is the healthy direction.
16→33 Rask.Server.Prerender uses Rask.Serverpart of a loop✕
Connections
2 pairs of types, where a type in Rask.Server.Prerender uses a type in Rask.Server.
Rask.Server.Prerender uses Rask.Server, so a change to Rask.Server can break Rask.Server.Prerender, while a change to Rask.Server.Prerender can't break Rask.Server.
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.
Rask.Core.Live uses Rask.Core.Diagnostics, so a change to Rask.Core.Diagnostics can break Rask.Core.Live, while a change to Rask.Core.Live can't break Rask.Core.Diagnostics.
Position
Below the diagonal: Rask.Core.Live uses a module listed above it, which is the healthy direction.
Rask.Core.Live uses Rask.Core.Authentication, so a change to Rask.Core.Authentication can break Rask.Core.Live, while a change to Rask.Core.Live can't break Rask.Core.Authentication.
Position
Below the diagonal: Rask.Core.Live uses a module listed above it, which is the healthy direction.
Rask.Core.Live uses Rask.Core.HeadAssets, so a change to Rask.Core.HeadAssets can break Rask.Core.Live, while a change to Rask.Core.Live can't break Rask.Core.HeadAssets.
Position
Below the diagonal: Rask.Core.Live uses a module listed above it, which is the healthy direction.
Rask.Core.Live uses Rask.Core.Routing, so a change to Rask.Core.Routing can break Rask.Core.Live, while a change to Rask.Core.Live can't break Rask.Core.Routing.
Position
Below the diagonal: Rask.Core.Live uses a module listed above it, which is the healthy direction.
Rask.Core.Live uses Rask.Core.Globalization, so a change to Rask.Core.Globalization can break Rask.Core.Live, while a change to Rask.Core.Live can't break Rask.Core.Globalization.
Position
Below the diagonal: Rask.Core.Live uses a module listed above it, which is the healthy direction.
Rask.Core.Live uses Rask.Core.Messaging, so a change to Rask.Core.Messaging can break Rask.Core.Live, while a change to Rask.Core.Live can't break Rask.Core.Messaging.
Position
Below the diagonal: Rask.Core.Live uses a module listed above it, which is the healthy direction.
Rask.Core.Live uses Rask.Core.Forms, so a change to Rask.Core.Forms can break Rask.Core.Live, while a change to Rask.Core.Live can't break Rask.Core.Forms.
Position
Below the diagonal: Rask.Core.Live uses a module listed above it, which is the healthy direction.
17→19 Rask.Core.Live uses Rask.Core.Componentspart of a loop✕
Connections
4 pairs of types, where a type in Rask.Core.Live uses a type in Rask.Core.Components.
Rask.Core.Live uses Rask.Core.Components, so a change to Rask.Core.Components can break Rask.Core.Live, while a change to Rask.Core.Live can't break Rask.Core.Components.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
17→21 Rask.Core.Live uses Rask.Corepart of a loop✕
Connections
31 pairs of types, where a type in Rask.Core.Live uses a type in Rask.Core. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
Rask.Core.Browser uses Rask.Core.Live, so a change to Rask.Core.Live can break Rask.Core.Browser, while a change to Rask.Core.Browser can't break Rask.Core.Live.
Position
Below the diagonal: Rask.Core.Browser uses a module listed above it, which is the healthy direction.
18→19 Rask.Core.Browser uses Rask.Core.Componentspart of a loop✕
Connections
2 pairs of types, where a type in Rask.Core.Browser uses a type in Rask.Core.Components.
Rask.Core.Browser uses Rask.Core.Components, so a change to Rask.Core.Components can break Rask.Core.Browser, while a change to Rask.Core.Browser can't break Rask.Core.Components.
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.
Rask.Core.Components uses Rask.Core.Authentication, so a change to Rask.Core.Authentication can break Rask.Core.Components, while a change to Rask.Core.Components can't break Rask.Core.Authentication.
Position
Below the diagonal: Rask.Core.Components uses a module listed above it, which is the healthy direction.
Rask.Core.Components uses Rask.Core.Routing, so a change to Rask.Core.Routing can break Rask.Core.Components, while a change to Rask.Core.Components can't break Rask.Core.Routing.
Position
Below the diagonal: Rask.Core.Components uses a module listed above it, which is the healthy direction.
Rask.Core.Components uses Rask.Core.Messaging, so a change to Rask.Core.Messaging can break Rask.Core.Components, while a change to Rask.Core.Components can't break Rask.Core.Messaging.
Position
Below the diagonal: Rask.Core.Components uses a module listed above it, which is the healthy direction.
Rask.Core.Components uses Rask.Core.Forms, so a change to Rask.Core.Forms can break Rask.Core.Components, while a change to Rask.Core.Components can't break Rask.Core.Forms.
Position
Below the diagonal: Rask.Core.Components uses a module listed above it, which is the healthy direction.
Rask.Core.Components uses Rask.Core.Live, so a change to Rask.Core.Live can break Rask.Core.Components, while a change to Rask.Core.Components can't break Rask.Core.Live.
Position
Below the diagonal: Rask.Core.Components uses a module listed above it, which is the healthy direction.
Rask.Core.Components uses Rask.Core.Browser, so a change to Rask.Core.Browser can break Rask.Core.Components, while a change to Rask.Core.Components can't break Rask.Core.Browser.
Position
Below the diagonal: Rask.Core.Components uses a module listed above it, which is the healthy direction.
19→21 Rask.Core.Components uses Rask.Corepart of a loop✕
Connections
45 pairs of types, where a type in Rask.Core.Components uses a type in Rask.Core. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
Rask.Core.Components uses Rask.Core, so a change to Rask.Core can break Rask.Core.Components, while a change to Rask.Core.Components can't break Rask.Core.
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.
Rask.Core.Diagnostics.DevTools uses Rask.Core.Diagnostics, so a change to Rask.Core.Diagnostics can break Rask.Core.Diagnostics.DevTools, while a change to Rask.Core.Diagnostics.DevTools can't break Rask.Core.Diagnostics.
Position
Below the diagonal: Rask.Core.Diagnostics.DevTools uses a module listed above it, which is the healthy direction.
Rask.Core.Diagnostics.DevTools uses Rask.Core.Live, so a change to Rask.Core.Live can break Rask.Core.Diagnostics.DevTools, while a change to Rask.Core.Diagnostics.DevTools can't break Rask.Core.Live.
Position
Below the diagonal: Rask.Core.Diagnostics.DevTools uses a module listed above it, which is the healthy direction.
Rask.Core.Diagnostics.DevTools uses Rask.Core.Components, so a change to Rask.Core.Components can break Rask.Core.Diagnostics.DevTools, while a change to Rask.Core.Diagnostics.DevTools can't break Rask.Core.Components.
Position
Below the diagonal: Rask.Core.Diagnostics.DevTools uses a module listed above it, which is the healthy direction.
20→21 Rask.Core.Diagnostics.DevTools uses Rask.Corepart of a loop✕
Connections
1 pair of types, where a type in Rask.Core.Diagnostics.DevTools uses a type in Rask.Core.
Rask.Core.Diagnostics.DevTools uses Rask.Core, so a change to Rask.Core can break Rask.Core.Diagnostics.DevTools, while a change to Rask.Core.Diagnostics.DevTools can't break Rask.Core.
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.
Rask.Core uses Rask.Core.Authentication, so a change to Rask.Core.Authentication can break Rask.Core, while a change to Rask.Core can't break Rask.Core.Authentication.
Position
Below the diagonal: Rask.Core uses a module listed above it, which is the healthy direction.
Rask.Core uses Rask.Core.HeadAssets, so a change to Rask.Core.HeadAssets can break Rask.Core, while a change to Rask.Core can't break Rask.Core.HeadAssets.
Position
Below the diagonal: Rask.Core uses a module listed above it, which is the healthy direction.
Rask.Core uses Rask.Core.Messaging, so a change to Rask.Core.Messaging can break Rask.Core, while a change to Rask.Core can't break Rask.Core.Messaging.
Position
Below the diagonal: Rask.Core uses a module listed above it, which is the healthy direction.
31 pairs of types, where a type in Rask.Core uses a type in Rask.Core.Forms. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
27 pairs of types, where a type in Rask.Core uses a type in Rask.Core.Live. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
Rask.Core uses Rask.Core.Components, so a change to Rask.Core.Components can break Rask.Core, while a change to Rask.Core can't break Rask.Core.Components.
Position
Below the diagonal: Rask.Core uses a module listed above it, which is the healthy direction.
Rask.Core uses Rask.Core.Diagnostics.DevTools, so a change to Rask.Core.Diagnostics.DevTools can break Rask.Core, while a change to Rask.Core can't break Rask.Core.Diagnostics.DevTools.
Position
Below the diagonal: Rask.Core uses a module listed above it, which is the healthy direction.
Rask.Core.ScopedAssets uses Rask.Core.Live, so a change to Rask.Core.Live can break Rask.Core.ScopedAssets, while a change to Rask.Core.ScopedAssets can't break Rask.Core.Live.
Position
Below the diagonal: Rask.Core.ScopedAssets uses a module listed above it, which is the healthy direction.
Rask.Core.ScopedAssets uses Rask.Core, so a change to Rask.Core can break Rask.Core.ScopedAssets, while a change to Rask.Core.ScopedAssets can't break Rask.Core.
Position
Below the diagonal: Rask.Core.ScopedAssets uses a module listed above it, which is the healthy direction.
Rask.DevTools.Probe uses Rask.Core.Diagnostics, so a change to Rask.Core.Diagnostics can break Rask.DevTools.Probe, while a change to Rask.DevTools.Probe can't break Rask.Core.Diagnostics.
Position
Below the diagonal: Rask.DevTools.Probe uses a module listed above it, which is the healthy direction.
Rask.DevTools.Probe uses Rask.Core.Live, so a change to Rask.Core.Live can break Rask.DevTools.Probe, while a change to Rask.DevTools.Probe can't break Rask.Core.Live.
Position
Below the diagonal: Rask.DevTools.Probe uses a module listed above it, which is the healthy direction.
Rask.DevTools.Probe uses Rask.Core.Components, so a change to Rask.Core.Components can break Rask.DevTools.Probe, while a change to Rask.DevTools.Probe can't break Rask.Core.Components.
Position
Below the diagonal: Rask.DevTools.Probe uses a module listed above it, which is the healthy direction.
Rask.DevTools.Probe uses Rask.Core.Diagnostics.DevTools, so a change to Rask.Core.Diagnostics.DevTools can break Rask.DevTools.Probe, while a change to Rask.DevTools.Probe can't break Rask.Core.Diagnostics.DevTools.
Position
Below the diagonal: Rask.DevTools.Probe uses a module listed above it, which is the healthy direction.
Rask.DevTools.Probe uses Rask.Core, so a change to Rask.Core can break Rask.DevTools.Probe, while a change to Rask.DevTools.Probe can't break Rask.Core.
Position
Below the diagonal: Rask.DevTools.Probe uses a module listed above it, which is the healthy direction.
Rask.Querying uses Rask.Core.Authentication, so a change to Rask.Core.Authentication can break Rask.Querying, while a change to Rask.Querying can't break Rask.Core.Authentication.
Position
Below the diagonal: Rask.Querying uses a module listed above it, which is the healthy direction.
Rask.Wasm uses Rask.Core.Authentication, so a change to Rask.Core.Authentication can break Rask.Wasm, while a change to Rask.Wasm can't break Rask.Core.Authentication.
Position
Below the diagonal: Rask.Wasm uses a module listed above it, which is the healthy direction.
Rask.Wasm uses Rask.Core.Globalization, so a change to Rask.Core.Globalization can break Rask.Wasm, while a change to Rask.Wasm can't break Rask.Core.Globalization.
Position
Below the diagonal: Rask.Wasm uses a module listed above it, which is the healthy direction.
Rask.DevTools.Panel uses Rask.Core.Routing, so a change to Rask.Core.Routing can break Rask.DevTools.Panel, while a change to Rask.DevTools.Panel can't break Rask.Core.Routing.
Position
Below the diagonal: Rask.DevTools.Panel uses a module listed above it, which is the healthy direction.
Rask.DevTools.Panel uses Rask.Core.Live, so a change to Rask.Core.Live can break Rask.DevTools.Panel, while a change to Rask.DevTools.Panel can't break Rask.Core.Live.
Position
Below the diagonal: Rask.DevTools.Panel uses a module listed above it, which is the healthy direction.
Rask.DevTools.Panel uses Rask.Core.Diagnostics.DevTools, so a change to Rask.Core.Diagnostics.DevTools can break Rask.DevTools.Panel, while a change to Rask.DevTools.Panel can't break Rask.Core.Diagnostics.DevTools.
Position
Below the diagonal: Rask.DevTools.Panel uses a module listed above it, which is the healthy direction.
Rask.DevTools.Panel uses Rask.Core, so a change to Rask.Core can break Rask.DevTools.Panel, while a change to Rask.DevTools.Panel can't break Rask.Core.
Position
Below the diagonal: Rask.DevTools.Panel uses a module listed above it, which is the healthy direction.
26 pairs of types, where a type in Rask.DevTools.Panel uses a type in Rask.DevTools.Probe. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
Rask.DevTools.Panel uses Rask.DevTools.Probe, so a change to Rask.DevTools.Probe can break Rask.DevTools.Panel, while a change to Rask.DevTools.Panel can't break Rask.DevTools.Probe.
Position
Below the diagonal: Rask.DevTools.Panel uses a module listed above it, which is the healthy direction.
31 pairs of types, where a type in Rask.Auth uses a type in Rask.Wire. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
Rask.Auth uses Rask.Core.Authentication, so a change to Rask.Core.Authentication can break Rask.Auth, while a change to Rask.Auth can't break Rask.Core.Authentication.
Position
Below the diagonal: Rask.Auth uses a module listed above it, which is the healthy direction.
Rask.Background uses Rask.Batteries, so a change to Rask.Batteries can break Rask.Background, while a change to Rask.Background can't break Rask.Batteries.
Position
Below the diagonal: Rask.Background uses a module listed above it, which is the healthy direction.
Rask.Server uses Rask.Core.Authentication, so a change to Rask.Core.Authentication can break Rask.Server, while a change to Rask.Server can't break Rask.Core.Authentication.
Position
Below the diagonal: Rask.Server uses a module listed above it, which is the healthy direction.
Rask.Server uses Rask.Core.Routing, so a change to Rask.Core.Routing can break Rask.Server, while a change to Rask.Server can't break Rask.Core.Routing.
Position
Below the diagonal: Rask.Server uses a module listed above it, which is the healthy direction.
Rask.Server uses Rask.Core.Globalization, so a change to Rask.Core.Globalization can break Rask.Server, while a change to Rask.Server can't break Rask.Core.Globalization.
Position
Below the diagonal: Rask.Server uses a module listed above it, which is the healthy direction.
Rask.Server uses Rask.Server.Prerender, so a change to Rask.Server.Prerender can break Rask.Server, while a change to Rask.Server can't break Rask.Server.Prerender.
Position
Below the diagonal: Rask.Server uses a module listed above it, which is the healthy direction.
Rask.Server uses Rask.Core.Browser, so a change to Rask.Core.Browser can break Rask.Server, while a change to Rask.Server can't break Rask.Core.Browser.
Position
Below the diagonal: Rask.Server uses a module listed above it, which is the healthy direction.
Rask.Server uses Rask.Core.Components, so a change to Rask.Core.Components can break Rask.Server, while a change to Rask.Server can't break Rask.Core.Components.
Position
Below the diagonal: Rask.Server uses a module listed above it, which is the healthy direction.
Rask.Server uses Rask.Core.ScopedAssets, so a change to Rask.Core.ScopedAssets can break Rask.Server, while a change to Rask.Server can't break Rask.Core.ScopedAssets.
Position
Below the diagonal: Rask.Server uses a module listed above it, which is the healthy direction.
Rask uses Rask.Core.Authentication, so a change to Rask.Core.Authentication can break Rask, while a change to Rask can't break Rask.Core.Authentication.
Position
Below the diagonal: Rask uses a module listed above it, which is the healthy direction.
85 pairs of types, where a type in Rask uses a type in Rask.Core.Forms. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
Rask.Dashboard.Panels uses Rask.Background, so a change to Rask.Background can break Rask.Dashboard.Panels, while a change to Rask.Dashboard.Panels can't break Rask.Background.
Position
Below the diagonal: Rask.Dashboard.Panels uses a module listed above it, which is the healthy direction.
Rask.Dashboard.Panels uses Rask.Caching, so a change to Rask.Caching can break Rask.Dashboard.Panels, while a change to Rask.Dashboard.Panels can't break Rask.Caching.
Position
Below the diagonal: Rask.Dashboard.Panels uses a module listed above it, which is the healthy direction.
Rask.Dashboard.Panels uses Rask.Mailing, so a change to Rask.Mailing can break Rask.Dashboard.Panels, while a change to Rask.Dashboard.Panels can't break Rask.Mailing.
Position
Below the diagonal: Rask.Dashboard.Panels uses a module listed above it, which is the healthy direction.
Rask.Dashboard.Panels uses Rask.Outbox, so a change to Rask.Outbox can break Rask.Dashboard.Panels, while a change to Rask.Dashboard.Panels can't break Rask.Outbox.
Position
Below the diagonal: Rask.Dashboard.Panels uses a module listed above it, which is the healthy direction.
Rask.Dashboard.Panels uses Rask.Storage, so a change to Rask.Storage can break Rask.Dashboard.Panels, while a change to Rask.Dashboard.Panels can't break Rask.Storage.
Position
Below the diagonal: Rask.Dashboard.Panels uses a module listed above it, which is the healthy direction.
Rask.Server.Printing uses Rask.Core.Routing, so a change to Rask.Core.Routing can break Rask.Server.Printing, while a change to Rask.Server.Printing can't break Rask.Core.Routing.
Position
Below the diagonal: Rask.Server.Printing uses a module listed above it, which is the healthy direction.
Rask.Server.Printing uses Rask.Core.Globalization, so a change to Rask.Core.Globalization can break Rask.Server.Printing, while a change to Rask.Server.Printing can't break Rask.Core.Globalization.
Position
Below the diagonal: Rask.Server.Printing uses a module listed above it, which is the healthy direction.
Rask.Server.Printing uses Rask.Server.Prerender, so a change to Rask.Server.Prerender can break Rask.Server.Printing, while a change to Rask.Server.Printing can't break Rask.Server.Prerender.
Position
Below the diagonal: Rask.Server.Printing uses a module listed above it, which is the healthy direction.
Rask.Server.Printing uses Rask.Core, so a change to Rask.Core can break Rask.Server.Printing, while a change to Rask.Server.Printing can't break Rask.Core.
Position
Below the diagonal: Rask.Server.Printing uses a module listed above it, which is the healthy direction.
Rask.Server.Printing uses Rask.Core.ScopedAssets, so a change to Rask.Core.ScopedAssets can break Rask.Server.Printing, while a change to Rask.Server.Printing can't break Rask.Core.ScopedAssets.
Position
Below the diagonal: Rask.Server.Printing uses a module listed above it, which is the healthy direction.
Rask.Server.Printing uses Rask.Server, so a change to Rask.Server can break Rask.Server.Printing, while a change to Rask.Server.Printing can't break Rask.Server.
Position
Below the diagonal: Rask.Server.Printing uses a module listed above it, which is the healthy direction.
Rask.Dashboard.Pages uses Rask.Core.Routing, so a change to Rask.Core.Routing can break Rask.Dashboard.Pages, while a change to Rask.Dashboard.Pages can't break Rask.Core.Routing.
Position
Below the diagonal: Rask.Dashboard.Pages uses a module listed above it, which is the healthy direction.
Rask.Dashboard.Pages uses Rask.Core, so a change to Rask.Core can break Rask.Dashboard.Pages, while a change to Rask.Dashboard.Pages can't break Rask.Core.
Position
Below the diagonal: Rask.Dashboard.Pages uses a module listed above it, which is the healthy direction.
Rask.Dashboard.Pages uses Rask.Dashboard.Panels, so a change to Rask.Dashboard.Panels can break Rask.Dashboard.Pages, while a change to Rask.Dashboard.Pages can't break Rask.Dashboard.Panels.
Position
Below the diagonal: Rask.Dashboard.Pages uses a module listed above it, which is the healthy direction.
Rask.Site.Features uses Rask.Core.Routing, so a change to Rask.Core.Routing can break Rask.Site.Features, while a change to Rask.Site.Features can't break Rask.Core.Routing.
Position
Below the diagonal: Rask.Site.Features uses a module listed above it, which is the healthy direction.
Rask.Site.Features uses Rask.Core.Forms, so a change to Rask.Core.Forms can break Rask.Site.Features, while a change to Rask.Site.Features can't break Rask.Core.Forms.
Position
Below the diagonal: Rask.Site.Features uses a module listed above it, which is the healthy direction.
Rask.Site.Features uses Rask.Core.Live, so a change to Rask.Core.Live can break Rask.Site.Features, while a change to Rask.Site.Features can't break Rask.Core.Live.
Position
Below the diagonal: Rask.Site.Features uses a module listed above it, which is the healthy direction.
Rask.Site.Features uses Rask.Core.Browser, so a change to Rask.Core.Browser can break Rask.Site.Features, while a change to Rask.Site.Features can't break Rask.Core.Browser.
Position
Below the diagonal: Rask.Site.Features uses a module listed above it, which is the healthy direction.
213 pairs of types, where a type in Rask.Site.Features uses a type in Rask.Core. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
Rask.Site.Features uses Rask.Querying, so a change to Rask.Querying can break Rask.Site.Features, while a change to Rask.Site.Features can't break Rask.Querying.
Position
Below the diagonal: Rask.Site.Features uses a module listed above it, which is the healthy direction.
Rask.Site uses Rask.Core.Authentication, so a change to Rask.Core.Authentication can break Rask.Site, while a change to Rask.Site can't break Rask.Core.Authentication.
Position
Below the diagonal: Rask.Site uses a module listed above it, which is the healthy direction.
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
85
High / Critical
A02:2025 — Security Misconfiguration
11
High / Critical
A03:2025 — Software Supply Chain Failures
6
Medium
A07:2025 — Authentication Failures
2
High / Critical
Roadmap
Top priorities: Resolve the 2 Leaked secret finding(s) in Secret Scanning — start with REDACTED, REDACTED; Add `AddStandardResilienceHandler()` (or a Polly policy and an explicit timeout) to each client registration flagged here, so a flaky dependency can't take the app down; Replace each EnsureCreated() in production code with the migrations the rest of the repository already uses (`Database.Migrate()` or a migrations bundle), so every database gets its schema from the one versioned path.
Ranked by impact ÷ effort. "Helps" is the estimated gain on the 0–100 health score.
Do this
Helps
Effort
Dimension
Resolve the 2 Leaked secret finding(s) in Secret Scanning — start with REDACTED, REDACTED.
Add `AddStandardResilienceHandler()` (or a Polly policy and an explicit timeout) to each client registration flagged here, so a flaky dependency can't take the app down.
Replace each EnsureCreated() in production code with the migrations the rest of the repository already uses (`Database.Migrate()` or a migrations bundle), so every database gets its schema from the one versioned path.
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.
Enforce accessibility in the test suite you already have: assert the accessibility invariants over the HTML your app renders — parse the rendered output in an existing test, or drive a real browser from one — and gate that test in CI so a regression blocks the merge.
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 — 183
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 — 1055
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 — 207
Recorded, with no effect on how the codebase functions.
Present so the survey is complete, not because it needs doing.
Could not be resolved — 5
Something this survey could not settle
from the outside, and which could be critical or serious. Either a control was required and no
positive evidence of it exists in the repository — a backup job that nothing shows was ever restored from proves
nothing about restores — or our own analysis could not run over that part of the tree. This is not a clean
result. These are excluded from the score rather than awarded a pass, so the number on the cover neither
rewards nor penalises them: if you act on this survey without resolving them, you carry that risk yourself. Each
one is named under Limitations.
Methodology & how to trust this report
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 108 evaluated dimensions are computed by tools and static analysis; no language model sets or judges any of them. Overall confidence is 1.0, 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 — 108 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, 1428 of 1445 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 — 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. At least one `dotnet test` target was stopped at its time budget, so the gathered reports cover only part of the suite. The overall 75.8% is a FLOOR (everything the completed runs covered really is covered), but a per-file figure from a partial gather cannot tell an untested file from one whose test project never ran — so per-file and CRAP rows are withheld rather than published as measurements. You can widen what we reach: optional: commit the Cobertura/OpenCover/lcov report your CI already produces, and per-file rows can be read without a re-run.
D8 Code Coverage — 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. 146 test(s) skipped themselves while running here (their declarations do not skip them: something they need, such as a database or a device, was not available to this run). The 14 production file(s) those tests reach that read under half covered are unmeasured in this run, not untested, so their figures are left out of the per-file rows and the 75.8% rather than published as low coverage. You can widen what we reach: optional: commit the Cobertura/OpenCover/lcov report of a run where those tests execute, and their files are read from it.
D10 Test 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. The 13,033 test(s) behind this row are the ones the C# collector could read, and this repository also carries at least 60 test source file(s) (.ts) that it cannot: it parses C# syntax and matches C# test attributes, so a vitest/jest/JUnit/pytest-style suite is invisible to it. Skipped tests, zero-assertion tests and the other quality signals on this row are UNMEASURED in that suite — their absence from the counts above is a gap in this analyzer's language coverage, not a finding that those tests are sound.
D11 Test Reliability — 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. Test reliability is scored on the 1 tier(s) that produced comparable repeat runs; 2 tier(s) did not, and are excluded from the measurement rather than counted (unit: not included — too large to re-run within its budget; e2e: not included — too large to re-run within its budget; other: measured (0 flaky)). This is OUR limitation, not a defect in the repository.
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: /usr/share/dotnet/sdk/10.0.400/NuGet.targets(198,5): error MSB4181: The "RestoreTask" task returned false but did not log an error. [src/Rask.Templates/server/Company.RaskServer.slnx].
D16 Bus Factor — not measured this run — This is a true statement about the repository that carries nothing for its owner to act on, so it is reported here rather than as a defect in their code. Single-contributor repository — bus factor is not applicable (1 contributor(s) across 4690 commit(s) sampled, automation and bot accounts excluded). Concentration needs a team to concentrate: with one contributor there is nobody to spread the knowledge to, so there is nothing here for the owner to act on.
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: Msbuild failed when processing the file 'src/Rask.Core/Rask.Core.csproj' with message: The "Rask.Core.Dom.Build.RaskDomEmit" task could not be loaded from the assembly src/Rask.Core/Dom/../../Rask.Dom.Tasks/bin/Debug/netstandard2.0/Rask.Dom.Tasks.dll. Could not load file or assembly '….
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 2 error(s), and the diagnostics it printed were: MSB6006: "csc" exited with code 137.; MSB3923: Failed to download file "https://storage.googleapis.com/chrome-for-testing-public/156.0.8078.73/linux64/chrome-headless-shell-linux64.zip". The proxy tunnel request to proxy 'http://egress:3128/' failed with status code '403'.". 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.
D23 Boundary Type-Coupling — 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 measured 0/40 valid on a seeded held-out sample of its rows on 98 C# repositories (docs/plans/deterministic-engine/adjudication/P5c-D23-units.md, "Version 1 ON MAIN"): the noise rows were dependencies on layer folders, shared cores and grouping folders read as contexts. By the pre-registered fallback (PREREGISTRATION v37) it publishes no row until version 4 passes its gate. The candidates are counted here, not reported as findings, and the score does not include them.
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) — 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. `gitleaks` TIMED OUT after 87.1s against a 86.4s budget, so we killed its process tree. The budget is ours; the work may simply be larger than it allows. Nothing about this repository is asserted by the absence of a result; the budget is ours to raise, and raising it is our backlog item, not an action for this repository's owner.
D31 IaC & Container Security — 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. Checkov ran but its report could not be read (checkov produced no output — not a clean result). Every misconfiguration only checkov reports — most of its Terraform, CloudFormation, Bicep and Ansible policies — is absent from this card, so its absence here is not evidence those resources are configured correctly.
D32 Data Compliance (PII/GDPR) — 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. `.claude/skills/run-rask/dashboard-driver.cs`, `.claude/skills/run-rask/driver.cs`, `.claude/skills/run-rask/fitprobe.cs`, `.claude/skills/run-rask/frameprobe.cs`, `.claude/skills/run-rask/growprobe.cs`, … (+592 more) produced a parse error, so every rule in this engine's `gdpr.yml` was absent there. That absence is NOT a clean result: these rules detect personal data crossing a boundary into a log sink, a URL or browser storage, and a file that was never parsed cannot report any of the three. The rest of the tree analysed normally and its rows above stand; only these files are unaccounted for. You can widen what we reach: fix the syntax error (or exclude the file deliberately) and re-scan to cover it.
AX2 Stateful singletons — 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. 5 further occurrence(s) are not listed individually; the score already reflects all 45.
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 REDACTED (REDACTED). docker build failed (exit 1) — ------ REDACTED:12 -------------------- 11 | COPY ["Company.RaskServer.csproj", "./"] 12 | >>> RUN --mount=type=cache,id=rask-nuget,target=/root/.nuget/packages \ 13 | >>> dotnet restore 14 | COPY . . -------------------- ERROR: failed to solve: process "/bin/sh -c dotnet restore" did not complete successfully: exit code: 1; runtime evidence skipped.
DM8 Value-object opportunities — 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. This check finds primitive parameters that travel together through several signatures of the domain (a missing value object). Its deterministic rule has not yet shown 95 % precision on adjudicated rows, so the clumps it finds are counted here and not published as findings, and the card carries no score. That is a limit of the analyzer, not a finding about your code.
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.
P12 CI test-gate honesty — 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. 23 further occurrence(s) are not listed individually; the score already reflects all 63.
R10 Code Duplication — 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. 8 further occurrence(s) are not listed individually; the score already reflects all 48.
X2 Cancellation propagation — 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. 733 further occurrence(s) are not listed individually; the score already reflects all 773.
X3 Exception handling — 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. 10 further occurrence(s) are not listed individually; the score already reflects all 50.
X7 Silent fallback defaults — 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. 33 further occurrence(s) are not listed individually; the score already reflects all 73.
Package restore incomplete — third-party types were unresolved in part of the solution — NuGet restore did not complete for src/Rask.Templates/server/Company.RaskServer.csproj, src/Rask.Templates/server/Company.RaskServer.Tests/Company.RaskServer.Tests.csproj, src/Rask.Templates/wasm-hosted/Company.RaskServer.csproj, src/Rask.Templates/wasm/Company.RaskServer.csproj, src/Rask.Templates/wasm/Company.RaskServer.Tests/Company.RaskServer.Tests.csproj, so those projects were analysed with framework references only: every check keyed on a third-party type saw an error type there and reported nothing. Findings on those projects are a lower bound; run `dotnet restore` on them and rescan.
Repo exclusion declarations (.gitattributes linguist-generated/vendored, .editorconfig generated_code): none declared — every source file was scored.
Limitations & what we did not check
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.
D8 Code Coverage: Coverage is measured by building and running the test suite inside our isolated image — the target repo is never modified, and nothing on your systems runs. So coverage exists only when the suite builds and runs within the inline time budget; one that needs external services, can't build, or exceeds the budget yields no coverage (D8 then degrades to not-measured, not a low score). Line coverage also says nothing about assertion quality.
D9 Test Distribution: The test-pyramid shape is inferred from project/folder naming and references, with a single test host bucketed per-file by its path tier and content signals — a suite that names tiers unconventionally and gives no per-file signal can still be mis-bucketed.
D10 Test Quality: Assertion density is structural — it cannot tell a meaningful behavioural assertion from a trivial one, only that an assertion is present.
D11 Test Reliability: Flakiness is inferred from history/markers — we run the suite once (for coverage), not the repeated runs under varied conditions that reveal nondeterminism, so a flaky test never recorded as failing is invisible here.
D13 Secret Scanning: Secret detection is signature- and entropy-based on the current tree — a secret that does not match a known pattern, or one already rotated, will not be flagged (a clean scan is "nothing matched", not "no secrets exist").
D14 License Compliance: License compatibility is checked against declared package metadata and a policy — mislabelled or missing license metadata, and obligations that depend on how you distribute, are not resolved here.
D15 Churn × Complexity Hotspots: Churn hotspots come from git history — a freshly imported or squashed repository has no churn signal, and recent rewrites can mask a historically risky file.
D17 Explicit Debt: Acknowledged-debt signals (TODO/FIXME, suppressions, dead code) are textual — undocumented debt that nobody marked, and debt that lives in design rather than annotations, is invisible. Committed machine-written code (scaffolded migrations, designer/codegen output, generated stubs) is excluded — it is never the team's dead code to delete.
D18 Solution Shape: Build integrity reflects whether the solution compiled in this environment — a build that needs a private feed, a specific SDK, or a generated file absent from the repo can read as broken when it is merely unreproducible here.
D19 Documentation Quality: Documentation quality 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.
D22 Internal API Consistency: API consistency compares the call shapes of members that play the same role on the exposed C# surface: whether the API suits its callers is not measured, and surfaces in other languages are not measured.
D23 Boundary Type-Coupling: Boundary leakage is detected from type references across detected contexts — leaks that flow through primitives, serialization or shared infrastructure may not surface as a typed reference.
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.
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").
D31 IaC & Container Security: IaC scanning checks Dockerfiles/Terraform/Kubernetes against best-practice rules — it cannot see the live cloud account, runtime configuration, or drift between the committed config and what is actually deployed.
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 REDACTED (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.
AC5 ARIA correctness: ARIA correctness is checked against the static role/attribute shape — roles/attributes set dynamically aren't seen, a valid role says nothing about whether it matches the element's real behaviour, and required-state checks are suppressed when a JSX spread could supply them. The two-branch toggle check (a control whose state is conveyed only by which of two mutually exclusive branches renders) reads CONDITIONALS THAT ARE ATTRIBUTES — Vue v-if/v-else/v-show and Alpine x-if/x-show — so the same toggle written as a Svelte {#if} block or a JSX ternary is control flow the markup model never projects as a branch and is not seen at all.
AC6 Visual & motion safety: Contrast and motion safety are PARTIAL by construction — literal colours (hex/rgb/hsl/named) in inline styles, in-repo <style> blocks, in-repo .css files, var() tokens, Tailwind neutral utilities and CSS-in-JS top-level declarations are read (same-rule/same-element colour+background pairs only); computed/runtime/theme colour, external-CDN stylesheets, CSS-in-JS dynamic (${…}) and nested-selector colours, cross-element pairs and image contrast stay out of reach, so a clean result is bounded by what the static CSS itself shows.
AC7 A11y enforcement: Enforcement is scored from in-repo config/CI evidence only — an a11y gate enforced in external tooling with no in-repo trace can't be credited, and a configured linter is presence, not proof the rules actually run or block a merge.
AX10 Code composition: Role is inferred from namespace/folder convention, not semantics — a domain concept living in a folder named "Services" reads as application, and the split is lines-of-code, not business value. The business-logic-share score is a SOFT, FLOORED signal: it contributes to the Architecture lens but is floored at the Critical gate, so an infrastructure-heavy design (a gateway, an ETL, a driver) is legitimately low without being nuked to zero.
AX9 CQS / query purity: Handlers are found by interface/name convention — a query handler using neither is not seen. Mutation is a resolved write/publish invocation (SaveChanges/repository/bus), so a write hidden behind a hand-rolled wrapper, reflection, or a string-keyed service locator resolves to a non-persistence type and isn't flagged; it detects that a query writes state, not whether the write is a legitimate read-side cache update. Clean means "no resolved write/publish in a query body", not a proof of CQS purity.
C3 Audit Trail: This control is scored from in-repo evidence only — a working control configured outside the repository leaves no signal a static scan can credit.
C4 Data Retention: This control is scored from in-repo evidence only — its real-world effectiveness, exercised only at runtime, is outside a static scan.
DM4 Rich vs anemic model: Behaviour is detected as state mutation inside a method body — a method that enforces an invariant by validating-and-throwing without mutating reads as a query, and mutation delegated through an interface the scan can't resolve isn't credited; entities with zero public properties still drop out of the population. It detects that state changes, not whether the rule is correct.
ED5 Idempotency: Idempotency is read from the handler body and one hop below: a mutation is flagged only on structural double-apply evidence (a fresh-identity insert, an accumulation, a growing list, an unkeyed POST/send/charge), so a duplicate effect through a home-grown gateway two hops down, or an insert keyed on the message with no unique constraint, is not flagged but counted as not classified; a guard enforced by a database constraint or a broker's exactly-once delivery is invisible either way. It flags the at-least-once double-apply SHAPE, not a runtime proof of a duplicate effect.
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.
P4 Deployment & Rollback: Approval/branch-protection rules live in repository settings the scan cannot see — only their in-repo evidence (config files, workflows) is checked, so a control enforced purely in the host's settings reads as "not evidenced".
P5 DR & Backup: Backup/restore and disaster-recovery readiness is judged from in-repo evidence — a config that exists is not a tested restore, so the absence of positive evidence is reported as "not evidenced", never scored as present.
P6 Release Hygiene: Rollback/observability controls are inferred from repo artefacts (pipelines, dashboards-as-code) — controls configured in external tooling, with no in-repo trace, cannot be credited.
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.
108 method(s) exceeded the cyclomatic complexity threshold of 15; the worst was rask-morph.morphNode at 97. A further 31 method(s) were over the threshold but excluded as flat dispatchers (a long switch/match over independent cases: many branches, almost no nesting), the largest being UiDateRangePresets.Label at 29 — they are counted neither in the figure above nor in this dimension's score. 18 files carry no cyclomatic complexity row at all for this reason — every one of their over-threshold methods was excluded, so the exclusion is disclosed nowhere in the file itself: src/Rask.Ui/UiDateRangePresets.cs (UiDateRangePresets.Label at 29), src/Rask.Core/Forms/AttributeMessages.cs (AttributeMessages.For at 24), src/Rask.Core/InputTypeExtensions.cs (InputTypeExtensions.ToHtml at 24), src/Rask.Ui/UiButtonClasses.cs (UiButtonClasses.Accent at 24), src/Rask.Ui/UiNavColors.cs (UiNavColors.Badge at 24), and 13 more not listed here. They are named here because the per-file figures other dimensions report are taken BEFORE this exclusion, so such a file can show a high maximum complexity elsewhere in this report and nothing here, with nothing to reconcile the two.
+ 103 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Bring the 1 body over 60 down to 60 or less in Cyclomatic Complexity — start with rask-morph.morphNode (cyclomatic 97). — Refactoring it lifts Cyclomatic Complexity from 6.0 to about 6.5/10.
Enforce Cyclomatic Complexity in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
Detailed fixes: d1_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: How hard the code is for a person to follow, beyond raw branching.
Method: Cognitive complexity per method (Sonar-style nesting-penalized score), computed exhaustively over production code, excluding test projects. Deterministic.
+ 184 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Bring the 1 body over 120 down to 120 or less in Cognitive Complexity — start with rask-morph.morphNode (cognitive 145). — Refactoring it lifts Cognitive Complexity from 5.6 to about 5.8/10.
Enforce Cognitive Complexity in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
Detailed fixes: d2_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D3 · God Classes9.1 / 10Stronggated by 63 serious findings✓ Tool-verified
What it measures: Over-large classes that try to do too much ("god classes").
Method: God-class detection by line and method-count thresholds per logical type (partial classes unified), filtered for generated code and registration/contract false positives. Deterministic.
Resolve the 32 TooManyMethods finding(s) in God Classes — start with Component.Handlers.cs, ComponentFactoryGenerator.ComponentModel.cs, REDACTED. — One of this dimension's main actionable groups (32 warning-level).
Resolve the 15 FileTooLong finding(s) in God Classes — start with REDACTED, rask.ts, rask-calendar.ts. — One of this dimension's main actionable groups (15 warning-level).
Resolve the 10 ClassTooLong finding(s) in God Classes — start with UiApi.cs, TranslationCatalogGenerator.cs, Ui.DateRangePreset.cs. — One of this dimension's main actionable groups (10 warning-level).
Enforce God Classes in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
Detailed fixes: d3_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Copy-pasted code that should be shared instead.
Method: Code duplication via token-stream sliding windows with type-aware normalization (locals masked, type names preserved), density-scored per KLoC of production code. Deterministic.
130 duplicated block group(s) detected. A further 5 rows report members as variants of one another; they aggregate block groups already counted above and are not themselves counted. 29 of the 135 are in trees this repository does not ship — vendored, example/demo, project-template, fixture and benchmark code — and are ranked below the shipped groups rather than excluded from them: the duplication there is real and is still counted in this dimension's score. The dimensions that publish a production-file census leave those trees out of theirs, so this count is deliberately drawn over the wider population.
+ 61 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Resolve the 12 Duplicated block (8 lines × 2) finding(s) in Code Duplication — start with ModelInputGenerator.Rules.cs, ComponentScopedCssGenerator.cs, QueryClient.cs. — One of this dimension's main actionable groups (12 warning-level).
Resolve the 11 Duplicated block (5 lines × 2) finding(s) in Code Duplication — start with FrameDiffer.cs, DevToolsPerfTab.cs, ComponentScopedJsGenerator.cs. — One of this dimension's main actionable groups (11 warning-level).
Resolve the 9 Duplicated block (7 lines × 2) finding(s) in Code Duplication — start with DomEmitter.cs, LivePayload.cs, AggregateSave.cs. — One of this dimension's main actionable groups (9 warning-level).
Enforce Code Duplication in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Verified — provenance only; does not change the score.
Detailed fixes: d4_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D5 · Coupling9.5 / 10Stronggated by 9 serious findings✓ Tool-verified
What it measures: Whether volatile projects sit underneath others that depend on them (so their churn ripples upward), and whether project dependencies form cycles. A widely-depended-on but stable shared/kernel project is healthy, not penalised.
Method: Dependency cycles via elementary-DFS over real .csproj references, plus Martin instability (afferent/efferent) per project. Exhaustive over the reference graph, deterministic.
Coverage: Exhaustive · type-level: afferent/efferent coupling + cycles computed over every production type — the population is all types, not a name convention.
Resolve the 7 Off the main sequence finding(s) in Coupling — start with Rask.SQLite.csproj, Rask.Wire.csproj, Rask.SQLite.Snapshots.csproj. — One of this dimension's main actionable groups (7 warning-level).
Resolve the 1 Unstable project Rask.Dashboard finding(s) in Coupling — start with Rask.Dashboard.csproj. — One of this dimension's main actionable groups (1 warning-level).
Resolve the 1 Unstable project Rask.Server finding(s) in Coupling — start with Rask.Server.csproj. — One of this dimension's main actionable groups (1 warning-level).
Enforce Coupling in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
Detailed fixes: d5_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether a class's methods are focused on a single responsibility.
Method: LCOM4 cohesion per production class with at least two methods: connected components of methods sharing state or calls, computed syntactically. Deterministic, not a proxy.
Coverage: Exhaustive · type-level: LCOM4 cohesion computed over every production class — the population is all types, not a name convention.
Resolve the 2 Low cohesion finding(s) in Cohesion (LCOM4) — start with LiveRenderContext.cs, Job.cs. — One of this dimension's main actionable groups (2 warning-level).
Enforce Cohesion (LCOM4) in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Verified — provenance only; does not change the score.
Detailed fixes: d6_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: How much of the code is actually exercised by tests.
Method: Coverage from coverlet runs or committed reports (Cobertura/OpenCover/lcov), computed per-file with structured exclusions for generated, trivial, and glue code. When the suite can't be built/run in-image AND no report is committed, coverage is reported NOT-MEASURED (excluded from the score) with the precondition to make it measurable — never a LoC-ratio proxy folded in as if measured. Deterministic.
No test project references Rask.Sitesrc/Rask.Site/Rask.Site.csproj
No test project references Fluxscripts/flux/Flux/Flux.csproj
No test project references KitBundlescripts/tools/KitBundle/KitBundle.csproj
No test project references Rask.Site.DataDemosrc/Rask.Site.DataDemo/Rask.Site.DataDemo.csproj
No test project references RaskRenamescripts/tools/RaskRename/RaskRename.csproj
What to do
Resolve the 1 No test project references Rask.Site finding(s) in Code Coverage — start with Rask.Site.csproj. — One of this dimension's main actionable groups (1 warning-level).
Resolve the 1 No test project references Flux finding(s) in Code Coverage — start with Flux.csproj. — One of this dimension's main actionable groups (1 warning-level).
Resolve the 1 No test project references KitBundle finding(s) in Code Coverage — start with KitBundle.csproj. — One of this dimension's main actionable groups (1 warning-level).
Enforce Code Coverage in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Verified — provenance only; does not change the score.
Detailed fixes: d8_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D9 · Test Distribution8.9 / 10Strong✓ Tool-verified
What it measures: Whether the test suite has a healthy mix of unit / integration / end-to-end tests.
Method: Test projects classified (Unit/Integration/BDD/E2E) from compiled metadata; test methods counted exhaustively across projects with placement-agnostic disk fallback. Deterministic.
13095 test methods: 11953 unit, 0 integration, 0 BDD, 1142 e2e.
What to do
Improve Test Distribution — currently 8.9/10. — 13095 test methods: 11953 unit, 0 integration, 0 BDD, 1142 e2e.
Detailed fixes: d9_recommendation.md.
Do you agree with this assessment?
D10 · Test Quality10.0 / 10Stronggated by 21 serious findings✓ 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.
1 skipped (1 with a documented reason), 13 zero-assertion, 5 synchronised by a fixed sleep, 2 depending on a live external host, 1 racing the wall clock, no mocking-framework packages referenced (hand-written doubles or no mocking) across 13033 tests. Measured on the C# suite only — at least 60 test source file(s) (.ts) went unread, so its test quality is unmeasured and is not in these counts.
No assertions: The_name_set_with_WithName_decides_the_client_method_name · ×13tests/Rask.Api.Client.Tests/MinimalApiRoundTripTests.cs:89
Depends on a live external host: Markdown_rules_the_heading_list_and_the_link_panel_shape_the_document · ×2tests/Rask.Site.E2E.Tests/UiKitEditorTests.cs:73
Races the wall clock: A_store_created_before_scopes_existed_is_migrated_rather_than_brokentests/Rask.Logging.Tests/LogScopeTests.cs:15
Resolve the 13 No assertions finding(s) in Test Quality — start with StateHasChangedTests.cs (2), ArrivalAfterHandlerTests.cs (2), MinimalApiRoundTripTests.cs. — One of this dimension's main actionable groups (13 warning-level).
Resolve the 5 Fixed-sleep synchronisation finding(s) in Test Quality — start with WatchHotReloadE2ETests.cs (3), AsyncLifecycleRenderingTests.cs, RaskSqliteExecutionStrategyTests.cs. — One of this dimension's main actionable groups (5 warning-level).
Resolve the 2 Depends on a live external host finding(s) in Test Quality — start with UiKitEditorTests.cs, WebApiTests.cs. — One of this dimension's main actionable groups (2 warning-level).
Enforce Test Quality in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
Detailed fixes: d10_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D11 · Test Reliability8.0 / 10Adequategated by 1 critical finding✓ Tool-verified
What it measures: Whether the tests pass reliably, with no flakiness.
Method: Suite re-run N times within tiered wall-clock budgets (unit to e2e); tests failing non-deterministically across runs flagged; guarded tests retried when #if guards detected.
Only 1 of 3 test tiers measured — the score covers those alone. 1 flaky across 1 measured tier(s). unit: not included — too large to re-run within its budget; e2e: not included — too large to re-run within its budget; other: measured (0 flaky).
Resolve the 1 Flaky test finding(s) in Test Reliability — start with HandlerFaultTests.cs. — One of this dimension's main actionable groups (1 issue-level).
Detailed fixes: d11_recommendation.md · top locations in Appendix A, every location in findings.md.
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.
Resolve the 2 Leaked secret finding(s) in Secret Scanning — start with REDACTED, REDACTED. — One of this dimension's main actionable groups (2 issue-level).
Enforce Secret Scanning in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
Detailed fixes: d13_recommendation.md · top locations in Appendix A, every location in findings.md.
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 143 packages use a banned license. ★ DEPTH: this repository's MSBuild projects declare 55 direct `PackageReference`(s), and 125 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.
Top hotspots: src/Rask.Core/Resources/rask-morph.ts (28×97=2716); REDACTED (36×45=1620); src/Rask.Server/Resources/rask.ts (62×26=1612) Repeated repair below the complexity floor: src/Rask.Core/Component.Handlers.cs (15 of 24 changes were fixes); src/Rask.Ui/UiTimePicker.cs (9 of 15 changes were fixes); src/Rask.Core/Resources/rask-owned.ts (8 of 15 changes were fixes)
Resolve the 29 Hotspot finding(s) in Churn × Complexity Hotspots — start with rask-morph.ts, REDACTED, rask.ts. — One of this dimension's main actionable groups (29 warning-level).
Resolve the 29 Repeated repair finding(s) in Churn × Complexity Hotspots — start with Component.Handlers.cs, UiTimePicker.cs, rask-owned.ts. — One of this dimension's main actionable groups (29 warning-level).
Detailed fixes: d15_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.
478 deducted debt markers + unmeasured dead symbols across 264979 LoC in the .NET projects (1.4/KLoC) → score 7.3. Dead code not measured: the solution did not load cleanly, so the reference search was skipped.
FileScopedPragmaDisable repeated across 119 filestests/Rask.Core.Tests/Authorization/HandlerAuthorizationTests.cs:10
+ 7 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Resolve the 61 FileScopedPragmaDisable finding(s) in Explicit Debt — start with ClassJoinChangeTests.cs, ClassJoinTests.cs, BuilderCallbackResetTests.cs. — One of this dimension's main actionable groups (61 issue-level).
Resolve the 27 EmptyCatchBlock finding(s) in Explicit Debt — start with REDACTED (7), DataChangesInterceptor.cs (3), DevStatusServer.cs (2). — One of this dimension's main actionable groups (27 issue-level).
Resolve the 18 NoWarnInCsproj finding(s) in Explicit Debt — start with Rask.Jobs.csproj (2), Directory.Build.props (2), Rask.Api.Generators.csproj. — One of this dimension's main actionable groups (18 issue-level).
Enforce Explicit Debt in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
Detailed fixes: d17_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether the solution is laid out in a sensible, conventional structure.
Method: Solution structure: project count, decomposition, shell-project detection, build success (confirmed failures cap the score); traced to actual .sln files and binaries. Deterministic.
141 projects, 8633 source files, 561877 hand-written lines of code (264979 production / 296898 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), 326 inter-project edges (build NOT measured — `dotnet build` did not complete in the analyzer, so the build half of this dimension is unmeasured rather than failed: the score above rests on structure alone and is not capped. The diagnostics that stopped it are named under Limitations.) Measured across 4 solutions loaded as one workspace: `Rask.slnx`, `src/Rask.Templates/server/Company.RaskServer.slnx`, `src/Rask.Templates/wasm-hosted/Company.RaskServer.slnx`, `src/Rask.Templates/wasm/Company.RaskServer.slnx`.
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. 99 document(s) read across 55 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.
Resolve the 1 No ADRs found finding(s) in ADR Quality. — One of this dimension's main actionable groups (1 recommendation-level).
Detailed fixes: d20_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D22 · Internal API Consistency9.1 / 10Stronggated by 2 serious findings✓ Tool-verified
What it measures: Whether the internal API surface is consistent and coherent.
Method: Call-shape rules (A1-A9) over the structured code model of the intentionally exposed C# surface: members of one type, overloads of one name and the same slot across sibling types are compared, and a member that makes a caller use a different convention for the same kind of operation is flagged. Deterministic, no model. Advisory.
2 API inconsistencies among 228 exposed members measured against a convention their peers follow.
`Files.Get` signals absence with a nullable value (null when absent) where its 3 sibling single-key reads use a plain value (absence must throw)src/Rask.Storage/Files.cs:45
`Push.Send` is awaitable while an overload of the same name is synchronoussrc/Rask.WebPush/Push.cs:20
What to do
Resolve the 1 `Files.Get` signals absence with a nullable value (null when absent)… finding(s) in Internal API Consistency — start with Files.cs. — One of this dimension's main actionable groups (1 warning-level).
Resolve the 1 `Push.Send` is awaitable while an overload of the same name is… finding(s) in Internal API Consistency — start with Push.cs. — One of this dimension's main actionable groups (1 warning-level).
Detailed fixes: d22_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether domain types (IDs, enums, value objects) leak across bounded-context boundaries.
Method: Cross-context domain-type leakage via Roslyn structural classification (strongly-typed IDs / value objects) over every public surface. Exhaustive, deterministic, type-level aggregate-boundary check.
Coverage: Bounded contexts derived from NAMESPACE prefix (or graph-inferred where available); cross-boundary domain-type leakage then checked exhaustively over every public member of every type.
4 domain type(s) cross context boundaries across 50 contexts; they are measured and withheld (not published, not scored). Contexts: Rask, Rask.Api.Client, Rask.Api.Generators, Rask.Auth, Rask.Batteries.Generators, Rask.Cache, Rask.Cli, Rask.Core, Rask.Cqrs, Rask.Cqrs.Client, Rask.Cqrs.Server, Rask.Dashboard and 38 more.
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.
Detailed fixes: d26_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D27 · Navigability8.2 / 10Strong✓ Tool-verified
What it measures: How far you must trace to follow a call — low indirection and co-located slices read easier.
Method: Call indirection (interface hops, cross-namespace calls, slice-locality scaled) over a sampled set of method invocations, size-aware baseline. Sampled; confidence discounted by symbol-resolution gaps. C# also names each pass-through layer (a class whose every public method only forwards its own parameters to one collaborator) as a located finding; the score is not affected.
Coverage: Slice locality from the first namespace segments, SAMPLED (≤400 methods) — not exhaustive.
67 % of calls cross a namespace and 6 % go through an interface, but 91 % of collaborators are co-located — so a call's collaborators sit together and tracing stays easy. Baseline: large — vertical-slice locality expected.
What to do
Improve Navigability — currently 8.2/10. — 67 % of calls cross a namespace and 6 % go through an interface, but 91 % of collaborators are co-located — so a call's collaborators sit together and tracing stays easy. Baseline: large — vertical-slice locality expected.
What it measures: 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).
85 finding(s): 0 critical, 46 high, 39 medium, 0 low. 33 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 623 file(s) — `.claude/skills/run-rask/dashboard-driver.cs` (line 1, line 2), `.claude/skills/run-rask/driver.cs` (line 1, line 2), `.claude/skills/run-rask/fitprobe.cs` (line 1, line 2), `.claude/skills/run-rask/frameprobe.cs` (line 1, line 2), `.claude/skills/run-rask/growprobe.cs` (line 1, line 2), … (+618 more) — so no absence of findings in the named regions is evidence of anything; rows reported elsewhere in those files are real. Fix the syntax error (or exclude the file deliberately) and re-scan to cover them. In 400 of those file(s) — `scripts/flux/Flux/Commands/ParityCarousel.cs`, `scripts/flux/Flux/Commands/ParityChart.cs`, `scripts/flux/Flux/Commands/ParityEditor.cs`, `scripts/flux/Flux/Lib/Args.cs`, `scripts/flux/Flux/Lib/FluxCommand.cs`, … (+395 more) — the break is a C# primary constructor, which semgrep's grammar cannot parse and which hides the type from every rule scoped to it; those files were re-scanned from a shadow copy with the constructor's parameter list blanked (line and column preserving), which restores the type to the rules, and 0 additional row(s) came from that pass. Only the header's own parameter list is unread in them. In 21 of those file(s) — `scripts/flux/Flux/Commands/Flags.cs`, `scripts/flux/Flux/Commands/ParityColorPicker.cs`, `scripts/flux/Flux/Commands/Refresh.cs`, `scripts/tools/KitBundle/Upstream.cs`, `src/Rask.Cli/Commands/DbCommand.cs`, … (+16 more) — the break is at a TYPE DECLARATION (a C# primary constructor semgrep's grammar cannot parse), so the loss is wider than the named lines: rules scoped to that type see no type to scope to and are blind over its whole body, while rules matching statements keep working there. Absence of a type-scoped finding in those types is not evidence of anything. Separately, one or more rules could not re-parse an embedded snippet in 1 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
+ 8 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Resolve the 5 REDACTED finding(s) charged to Static Analysis (SAST) — the other 33 are reported here at file:line but scored by D36 (supply-chain provenance), which charges them once. — One of this dimension's main actionable groups (38 issue-level, 5 of them charged here).
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 1 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
Detailed fixes: d29_recommendation.md · top locations in Appendix A, every location in findings.md.
Resolve the 1 High IaC finding(s) in IaC & Container Security — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
Resolve the 7 Medium IaC finding(s) in IaC & Container Security — start with REDACTED (7). — One of this dimension's main actionable groups (7 warning-level).
Resolve the 3 Low IaC finding(s) in IaC & Container Security — start with REDACTED (3). — One of this dimension's main actionable groups (3 recommendation-level).
Detailed fixes: d31_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.
Every significant source file has living knowledge — recently and meaningfully worked. Counted over 1385 of the 3106 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.
What it measures: Whether files that change together actually belong together — pairs that repeatedly co-change in git history despite having no explicit code dependency, surfacing the hidden/logical coupling (and boundaries in the wrong place) a static scan can't see.
Method: Pairwise co-occurrence over the per-commit file sets in git history (production source only — tests and generated dropped): Degree-of-Coupling = shared ÷ min individual revisions, reported above noise floors (each file ≥10 revisions, ≥5 shared commits, ≥50% strength); sweeping commits excluded. Deterministic over fixed history.
Coverage: Population: PRODUCTION source files only — test and generated files are dropped before pairing, so a class co-changing with its own test (trivially ~100%) can't drown the real production↔production coupling. Pairs ranked by Degree-of-Coupling. A non-source file is never a coupling PARTICIPANT either: documentation, schemas, config and data files are dropped with the rest, so a code↔docs pair — a command and the reference page that restates it — is not reported however strongly the two co-change; nor is coupling that runs THROUGH a build step or config file.
Resolve the 4 Change coupling finding(s) in Change Coupling — start with RaskBrowserJsonContext.cs, rask-hook-loader.ts, ProjectGenerator.Server.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.
What it measures: Whether the repository publishes a coordinated-vulnerability-disclosure policy (SECURITY.md or security.txt) with a reporting contact, so finders know how to report a vulnerability. Presence of a policy file with a contact, not whether the policy is adequate or honoured.
Method: Vulnerability-disclosure policy read deterministically from the repo: a SECURITY.md (root/.github/docs) or .well-known/security.txt / security.txt, regex-checked for a reporting contact (email / URL / mailto). Present + contact → 10; present without a contact → 4; NotApplicable when no policy file exists (it may live off-repo). Detects the policy file's presence + contact, not its adequacy.
A vulnerability-disclosure policy (.github/SECURITY.md) is published with a reporting contact.
✓ On the Gold path — maintain.
Detailed fixes: d37_recommendation.md.
Do you agree with this assessment?
D39 · IL Efficiency9.9 / 10Exemplary✓ Tool-verified
Method: IL instruction count per method, read from the BUILT first-party assemblies via Mono.Cecil (the target is compiled on a deep run); scored on the fraction of methods whose emitted IL body exceeds the size threshold. Sees compiler-generated bloat source can't; not-applicable when the target fails to build. Deterministic.
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 134 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.
No <main> (or role="main") means no "skip to content" target and a weaker landmark map. Wrap the primary content in <main>. (×7) — assets/og-card.html:2, src/Rask.Site.DataDemo/wwwroot/index.html:2, src/Rask.Site/wwwroot/index.html: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 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.
`.rask-boot .rask-spin` moves (`animation: rask-spin 0.8s linear infinite`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce. (×4) — src/Rask.Site/wwwroot/index.html:59, src/Rask.Templates/wasm-hosted/Client/wwwroot/index.html:48, src/Rask.Templates/wasm/wwwroot/index.html:50, …
`.rask-boot__fill` moves (`transition: width 0.2s ease`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce. (×2) — src/Rask.Site/wwwroot/index.html:85, src/Rask.Wasm/Browser/index.html:131
`:where([data-ui-date-picker], [data-ui-time-picker], [data-ui-color-picker-trigger], [data-ui-pillbox-trigger]) :where(input, [role="spinbutton"], [contenteditable]):not([data-ui-control]):focus-visible` 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/Rask.Ui/Styles/ui.css:1124
`[data-ui-editor] [data-slot="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. — src/Rask.Ui/Styles/ui.css:1311
`[data-ui-editor] [data-slot="content"] :focus-visible` 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/Rask.Ui/Styles/ui.css:1316
`[data-ui-toast] > [data-ui-toast-dialog]` moves (`transition: opacity 0.2s ease allow-discrete,
transform 0.2s ease allow-discrete,
height 0.2s ease allow-discrete`) 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/Rask.Ui/Styles/ui.css:900
`[data-ui-toast] > [data-ui-toast-dialog]` moves (`animation: ui-toast-fade 0.2s ease,
ui-toast-rise 0.35s ease`) 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/Rask.Ui/Styles/ui.css:904
`[data-ui-toast] > [data-ui-toast-dialog][data-rask-dismiss-after]` moves (`animation: ui-toast-fade 0.2s ease,
ui-toast-rise 0.35s ease,
ui-toast-leave 0.35s ease var(--ui-toast-duration) forwards`) 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/Rask.Ui/Styles/ui.css:910
`[data-ui-toast-group] > [data-ui-toast-dialog]` moves (`transition: opacity 0.35s ease allow-discrete,
transform 0.35s ease allow-discrete,
height 0.35s ease allow-discrete`) 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/Rask.Ui/Styles/ui.css:920
`[data-ui-toast-group] > [data-ui-toast-dialog] > :first-child` moves (`transition: opacity 0.35s ease allow-discrete,
transform 0.35s ease allow-discrete,
height 0.35s ease allow-discrete`) 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/Rask.Ui/Styles/ui.css:946
`[data-ui-toast-group] > [data-ui-toast-dialog] > :first-child` moves (`animation: ui-toast-fade 0.35s ease,
ui-toast-rise 0.35s ease`) 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/Rask.Ui/Styles/ui.css:950
`[data-ui-toast-group] > [data-ui-toast-dialog][data-rask-dismiss-after] > :first-child` moves (`animation: ui-toast-fade 0.35s ease,
ui-toast-rise 0.35s ease,
ui-toast-lift 0.35s ease var(--ui-toast-duration) forwards`) 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/Rask.Ui/Styles/ui.css:956
`[data-ui-accordion][data-transition] > [data-ui-accordion-item]::details-content` moves (`transition: height 250ms cubic-bezier(0.4, 0, 0.2, 1),
content-visibility 250ms allow-discrete,
overflow 0s allow-discrete`) 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/Rask.Ui/Styles/ui.css:1162
`[data-ui-accordion][data-transition] > [data-ui-accordion-item][open]::details-content` moves (`transition: height 250ms cubic-bezier(0.4, 0, 0.2, 1),
content-visibility 250ms allow-discrete,
overflow 0s 250ms allow-discrete`) 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/Rask.Ui/Styles/ui.css:1170
`.guide-prevnext-link` moves (`transition: border-color .12s ease, box-shadow .12s ease, transform .12s ease`) 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/Rask.Site/Shared/GuideChrome.css:208
`box.animate()` moves (`Web Animations API keyframes`) 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/Rask.DevTools/Resources/host/flash.ts:112
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.
Do you agree with this assessment?
AC7 · A11y enforcement4.0 / 10Weak✓ Tool-verified
Other · Accessibility — Whether accessibility is ENFORCED in the toolchain — an accessibility checker configured over the markup (an a11y lint rule set, e.g. eslint-plugin-jsx-a11y or vuejs-accessibility where the project lints JavaScript) and an automated accessibility assertion wired into tests or CI (axe/pa11y/Lighthouse or an equivalent) — on the Documented→Verified→Prevented ladder.
Method: Repo config/CI scan: an accessibility checker configured over the markup (an a11y lint rule set such as eslint-plugin-jsx-a11y / vuejs-accessibility where JavaScript is linted) and an automated accessibility assertion in tests or CI (axe/pa11y/Lighthouse or equivalent), graded on the Documented→Verified→Prevented rungs. Deterministic, presence/rung detection.
Coverage: Population: the repository's own tooling configuration — lint config, test and CI files — NOT the markup. It is read for a configured accessibility checker and an automated accessibility assertion (axe/pa11y/Lighthouse, or a native-toolkit equivalent), and it credits an INVOCATION, never a mention: a licence filename, an import comment or a doc reference earns no rung. Enforcement configured entirely outside the repository leaves no evidence here and cannot be credited.
No accessibility enforcement found — no automated accessibility check runs over the HTML your app renders. Assert the accessibility invariants over that HTML in the test suite you already have (parse the output and assert, or drive a browser), and gate that test in CI so a regression blocks the merge. What was searched, so you can tell an absence from a miss: the 7 markup file(s) this pass actually assessed, the linter configuration checked in beside them, and this repository's test and CI files — matched by name against the accessibility checkers this dimension carries. An audit run outside the repository, a hosted scanner, or a check whose name is not one of those, is not seen here.
What to do
Enforce accessibility in the test suite you already have: assert the accessibility invariants over the HTML your app renders — parse the rendered output in an existing test, or drive a real browser from one — and gate that test in CI so a regression blocks the merge.
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.
`SessionKept` is registered as a SINGLETON but its constructor takes `Type Type`, which is registered as Scoped. The singleton captures one instance of the scoped dependency forever — defeating its lifetime (a per-request DbContext shared across all requests is a classic data-corruption/threading bug). Make the singleton resolve `Type` per-use (inject `IServiceScopeFactory` or a factory func), or align the lifetimes. — src/Rask.Core/Live/SessionKept.cs:4
`RaskMountedApp` is registered as a SINGLETON but its constructor takes `Type root`, which is registered as Scoped. The singleton captures one instance of the scoped dependency forever — defeating its lifetime (a per-request DbContext shared across all requests is a classic data-corruption/threading bug). Make the singleton resolve `Type` per-use (inject `IServiceScopeFactory` or a factory func), or align the lifetimes. — src/Rask.Core/Routing/RaskMountedApp.cs:37
`AmbientContextBinding` is registered as a SINGLETON but its constructor takes `Type contextType`, which is registered as Scoped. The singleton captures one instance of the scoped dependency forever — defeating its lifetime (a per-request DbContext shared across all requests is a classic data-corruption/threading bug). Make the singleton resolve `Type` per-use (inject `IServiceScopeFactory` or a factory func), or align the lifetimes. — src/Rask.Data/AmbientContextBinding.cs:18
`Navigator` is registered as a SINGLETON but its constructor takes `RouteState routeState`, which is registered as Scoped. The singleton captures one instance of the scoped dependency forever — defeating its lifetime (a per-request DbContext shared across all requests is a classic data-corruption/threading bug). Make the singleton resolve `RouteState` per-use (inject `IServiceScopeFactory` or a factory func), or align the lifetimes. — src/Rask.Core/Routing/Navigator.cs:21
`Navigator` is registered as a SINGLETON but its constructor takes `IDownloadSink downloadSink`, which is registered as Scoped. The singleton captures one instance of the scoped dependency forever — defeating its lifetime (a per-request DbContext shared across all requests is a classic data-corruption/threading bug). Make the singleton resolve `IDownloadSink` per-use (inject `IServiceScopeFactory` or a factory func), or align the lifetimes. — src/Rask.Core/Routing/Navigator.cs:21
Building the SINGLETON `IPersistentState` resolves `PersistentState`, registered as Scoped, from the provider it was handed — the ROOT provider, outside any scope. The root provider keeps that instance for the life of the process, so the singleton is handed one scoped `PersistentState` forever (ASP.NET Core's scope validation rejects it in Development and lets it through in Production). Create a scope per use (`IServiceScopeFactory.CreateScope()`) and resolve `PersistentState` from the scope's provider, or align the lifetimes. — src/Rask.Wasm/WasmHostBuilder.cs:45
`WasmUserWatch` is registered as a SINGLETON but its constructor takes `IUserProvider users`, which is registered as Scoped. The singleton captures one instance of the scoped dependency forever — defeating its lifetime (a per-request DbContext shared across all requests is a classic data-corruption/threading bug). Make the singleton resolve `IUserProvider` per-use (inject `IServiceScopeFactory` or a factory func), or align the lifetimes. — src/Rask.Wasm/Authentication/WasmUserWatch.cs:29
`WasmAuthSignIn` is registered as a SINGLETON but its constructor takes `IUserProvider userProvider`, which is registered as Scoped. The singleton captures one instance of the scoped dependency forever — defeating its lifetime (a per-request DbContext shared across all requests is a classic data-corruption/threading bug). Make the singleton resolve `IUserProvider` per-use (inject `IServiceScopeFactory` or a factory func), or align the lifetimes. — src/Rask.Wasm/Authentication/WasmAuthSignIn.cs:17
What to do
Don't inject scoped/transient services into singletons; resolve them per-use via IServiceScopeFactory or a factory delegate, or align the lifetimes.
Other · Architecture — How the codebase splits by code ROLE — domain, application, infrastructure, test, generated. The significance map behind the knowledge/coupling weighting, and a DDD signal in its own right: a thin domain core under fat infrastructure is the anemic-domain smell, quantified. How each file's role is decided, because the split is only as good as that: a generated name or a build-output tree makes it Generated, a test project makes it Test, and otherwise the file's NAMESPACE and PATH words are matched against fixed vocabularies in a fixed ORDER — domain, then infrastructure, then application — so a file whose words hit two layers is counted under the earlier one. A production file matching none of them counts as application, so that share reads 'application or unclassified' rather than a measured application layer. Roles come from naming convention, never from what the code does.
Method: Roslyn line-count by code ROLE: every source file classified Domain/Application/Infrastructure/Test/Generated by namespace + path convention (the shared CodeRoleClassifier), then significant lines summed per role. Deterministic; the advisory score is the business-logic (domain+application) share of production code.
Coverage: Population: ALL source files, each bucketed into ONE of five roles (Domain/Application/Infrastructure/Test/Generated) by namespace + path convention — a file whose layer isn't named in the convention falls to Application (the neutral default), and the split is line-count, not semantic depth or business value.
What to do
The domain core is a small share of production code, but most of the rest matched no layer vocabulary at all — so this is not yet an anemic-domain finding. The namespace/path convention could not place that code, which makes the composition above a statement about the naming, not about the design. Name the layers (or check that the repository's conventions differ from the ones this check knows) before reading a thin domain into it.
Other · Architecture — Whether singleton services avoid mutable shared instance state that concurrent callers would race on.
Method: Roslyn scan: singleton field mutations unguarded by lock or Interlocked, per type; syntax-based guard detection. Deterministic, traceable per field.
`ApiClientOptions` is a singleton (one shared instance) but mutates instance state outside any lock (_timeout; e.g. `_timeout` at line 41). — src/Rask.Api.Client/ApiClientOptions.cs:6
`AuthClientOptions` is a singleton (one shared instance) but mutates instance state outside any lock (_prefix; e.g. `_prefix` at line 27). — src/Rask.Auth.Client/AuthClientOptions.cs:6
`HttpUserProvider` is a singleton (one shared instance) but mutates instance state outside any lock (IsLoading, _loaded, _current; e.g. `IsLoading` at line 59). — src/Rask.Auth.Client/HttpUserProvider.cs:25
`EventScopeCatalog` is a singleton (one shared instance) but mutates instance state outside any lock (_owned; e.g. `_owned` at line 69). — src/Rask.Core/Live/EventScopeCatalog.cs:15
`DashboardSecurityState` is a singleton (one shared instance) but mutates instance state outside any lock (UsingFallbackPolicy, FallbackIsOpen; e.g. `UsingFallbackPolicy` at src/Rask.Dashboard/RaskDashboardServiceCollectionExtensions.cs line 127, through the shared instance). — src/Rask.Dashboard/DashboardSecurityState.cs:12
`DevToolsServerEndpoints` is a singleton (one shared instance) but mutates instance state outside any lock (PanelScriptUrl, _prefixUnderBase, _hostScriptUrl, _panelUrl, _allowRemote; e.g. `PanelScriptUrl` at line 107). — src/Rask.DevTools/Endpoints/DevToolsServerEndpoints.cs:18
`RouteState` is a singleton (one shared instance) but mutates instance state outside any lock (_path, _query, _forbidden, _split; e.g. `_path` at line 40). — src/Rask.Core/Routing/RouteState.cs:19
`Navigator` is a singleton (one shared instance) but mutates instance state outside any lock (_exit, _replace, _dirty, _redirected, _redirects, _inInitialRender; e.g. `_exit` at line 190). — src/Rask.Core/Routing/Navigator.cs:21
`BatteryTablesExtension` is a singleton (one shared instance) but mutates instance state outside any lock (_info; e.g. `_info` at line 15). — src/Rask.Server/App/BatteryTablesExtension.cs:9
`ServerPrintablePages` is a singleton (one shared instance) but mutates instance state outside any lock (_selector, _pathBase; e.g. `_selector` at line 33). — src/Rask.Server/Printing/ServerPrintablePages.cs:24
`RaskDrainService` is a singleton (one shared instance) but mutates instance state outside any lock (_stoppingRegistration, _announce; e.g. `_stoppingRegistration` at line 59). — src/Rask.Server/RaskDrainService.cs:24
`BrowserSqliteOptions` is a singleton (one shared instance) but mutates instance state outside any lock (DatabasePath; e.g. `DatabasePath` at line 77). — src/Rask.SQLite.Browser/BrowserSqliteOptions.cs:4
`BrowserSqliteOwnership` is a singleton (one shared instance) but mutates instance state outside any lock (IsOwner; e.g. `IsOwner` at line 70). — src/Rask.SQLite.Browser/BrowserSqliteOwnership.cs:24
`SqliteSnapshotOptions` is a singleton (one shared instance) but mutates instance state outside any lock (DatabasePath; e.g. `DatabasePath` at src/Rask.SQLite.Snapshots/SqliteSnapshotsServiceCollectionExtensions.cs line 43, through the shared instance). — src/Rask.SQLite.Snapshots/SqliteSnapshotOptions.cs:7
`BrowserSqliteHost` is a singleton (one shared instance) but mutates instance state outside any lock (IsOwner, _takeoverWatch, _ownerHold; e.g. `IsOwner` at line 79). — src/Rask.SQLite.Browser/BrowserSqliteHost.cs:36
`RouteState` is a singleton (one shared instance) but mutates instance state outside any lock (_path, _query, _forbidden, _split, Languages; e.g. `_path` at line 40). — src/Rask.Core/Routing/RouteState.cs:19
`PersistentState` is a singleton (one shared instance) but mutates instance state outside any lock (_bytes, _entries, Version, Overflowed; e.g. `_bytes` at line 119). — src/Rask.Core/Live/PersistentState.cs:19
`WasmDownloadSink` is a singleton (one shared instance) but mutates instance state outside any lock (_order, _pending; e.g. `_order` at line 32). — src/Rask.Wasm/Files/WasmDownloadSink.cs:10
`WasmJSRuntime` is a singleton (one shared instance) but mutates instance state outside any lock (_host; e.g. `_host` at line 67). — src/Rask.Wasm/JSInterop/WasmJSRuntime.cs:27
`WasmUserWatch` is a singleton (one shared instance) but mutates instance state outside any lock (_asking, HasEnded; e.g. `_asking` at line 70). — src/Rask.Wasm/Authentication/WasmUserWatch.cs:29
`IndexedDbSnapshotStore` is not registered, but the singleton `BrowserSqliteHost` creates it and keeps it in `_store`, so one instance outlives every request and is shared by every caller that reaches it — and it mutates instance state outside any lock (_store; e.g. `_store` at line 110). — src/Rask.SQLite.Browser/IndexedDbSnapshotStore.cs:17
`RouteTitle` is not registered, but the singleton `RouteState` creates it and keeps it in `_title`, so one instance outlives every request and is shared by every caller that reaches it — and it mutates instance state outside any lock (_walked, _readers, _value; e.g. `_walked` at line 18). — src/Rask.Core/Routing/RouteTitle.cs:6
`Lazy` is not registered, but `RaskEndpointExtensions` creates it and keeps it in the static `RuntimeHash`, 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 (_inView; e.g. `_inView` at line 51). — src/Rask.Core/Components/Lazy.cs:20
`WasmLiveSession` is not registered, but `WasmHostBuilder` creates it and keeps it in the static `JSInterop._session`, 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 (_navigator, _guardedTo, _lastBuildHadJsInvokes; e.g. `_navigator` at line 178). — src/Rask.Wasm/WasmLiveSession.cs:19
`WasmHostedServices` is not registered, but `WasmHostBuilder` creates it and keeps it in the static `JSInterop._hostedServices`, 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 (_started, _stopped; e.g. `_started` at line 77). — src/Rask.Wasm/WasmHostedServices.cs:26
`DevToolsTreeCapture` is not registered, but the singleton `DevToolsFeed` creates it and keeps it in `_capture`, so one instance outlives every request and is shared by every caller that reaches it — and it mutates instance state outside any lock (Root, ItemCount, _items, HasContexts, _provideCount, _provides; e.g. `Root` at line 52). — src/Rask.DevTools/Probe/DevToolsTreeCapture.cs:21
`AccountName` 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 (_last; e.g. `_last` at line 104). Concurrent callers lose updates, and a collection that is not built for concurrent writers can corrupt. — src/Rask.Auth.Api/AccountName.cs:17
`AuthUser` 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 (Binding; e.g. `Binding` at line 47). Concurrent callers lose updates, and a collection that is not built for concurrent writers can corrupt. — src/Rask.Auth.Api/AuthUser.cs:25
`RaskCulture` 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 (IsEnabled; e.g. `IsEnabled` at line 164). Concurrent callers lose updates, and a collection that is not built for concurrent writers can corrupt. — src/Rask.Core/Globalization/RaskCulture.cs:25
`RaskStrings` 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 (Source, _libraries; e.g. `Source` at line 47). Concurrent callers lose updates, and a collection that is not built for concurrent writers can corrupt. — src/Rask.Core/Globalization/RaskStrings.cs:27
`FrameSinkScope` 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 (Current; e.g. `Current` at line 19). Concurrent callers lose updates, and a collection that is not built for concurrent writers can corrupt. — src/Rask.Core/Live/FrameSinkScope.cs:12
`LiveOptions` 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 (_pathBase; e.g. `_pathBase` at line 68). Concurrent callers lose updates, and a collection that is not built for concurrent writers can corrupt. — src/Rask.Core/Live/LiveOptions.cs:14
`ScopedScript` 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 (Options; e.g. `Options` at line 208). Concurrent callers lose updates, and a collection that is not built for concurrent writers can corrupt. — src/Rask.Core/ScopedAssets/ScopedScript.cs:24
`Dispatcher` 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 (_root; e.g. `_root` at line 56). Concurrent callers lose updates, and a collection that is not built for concurrent writers can corrupt. — src/Rask.Cqrs/Dispatcher.cs:23
`CurrentRows` 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 (_tenant, _user; e.g. `_tenant` at line 56). Concurrent callers lose updates, and a collection that is not built for concurrent writers can corrupt. — src/Rask.Data/CurrentRows.cs:23
`Db` 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 (_factory; e.g. `_factory` at line 84). Concurrent callers lose updates, and a collection that is not built for concurrent writers can corrupt. — src/Rask.Data/Db.cs:41
`ModelRegistry` 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 (_appModel; e.g. `_appModel` at line 90). Concurrent callers lose updates, and a collection that is not built for concurrent writers can corrupt. — src/Rask.Data/ModelRegistry.cs:27
`ReadDb` 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 (_factory; e.g. `_factory` at line 52). Concurrent callers lose updates, and a collection that is not built for concurrent writers can corrupt. — src/Rask.Data/ReadDb.cs:23
`DevToolsProbe` 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 (t_walkBuffer, t_walk, t_rendersBuffer, t_renders, t_walkStart, t_providesBuffer; e.g. `t_walkBuffer` at line 109). Concurrent callers lose updates, and a collection that is not built for concurrent writers can corrupt. — src/Rask.DevTools/Probe/DevToolsProbe.cs:34
`JSInterop` 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 (_session, _hostedServices, _runtime, ModuleImportOrder, _seq, HotReloadAppliedCount; e.g. `_session` at line 34). Concurrent callers lose updates, and a collection that is not built for concurrent writers can corrupt. — src/Rask.Wasm/JSInterop.cs:18
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 Rask ↔ Rask.Auth ↔ Rask.Background ↔ Rask.Caching ↔ Rask.Core ↔ Rask.Core.Browser ↔ Rask.Core.Components ↔ Rask.Core.Diagnostics.DevTools ↔ Rask.Core.DragAndDrop ↔ Rask.Core.Forms ↔ Rask.Core.Globalization ↔ Rask.Core.HeadAssets ↔ Rask.Core.Live ↔ Rask.Core.Messaging ↔ Rask.Core.Routing ↔ Rask.Core.ScopedAssets ↔ Rask.Data ↔ Rask.Logging ↔ Rask.Mailing ↔ Rask.Outbox ↔ Rask.Querying ↔ Rask.SQLite ↔ Rask.Server ↔ Rask.Server.Authentication ↔ Rask.Server.Diagnostics ↔ Rask.Server.Files ↔ Rask.Server.Http ↔ Rask.Server.JSInterop ↔ Rask.Server.Prerender ↔ Rask.Storage ↔ Rask.Storage.Backends ↔ Rask.Storage.Serving ↔ Rask.Wasm ↔ Rask.WebPush depend on each other. The lightest dependency in the cycle is Rask → Rask.Auth (Rask.RaskAppOptions → Rask.Auth.AuthOptions, 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/Rask.Server/App/RaskAppOptions.cs:2
The namespaces Rask.Batteries.Generators ↔ Rask.Generators.Shared depend on each other. The lightest dependency in the cycle is Rask.Generators.Shared → Rask.Batteries.Generators (Rask.Generators.Shared.ReadRelationship → Rask.Batteries.Generators.EquatableArray, 2 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/Rask.Generators.Shared/ReadRelationship.cs:1
The namespaces Rask.Cli ↔ Rask.Cli.Scaffolding depend on each other. The lightest dependency in the cycle is Rask.Cli.Scaffolding → Rask.Cli (Rask.Cli.Scaffolding.DeployConfig → Rask.Cli.IConsole, 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/Rask.Cli/Scaffolding/DeployConfig.cs:12
The namespaces Rask.Site ↔ Rask.Site.Features depend on each other. The lightest dependency in the cycle is Rask.Site → Rask.Site.Features (Rask.Site.GuideCards → Rask.Site.Features.GuideEntry, 2 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/Rask.Site/Shared/GuideCards.cs:2
What to do
Break namespace cycles inside a project by moving the shared type to a namespace both sides can use, or by inverting the back edge behind an interface.
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.
`IRenderHandle` declares 17 members: `RequestRender`, `RequestPublishRender`, `Asked`, `RenderInScopeAsync`, `HandlerStarted`, `HandlerEnded`, `HandlerRepaintBudget`, `IsDevelopment`, `RunInOrder`, `TryNavigate`, `ReportDevError`, `Engine`, `Culture`, `UICulture`, `HasCulture`, `PendingBinds`, `HeardValues`. Counted as the author wrote them — a property is ONE member and its get/set accessors are not counted separately, and an event counts once. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces. — src/Rask.Core/Live/IRenderHandle.cs:3
`IQueryClient` declares 22 members under just 9 distinct name(s): `Query`, `Query`, `Query`, `Query`, `Load`, `Warm`, `Send`, `Send`, `Command`, `Command`, `Command`, `Subscribe`, `Subscribe`, `Subscribe`, `Subscribe`, `Invalidate`, `Invalidate`, `Invalidate`, `Invalidate`, `InvalidateAll`, `Set`, `Set`. Counted as the author wrote them — a property is ONE member and its get/set accessors are not counted separately, and an event counts once. That is an OVERLOAD SET, not 22 separate responsibilities: a caller binds to 9 operation(s) and uses the overload it selected, so the Interface-Segregation harm does NOT apply on the caller's side and splitting this into role-interfaces would scatter one operation without relieving anything. The burden that does remain is the IMPLEMENTER's — all 22 signatures must be written and kept in step. Reduce it by collapsing overloads (optional or default parameters, or an options object) rather than by segregating the interface. — src/Rask.Query/IQueryClient.cs:19
What to do
Split fat interfaces into focused role-interfaces so clients depend only on what they use.
Where the width is an overload set rather than separate responsibilities, collapse the overloads instead — segregating those relieves no caller.
Do you agree with this assessment?
AX7 · Slice cohesion4.3 / 10Weak✓ Tool-verified
Other · Architecture — Whether feature slices stay independent (no direct cross-slice references) — the discipline that makes vertical-slice architecture pay off.
Method: Roslyn scan (vertical-slice gated): feature slices resolved from namespaces (.Features.*, .Slices.*) or project names; cross-slice type references detected. Deterministic, traceable.
`ElementsFormsDemo` (slice 'Elements') depends on `ElementsFormsDemo.Fields` from slice 'Events'. — src/Rask.Site/Features/Elements/ElementsFormsDemo.cs:11
`EventsFormDemo` (slice 'Events') depends on `EventsFormDemo.Fields` from slice 'Elements'. — src/Rask.Site/Features/Events/EventsFormDemo.cs:10
`LlmsText` (slice 'Guides') depends on `UiDocsCatalog` from slice 'UiDocs'. — src/Rask.Site/Features/Guides/LlmsText.cs:105
`HomePage` (slice 'Home') depends on `GuideCatalog` from slice 'Guides'. — src/Rask.Site/Features/Home/HomePage.cs:324
`CartModel` (slice 'NestedForms') depends on `LineItem` from slice 'Orders'. — src/Rask.Site/Features/NestedForms/CartModel.cs:5
`NestedListForeachDemo` (slice 'NestedForms') depends on `LineItem` from slice 'Orders'. — src/Rask.Site/Features/NestedForms/NestedListForeachDemo.cs:11
`MasterDetailDemo` (slice 'Orders') depends on `MasterDetailDemo.LineItem` from slice 'NestedForms'. — src/Rask.Site/Features/Orders/MasterDetailDemo.cs:180
`TagsFormDemo` (slice 'Tags') depends on `TagsFormDemo.Fields` from slice 'Elements'. — src/Rask.Site/Features/Tags/TagsFormDemo.cs:6
`UiKitActionsPage` (slice 'UiKit') depends on `UiDocsCatalog` from slice 'UiDocs'. — src/Rask.Site/Features/UiKit/UiKitActionsPage.cs:20
`UiKitDataDisplayPage` (slice 'UiKit') depends on `UiDocsCatalog` from slice 'UiDocs'. — src/Rask.Site/Features/UiKit/UiKitDataDisplayPage.cs:22
`UiKitDataGridPage` (slice 'UiKit') depends on `UiDocsCatalog` from slice 'UiDocs'. — src/Rask.Site/Features/UiKit/UiKitDataGridPage.cs:19
`UiKitDataInputPage` (slice 'UiKit') depends on `UiDocsCatalog` from slice 'UiDocs'. — src/Rask.Site/Features/UiKit/UiKitDataInputPage.cs:20
`UiKitFeedbackPage` (slice 'UiKit') depends on `UiDocsCatalog` from slice 'UiDocs'. — src/Rask.Site/Features/UiKit/UiKitFeedbackPage.cs:20
`UiKitLayoutPage` (slice 'UiKit') depends on `UiDocsCatalog` from slice 'UiDocs'. — src/Rask.Site/Features/UiKit/UiKitLayoutPage.cs:20
`UiKitMovedPages` (slice 'UiKit') depends on `UiDocsEntry` from slice 'UiDocs'. — src/Rask.Site/Features/UiKit/UiKitMovedPages.cs:12
`UiKitNavigationPage` (slice 'UiKit') depends on `UiDocsCatalog` from slice 'UiDocs'. — src/Rask.Site/Features/UiKit/UiKitNavigationPage.cs:20
What to do
Keep slices independent: share cross-slice needs via an explicit contract/shared-kernel, not direct references between slices.
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.
Other · Architecture — Whether read (query) handlers stay side-effect-free — a query that writes persistent state or raises events breaks CQS and makes reads unsafe to retry, cache, or route to a read replica.
Method: Roslyn scan: CQRS handlers classified query-vs-command by interface (IQueryHandler/ICommandHandler/IRequestHandler<TQuery,TResult>) and name convention (*Query/Get*/Find* vs *Command); each query handler's body checked for persistent-state writes (SaveChanges/repository Add-Update) or event publishes by resolved invocation. Deterministic, type-level, exhaustive over the detected handlers.
Coverage: Population: CQRS handlers identified by IQueryHandler/ICommandHandler/IRequestHandler interface + *Query/Get*/Find*/*Command NAME convention; query purity then checked exhaustively within that set — a query handler using neither convention is invisible, and mutation is a resolved persistence/publish CALL, not full dataflow.
Do you agree with this assessment?
C1 · Data Protection6.5 / 10Adequate✓ Tool-verified
Other · Security — Whether sensitive data is encrypted at rest and in transit and keys are vaulted.
Method: Roslyn plus filesystem scan: encryption presence (EF ColumnEncryption, key-vault references, HTTPS enforcement) and key-derivation KDF detection. Deterministic.
What to do
Strengthen data-at-rest protection: vault your keys (Azure Key Vault / AWS KMS / IDataProtector key ring) and encrypt the most sensitive columns (EF HasConversion encryption or provider-native column encryption) — partial coverage still leaves gaps.
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.
Do you agree with this assessment?
C3 · Audit Trail7.5 / 10Strong✓ Tool-verified
Other · Security — Whether changes to sensitive data are recorded (who, what, when) for compliance + incident response.
An audit mechanism is present, but the trail is not yet complete — missing: an immutable audit-log / audit-trail type to write to, [Audited] per-entity coverage.
What to do
Back the audit convention with a structural mechanism: an EF SaveChanges interceptor (or equivalent) writing every sensitive change to an immutable audit log, and apply [Audited] to the entities that need a who-changed-what trail.
Do you agree with this assessment?
C4 · Data Retention7.5 / 10Strong✓ Tool-verified
Other · Security — Whether data has a defined lifetime — retention periods, TTLs, cleanup jobs (storage limitation).
Method: Roslyn scan: retention/TTL configuration presence in schema; CascadeDelete detected but not scored as retention control. Deterministic, gated by PII presence.
A retention mechanism is present, but the data-lifecycle is not yet complete — missing: a scheduled purge / cleanup job (PurgeOlderThan / CleanupJob).
What to do
Complete the data-lifecycle story: an expiry limit (a declared maximum age for the stored data — a retention-age setting, or a store-level TTL where your storage offers one), a scheduled purge/cleanup job that enforces it, and a documented retention period covering the personal data.
Other · Domain Modelling — Whether aggregates reference each other by identity (id) rather than by direct object reference — the core DDD consistency-boundary rule.
Method: Roslyn (DDD-gated): aggregate roots identified by convention; each aggregate field checked for direct references to other aggregates versus id-only. Deterministic, DDD-native.
Coverage: Population: aggregate roots identified by AggregateRoot/IAggregateRoot base/interface NAME convention; reference-by-identity then checked exhaustively within that set — a root not using those names is invisible.
Do you agree with this assessment?
DM10 · One transaction, one aggregate9.9 / 10Exemplary✓ Tool-verified
Other · Domain Modelling — Whether a single operation mutates more than one aggregate root. An aggregate is a consistency boundary, so saving two together fuses them into one — the second's invariants come to depend on the first's transaction, and the pair can no longer be separated. Reads of other aggregates are not counted.
Method: Neutral body surface (DDD-gated): every method body scanned for repository WRITE calls (Add/Update/Save/Remove/Delete/Insert/Store and their async forms), keyed on the ARGUMENT type rather than the repository type — three `IRepository<T>` writes collapse to one repository but are three distinct aggregates. Reads (Get/Find/Load/Query) are excluded, so loading another aggregate for context never counts. Score is offending methods over methods that write at all. Deterministic.
`FileStore.SaveCoreAsync` saves `DatabaseBlobBackend`, `DbSet` in a single operation. Each is its own consistency boundary, so committing them together makes the second's invariants depend on the first's transaction, holds a lock across both for the whole operation, and means the pair can no longer be separated — into different services, or different databases. Mutate one aggregate here and let the others follow from a domain event. — src/Rask.Storage/FileStore.cs:173
What to do
Mutate one aggregate per operation and let the others follow from a domain event — the second aggregate reaching consistency a moment later is the design, not a compromise.
Other · Domain Modelling — Whether an aggregate can be constructed in a state its own rules forbid — a public constructor that takes a raw primitive, stores it, and validates nothing, with no factory beside it. A constructor taking only value objects is not counted: each parameter has already validated itself.
Method: Neutral surface (DDD-gated): each non-abstract entity/aggregate checked for a PUBLIC constructor taking at least one RAW PRIMITIVE parameter whose body contains no guard token (throw / Guard. / Ensure. / ArgumentException / CheckRule / an XException.ThrowIf* helper). C#: a static factory beside a public constructor does not exempt it, and a public parameterless constructor followed by public raw-primitive setters that refuse nothing is charged when the type also declares a validating way in (a guarded constructor or a guarding static method returning the type); TypeScript: a static Create/Of/From/New factory exempts the type. A constructor taking only value objects is never charged -- measured: 64 of 87 unguarded public constructors on the C# corpus take value objects only, so ignoring parameter types would be 73% false positives. One finding per entity. Deterministic.
Other · Domain Modelling — How much of the domain uses strongly-typed ids vs raw Guid/string/int — adoption curve, not all-or-nothing.
Method: Roslyn (DDD-gated): strongly-typed id adoption on domain entities/events; raw Guid/int/string ids counted versus wrapped types. An id wrapper is recognised by VALUE SEMANTICS, not by being a struct — a record struct, a record class (`record ApartmentId(Guid Value)`) or a class declared by a typed-id base (`class MemberId : TypedIdValueBase`) all count, while a plain mutable class (reference equality) and a verb-phrase query record (`GetCustomerById`) do not. Deterministic, adoption percentage.
Coverage: Population: id-like members by *Id/*Key NAME suffix; strongly-typed-ID shape then checked semantically — non-suffixed identifiers are not seen.
`Authenticatable.TenantId` is a raw `Guid` — give it a strongly-typed id: a dedicated single-field type wrapping the `Guid`, in whatever form your language spells that. — src/Rask.Auth.Api/Authenticatable.cs:69
`EmailConfirmed.UserId` is a raw `Guid` — give it a strongly-typed id: a dedicated single-field type wrapping the `Guid`, in whatever form your language spells that. — src/Rask.Auth.Api/EmailConfirmed.cs:9
`Passkey.UserId` is a raw `Guid` — give it a strongly-typed id: a dedicated single-field type wrapping the `Guid`, in whatever form your language spells that. — src/Rask.Auth.Api/Passkey.cs:22
`PasskeyAdded.UserId` is a raw `Guid` — give it a strongly-typed id: a dedicated single-field type wrapping the `Guid`, in whatever form your language spells that. — src/Rask.Auth.Api/PasskeyAdded.cs:10
`PasskeyAdded.PasskeyId` is a raw `Guid` — give it a strongly-typed id: a dedicated single-field type wrapping the `Guid`, in whatever form your language spells that. — src/Rask.Auth.Api/PasskeyAdded.cs:10
`PasskeyRemoved.UserId` is a raw `Guid` — give it a strongly-typed id: a dedicated single-field type wrapping the `Guid`, in whatever form your language spells that. — src/Rask.Auth.Api/PasskeyRemoved.cs:10
`PasskeyRemoved.PasskeyId` is a raw `Guid` — give it a strongly-typed id: a dedicated single-field type wrapping the `Guid`, in whatever form your language spells that. — src/Rask.Auth.Api/PasskeyRemoved.cs:10
`PasswordReset.UserId` is a raw `Guid` — give it a strongly-typed id: a dedicated single-field type wrapping the `Guid`, in whatever form your language spells that. — src/Rask.Auth.Api/PasswordReset.cs:8
`Session.UserId` is a raw `Guid` — give it a strongly-typed id: a dedicated single-field type wrapping the `Guid`, in whatever form your language spells that. — src/Rask.Auth.Api/Session.cs:22
`SignedIn.UserId` is a raw `Guid` — give it a strongly-typed id: a dedicated single-field type wrapping the `Guid`, in whatever form your language spells that. — src/Rask.Auth.Api/SignedIn.cs:9
`SignedIn.SessionId` is a raw `Guid` — give it a strongly-typed id: a dedicated single-field type wrapping the `Guid`, in whatever form your language spells that. — src/Rask.Auth.Api/SignedIn.cs:9
`SignedOut.UserId` is a raw `Guid` — give it a strongly-typed id: a dedicated single-field type wrapping the `Guid`, in whatever form your language spells that. — src/Rask.Auth.Api/SignedOut.cs:9
`SignedOut.SessionId` is a raw `Guid` — give it a strongly-typed id: a dedicated single-field type wrapping the `Guid`, in whatever form your language spells that. — src/Rask.Auth.Api/SignedOut.cs:9
`UserRegistered.UserId` is a raw `Guid` — give it a strongly-typed id: a dedicated single-field type wrapping the `Guid`, in whatever form your language spells that. — src/Rask.Auth.Api/UserRegistered.cs:9
`CacheEntry.Key` is a raw `String` — give it a strongly-typed id: a dedicated single-field type wrapping the `String`, in whatever form your language spells that. — src/Rask.Cache/CacheEntry.cs:19
`Job.UserId` is a raw `Guid` — give it a strongly-typed id: a dedicated single-field type wrapping the `Guid`, in whatever form your language spells that. — src/Rask.Jobs/Job.cs:62
`Job.TenantId` is a raw `Guid` — give it a strongly-typed id: a dedicated single-field type wrapping the `Guid`, in whatever form your language spells that. — src/Rask.Jobs/Job.cs:72
`Job.WaitingKey` is a raw `String` — give it a strongly-typed id: a dedicated single-field type wrapping the `String`, in whatever form your language spells that. — src/Rask.Jobs/Job.cs:99
`QueuedMail.UserId` is a raw `Guid` — give it a strongly-typed id: a dedicated single-field type wrapping the `Guid`, in whatever form your language spells that. — src/Rask.Mail/QueuedMail.cs:103
`QueuedMail.TenantId` is a raw `Guid` — give it a strongly-typed id: a dedicated single-field type wrapping the `Guid`, in whatever form your language spells that. — src/Rask.Mail/QueuedMail.cs:113
`OutboxMessage.UserId` is a raw `Guid` — give it a strongly-typed id: a dedicated single-field type wrapping the `Guid`, in whatever form your language spells that. — src/Rask.Outbox/OutboxMessage.cs:76
`OutboxMessage.TenantId` is a raw `Guid` — give it a strongly-typed id: a dedicated single-field type wrapping the `Guid`, in whatever form your language spells that. — src/Rask.Outbox/OutboxMessage.cs:86
`StoredFile.Key` is a raw `String` — give it a strongly-typed id: a dedicated single-field type wrapping the `String`, in whatever form your language spells that. — src/Rask.Storage/StoredFile.cs:34
`StoredFile.TenantId` is a raw `Guid` — give it a strongly-typed id: a dedicated single-field type wrapping the `Guid`, in whatever form your language spells that. — src/Rask.Storage/StoredFile.cs:45
`PushSubscriber.UserId` is a raw `Guid` — give it a strongly-typed id: a dedicated single-field type wrapping the `Guid`, in whatever form your language spells that. — src/Rask.WebPush/PushSubscriber.cs:29
`PushSubscriber.TenantId` is a raw `Guid` — give it a strongly-typed id: a dedicated single-field type wrapping the `Guid`, in whatever form your language spells that. — src/Rask.WebPush/PushSubscriber.cs:32
What to do
Adopt strongly-typed ids across the domain — finish the migration or document the boundary; primitive ids invite transposed-argument bugs.
Do you agree with this assessment?
DM4 · Rich vs anemic model10.0 / 10Exemplary✓ Tool-verified
Other · Domain Modelling — Whether aggregates/entities carry the behaviour that protects their invariants, rather than being data bags driven by external services.
Method: Roslyn (DDD-gated): entity method BODIES classified mutator-vs-query — only methods that mutate the entity's own declared state count as invariant-protecting behaviour, so a getter/passthrough doesn't rescue an anemic class. Deterministic, exhaustive over domain-layer entities.
Coverage: Population: entities by name/base convention; rich-vs-anemic judged by classifying each method body mutator-vs-query — logic-bearing domain types outside the convention are invisible.
Other · Domain Modelling — Whether entities protect their state — private/init-only setters, and collections handed out as read-only views rather than the mutable backing collection — instead of exposing writable state that bypasses invariants. Softened when a rehydration framework (Marten/EF) is present.
Method: Roslyn (DDD-gated): entities scanned for publicly writable state — public setters, and (C#/VB) own mutable collections handed out through an auto-property, a public field or a bare-field expression getter, where a computed/copying getter is never charged. One finding per entity; score softened when Marten/EF rehydration frameworks present. Deterministic, framework-aware.
Coverage: Population: entities by convention; encapsulation (setter shape) checked exhaustively within the set.
Other · Domain Modelling — Whether one domain rule is decided — or one measurement produced — in more than one place, rather than living on the type that owns it.
Method: Neutral body surface plus Roslyn (DDD-gated), two arms. DECISION (Roslyn only): a predicate over a domain type's members judged in two or more types, where none of those decisions live on the owning type — operands of comparisons and relational property patterns only, so a member merely passed as an argument is not judged. DERIVATION: a plain all-numeric carrier of ≥2 members, with no base type and exactly one constructor, CONSTRUCTED as the result of a method (returned or assigned, never inline as an argument) in two or more types other than its own — the same measurement produced twice, which centralising the judgement does not fix. DERIVATION runs on every language whose frontend declares the produced-or-passed fact per construction (Roslyn and the Java sidecar today); a target with only the derivation arm carries an engine gap naming the decision arm as not assessed, and a frontend that declares nothing keeps the dimension not measured rather than clean. Single-member rules, test code and generated code are out of population for both. Advisory.
Rask.UiDateRange's [End, Start] are judged in Rask.UiCalendarRangePick, Rask.UiDatePickerPresets, Rask.UiPickerLimits — the same decision, restated. Every copy is a chance to drift, and copies drift silently because each one looks correct on its own. Move the judgement onto the type that owns the members and let the call sites ask it.
What to do
Move each repeated judgement onto the type that owns the members it reads, so the rule has one home and cannot drift.
Other · Readiness — Whether retry-prone mutations (command handlers and message or event consumers) are idempotent, so an at-least-once redelivery or a client retry does not apply the effect twice.
Method: Roslyn (any mutation, ungated): each persistent write of a command handler or message/event consumer is idempotent when a guard is visible (an exists/dedup read that gates an exit, upsert, idempotency-key/inbox used in a condition or store call, versioned or fixed-value write, dedup envelope or pipeline), at risk only on positive double-apply evidence (a fresh-identity insert, an accumulation on a loaded and saved object, a growing member list, an unkeyed POST/SMTP send/Stripe charge), and otherwise not classified. Deterministic, no model; not scored when more than half are not classified. Advisory.
Coverage: Population: retry-prone mutations — command handlers (CQRS write side) + message/event consumers (IConsumer/I*EventHandler) — that mutate persistent state; runs on any repo with mutations, not only event-driven ones. Every mutation is classified exhaustively and deterministically: guarded, at risk on positive evidence, or not classified; the score is over the classified ones and is withheld when they are fewer than half.
Other · Code Health — Unreviewed-generation residue: shipped members still throwing NotImplementedException, and placeholder string literals left in non-test, non-generated code. Scored as a quality signature, never as a claim about authorship.
Method: Roslyn syntax scan: NotImplementedException throws and placeholder string literals in non-test, non-generated shipped code. Deterministic, code-shape signature.
A placeholder string ("[Rask.Prerender] no hreflang alternates …") is still in shipped code — typical of generated boilerplate that was never filled in. — src/Rask.Wasm/PrerenderedLanguages.cs:175
A placeholder string ("[Rask.Prerender] no sitemap — set <RaskS…") is still in shipped code — typical of generated boilerplate that was never filled in. — src/Rask.Wasm/SitemapWriter.cs:38
What to do
Finish or delete NotImplementedException stubs and replace placeholder literals before shipping.
Other · Code Health — Unfinished work detected by code SHAPE, not keywords: members that only throw a "not implemented" exception, methods that take inputs and return a constant, async methods that never await, dead `if (false)` / `#if false` branches, and skeleton types most of whose members are holes. A real, objective slice of technical debt.
Method: Roslyn syntax scan: incompleteness by code shape (constant-returning methods, async-never-await, #if false branches, guards that return what the code already falls through to, tests an earlier guard already decided, comparisons against NaN, skeleton types), not keyword-gated. Deterministic, code-shape heuristic.
Control only reaches here when `state.Messages.Count > 0` is false, because the guard on line 8 exits otherwise. This test is therefore always false and everything it guards is unreachable. Implement the distinction that was intended, or delete the test. — src/Rask.Core/Forms/EditContext.Validation.cs:16
`OnMount` is declared `async` but never awaits anything, so it runs synchronously while pretending to be asynchronous. Drop `async` or do the real async work. (×4) — src/Rask.Site/Features/Components/SkipFactoryCounter.cs:12, src/Rask.Site/Features/Users/UserGateDemo.cs:12, src/Rask.Site/Shared/PathDisplay.cs:15, …
`OnUpdated` is declared `async` but never awaits anything, so it runs synchronously while pretending to be asynchronous. Drop `async` or do the real async work. — src/Rask.Site/Features/Todos/TodosPage.cs:51
`OnFirstRender` is declared `async` but never awaits anything, so it runs synchronously while pretending to be asynchronous. Drop `async` or do the real async work. (×7) — src/Rask.Site/Features/UiKit/UiKitActionsPage.cs:23, src/Rask.Site/Features/UiKit/UiKitDataDisplayPage.cs:25, src/Rask.Site/Features/UiKit/UiKitDataGridPage.cs:22, …
`OnUnmount` is declared `async` but never awaits anything, so it runs synchronously while pretending to be asynchronous. Drop `async` or do the real async work. (×3) — src/Rask.Site/Features/Users/UserGateDemo.cs:14, src/Rask.Site/Shared/PathDisplay.cs:17, src/Rask.Site/Shared/ShowcaseLayout.cs:52
`ReadFileChunkAsync` looks like it should compute a result but its body just returns a constant — a placeholder return that was never filled in. — src/Rask.Wasm/JSInterop.cs:350
A placeholder e-mail address ("no-reply@example.com") is still in shipped code — its domain is reserved for documentation, so anything sent here is undeliverable by construction. Replace it with the real address, or take it from configuration. — src/Rask.Server/App/RaskBatteryWiring.cs:72
A placeholder value ("Jane Doe") is still in shipped code — sample/mock data that was never replaced with the real thing. (×2) — src/Rask.Site/Features/Elements/ElementsFormsDemo.cs:38, src/Rask.Site/Features/Elements/ElementsFormsDemo.cs:40
A placeholder e-mail address ("contact@example.com") is still in shipped code — its domain is reserved for documentation, so anything sent here is undeliverable by construction. Replace it with the real address, or take it from configuration. — src/Rask.Site/Features/Elements/ElementsSectionsDemo.cs:33
A test is skipped ("diagnostic — run manually to gather allocation deltas") — 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. — tests/Rask.Core.Tests/Performance/CounterAllocationPinTests.cs:46
What to do
Finish or delete the unfinished stubs (NotImplementedException / empty / constant-returning bodies) — they are dead surface that looks live.
Clear the softer debt: remove commented-out code and dead branches, re-enable or delete skipped tests, and replace blanket warning suppressions with targeted ones.
Maturity · Maturity — Whether the repo and its projects have a README, and whether it's substantive and current.
Method: Filesystem scan: README presence, word count, and headings for depth; git history for staleness. Exhaustive across root and project dirs, deterministic.
What to do
Add a README to the 54 of 57 project(s) that lack one — worth up to 1.9 pts.
Maturity · Maturity — Whether key decisions (ADRs) and the high-level shape (C4/diagrams) are written down.
Method: Filesystem scan: ADR folder/naming conventions or content, plus Mermaid/PlantUML/C4/architecture.md discovery. Exhaustive, deterministic.
No Architecture Decision Records found — no conventional ADR directory, no numbered `NNNN-title` documents in any markup this check reads, and nothing ADR-shaped by content. Design rationale recorded elsewhere (a design-notes tree, a mailing list, pull-request discussion) is not visible to this check and is not re-findable per decision, so a future maintainer cannot ask why one choice was made and get an answer.
What to do
Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them.
Maturity · Maturity — Whether the 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 & versioning10.0 / 10Exemplary○ Nothing flagged
Readiness · Readiness — For a library: a deliberate (small) public API surface and explicit semantic versioning so consumers can depend on it safely.
Method: Roslyn scan: public API surface area and semantic-versioning markers (SemVer attributes, changelog entries) for libraries; off .NET, a library is the ecosystem's publication act (an npm package that is not private and names an entry point, a PyPI distribution with a build system, a Rust library crate, a Maven/Gradle module that publishes, a Go module with no package main, a gemspec, a Composer library, a SwiftPM library product, a pub.dev or Hex package), its surface is the share of types the language'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.
Only 19/46 service-like projects use logging (pure contract/DTO projects are excluded — they have nothing to log). Of those 46, 7 ship a process this repository operates; the rest are libraries their consumer hosts, where the logging decision belongs to the host.
`REDACTED` reports through `Console.Write…` at line 539 although other files in its project log through a logger. Console lines carry no level, category or structured properties and never reach the log pipeline or its exporters. — REDACTED:539
`src/Rask.Wasm/WasmHostBuilder.cs` reports through `Console.Write…` at line 350 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/Rask.Wasm/WasmHostBuilder.cs:350
`src/Rask.Wasm/WasmHostBuilder.cs` reports through `Console.Write…` at line 371 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/Rask.Wasm/WasmHostBuilder.cs:371
`src/Rask.Wasm/WasmHostBuilder.cs` reports through `Console.Write…` at line 372 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/Rask.Wasm/WasmHostBuilder.cs:372
`src/Rask.Wasm/WasmHostBuilder.cs` reports through `Console.Write…` at line 412 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/Rask.Wasm/WasmHostBuilder.cs:412
`src/Rask.Wasm/WasmHostBuilder.cs` reports through `Console.Write…` at line 413 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/Rask.Wasm/WasmHostBuilder.cs:413
`src/Rask.Wasm/WasmHostBuilder.cs` reports through `Console.Write…` at line 415 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/Rask.Wasm/WasmHostBuilder.cs:415
`src/Rask.Wasm/WasmHostBuilder.cs` reports through `Console.Write…` at line 425 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/Rask.Wasm/WasmHostBuilder.cs:425
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.
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.
What to do
Add gitleaks/trufflehog in CI to block PRs that introduce committed secrets.
Readiness · Readiness — Whether releases are automated and safely reversible (probes, rolling updates, approval gates) — from manifests/pipeline files, not the live environment.
Method: Filesystem scan: deployment manifests/IaC (K8s YAML, Helm, Terraform) for rolling updates, probes, approval gates, migration hooks. Exhaustive, deterministic.
Deployment automation exists but no readiness/liveness probes, rolling-update strategy, lifecycle hooks or migration job were evidenced — a bad release is harder to detect and reverse.
What to do
Add readiness/liveness probes and a rolling-update (or blue/green) strategy so a bad release is caught and rolled back automatically.
The pipeline declares a deployment environment, but whether required reviewers / protection rules are attached to it lives in repository settings we cannot read — confirm the gate is enforced before production promotion.
Do you agree with this assessment?
P5 · DR & Backup4.0 / 10Weak✓ Tool-verified
Readiness · Readiness — Whether disaster recovery is planned and codified — backups, geo-recovery, RTO/RPO, persistence guarantees — from IaC + container manifests + docs, never the live cloud.
Method: Filesystem scan: disaster recovery, backup, geo-recovery, RTO/RPO, persistence guarantees from IaC, manifests, and docs. Exhaustive, deterministic, never a live environment.
What to do
Document RTO/RPO and a tested restore procedure (a backup config alone isn't disaster recovery).
Enable purge protection / soft-delete (and prevent_destroy on critical resources) so data stores can't be lost to an accidental or malicious delete.
Readiness · Readiness — Whether outbound HTTP calls are wrapped in resilience (retry/timeout/circuit-breaker) so a failing dependency doesn't cascade.
Method: Source scan: outbound HTTP clients and what bounds them — resilience handlers (Polly, AddStandardResilienceHandler) on .NET; on Go, the JVM, Python, JavaScript/TypeScript, Ruby, PHP, Rust, Elixir, Swift, Dart and Erlang, a timeout, deadline, retry or breaker beside each call, or a process-wide client default (a framework-wide deadline such as Drupal core's, Laravel's or actix's awc counts). Exhaustive, deterministic.
`new HttpClient()` builds an outbound HTTP client and nothing bounds it: no timeout is set on it and no retry or resilience policy wraps its calls in the type that owns it. A slow or failing dependency will hold this service's request, thread or connection — and cascade — until the call gives up on its own (100 s for HttpClient's default). (×5) — scripts/flux/Flux/Commands/ParityChart.cs:221, scripts/flux/Flux/Commands/Refresh.cs:64, scripts/flux/Flux/Commands/Sync.cs:379, …
`new HttpClient { BaseAddress = httpBaseAddress(sp) }` builds an outbound HTTP client and nothing bounds it: no timeout is set on it and no retry or resilience policy wraps its calls in the type that owns it. A slow or failing dependency will hold this service's request, thread or connection — and cascade — until the call gives up on its own (100 s for HttpClient's default). — src/Rask.Site/ExampleServiceCollectionExtensions.cs:25
`services.AddHttpClient(HttpClientName)` registers an outbound HTTP client, and what is applied to it does not bound it. Its `Timeout` is set to `Timeout.InfiniteTimeSpan`, which removes HttpClient's own bound rather than setting one. A slow or failing dependency will hold this service's request, thread or connection — and cascade — until the call gives up on its own (100 s for HttpClient's default). — src/Rask.Storage/RaskStorageServiceCollectionExtensions.cs:47
`new HttpClient(new SignInRefusals(sp, origin) { InnerHandler = new HttpClient...` builds an outbound HTTP client and nothing bounds it: no timeout is set on it and no retry or resilience policy wraps its calls in the type that owns it. A slow or failing dependency will hold this service's request, thread or connection — and cascade — until the call gives up on its own (100 s for HttpClient's default). — src/Rask.Wasm/WasmHostBuilder.cs:99
What to do
Add `AddStandardResilienceHandler()` (or a Polly policy and an explicit timeout) to each client registration flagged here, so a flaky dependency can't take the app down.
Do you agree with this assessment?
P8 · Schema migrations3.0 / 10Weak✓ Tool-verified
Readiness · Readiness — Whether EF Core schema changes go through versioned migrations rather than the un-evolvable EnsureCreated().
Method: Roslyn scan: EF Core DbContext for a versioned migrations directory versus bare EnsureCreated usage; off .NET, a file scan of dependency manifests, migration histories (Flyway, Liquibase, Alembic, Django, Rails, Prisma, TypeORM, Knex/Sequelize, golang-migrate, goose, Laravel, Doctrine, Diesel/sqlx) and schema auto-create in production source or config. Exhaustive, deterministic.
This repository evolves its schema with versioned migrations, but `EnsureCreated()` here builds a schema straight from the model instead — with no migrations-history row, so a database it creates can't be upgraded by `Migrate()` afterwards and the two paths can disagree about the shape. Apply the migrations here (`Migrate()` / a migrations bundle) rather than creating the schema. (×2) — src/Rask.Data/SchemaStep.cs:11, src/Rask.Data/SchemaStep.cs:21
This repository evolves its schema with versioned migrations, but a CREATE TABLE statement here creates schema at runtime outside them — structure no migration created and the migration history does not describe, so a later migration that touches it fails on a fresh environment and the environments drift apart. Create it in a migration instead. (×2) — REDACTED:328, src/Rask.SQLite.Litestream/LitestreamVerifier.cs:19
What to do
Replace each EnsureCreated() in production code with the migrations the rest of the repository already uses (`Database.Migrate()` or a migrations bundle), so every database gets its schema from the one versioned path.
Readiness · Performance — Whether the code protects its performance with benchmarks — a benchmark suite, allocation/memory measurement, and (ideally) a CI gate. Presence is credited as a bonus, never a deduction.
Method: Repo + source scan: BenchmarkDotNet referenced (csproj/source), [Benchmark]/[MemoryDiagnoser] attribute counts, and a benchmark step in CI; off .NET, the same ladder over Go testing.B, Rust criterion/#[bench]/divan, JMH/kotlinx-benchmark, pytest-benchmark/asv/pyperf, tinybench/mitata/vitest bench/benchmark.js and Swift package-benchmark — scored as a bonus ladder (absence is neutral, never a deduction). Deterministic, presence detection.
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.
20 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). (×20) — src/Rask.Cache/RaskDistributedCache.cs:36, src/Rask.Cache/RaskDistributedCache.cs:111, src/Rask.Cache/RaskDistributedCache.cs:119, …
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 Safety9.9 / 10Exemplary✓ 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.
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.
13 duplicated blocks under src/ have copies in at least two of the sibling directories Rask.Core, Rask.Server, Rask.Wasm — 10 of them are reported below, and 3 are counted here but not reported individually: those copies match on shape but no longer clear R10's bar for an individually reported row — either they kept neither their own names nor their values, or what was copied is too small to stand on its own (it reports near-exact duplication only, and only of substantial extent). What this row states is the concentration, which the detector measured over all 13 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 13 local ones: the siblings replicate behaviour none of them owns, which is the shape of a missing shared module — a common library every sibling imports — rather than 13 separate extractions. Check first whether the siblings are deliberately standalone deliverables (scaffold templates, demo apps that must stay copy-pasteable); where they are, the duplication is the design and the per-block rows are the ones to act on. — src/Rask.Server/Resources/rask.ts:1687
src/Rask.Server/Resources/rask.ts:1687 · src/Rask.Wasm/Resources/rask.wasm.ts:490 — 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/Rask.Server/Resources/rask.ts:1687
src/Rask.Server/Resources/rask.ts:295 · src/Rask.Wasm/Resources/rask-wasm-auth.ts:74 — 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/Rask.Server/Resources/rask.ts:295
src/Rask.Core/Resources/browser/auth.ts:211 · src/Rask.Core/Resources/browser/auth.ts:281 — 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/Rask.Core/Resources/browser/auth.ts:211
src/Rask.Server/Resources/rask.ts:114 · src/Rask.Wasm/Resources/rask.wasm.ts:73 — 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/Rask.Server/Resources/rask.ts:114
src/Rask.Core/Resources/rask-carousel.ts:308 · src/Rask.Core/Resources/rask-carousel.ts:322 — 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/Rask.Core/Resources/rask-carousel.ts:308
src/Rask.Core/Resources/rask-requires.ts:33 · src/Rask.Core/Resources/rask-toast.ts:81 — the two spans are one implementation copied and then locally edited — 77 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — src/Rask.Core/Resources/rask-requires.ts:33
src/Rask.Core/Resources/rask-dom-path.ts:70 · REDACTED:64 — the two spans are one implementation copied and then locally edited — 83 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — src/Rask.Core/Resources/rask-dom-path.ts:70
src/Rask.Core/Resources/rask-list.ts:153 · src/Rask.Core/Resources/rask-menu.ts:59 — the two spans are one implementation copied and then locally edited — 75 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — src/Rask.Core/Resources/rask-list.ts:153
src/Rask.Core/Resources/rask-calendar.ts:1005 · src/Rask.Core/Resources/rask-color.ts:558 — 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/Rask.Core/Resources/rask-calendar.ts:1005
REDACTED:290 · REDACTED:304 — 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:290
REDACTED:519 · REDACTED:702 — 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:519
REDACTED:881 · src/Rask.Core/Resources/rask-owned.ts:350 — the two spans are one implementation copied and then locally edited — 55 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — REDACTED:881
src/Rask.Core/Resources/rask-calendar.ts:179 · src/Rask.Core/Resources/rask-datetime.ts:53 — 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/Rask.Core/Resources/rask-calendar.ts:179
src/Rask.Core/Resources/rask-color.ts:608 · src/Rask.Core/Resources/rask-color.ts:628 — 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/Rask.Core/Resources/rask-color.ts:608
src/Rask.Core/Resources/rask-otp.ts:102 · src/Rask.Core/Resources/rask-otp.ts:169 — the two spans are one implementation copied and then locally edited — 72 tokens are still identical, in the same order in both spans, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — src/Rask.Core/Resources/rask-otp.ts:102
REDACTED:410 · src/Rask.Core/Resources/rask-time-list.ts:136 — the two spans are one implementation copied and then locally edited — 61 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — REDACTED:410
src/Rask.Core/Resources/rask-scoped.ts:37 · src/Rask.Core/Resources/rask-scoped.ts:75 — 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/Rask.Core/Resources/rask-scoped.ts:37
src/Rask.Core/Resources/rask-toggle.ts:142 · src/Rask.Core/Resources/rask-toggle.ts:165 — the two spans are one implementation copied and then locally edited — 68 tokens are still identical, in the same order in both spans, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — src/Rask.Core/Resources/rask-toggle.ts:142
src/Rask.Server/Resources/rask.ts:174 · src/Rask.Wasm/Resources/rask.wasm.ts:126 — 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/Rask.Server/Resources/rask.ts:174
src/Rask.Server/Resources/rask.ts:1912 · src/Rask.Wasm/Resources/rask.wasm.ts:710 — 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/Rask.Server/Resources/rask.ts:1912
src/Rask.Server/Resources/rask.ts:1929 · src/Rask.Wasm/Resources/rask.wasm.ts:726 — 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/Rask.Server/Resources/rask.ts:1929
src/Rask.Core/Resources/browser/auth.ts:393 · src/Rask.Core/Resources/browser/auth.ts:423 — 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/Rask.Core/Resources/browser/auth.ts:393
src/Rask.Core/Resources/rask-calendar.ts:1159 · src/Rask.Core/Resources/rask-calendar.ts:1186 — 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/Rask.Core/Resources/rask-calendar.ts:1159
REDACTED:1001 · REDACTED:1249 — 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:1001
src/Rask.Server/Resources/rask.ts:1821 · src/Rask.Wasm/Resources/rask.wasm.ts:677 — 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/Rask.Server/Resources/rask.ts:1821
src/Rask.Server/Resources/rask.ts:2014 · src/Rask.Wasm/Resources/rask.wasm.ts:751 — 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/Rask.Server/Resources/rask.ts:2014
src/Rask.Core/Resources/rask-color.ts:265 · src/Rask.Core/Resources/rask-command.ts:60 · src/Rask.Core/Resources/rask-tabs.ts:88 — the 3 copies sit in sibling files in one directory, so check first whether one of them (or an existing module there) already owns this behaviour and the others should call it; otherwise extract it into one module in that directory and have each site call it. There is one copy in each of 3 separate files rather than several in one place, so check first whether these are sibling modules that each declare their own version of one shape — one per entity, per provider, per language. Where they are, no single extracted module collapses them: each module still has to be written, and what recurs is the TEMPLATE. The moves that do collapse a template are to generate these modules from the set they enumerate, or to replace the repeated construction with one factory each site calls with its own values — and where the set is the point, each module pinning one distinct thing, the repetition IS the enumeration and there is nothing to delete. — src/Rask.Core/Resources/rask-color.ts:265
REDACTED:904 · src/Rask.Core/Resources/rask-overlay.ts:257 — 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. — REDACTED:904
src/Rask.Core/Resources/rask-menu.ts:59 · src/Rask.Core/Resources/rask-time-list.ts:71 — the two spans are one implementation copied and then locally edited — 53 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — src/Rask.Core/Resources/rask-menu.ts:59
src/Rask.Core/Resources/rask-persist.ts:71 · src/Rask.Core/Resources/rask-requires.ts:33 — the two spans are one implementation copied and then locally edited — 59 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — src/Rask.Core/Resources/rask-persist.ts:71
src/Rask.Server/Resources/rask.ts:1898 · src/Rask.Wasm/Resources/rask.wasm.ts:697 — 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/Rask.Server/Resources/rask.ts:1898
src/Rask.Core/Resources/browser/auth.ts:382 · src/Rask.Core/Resources/browser/webAuthn.ts:94 · src/Rask.Core/Resources/rask-api.ts:259 — 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/Rask.Core/Resources/browser/auth.ts:382
src/Rask.Core/Resources/rask-calendar.ts:1088 · src/Rask.Core/Resources/rask-calendar.ts:1130 — 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/Rask.Core/Resources/rask-calendar.ts:1088
src/Rask.Core/Resources/rask-carousel.ts:338 · src/Rask.Core/Resources/rask-grow.ts:61 — 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/Rask.Core/Resources/rask-carousel.ts:338
src/Rask.Core/Resources/rask-list.ts:124 · src/Rask.Core/Resources/rask-time-list.ts:52 — 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/Rask.Core/Resources/rask-list.ts:124
src/Rask.Core/Resources/rask-menu-keys.ts:249 · src/Rask.Core/Resources/rask-overlay.ts:100 — 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/Rask.Core/Resources/rask-menu-keys.ts:249
src/Rask.Core/Resources/rask-morph.ts:233 · src/Rask.Core/Resources/rask-morph.ts:259 — 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/Rask.Core/Resources/rask-morph.ts:233
src/Rask.Core/Resources/rask-persist.ts:72 · src/Rask.Core/Resources/rask-plot.ts:318 — the two spans are one implementation copied and then locally edited — 57 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — src/Rask.Core/Resources/rask-persist.ts:72
src/Rask.Core/Resources/rask-color.ts:583 · src/Rask.Core/Resources/rask-color.ts:645 — 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/Rask.Core/Resources/rask-color.ts:583
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.
morphNode has cyclomatic complexity 95 and cognitive complexity 148; 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/Rask.Core/Resources/rask-morph.ts:583
(anonymous) has cyclomatic complexity 52 and cognitive complexity 57; 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/Rask.Core/Resources/rask-list.ts:827
applyOps has cyclomatic complexity 43 and cognitive complexity 96; 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. — REDACTED:199
draw has cyclomatic complexity 38 and cognitive complexity 68; 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/Rask.Core/Resources/rask-color.ts:314
(anonymous) has cyclomatic complexity 35 and cognitive complexity 32; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — src/Rask.Core/Resources/rask-list.ts:761
(anonymous) has cyclomatic complexity 34 and cognitive complexity 40; 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/Rask.Core/Resources/rask-calendar.ts:1036
paintDay has cyclomatic complexity 33 and cognitive complexity 36; 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/Rask.Core/Resources/rask-calendar.ts:447
handle has cyclomatic complexity 30 and cognitive complexity 40; 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/Rask.Ui/Resources/phone/ui-phone.ts:397
cursorKey has cyclomatic complexity 29 and cognitive complexity 32; 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/Rask.Core/Resources/rask-menu-keys.ts:78
maskMoney has cyclomatic complexity 28 and cognitive complexity 30; 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/Rask.Core/Resources/rask-field.ts:67
(anonymous) has cyclomatic complexity 27 and cognitive complexity 32; 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/Rask.Core/Resources/rask-menu-keys.ts:142
(anonymous) has cyclomatic complexity 27 and cognitive complexity 23; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — src/Rask.Core/Resources/rask-keys.ts:56
parseAbsolute has cyclomatic complexity 26 and cognitive complexity 39; 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. — tests/Rask.TestSupport/ScriptFixtures/web-globals.js:699
onFrame has cyclomatic complexity 26 and cognitive complexity 35; 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/Rask.Server/Resources/rask.ts:593
(anonymous) has cyclomatic complexity 26 and cognitive complexity 30; 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/Rask.Core/Resources/rask-plot.ts:167
(anonymous) has cyclomatic complexity 24 and cognitive complexity 26; 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/Rask.Core/Resources/rask-api.ts:120
commit has cyclomatic complexity 22 and cognitive complexity 28; 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/Rask.Server/Resources/rask.ts:1724
formatDay has cyclomatic complexity 21 and cognitive complexity 47; 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/Rask.Core/Resources/rask-calendar.ts:177
(anonymous) has cyclomatic complexity 21 and cognitive complexity 16; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — src/Rask.Core/Resources/rask-field.ts:239
(anonymous) has cyclomatic complexity 20 and cognitive complexity 25; 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/Rask.Core/Resources/rask-color.ts:583
What to do
Break down the listed branch-heavy functions; aim P95 cyclomatic ≤ 5.
Do you agree with this assessment?
R3 · Large Files4.7 / 10Adequate✓ 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/Rask.Server/Resources/rask.ts has 2024 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/Rask.Server/Resources/rask.ts:1
REDACTED has 1327 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
src/Rask.Core/Resources/rask-calendar.ts has 1101 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/Rask.Core/Resources/rask-calendar.ts:1
src/Rask.Core/Resources/rask-list.ts has 878 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/Rask.Core/Resources/rask-list.ts:1
src/Rask.Wasm/Resources/rask.wasm.ts has 802 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/Rask.Wasm/Resources/rask.wasm.ts:1
src/Rask.Core/Resources/rask-morph.ts has 795 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/Rask.Core/Resources/rask-morph.ts:1
src/Rask.Core/Resources/rask-color.ts has 604 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/Rask.Core/Resources/rask-color.ts:1
src/Rask.Core/Resources/rask-api.ts has 547 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/Rask.Core/Resources/rask-api.ts:1
src/Rask.Core/Resources/rask-owned.ts has 485 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/Rask.Core/Resources/rask-owned.ts:1
src/Rask.Core/Resources/rask-input.ts has 441 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/Rask.Core/Resources/rask-input.ts:1
src/Rask.Server/Resources/rask-http-transport.ts has 436 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/Rask.Server/Resources/rask-http-transport.ts:1
REDACTED has 434 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
src/Rask.Core/Resources/rask-segments.ts has 432 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/Rask.Core/Resources/rask-segments.ts:1
src/Rask.Ui/Resources/phone/ui-phone.ts has 421 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/Rask.Ui/Resources/phone/ui-phone.ts:1
src/Rask.Core/Resources/browser/auth.ts has 411 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/Rask.Core/Resources/browser/auth.ts: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 Coverage7.6 / 10Strong✓ 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.
No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one. (×26) — src/Rask.Server/Resources/rask.ts:1, src/Rask.Wasm/Resources/rask.wasm.ts:1, src/Rask.Ui/Resources/phone/ui-phone.ts:1, …
What to do
Add tests that import the unreached modules (directly or through their public entry).
Do you agree with this assessment?
R7 · Dead Code9.8 / 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.
179 file(s) (~35657 LoC) were excluded from dead-code analysis. This package's entry point(s) resolved, but the walk stopped one hop in: src/Rask.Wasm/Browser/main.ts imports './_framework/dotnet.js', which is not in the scanned tree. That is usually a generated or build-output module, so reachability cannot see past it and no dead-code claim is made about this package. Nothing is necessarily wrong here.
Nothing ultimately consumes this binding: its only referrer is the re-export in src/Rask.Core/Resources/browser/index.ts, whose re-exported name has no consumer either. Removing it is therefore not a one-file change — drop the re-export line in src/Rask.Core/Resources/browser/index.ts in the same commit, or the barrel will import a name that no longer exists. (×5) — src/Rask.Core/Resources/browser/auth.ts:98, src/Rask.Core/Resources/browser/mediaDevices.ts:25, src/Rask.Core/Resources/browser/mediaDevices.ts:34, …
What to do
Delete the dead files and unused exports — every line is maintenance cost and rebuild-estimate inflation with zero runtime value.
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.
`IdentityV3HeaderBytes` is the key-derivation salt and is a compile-time constant, so the secret this operation depends on is published with the source. A key that ships with the source is not secret: every contributor, fork, mirror and released binary carries it, so anyone holding the repository can decrypt what any installation encrypted, and there is no way to invalidate what was already protected because every deployment built from this source shares the value. Where the constant is a password salt the consequence differs but is no smaller — one global salt means precomputation amortises across every installation, which is the property salting exists to destroy. Read the value from configuration, an environment variable or a secrets manager at startup and FAIL FAST when it is absent, so a missing key stops the process instead of silently falling back to a shared default; treat the committed value as disclosed and rotate it rather than only deleting the line. For a salt, generate a fresh random one per password and store it alongside the hash. — src/Rask.Auth.Api/PasswordHasher.cs:36
Set: Content-Security-Policy, Referrer-Policy, X-Content-Type-Options, X-Frame-Options. Missing: Strict-Transport-Security — the four headers that carry the points of this card's security-headers term (Content-Security-Policy, Strict-Transport-Security, X-Content-Type-Options, X-Frame-Options), 0.5 each. (−0.5 on this card.) — REDACTED:643
What to do
Load cryptographic key and salt material from configuration, an environment variable or a secrets manager rather than fixing it in the source, and fail fast at startup when it is absent — a default that silently works is the one that reaches production. Rotate anything already committed: it must be treated as disclosed. Salts should be generated per password and stored with the hash, never shared across installations.
Add Strict-Transport-Security beside the headers already set; Content-Security-Policy is the one that pays for itself first, then Strict-Transport-Security, then nosniff and a frame policy.
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.
Blocking on a Task with `.Wait()`/`.GetAwaiter().GetResult()` can deadlock (and wastes a thread). Prefer awaiting it: make the caller `async` and `await` instead. Where a synchronous entry point must stay — a public sync API you cannot break, or a process entry point that must not return until the work finishes — the block belongs in ONE documented bridge and never inside code that is already async; and where it already is that bridge, give the wait a TIMEOUT so a hung task fails the call instead of hanging the process. (×16) — src/Rask.Cache/RaskDistributedCache.cs:36, src/Rask.Cache/RaskDistributedCache.cs:111, src/Rask.Cache/RaskDistributedCache.cs:119, …
`.Wait(…)` blocks this thread until the task completes or the bound expires — sync-over-async: it can deadlock under a synchronization context and it parks a thread while it waits. `await` the task (with `.WaitAsync(timeout, token)` where the bound matters). — src/Rask.Core/AppCapture.cs:53
Blocking on a Task with `.Wait()`/`.GetAwaiter().GetResult()` wastes a thread and, if the task needs a context this one is holding, deadlocks. `Dispose()` returns void by contract, so it cannot simply `await`: signal the work to stop first (cancel its token, set its stop flag) so the wait is short, give the wait a TIMEOUT so a hung task cannot hang shutdown, and — where callers can use it — add an awaitable teardown (`DisposeAsync`/`StopAsync`) beside the synchronous one and let `Dispose()` remain the bounded fallback. — src/Rask.Data/DeclaredRuleCheckInterceptor.cs:188
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. — scripts/flux/Flux/Lib/Runtime.cs:43
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 · Security — Whether a hand-rolled public/private IP check can be walked past — a method that unwraps IPv4-mapped IPv6 but returns the opposite verdict for the same host written as IPv4-compatible, 6to4 or NAT64.
Method: Roslyn syntax + semantics: methods that unwrap IPv4-mapped IPv6 and hand-roll IPv4 range carve-outs, checked for whether the IPv6 branch also accounts for the IPv4-compatible, 6to4 and NAT64 embeddings. Deterministic, provable per finding. Advisory.
This method unwraps IPv4-MAPPED IPv6 (`IsIPv4MappedToIPv6`, line 30) and then rejects `10.0.0.0/8` on its IPv4 path — but the IPv6 branch at line 35 classifies the address as written, and IPv4 reaches IPv6 through three MORE embeddings this method never mentions: IPv4-compatible (`::a.b.c.d`), 6to4 (`2002::/16`) and NAT64 (`64:ff9b::/96`). So `::10.0.0.1`, `2002:0a00:0001::` and `64:ff9b::10.0.0.0` all name a host inside `10.0.0.0/8` — the range this same method declares non-public — and all reach the IPv6 branch un-unwrapped, taking the opposite verdict. Unwrap every embedding to its IPv4 form before classifying, or reject any IPv6 address carrying an embedded IPv4 outright. — src/Rask.WebPush/PushConnection.cs:35
What to do
Each finding names the IPv4 branch that rejects the host and the IPv6 branch that accepts the same host in another notation. Confirm from the two, then unwrap every IPv4-in-IPv6 embedding before classifying, or reject non-native IPv6 outright.
Do you agree with this assessment?
X15 · Unvalidated length from an untrusted reader10.0 / 10Exemplary○ Nothing flagged
Other · Security — Whether a length read out of the stream being parsed is bounded before it is allocated or read — an unchecked count taken from the input lets the input choose the allocation.
Method: Roslyn syntax + semantics: integer lengths read from a BinaryReader and spent on a bulk read or an array allocation, checked for any comparison or bounding call on the value anywhere in the method. Deterministic, provable per finding. Advisory.
Other · Code Health — Whether a loop that shortens a string until it fits a length budget has a floor — one with none grinds the value down to the empty string, or past it into a negative-length `Substring`.
Method: Roslyn syntax + semantics: while/do loops whose body's only effect on a string is to drop its last character, checked for whether anything — a direct comparison on the length, a body guard, a break — bounds that length below. On a repository with no .NET source it reads JavaScript/TypeScript off the engine’s own token stream (test, vendored and minified paths not) with the same rule: a `while`/`do` loop whose body’s one assignment to a value is `x = x.slice(0, -1)` or `x = x.slice|substring|substr(0, x.length - 1)`, driven by a condition that reads `x.length` only as a term of a larger expression — never compared directly, never tested for truthiness, and with no other read of `x` — and whose body has no `break`, `return`, `throw` or `if` naming `x`. Deterministic, provable per finding. Advisory.
Do you agree with this assessment?
X17 · Uncapped recursion over a caller-supplied document10.0 / 10Exemplary○ Nothing flagged
Other · Security — Whether a walk that recurses through a JSON/XML tree handed in by its caller bounds how deep it will go — an uncapped walk lets the document's nesting choose the stack depth, and the resulting StackOverflowException cannot be caught.
Method: Roslyn syntax + semantics: methods that take a JSON/XML document node and call themselves with a child of it, reachable from an externally-callable member of the same type that accepts a document, checked for any depth parameter, descent counter or threaded arithmetic anywhere in the walk. On a repository with no .NET source it reads TypeScript off the engine’s own token stream (test, vendored, generated and minified paths and `.d.ts` not) with the same rule: a function or method with a parameter typed as a document value — `unknown`, `any`, `object`, `Record<string, unknown|any>`, a JSON alias (`JsonValue`, `JSONObject`, …) or a DOM node global the file does not rebind — that calls itself (bare, or through `this` for a method, or hands itself to a call over the value as in `value.map(walk)`) with something it took out of that value and never through an ancestor accessor such as `closest()` or `parentElement`, that is exported or reached from an exported function (a public method of the same exported class) taking such a value, and that names no depth, level, nesting, recursion, remaining or budget anywhere and threads no `+`/`-` arithmetic through a self-call. Plain JavaScript is not read: with no annotation nothing tells a parsed document from a tree the code built itself. Deterministic, provable per finding. Advisory.
Other · Code Health — Whether a type's disposal matches what it OWNS — releasing what it created, leaving alone what it was handed, and not declaring a finalizer for state that has nothing unmanaged to finalize.
Method: Roslyn syntax + semantics: every assignment to a disposable field is read to decide whether the type CREATED the value or was handed it, and the type's disposal is checked against that answer — an injected interface it disposes, a value it constructed and never releases, a finalizer on a type holding nothing unmanaged, and a disposable local whose every reference is a plain member read. A value handed to a container that disposes its contents (a parent control's `Controls` collection, a component `IContainer`) is released by that container and is not reported; generated code is out of population. On a repository with no .NET source the same ownership questions are read in JavaScript/TypeScript off the engine’s own token stream (test, vendored, generated and minified paths not): a class declaring `dispose()`, `[Symbol.dispose]()` or `[Symbol.asyncDispose]()` that disposes a field it was handed through a constructor parameter typed as a repository interface or resolved by a dependency-injection container; that assigns a field only ever from `new X(…)` of a disposable class and neither releases it anywhere in the class nor names it in its disposal member or a method that member calls, nor hands it to anything else; and a `const`/`let` local built from literals only whose every reference opens a statement operating on a non-release member of it. A class is disposable when every repository declaration of its name declares or inherits a disposal member, or when it is a documented library disposable (`vscode` EventEmitter, CancellationTokenSource and Disposable; three.js geometries, materials, textures, render targets, renderers, controls and composers). The finalizer arm has no JavaScript counterpart: a class cannot declare one. Dart is read for the owned-and-never-released arm: a Flutter `State` (or a class declaring `dispose()`/`close()`) whose library-private field is written only with direct creations of a framework controller, `FocusNode`, `StreamController` or periodic `Timer` (or a `.listen(…)` into a field declared `StreamSubscription`), which nothing in the class or its library releases (`dispose`/`close`/`cancel`) and which is never handed on except as a named argument. Ruby is read for the owned-and-never-released arm and the abandoned-local arm: a class declaring an instance `close`, `dispose`, `shutdown`, `stop`, `disconnect` or `terminate` whose instance variable is written only with a blockless core descriptor creation (`File.open`/`new`, `Tempfile`, `Dir.open`, `IO.popen`, the `socket` and `openssl` socket classes) that no method of the class closes and that is never handed on (passed, returned, stored, exposed by `attr_reader`, delegated) — a class whose superclass or mixin lies outside the repository is not judged — and a blockless creation read through and dropped (`File.open(path).read`) or held in a local that is never closed, returned, passed or stored (a `&:read` block-pass, an `autoclose: false` borrow and a `fileno` hand-over are not abandonment). PHP is read for the same two arms: a class (not a trait, and not one using a trait) declaring an instance `close`, `dispose`, `shutdown`, `stop`, `disconnect` or `terminate` whose `private` property (or a `final` class's `protected` one) is written only with a direct core `fopen`, `tmpfile`, `popen`, `proc_open`, `fsockopen`, `stream_socket_client`/`server` or `opendir` that nothing in the class closes (`fclose`, `pclose`, `closedir`, `unset`, a reset to `null`) and that is never handed on, and a handle held in a function's local, or read through as the argument of a reader, that is never closed, returned, passed, captured or stored; a `php://` stream, `curl_init`, `SplFileObject`, `PDO` and a function the repository declares under the core name are not read. Deterministic, provable per finding. Advisory.
`_key` is never created by `CoseKey` — every assignment to it takes a constructor parameter — yet this type disposes it here (line 104). Its declared type `AsymmetricAlgorithm` is an abstract class, so the instance came from whoever chose and created it, and that owner decides when it ends. Disposing it from here reaches outside this object's lifetime: a dependency shared with the rest of the process is torn down when THIS instance goes away, and the real owner's later `Dispose()` runs a second time on an object already disposed. Drop the call — a type disposes what it constructed, and only that. If this dependency genuinely is exclusive to this instance, construct it here (or take an owned factory) so the ownership is stated in the code rather than assumed. — src/Rask.Auth.Api/CoseKey.cs:104
`_stop` is a `CancellationTokenSource` that `DockerTunnel` never creates — every assignment to it takes a constructor parameter — and this type disposes it here (line 187). The caller that hands it over at `new DockerTunnel(host, directory, stop, ssh)` (DockerTunnel.cs line 102) releases the same value itself, so it kept ownership: this release is a second one, on a value that is still the caller's, and it ends the caller's instance while the caller may still be using it. Drop the call and leave the release to the caller that created the value — or, if this type is meant to own it, stop releasing it at the construction site so ownership is stated once. — src/Rask.Cli/Commands/DockerTunnel.cs:187
`probe` is a `TcpListener`, which implements `IDisposable`, and it is created here (line 89). Every use of it in `TryStart` 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 probe = …;`), which releases it at the end of the scope on every path including a throw. — src/Rask.Cli/Dev/DevStatusServer.cs:89
`_inner` is declared `IDisposable` and nothing more, and every assignment to it takes a constructor parameter — so `PinnedScope` can do exactly one thing with it, which is the release performed here (line 96), and it is the only reference left that can perform it. That release is the tail of an unprotected sequence: `ReferenceEquals(CultureInfo.CurrentUICulture, _uiCulture)` runs first (line 91), and nothing in `Dispose` catches it. A single throw from that call skips the release entirely — and because a bare `IDisposable` carries no state to inspect and no second holder to fall back on, whatever it represents (a lock taken for this instance, a semaphore lease, a scope) is then held for the remaining lifetime of the process, with nothing left that could ever give it back. Wrap the calls that precede it in a `try` and move the release into the `finally`, so the one statement that must happen is the one that always happens. — src/Rask.Core/Globalization/RaskCultureScope.cs:96
`LiveSessionBase` implements `IDisposable` — so it has told every caller it holds something worth releasing — and it constructs `_htmlBuffers` itself (line 40), which makes that instance its own. But `_htmlBuffers` is named in none of the methods the disposal search covered: `Dispose` (line 46), `Dispose` (line 54), `Dispose` (line 46), `Dispose` (line 54) — 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` (`_htmlBuffers?.Dispose();`), or, if it truly does not need releasing, drop `IDisposable` from the type so the claim and the behaviour agree. — src/Rask.Core/Live/LiveSessionBase.cs:40
`Reference` is never created by `ScriptObject` — every assignment to it takes a constructor parameter — yet this type disposes it here (line 38). Its declared type `IJSObjectReference` is an interface, so the instance came from whoever chose and created it, and that owner decides when it ends. Disposing it from here reaches outside this object's lifetime: a dependency shared with the rest of the process is torn down when THIS instance goes away, and the real owner's later `Dispose()` runs a second time on an object already disposed. Drop the call — a type disposes what it constructed, and only that. If this dependency genuinely is exclusive to this instance, construct it here (or take an owned factory) so the ownership is stated in the code rather than assumed. — src/Rask.Core/ScopedAssets/ScriptObject.cs:38
`_schemaOwner` is never created by `TestDatabase` — every assignment to it takes a constructor parameter — yet this type disposes it here (line 228). Its declared type `RaskDbContext` is an abstract class, so the instance came from whoever chose and created it, and that owner decides when it ends. Disposing it from here reaches outside this object's lifetime: a dependency shared with the rest of the process is torn down when THIS instance goes away, and the real owner's later `Dispose()` runs a second time on an object already disposed. Drop the call — a type disposes what it constructed, and only that. If this dependency genuinely is exclusive to this instance, construct it here (or take an owned factory) so the ownership is stated in the code rather than assumed. — src/Rask.Data/TestDatabase.cs:228
`_lease` is never created by `TestDatabase` — every assignment to it takes a constructor parameter — yet this type disposes it here (line 231). Its declared type `IAsyncDisposable` is an interface, so the instance came from whoever chose and created it, and that owner decides when it ends. Disposing it from here reaches outside this object's lifetime: a dependency shared with the rest of the process is torn down when THIS instance goes away, and the real owner's later `Dispose()` runs a second time on an object already disposed. Drop the call — a type disposes what it constructed, and only that. If this dependency genuinely is exclusive to this instance, construct it here (or take an owned factory) so the ownership is stated in the code rather than assumed. — src/Rask.Data/TestDatabase.cs:231
`_grace` is a `CancellationTokenSource` this type creates itself, and here (line 193) a new instance is written over it — but `JobProcessor` creates `_grace` when it is constructed, so every later call finds an instance there, and nothing earlier in `ExecuteAsync` disposes, closes, saves or hands on the instance being replaced. The assignment makes it unreachable while it still holds what it holds (a timer that keeps firing, a callback registered on a longer-lived token, a socket, a handle), and no later `Dispose` can reach it: the type's own disposal releases only the CURRENT instance. The cost accumulates once per overwrite. Release the previous instance first (`_grace?.Dispose();` before the assignment), or swap it out with `Interlocked.Exchange` and dispose what comes back. — src/Rask.Jobs/JobProcessor.cs:193
`ChromiumPrinter` implements `IDisposable` — so it has told every caller it holds something worth releasing — and it constructs `_turns` itself (line 13), which makes that instance its own. But `_turns` is named in none of the methods the disposal search covered: `DisposeAsync` (line 66) — 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` (`_turns?.Dispose();`), or, if it truly does not need releasing, drop `IDisposable` from the type so the claim and the behaviour agree. — src/Rask.Pdf/ChromiumPrinter.cs:13
`_toBrowser` is never created by `DevToolsConnection` — every assignment to it takes a constructor parameter — yet this type disposes it here (line 97). Its declared type `Stream` is an abstract class, so the instance came from whoever chose and created it, and that owner decides when it ends. Disposing it from here reaches outside this object's lifetime: a dependency shared with the rest of the process is torn down when THIS instance goes away, and the real owner's later `Dispose()` runs a second time on an object already disposed. Drop the call — a type disposes what it constructed, and only that. If this dependency genuinely is exclusive to this instance, construct it here (or take an owned factory) so the ownership is stated in the code rather than assumed. — src/Rask.Pdf/DevToolsConnection.cs:97
`db` is never created by `DatabaseReadStream` — every assignment to it takes a constructor parameter — yet this type disposes it here (line 104). Its declared type `DbContext` is an abstract class, so the instance came from whoever chose and created it, and that owner decides when it ends. Disposing it from here reaches outside this object's lifetime: a dependency shared with the rest of the process is torn down when THIS instance goes away, and the real owner's later `Dispose()` runs a second time on an object already disposed. Drop the call — a type disposes what it constructed, and only that. If this dependency genuinely is exclusive to this instance, construct it here (or take an owned factory) so the ownership is stated in the code rather than assumed. — src/Rask.Storage/Backends/DatabaseReadStream.cs:104
`db` is never created by `DatabaseReadStream` — every assignment to it takes a constructor parameter — yet this type disposes it here (line 115). Its declared type `DbContext` is an abstract class, so the instance came from whoever chose and created it, and that owner decides when it ends. Disposing it from here reaches outside this object's lifetime: a dependency shared with the rest of the process is torn down when THIS instance goes away, and the real owner's later `Dispose()` runs a second time on an object already disposed. Drop the call — a type disposes what it constructed, and only that. If this dependency genuinely is exclusive to this instance, construct it here (or take an owned factory) so the ownership is stated in the code rather than assumed. — src/Rask.Storage/Backends/DatabaseReadStream.cs:115
`app.Services.CreateScope()` (line 56) creates an `IServiceScope`, and it is dropped: `CreateScope().ServiceProvider` never names the scope, so nothing can release it. A scope owns every scoped service resolved from it — the `DbContext`, its connection, anything registered `AddScoped` — and releases them only when the scope itself is disposed; nothing here ever does, so each scope's services stay alive until the process ends. Create it with `using var scope = …CreateScope();` (or `await using` for `CreateAsyncScope`), or, when it must outlive the method, dispose it from the owning type's `Dispose`. — src/Rask.Testing/Page.Visit.cs:56
`WasmLiveSession` implements `IDisposable` — so it has told every caller it holds something worth releasing — and it constructs `_inScopeRender` itself (line 30), which makes that instance its own. But `_inScopeRender` is named in none of the methods the disposal search covered: `Dispose` (line 98) — 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` (`_inScopeRender?.Dispose();`), or, if it truly does not need releasing, drop `IDisposable` from the type so the claim and the behaviour agree. — src/Rask.Wasm/WasmLiveSession.cs:30
`probe` is a `TcpListener`, which implements `IDisposable`, and it is created here (line 106). Every use of it in `FreePort` 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 probe = …;`), which releases it at the end of the scope on every path including a throw. — scripts/flux/Flux/Commands/ParityPhone.cs:106
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 614/1375 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 — the body observes an ambient token instead (a field or a context object), so the work does stop on cancellation, but a caller cannot cancel this call independently of the owner that created that token. (×4) — REDACTED:75, src/Rask.Auth.Api/AuthBearerEvents.cs:9, src/Rask.Cache/Remembering.cs:49, …
No CancellationToken parameter — this work can't be stopped early once started. (×35) — src/Rask.Auth.Client/BrowserAuth.cs:47, src/Rask.Auth.Client/BrowserAuth.cs:56, src/Rask.Auth.Client/BrowserAuth.cs:63, …
What to do
Thread a CancellationToken through async methods so work stops promptly on cancellation.
Other · Code Health — Whether an argument guard throws the exception its own condition describes — a guard that rejects a value for being EMPTY and reports it as `ArgumentNullException` tells the caller a parameter was null when it provably was not.
Method: Roslyn syntax: `throw new ArgumentNullException(nameof(p))` statements controlled by an `if`, whose condition is read for a test that is true of a NON-null `p` — an emptiness test that dereferences it (`p.Count == 0`, `!p.Any()`) or a BCL predicate documented true of the empty value (`string.IsNullOrEmpty(p)`). Deterministic, provable per finding. Advisory.
Other · Code Health — Whether a `when` guard is free of side effects — a guard that increments a counter or assigns while deciding whether its arm matches applies that change during PATTERN MATCHING, on an arm that may not be selected, and skips it entirely when a short-circuit to its left answers first.
Method: Roslyn syntax: `when` guards on case labels and switch-expression arms, read for a mutation (`++`/`--`/assignment) sitting in a position the guard's own `&&`/`||`/`??`/`?:`/`?.` can skip. Deterministic, provable per finding. Advisory.
Other · Code Health — Whether a method that TAKES a lock or semaphore and gives it back from a flag-guarded `finally` returns the value that flag implies — reporting success while the guard hands the primitive back admits a second caller the exclusion was there to keep out, and reporting failure while the guard keeps it leaves nothing to ever give it back. Also whether a `finally` that gives the primitive back unconditionally can run in a state where the method does not hold it: after a timed wait whose result was discarded, after an acquire inside the `try` that can fail, after the body already released it, or never, because a `return` left between the acquire and the `try`.
Method: Roslyn syntax: `try` statements whose `finally` releases a synchronisation primitive under a bare local-bool guard, where the method also TOOK that same primitive before the `try`, checked for a `return` of a bool literal whose value disagrees with the flag state the method's own straight-line assignments put it in. Deterministic, provable per finding. Advisory.
`Lock.WaitAsync(CancellationToken.None)` has already taken `Lock` when this `return` leaves, and the `finally` that calls `Lock.Release()` belongs to the `try` below it, so it never runs: `Lock` stays held and every later waiter blocks. Move the `return` inside the `try`, or take `Lock` after it. — src/Rask.Server/LiveSession.cs:713
What to do
Each finding names the return, the `finally` guard it disagrees with, and the flag state the method's own assignments put it in at that point. Confirm from the three, then make the two statements of ownership agree: the flag and the returned value both say whether the caller now owns the primitive, so a return reporting success must leave the guard skipping the release, and a return reporting failure must leave it performing one. Setting the flag immediately before the return that reports success — never after it, and never on a path that goes on to report failure — is what keeps the pair readable.
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 unescaped6.0 / 10Adequate✓ Tool-verified
Other · Security — Whether text read out of the document being converted is escaped before it is written into generated markup — a value the document's author chose, interpolated into an attribute the surrounding literal delimits, can close that attribute and open another.
Method: Roslyn semantic model over the whole compilation: a string-typed `Value`/`InnerText`/`InnerXml`/`Text` member declared inside `DocumentFormat.OpenXml` or `System.Xml` is a taint SOURCE, propagated through assignments, returns, arguments, tuple elements and string composition to its transitive closure, then read at interpolated-string holes that sit in a markup position the surrounding literal itself delimits. Escaper/encoder calls and enclosing validator conditions cut the flow. Flow- and container-insensitive by construction. A second arm needs no provenance at all and reports a type that CONTRADICTS ITSELF — the same expression escaped at one delimited markup hole and interpolated raw at another hole in the same markup position of the same type, which the type's own escaping proves is a defect without knowing where the value came from. On a repository with no .NET source it reads JavaScript/TypeScript off the token stream with the same rule: a DOM read of raw document text (`getAttribute`, `textContent`, `innerText`, `nodeValue`) is the source, propagated through local bindings and string composition, and judged at template-literal and concatenation holes in the same two delimited markup positions; escapers and validating conditions cut it, and documentation-site, test, vendored and minified scripts are not read. Deterministic, provable per finding. Advisory.
`Escape(link)` is text this program did not author, and it is written into the start of a URL attribute, where it chooses the scheme through markup this member returns with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. HTML encoding does not help here — a `javascript:` URL contains nothing it changes; allow only http(s) or a relative path. — src/Rask.Auth.Api/AuthEmailBodies.cs:49
`message.HtmlBody` is text this program did not author, and it is written into the text of an element through an HTML e-mail body with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup. — src/Rask.Mail/MailSerializer.cs:40
`mail.HtmlBody` is text this program did not author, and it is written into the text of an element through an HTML e-mail body with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup. — src/Rask.Mail/MimeMailFactory.cs:25
`email.HtmlBody` is text this program did not author, and it is written into the text of an element through an HTML e-mail body with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup. — src/Rask.Mail/QueuedMail.cs:31
`html` is text this program did not author, and it is written into the text of an element through `innerHTML` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup. (×2) — REDACTED:92, REDACTED:96
`op[2]==null?"":op[2]` is text this program did not author, and it is written into the text of an element through `innerHTML` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup. — REDACTED:360
What to do
Each finding names the expression, the attribute it lands in and the line. Confirm the value's origin from the read this analyzer traced, then escape it at the sink or validate it against the shape the attribute accepts before interpolating.
Other · Code Health — Whether a value the caller is invited to supply is the value the type actually uses — a constructor parameter stored in a private field that nothing ever reads while the default it was given is spelled out a second time at the site that should have read it, a keyed lookup that falls back to a different setting than the one its key names while the same type falls back to the matching one for that same key, or a culture-sensitive parse given no format provider by a type that feeds its own settable culture to the same kind of parse elsewhere, or a number an entry point writes to standard output under the host's culture while the same entry point formats with the invariant culture elsewhere. Either way, every caller who supplies a value silently gets something else.
Method: Roslyn syntax: private instance fields of a non-partial type assigned in a constructor from one of its own parameters with a `??` fallback, checked for whether anything in the type body reads the field and whether that same fallback expression is spelled out again outside the constructor; and `??` fallbacks onto a member access from a lookup call carrying exactly one string literal, grouped by that key across the type and checked for a fallback member whose folded name disagrees with the key while a sibling site for the same key agrees with it. On a repository with no .NET source the first two arms read JavaScript/TypeScript off the engine’s own token stream (tests included, bundles and vendored paths not): a `#x`, `private` or `private` parameter-property instance field filled in the constructor from a parameter (or one member of one) through `??`/`||` or a parameter default, never read anywhere in the file by name, whose constructed default is spelled again in the class body; and `lookup("key") ?? s.member` grouped by key per class, or per module outside every class. The culture arm has no JavaScript counterpart: its parses take no locale. Deterministic, provable per finding. Advisory.
Other · Code Health — Whether a value handed from a callback to the body that waits on it crosses on something built to be crossed — a `Queue<T>`/`List<T>`/`Dictionary<K,V>` written inside an event handler and read back outside it is mutated by two flows at once, and the semaphore or completion source beside it orders how MANY items exist while leaving the collection's own head, tail and backing array unprotected.
Method: Roslyn syntax: method, accessor, local-function and lambda bodies that declare BOTH a non-thread-safe generic collection (`Queue`/`Stack`/`List`/`Dictionary`/`HashSet`/`Sorted*`/`LinkedList`) and a synchronisation primitive (`SemaphoreSlim`/`TaskCompletionSource`/`ManualResetEvent(Slim)`/`AutoResetEvent`/`CountdownEvent`) as locals, then read for a `+=`-registered lambda that raises that primitive while the body outside every lambda waits on it — and, in that scope, a mutating call on the collection inside the lambda paired with a mention of it outside. Any `lock` in the scope abstains it. On a repository with no .NET source the same handoff is read in Java off the engine’s own token stream (test source sets, vendored and demonstration paths not): an `ArrayList`/`LinkedList`/`ArrayDeque`/`PriorityQueue`/`Hash*`/`LinkedHash*`/`Tree*` local and a `CountDownLatch`/`Semaphore`/`CompletableFuture` local, a lambda or anonymous class that raises the primitive and mutates the collection, and a wait outside it; any `synchronized` or `lock()` abstains the body. Because each of those primitives orders what the callback wrote before raising it, only a touch that provably overlaps the callback is convicted: one after the registration and before the next wait, or one in a loop registered-before, waiting on every pass and not declaring the collection. Deterministic, provable per finding. Advisory.
Do you agree with this assessment?
X27 · Collection changed while being enumerated10.0 / 10Exemplary○ Nothing flagged
Other · Code Health — Whether a `foreach` leaves the collection it is walking alone — a body that adds to or removes from the very collection the loop is enumerating invalidates the enumerator it is holding, so the next `MoveNext` throws `InvalidOperationException` and the remaining items are never seen.
Method: Roslyn syntax + semantics: `foreach` statements whose body calls a structural mutator (`Add`/`Remove`/`Clear`/`Insert`/…) on the very expression the loop is enumerating. Two arms. ARM A — the source is a concrete fragile BCL collection, or a live `Keys`/`Values` view over one, and the mutator resolves to that same collection's own member; concurrent and immutable collections and arrays are outside the population by construction, since their enumerators survive a structural change. ARM B — the source is an argument-less accessor CALL on a receiver whose body is in source: the accessor must return a stored field VERBATIM and a sibling member must structurally change that same field, both read off the implementations rather than from the members' names. A mutation the loop provably exits immediately after (`break`/`return`/`throw`/`goto`), or one written inside a nested loop or a lambda, is counted and never reported. Deterministic, provable per finding. Advisory.
Do you agree with this assessment?
X28 · Index access outside its own emptiness guard10.0 / 10Exemplary○ Nothing flagged
Other · Code Health — Whether a condition that tests a value for emptiness indexes that same value only where the test holds — an `||` written one parenthesis too far to the left leaves an index access outside the guard beside it, so the empty case the guard exists to anticipate reaches the index and throws.
Method: Roslyn syntax only, no semantic model: the OUTERMOST `&&`/`||` of every boolean condition, read for a symbol the condition tests for emptiness (`string.IsNullOrEmpty`/`IsNullOrWhiteSpace`, a `Length`/`Count` comparison against a literal, `Any()`, a `Length`/`Count` pattern, or a comparison against `""`) and ALSO indexes. Each `symbol[...]` access is placed by a boolean-reachability walk from the access up to the outermost connective: an access is COVERED when some enclosing step has it in the right operand and the left operand, under the truth value that step forces, proves the symbol non-empty — a recursion over `&&`/`||` whose true- and false-directions are asymmetric. A finding needs BOTH an uncovered access and a covered one on the same symbol in the same condition, which is the agreeing twin that separates a misplaced parenthesis from an unrelated length test. Bare index accesses with no emptiness test in the condition are neither counted nor reported; a non-identifier receiver and a lambda nested inside the condition are outside the population. Deterministic, provable per finding. Advisory.
Do you agree with this assessment?
X29 · Per-element action decided by a fixed element10.0 / 10Exemplary○ Nothing flagged
Other · Code Health — Whether a decision taken once per element is taken ABOUT that element — a test inside a counted loop that reads a fixed subscript of the very collection its guarded statement indexes by the loop variable applies element zero's answer to all of them, so the elements that differ from it are all handled wrongly, and in the same direction.
Method: Roslyn syntax only, no semantic model: every `for` statement declaring exactly ONE loop variable, and every `if` inside its body that is not under a nested loop or a lambda. A site enters the population when the `if`’s condition never mentions the loop variable while the statement it guards indexes some collection by that variable ALONE (`c[i]`; `c[i + 1]` and `c[i, j]` are outside it). A finding additionally needs the AGREEING TWIN at the same-collection grain: the condition must read THAT SAME collection at a subscript that does not move — written into the condition, or reached through a local declared BEFORE the loop, so an alias bound inside the body is not followed. Both collection expressions must be simple identifiers. On a repository with no .NET source the same rule reads JavaScript/TypeScript off the engine’s own token stream (tests included, bundles and vendored paths not): a `for (let|var|const x = …; …; …)` with one declarator and a braced body, an alias followed only when it is declared before the loop in a block that encloses it and never assigned inside the loop. Deterministic, provable per finding. Advisory.
Other · Code Health — Whether exceptions are handled rather than silently swallowed or rethrown with lost stack traces.
Method: Roslyn syntax scan: every catch clause counted; empty catches and bare rethrows flagged. Population is all catch clauses, not estimated. Deterministic, hard fact.
`catch (Exception)` does nothing with the exception it caught — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch. Log it through whatever this codebase already uses to report problems, or let it propagate; if one specific failure genuinely cannot matter, catch exactly that exception type and say why in a comment on the catch. (×3) — src/Rask.Batteries.Shared/HousekeepingContextFactory.cs:84, src/Rask.Query/SessionQueryClient.cs:484, src/Rask.Site/Features/Browser/BatteryDemo.cs:31
`catch (SqliteException)` does nothing with the exception it caught — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch. Log it through whatever this codebase already uses to report problems, or let it propagate; if one specific failure genuinely cannot matter, catch exactly that exception type and say why in a comment on the catch. — src/Rask.Cli/Commands/DbCommand.Backup.cs:401
`catch (Exception) when (…)` does nothing with the exception it caught — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch. Log it through whatever this codebase already uses to report problems, or let it propagate; if one specific failure genuinely cannot matter, catch exactly that exception type and say why in a comment on the catch. — src/Rask.Cli/Dev/DevStatusServer.cs:127
`catch (HttpListenerException)` does nothing with the exception it caught — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch. Log it through whatever this codebase already uses to report problems, or let it propagate; if one specific failure genuinely cannot matter, catch exactly that exception type and say why in a comment on the catch. — src/Rask.Cli/Dev/DevStatusServer.cs:131
An empty catch block silently discards the error — failures vanish with no log and no rethrow. On a teardown path letting it propagate is not an option (throwing out of `Dispose()` masks the failure already in flight and abandons the rest of the cleanup), so make the swallow deliberate instead: record it through whatever this codebase already uses to report problems — or, if one specific failure truly cannot matter, catch exactly that exception type and say why in a comment on the catch (a comment on a catch-all still swallows everything else). (×2) — src/Rask.Cli/Dev/DevStatusServer.cs:176, src/Rask.Cli/Dev/DevStatusServer.cs:182
`catch (IOException)` does nothing with the exception it caught — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch. Log it through whatever this codebase already uses to report problems, or let it propagate; if one specific failure genuinely cannot matter, catch exactly that exception type and say why in a comment on the catch. (×2) — src/Rask.Cli/Dev/LinuxDevHostPlatform.cs:237, src/Rask.Cli/Dev/LinuxDevHostPlatform.cs:299
`catch (UnauthorizedAccessException)` does nothing with the exception it caught — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch. Log it through whatever this codebase already uses to report problems, or let it propagate; if one specific failure genuinely cannot matter, catch exactly that exception type and say why in a comment on the catch. (×2) — src/Rask.Cli/Dev/LinuxDevHostPlatform.cs:241, src/Rask.Cli/Dev/LinuxDevHostPlatform.cs:303
`catch (Win32Exception)` does nothing with the exception it caught — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch. Log it through whatever this codebase already uses to report problems, or let it propagate; if one specific failure genuinely cannot matter, catch exactly that exception type and say why in a comment on the catch. — src/Rask.Cli/DockerProbe.cs:64
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. (×21) — src/Rask.Cli/ProcessRunner.cs:116, src/Rask.Core/HotReload/RaskHotReload.cs:172, src/Rask.Data/DataChangesInterceptor.cs:214, …
`catch` does nothing with the exception it caught — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch. Log it through whatever this codebase already uses to report problems, or let it propagate; if one specific failure genuinely cannot matter, catch exactly that exception type and say why in a comment on the catch. (×2) — src/Rask.Core/Components/Authorize.cs:219, src/Rask.Core/Forms/ModelGraphWalker.cs:162
`ContinueWith` with a continuation that does nothing discards the antecedent's failure — the task it returns completes successfully whether or not the work faulted, so the failure vanishes with no log and no rethrow. Await the task and handle the exception, or report the fault from the continuation (`t.Exception`). — src/Rask.Core/Live/QuiescenceScope.cs:197
`catch (JsonException)` does nothing with the exception it caught — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch. Log it through whatever this codebase already uses to report problems, or let it propagate; if one specific failure genuinely cannot matter, catch exactly that exception type and say why in a comment on the catch. (×2) — src/Rask.Cqrs.Server/EventStream.cs:138, src/Rask.DevTools/Panel/DevToolsPanelSession.cs:94
`catch (JSException) when (…)` does nothing with the exception it caught — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch. Log it through whatever this codebase already uses to report problems, or let it propagate; if one specific failure genuinely cannot matter, catch exactly that exception type and say why in a comment on the catch. — src/Rask.Site/Features/Browser/FileSystemAccessDemo.cs:62
What to do
Swallowed exception (caught, then discarded)
Do you agree with this assessment?
X30 · Support guard that admits what it rejects10.0 / 10Exemplary○ Nothing flagged
Other · Code Health — Whether a guard written as a NEGATED `||` says what its author meant — `!(a || b || x != k)` is `!a && !b && x == k` by De Morgan, so a bail-out that mixes capabilities the code needs with a fault it refuses turns inside out: it fires only where the capabilities are ABSENT, and lets every value the fault term names walk straight into the body that cannot handle it.
Method: Roslyn syntax only, no semantic model: every logical-not whose operand is a parenthesised `||` chain of two or more disjuncts, flattened (a left-nested `a || b || c` read once would see `(a || b)` as one disjunct). A site enters the population on that shape alone. A finding additionally needs the disjuncts to DISAGREE in polarity: at least one bare boolean read — an identifier or member access, never an invocation, which is a predicate rather than a capability flag — and at least one `x != <constant>`, the only form that negates into an exact-value pin (`== null` negates into a looser requirement and is outside the fault set). Consistently-polarised disjunctions, all-fault or all-capability, are counted and never reported; a negated `&&` is outside the population entirely. No same-receiver gate: it was measured to cost a real defect and remove no false positive. Deterministic, provable per finding. Advisory.
Do you agree with this assessment?
X32 · Type resolved by simple name across every loaded assembly10.0 / 10Exemplary○ Nothing flagged
Other · Code Health — Whether a plugin lookup names the type it means — searching every assembly loaded into the process for a candidate whose SIMPLE name equals a string supplied at runtime, and taking the first one found, is decided by assembly LOAD ORDER rather than by this source, so the same name can resolve to a different type on the next run.
Method: Roslyn syntax only, no semantic model: every invocation of `First`/`FirstOrDefault`/`Single`/`SingleOrDefault` whose OWN expression subtree contains both a `GetAssemblies()` call and a `GetTypes()`/`GetExportedTypes()` call — a single-element pick out of every type loaded into the process. A nested selector in the same chain sees no `GetAssemblies()` in its own subtree and is outside the population, so one lookup counts once however many links its chain has. A finding additionally needs both remaining halves: the selector must be `First`/`FirstOrDefault` (`Single`/`SingleOrDefault` reports the ambiguity rather than resolving it, and is counted and never reported), and the chain must carry an `==` comparison of `<lambda parameter>.Name` against something that is not a literal. The receiver must be a plain identifier bound by one of the chain’s own lambdas, which places `assembly.GetName().Name == "X"` outside the rule by construction. One exemption: a `.Name` test joined by `&&` to a `FullName`/`AssemblyQualifiedName` test on the same identifier is spared; joined by `||` it is not. Deterministic, provable per finding. Advisory.
Other · Code Health — Whether log calls use message templates (queryable) rather than interpolated strings.
Method: Roslyn syntax scan: every log call-site counted; interpolated-string first-argument violations flagged. Population is all log calls, not estimated. On a repository with no .NET source it reads JavaScript/TypeScript off the engine’s own token stream (test, vendored and minified paths not) with the same rule: a `trace`/`debug`/`info`/`warn`/`error`/`fatal`/`verbose`/`silly`/`http`/`log` call on a receiver named for a logger, in a package whose own or an enclosing `package.json` declares a logger that carries values as fields (pino, pino-http, nestjs-pino, Fastify, winston, bunyan, tslog, LogTape, roarr), whose first deciding argument is a template literal with substitutions; an object-literal fields argument is stepped over, a plain string message clears the call. Python is read the same way: a `debug`/`info`/`warning`/`error`/`exception`/`critical`/`log` call on a logger in a file that imports the standard library’s `logging` or structlog (loguru, which formats at the call, is not judged), whose message is a whole f-string with a non-constant field; a `%`-formatted, `.format()`-ed or concatenated message is not convicted, as in C#. PHP is read the same way: a PSR-3 level call (`emergency`…`debug`, `log`) on a logger (`$logger`, `$this->logger`, Laravel’s `Log::`, `logger()`, `\Drupal::logger()`) in a package whose `composer.json` requires a PSR-3 logger or a framework that hands one out (psr/log, Monolog, Laravel, Symfony, Drupal, CakePHP), or a file that imports one, whose message is a double-quoted string interpolating a variable; a single-quoted message clears the call, and `sprintf` or `.` concatenation is not convicted, as in C#. Dart is read the same way: a `trace`/`debug`/`info`/`warn`/`error`/`fatal` call on Sentry’s structured logger (`Sentry.logger`) whose message is a whole string literal interpolating a value (`$name`, `${…}`); the `Sentry.logger.fmt` template API clears the call. Dart that logs only through loggers with one message and no fields (package:logging, package:logger, talker, dart:developer) is not applicable rather than a reach gap. Ruby is read the same way: a `trace`/`debug`/`info`/`warn`/`error`/`fatal` call on the console gem’s `Console` (declared by a Gemfile, gemspec or Gemfile.lock, or required) or, where SemanticLogger, Ougai or dry-logger is declared or required, on a receiver named for a logger (`logger`, `@logger`, `Rails.logger`, `log`), whose first deciding argument is, as the whole argument, a double-quoted string interpolating a non-constant value (`#{…}`, `#@ivar`); a plain literal clears the call, keyword arguments are the fields, and a block, `%`-format or `+` concatenation is not convicted. Ruby that logs only through the standard Logger (Rails.logger) is not applicable rather than a reach gap. Deterministic.
Other · Code Health — Whether nullable reference types are enabled and not undermined by heavy `!` suppression.
Method: Roslyn compiler-options scan: NullableContextOptions per project; null-forgiving (!) suppression density per 1k syntax nodes. Deterministic, adoption plus suppression penalty.
This method contradicts itself about `principal`: line 39 writes `principal?.`, which says `principal` can be null, but line 44 then dereferences it directly as `principal.Claims` with no null test between them and no guard around it. If the `?.` is right, that dereference throws NullReferenceException on the input it was written for; if `principal` truly cannot be null here, the `?.` is misleading. Settle it one way — test `principal` once before the first use and handle the null case, or drop the `?.` — rather than leaving the two readings side by side. — src/Rask.Jobs/JobPrincipal.cs:44
~0.8 `!` suppressions per 1k syntax nodes — 790 suppression(s) across the 1021975 syntax node(s) in code where nullable warnings are ENABLED, which is the only code a `!` can suppress anything in (a `!` under `#nullable disable` is inert and is not counted, and its file's nodes are not in the denominator). Each one tells the compiler to trust you about null, suppressing the very safety NRTs provide.
What to do
Where a method uses `?.` on a symbol and then dereferences it directly, settle the question once: test it before the first use and handle null, or drop the `?.`.
Enable <Nullable>enable</Nullable> across all projects and resolve warnings rather than suppressing with `!`.
Do you agree with this assessment?
WCAG coverage — what static analysis assessed
Statically assessed 13 of 55 WCAG 2.2 Level A/AA success criteria (24%; ≈26% of the 50 WCAG 2.1 AA criteria for EN 301 549). The other 42 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 — 6 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 — 40 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.
X10 Duplicated predicate — 25 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
X6 Hand-rolled structured-format parsing — 8 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
X7 Silent fallback defaults — 40 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
X8 JS interop contract — 11 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
X9 Subsumed condition operand — 1 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
Not evidenced — 1 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.
C5 Data-Subject Rights — Repo shows no corroborated data-subject-rights mechanism (erasure / export-portability / consent) tied to a subject id or GDPR vocabulary — absence of evidence is not evidence of a working control. Implement erasure, data export/portability and consent tracking over the subject's records.
Not included — 29 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.
AC4 Keyboard semantics — No interactive element found in the parsed markup — AC4 not applicable here.
AX4 Dependency direction — not applicable to a vertical-slice + CQRS architecture (the inward-dependency rule is for layered/clean styles)
AXB2 Runtime readiness — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
AXR1 Runtime accessibility — docker build failed (exit 1) — ------ REDACTED:12 -------------------- 11 | COPY ["Company.RaskServer.csproj", "./"] 12 | >>> RUN --mount=type=cache,id=rask-nuget,target=/root/.nuget/packages \ 13 | >>> dotnet restore 14 | COPY . . -------------------- ERROR: failed to solve: process "/bin/sh -c dotnet restore" did not complete successfully: exit code: 1; runtime evidence skipped 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.
D12 Dependency Hygiene — Dependency hygiene not measured
D16 Bus Factor — single-contributor repository — bus factor is not applicable
D21 Naming Consistency — Naming consistency is measured on C# and TypeScript only; JavaScript, Python, html not measured.
D25 ADR Conformance — no ADRs to check
D28 Secrets (history) — gitleaks killed before it finished — this repository's working tree not scanned
D30 Dependency Vulnerabilities — nuget: the solution did not restore on the analyzer's .NET SDK (an SDK/target-framework/restore mismatch, common for an older codebase), so there was no restored dependency graph to scan
D32 Data Compliance (PII/GDPR) — 597 file(s) were not parsed by semgrep — the PII/GDPR ruleset never ran over them
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
DM12 Ambient inputs in the domain — no domain-layer types detected — ambient-input check not applicable
DM3 Integration-event coupling — no integration events detected — coupling check not applicable
DM6 Domain ↔ infrastructure boundary — no domain-layer types detected — domain↔infrastructure boundary check not applicable
DM7 Repository granularity — no repository abstraction detected (e.g. uses a document session)
DM8 Value-object opportunities — not scored — the deterministic rule found 0 candidate clump(s); its rows are withheld until it has a measured precision of 95 % (a sample of fewer than 10 rows cannot show one)
ED1 Event-Driven — applicable but not scored (2 of 3 signals for this style — below the bar we score at): 13 event handler(s); 11 CQRS handler(s)
ES1 Event Sourcing — not scored — this repository shows none of the 3 signals this lens looks for
P9 Domain vs controller coverage — coverage data present for 4368 file(s), but no domain-layer files were identified: no covered file's path contains any of the markers this check keys on (/domain/, /aggregates/, /valueobjects/, /domainmodel/, .domain/, /entities/), which are matched case-insensitively anywhere in the path. With no domain partition there is nothing to compare the web/controller layer against — if this repository keeps its business rules under a folder named none of those, that naming is what the check cannot see, not the domain logic.
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.
R5 Dependency Freshness — no package-lock.json — dependency freshness not measured (would require an npm lockfile); JS/npm CVEs are scored in D30 (Dependency Vulnerabilities), which answers every ecosystem
R6 Tooling — no package.json in the repository — test/lint/typecheck wiring is read from package.json scripts (corroborated against CI), so this project's own toolchain isn't measured here
R8 Dependency Hygiene — Not measured — no package.json declares any dependency, so there is nothing to check imports against (imports may resolve through a host runtime rather than node).
SC1 Supply-chain hygiene — 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.
FileScopedPragmaDisable tests/Rask.Core.Tests/Builder/ClassJoinChangeTests.cs:3— #pragma warning disable RASK014 // the tests need the very instance they hand to the render context — the disable has no matching restore anywhere in this file, so it does not end with the construct that needed it: it runs to the end of the file and silences the rule for everything written below, including code added years later that nobody weighed against it. Close it with the matching restore directive immediately after the construct it covers — that alone turns a standing exemption into a scoped one — or fix the cause and drop the directive entirely.
FileScopedPragmaDisable tests/Rask.Core.Tests/Builder/ClassJoinTests.cs:3— #pragma warning disable RASK014 // the tests need the very instance they hand to the render context — the disable has no matching restore anywhere in this file, so it does not end with the construct that needed it: it runs to the end of the file and silences the rule for everything written below, including code added years later that nobody weighed against it. Close it with the matching restore directive immediately after the construct it covers — that alone turns a standing exemption into a scoped one — or fix the cause and drop the directive entirely.
FileScopedPragmaDisable tests/Rask.Core.Tests/BuilderCallbackResetTests.cs:5— #pragma warning disable RASK014 // the tests need the very instance they hand to the render context — the disable has no matching restore anywhere in this file, so it does not end with the construct that needed it: it runs to the end of the file and silences the rule for everything written below, including code added years later that nobody weighed against it. Close it with the matching restore directive immediately after the construct it covers — that alone turns a standing exemption into a scoped one — or fix the cause and drop the directive entirely.
FileScopedPragmaDisable tests/Rask.Core.Tests/BuilderHoistTests.cs:3— #pragma warning disable RASK014 // the tests need the very instance they hand to the render context — the disable has no matching restore anywhere in this file, so it does not end with the construct that needed it: it runs to the end of the file and silences the rule for everything written below, including code added years later that nobody weighed against it. Close it with the matching restore directive immediately after the construct it covers — that alone turns a standing exemption into a scoped one — or fix the cause and drop the directive entirely.
FileScopedPragmaDisable tests/Rask.Core.Tests/BuilderLifecycleTests.cs:3— #pragma warning disable RASK014 // the tests need the very instance they hand to the render context — the disable has no matching restore anywhere in this file, so it does not end with the construct that needed it: it runs to the end of the file and silences the rule for everything written below, including code added years later that nobody weighed against it. Close it with the matching restore directive immediately after the construct it covers — that alone turns a standing exemption into a scoped one — or fix the cause and drop the directive entirely.
FileScopedPragmaDisable tests/Rask.Core.Tests/BuilderRenderPathTests.cs:4— #pragma warning disable RASK014 // the tests need the very instance they hand to the render context — the disable has no matching restore anywhere in this file, so it does not end with the construct that needed it: it runs to the end of the file and silences the rule for everything written below, including code added years later that nobody weighed against it. Close it with the matching restore directive immediately after the construct it covers — that alone turns a standing exemption into a scoped one — or fix the cause and drop the directive entirely.
FileScopedPragmaDisable tests/Rask.Core.Tests/BuilderResetTests.cs:3— #pragma warning disable RASK014 // the tests need the very instance they hand to the render context — the disable has no matching restore anywhere in this file, so it does not end with the construct that needed it: it runs to the end of the file and silences the rule for everything written below, including code added years later that nobody weighed against it. Close it with the matching restore directive immediately after the construct it covers — that alone turns a standing exemption into a scoped one — or fix the cause and drop the directive entirely.
FileScopedPragmaDisable tests/Rask.Core.Tests/Components/DivScrollTests.cs:4— #pragma warning disable RASK014 // test-defined StubComponent has no generated factory — the disable has no matching restore anywhere in this file, so it does not end with the construct that needed it: it runs to the end of the file and silences the rule for everything written below, including code added years later that nobody weighed against it. Close it with the matching restore directive immediately after the construct it covers — that alone turns a standing exemption into a scoped one — or fix the cause and drop the directive entirely.
FileScopedPragmaDisable tests/Rask.Core.Tests/Components/DragDropTests.cs:4— #pragma warning disable RASK014 // test-defined StubComponent has no generated factory — the disable has no matching restore anywhere in this file, so it does not end with the construct that needed it: it runs to the end of the file and silences the rule for everything written below, including code added years later that nobody weighed against it. Close it with the matching restore directive immediately after the construct it covers — that alone turns a standing exemption into a scoped one — or fix the cause and drop the directive entirely.
FileScopedPragmaDisable tests/Rask.Core.Tests/Components/ElementDialogEventsTests.cs:4— #pragma warning disable RASK014 // test-defined StubComponent has no generated factory — the disable has no matching restore anywhere in this file, so it does not end with the construct that needed it: it runs to the end of the file and silences the rule for everything written below, including code added years later that nobody weighed against it. Close it with the matching restore directive immediately after the construct it covers — that alone turns a standing exemption into a scoped one — or fix the cause and drop the directive entirely.
FileScopedPragmaDisable tests/Rask.Core.Tests/Components/ElementDomEventsTests.cs:4— #pragma warning disable RASK014 // test-defined StubComponent has no generated factory — the disable has no matching restore anywhere in this file, so it does not end with the construct that needed it: it runs to the end of the file and silences the rule for everything written below, including code added years later that nobody weighed against it. Close it with the matching restore directive immediately after the construct it covers — that alone turns a standing exemption into a scoped one — or fix the cause and drop the directive entirely.
FileScopedPragmaDisable tests/Rask.Core.Tests/Components/ElementDragTests.cs:1— #pragma warning disable RASK014 // test-defined StubComponent has no generated factory — the disable has no matching restore anywhere in this file, so it does not end with the construct that needed it: it runs to the end of the file and silences the rule for everything written below, including code added years later that nobody weighed against it. Close it with the matching restore directive immediately after the construct it covers — that alone turns a standing exemption into a scoped one — or fix the cause and drop the directive entirely.
FileScopedPragmaDisable tests/Rask.Core.Tests/Components/ElementKeyboardTests.cs:4— #pragma warning disable RASK014 // test-defined StubComponent has no generated factory — the disable has no matching restore anywhere in this file, so it does not end with the construct that needed it: it runs to the end of the file and silences the rule for everything written below, including code added years later that nobody weighed against it. Close it with the matching restore directive immediately after the construct it covers — that alone turns a standing exemption into a scoped one — or fix the cause and drop the directive entirely.
FileScopedPragmaDisable tests/Rask.Core.Tests/Components/ElementToggleTests.cs:4— #pragma warning disable RASK014 // test-defined StubComponent has no generated factory — the disable has no matching restore anywhere in this file, so it does not end with the construct that needed it: it runs to the end of the file and silences the rule for everything written below, including code added years later that nobody weighed against it. Close it with the matching restore directive immediately after the construct it covers — that alone turns a standing exemption into a scoped one — or fix the cause and drop the directive entirely.
FileScopedPragmaDisable tests/Rask.Core.Tests/Components/VirtualizeModelTests.cs:4— #pragma warning disable RASK014 // test-defined StubComponent has no generated factory — the disable has no matching restore anywhere in this file, so it does not end with the construct that needed it: it runs to the end of the file and silences the rule for everything written below, including code added years later that nobody weighed against it. Close it with the matching restore directive immediately after the construct it covers — that alone turns a standing exemption into a scoped one — or fix the cause and drop the directive entirely.
FileScopedPragmaDisable tests/Rask.Core.Tests/Forms/AsyncFormBindingTests.cs:8— #pragma warning disable RASK014 — the disable has no matching restore anywhere in this file, so it does not end with the construct that needed it: it runs to the end of the file and silences the rule for everything written below, including code added years later that nobody weighed against it. Close it with the matching restore directive immediately after the construct it covers — that alone turns a standing exemption into a scoped one — or fix the cause and drop the directive entirely.
FileScopedPragmaDisable tests/Rask.Core.Tests/Forms/RaskFileDispatchTests.cs:5— #pragma warning disable RASK014 — the disable has no matching restore anywhere in this file, so it does not end with the construct that needed it: it runs to the end of the file and silences the rule for everything written below, including code added years later that nobody weighed against it. Close it with the matching restore directive immediately after the construct it covers — that alone turns a standing exemption into a scoped one — or fix the cause and drop the directive entirely.
FileScopedPragmaDisable tests/Rask.Core.Tests/Live/AmbientTests.cs:4— #pragma warning disable RASK014 — the disable has no matching restore anywhere in this file, so it does not end with the construct that needed it: it runs to the end of the file and silences the rule for everything written below, including code added years later that nobody weighed against it. Close it with the matching restore directive immediately after the construct it covers — that alone turns a standing exemption into a scoped one — or fix the cause and drop the directive entirely.
FileScopedPragmaDisable tests/Rask.Core.Tests/Live/CrossParentKeyedMoveTests.cs:1— #pragma warning disable RASK014 — the disable has no matching restore anywhere in this file, so it does not end with the construct that needed it: it runs to the end of the file and silences the rule for everything written below, including code added years later that nobody weighed against it. Close it with the matching restore directive immediately after the construct it covers — that alone turns a standing exemption into a scoped one — or fix the cause and drop the directive entirely.
FileScopedPragmaDisable tests/Rask.Core.Tests/Live/CleanSubtreeReplayTests.cs:5— #pragma warning disable RASK014 // test-defined component subclasses have no generated factories — the disable has no matching restore anywhere in this file, so it does not end with the construct that needed it: it runs to the end of the file and silences the rule for everything written below, including code added years later that nobody weighed against it. Close it with the matching restore directive immediately after the construct it covers — that alone turns a standing exemption into a scoped one — or fix the cause and drop the directive entirely.
FileScopedPragmaDisable tests/Rask.Core.Tests/Live/ExternalStateInvalidationTests.cs:4— #pragma warning disable RASK014 // test-defined component subclasses have no generated factories — the disable has no matching restore anywhere in this file, so it does not end with the construct that needed it: it runs to the end of the file and silences the rule for everything written below, including code added years later that nobody weighed against it. Close it with the matching restore directive immediately after the construct it covers — that alone turns a standing exemption into a scoped one — or fix the cause and drop the directive entirely.
FileScopedPragmaDisable tests/Rask.Core.Tests/Live/HandlerOutlivesRenderTests.cs:4— #pragma warning disable RASK014 // test-defined component subclasses have no generated factories — the disable has no matching restore anywhere in this file, so it does not end with the construct that needed it: it runs to the end of the file and silences the rule for everything written below, including code added years later that nobody weighed against it. Close it with the matching restore directive immediately after the construct it covers — that alone turns a standing exemption into a scoped one — or fix the cause and drop the directive entirely.
FileScopedPragmaDisable tests/Rask.Core.Tests/Live/OpaqueSubtreeTests.cs:4— #pragma warning disable RASK014 // test-defined component subclasses have no generated factories — the disable has no matching restore anywhere in this file, so it does not end with the construct that needed it: it runs to the end of the file and silences the rule for everything written below, including code added years later that nobody weighed against it. Close it with the matching restore directive immediately after the construct it covers — that alone turns a standing exemption into a scoped one — or fix the cause and drop the directive entirely.
FileScopedPragmaDisable tests/Rask.Core.Tests/Live/StableHandlerIdTests.cs:5— #pragma warning disable RASK014 // test-defined component subclasses have no generated factories — the disable has no matching restore anywhere in this file, so it does not end with the construct that needed it: it runs to the end of the file and silences the rule for everything written below, including code added years later that nobody weighed against it. Close it with the matching restore directive immediately after the construct it covers — that alone turns a standing exemption into a scoped one — or fix the cause and drop the directive entirely.
FileScopedPragmaDisable tests/Rask.Core.Tests/Live/StaleEventTests.cs:5— #pragma warning disable RASK014 // test-defined component subclasses have no generated factories — the disable has no matching restore anywhere in this file, so it does not end with the construct that needed it: it runs to the end of the file and silences the rule for everything written below, including code added years later that nobody weighed against it. Close it with the matching restore directive immediately after the construct it covers — that alone turns a standing exemption into a scoped one — or fix the cause and drop the directive entirely.
EmptyCatchBlock src/Rask.Cli/Dev/DevStatusServer.cs:176— 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/Rask.Cli/Dev/DevStatusServer.cs:182— 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/Rask.Cli/ProcessRunner.cs:116— empty catch block — the error is discarded with nothing recorded, so a failure here leaves no trace anywhere. Record it through whatever this codebase already uses to report problems, or let it propagate. Where swallowing one specific failure really is correct — as it often is on a teardown/dispose path where throwing would mask the original failure — catch exactly that exception type and write down WHY in a comment on the catch. Both are needed: a comment on a catch-all still swallows every failure nobody anticipated, and a note that only restates the swallow ("ignored", "do nothing") is read as no explanation at all.
EmptyCatchBlock src/Rask.Core/HotReload/RaskHotReload.cs:172— 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/Rask.Data/DataChangesInterceptor.cs:214— 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/Rask.Data/DataChangesInterceptor.cs:273— 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/Rask.Data/DataChangesInterceptor.cs:309— 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/Rask.Query/QueryEntry.cs:245— 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/Rask.Server/Diagnostics/RaskServerDiagnostics.cs:84— 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/Rask.Server/Files/SessionDownloadStore.cs:101— 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/Rask.Server/Files/SessionUploadStore.cs:137— empty catch block — the error is discarded with nothing recorded, so a failure here leaves no trace anywhere. Record it through whatever this codebase already uses to report problems, or let it propagate. Where swallowing one specific failure really is correct — as it often is on a teardown/dispose path where throwing would mask the original failure — catch exactly that exception type and write down WHY in a comment on the catch. Both are needed: a comment on a catch-all still swallows every failure nobody anticipated, and a note that only restates the swallow ("ignored", "do nothing") is read as no explanation at all.
EmptyCatchBlock src/Rask.Server/LiveSession.cs:861— 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/Rask.Server/LiveSessionStore.cs:582— 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/Rask.Server/LiveSessionStore.cs:616— 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/Rask.Server/RaskDrainService.cs:129— empty catch block — the error is discarded with nothing recorded, so a failure here leaves no trace anywhere. Record it through whatever this codebase already uses to report problems, or let it propagate. Where swallowing one specific failure really is correct — as it often is on a teardown/dispose path where throwing would mask the original failure — catch exactly that exception type and write down WHY in a comment on the catch. Both are needed: a comment on a catch-all still swallows every failure nobody anticipated, and a note that only restates the swallow ("ignored", "do nothing") is read as no explanation at all.
EmptyCatchBlock REDACTED:2051— empty catch block — the error is discarded with nothing recorded, so a failure here leaves no trace anywhere. Record it through whatever this codebase already uses to report problems, or let it propagate. Where swallowing one specific failure really is correct — as it often is on a teardown/dispose path where throwing would mask the original failure — catch exactly that exception type and write down WHY in a comment on the catch. Both are needed: a comment on a catch-all still swallows every failure nobody anticipated, and a note that only restates the swallow ("ignored", "do nothing") is read as no explanation at all.
EmptyCatchBlock REDACTED:2131— empty catch block — the error is discarded with nothing recorded, so a failure here leaves no trace anywhere. Record it through whatever this codebase already uses to report problems, or let it propagate. Where swallowing one specific failure really is correct — as it often is on a teardown/dispose path where throwing would mask the original failure — catch exactly that exception type and write down WHY in a comment on the catch. Both are needed: a comment on a catch-all still swallows every failure nobody anticipated, and a note that only restates the swallow ("ignored", "do nothing") is read as no explanation at all.
EmptyCatchBlock REDACTED:2226— empty catch block — the error is discarded with nothing recorded, so a failure here leaves no trace anywhere. Record it through whatever this codebase already uses to report problems, or let it propagate. Where swallowing one specific failure really is correct — as it often is on a teardown/dispose path where throwing would mask the original failure — catch exactly that exception type and write down WHY in a comment on the catch. Both are needed: a comment on a catch-all still swallows every failure nobody anticipated, and a note that only restates the swallow ("ignored", "do nothing") is read as no explanation at all.
EmptyCatchBlock REDACTED:2904— empty catch block — the error is discarded with nothing recorded, so a failure here leaves no trace anywhere. Record it through whatever this codebase already uses to report problems, or let it propagate. Where swallowing one specific failure really is correct — as it often is on a teardown/dispose path where throwing would mask the original failure — catch exactly that exception type and write down WHY in a comment on the catch. Both are needed: a comment on a catch-all still swallows every failure nobody anticipated, and a note that only restates the swallow ("ignored", "do nothing") is read as no explanation at all.
EmptyCatchBlock REDACTED:2929— empty catch block — the error is discarded with nothing recorded, so a failure here leaves no trace anywhere. Record it through whatever this codebase already uses to report problems, or let it propagate. Where swallowing one specific failure really is correct — as it often is on a teardown/dispose path where throwing would mask the original failure — catch exactly that exception type and write down WHY in a comment on the catch. Both are needed: a comment on a catch-all still swallows every failure nobody anticipated, and a note that only restates the swallow ("ignored", "do nothing") is read as no explanation at all.
EmptyCatchBlock REDACTED:3171— empty catch block — the error is discarded with nothing recorded, so a failure here leaves no trace anywhere. Record it through whatever this codebase already uses to report problems, or let it propagate. Where swallowing one specific failure really is correct — as it often is on a teardown/dispose path where throwing would mask the original failure — catch exactly that exception type and write down WHY in a comment on the catch. Both are needed: a comment on a catch-all still swallows every failure nobody anticipated, and a note that only restates the swallow ("ignored", "do nothing") is read as no explanation at all.
EmptyCatchBlock REDACTED:3524— 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/Rask.Server/Transport/WebSocketTransport.cs:42— 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/Rask.Wasm.Tasks/BakeScopedAssetsTask.cs:225— 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/Rask.Wasm/Diagnostics/RaskWasmDiagnostics.cs:78— 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.
NoWarnInCsproj src/Rask.Api.Generators/Rask.Api.Generators.csproj:11— RS2008 — 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/Rask.Batteries.Generators/Rask.Batteries.Generators.csproj:11— RS2008 — 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/Rask.Generators/Rask.Generators.csproj:11— RS2008 — 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/Rask.Generators.CodeFixes/Rask.Generators.CodeFixes.csproj:19— RS2008 — 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/Rask.Jobs/Rask.Jobs.csproj:44— SYSLIB1100 — 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/Rask.Jobs/Rask.Jobs.csproj:44— SYSLIB1101 — 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/Rask.Tailwind/Rask.Tailwind.csproj:24— 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.
NoWarnInCsproj tests/Rask.DevTools.E2E.Tests/Rask.DevTools.E2E.Tests.csproj:21— RASK014 — 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 tests/Rask.Server.E2E.Tests/Rask.Server.E2E.Tests.csproj:18— RASK014 — 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 tests/Rask.Server.HotReload.Tests/Rask.Server.HotReload.Tests.csproj:8— RASK014 — 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 tests/Rask.Server.Tests/Rask.Server.Tests.csproj:8— RASK014 — 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 tests/Rask.Site.Tests/Rask.Site.Tests.csproj:8— RASK014 — 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 tests/Rask.Ui.Tests/Rask.Ui.Tests.csproj:10— RASK014 — 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 tests/Rask.Wasm.Tests/Rask.Wasm.Tests.csproj:17— RASK014 — 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 tests/Rask.DevTools.Fixture.Wasm/Rask.DevTools.Fixture.Wasm.csproj:24— IL2104 — 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 tests/Rask.Wasm.Fixture.Wasm/Rask.Wasm.Fixture.Wasm.csproj:25— IL2104 — 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 Directory.Build.props:106— 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 tests/Directory.Build.props:49— RASK115 — 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.
Captive dependency: singleton SessionKept captures scoped Type src/Rask.Core/Live/SessionKept.cs:4— `SessionKept` is registered as a SINGLETON but its constructor takes `Type Type`, which is registered as Scoped. The singleton captures one instance of the scoped dependency forever — defeating its lifetime (a per-request DbContext shared across all requests is a classic data-corruption/threading bug). Make the singleton resolve `Type` per-use (inject `IServiceScopeFactory` or a factory func), or align the lifetimes.
Captive dependency: singleton RaskMountedApp captures scoped Type src/Rask.Core/Routing/RaskMountedApp.cs:37— `RaskMountedApp` is registered as a SINGLETON but its constructor takes `Type root`, which is registered as Scoped. The singleton captures one instance of the scoped dependency forever — defeating its lifetime (a per-request DbContext shared across all requests is a classic data-corruption/threading bug). Make the singleton resolve `Type` per-use (inject `IServiceScopeFactory` or a factory func), or align the lifetimes.
Captive dependency: singleton AmbientContextBinding captures scoped Type src/Rask.Data/AmbientContextBinding.cs:18— `AmbientContextBinding` is registered as a SINGLETON but its constructor takes `Type contextType`, which is registered as Scoped. The singleton captures one instance of the scoped dependency forever — defeating its lifetime (a per-request DbContext shared across all requests is a classic data-corruption/threading bug). Make the singleton resolve `Type` per-use (inject `IServiceScopeFactory` or a factory func), or align the lifetimes.
Captive dependency: singleton Navigator captures scoped RouteState src/Rask.Core/Routing/Navigator.cs:21— `Navigator` is registered as a SINGLETON but its constructor takes `RouteState routeState`, which is registered as Scoped. The singleton captures one instance of the scoped dependency forever — defeating its lifetime (a per-request DbContext shared across all requests is a classic data-corruption/threading bug). Make the singleton resolve `RouteState` per-use (inject `IServiceScopeFactory` or a factory func), or align the lifetimes.
Captive dependency: singleton Navigator captures scoped IDownloadSink src/Rask.Core/Routing/Navigator.cs:21— `Navigator` is registered as a SINGLETON but its constructor takes `IDownloadSink downloadSink`, which is registered as Scoped. The singleton captures one instance of the scoped dependency forever — defeating its lifetime (a per-request DbContext shared across all requests is a classic data-corruption/threading bug). Make the singleton resolve `IDownloadSink` per-use (inject `IServiceScopeFactory` or a factory func), or align the lifetimes.
Captive dependency: singleton IPersistentState resolves scoped PersistentState from the root provider src/Rask.Wasm/WasmHostBuilder.cs:45— Building the SINGLETON `IPersistentState` resolves `PersistentState`, registered as Scoped, from the provider it was handed — the ROOT provider, outside any scope. The root provider keeps that instance for the life of the process, so the singleton is handed one scoped `PersistentState` forever (ASP.NET Core's scope validation rejects it in Development and lets it through in Production). Create a scope per use (`IServiceScopeFactory.CreateScope()`) and resolve `PersistentState` from the scope's provider, or align the lifetimes.
Captive dependency: singleton WasmUserWatch captures scoped IUserProvider src/Rask.Wasm/Authentication/WasmUserWatch.cs:29— `WasmUserWatch` is registered as a SINGLETON but its constructor takes `IUserProvider users`, which is registered as Scoped. The singleton captures one instance of the scoped dependency forever — defeating its lifetime (a per-request DbContext shared across all requests is a classic data-corruption/threading bug). Make the singleton resolve `IUserProvider` per-use (inject `IServiceScopeFactory` or a factory func), or align the lifetimes.
Captive dependency: singleton WasmAuthSignIn captures scoped IUserProvider src/Rask.Wasm/Authentication/WasmAuthSignIn.cs:17— `WasmAuthSignIn` is registered as a SINGLETON but its constructor takes `IUserProvider userProvider`, which is registered as Scoped. The singleton captures one instance of the scoped dependency forever — defeating its lifetime (a per-request DbContext shared across all requests is a classic data-corruption/threading bug). Make the singleton resolve `IUserProvider` per-use (inject `IServiceScopeFactory` or a factory func), or align the lifetimes.
AnalyzerSeverityNone .editorconfig:270— RS0026 — this rule is switched off for every file the section matches, in every project under this directory, and the only record that it was ever switched off is this line: nothing at the sites it would have reported says so, so a reader of that code has no reason to look here, and code added years from now inherits the decision silently. Fix what the rule reports and delete the entry, or — where some sites really are legitimate — leave the rule on and suppress it at those sites with their reasons, so it keeps protecting the rest of the tree. If the rule is genuinely unwanted here, say why — on this line after the entry, or in the comment run directly above it: a comment that only repeats the rule's own title is read as no explanation at all and leaves this row in place.
AnalyzerSeverityNone .editorconfig:271— RS0027 — this rule is switched off for every file the section matches, in every project under this directory, and the only record that it was ever switched off is this line: nothing at the sites it would have reported says so, so a reader of that code has no reason to look here, and code added years from now inherits the decision silently. Fix what the rule reports and delete the entry, or — where some sites really are legitimate — leave the rule on and suppress it at those sites with their reasons, so it keeps protecting the rest of the tree. If the rule is genuinely unwanted here, say why — on this line after the entry, or in the comment run directly above it: a comment that only repeats the rule's own title is read as no explanation at all and leaves this row in place.
AnalyzerSeverityNone .editorconfig:288— CS0108 — this rule is switched off for every file the section matches, in every project under this directory, and the only record that it was ever switched off is this line: nothing at the sites it would have reported says so, so a reader of that code has no reason to look here, and code added years from now inherits the decision silently. Fix what the rule reports and delete the entry, or — where some sites really are legitimate — leave the rule on and suppress it at those sites with their reasons, so it keeps protecting the rest of the tree. If the rule is genuinely unwanted here, say why — on this line after the entry, or in the comment run directly above it: a comment that only repeats the rule's own title is read as no explanation at all and leaves this row in place.
AnalyzerSeverityNone .editorconfig:301— MA0004 — this rule is switched off for every file the section matches, in every project under this directory, and the only record that it was ever switched off is this line: nothing at the sites it would have reported says so, so a reader of that code has no reason to look here, and code added years from now inherits the decision silently. Fix what the rule reports and delete the entry, or — where some sites really are legitimate — leave the rule on and suppress it at those sites with their reasons, so it keeps protecting the rest of the tree. If the rule is genuinely unwanted here, say why — on this line after the entry, or in the comment run directly above it: a comment that only repeats the rule's own title is read as no explanation at all and leaves this row in place.
AnalyzerSeverityNone .editorconfig:306— CA1716 — this rule is switched off for every file the section matches, in every project under this directory, and the only record that it was ever switched off is this line: nothing at the sites it would have reported says so, so a reader of that code has no reason to look here, and code added years from now inherits the decision silently. Fix what the rule reports and delete the entry, or — where some sites really are legitimate — leave the rule on and suppress it at those sites with their reasons, so it keeps protecting the rest of the tree. If the rule is genuinely unwanted here, say why — on this line after the entry, or in the comment run directly above it: a comment that only repeats the rule's own title is read as no explanation at all and leaves this row in place.
AnalyzerSeverityNone src/Rask.Templates/server/.editorconfig:17— CA2007 — this rule is switched off for every file the section matches, in every project under this directory, and the only record that it was ever switched off is this line: nothing at the sites it would have reported says so, so a reader of that code has no reason to look here, and code added years from now inherits the decision silently. Fix what the rule reports and delete the entry, or — where some sites really are legitimate — leave the rule on and suppress it at those sites with their reasons, so it keeps protecting the rest of the tree. If the rule is genuinely unwanted here, say why — on this line after the entry, or in the comment run directly above it: a comment that only repeats the rule's own title is read as no explanation at all and leaves this row in place.
AnalyzerSeverityNone src/Rask.Templates/wasm/.editorconfig:17— CA2007 — this rule is switched off for every file the section matches, in every project under this directory, and the only record that it was ever switched off is this line: nothing at the sites it would have reported says so, so a reader of that code has no reason to look here, and code added years from now inherits the decision silently. Fix what the rule reports and delete the entry, or — where some sites really are legitimate — leave the rule on and suppress it at those sites with their reasons, so it keeps protecting the rest of the tree. If the rule is genuinely unwanted here, say why — on this line after the entry, or in the comment run directly above it: a comment that only repeats the rule's own title is read as no explanation at all and leaves this row in place.
AnalyzerSeverityNone src/Rask.Templates/wasm-hosted/.editorconfig:17— CA2007 — this rule is switched off for every file the section matches, in every project under this directory, and the only record that it was ever switched off is this line: nothing at the sites it would have reported says so, so a reader of that code has no reason to look here, and code added years from now inherits the decision silently. Fix what the rule reports and delete the entry, or — where some sites really are legitimate — leave the rule on and suppress it at those sites with their reasons, so it keeps protecting the rest of the tree. If the rule is genuinely unwanted here, say why — on this line after the entry, or in the comment run directly above it: a comment that only repeats the rule's own title is read as no explanation at all and leaves this row in place.
Namespace dependency cycle src/Rask.Server/App/RaskAppOptions.cs:2— The namespaces Rask ↔ Rask.Auth ↔ Rask.Background ↔ Rask.Caching ↔ Rask.Core ↔ Rask.Core.Browser ↔ Rask.Core.Components ↔ Rask.Core.Diagnostics.DevTools ↔ Rask.Core.DragAndDrop ↔ Rask.Core.Forms ↔ Rask.Core.Globalization ↔ Rask.Core.HeadAssets ↔ Rask.Core.Live ↔ Rask.Core.Messaging ↔ Rask.Core.Routing ↔ Rask.Core.ScopedAssets ↔ Rask.Data ↔ Rask.Logging ↔ Rask.Mailing ↔ Rask.Outbox ↔ Rask.Querying ↔ Rask.SQLite ↔ Rask.Server ↔ Rask.Server.Authentication ↔ Rask.Server.Diagnostics ↔ Rask.Server.Files ↔ Rask.Server.Http ↔ Rask.Server.JSInterop ↔ Rask.Server.Prerender ↔ Rask.Storage ↔ Rask.Storage.Backends ↔ Rask.Storage.Serving ↔ Rask.Wasm ↔ Rask.WebPush depend on each other. The lightest dependency in the cycle is Rask → Rask.Auth (Rask.RaskAppOptions → Rask.Auth.AuthOptions, 1 type pair(s)); cut that one first, e.g. by moving the shared type to a namespace both can use or inverting it behind an interface.
Namespace dependency cycle src/Rask.Generators.Shared/ReadRelationship.cs:1— The namespaces Rask.Batteries.Generators ↔ Rask.Generators.Shared depend on each other. The lightest dependency in the cycle is Rask.Generators.Shared → Rask.Batteries.Generators (Rask.Generators.Shared.ReadRelationship → Rask.Batteries.Generators.EquatableArray, 2 type pair(s)); cut that one first, e.g. by moving the shared type to a namespace both can use or inverting it behind an interface.
Namespace dependency cycle src/Rask.Cli/Scaffolding/DeployConfig.cs:12— The namespaces Rask.Cli ↔ Rask.Cli.Scaffolding depend on each other. The lightest dependency in the cycle is Rask.Cli.Scaffolding → Rask.Cli (Rask.Cli.Scaffolding.DeployConfig → Rask.Cli.IConsole, 1 type pair(s)); cut that one first, e.g. by moving the shared type to a namespace both can use or inverting it behind an interface.
Namespace dependency cycle src/Rask.Site/Shared/GuideCards.cs:2— The namespaces Rask.Site ↔ Rask.Site.Features depend on each other. The lightest dependency in the cycle is Rask.Site → Rask.Site.Features (Rask.Site.GuideCards → Rask.Site.Features.GuideEntry, 2 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.
FileScopedPragmaDisable repeated across 119 files tests/Rask.Core.Tests/Authorization/HandlerAuthorizationTests.cs:10— The identical FileScopedPragmaDisable (`#pragma warning disable RASK014 // test-defined Component subclasses have no generated factories`) appears in 119 files (119 occurrences) — a single repo-wide policy (e.g. a Directory.Build.props decision or an idiomatic suppression), not 119 independent debts. Decide it once centrally rather than file-by-file. (Every occurrence still counts toward the score and metrics.)
FileScopedPragmaDisable repeated across 22 files tests/Rask.Core.Tests/Live/ConditionalSiblingIdentityTests.cs:6— The identical FileScopedPragmaDisable (`#pragma warning disable RASK014 // the test owns the root it re-renders; there is no parent to build it`) appears in 22 files (22 occurrences) — a single repo-wide policy (e.g. a Directory.Build.props decision or an idiomatic suppression), not 22 independent debts. Decide it once centrally rather than file-by-file. (Every occurrence still counts toward the score and metrics.)
FileScopedPragmaDisable repeated across 95 files tests/Rask.Server.E2E.Tests/AnAppSizesTheKitTests.cs:7— The identical FileScopedPragmaDisable (`#pragma warning disable RASK019 // a small test page; its <head> is not what is under test`) appears in 95 files (95 occurrences) — a single repo-wide policy (e.g. a Directory.Build.props decision or an idiomatic suppression), not 95 independent debts. Decide it once centrally rather than file-by-file. (Every occurrence still counts toward the score and metrics.)
FileScopedPragmaDisable repeated across 25 files tests/Rask.Server.E2E.Tests/AutofocusJourneyTests.cs:9— The identical FileScopedPragmaDisable (`#pragma warning disable RASK019 // a small test app; its <head> is not what is under test`) appears in 25 files (25 occurrences) — a single repo-wide policy (e.g. a Directory.Build.props decision or an idiomatic suppression), not 25 independent debts. Decide it once centrally rather than file-by-file. (Every occurrence still counts toward the score and metrics.)
FileScopedPragmaDisable repeated across 14 files tests/Rask.Server.Tests/Authentication/DeferredAuthNavTestApp.cs:7— The identical FileScopedPragmaDisable (`#pragma warning disable RASK019 // test-infra app predates framework-managed <head>`) appears in 14 files (14 occurrences) — a single repo-wide policy (e.g. a Directory.Build.props decision or an idiomatic suppression), not 14 independent debts. Decide it once centrally rather than file-by-file. (Every occurrence still counts toward the score and metrics.)
FileScopedPragmaDisable repeated across 54 files tests/Rask.Server.Tests/Authentication/SessionStaysItsUsersTests.EveryEvent.cs:12— The identical FileScopedPragmaDisable (`#pragma warning disable RASK019 // test-infra apps predate framework-managed <head>`) appears in 54 files (54 occurrences) — a single repo-wide policy (e.g. a Directory.Build.props decision or an idiomatic suppression), not 54 independent debts. Decide it once centrally rather than file-by-file. (Every occurrence still counts toward the score and metrics.)
S1 · Web-Security Posture· Cryptographic key material is a compile-time constant · ×1
Cryptographic key material is a compile-time constant src/Rask.Auth.Api/PasswordHasher.cs:36— `IdentityV3HeaderBytes` is the key-derivation salt and is a compile-time constant, so the secret this operation depends on is published with the source. A key that ships with the source is not secret: every contributor, fork, mirror and released binary carries it, so anyone holding the repository can decrypt what any installation encrypted, and there is no way to invalidate what was already protected because every deployment built from this source shares the value. Where the constant is a password salt the consequence differs but is no smaller — one global salt means precomputation amortises across every installation, which is the property salting exists to destroy. Read the value from configuration, an environment variable or a secrets manager at startup and FAIL FAST when it is absent, so a missing key stops the process instead of silently falling back to a shared default; treat the committed value as disclosed and rotate it rather than only deleting the line. For a salt, generate a fresh random one per password and store it alongside the hash.
Serious — 1055 finding(s)
P12 · CI test-gate honesty· Test project never run by CI · ×39
Test project never run by CI tests/Rask.Api.Client.Tests/Rask.Api.Client.Tests.csproj:1— `tests/Rask.Api.Client.Tests/Rask.Api.Client.Tests.csproj` declares 21 test(s), but no CI command runs it — it is not in the solution the pipeline tests and no step names it, so its tests gate nothing. Add it to the solution (or a test step), or delete it.
Test project never run by CI tests/Rask.Api.Generators.Tests/Rask.Api.Generators.Tests.csproj:1— `tests/Rask.Api.Generators.Tests/Rask.Api.Generators.Tests.csproj` declares 20 test(s), but no CI command runs it — it is not in the solution the pipeline tests and no step names it, so its tests gate nothing. Add it to the solution (or a test step), or delete it.
Test project never run by CI tests/Rask.Api.Tests/Rask.Api.Tests.csproj:1— `tests/Rask.Api.Tests/Rask.Api.Tests.csproj` declares 26 test(s), but no CI command runs it — it is not in the solution the pipeline tests and no step names it, so its tests gate nothing. Add it to the solution (or a test step), or delete it.
Test project never run by CI tests/Rask.Auth.Client.Tests/Rask.Auth.Client.Tests.csproj:1— `tests/Rask.Auth.Client.Tests/Rask.Auth.Client.Tests.csproj` declares 22 test(s), but no CI command runs it — it is not in the solution the pipeline tests and no step names it, so its tests gate nothing. Add it to the solution (or a test step), or delete it.
Test project never run by CI tests/Rask.Auth.SignInName.Tests/Rask.Auth.SignInName.Tests.csproj:1— `tests/Rask.Auth.SignInName.Tests/Rask.Auth.SignInName.Tests.csproj` declares 22 test(s), but no CI command runs it — it is not in the solution the pipeline tests and no step names it, so its tests gate nothing. Add it to the solution (or a test step), or delete it.
Test project never run by CI tests/Rask.Auth.Tests/Rask.Auth.Tests.csproj:1— `tests/Rask.Auth.Tests/Rask.Auth.Tests.csproj` declares 170 test(s), but no CI command runs it — it is not in the solution the pipeline tests and no step names it, so its tests gate nothing. Add it to the solution (or a test step), or delete it.
Test project never run by CI tests/Rask.Batteries.Generators.Tests/Rask.Batteries.Generators.Tests.csproj:1— `tests/Rask.Batteries.Generators.Tests/Rask.Batteries.Generators.Tests.csproj` declares 328 test(s), but no CI command runs it — it is not in the solution the pipeline tests and no step names it, so its tests gate nothing. Add it to the solution (or a test step), or delete it.
Test project never run by CI tests/Rask.Batteries.Tests/Rask.Batteries.Tests.csproj:1— `tests/Rask.Batteries.Tests/Rask.Batteries.Tests.csproj` declares 4 test(s), but no CI command runs it — it is not in the solution the pipeline tests and no step names it, so its tests gate nothing. Add it to the solution (or a test step), or delete it.
Test project never run by CI tests/Rask.Cache.Tests/Rask.Cache.Tests.csproj:1— `tests/Rask.Cache.Tests/Rask.Cache.Tests.csproj` declares 54 test(s), but no CI command runs it — it is not in the solution the pipeline tests and no step names it, so its tests gate nothing. Add it to the solution (or a test step), or delete it.
Test project never run by CI tests/Rask.Cli.E2E.Tests/Rask.Cli.E2E.Tests.csproj:1— `tests/Rask.Cli.E2E.Tests/Rask.Cli.E2E.Tests.csproj` declares 33 test(s), but no CI command runs it — it is not in the solution the pipeline tests and no step names it, so its tests gate nothing. Add it to the solution (or a test step), or delete it.
Test project never run by CI tests/Rask.Cli.Tests/Rask.Cli.Tests.csproj:1— `tests/Rask.Cli.Tests/Rask.Cli.Tests.csproj` declares 966 test(s), but no CI command runs it — it is not in the solution the pipeline tests and no step names it, so its tests gate nothing. Add it to the solution (or a test step), or delete it.
Test project never run by CI tests/Rask.Core.Tests/Rask.Core.Tests.csproj:1— `tests/Rask.Core.Tests/Rask.Core.Tests.csproj` declares 2968 test(s), but no CI command runs it — it is not in the solution the pipeline tests and no step names it, so its tests gate nothing. Add it to the solution (or a test step), or delete it.
Test project never run by CI tests/Rask.Cqrs.Client.Tests/Rask.Cqrs.Client.Tests.csproj:1— `tests/Rask.Cqrs.Client.Tests/Rask.Cqrs.Client.Tests.csproj` declares 29 test(s), but no CI command runs it — it is not in the solution the pipeline tests and no step names it, so its tests gate nothing. Add it to the solution (or a test step), or delete it.
Test project never run by CI tests/Rask.Cqrs.Codecs.Tests/Rask.Cqrs.Codecs.Tests.csproj:1— `tests/Rask.Cqrs.Codecs.Tests/Rask.Cqrs.Codecs.Tests.csproj` declares 21 test(s), but no CI command runs it — it is not in the solution the pipeline tests and no step names it, so its tests gate nothing. Add it to the solution (or a test step), or delete it.
Test project never run by CI tests/Rask.Cqrs.Server.Tests/Rask.Cqrs.Server.Tests.csproj:1— `tests/Rask.Cqrs.Server.Tests/Rask.Cqrs.Server.Tests.csproj` declares 44 test(s), but no CI command runs it — it is not in the solution the pipeline tests and no step names it, so its tests gate nothing. Add it to the solution (or a test step), or delete it.
Test project never run by CI tests/Rask.Cqrs.Tests/Rask.Cqrs.Tests.csproj:1— `tests/Rask.Cqrs.Tests/Rask.Cqrs.Tests.csproj` declares 103 test(s), but no CI command runs it — it is not in the solution the pipeline tests and no step names it, so its tests gate nothing. Add it to the solution (or a test step), or delete it.
Test project never run by CI tests/Rask.Cqrs.Transport.Tests/Rask.Cqrs.Transport.Tests.csproj:1— `tests/Rask.Cqrs.Transport.Tests/Rask.Cqrs.Transport.Tests.csproj` declares 31 test(s), but no CI command runs it — it is not in the solution the pipeline tests and no step names it, so its tests gate nothing. Add it to the solution (or a test step), or delete it.
Test project never run by CI tests/Rask.Dashboard.Tests/Rask.Dashboard.Tests.csproj:1— `tests/Rask.Dashboard.Tests/Rask.Dashboard.Tests.csproj` declares 101 test(s), but no CI command runs it — it is not in the solution the pipeline tests and no step names it, so its tests gate nothing. Add it to the solution (or a test step), or delete it.
Test project never run by CI tests/Rask.Data.Tests/Rask.Data.Tests.csproj:1— `tests/Rask.Data.Tests/Rask.Data.Tests.csproj` declares 842 test(s), but no CI command runs it — it is not in the solution the pipeline tests and no step names it, so its tests gate nothing. Add it to the solution (or a test step), or delete it.
Test project never run by CI tests/Rask.DevTools.E2E.Tests/Rask.DevTools.E2E.Tests.csproj:1— `tests/Rask.DevTools.E2E.Tests/Rask.DevTools.E2E.Tests.csproj` declares 11 test(s), but no CI command runs it — it is not in the solution the pipeline tests and no step names it, so its tests gate nothing. Add it to the solution (or a test step), or delete it.
Test project never run by CI tests/Rask.DevTools.Tests/Rask.DevTools.Tests.csproj:1— `tests/Rask.DevTools.Tests/Rask.DevTools.Tests.csproj` declares 171 test(s), but no CI command runs it — it is not in the solution the pipeline tests and no step names it, so its tests gate nothing. Add it to the solution (or a test step), or delete it.
Test project never run by CI tests/Rask.Generators.Tests/Rask.Generators.Tests.csproj:1— `tests/Rask.Generators.Tests/Rask.Generators.Tests.csproj` declares 572 test(s), but no CI command runs it — it is not in the solution the pipeline tests and no step names it, so its tests gate nothing. Add it to the solution (or a test step), or delete it.
Test project never run by CI tests/Rask.Jobs.Tests/Rask.Jobs.Tests.csproj:1— `tests/Rask.Jobs.Tests/Rask.Jobs.Tests.csproj` declares 152 test(s), but no CI command runs it — it is not in the solution the pipeline tests and no step names it, so its tests gate nothing. Add it to the solution (or a test step), or delete it.
Test project never run by CI tests/Rask.Logging.Tests/Rask.Logging.Tests.csproj:1— `tests/Rask.Logging.Tests/Rask.Logging.Tests.csproj` declares 54 test(s), but no CI command runs it — it is not in the solution the pipeline tests and no step names it, so its tests gate nothing. Add it to the solution (or a test step), or delete it.
Test project never run by CI tests/Rask.Mail.Tests/Rask.Mail.Tests.csproj:1— `tests/Rask.Mail.Tests/Rask.Mail.Tests.csproj` declares 42 test(s), but no CI command runs it — it is not in the solution the pipeline tests and no step names it, so its tests gate nothing. Add it to the solution (or a test step), or delete it.
+ 14 more in this group — see findings.md.
X2 · Cancellation propagation· Async method without CancellationToken · ×35
Async method without CancellationToken: SignOut src/Rask.Auth.Client/BrowserAuth.cs:47— No CancellationToken parameter — this work can't be stopped early once started.
Async method without CancellationToken: SignOutOtherDevices src/Rask.Auth.Client/BrowserAuth.cs:56— No CancellationToken parameter — this work can't be stopped early once started.
Async method without CancellationToken: SignOutEverywhere src/Rask.Auth.Client/BrowserAuth.cs:63— No CancellationToken parameter — this work can't be stopped early once started.
Async method without CancellationToken: SignedOut src/Rask.Auth.Client/BrowserAuth.cs:72— No CancellationToken parameter — this work can't be stopped early once started.
Async method without CancellationToken: AddPasskey src/Rask.Auth.Client/BrowserAuth.cs:101— No CancellationToken parameter — this work can't be stopped early once started.
Async method without CancellationToken: SignInWithPasskey src/Rask.Auth.Client/BrowserAuth.cs:151— No CancellationToken parameter — this work can't be stopped early once started.
Async method without CancellationToken: AskAsync src/Rask.Auth.Client/BrowserAuth.cs:220— No CancellationToken parameter — this work can't be stopped early once started.
Async method without CancellationToken: PostAsync src/Rask.Auth.Client/BrowserAuth.cs:239— No CancellationToken parameter — this work can't be stopped early once started.
Async method without CancellationToken: ExchangeAsync src/Rask.Auth.Client/BrowserAuth.cs:262— No CancellationToken parameter — this work can't be stopped early once started.
Async method without CancellationToken: ReadFailureAsync src/Rask.Auth.Client/BrowserAuth.cs:293— No CancellationToken parameter — this work can't be stopped early once started.
Async method without CancellationToken: EnsureLoaded src/Rask.Auth.Client/HttpUserProvider.cs:46— No CancellationToken parameter — this work can't be stopped early once started.
Async method without CancellationToken: Refresh src/Rask.Auth.Client/HttpUserProvider.cs:57— No CancellationToken parameter — this work can't be stopped early once started.
Async method without CancellationToken: SignIn src/Rask.Auth/ServerAuth.cs:55— No CancellationToken parameter — this work can't be stopped early once started.
Async method without CancellationToken: SignOutOtherDevices src/Rask.Auth/ServerAuth.cs:71— No CancellationToken parameter — this work can't be stopped early once started.
Async method without CancellationToken: SignOutEverywhere src/Rask.Auth/ServerAuth.cs:73— No CancellationToken parameter — this work can't be stopped early once started.
Async method without CancellationToken: SendPasswordReset src/Rask.Auth/ServerAuth.cs:79— No CancellationToken parameter — this work can't be stopped early once started.
Async method without CancellationToken: ResetPassword src/Rask.Auth/ServerAuth.cs:82— No CancellationToken parameter — this work can't be stopped early once started.
Async method without CancellationToken: ConfirmEmail src/Rask.Auth/ServerAuth.cs:85— No CancellationToken parameter — this work can't be stopped early once started.
Async method without CancellationToken: AddPasskey src/Rask.Auth/ServerAuth.cs:88— No CancellationToken parameter — this work can't be stopped early once started.
Async method without CancellationToken: SignInWithPasskey src/Rask.Auth/ServerAuth.cs:142— No CancellationToken parameter — this work can't be stopped early once started.
Async method without CancellationToken: RemovePasskey src/Rask.Auth/ServerAuth.cs:188— No CancellationToken parameter — this work can't be stopped early once started.
Async method without CancellationToken: ChooseTenantAsync src/Rask.Auth/ServerAuth.cs:204— No CancellationToken parameter — this work can't be stopped early once started.
Async method without CancellationToken: RegisterCoreAsync src/Rask.Auth/ServerAuth.cs:216— No CancellationToken parameter — this work can't be stopped early once started.
Async method without CancellationToken: ConfirmDropAsync src/Rask.Cli/Commands/DbCommand.cs:300— No CancellationToken parameter — this work can't be stopped early once started.
Async method without CancellationToken: ResolveProjectAsync src/Rask.Cli/Commands/DeployCommand.Planning.cs:155— No CancellationToken parameter — this work can't be stopped early once started.
TooManyMethods: Component src/Rask.Core/Component.Handlers.cs— TooManyMethods — 1654 significant lines (blank, comment-only and punctuation-only lines excluded), 207 methods, declared across 20 files: Rask.Core/Component.Handlers.cs (40), Rask.Core/Component.Lifecycle.cs (26), Rask.Core/Component.cs (23), Rask.Core/Component.LiveRender.cs (19), +16 more file(s). The bar is 30 methods; this is 177 over it, 6.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: ComponentFactoryGenerator src/Rask.Generators/ComponentFactoryGenerator.ComponentModel.cs— TooManyMethods — 2742 significant lines (blank, comment-only and punctuation-only lines excluded), 205 methods, declared across 11 files: Rask.Generators/ComponentFactoryGenerator.ComponentModel.cs (39), Rask.Generators/ComponentFactoryGenerator.SetterOverloads.cs (34), Rask.Generators/ComponentFactoryGenerator.Setters.cs (28), Rask.Generators/ComponentFactoryGenerator.EntryHosts.cs (26), +7 more file(s). The bar is 30 methods; this is 175 over it, 6.83× the bar. The type holds no instance state, so there is no shared data to group its members by. To reduce it, split it by area instead: give each cohesive family of members its own smaller type, so no one type has to be read whole to change one of them.
TooManyMethods: RaskEndpointExtensions REDACTED— TooManyMethods — 2358 significant lines (blank, comment-only and punctuation-only lines excluded), 202 methods, declared across 4 files: REDACTED (159), Rask.Server/RaskEndpointExtensions.SessionUser.cs (35), Rask.Server/RaskEndpointExtensions.AuthRedeem.cs (5), Rask.Server/RaskEndpointExtensions.CaughtUp.cs (3). The bar is 30 methods; this is 172 over it, 6.73× the bar. The type holds no instance state, so there is no shared data to group its members by. To reduce it, split it by area instead: give each cohesive family of members its own smaller type, so no one type has to be read whole to change one of them.
TooManyMethods: ModelInputGenerator src/Rask.Batteries.Generators/ModelInputGenerator.Model.cs— TooManyMethods — 1990 significant lines (blank, comment-only and punctuation-only lines excluded), 147 methods, declared across 9 files: Rask.Batteries.Generators/ModelInputGenerator.Model.cs (29), Rask.Batteries.Generators/ModelInputGenerator.WriteRules.cs (28), Rask.Batteries.Generators/ModelInputGenerator.Rules.cs (23), Rask.Batteries.Generators/ModelInputGenerator.ModelClass.cs (21), +5 more file(s). The bar is 30 methods; this is 117 over it, 4.90× the bar. The type holds no instance state, so there is no shared data to group its members by. To reduce it, split it by area instead: give each cohesive family of members its own smaller type, so no one type has to be read whole to change one of them.
TooManyMethods: UiSelectControl src/Rask.Ui/UiSelectControl.Drawn.cs— TooManyMethods — 715 significant lines (blank, comment-only and punctuation-only lines excluded), 91 methods, declared across 10 files: Rask.Ui/UiSelectControl.Drawn.cs (21), Rask.Ui/UiSelectControl.Popup.cs (15), Rask.Ui/UiSelectControl.Held.cs (12), Rask.Ui/UiSelectControl.Pills.cs (12), +6 more file(s). The bar is 30 methods; this is 61 over it, 3.03× 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: DeployCommand src/Rask.Cli/Commands/DeployCommand.Rollout.cs— TooManyMethods — 1109 significant lines (blank, comment-only and punctuation-only lines excluded), 85 methods, declared across 5 files: Commands/DeployCommand.Rollout.cs (26), Commands/DeployCommand.Planning.cs (19), Commands/DeployCommand.Proxy.cs (17), Commands/DeployCommand.Ops.cs (15), +1 more file(s). The bar is 30 methods; this is 55 over it, 2.83× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: LiveSession src/Rask.Server/LiveSession.cs— TooManyMethods — 584 significant lines (blank, comment-only and punctuation-only lines excluded), 79 methods. The bar is 30 methods; this is 49 over it, 2.63× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: EditContext src/Rask.Core/Forms/EditContext.cs— TooManyMethods — 430 significant lines (blank, comment-only and punctuation-only lines excluded), 62 methods, declared across 6 files: Forms/EditContext.cs (27), Forms/EditContext.FieldFailures.cs (13), Forms/EditContext.Validation.cs (8), Forms/EditContext.AsyncValidation.cs (7), +2 more file(s). The bar is 30 methods; this is 32 over it, 2.07× 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: LiveSessionBase src/Rask.Core/Live/LiveSessionBase.cs— TooManyMethods — 362 significant lines (blank, comment-only and punctuation-only lines excluded), 60 methods. The bar is 30 methods; this is 30 over it, 2.00× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: JsChain src/Rask.Web/JsChain.cs— TooManyMethods — 286 significant lines (blank, comment-only and punctuation-only lines excluded), 59 methods. The bar is 30 methods; this is 29 over it, 1.97× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: RoutesGenerator src/Rask.Generators/RoutesGenerator.Factories.cs— TooManyMethods — 998 significant lines (blank, comment-only and punctuation-only lines excluded), 57 methods, declared across 7 files: Rask.Generators/RoutesGenerator.Factories.cs (19), Rask.Generators/RoutesGenerator.Model.cs (13), Rask.Generators/RoutesGenerator.RoutesClass.cs (8), Rask.Generators/RoutesGenerator.Diagnostics.cs (6), +3 more file(s). The bar is 30 methods; this is 27 over it, 1.90× the bar. The type holds no instance state, so there is no shared data to group its members by. To reduce it, split it by area instead: give each cohesive family of members its own smaller type, so no one type has to be read whole to change one of them.
TooManyMethods: SessionQueryClient src/Rask.Query/SessionQueryClient.cs— TooManyMethods — 368 significant lines (blank, comment-only and punctuation-only lines excluded), 49 methods. The bar is 30 methods; this is 19 over it, 1.63× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: FrameDiffer src/Rask.Core/Live/FrameDiffer.cs— TooManyMethods — 706 significant lines (blank, comment-only and punctuation-only lines excluded), 46 methods, declared across 3 files: Live/FrameDiffer.cs (34), Live/FrameDiffer.OneRun.cs (10), Live/FrameDiffer.RefusedLevel.cs (2). The bar is 30 methods; this is 16 over it, 1.53× the bar. The type holds no instance state, so there is no shared data to group its members by. To reduce it, split it by area instead: give each cohesive family of members its own smaller type, so no one type has to be read whole to change one of them.
TooManyMethods: DomValueTypes src/Rask.Dom.Tasks/DomValueTypes.cs— TooManyMethods — 388 significant lines (blank, comment-only and punctuation-only lines excluded), 42 methods. The bar is 30 methods; this is 12 over it, 1.40× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: GeneratedModelShape src/Rask.Generators.Shared/GeneratedModelShape.cs— TooManyMethods — 335 significant lines (blank, comment-only and punctuation-only lines excluded), 42 methods. The bar is 30 methods; this is 12 over it, 1.40× the bar. The type holds no instance state, so there is no shared data to group its members by. To reduce it, split it by area instead: give each cohesive family of members its own smaller type, so no one type has to be read whole to change one of them.
TooManyMethods: LivePayload src/Rask.Core/Live/LivePayload.cs— TooManyMethods — 545 significant lines (blank, comment-only and punctuation-only lines excluded), 40 methods. The bar is 30 methods; this is 10 over it, 1.33× the bar. The type holds no instance state, so there is no shared data to group its members by. To reduce it, split it by area instead: give each cohesive family of members its own smaller type, so no one type has to be read whole to change one of them.
TooManyMethods: JobProcessor src/Rask.Jobs/JobProcessor.cs— TooManyMethods — 440 significant lines (blank, comment-only and punctuation-only lines excluded), 40 methods. The bar is 30 methods; this is 10 over it, 1.33× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: Refresh scripts/mdn/refresh.py:83— TooManyMethods — 39 methods. The bar is 30 methods; this is 9 over it, 1.30× the bar. This type is on a published API surface — Microsoft.CodeAnalysis.PublicApiAnalyzers (PublicAPI.Shipped.txt) (Directory.Build.targets) declares its compatibility contractual — so moving members onto a smaller type is a breaking change for every consumer, not a local refactor. To reduce it, treat the split as an API migration: move each cohesive group onto its own published type and keep the old members as deprecated forwards for a deprecation period, removing them at the next compatibility break. Where the surface has to stay as it is, that is a decision to record rather than a change to make.
TooManyMethods: DbCommand src/Rask.Cli/Commands/DbCommand.Backup.cs— TooManyMethods — 543 significant lines (blank, comment-only and punctuation-only lines excluded), 38 methods, declared across 2 files: Commands/DbCommand.Backup.cs (25), Commands/DbCommand.cs (13). The bar is 30 methods; this is 8 over it, 1.27× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: DomEmitter src/Rask.Dom.Tasks/DomEmitter.cs— TooManyMethods — 393 significant lines (blank, comment-only and punctuation-only lines excluded), 38 methods. The bar is 30 methods; this is 8 over it, 1.27× the bar. The type holds no instance state, so there is no shared data to group its members by. To reduce it, split it by area instead: give each cohesive family of members its own smaller type, so no one type has to be read whole to change one of them.
TooManyMethods: ModelQuery src/Rask.Data/ModelQuery.cs— TooManyMethods — 135 significant lines (blank, comment-only and punctuation-only lines excluded), 38 methods. The bar is 30 methods; this is 8 over it, 1.27× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: ScopedAssetRegistry src/Rask.Core/ScopedAssets/ScopedAssetRegistry.cs— TooManyMethods — 409 significant lines (blank, comment-only and punctuation-only lines excluded), 37 methods. The bar is 30 methods; this is 7 over it, 1.23× the bar. The type holds no instance state, so there is no shared data to group its members by. To reduce it, split it by area instead: give each cohesive family of members its own smaller type, so no one type has to be read whole to change one of them.
TooManyMethods: WasmLiveSession src/Rask.Wasm/WasmLiveSession.cs— TooManyMethods — 425 significant lines (blank, comment-only and punctuation-only lines excluded), 36 methods. The bar is 30 methods; this is 6 over it, 1.20× 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: ModelRegistryGenerator src/Rask.Batteries.Generators/ModelRegistryGenerator.cs— TooManyMethods — 571 significant lines (blank, comment-only and punctuation-only lines excluded), 35 methods, declared across 4 files: Rask.Batteries.Generators/ModelRegistryGenerator.cs (27), Rask.Batteries.Generators/ModelRegistryGenerator.ConstructorBuiltHolders.cs (4), Rask.Batteries.Generators/ModelRegistryGenerator.NoListBehind.cs (2), Rask.Batteries.Generators/ModelRegistryGenerator.ReferenceValues.cs (2). The bar is 30 methods; this is 5 over it, 1.17× the bar. The type holds no instance state, so there is no shared data to group its members by. To reduce it, split it by area instead: give each cohesive family of members its own smaller type, so no one type has to be read whole to change one of them.
TooManyMethods: UiColorPicker src/Rask.Ui/UiColorPicker.Popover.cs— TooManyMethods — 397 significant lines (blank, comment-only and punctuation-only lines excluded), 35 methods, declared across 4 files: Rask.Ui/UiColorPicker.Popover.cs (18), Rask.Ui/UiColorPicker.Trigger.cs (8), Rask.Ui/UiColorPicker.State.cs (6), Rask.Ui/UiColorPicker.cs (3). The bar is 30 methods; this is 5 over it, 1.17× 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/Rask.Core/Resources/rask-morph.ts src/Rask.Core/Resources/rask-morph.ts:583— src/Rask.Core/Resources/rask-morph.ts changed 28 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 97 in rask-morph.morphNode at line 583. 13 of those changes were fix/bug commits, and the other 15 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-08-08..2026-11-06, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-08 15:23:35 +01:00' --until='2026-11-06 15:23:35 +01:00' --full-history --no-merges -- src/Rask.Core/Resources/rask-morph.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: REDACTED REDACTED:199— REDACTED changed 36 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 45 in rask-dom.applyOps at line 199. 16 of those changes were fix/bug commits, and the other 20 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-08-08..2026-11-06, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-08 15:23:35 +01:00' --until='2026-11-06 15:23:35 +01:00' --full-history --no-merges -- REDACTED`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: src/Rask.Server/Resources/rask.ts src/Rask.Server/Resources/rask.ts:593— src/Rask.Server/Resources/rask.ts changed 62 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 26 in rask.onFrame at line 593. 24 of those changes were fix/bug commits, and the other 38 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-08-08..2026-11-06, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-08 15:23:35 +01:00' --until='2026-11-06 15:23:35 +01:00' --full-history --no-merges -- src/Rask.Server/Resources/rask.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/Rask.Core/Live/LiveSessionBase.cs src/Rask.Core/Live/LiveSessionBase.cs:1028— src/Rask.Core/Live/LiveSessionBase.cs changed 51 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 19 in LiveSessionBase.TryWriteDiff at line 1028. 24 of those changes were fix/bug commits, and the other 27 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-08-08..2026-11-06, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-08 15:23:35 +01:00' --until='2026-11-06 15:23:35 +01:00' --full-history --no-merges -- src/Rask.Core/Live/LiveSessionBase.cs`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: src/Rask.Wasm/WasmLiveSession.cs src/Rask.Wasm/WasmLiveSession.cs:452— src/Rask.Wasm/WasmLiveSession.cs changed 40 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 15 in WasmLiveSession.DispatchAsync at line 452. 17 of those changes were fix/bug commits, and the other 23 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-08-08..2026-11-06, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-08 15:23:35 +01:00' --until='2026-11-06 15:23:35 +01:00' --full-history --no-merges -- src/Rask.Wasm/WasmLiveSession.cs`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: src/Rask.Core/Resources/rask-api.ts src/Rask.Core/Resources/rask-api.ts:120— src/Rask.Core/Resources/rask-api.ts changed 19 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 24 in rask-api.raskWebData at line 120. 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-08-08..2026-11-06, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-08 15:23:35 +01:00' --until='2026-11-06 15:23:35 +01:00' --full-history --no-merges -- src/Rask.Core/Resources/rask-api.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/Rask.Core/Resources/rask-calendar.ts src/Rask.Core/Resources/rask-calendar.ts:447— src/Rask.Core/Resources/rask-calendar.ts changed 10 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 33 in rask-calendar.paintDay at line 447. 5 of those changes were fix/bug commits, and the other 5 changed it for other reasons — this file is under both repair and feature pressure. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-08-08..2026-11-06, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-08 15:23:35 +01:00' --until='2026-11-06 15:23:35 +01:00' --full-history --no-merges -- src/Rask.Core/Resources/rask-calendar.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: REDACTED REDACTED:54— REDACTED changed 6 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 52 in panel-client.installPanelClient at line 54. 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-08-08..2026-11-06, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-08 15:23:35 +01:00' --until='2026-11-06 15:23:35 +01:00' --full-history --no-merges -- REDACTED`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: src/Rask.Core/Resources/rask-events.ts src/Rask.Core/Resources/rask-events.ts:40— src/Rask.Core/Resources/rask-events.ts changed 16 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 19 in rask-events.domEvents.forEach() at line 40. 5 of those changes were fix/bug commits, and the other 11 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-08-08..2026-11-06, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-08 15:23:35 +01:00' --until='2026-11-06 15:23:35 +01:00' --full-history --no-merges -- src/Rask.Core/Resources/rask-events.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/Rask.Generators.Shared/GeneratedModelShape.cs src/Rask.Generators.Shared/GeneratedModelShape.cs:389— src/Rask.Generators.Shared/GeneratedModelShape.cs changed 20 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 15 in GeneratedModelShape.DescribeChild at line 389. 6 of those changes were fix/bug commits, and the other 14 changed it for other reasons — this file is under both repair and feature pressure. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-08-08..2026-11-06, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-08 15:23:35 +01:00' --until='2026-11-06 15:23:35 +01:00' --full-history --no-merges -- src/Rask.Generators.Shared/GeneratedModelShape.cs`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: src/Rask.Core/Resources/rask-overlay.ts src/Rask.Core/Resources/rask-overlay.ts:255— src/Rask.Core/Resources/rask-overlay.ts changed 7 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 40 in rask-overlay.installModal at line 255. 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-08-08..2026-11-06, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-08 15:23:35 +01:00' --until='2026-11-06 15:23:35 +01:00' --full-history --no-merges -- src/Rask.Core/Resources/rask-overlay.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/Rask.Site/Features/Home/HeroCode.cs src/Rask.Site/Features/Home/HeroCode.cs:137— src/Rask.Site/Features/Home/HeroCode.cs changed 14 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 19 in HeroCode.Highlight at line 137. 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-08-08..2026-11-06, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-08 15:23:35 +01:00' --until='2026-11-06 15:23:35 +01:00' --full-history --no-merges -- src/Rask.Site/Features/Home/HeroCode.cs`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: src/Rask.Generators/Analyzers/BuilderEntry.cs src/Rask.Generators/Analyzers/BuilderEntry.cs:318— src/Rask.Generators/Analyzers/BuilderEntry.cs changed 15 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 17 in BuilderEntry.IsGroupedEntry at line 318. 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-08-08..2026-11-06, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-08 15:23:35 +01:00' --until='2026-11-06 15:23:35 +01:00' --full-history --no-merges -- src/Rask.Generators/Analyzers/BuilderEntry.cs`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: src/Rask.Dom.Tasks/DomValueTypes.cs src/Rask.Dom.Tasks/DomValueTypes.cs:194— src/Rask.Dom.Tasks/DomValueTypes.cs changed 10 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 25 in DomValueTypes.Map at line 194. 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-08-08..2026-11-06, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-08 15:23:35 +01:00' --until='2026-11-06 15:23:35 +01:00' --full-history --no-merges -- src/Rask.Dom.Tasks/DomValueTypes.cs`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: src/Rask.Batteries.Generators/CqrsDispatchGenerator.cs src/Rask.Batteries.Generators/CqrsDispatchGenerator.cs:65— src/Rask.Batteries.Generators/CqrsDispatchGenerator.cs changed 14 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 15 in CqrsDispatchGenerator.GetCandidate at line 65. 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-08-08..2026-11-06, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-08 15:23:35 +01:00' --until='2026-11-06 15:23:35 +01:00' --full-history --no-merges -- src/Rask.Batteries.Generators/CqrsDispatchGenerator.cs`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: src/Rask.Core/Component.StaleEvents.cs src/Rask.Core/Component.StaleEvents.cs:77— src/Rask.Core/Component.StaleEvents.cs changed 8 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 25 in Component.TryFindHandler at line 77. 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-08-08..2026-11-06, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-08 15:23:35 +01:00' --until='2026-11-06 15:23:35 +01:00' --full-history --no-merges -- src/Rask.Core/Component.StaleEvents.cs`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: scripts/lib/affected_projects.py scripts/lib/affected_projects.py:139— scripts/lib/affected_projects.py changed 5 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 38 in affected_projects.main at line 139. 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-08-08..2026-11-06, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-08 15:23:35 +01:00' --until='2026-11-06 15:23:35 +01:00' --full-history --no-merges -- scripts/lib/affected_projects.py`: 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/Rask.Wasm/Resources/rask-wasm-api.ts src/Rask.Wasm/Resources/rask-wasm-api.ts:25— src/Rask.Wasm/Resources/rask-wasm-api.ts changed 10 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 18 in applyManifest at line 25. 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-08-08..2026-11-06, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-08 15:23:35 +01:00' --until='2026-11-06 15:23:35 +01:00' --full-history --no-merges -- src/Rask.Wasm/Resources/rask-wasm-api.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/Rask.Core/Resources/rask-list.ts src/Rask.Core/Resources/rask-list.ts:562— src/Rask.Core/Resources/rask-list.ts changed 9 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 18 in rask-list.picked at line 562. 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-08-08..2026-11-06, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-08 15:23:35 +01:00' --until='2026-11-06 15:23:35 +01:00' --full-history --no-merges -- src/Rask.Core/Resources/rask-list.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/Rask.Dom.Tasks/WebMember.cs src/Rask.Dom.Tasks/WebMember.cs:148— src/Rask.Dom.Tasks/WebMember.cs changed 9 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 17 in WebMember.Expand at line 148. 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-08-08..2026-11-06, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-08 15:23:35 +01:00' --until='2026-11-06 15:23:35 +01:00' --full-history --no-merges -- src/Rask.Dom.Tasks/WebMember.cs`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: src/Rask.Ui/Resources/phone/ui-phone.ts src/Rask.Ui/Resources/phone/ui-phone.ts:397— src/Rask.Ui/Resources/phone/ui-phone.ts changed 4 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 30 in ui-phone.handle at line 397. 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-08-08..2026-11-06, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-08 15:23:35 +01:00' --until='2026-11-06 15:23:35 +01:00' --full-history --no-merges -- src/Rask.Ui/Resources/phone/ui-phone.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/Rask.Server/Resources/rask-http-transport.ts src/Rask.Server/Resources/rask-http-transport.ts:393— src/Rask.Server/Resources/rask-http-transport.ts changed 7 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 15 in rask-http-transport.openHttpConnection.parse at line 393. 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-08-08..2026-11-06, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-08 15:23:35 +01:00' --until='2026-11-06 15:23:35 +01:00' --full-history --no-merges -- src/Rask.Server/Resources/rask-http-transport.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/Rask.DevTools/Resources/host/bridge.ts src/Rask.DevTools/Resources/host/bridge.ts:48— src/Rask.DevTools/Resources/host/bridge.ts changed 5 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 17 in bridge.createBridge.handle at line 48. 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-08-08..2026-11-06, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-08 15:23:35 +01:00' --until='2026-11-06 15:23:35 +01:00' --full-history --no-merges -- src/Rask.DevTools/Resources/host/bridge.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/Rask.Core/Resources/rask-deverror.ts src/Rask.Core/Resources/rask-deverror.ts:232— src/Rask.Core/Resources/rask-deverror.ts changed 4 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 20 in rask-deverror.showDevError at line 232. 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-08-08..2026-11-06, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-08 15:23:35 +01:00' --until='2026-11-06 15:23:35 +01:00' --full-history --no-merges -- src/Rask.Core/Resources/rask-deverror.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/Rask.Core/Resources/rask-carousel.ts src/Rask.Core/Resources/rask-carousel.ts:116— src/Rask.Core/Resources/rask-carousel.ts changed 4 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 15 in rask-carousel.sync at line 116. 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-08-08..2026-11-06, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-08 15:23:35 +01:00' --until='2026-11-06 15:23:35 +01:00' --full-history --no-merges -- src/Rask.Core/Resources/rask-carousel.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.
Repeated repair: src/Rask.Core/Component.Handlers.cs src/Rask.Core/Component.Handlers.cs:737— src/Rask.Core/Component.Handlers.cs changed 24 times in last 90 days and 15 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 8 (its worst body is Component.ExtractStringList at line 737), UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “fix(live): a repaint made while a handler awaits is drawn in its dispatch flow”; “fix(server): a confirmed press reaches its handler on a page redrawn every few ms”; “fix(core): a walk that sent nothing no longer pushes a press out of its slot's memory”; “fix(server): a revalidation or handler cancelled with its client ends quietly”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-08-08..2026-11-06, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-08 15:23:35 +01:00' --until='2026-11-06 15:23:35 +01:00' --full-history --no-merges -- src/Rask.Core/Component.Handlers.cs`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Repeated repair: src/Rask.Ui/UiTimePicker.cs src/Rask.Ui/UiTimePicker.cs:153— src/Rask.Ui/UiTimePicker.cs changed 15 times in last 90 days and 9 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 6 (its worst body is UiTimePicker.Render at line 153), UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “fix(ui): a disabled kit control writes nothing, and a calendar takes only a day it drew”; “fix(ui): draw a picker's clear control inside its trigger, as Flux does”; “fix(ui): a class on the date and time picker sizes it, as Flux's does”; “fix(ui): the time picker opens on its start row without a script and records its bundle cost”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-08-08..2026-11-06, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-08 15:23:35 +01:00' --until='2026-11-06 15:23:35 +01:00' --full-history --no-merges -- src/Rask.Ui/UiTimePicker.cs`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Repeated repair: src/Rask.Core/Resources/rask-owned.ts src/Rask.Core/Resources/rask-owned.ts:411— src/Rask.Core/Resources/rask-owned.ts changed 15 times in last 90 days and 8 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 9 (its worst body is rask-owned.said at line 411), UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “fix(ui): a tooltip left before the hooks arrived stays hidden; the side test moves off each bubble”; “fix(runtime): the busy hold lives on the seam in rask-owned.ts; otp-submit is no reason to load”; “fix(ui): wip - a list's own rewrite ends the pause, and a pressed suggestion keeps the focus”; “fix(ui)!: a kit control drawing itself does not send what the reader typed”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-08-08..2026-11-06, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-08 15:23:35 +01:00' --until='2026-11-06 15:23:35 +01:00' --full-history --no-merges -- src/Rask.Core/Resources/rask-owned.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.
Repeated repair: src/Rask.Core/Component.Lifecycle.cs src/Rask.Core/Component.Lifecycle.cs:143— src/Rask.Core/Component.Lifecycle.cs changed 12 times in last 90 days and 7 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 7 (its worst body is Component.AfterRendered at line 143), UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “fix(core): a hook's continuation waits until its walk has held the hook's event”; “fix(live): each component's part of a live event gets its own scoped services”; “fix(live): a first request whose hook detaches its read is answered at once”; “fix(live): a hook that outlives its navigation keeps its event's scope until it is done”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-08-08..2026-11-06, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-08 15:23:35 +01:00' --until='2026-11-06 15:23:35 +01:00' --full-history --no-merges -- src/Rask.Core/Component.Lifecycle.cs`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Repeated repair: src/Rask.Core/Resources/rask-menu.ts src/Rask.Core/Resources/rask-menu.ts:228— src/Rask.Core/Resources/rask-menu.ts changed 9 times in last 90 days and 7 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 12 (its worst body is rask-menu.leave at line 228), UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “fix(ui): a submenu's row is entered again only when the pointer came from outside it”; “fix(ui): a submenu's flyout closes when the pointer moves on out of the menu, as Flux UI's”; “fix(ui): a pointer whose safe area went with the flyout enters the row it is over”; “fix(ui): an arrow that shuts a flyout under the pointer hands the light back to its row”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-08-08..2026-11-06, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-08 15:23:35 +01:00' --until='2026-11-06 15:23:35 +01:00' --full-history --no-merges -- src/Rask.Core/Resources/rask-menu.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.
Repeated repair: src/Rask.Core/Resources/rask-hover.ts src/Rask.Core/Resources/rask-hover.ts:123— src/Rask.Core/Resources/rask-hover.ts changed 9 times in last 90 days and 7 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 8 (its worst body is rask-hover.look at line 123), UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “fix(ui): a tooltip left before the hooks arrived stays hidden; the side test moves off each bubble”; “fix(ui): a tooltip stays while the pointer moves from its trigger onto it, as Flux's does”; “fix(ui): a finger shows a tooltip and holds a toast as Flux's does on a phone”; “fix(core): popovers, lists and pills answer a finger as Flux UI's do”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-08-08..2026-11-06, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-08 15:23:35 +01:00' --until='2026-11-06 15:23:35 +01:00' --full-history --no-merges -- src/Rask.Core/Resources/rask-hover.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.
Repeated repair: src/Rask.Ui/UiSelectControl.Keyboard.cs src/Rask.Ui/UiSelectControl.Keyboard.cs:74— src/Rask.Ui/UiSelectControl.Keyboard.cs changed 11 times in last 90 days and 6 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 6 (its worst body is UiSelectControl.HearingMarks at line 74), UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “fix(ui): a disabled kit control writes nothing, and a calendar takes only a day it drew”; “fix(ui): a pick under a debounced search no longer waits on the browser after the page navigated”; “fix(ui): a row of Ui.Select pressed before the page answered the list opening is picked”; “fix(ui)!: a kit control drawing itself does not send what the reader typed”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-08-08..2026-11-06, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-08 15:23:35 +01:00' --until='2026-11-06 15:23:35 +01:00' --full-history --no-merges -- src/Rask.Ui/UiSelectControl.Keyboard.cs`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Repeated repair: src/Rask.Core/Live/EventServices.cs src/Rask.Core/Live/EventServices.cs:337— src/Rask.Core/Live/EventServices.cs changed 6 times in last 90 days and 6 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 12 (its worst body is EventServices.Life at line 337), UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “fix(live)!: a hook's scope ends with the hook; detached work opens its own (#1265)”; “fix(live): a hook's lent provider lets its scope go once nothing holds it (#1265)”; “fix(query): a sent command runs to its end; a page that left drops its answer silently”; “fix(live): each component's part of a live event gets its own scoped services”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-08-08..2026-11-06, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-08 15:23:35 +01:00' --until='2026-11-06 15:23:35 +01:00' --full-history --no-merges -- src/Rask.Core/Live/EventServices.cs`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Repeated repair: src/Rask.Ui/UiPillboxLook.cs src/Rask.Ui/UiPillboxLook.cs:94— src/Rask.Ui/UiPillboxLook.cs changed 9 times in last 90 days and 5 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 2 (its worst body is UiPillboxLook.TriggerSize at line 94), UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “fix(ui): the pillbox chevron darkens under the pointer, as Flux's”; “fix(core): popovers, lists and pills answer a finger as Flux UI's do”; “fix(ui): fields, editor, navlist and groups take Flux's phone sizes”; “fix(ui): typing in a list's search field does not make a ConfirmLeave form unsaved”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-08-08..2026-11-06, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-08 15:23:35 +01:00' --until='2026-11-06 15:23:35 +01:00' --full-history --no-merges -- src/Rask.Ui/UiPillboxLook.cs`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Repeated repair: src/Rask.Ui/UiDatePickerButton.cs src/Rask.Ui/UiDatePickerButton.cs:45— src/Rask.Ui/UiDatePickerButton.cs changed 9 times in last 90 days and 5 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 6 (its worst body is UiDatePickerButton.Render at line 45), UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “fix(ui): darken a date picker button's chevron under its pointer or tap, as Flux”; “fix(ui): round a range's last-row end as Flux does, and write the chosen date in a div”; “fix(ui): draw a picker's clear control inside its trigger, as Flux does”; “fix(ui)!: a kit control drawing itself does not send what the reader typed”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-08-08..2026-11-06, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-08 15:23:35 +01:00' --until='2026-11-06 15:23:35 +01:00' --full-history --no-merges -- src/Rask.Ui/UiDatePickerButton.cs`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Repeated repair: src/Rask.Core/Live/QuiescenceScope.cs src/Rask.Core/Live/QuiescenceScope.cs:223— src/Rask.Core/Live/QuiescenceScope.cs changed 9 times in last 90 days and 5 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 4 (its worst body is QuiescenceScope.TrySnapshotPending at line 223), UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “fix(wasm): follow WasmHostBuilder.Run through the templates and RASK021”; “fix(core): find a render's quiescence scope through the async flow only”; “fix(ssr): track the paint, not the hook, for quiescence”; “fix(ssr): hand the quiescence pass to the lifecycle sync context”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-08-08..2026-11-06, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-08 15:23:35 +01:00' --until='2026-11-06 15:23:35 +01:00' --full-history --no-merges -- src/Rask.Core/Live/QuiescenceScope.cs`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Repeated repair: src/Rask.Ui/UiDatetimePickerControl.cs src/Rask.Ui/UiDatetimePickerControl.cs:326— src/Rask.Ui/UiDatetimePickerControl.cs changed 8 times in last 90 days and 5 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 8 (its worst body is UiDatetimePickerControl.TimeRefusal at line 326), UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “fix(forms): a disabled control takes no event, and a picker says why it refused a typed limit”; “fix(ui): a disabled kit control writes nothing, and a calendar takes only a day it drew”; “fix(ui): an open date picker rests the focus on nothing, as Flux; parity-focus.mjs holds the look”; “fix(ui): a late pick, clear or step from an older page reaches its handler”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-08-08..2026-11-06, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-08 15:23:35 +01:00' --until='2026-11-06 15:23:35 +01:00' --full-history --no-merges -- src/Rask.Ui/UiDatetimePickerControl.cs`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Repeated repair: src/Rask.Core/Resources/rask-confirm.ts src/Rask.Core/Resources/rask-confirm.ts:44— src/Rask.Core/Resources/rask-confirm.ts changed 7 times in last 90 days and 5 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 10 (its worst body is rask-confirm.confirmed at line 44), UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “fix(server): a confirmed press waits until the server says every page it sent is on screen”; “fix(core): a confirmed press goes just after a page lands, the furthest from the next”; “fix(core): a yes in the browser's confirm() presses again once the held page caught up”; “fix(core): a confirm's yes presses the same button on a page that re-renders while asked”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-08-08..2026-11-06, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-08 15:23:35 +01:00' --until='2026-11-06 15:23:35 +01:00' --full-history --no-merges -- src/Rask.Core/Resources/rask-confirm.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.
Repeated repair: src/Rask.Data/AmbientTransaction.cs src/Rask.Data/AmbientTransaction.cs:183— src/Rask.Data/AmbientTransaction.cs changed 7 times in last 90 days and 4 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 6 (its worst body is AmbientTransaction.Joinable at line 183), UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “fix(data): refuse BeginTransaction, Migrate and EnsureCreated inside Db.Transaction, saying why”; “fix(data): work Rask starts inside a Db.Transaction reads outside it”; “fix(data): raw SQL on an app context inside Db.Transaction runs inside the transaction”; “fix(data): hand a db: context back on its own connection when Db.Transaction ends”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-08-08..2026-11-06, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-08 15:23:35 +01:00' --until='2026-11-06 15:23:35 +01:00' --full-history --no-merges -- src/Rask.Data/AmbientTransaction.cs`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Repeated repair: src/Rask.Core/Component.LiveRender.cs src/Rask.Core/Component.LiveRender.cs:109— src/Rask.Core/Component.LiveRender.cs changed 7 times in last 90 days and 4 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 7 (its worst body is Component.CanServeCachedRender at line 109), UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “fix(live): a render asked for past a dispatch's budget is made after it, never dropped”; “fix(core): a child that comes or goes no longer remounts the components after it”; “fix(core): an unkeyed child beside keyed ones keeps its instance, and a repeated key its own row”; “fix(core): keep a form children function's fields when the page renders around it”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-08-08..2026-11-06, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-08 15:23:35 +01:00' --until='2026-11-06 15:23:35 +01:00' --full-history --no-merges -- src/Rask.Core/Component.LiveRender.cs`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Repeated repair: src/Rask.Ui/UiDatePickerScope.cs src/Rask.Ui/UiDatePickerScope.cs:73— src/Rask.Ui/UiDatePickerScope.cs changed 6 times in last 90 days and 4 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 3 (its worst body is UiDatePickerScope.ClearInside at line 73), UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “fix(ui): a late pick, clear or step from an older page reaches its handler”; “fix(ui): draw a picker's clear control inside its trigger, as Flux does”; “fix(ui): keep every clear button inside its trigger, and give the date picker Flux's clearable”; “fix(ui): a typed date or time picker left half filled says so instead of saving what it held”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-08-08..2026-11-06, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-08 15:23:35 +01:00' --until='2026-11-06 15:23:35 +01:00' --full-history --no-merges -- src/Rask.Ui/UiDatePickerScope.cs`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Repeated repair: src/Rask.Cli/Commands/DeployCommand.Proxy.cs src/Rask.Cli/Commands/DeployCommand.Proxy.cs:133— src/Rask.Cli/Commands/DeployCommand.Proxy.cs changed 5 times in last 90 days and 4 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 10 (its worst body is DeployCommand.RewriteRoutesAsync at line 133), UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “fix(cli): a deploy lets the old container finish its jobs, up to the app's stopTimeout”; “fix(cli): one deploy of an app at a time, and never touch another app's proxy file”; “fix(cli): say a box moved to per-app proxy files only when another app was carried over”; “fix(cli): let verification catch a vanished new colour instead of a listing check”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-08-08..2026-11-06, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-08 15:23:35 +01:00' --until='2026-11-06 15:23:35 +01:00' --full-history --no-merges -- src/Rask.Cli/Commands/DeployCommand.Proxy.cs`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Repeated repair: src/Rask.Core/Forms/OfferedGuard.cs src/Rask.Core/Forms/OfferedGuard.cs:36— src/Rask.Core/Forms/OfferedGuard.cs changed 4 times in last 90 days and 4 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 4 (its worst body is OfferedGuard.ManyAsync at line 36), UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “fix(forms): a disabled control takes no event, and a picker says why it refused a typed limit”; “fix(ui): a disabled kit control writes nothing, and a calendar takes only a day it drew”; “fix(forms): a disabled bound control and a Ui.Tabs take only what the reader could send”; “fix(forms): a radio group, checkbox group, toggle and OnSelect take only what they offered”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-08-08..2026-11-06, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-08 15:23:35 +01:00' --until='2026-11-06 15:23:35 +01:00' --full-history --no-merges -- src/Rask.Core/Forms/OfferedGuard.cs`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Repeated repair: src/Rask.Ui/UiEditorMarkup.cs src/Rask.Ui/UiEditorMarkup.cs:44— src/Rask.Ui/UiEditorMarkup.cs changed 5 times in last 90 days and 3 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 4 (its worst body is UiEditorMarkup.Button at line 44), UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “fix(ui): the phone's country list and the editor's toolbar match Flux UI again (#1260)”; “fix(ui): an app's class wins over the editor's, file upload's, kanban's and main's defaults”; “fix(ui): chevrons and menu icons keep a tap's hover, a toolbar fills only under a pointer, as Flux”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-08-08..2026-11-06, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-08 15:23:35 +01:00' --until='2026-11-06 15:23:35 +01:00' --full-history --no-merges -- src/Rask.Ui/UiEditorMarkup.cs`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Repeated repair: src/Rask.Ui/UiDatetimePickerButton.cs src/Rask.Ui/UiDatetimePickerButton.cs:42— src/Rask.Ui/UiDatetimePickerButton.cs changed 5 times in last 90 days and 3 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 6 (its worst body is UiDatetimePickerButton.Render at line 42), UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “fix(ui): darken a date picker button's chevron under its pointer or tap, as Flux”; “fix(ui): join the datetime picker's date and time by CLDR in its locale, as Flux”; “fix(ui): draw a picker's clear control inside its trigger, as Flux does”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-08-08..2026-11-06, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-08 15:23:35 +01:00' --until='2026-11-06 15:23:35 +01:00' --full-history --no-merges -- src/Rask.Ui/UiDatetimePickerButton.cs`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Repeated repair: src/Rask.Core/Resources/rask-plot.ts src/Rask.Core/Resources/rask-plot.ts:102— src/Rask.Core/Resources/rask-plot.ts changed 5 times in last 90 days and 3 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 13 (its worst body is rask-plot.write at line 102), UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “fix(ui): a chart's tooltip takes the pointer as Flux's does”; “fix(core): a toast leaving by itself is not the reader's next action”; “fix(ui): a chart is measured again after its first drawing replaced the measured element”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-08-08..2026-11-06, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-08 15:23:35 +01:00' --until='2026-11-06 15:23:35 +01:00' --full-history --no-merges -- src/Rask.Core/Resources/rask-plot.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.
Repeated repair: src/Rask.Core/Live/LiveOptions.cs src/Rask.Core/Live/LiveOptions.cs:65— src/Rask.Core/Live/LiveOptions.cs changed 5 times in last 90 days and 3 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 1 (its worst body is LiveOptions.PathBase.get at line 65), UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “fix(core): each host decides whether it is in Development, not the first host in the process”; “fix(core)!: a production error page says nothing of the exception”; “fix(storage): run without Rask.Core on every lane; bind Rask:Storage”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-08-08..2026-11-06, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-08 15:23:35 +01:00' --until='2026-11-06 15:23:35 +01:00' --full-history --no-merges -- src/Rask.Core/Live/LiveOptions.cs`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Repeated repair: src/Rask.Core/Resources/rask-persist.ts src/Rask.Core/Resources/rask-persist.ts:38— src/Rask.Core/Resources/rask-persist.ts changed 5 times in last 90 days and 3 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 5 (its worst body is rask-persist.restore at line 38), UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “fix(core): a toast leaving by itself is not the reader's next action”; “fix(core): a persisted checkbox is the reader's from the first render, before the hooks arrive”; “fix(core): a drawer is put away by a press on a link to the page already open”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-08-08..2026-11-06, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-08 15:23:35 +01:00' --until='2026-11-06 15:23:35 +01:00' --full-history --no-merges -- src/Rask.Core/Resources/rask-persist.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.
Repeated repair: src/Rask.Wasm/WasmCultureSeeder.cs src/Rask.Wasm/WasmCultureSeeder.cs:132— src/Rask.Wasm/WasmCultureSeeder.cs changed 4 times in last 90 days and 3 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 8 (its worst body is WasmCultureSeeder.Negotiate at line 132), UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “fix(wasm): read the culture cookie and query key the app configured, not ASP.NET's defaults”; “fix(wasm): make host.UseCulture configure the app's languages, and bake them into the prerender”; “fix(wasm): an app with no configured culture formats in its page's language, not the browser's”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-08-08..2026-11-06, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-08 15:23:35 +01:00' --until='2026-11-06 15:23:35 +01:00' --full-history --no-merges -- src/Rask.Wasm/WasmCultureSeeder.cs`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Repeated repair: src/Rask.Core/Component.State.cs src/Rask.Core/Component.State.cs:15— src/Rask.Core/Component.State.cs changed 4 times in last 90 days and 3 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 1 (its worst body is Component.EnsureLiveStateInternal at line 15), UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “fix(core): a child that comes or goes no longer remounts the components after it”; “fix(core): an unkeyed child beside keyed ones keeps its instance, and a repeated key its own row”; “fix(core): keep a form children function's fields when the page renders around it”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-08-08..2026-11-06, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-08 15:23:35 +01:00' --until='2026-11-06 15:23:35 +01:00' --full-history --no-merges -- src/Rask.Core/Component.State.cs`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
+ 4 more in this group — see findings.md.
R4 · Test Coverage· No test reaches this file · ×26
No test reaches this file src/Rask.Server/Resources/rask.ts:1— No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
No test reaches this file src/Rask.Wasm/Resources/rask.wasm.ts:1— No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
No test reaches this file src/Rask.Ui/Resources/phone/ui-phone.ts:1— No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
No test reaches this file src/Rask.Ui/Resources/editor/ui-editor.ts:1— No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
No test reaches this file src/Rask.Core/Resources/rask-deverror.ts:1— No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
No test reaches this file src/Rask.Wasm/Browser/main.ts:1— No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
No test reaches this file src/Rask.Core/Resources/rask-hook-loader.ts:1— No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
No test reaches this file src/Rask.Wasm/Resources/rask-wasm-api.ts:1— No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
No test reaches this file src/Rask.Pdf/PrintTables.js:1— No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
No test reaches this file src/Rask.Core/Resources/rask-head-assets.ts:1— No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
No test reaches this file src/Rask.Core/Resources/rask-js-invoke.ts:1— No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
No test reaches this file src/Rask.Site/Shared/GuideChrome.ts:1— No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
No test reaches this file src/Rask.Wasm/Resources/rask-wasm-auth.ts:1— No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
No test reaches this file src/Rask.Core/Resources/rask-files.ts:1— No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
No test reaches this file REDACTED:1— No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
No test reaches this file src/Rask.Core/Resources/rask-scoped.ts:1— No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
No test reaches this file src/Rask.Core/Resources/rask-hotreload.ts:1— No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
No test reaches this file src/Rask.DevTools/Resources/rask-devtools-host.ts:1— No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
No test reaches this file src/Rask.Site/Shared/CodeSample.ts:1— No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
No test reaches this file src/Rask.Site/Features/PictureInPictureDemo.ts:1— No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
No test reaches this file src/Rask.Site/Features/AssetLoading/ScriptCallsDemo.ts:1— No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
No test reaches this file src/Rask.Ui/UiEditor.ts:1— No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
No test reaches this file src/Rask.Core/Resources/rask-visibility.ts:1— No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
No test reaches this file src/Rask.DevTools/Resources/rask-devtools-panel.ts:1— No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
No test reaches this file src/Rask.Site/Features/ElementRef/ElementRefDemo.ts:1— No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
Swallowed exception (empty catch) src/Rask.Cli/Dev/DevStatusServer.cs:176— An empty catch block silently discards the error — failures vanish with no log and no rethrow. On a teardown path letting it propagate is not an option (throwing out of `Dispose()` masks the failure already in flight and abandons the rest of the cleanup), so make the swallow deliberate instead: record it through whatever this codebase already uses to report problems — or, if one specific failure truly cannot matter, catch exactly that exception type and say why in a comment on the catch (a comment on a catch-all still swallows everything else).
Swallowed exception (empty catch) src/Rask.Cli/Dev/DevStatusServer.cs:182— An empty catch block silently discards the error — failures vanish with no log and no rethrow. On a teardown path letting it propagate is not an option (throwing out of `Dispose()` masks the failure already in flight and abandons the rest of the cleanup), so make the swallow deliberate instead: record it through whatever this codebase already uses to report problems — or, if one specific failure truly cannot matter, catch exactly that exception type and say why in a comment on the catch (a comment on a catch-all still swallows everything else).
Swallowed exception (empty catch) src/Rask.Cli/ProcessRunner.cs:116— An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Swallowed exception (empty catch) src/Rask.Core/HotReload/RaskHotReload.cs:172— 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/Rask.Data/DataChangesInterceptor.cs:214— 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/Rask.Data/DataChangesInterceptor.cs:273— 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/Rask.Data/DataChangesInterceptor.cs:309— 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/Rask.Query/QueryEntry.cs:245— 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/Rask.Server/Diagnostics/RaskServerDiagnostics.cs:84— 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/Rask.Server/Files/SessionDownloadStore.cs:101— 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/Rask.Server/Files/SessionUploadStore.cs:137— 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/Rask.Server/LiveSession.cs:861— 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/Rask.Server/LiveSessionStore.cs:582— 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/Rask.Server/LiveSessionStore.cs:616— 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/Rask.Server/RaskDrainService.cs:129— An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Swallowed exception (empty catch) REDACTED:2051— An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Swallowed exception (empty catch) REDACTED:2131— An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Swallowed exception (empty catch) REDACTED:2226— An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Swallowed exception (empty catch) REDACTED:2904— An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Swallowed exception (empty catch) REDACTED:2929— An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Swallowed exception (empty catch) REDACTED:3171— An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Swallowed exception (empty catch) REDACTED:3524— 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/Rask.Server/Transport/WebSocketTransport.cs:42— 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.
Sync-over-async blocking — 20 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/Rask.Cache/RaskDistributedCache.cs:36— `.GetAwaiter().GetResult()` blocks this thread until the async work completes — it wastes a thread-pool thread for as long as the work runs and can deadlock wherever a synchronization context is in play (a UI thread, or a caller that has one).
Sync-over-async blocking src/Rask.Cache/RaskDistributedCache.cs:111— `.GetAwaiter().GetResult()` blocks this thread until the async work completes — it wastes a thread-pool thread for as long as the work runs and can deadlock wherever a synchronization context is in play (a UI thread, or a caller that has one).
Sync-over-async blocking src/Rask.Cache/RaskDistributedCache.cs:119— `.GetAwaiter().GetResult()` blocks this thread until the async work completes — it wastes a thread-pool thread for as long as the work runs and can deadlock wherever a synchronization context is in play (a UI thread, or a caller that has one).
Sync-over-async blocking src/Rask.Cache/RaskDistributedCache.cs:134— `.GetAwaiter().GetResult()` blocks this thread until the async work completes — it wastes a thread-pool thread for as long as the work runs and can deadlock wherever a synchronization context is in play (a UI thread, or a caller that has one).
Sync-over-async blocking src/Rask.Core/Live/HandlerSyncContext.cs:66— `.GetAwaiter().GetResult()` blocks this thread until the async work completes — it wastes a thread-pool thread for as long as the work runs and can deadlock wherever a synchronization context is in play (a UI thread, or a caller that has one).
Sync-over-async blocking src/Rask.Data/AuditingInterceptor.cs:30— `.GetAwaiter().GetResult()` blocks this thread until the async work completes — it wastes a thread-pool thread for as long as the work runs and can deadlock wherever a synchronization context is in play (a UI thread, or a caller that has one).
Sync-over-async blocking src/Rask.Data/DeclaredRuleCheckInterceptor.cs:37— `.GetAwaiter().GetResult()` blocks this thread until the async work completes — it wastes a thread-pool thread for as long as the work runs and can deadlock wherever a synchronization context is in play (a UI thread, or a caller that has one).
Sync-over-async blocking src/Rask.Data/DeclaredRuleCheckInterceptor.cs:188— `.GetAwaiter().GetResult()` blocks this thread until the async work completes — it wastes a thread-pool thread for as long as the work runs and can deadlock wherever a synchronization context is in play (a UI thread, or a caller that has one).
Sync-over-async blocking src/Rask.Data/DomainEventInterceptor.cs:49— `.GetAwaiter().GetResult()` blocks this thread until the async work completes — it wastes a thread-pool thread for as long as the work runs and can deadlock wherever a synchronization context is in play (a UI thread, or a caller that has one).
Sync-over-async blocking src/Rask.Server/App/RaskApp.cs:337— `.GetAwaiter().GetResult()` blocks this thread until the async work completes — it wastes a thread-pool thread for as long as the work runs and can deadlock wherever a synchronization context is in play (a UI thread, or a caller that has one).
Sync-over-async blocking src/Rask.Storage/Backends/BlobRangeStream.cs:98— `.GetAwaiter().GetResult()` blocks this thread until the async work completes — it wastes a thread-pool thread for as long as the work runs and can deadlock wherever a synchronization context is in play (a UI thread, or a caller that has one).
Sync-over-async blocking src/Rask.Storage/Backends/DatabaseReadStream.cs:85— `.GetAwaiter().GetResult()` blocks this thread until the async work completes — it wastes a thread-pool thread for as long as the work runs and can deadlock wherever a synchronization context is in play (a UI thread, or a caller that has one).
Sync-over-async blocking src/Rask.Tailwind.Tasks/ResolveTailwindCliTask.cs:169— `.GetAwaiter().GetResult()` blocks this thread until the async work completes — it wastes a thread-pool thread for as long as the work runs and can deadlock wherever a synchronization context is in play (a UI thread, or a caller that has one).
Sync-over-async blocking src/Rask.Tailwind.Tasks/ResolveTailwindCliTask.cs:198— `.GetAwaiter().GetResult()` blocks this thread until the async work completes — it wastes a thread-pool thread for as long as the work runs and can deadlock wherever a synchronization context is in play (a UI thread, or a caller that has one).
Sync-over-async blocking src/Rask.Testing/Page.Visit.cs:136— `.GetAwaiter().GetResult()` blocks this thread until the async work completes — it wastes a thread-pool thread for as long as the work runs and can deadlock wherever a synchronization context is in play (a UI thread, or a caller that has one).
Sync-over-async blocking src/Rask.Testing/TestApp.cs:131— `.GetAwaiter().GetResult()` blocks this thread until the async work completes — it wastes a thread-pool thread for as long as the work runs and can deadlock wherever a synchronization context is in play (a UI thread, or a caller that has one).
Sync-over-async blocking src/Rask.TypeScript.Tasks/ResolveTypeScriptToolTask.cs:192— `.GetAwaiter().GetResult()` blocks this thread until the async work completes — it wastes a thread-pool thread for as long as the work runs and can deadlock wherever a synchronization context is in play (a UI thread, or a caller that has one).
Sync-over-async blocking src/Rask.TypeScript.Tasks/ResolveTypeScriptToolTask.cs:207— `.GetAwaiter().GetResult()` blocks this thread until the async work completes — it wastes a thread-pool thread for as long as the work runs and can deadlock wherever a synchronization context is in play (a UI thread, or a caller that has one).
Sync-over-async blocking src/Rask.TypeScript.Tasks/ResolveTypeScriptToolTask.cs:243— `.GetAwaiter().GetResult()` blocks this thread until the async work completes — it wastes a thread-pool thread for as long as the work runs and can deadlock wherever a synchronization context is in play (a UI thread, or a caller that has one).
Sync-over-async blocking src/Rask.TypeScript.Tasks/TransientRetry.cs:29— `.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).
Stateful singleton: ApiClientOptions src/Rask.Api.Client/ApiClientOptions.cs:6— `ApiClientOptions` is a singleton (one shared instance) but mutates instance state outside any lock (_timeout; e.g. `_timeout` at line 41).
Stateful singleton: AuthClientOptions src/Rask.Auth.Client/AuthClientOptions.cs:6— `AuthClientOptions` is a singleton (one shared instance) but mutates instance state outside any lock (_prefix; e.g. `_prefix` at line 27).
Stateful singleton: HttpUserProvider src/Rask.Auth.Client/HttpUserProvider.cs:25— `HttpUserProvider` is a singleton (one shared instance) but mutates instance state outside any lock (IsLoading, _loaded, _current; e.g. `IsLoading` at line 59).
Stateful singleton: EventScopeCatalog src/Rask.Core/Live/EventScopeCatalog.cs:15— `EventScopeCatalog` is a singleton (one shared instance) but mutates instance state outside any lock (_owned; e.g. `_owned` at line 69).
Stateful singleton: DashboardSecurityState src/Rask.Dashboard/DashboardSecurityState.cs:12— `DashboardSecurityState` is a singleton (one shared instance) but mutates instance state outside any lock (UsingFallbackPolicy, FallbackIsOpen; e.g. `UsingFallbackPolicy` at src/Rask.Dashboard/RaskDashboardServiceCollectionExtensions.cs line 127, through the shared instance).
Stateful singleton: DevToolsServerEndpoints src/Rask.DevTools/Endpoints/DevToolsServerEndpoints.cs:18— `DevToolsServerEndpoints` is a singleton (one shared instance) but mutates instance state outside any lock (PanelScriptUrl, _prefixUnderBase, _hostScriptUrl, _panelUrl, _allowRemote; e.g. `PanelScriptUrl` at line 107).
Stateful singleton: RouteState src/Rask.Core/Routing/RouteState.cs:19— `RouteState` is a singleton (one shared instance) but mutates instance state outside any lock (_path, _query, _forbidden, _split; e.g. `_path` at line 40).
Stateful singleton: Navigator src/Rask.Core/Routing/Navigator.cs:21— `Navigator` is a singleton (one shared instance) but mutates instance state outside any lock (_exit, _replace, _dirty, _redirected, _redirects, _inInitialRender; e.g. `_exit` at line 190).
Stateful singleton: BatteryTablesExtension src/Rask.Server/App/BatteryTablesExtension.cs:9— `BatteryTablesExtension` is a singleton (one shared instance) but mutates instance state outside any lock (_info; e.g. `_info` at line 15).
Stateful singleton: ServerPrintablePages src/Rask.Server/Printing/ServerPrintablePages.cs:24— `ServerPrintablePages` is a singleton (one shared instance) but mutates instance state outside any lock (_selector, _pathBase; e.g. `_selector` at line 33).
Stateful singleton: RaskDrainService src/Rask.Server/RaskDrainService.cs:24— `RaskDrainService` is a singleton (one shared instance) but mutates instance state outside any lock (_stoppingRegistration, _announce; e.g. `_stoppingRegistration` at line 59).
Stateful singleton: BrowserSqliteOptions src/Rask.SQLite.Browser/BrowserSqliteOptions.cs:4— `BrowserSqliteOptions` is a singleton (one shared instance) but mutates instance state outside any lock (DatabasePath; e.g. `DatabasePath` at line 77).
Stateful singleton: BrowserSqliteOwnership src/Rask.SQLite.Browser/BrowserSqliteOwnership.cs:24— `BrowserSqliteOwnership` is a singleton (one shared instance) but mutates instance state outside any lock (IsOwner; e.g. `IsOwner` at line 70).
Stateful singleton: SqliteSnapshotOptions src/Rask.SQLite.Snapshots/SqliteSnapshotOptions.cs:7— `SqliteSnapshotOptions` is a singleton (one shared instance) but mutates instance state outside any lock (DatabasePath; e.g. `DatabasePath` at src/Rask.SQLite.Snapshots/SqliteSnapshotsServiceCollectionExtensions.cs line 43, through the shared instance).
Stateful singleton: BrowserSqliteHost src/Rask.SQLite.Browser/BrowserSqliteHost.cs:36— `BrowserSqliteHost` is a singleton (one shared instance) but mutates instance state outside any lock (IsOwner, _takeoverWatch, _ownerHold; e.g. `IsOwner` at line 79).
Stateful singleton: RouteState src/Rask.Core/Routing/RouteState.cs:19— `RouteState` is a singleton (one shared instance) but mutates instance state outside any lock (_path, _query, _forbidden, _split, Languages; e.g. `_path` at line 40).
Stateful singleton: PersistentState src/Rask.Core/Live/PersistentState.cs:19— `PersistentState` is a singleton (one shared instance) but mutates instance state outside any lock (_bytes, _entries, Version, Overflowed; e.g. `_bytes` at line 119).
Stateful singleton: WasmDownloadSink src/Rask.Wasm/Files/WasmDownloadSink.cs:10— `WasmDownloadSink` is a singleton (one shared instance) but mutates instance state outside any lock (_order, _pending; e.g. `_order` at line 32).
Stateful singleton: WasmJSRuntime src/Rask.Wasm/JSInterop/WasmJSRuntime.cs:27— `WasmJSRuntime` is a singleton (one shared instance) but mutates instance state outside any lock (_host; e.g. `_host` at line 67).
Stateful singleton: WasmUserWatch src/Rask.Wasm/Authentication/WasmUserWatch.cs:29— `WasmUserWatch` is a singleton (one shared instance) but mutates instance state outside any lock (_asking, HasEnded; e.g. `_asking` at line 70).
AC6 · Visual & motion safety· Animation without a prefers-reduced-motion guard · ×17
Animation without a prefers-reduced-motion guard src/Rask.Site/wwwroot/index.html:59— `.rask-boot .rask-spin` moves (`animation: rask-spin 0.8s linear infinite`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce.
Animation without a prefers-reduced-motion guard src/Rask.Site/wwwroot/index.html:85— `.rask-boot__fill` moves (`transition: width 0.2s ease`) 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/Rask.Templates/wasm-hosted/Client/wwwroot/index.html:48— `.rask-boot .rask-spin` moves (`animation: rask-spin 0.8s linear infinite`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce.
Animation without a prefers-reduced-motion guard src/Rask.Templates/wasm/wwwroot/index.html:50— `.rask-boot .rask-spin` moves (`animation: rask-spin 0.8s linear infinite`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce.
Animation without a prefers-reduced-motion guard src/Rask.Wasm/Browser/index.html:105— `.rask-boot .rask-spin` moves (`animation: rask-spin 0.8s linear infinite`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce.
Animation without a prefers-reduced-motion guard src/Rask.Wasm/Browser/index.html:131— `.rask-boot__fill` moves (`transition: width 0.2s ease`) 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/Rask.Ui/Styles/ui.css:900— `[data-ui-toast] > [data-ui-toast-dialog]` moves (`transition: opacity 0.2s ease allow-discrete,
transform 0.2s ease allow-discrete,
height 0.2s ease allow-discrete`) 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/Rask.Ui/Styles/ui.css:904— `[data-ui-toast] > [data-ui-toast-dialog]` moves (`animation: ui-toast-fade 0.2s ease,
ui-toast-rise 0.35s ease`) 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/Rask.Ui/Styles/ui.css:910— `[data-ui-toast] > [data-ui-toast-dialog][data-rask-dismiss-after]` moves (`animation: ui-toast-fade 0.2s ease,
ui-toast-rise 0.35s ease,
ui-toast-leave 0.35s ease var(--ui-toast-duration) forwards`) 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/Rask.Ui/Styles/ui.css:920— `[data-ui-toast-group] > [data-ui-toast-dialog]` moves (`transition: opacity 0.35s ease allow-discrete,
transform 0.35s ease allow-discrete,
height 0.35s ease allow-discrete`) 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/Rask.Ui/Styles/ui.css:946— `[data-ui-toast-group] > [data-ui-toast-dialog] > :first-child` moves (`transition: opacity 0.35s ease allow-discrete,
transform 0.35s ease allow-discrete,
height 0.35s ease allow-discrete`) 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/Rask.Ui/Styles/ui.css:950— `[data-ui-toast-group] > [data-ui-toast-dialog] > :first-child` moves (`animation: ui-toast-fade 0.35s ease,
ui-toast-rise 0.35s ease`) 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/Rask.Ui/Styles/ui.css:956— `[data-ui-toast-group] > [data-ui-toast-dialog][data-rask-dismiss-after] > :first-child` moves (`animation: ui-toast-fade 0.35s ease,
ui-toast-rise 0.35s ease,
ui-toast-lift 0.35s ease var(--ui-toast-duration) forwards`) 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/Rask.Ui/Styles/ui.css:1162— `[data-ui-accordion][data-transition] > [data-ui-accordion-item]::details-content` moves (`transition: height 250ms cubic-bezier(0.4, 0, 0.2, 1),
content-visibility 250ms allow-discrete,
overflow 0s allow-discrete`) 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/Rask.Ui/Styles/ui.css:1170— `[data-ui-accordion][data-transition] > [data-ui-accordion-item][open]::details-content` moves (`transition: height 250ms cubic-bezier(0.4, 0, 0.2, 1),
content-visibility 250ms allow-discrete,
overflow 0s 250ms allow-discrete`) 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/Rask.Site/Shared/GuideChrome.css:208— `.guide-prevnext-link` moves (`transition: border-color .12s ease, box-shadow .12s ease, transform .12s ease`) 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/Rask.DevTools/Resources/host/flash.ts:112— `box.animate()` moves (`Web Animations API keyframes`) 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.
Sync-over-async (deadlock risk) src/Rask.Cache/RaskDistributedCache.cs:36— Blocking on a Task with `.Wait()`/`.GetAwaiter().GetResult()` can deadlock (and wastes a thread). Prefer awaiting it: make the caller `async` and `await` instead. Where a synchronous entry point must stay — a public sync API you cannot break, or a process entry point that must not return until the work finishes — the block belongs in ONE documented bridge and never inside code that is already async; and where it already is that bridge, give the wait a TIMEOUT so a hung task fails the call instead of hanging the process.
Sync-over-async (deadlock risk) src/Rask.Cache/RaskDistributedCache.cs:111— Blocking on a Task with `.Wait()`/`.GetAwaiter().GetResult()` can deadlock (and wastes a thread). Prefer awaiting it: make the caller `async` and `await` instead. Where a synchronous entry point must stay — a public sync API you cannot break, or a process entry point that must not return until the work finishes — the block belongs in ONE documented bridge and never inside code that is already async; and where it already is that bridge, give the wait a TIMEOUT so a hung task fails the call instead of hanging the process.
Sync-over-async (deadlock risk) src/Rask.Cache/RaskDistributedCache.cs:119— Blocking on a Task with `.Wait()`/`.GetAwaiter().GetResult()` can deadlock (and wastes a thread). Prefer awaiting it: make the caller `async` and `await` instead. Where a synchronous entry point must stay — a public sync API you cannot break, or a process entry point that must not return until the work finishes — the block belongs in ONE documented bridge and never inside code that is already async; and where it already is that bridge, give the wait a TIMEOUT so a hung task fails the call instead of hanging the process.
Sync-over-async (deadlock risk) src/Rask.Cache/RaskDistributedCache.cs:134— Blocking on a Task with `.Wait()`/`.GetAwaiter().GetResult()` can deadlock (and wastes a thread). Prefer awaiting it: make the caller `async` and `await` instead. Where a synchronous entry point must stay — a public sync API you cannot break, or a process entry point that must not return until the work finishes — the block belongs in ONE documented bridge and never inside code that is already async; and where it already is that bridge, give the wait a TIMEOUT so a hung task fails the call instead of hanging the process.
Sync-over-async (deadlock risk) src/Rask.Core/Live/HandlerSyncContext.cs:66— Blocking on a Task with `.Wait()`/`.GetAwaiter().GetResult()` can deadlock (and wastes a thread). Prefer awaiting it: make the caller `async` and `await` instead. Where a synchronous entry point must stay — a public sync API you cannot break, or a process entry point that must not return until the work finishes — the block belongs in ONE documented bridge and never inside code that is already async; and where it already is that bridge, give the wait a TIMEOUT so a hung task fails the call instead of hanging the process.
Sync-over-async (deadlock risk) src/Rask.Data/AuditingInterceptor.cs:30— Blocking on a Task with `.Wait()`/`.GetAwaiter().GetResult()` can deadlock (and wastes a thread). Prefer awaiting it: make the caller `async` and `await` instead. Where a synchronous entry point must stay — a public sync API you cannot break, or a process entry point that must not return until the work finishes — the block belongs in ONE documented bridge and never inside code that is already async; and where it already is that bridge, give the wait a TIMEOUT so a hung task fails the call instead of hanging the process.
Sync-over-async (deadlock risk) src/Rask.Data/DeclaredRuleCheckInterceptor.cs:37— Blocking on a Task with `.Wait()`/`.GetAwaiter().GetResult()` can deadlock (and wastes a thread). Prefer awaiting it: make the caller `async` and `await` instead. Where a synchronous entry point must stay — a public sync API you cannot break, or a process entry point that must not return until the work finishes — the block belongs in ONE documented bridge and never inside code that is already async; and where it already is that bridge, give the wait a TIMEOUT so a hung task fails the call instead of hanging the process.
Sync-over-async (deadlock risk) src/Rask.Data/DeclaredRuleCheckInterceptor.cs:188— Blocking on a Task with `.Wait()`/`.GetAwaiter().GetResult()` wastes a thread and, if the task needs a context this one is holding, deadlocks. `Dispose()` returns void by contract, so it cannot simply `await`: signal the work to stop first (cancel its token, set its stop flag) so the wait is short, give the wait a TIMEOUT so a hung task cannot hang shutdown, and — where callers can use it — add an awaitable teardown (`DisposeAsync`/`StopAsync`) beside the synchronous one and let `Dispose()` remain the bounded fallback.
Sync-over-async (deadlock risk) src/Rask.Data/DomainEventInterceptor.cs:49— Blocking on a Task with `.Wait()`/`.GetAwaiter().GetResult()` can deadlock (and wastes a thread). Prefer awaiting it: make the caller `async` and `await` instead. Where a synchronous entry point must stay — a public sync API you cannot break, or a process entry point that must not return until the work finishes — the block belongs in ONE documented bridge and never inside code that is already async; and where it already is that bridge, give the wait a TIMEOUT so a hung task fails the call instead of hanging the process.
Sync-over-async (deadlock risk) src/Rask.Server/App/RaskApp.cs:337— Blocking on a Task with `.Wait()`/`.GetAwaiter().GetResult()` can deadlock (and wastes a thread). Prefer awaiting it: make the caller `async` and `await` instead. Where a synchronous entry point must stay — a public sync API you cannot break, or a process entry point that must not return until the work finishes — the block belongs in ONE documented bridge and never inside code that is already async; and where it already is that bridge, give the wait a TIMEOUT so a hung task fails the call instead of hanging the process.
Sync-over-async (deadlock risk) src/Rask.Storage/Backends/BlobRangeStream.cs:98— Blocking on a Task with `.Wait()`/`.GetAwaiter().GetResult()` can deadlock (and wastes a thread). Prefer awaiting it: make the caller `async` and `await` instead. Where a synchronous entry point must stay — a public sync API you cannot break, or a process entry point that must not return until the work finishes — the block belongs in ONE documented bridge and never inside code that is already async; and where it already is that bridge, give the wait a TIMEOUT so a hung task fails the call instead of hanging the process.
Sync-over-async (deadlock risk) src/Rask.Storage/Backends/DatabaseReadStream.cs:85— Blocking on a Task with `.Wait()`/`.GetAwaiter().GetResult()` can deadlock (and wastes a thread). Prefer awaiting it: make the caller `async` and `await` instead. Where a synchronous entry point must stay — a public sync API you cannot break, or a process entry point that must not return until the work finishes — the block belongs in ONE documented bridge and never inside code that is already async; and where it already is that bridge, give the wait a TIMEOUT so a hung task fails the call instead of hanging the process.
Sync-over-async (deadlock risk) src/Rask.Tailwind.Tasks/ResolveTailwindCliTask.cs:168— Blocking on a Task with `.Wait()`/`.GetAwaiter().GetResult()` can deadlock (and wastes a thread). Prefer awaiting it: make the caller `async` and `await` instead. Where a synchronous entry point must stay — a public sync API you cannot break, or a process entry point that must not return until the work finishes — the block belongs in ONE documented bridge and never inside code that is already async; and where it already is that bridge, give the wait a TIMEOUT so a hung task fails the call instead of hanging the process.
Sync-over-async (deadlock risk) src/Rask.Tailwind.Tasks/ResolveTailwindCliTask.cs:198— Blocking on a Task with `.Wait()`/`.GetAwaiter().GetResult()` can deadlock (and wastes a thread). Prefer awaiting it: make the caller `async` and `await` instead. Where a synchronous entry point must stay — a public sync API you cannot break, or a process entry point that must not return until the work finishes — the block belongs in ONE documented bridge and never inside code that is already async; and where it already is that bridge, give the wait a TIMEOUT so a hung task fails the call instead of hanging the process.
Sync-over-async (deadlock risk) src/Rask.TypeScript.Tasks/ResolveTypeScriptToolTask.cs:192— Blocking on a Task with `.Wait()`/`.GetAwaiter().GetResult()` can deadlock (and wastes a thread). Prefer awaiting it: make the caller `async` and `await` instead. Where a synchronous entry point must stay — a public sync API you cannot break, or a process entry point that must not return until the work finishes — the block belongs in ONE documented bridge and never inside code that is already async; and where it already is that bridge, give the wait a TIMEOUT so a hung task fails the call instead of hanging the process.
Sync-over-async (deadlock risk) src/Rask.TypeScript.Tasks/ResolveTypeScriptToolTask.cs:207— Blocking on a Task with `.Wait()`/`.GetAwaiter().GetResult()` can deadlock (and wastes a thread). Prefer awaiting it: make the caller `async` and `await` instead. Where a synchronous entry point must stay — a public sync API you cannot break, or a process entry point that must not return until the work finishes — the block belongs in ONE documented bridge and never inside code that is already async; and where it already is that bridge, give the wait a TIMEOUT so a hung task fails the call instead of hanging the process.
Sync-over-async (deadlock risk) src/Rask.TypeScript.Tasks/ResolveTypeScriptToolTask.cs:243— 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.
Swallowed exception (caught, then discarded) src/Rask.Batteries.Shared/HousekeepingContextFactory.cs:84— `catch (Exception)` does nothing with the exception it caught — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch. Log it through whatever this codebase already uses to report problems, or let it propagate; if one specific failure genuinely cannot matter, catch exactly that exception type and say why in a comment on the catch.
Swallowed exception (caught, then discarded) src/Rask.Cli/Commands/DbCommand.Backup.cs:401— `catch (SqliteException)` does nothing with the exception it caught — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch. Log it through whatever this codebase already uses to report problems, or let it propagate; if one specific failure genuinely cannot matter, catch exactly that exception type and say why in a comment on the catch.
Swallowed exception (caught, then discarded) src/Rask.Cli/Dev/DevStatusServer.cs:127— `catch (Exception) when (…)` does nothing with the exception it caught — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch. Log it through whatever this codebase already uses to report problems, or let it propagate; if one specific failure genuinely cannot matter, catch exactly that exception type and say why in a comment on the catch.
Swallowed exception (caught, then discarded) src/Rask.Cli/Dev/DevStatusServer.cs:131— `catch (HttpListenerException)` does nothing with the exception it caught — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch. Log it through whatever this codebase already uses to report problems, or let it propagate; if one specific failure genuinely cannot matter, catch exactly that exception type and say why in a comment on the catch.
Swallowed exception (caught, then discarded) src/Rask.Cli/Dev/LinuxDevHostPlatform.cs:237— `catch (IOException)` does nothing with the exception it caught — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch. Log it through whatever this codebase already uses to report problems, or let it propagate; if one specific failure genuinely cannot matter, catch exactly that exception type and say why in a comment on the catch.
Swallowed exception (caught, then discarded) src/Rask.Cli/Dev/LinuxDevHostPlatform.cs:241— `catch (UnauthorizedAccessException)` does nothing with the exception it caught — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch. Log it through whatever this codebase already uses to report problems, or let it propagate; if one specific failure genuinely cannot matter, catch exactly that exception type and say why in a comment on the catch.
Swallowed exception (caught, then discarded) src/Rask.Cli/Dev/LinuxDevHostPlatform.cs:299— `catch (IOException)` does nothing with the exception it caught — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch. Log it through whatever this codebase already uses to report problems, or let it propagate; if one specific failure genuinely cannot matter, catch exactly that exception type and say why in a comment on the catch.
Swallowed exception (caught, then discarded) src/Rask.Cli/Dev/LinuxDevHostPlatform.cs:303— `catch (UnauthorizedAccessException)` does nothing with the exception it caught — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch. Log it through whatever this codebase already uses to report problems, or let it propagate; if one specific failure genuinely cannot matter, catch exactly that exception type and say why in a comment on the catch.
Swallowed exception (caught, then discarded) src/Rask.Cli/DockerProbe.cs:64— `catch (Win32Exception)` does nothing with the exception it caught — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch. Log it through whatever this codebase already uses to report problems, or let it propagate; if one specific failure genuinely cannot matter, catch exactly that exception type and say why in a comment on the catch.
Swallowed exception (caught, then discarded) src/Rask.Core/Components/Authorize.cs:219— `catch` does nothing with the exception it caught — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch. Log it through whatever this codebase already uses to report problems, or let it propagate; if one specific failure genuinely cannot matter, catch exactly that exception type and say why in a comment on the catch.
Swallowed exception (caught, then discarded) src/Rask.Core/Forms/ModelGraphWalker.cs:162— `catch` does nothing with the exception it caught — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch. Log it through whatever this codebase already uses to report problems, or let it propagate; if one specific failure genuinely cannot matter, catch exactly that exception type and say why in a comment on the catch.
Swallowed exception (caught, then discarded) src/Rask.Core/Live/QuiescenceScope.cs:197— `ContinueWith` with a continuation that does nothing discards the antecedent's failure — the task it returns completes successfully whether or not the work faulted, so the failure vanishes with no log and no rethrow. Await the task and handle the exception, or report the fault from the continuation (`t.Exception`).
Swallowed exception (caught, then discarded) src/Rask.Cqrs.Server/EventStream.cs:138— `catch (JsonException)` does nothing with the exception it caught — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch. Log it through whatever this codebase already uses to report problems, or let it propagate; if one specific failure genuinely cannot matter, catch exactly that exception type and say why in a comment on the catch.
Swallowed exception (caught, then discarded) src/Rask.DevTools/Panel/DevToolsPanelSession.cs:94— `catch (JsonException)` does nothing with the exception it caught — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch. Log it through whatever this codebase already uses to report problems, or let it propagate; if one specific failure genuinely cannot matter, catch exactly that exception type and say why in a comment on the catch.
Swallowed exception (caught, then discarded) src/Rask.Query/SessionQueryClient.cs:484— `catch (Exception)` does nothing with the exception it caught — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch. Log it through whatever this codebase already uses to report problems, or let it propagate; if one specific failure genuinely cannot matter, catch exactly that exception type and say why in a comment on the catch.
Swallowed exception (caught, then discarded) src/Rask.Site/Features/Browser/BatteryDemo.cs:31— `catch (Exception)` does nothing with the exception it caught — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch. Log it through whatever this codebase already uses to report problems, or let it propagate; if one specific failure genuinely cannot matter, catch exactly that exception type and say why in a comment on the catch.
Swallowed exception (caught, then discarded) src/Rask.Site/Features/Browser/FileSystemAccessDemo.cs:62— `catch (JSException) when (…)` does nothing with the exception it caught — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch. Log it through whatever this codebase already uses to report problems, or let it propagate; if one specific failure genuinely cannot matter, catch exactly that exception type and say why in a comment on the catch.
Cross-slice coupling: Elements → Events src/Rask.Site/Features/Elements/ElementsFormsDemo.cs:11— `ElementsFormsDemo` (slice 'Elements') depends on `ElementsFormsDemo.Fields` from slice 'Events'.
Cross-slice coupling: Events → Elements src/Rask.Site/Features/Events/EventsFormDemo.cs:10— `EventsFormDemo` (slice 'Events') depends on `EventsFormDemo.Fields` from slice 'Elements'.
Cross-slice coupling: Guides → UiDocs src/Rask.Site/Features/Guides/LlmsText.cs:105— `LlmsText` (slice 'Guides') depends on `UiDocsCatalog` from slice 'UiDocs'.
Cross-slice coupling: Home → Guides src/Rask.Site/Features/Home/HomePage.cs:324— `HomePage` (slice 'Home') depends on `GuideCatalog` from slice 'Guides'.
Cross-slice coupling: NestedForms → Orders src/Rask.Site/Features/NestedForms/CartModel.cs:5— `CartModel` (slice 'NestedForms') depends on `LineItem` from slice 'Orders'.
Cross-slice coupling: NestedForms → Orders src/Rask.Site/Features/NestedForms/NestedListForeachDemo.cs:11— `NestedListForeachDemo` (slice 'NestedForms') depends on `LineItem` from slice 'Orders'.
Cross-slice coupling: Orders → NestedForms src/Rask.Site/Features/Orders/MasterDetailDemo.cs:180— `MasterDetailDemo` (slice 'Orders') depends on `MasterDetailDemo.LineItem` from slice 'NestedForms'.
Cross-slice coupling: Tags → Elements src/Rask.Site/Features/Tags/TagsFormDemo.cs:6— `TagsFormDemo` (slice 'Tags') depends on `TagsFormDemo.Fields` from slice 'Elements'.
Cross-slice coupling: UiKit → UiDocs src/Rask.Site/Features/UiKit/UiKitActionsPage.cs:20— `UiKitActionsPage` (slice 'UiKit') depends on `UiDocsCatalog` from slice 'UiDocs'.
Cross-slice coupling: UiKit → UiDocs src/Rask.Site/Features/UiKit/UiKitDataDisplayPage.cs:22— `UiKitDataDisplayPage` (slice 'UiKit') depends on `UiDocsCatalog` from slice 'UiDocs'.
Cross-slice coupling: UiKit → UiDocs src/Rask.Site/Features/UiKit/UiKitDataGridPage.cs:19— `UiKitDataGridPage` (slice 'UiKit') depends on `UiDocsCatalog` from slice 'UiDocs'.
Cross-slice coupling: UiKit → UiDocs src/Rask.Site/Features/UiKit/UiKitDataInputPage.cs:20— `UiKitDataInputPage` (slice 'UiKit') depends on `UiDocsCatalog` from slice 'UiDocs'.
Cross-slice coupling: UiKit → UiDocs src/Rask.Site/Features/UiKit/UiKitFeedbackPage.cs:20— `UiKitFeedbackPage` (slice 'UiKit') depends on `UiDocsCatalog` from slice 'UiDocs'.
Cross-slice coupling: UiKit → UiDocs src/Rask.Site/Features/UiKit/UiKitLayoutPage.cs:20— `UiKitLayoutPage` (slice 'UiKit') depends on `UiDocsCatalog` from slice 'UiDocs'.
Cross-slice coupling: UiKit → UiDocs src/Rask.Site/Features/UiKit/UiKitMovedPages.cs:12— `UiKitMovedPages` (slice 'UiKit') depends on `UiDocsEntry` from slice 'UiDocs'.
Cross-slice coupling: UiKit → UiDocs src/Rask.Site/Features/UiKit/UiKitNavigationPage.cs:20— `UiKitNavigationPage` (slice 'UiKit') depends on `UiDocsCatalog` from slice 'UiDocs'.
FileTooLong: REDACTED REDACTED— FileTooLong — 2156 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 1656 over it, 4.31× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: Resources/rask.ts src/Rask.Server/Resources/rask.ts— FileTooLong — 1227 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 727 over it, 2.45× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: Resources/rask-calendar.ts src/Rask.Core/Resources/rask-calendar.ts— FileTooLong — 829 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 329 over it, 1.66× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: Translations/TranslationCatalogGenerator.cs src/Rask.Generators/Translations/TranslationCatalogGenerator.cs— FileTooLong — 771 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 271 over it, 1.54× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: REDACTED REDACTED— FileTooLong — 738 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 238 over it, 1.48× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: mdn/refresh.py scripts/mdn/refresh.py— FileTooLong — 629 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 129 over it, 1.26× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: UiDocs/UiApi.cs src/Rask.Site/Features/UiDocs/UiApi.cs— FileTooLong — 619 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 119 over it, 1.24× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: Rask.Server/LiveSession.cs src/Rask.Server/LiveSession.cs— FileTooLong — 602 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 102 over it, 1.20× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: Live/FrameDiffer.cs src/Rask.Core/Live/FrameDiffer.cs— FileTooLong — 599 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 99 over it, 1.20× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: Resources/rask-list.ts src/Rask.Core/Resources/rask-list.ts— FileTooLong — 578 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 78 over it, 1.16× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: Live/LivePayload.cs src/Rask.Core/Live/LivePayload.cs— FileTooLong — 555 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 55 over it, 1.11× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: Rask.Batteries.Generators/ModelRegistryGenerator.cs src/Rask.Batteries.Generators/ModelRegistryGenerator.cs— FileTooLong — 533 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 33 over it, 1.07× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: Commands/ParityMenu.cs scripts/flux/Flux/Commands/ParityMenu.cs— FileTooLong — 520 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 20 over it, 1.04× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: Rask.Batteries.Generators/CqrsDispatchGenerator.cs src/Rask.Batteries.Generators/CqrsDispatchGenerator.cs— FileTooLong — 510 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 10 over it, 1.02× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: Commands/ParityTooltip.cs scripts/flux/Flux/Commands/ParityTooltip.cs— FileTooLong — 502 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 2 over it, 1.00× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
Fake-async — async method never awaits src/Rask.Site/Features/Components/SkipFactoryCounter.cs:12— `OnMount` is declared `async` but never awaits anything, so it runs synchronously while pretending to be asynchronous. Drop `async` or do the real async work.
Fake-async — async method never awaits src/Rask.Site/Features/Todos/TodosPage.cs:51— `OnUpdated` is declared `async` but never awaits anything, so it runs synchronously while pretending to be asynchronous. Drop `async` or do the real async work.
Fake-async — async method never awaits src/Rask.Site/Features/UiKit/UiKitActionsPage.cs:23— `OnFirstRender` is declared `async` but never awaits anything, so it runs synchronously while pretending to be asynchronous. Drop `async` or do the real async work.
Fake-async — async method never awaits src/Rask.Site/Features/UiKit/UiKitDataDisplayPage.cs:25— `OnFirstRender` is declared `async` but never awaits anything, so it runs synchronously while pretending to be asynchronous. Drop `async` or do the real async work.
Fake-async — async method never awaits src/Rask.Site/Features/UiKit/UiKitDataGridPage.cs:22— `OnFirstRender` is declared `async` but never awaits anything, so it runs synchronously while pretending to be asynchronous. Drop `async` or do the real async work.
Fake-async — async method never awaits src/Rask.Site/Features/UiKit/UiKitDataInputPage.cs:23— `OnFirstRender` is declared `async` but never awaits anything, so it runs synchronously while pretending to be asynchronous. Drop `async` or do the real async work.
Fake-async — async method never awaits src/Rask.Site/Features/UiKit/UiKitFeedbackPage.cs:23— `OnFirstRender` is declared `async` but never awaits anything, so it runs synchronously while pretending to be asynchronous. Drop `async` or do the real async work.
Fake-async — async method never awaits src/Rask.Site/Features/UiKit/UiKitLayoutPage.cs:23— `OnFirstRender` is declared `async` but never awaits anything, so it runs synchronously while pretending to be asynchronous. Drop `async` or do the real async work.
Fake-async — async method never awaits src/Rask.Site/Features/UiKit/UiKitNavigationPage.cs:23— `OnFirstRender` is declared `async` but never awaits anything, so it runs synchronously while pretending to be asynchronous. Drop `async` or do the real async work.
Fake-async — async method never awaits src/Rask.Site/Features/Users/UserGateDemo.cs:12— `OnMount` is declared `async` but never awaits anything, so it runs synchronously while pretending to be asynchronous. Drop `async` or do the real async work.
Fake-async — async method never awaits src/Rask.Site/Features/Users/UserGateDemo.cs:14— `OnUnmount` is declared `async` but never awaits anything, so it runs synchronously while pretending to be asynchronous. Drop `async` or do the real async work.
Fake-async — async method never awaits src/Rask.Site/Shared/PathDisplay.cs:15— `OnMount` is declared `async` but never awaits anything, so it runs synchronously while pretending to be asynchronous. Drop `async` or do the real async work.
Fake-async — async method never awaits src/Rask.Site/Shared/PathDisplay.cs:17— `OnUnmount` is declared `async` but never awaits anything, so it runs synchronously while pretending to be asynchronous. Drop `async` or do the real async work.
Fake-async — async method never awaits src/Rask.Site/Shared/ShowcaseLayout.cs:45— `OnMount` is declared `async` but never awaits anything, so it runs synchronously while pretending to be asynchronous. Drop `async` or do the real async work.
Fake-async — async method never awaits src/Rask.Site/Shared/ShowcaseLayout.cs:52— `OnUnmount` is declared `async` but never awaits anything, so it runs synchronously while pretending to be asynchronous. Drop `async` or do the real async work.
AX2 · Stateful singletons· Process-global static state · ×14
Process-global static state: AccountName src/Rask.Auth.Api/AccountName.cs:17— `AccountName` 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 (_last; e.g. `_last` at line 104). Concurrent callers lose updates, and a collection that is not built for concurrent writers can corrupt.
Process-global static state: AuthUser src/Rask.Auth.Api/AuthUser.cs:25— `AuthUser` 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 (Binding; e.g. `Binding` at line 47). Concurrent callers lose updates, and a collection that is not built for concurrent writers can corrupt.
Process-global static state: RaskCulture src/Rask.Core/Globalization/RaskCulture.cs:25— `RaskCulture` 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 (IsEnabled; e.g. `IsEnabled` at line 164). Concurrent callers lose updates, and a collection that is not built for concurrent writers can corrupt.
Process-global static state: RaskStrings src/Rask.Core/Globalization/RaskStrings.cs:27— `RaskStrings` 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 (Source, _libraries; e.g. `Source` at line 47). Concurrent callers lose updates, and a collection that is not built for concurrent writers can corrupt.
Process-global static state: FrameSinkScope src/Rask.Core/Live/FrameSinkScope.cs:12— `FrameSinkScope` 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 (Current; e.g. `Current` at line 19). Concurrent callers lose updates, and a collection that is not built for concurrent writers can corrupt.
Process-global static state: LiveOptions src/Rask.Core/Live/LiveOptions.cs:14— `LiveOptions` 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 (_pathBase; e.g. `_pathBase` at line 68). Concurrent callers lose updates, and a collection that is not built for concurrent writers can corrupt.
Process-global static state: ScopedScript src/Rask.Core/ScopedAssets/ScopedScript.cs:24— `ScopedScript` 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 (Options; e.g. `Options` at line 208). Concurrent callers lose updates, and a collection that is not built for concurrent writers can corrupt.
Process-global static state: Dispatcher src/Rask.Cqrs/Dispatcher.cs:23— `Dispatcher` 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 (_root; e.g. `_root` at line 56). Concurrent callers lose updates, and a collection that is not built for concurrent writers can corrupt.
Process-global static state: CurrentRows src/Rask.Data/CurrentRows.cs:23— `CurrentRows` 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 (_tenant, _user; e.g. `_tenant` at line 56). Concurrent callers lose updates, and a collection that is not built for concurrent writers can corrupt.
Process-global static state: Db src/Rask.Data/Db.cs:41— `Db` 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 (_factory; e.g. `_factory` at line 84). Concurrent callers lose updates, and a collection that is not built for concurrent writers can corrupt.
Process-global static state: ModelRegistry src/Rask.Data/ModelRegistry.cs:27— `ModelRegistry` 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 (_appModel; e.g. `_appModel` at line 90). Concurrent callers lose updates, and a collection that is not built for concurrent writers can corrupt.
Process-global static state: ReadDb src/Rask.Data/ReadDb.cs:23— `ReadDb` 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 (_factory; e.g. `_factory` at line 52). Concurrent callers lose updates, and a collection that is not built for concurrent writers can corrupt.
Process-global static state: DevToolsProbe src/Rask.DevTools/Probe/DevToolsProbe.cs:34— `DevToolsProbe` 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 (t_walkBuffer, t_walk, t_rendersBuffer, t_renders, t_walkStart, t_providesBuffer; e.g. `t_walkBuffer` at line 109). Concurrent callers lose updates, and a collection that is not built for concurrent writers can corrupt.
Process-global static state: JSInterop src/Rask.Wasm/JSInterop.cs:18— `JSInterop` 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 (_session, _hostedServices, _runtime, ModuleImportOrder, _seq, HotReloadAppliedCount; e.g. `_session` at line 34). Concurrent callers lose updates, and a collection that is not built for concurrent writers can corrupt.
No assertions: The_name_set_with_WithName_decides_the_client_method_name tests/Rask.Api.Client.Tests/MinimalApiRoundTripTests.cs:89— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: Subscribing_and_unsubscribing_Changed_does_not_throw tests/Rask.Core.Tests/Authentication/AnonymousUserProviderTests.cs:16— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: Notifying_and_validating_with_a_null_context_is_a_no_op tests/Rask.Core.Tests/Forms/PublicBindingApiTests.cs:105— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: Draining_with_no_pending_posts_completes_immediately tests/Rask.Core.Tests/Live/HandlerSyncContextTests.cs:8— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: Rerendering_all_with_no_sessions_gives_a_completed_task tests/Rask.Core.Tests/Live/LiveSessionStoreTests.cs:200— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: StateHasChanged_without_a_handle_does_not_throw tests/Rask.Core.Tests/Live/StateHasChangedTests.cs:11— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: StateHasChangedAsync_without_a_handle_gives_a_completed_task tests/Rask.Core.Tests/Live/StateHasChangedTests.cs:18— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: A_failed_prefetch_does_not_throw tests/Rask.Query.Tests/PlaceholderDataTests.cs:124— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: The_constructor_assigns_the_render_handle_so_StateHasChangedAsync_routes_to_the_session tests/Rask.Server.Tests/Live/LiveSessionDirectTests.cs:80— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: Optimize_on_a_closed_connection_is_a_no_op tests/Rask.SQLite.Tests/SqliteHardeningIntegrationTests.cs:47— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: A_fired_sync_with_no_subscribers_is_harmless tests/Rask.Wasm.Tests/Browser/BackgroundSyncTests.cs:181— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: A_list_reached_by_Go_from_a_handler_shows_both_of_its_reads tests/Rask.Wasm.Tests/Session/ArrivalAfterHandlerTests.cs:13— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: A_list_reached_by_a_link_shows_both_of_its_reads tests/Rask.Wasm.Tests/Session/ArrivalAfterHandlerTests.cs:28— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
Duplicated block (8 lines × 2) src/Rask.Batteries.Generators/ModelInputGenerator.Rules.cs:404— src/Rask.Batteries.Generators/ModelInputGenerator.Rules.cs:404-411 | src/Rask.Batteries.Generators/ModelInputGenerator.Rules.cs:418-425 — 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/Rask.Batteries.Generators/ModelInputGenerator.Rules.cs:404` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (8 lines × 2) src/Rask.Generators/ComponentScopedCssGenerator.cs:155— src/Rask.Generators/ComponentScopedCssGenerator.cs:155-162 | src/Rask.Generators/ComponentScopedJsGenerator.cs:208-215 — before extracting anything, compare `src/Rask.Generators/ComponentScopedCssGenerator.cs` and `src/Rask.Generators/ComponentScopedJsGenerator.cs` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 86 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/Rask.Generators/ComponentScopedCssGenerator.cs:155` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (8 lines × 2) src/Rask.Query/QueryClient.cs:59— src/Rask.Query/QueryClient.cs:59-66 | src/Rask.Query/QueryClient.cs:159-166 — 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/Rask.Query/QueryClient.cs:59` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (8 lines × 2) src/Rask.Batteries.Generators/CompositeKeyGenerator.cs:46— src/Rask.Batteries.Generators/CompositeKeyGenerator.cs:46-53 | src/Rask.Batteries.Generators/ReadModelGenerator.cs:133-140 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `src/Rask.Batteries.Generators/CompositeKeyGenerator.cs:46` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (8 lines × 2) src/Rask.Site/Features/Virtualize/VirtualizeItemsDemo.cs:52— src/Rask.Site/Features/Virtualize/VirtualizeItemsDemo.cs:52-59 | src/Rask.Site/Features/Virtualize/VirtualizeProviderDemo.cs:58-65 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `src/Rask.Site/Features/Virtualize/VirtualizeItemsDemo.cs:52` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (8 lines × 2) scripts/flux/Flux/Commands/ParityMenu.cs:502— scripts/flux/Flux/Commands/ParityMenu.cs:502-509 | scripts/flux/Flux/Commands/ParityTooltip.cs:263-270 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `scripts/flux/Flux/Commands/ParityMenu.cs:502` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (8 lines × 2) src/Rask.Batteries.Generators/ModelInputGenerator.ModelClass.cs:515— src/Rask.Batteries.Generators/ModelInputGenerator.ModelClass.cs:515-522 | src/Rask.Batteries.Generators/ModelInputGenerator.ModelClass.cs:526-533 — 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/Rask.Batteries.Generators/ModelInputGenerator.ModelClass.cs:515` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (8 lines × 2) src/Rask.Cqrs/LocalDispatcher.cs:39— src/Rask.Cqrs/LocalDispatcher.cs:39-46 | src/Rask.Cqrs/LocalDispatcher.cs:59-66 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (8 lines × 2) src/Rask.Generators/ComponentFactoryGenerator.ChainStates.cs:396— src/Rask.Generators/ComponentFactoryGenerator.ChainStates.cs:396-403 | src/Rask.Generators/ComponentFactoryGenerator.ChainStates.cs:548-560 — 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 (8 lines × 2) src/Rask.Generators/Analyzers/ChainAssignedAfterwardsAnalyzer.cs:174— src/Rask.Generators/Analyzers/ChainAssignedAfterwardsAnalyzer.cs:174-183 | src/Rask.Generators/Analyzers/DuplicateChainCallAnalyzer.cs:152-159 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `src/Rask.Generators/Analyzers/DuplicateChainCallAnalyzer.cs:147` calls `Unwrap` and `src/Rask.Generators/Analyzers/ChainAssignedAfterwardsAnalyzer.cs:170` 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 (8 lines × 2) src/Rask.Site/Features/UiDocs/Examples/SelectClearableExample.cs:9— src/Rask.Site/Features/UiDocs/Examples/SelectClearableExample.cs:9-16 | src/Rask.Site/Features/UiDocs/Examples/SelectSmallExample.cs:9-16 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `src/Rask.Site/Features/UiDocs/Examples/SelectClearableExample.cs:9` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (8 lines × 2) src/Rask.Site/Features/UiDocs/Examples/CommandExample.cs:11— src/Rask.Site/Features/UiDocs/Examples/CommandExample.cs:11-18 | src/Rask.Site/Features/UiDocs/Examples/CommandModalExample.cs:17-24 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (5 lines × 2) src/Rask.Core/Live/FrameDiffer.cs:234— src/Rask.Core/Live/FrameDiffer.cs:234-238 | src/Rask.Core/Live/FrameDiffer.cs:379-383 — 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/Rask.Core/Live/FrameDiffer.cs:234` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (5 lines × 2) src/Rask.DevTools/Panel/DevToolsPerfTab.cs:233— src/Rask.DevTools/Panel/DevToolsPerfTab.cs:233-237 | src/Rask.DevTools/Panel/DevToolsWireTab.cs:126-130 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `src/Rask.DevTools/Panel/DevToolsPerfTab.cs:233` 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/Rask.Generators/ComponentScopedJsGenerator.cs:135— src/Rask.Generators/ComponentScopedJsGenerator.cs:135-141 | src/Rask.Generators/ScopedScripts/ScopedScriptCallsGenerator.cs:93-97 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `src/Rask.Generators/ComponentScopedJsGenerator.cs:135` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (5 lines × 2) src/Rask.Generators.Shared/AggregateShape.cs:291— src/Rask.Generators.Shared/AggregateShape.cs:291-295 | src/Rask.Generators.Shared/GeneratedModelShape.cs:873-877 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (5 lines × 2) src/Rask.Ui/UiSelect.cs:57— src/Rask.Ui/UiSelect.cs:57-61 | src/Rask.Ui/UiSelectMultiple.cs:56-60 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (5 lines × 2) src/Rask.Dom.Tasks/DomRefEmitter.cs:181— src/Rask.Dom.Tasks/DomRefEmitter.cs:181-185 | src/Rask.Dom.Tasks/WebMember.cs:411-415 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `src/Rask.Dom.Tasks/DomRefEmitter.cs:181` 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/Rask.Generators/ComponentFactoryGenerator.SetterOverloads.cs:388— src/Rask.Generators/ComponentFactoryGenerator.SetterOverloads.cs:388-392 | src/Rask.Generators/ComponentFactoryGenerator.SetterOverloads.cs:403-407 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Rask.Generators/ComponentFactoryGenerator.SetterOverloads.cs:388` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. 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 (5 lines × 2) src/Rask.Site/Features/UiDocs/Examples/TimelineBlockExample.cs:6— src/Rask.Site/Features/UiDocs/Examples/TimelineBlockExample.cs:6-10 | src/Rask.Site/Features/UiDocs/Examples/TimelineSubgridExample.cs:7-11 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `src/Rask.Site/Features/UiDocs/Examples/TimelineBlockExample.cs:6` 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/Rask.Site/Features/UiDocs/Examples/SelectBackendSearchExample.cs:15— src/Rask.Site/Features/UiDocs/Examples/SelectBackendSearchExample.cs:15-19 | src/Rask.Site/Features/UiDocs/Examples/SelectLoadingExample.cs:12-16 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `src/Rask.Site/Features/UiDocs/Examples/SelectBackendSearchExample.cs:15` 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 (5 lines × 2) src/Rask.Site/Features/UiDocs/Examples/PillboxBackendSearchExample.cs:35— src/Rask.Site/Features/UiDocs/Examples/PillboxBackendSearchExample.cs:35-39 | src/Rask.Site/Features/UiDocs/Examples/PillboxCreateExample.cs:21-25 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (5 lines × 2) src/Rask.Site/Features/UiDocs/Examples/RadioBareCardsExample.cs:8— src/Rask.Site/Features/UiDocs/Examples/RadioBareCardsExample.cs:8-12 | src/Rask.Site/Features/UiDocs/Examples/RadioCardIconsExample.cs:8-12 — 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.
Unresolved JS interop binding src/Rask.Core/Browser/IndexedDb.cs:20— `__raskIdb.open` is invoked from C# here, and no definition of that name was found by the search this dimension ran: 2 first-party JavaScript file(s) (.js/.mjs/.cjs, vendored trees excluded) plus 10 markup file(s) scanned for inline <script> blocks (.html/.cshtml/.razor). NOT searched: scripts fetched or injected at runtime, and vendored/dynamically-loaded bundles — a definition living in one of those is invisible here. To settle it, grep the repository for `__raskIdb.open`. If it is defined nowhere, this call throws or silently no-ops at runtime, and a swallowed interop catch will hide it — define it, or invoke a wrapper that exists.
Unresolved JS interop binding src/Rask.Core/Browser/IndexedDb.cs:30— `__raskIdb.set` is invoked from C# here, and no definition of that name was found by the search this dimension ran: 2 first-party JavaScript file(s) (.js/.mjs/.cjs, vendored trees excluded) plus 10 markup file(s) scanned for inline <script> blocks (.html/.cshtml/.razor). NOT searched: scripts fetched or injected at runtime, and vendored/dynamically-loaded bundles — a definition living in one of those is invisible here. To settle it, grep the repository for `__raskIdb.set`. If it is defined nowhere, this call throws or silently no-ops at runtime, and a swallowed interop catch will hide it — define it, or invoke a wrapper that exists.
Unresolved JS interop binding src/Rask.Core/Browser/IndexedDb.cs:36— `__raskIdb.get` is invoked from C# here, and no definition of that name was found by the search this dimension ran: 2 first-party JavaScript file(s) (.js/.mjs/.cjs, vendored trees excluded) plus 10 markup file(s) scanned for inline <script> blocks (.html/.cshtml/.razor). NOT searched: scripts fetched or injected at runtime, and vendored/dynamically-loaded bundles — a definition living in one of those is invisible here. To settle it, grep the repository for `__raskIdb.get`. If it is defined nowhere, this call throws or silently no-ops at runtime, and a swallowed interop catch will hide it — define it, or invoke a wrapper that exists.
Unresolved JS interop binding src/Rask.Core/Browser/IndexedDb.cs:61— `__raskIdb.keys` is invoked from C# here, and no definition of that name was found by the search this dimension ran: 2 first-party JavaScript file(s) (.js/.mjs/.cjs, vendored trees excluded) plus 10 markup file(s) scanned for inline <script> blocks (.html/.cshtml/.razor). NOT searched: scripts fetched or injected at runtime, and vendored/dynamically-loaded bundles — a definition living in one of those is invisible here. To settle it, grep the repository for `__raskIdb.keys`. If it is defined nowhere, this call throws or silently no-ops at runtime, and a swallowed interop catch will hide it — define it, or invoke a wrapper that exists.
Unresolved JS interop binding src/Rask.Core/Browser/Signaling.cs:36— `__raskSignal.open` is invoked from C# here, and no definition of that name was found by the search this dimension ran: 2 first-party JavaScript file(s) (.js/.mjs/.cjs, vendored trees excluded) plus 10 markup file(s) scanned for inline <script> blocks (.html/.cshtml/.razor). NOT searched: scripts fetched or injected at runtime, and vendored/dynamically-loaded bundles — a definition living in one of those is invisible here. To settle it, grep the repository for `__raskSignal.open`. If it is defined nowhere, this call throws or silently no-ops at runtime, and a swallowed interop catch will hide it — define it, or invoke a wrapper that exists.
Unresolved JS interop binding src/Rask.Core/Browser/Signaling.cs:75— `__raskSignal.close` is invoked from C# here, and no definition of that name was found by the search this dimension ran: 2 first-party JavaScript file(s) (.js/.mjs/.cjs, vendored trees excluded) plus 10 markup file(s) scanned for inline <script> blocks (.html/.cshtml/.razor). NOT searched: scripts fetched or injected at runtime, and vendored/dynamically-loaded bundles — a definition living in one of those is invisible here. To settle it, grep the repository for `__raskSignal.close`. If it is defined nowhere, this call throws or silently no-ops at runtime, and a swallowed interop catch will hide it — define it, or invoke a wrapper that exists.
Unresolved JS interop binding src/Rask.Core/Browser/ViewTransitions.cs:15— `__raskVt.set` is invoked from C# here, and no definition of that name was found by the search this dimension ran: 2 first-party JavaScript file(s) (.js/.mjs/.cjs, vendored trees excluded) plus 10 markup file(s) scanned for inline <script> blocks (.html/.cshtml/.razor). NOT searched: scripts fetched or injected at runtime, and vendored/dynamically-loaded bundles — a definition living in one of those is invisible here. To settle it, grep the repository for `__raskVt.set`. If it is defined nowhere, this call throws or silently no-ops at runtime, and a swallowed interop catch will hide it — define it, or invoke a wrapper that exists.
Unresolved JS interop binding src/Rask.Core/Browser/WebAuthn.cs:31— `__raskWebAuthn.get` is invoked from C# here, and no definition of that name was found by the search this dimension ran: 2 first-party JavaScript file(s) (.js/.mjs/.cjs, vendored trees excluded) plus 10 markup file(s) scanned for inline <script> blocks (.html/.cshtml/.razor). NOT searched: scripts fetched or injected at runtime, and vendored/dynamically-loaded bundles — a definition living in one of those is invisible here. To settle it, grep the repository for `__raskWebAuthn.get`. If it is defined nowhere, this call throws or silently no-ops at runtime, and a swallowed interop catch will hide it — define it, or invoke a wrapper that exists.
Unresolved JS interop binding src/Rask.Core/Browser/WebRtc.cs:130— `__raskRtc.close` is invoked from C# here, and no definition of that name was found by the search this dimension ran: 2 first-party JavaScript file(s) (.js/.mjs/.cjs, vendored trees excluded) plus 10 markup file(s) scanned for inline <script> blocks (.html/.cshtml/.razor). NOT searched: scripts fetched or injected at runtime, and vendored/dynamically-loaded bundles — a definition living in one of those is invisible here. To settle it, grep the repository for `__raskRtc.close`. If it is defined nowhere, this call throws or silently no-ops at runtime, and a swallowed interop catch will hide it — define it, or invoke a wrapper that exists.
Unresolved JS interop binding src/Rask.Core/ElementRefCall.cs:34— `__raskEl.get` is invoked from C# here, and no definition of that name was found by the search this dimension ran: 2 first-party JavaScript file(s) (.js/.mjs/.cjs, vendored trees excluded) plus 10 markup file(s) scanned for inline <script> blocks (.html/.cshtml/.razor). NOT searched: scripts fetched or injected at runtime, and vendored/dynamically-loaded bundles — a definition living in one of those is invisible here. To settle it, grep the repository for `__raskEl.get`. If it is defined nowhere, this call throws or silently no-ops at runtime, and a swallowed interop catch will hide it — define it, or invoke a wrapper that exists.
Unresolved JS interop binding src/Rask.Core/ElementRefCall.cs:37— `__raskEl.set` is invoked from C# here, and no definition of that name was found by the search this dimension ran: 2 first-party JavaScript file(s) (.js/.mjs/.cjs, vendored trees excluded) plus 10 markup file(s) scanned for inline <script> blocks (.html/.cshtml/.razor). NOT searched: scripts fetched or injected at runtime, and vendored/dynamically-loaded bundles — a definition living in one of those is invisible here. To settle it, grep the repository for `__raskEl.set`. If it is defined nowhere, this call throws or silently no-ops at runtime, and a swallowed interop catch will hide it — define it, or invoke a wrapper that exists.
ClassTooLong: UiApi src/Rask.Site/Features/UiDocs/UiApi.cs— ClassTooLong — 1382 significant lines (blank, comment-only and punctuation-only lines excluded), 0 methods. The bar is 400 significant lines; this is 982 over it, 3.46× the bar. The type holds no instance state, so there is no shared data to group its members by. To reduce it, split it by area instead: give each cohesive family of members its own smaller type, so no one type has to be read whole to change one of them.
ClassTooLong: TranslationCatalogGenerator src/Rask.Generators/Translations/TranslationCatalogGenerator.cs— ClassTooLong — 760 significant lines (blank, comment-only and punctuation-only lines excluded), 30 methods. The bar is 400 significant lines; this is 360 over it, 1.90× the bar. The type holds no instance state, so there is no shared data to group its members by. To reduce it, split it by area instead: give each cohesive family of members its own smaller type, so no one type has to be read whole to change one of them.
ClassTooLong: Ui src/Rask.Ui/Ui.DateRangePreset.cs— ClassTooLong — 637 significant lines (blank, comment-only and punctuation-only lines excluded), 0 methods. The bar is 400 significant lines; this is 237 over it, 1.59× the bar. The type holds no instance state, so there is no shared data to group its members by. To reduce it, split it by area instead: give each cohesive family of members its own smaller type, so no one type has to be read whole to change one of them.
ClassTooLong: ParityMenu scripts/flux/Flux/Commands/ParityMenu.cs— ClassTooLong — 516 significant lines (blank, comment-only and punctuation-only lines excluded), 25 methods. The bar is 400 significant lines; this is 116 over it, 1.29× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
ClassTooLong: DomEventEmitter src/Rask.Dom.Tasks/DomEventEmitter.cs— ClassTooLong — 467 significant lines (blank, comment-only and punctuation-only lines excluded), 30 methods. The bar is 400 significant lines; this is 67 over it, 1.17× the bar. The type holds no instance state, so there is no shared data to group its members by. To reduce it, split it by area instead: give each cohesive family of members its own smaller type, so no one type has to be read whole to change one of them.
ClassTooLong: ApiClientGenerator src/Rask.Api.Generators/ApiClientGenerator.cs— ClassTooLong — 422 significant lines (blank, comment-only and punctuation-only lines excluded), 23 methods. The bar is 400 significant lines; this is 22 over it, 1.06× the bar. The type holds no instance state, so there is no shared data to group its members by. To reduce it, split it by area instead: give each cohesive family of members its own smaller type, so no one type has to be read whole to change one of them.
ClassTooLong: AccountService src/Rask.Auth.Api/AccountService.cs— ClassTooLong — 413 significant lines (blank, comment-only and punctuation-only lines excluded), 30 methods. The bar is 400 significant lines; this is 13 over it, 1.03× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
ClassTooLong: ReadModelGenerator src/Rask.Batteries.Generators/ReadModelGenerator.cs— ClassTooLong — 408 significant lines (blank, comment-only and punctuation-only lines excluded), 20 methods. The bar is 400 significant lines; this is 8 over it, 1.02× the bar. The type holds no instance state, so there is no shared data to group its members by. To reduce it, split it by area instead: give each cohesive family of members its own smaller type, so no one type has to be read whole to change one of them.
ClassTooLong: CqrsCodecGenerator src/Rask.Batteries.Generators/CqrsCodecGenerator.cs— ClassTooLong — 404 significant lines (blank, comment-only and punctuation-only lines excluded), 27 methods. The bar is 400 significant lines; this is 4 over it, 1.01× the bar. The type holds no instance state, so there is no shared data to group its members by. To reduce it, split it by area instead: give each cohesive family of members its own smaller type, so no one type has to be read whole to change one of them.
ClassTooLong: UiDocsCatalog src/Rask.Site/Features/UiDocs/UiDocsCatalog.cs— ClassTooLong — 401 significant lines (blank, comment-only and punctuation-only lines excluded), 0 methods. The bar is 400 significant lines; this is 1 over it, 1.00× the bar. The type holds no instance state, so there is no shared data to group its members by. To reduce it, split it by area instead: give each cohesive family of members its own smaller type, so no one type has to be read whole to change one of them.
Duplicated block (7 lines × 2) src/Rask.Dom.Tasks/DomEmitter.cs:513— src/Rask.Dom.Tasks/DomEmitter.cs:513-519 | src/Rask.Dom.Tasks/DomEmitter.cs:523-529 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (7 lines × 2) src/Rask.Core/Live/LivePayload.cs:637— src/Rask.Core/Live/LivePayload.cs:637-644 | src/Rask.Core/Live/LivePayload.cs:678-684 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (7 lines × 2) src/Rask.Data/AggregateSave.cs:119— src/Rask.Data/AggregateSave.cs:119-126 | src/Rask.Data/AggregateSave.cs:171-177 — 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/Rask.Data/AggregateSave.cs:119` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (7 lines × 2) REDACTED:2376— REDACTED:2376-2382 | src/Rask.Wasm/WasmLiveSession.cs:707-713 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `REDACTED:2376` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
Duplicated block (7 lines × 2) scripts/flux/Flux/Commands/ParityMenu.cs:1177— scripts/flux/Flux/Commands/ParityMenu.cs:1177-1183 | scripts/flux/Flux/Commands/ParityTooltip.cs:549-555 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (7 lines × 2) src/Rask.DevTools/Panel/DevToolsErrorsTab.cs:52— src/Rask.DevTools/Panel/DevToolsErrorsTab.cs:52-58 | src/Rask.DevTools/Panel/DevToolsTabs.cs:48-54 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. 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/Rask.Site/Features/UiDocs/Examples/EditorCustomItemExample.cs:15— src/Rask.Site/Features/UiDocs/Examples/EditorCustomItemExample.cs:15-21 | src/Rask.Site/Features/UiDocs/Examples/EditorCustomizationExample.cs:10-16 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `src/Rask.Site/Features/UiDocs/Examples/EditorCustomItemExample.cs:15` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (7 lines × 2) src/Rask.Site/Features/UiDocs/Examples/ChartGroupedBarsExample.cs:19— src/Rask.Site/Features/UiDocs/Examples/ChartGroupedBarsExample.cs:19-25 | src/Rask.Site/Features/UiDocs/Examples/ChartStackedBarsExample.cs:19-25 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `src/Rask.Site/Features/UiDocs/Examples/ChartGroupedBarsExample.cs:19` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (7 lines × 2) src/Rask.Site/Features/UiDocs/Examples/ModalExample.cs:11— src/Rask.Site/Features/UiDocs/Examples/ModalExample.cs:11-17 | src/Rask.Site/Features/UiDocs/Examples/ModalFlyoutExample.cs:9-15 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `src/Rask.Site/Features/UiDocs/Examples/ModalExample.cs:11` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (6 lines × 2) src/Rask.SQLite.EntityFrameworkCore/RaskSqliteRangeExclusionSqlGenerator.cs:38— src/Rask.SQLite.EntityFrameworkCore/RaskSqliteRangeExclusionSqlGenerator.cs:38-43 | src/Rask.SQLite.EntityFrameworkCore/RaskSqliteStrictRangeExclusionSqlGenerator.cs:34-39 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (6 lines × 2) src/Rask.Auth.Api/AccountPrincipals.cs:14— src/Rask.Auth.Api/AccountPrincipals.cs:14-19 | src/Rask.Auth.Api/AccountService.cs:502-507 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `src/Rask.Auth.Api/AccountPrincipals.cs:14` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (6 lines × 2) src/Rask.Batteries.Generators/ModelInputGenerator.Writes.cs:92— src/Rask.Batteries.Generators/ModelInputGenerator.Writes.cs:92-98 | src/Rask.Batteries.Generators/ModelInputGenerator.Writes.cs:123-128 — 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/Rask.Batteries.Generators/ModelInputGenerator.Writes.cs:123` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (6 lines × 2) src/Rask.Core/Component.StaleEvents.cs:138— src/Rask.Core/Component.StaleEvents.cs:138-143 | src/Rask.Core/Component.StaleEvents.cs:180-185 — 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/Rask.Core/Component.StaleEvents.cs:138` 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) scripts/flux/Flux/Commands/Rail.cs:146— scripts/flux/Flux/Commands/Rail.cs:146-151 | scripts/flux/Flux/Commands/Rail.cs:188-193 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (6 lines × 2) src/Rask.Site/Features/UiDocs/Examples/RowActionsExample.cs:20— src/Rask.Site/Features/UiDocs/Examples/RowActionsExample.cs:20-25 | src/Rask.Site/Features/UiDocs/Examples/RowActionsMenuExample.cs:30-35 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `src/Rask.Site/Features/UiDocs/Examples/RowActionsExample.cs:20` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
Duplicated block (6 lines × 2) src/Rask.Site/Features/UiDocs/Examples/ComposerExample.cs:27— src/Rask.Site/Features/UiDocs/Examples/ComposerExample.cs:27-32 | src/Rask.Site/Features/UiDocs/Examples/ComposerSubmitExample.cs:28-33 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (6 lines × 2) src/Rask.Site/Features/UiDocs/Examples/TableSortableExample.cs:62— src/Rask.Site/Features/UiDocs/Examples/TableSortableExample.cs:62-67 | src/Rask.Site/Features/UiDocs/Examples/TableSteadyColumnsExample.cs:81-86 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Outbound HTTP without resilience scripts/flux/Flux/Commands/ParityChart.cs:221— `new HttpClient()` builds an outbound HTTP client and nothing bounds it: no timeout is set on it and no retry or resilience policy wraps its calls in the type that owns it. A slow or failing dependency will hold this service's request, thread or connection — and cascade — until the call gives up on its own (100 s for HttpClient's default).
Outbound HTTP without resilience scripts/flux/Flux/Commands/Refresh.cs:64— `new HttpClient()` builds an outbound HTTP client and nothing bounds it: no timeout is set on it and no retry or resilience policy wraps its calls in the type that owns it. A slow or failing dependency will hold this service's request, thread or connection — and cascade — until the call gives up on its own (100 s for HttpClient's default).
Outbound HTTP without resilience scripts/flux/Flux/Commands/Sync.cs:379— `new HttpClient()` builds an outbound HTTP client and nothing bounds it: no timeout is set on it and no retry or resilience policy wraps its calls in the type that owns it. A slow or failing dependency will hold this service's request, thread or connection — and cascade — until the call gives up on its own (100 s for HttpClient's default).
Outbound HTTP without resilience src/Rask.Cli/Scaffolding/PackageFeed.cs:63— `new HttpClient()` builds an outbound HTTP client and nothing bounds it: no timeout is set on it and no retry or resilience policy wraps its calls in the type that owns it. A slow or failing dependency will hold this service's request, thread or connection — and cascade — until the call gives up on its own (100 s for HttpClient's default).
Outbound HTTP without resilience src/Rask.Site/ExampleServiceCollectionExtensions.cs:25— `new HttpClient { BaseAddress = httpBaseAddress(sp) }` builds an outbound HTTP client and nothing bounds it: no timeout is set on it and no retry or resilience policy wraps its calls in the type that owns it. A slow or failing dependency will hold this service's request, thread or connection — and cascade — until the call gives up on its own (100 s for HttpClient's default).
Outbound HTTP without resilience src/Rask.Storage/RaskStorageServiceCollectionExtensions.cs:47— `services.AddHttpClient(HttpClientName)` registers an outbound HTTP client, and what is applied to it does not bound it. Its `Timeout` is set to `Timeout.InfiniteTimeSpan`, which removes HttpClient's own bound rather than setting one. A slow or failing dependency will hold this service's request, thread or connection — and cascade — until the call gives up on its own (100 s for HttpClient's default).
Outbound HTTP without resilience src/Rask.Wasm/WasmHostBuilder.cs:99— `new HttpClient(new SignInRefusals(sp, origin) { InnerHandler = new HttpClient...` builds an outbound HTTP client and nothing bounds it: no timeout is set on it and no retry or resilience policy wraps its calls in the type that owns it. A slow or failing dependency will hold this service's request, thread or connection — and cascade — until the call gives up on its own (100 s for HttpClient's default).
Outbound HTTP without resilience src/Rask.Wasm/WasmHostBuilder.cs:103— `new HttpClient()` builds an outbound HTTP client and nothing bounds it: no timeout is set on it and no retry or resilience policy wraps its calls in the type that owns it. A slow or failing dependency will hold this service's request, thread or connection — and cascade — until the call gives up on its own (100 s for HttpClient's default).
X18 · Disposal-pattern correctness· Disposes a dependency it does not own · ×8
Disposes a dependency it does not own src/Rask.Auth.Api/CoseKey.cs:104— `_key` is never created by `CoseKey` — every assignment to it takes a constructor parameter — yet this type disposes it here (line 104). Its declared type `AsymmetricAlgorithm` is an abstract class, so the instance came from whoever chose and created it, and that owner decides when it ends. Disposing it from here reaches outside this object's lifetime: a dependency shared with the rest of the process is torn down when THIS instance goes away, and the real owner's later `Dispose()` runs a second time on an object already disposed. Drop the call — a type disposes what it constructed, and only that. If this dependency genuinely is exclusive to this instance, construct it here (or take an owned factory) so the ownership is stated in the code rather than assumed.
Disposes a dependency it does not own src/Rask.Cli/Commands/DockerTunnel.cs:187— `_stop` is a `CancellationTokenSource` that `DockerTunnel` never creates — every assignment to it takes a constructor parameter — and this type disposes it here (line 187). The caller that hands it over at `new DockerTunnel(host, directory, stop, ssh)` (DockerTunnel.cs line 102) releases the same value itself, so it kept ownership: this release is a second one, on a value that is still the caller's, and it ends the caller's instance while the caller may still be using it. Drop the call and leave the release to the caller that created the value — or, if this type is meant to own it, stop releasing it at the construction site so ownership is stated once.
Disposes a dependency it does not own src/Rask.Core/ScopedAssets/ScriptObject.cs:38— `Reference` is never created by `ScriptObject` — every assignment to it takes a constructor parameter — yet this type disposes it here (line 38). Its declared type `IJSObjectReference` is an interface, so the instance came from whoever chose and created it, and that owner decides when it ends. Disposing it from here reaches outside this object's lifetime: a dependency shared with the rest of the process is torn down when THIS instance goes away, and the real owner's later `Dispose()` runs a second time on an object already disposed. Drop the call — a type disposes what it constructed, and only that. If this dependency genuinely is exclusive to this instance, construct it here (or take an owned factory) so the ownership is stated in the code rather than assumed.
Disposes a dependency it does not own src/Rask.Data/TestDatabase.cs:228— `_schemaOwner` is never created by `TestDatabase` — every assignment to it takes a constructor parameter — yet this type disposes it here (line 228). Its declared type `RaskDbContext` is an abstract class, so the instance came from whoever chose and created it, and that owner decides when it ends. Disposing it from here reaches outside this object's lifetime: a dependency shared with the rest of the process is torn down when THIS instance goes away, and the real owner's later `Dispose()` runs a second time on an object already disposed. Drop the call — a type disposes what it constructed, and only that. If this dependency genuinely is exclusive to this instance, construct it here (or take an owned factory) so the ownership is stated in the code rather than assumed.
Disposes a dependency it does not own src/Rask.Data/TestDatabase.cs:231— `_lease` is never created by `TestDatabase` — every assignment to it takes a constructor parameter — yet this type disposes it here (line 231). Its declared type `IAsyncDisposable` is an interface, so the instance came from whoever chose and created it, and that owner decides when it ends. Disposing it from here reaches outside this object's lifetime: a dependency shared with the rest of the process is torn down when THIS instance goes away, and the real owner's later `Dispose()` runs a second time on an object already disposed. Drop the call — a type disposes what it constructed, and only that. If this dependency genuinely is exclusive to this instance, construct it here (or take an owned factory) so the ownership is stated in the code rather than assumed.
Disposes a dependency it does not own src/Rask.Pdf/DevToolsConnection.cs:97— `_toBrowser` is never created by `DevToolsConnection` — every assignment to it takes a constructor parameter — yet this type disposes it here (line 97). Its declared type `Stream` is an abstract class, so the instance came from whoever chose and created it, and that owner decides when it ends. Disposing it from here reaches outside this object's lifetime: a dependency shared with the rest of the process is torn down when THIS instance goes away, and the real owner's later `Dispose()` runs a second time on an object already disposed. Drop the call — a type disposes what it constructed, and only that. If this dependency genuinely is exclusive to this instance, construct it here (or take an owned factory) so the ownership is stated in the code rather than assumed.
Disposes a dependency it does not own src/Rask.Storage/Backends/DatabaseReadStream.cs:104— `db` is never created by `DatabaseReadStream` — every assignment to it takes a constructor parameter — yet this type disposes it here (line 104). Its declared type `DbContext` is an abstract class, so the instance came from whoever chose and created it, and that owner decides when it ends. Disposing it from here reaches outside this object's lifetime: a dependency shared with the rest of the process is torn down when THIS instance goes away, and the real owner's later `Dispose()` runs a second time on an object already disposed. Drop the call — a type disposes what it constructed, and only that. If this dependency genuinely is exclusive to this instance, construct it here (or take an owned factory) so the ownership is stated in the code rather than assumed.
Disposes a dependency it does not own src/Rask.Storage/Backends/DatabaseReadStream.cs:115— `db` is never created by `DatabaseReadStream` — every assignment to it takes a constructor parameter — yet this type disposes it here (line 115). Its declared type `DbContext` is an abstract class, so the instance came from whoever chose and created it, and that owner decides when it ends. Disposing it from here reaches outside this object's lifetime: a dependency shared with the rest of the process is torn down when THIS instance goes away, and the real owner's later `Dispose()` runs a second time on an object already disposed. Drop the call — a type disposes what it constructed, and only that. If this dependency genuinely is exclusive to this instance, construct it here (or take an owned factory) so the ownership is stated in the code rather than assumed.
AC3 · Page structure· Page without a main landmark · ×7
Page without a main landmark assets/og-card.html:2— No <main> (or role="main") means no "skip to content" target and a weaker landmark map. Wrap the primary content in <main>.
Page without a main landmark src/Rask.Site.DataDemo/wwwroot/index.html:2— No <main> (or role="main") means no "skip to content" target and a weaker landmark map. Wrap the primary content in <main>.
Page without a main landmark src/Rask.Site/wwwroot/index.html:2— No <main> (or role="main") means no "skip to content" target and a weaker landmark map. Wrap the primary content in <main>.
Page without a main landmark src/Rask.Templates/server/wwwroot/offline.html:2— No <main> (or role="main") means no "skip to content" target and a weaker landmark map. Wrap the primary content in <main>.
Page without a main landmark src/Rask.Templates/wasm-hosted/Client/wwwroot/index.html:2— No <main> (or role="main") means no "skip to content" target and a weaker landmark map. Wrap the primary content in <main>.
Page without a main landmark src/Rask.Templates/wasm/wwwroot/index.html:2— No <main> (or role="main") means no "skip to content" target and a weaker landmark map. Wrap the primary content in <main>.
Page without a main landmark src/Rask.Wasm/Browser/index.html:15— No <main> (or role="main") means no "skip to content" target and a weaker landmark map. Wrap the primary content in <main>.
Off the main sequence: Rask.SQLite src/Rask.SQLite/Rask.SQLite.csproj:1— Rask.SQLite: abstractness 0.06, instability 0.00, distance 0.94 — zone of pain — concrete and depended on by 3 project(s), so it's rigid to change.
Off the main sequence: Rask.Wire src/Rask.Wire/Rask.Wire.csproj:1— Rask.Wire: abstractness 0.09, instability 0.00, distance 0.91 — zone of pain — concrete and depended on by 7 project(s), so it's rigid to change.
Off the main sequence: Rask.SQLite.Snapshots src/Rask.SQLite.Snapshots/Rask.SQLite.Snapshots.csproj:1— Rask.SQLite.Snapshots: abstractness 0.17, instability 0.00, distance 0.83 — zone of pain — concrete and depended on by 2 project(s), so it's rigid to change.
Off the main sequence: Rask.Web src/Rask.Web/Rask.Web.csproj:1— Rask.Web: abstractness 0.04, instability 0.14, distance 0.82 — zone of pain — concrete and depended on by 3 project(s), so it's rigid to change.
Off the main sequence: Rask.Core(net10.0) src/Rask.Core/Rask.Core.csproj:1— Rask.Core(net10.0): abstractness 0.13, instability 0.05, distance 0.81 — zone of pain — concrete and depended on by 16 project(s), so it's rigid to change.
Off the main sequence: Rask.Validation.FluentValidation src/Rask.Validation.FluentValidation/Rask.Validation.FluentValidation.csproj:1— Rask.Validation.FluentValidation: abstractness 0.00, instability 0.20, distance 0.80 — zone of pain — concrete and depended on by 2 project(s), so it's rigid to change.
Off the main sequence: Rask.Api.Client src/Rask.Api.Client/Rask.Api.Client.csproj:1— Rask.Api.Client: abstractness 0.00, instability 0.25, distance 0.75 — zone of pain — concrete and depended on by 2 project(s), so it's rigid to change.
X24 · Document value interpolated into markup unescaped· Untrusted text written into markup unescaped · ×7
Untrusted text written into markup unescaped src/Rask.Auth.Api/AuthEmailBodies.cs:49— `Escape(link)` is text this program did not author, and it is written into the start of a URL attribute, where it chooses the scheme through markup this member returns with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. HTML encoding does not help here — a `javascript:` URL contains nothing it changes; allow only http(s) or a relative path.
Untrusted text written into markup unescaped src/Rask.Mail/MailSerializer.cs:40— `message.HtmlBody` is text this program did not author, and it is written into the text of an element through an HTML e-mail body with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup.
Untrusted text written into markup unescaped src/Rask.Mail/MimeMailFactory.cs:25— `mail.HtmlBody` is text this program did not author, and it is written into the text of an element through an HTML e-mail body with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup.
Untrusted text written into markup unescaped src/Rask.Mail/QueuedMail.cs:31— `email.HtmlBody` is text this program did not author, and it is written into the text of an element through an HTML e-mail body with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup.
Untrusted text written into markup unescaped REDACTED:92— `html` is text this program did not author, and it is written into the text of an element through `innerHTML` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup.
Untrusted text written into markup unescaped REDACTED:96— `html` is text this program did not author, and it is written into the text of an element through `innerHTML` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup.
Untrusted text written into markup unescaped REDACTED:360— `op[2]==null?"":op[2]` is text this program did not author, and it is written into the text of an element through `innerHTML` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup.
Stateful shared instance: IndexedDbSnapshotStore src/Rask.SQLite.Browser/IndexedDbSnapshotStore.cs:17— `IndexedDbSnapshotStore` is not registered, but the singleton `BrowserSqliteHost` creates it and keeps it in `_store`, so one instance outlives every request and is shared by every caller that reaches it — and it mutates instance state outside any lock (_store; e.g. `_store` at line 110).
Stateful shared instance: RouteTitle src/Rask.Core/Routing/RouteTitle.cs:6— `RouteTitle` is not registered, but the singleton `RouteState` creates it and keeps it in `_title`, so one instance outlives every request and is shared by every caller that reaches it — and it mutates instance state outside any lock (_walked, _readers, _value; e.g. `_walked` at line 18).
Stateful shared instance: Lazy src/Rask.Core/Components/Lazy.cs:20— `Lazy` is not registered, but `RaskEndpointExtensions` creates it and keeps it in the static `RuntimeHash`, 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 (_inView; e.g. `_inView` at line 51).
Stateful shared instance: WasmLiveSession src/Rask.Wasm/WasmLiveSession.cs:19— `WasmLiveSession` is not registered, but `WasmHostBuilder` creates it and keeps it in the static `JSInterop._session`, 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 (_navigator, _guardedTo, _lastBuildHadJsInvokes; e.g. `_navigator` at line 178).
Stateful shared instance: WasmHostedServices src/Rask.Wasm/WasmHostedServices.cs:26— `WasmHostedServices` is not registered, but `WasmHostBuilder` creates it and keeps it in the static `JSInterop._hostedServices`, 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 (_started, _stopped; e.g. `_started` at line 77).
Stateful shared instance: DevToolsTreeCapture src/Rask.DevTools/Probe/DevToolsTreeCapture.cs:21— `DevToolsTreeCapture` is not registered, but the singleton `DevToolsFeed` creates it and keeps it in `_capture`, so one instance outlives every request and is shared by every caller that reaches it — and it mutates instance state outside any lock (Root, ItemCount, _items, HasContexts, _provideCount, _provides; e.g. `Root` at line 52).
Duplicated block (17 lines × 2) src/Rask.Core/ScopedCss/CssScoper.cs:250— src/Rask.Core/ScopedCss/CssScoper.cs:250-266 | src/Rask.Core/ScopedCss/CssScoper.cs:291-307 — 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 (17 lines × 2) src/Rask.Ui/UiDatePickerButton.cs:13— src/Rask.Ui/UiDatePickerButton.cs:13-29 | src/Rask.Ui/UiDatetimePickerButton.cs:13-29 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (17 lines × 2) src/Rask.Batteries.Generators/EquatableArray.cs:24— src/Rask.Batteries.Generators/EquatableArray.cs:24-40 | src/Rask.Generators/EquatableArray.cs:21-37 — `src/Rask.Batteries.Generators/EquatableArray.cs` and `src/Rask.Generators/EquatableArray.cs` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 2 separate duplicated blocks between them, totalling at least 29 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (17 lines × 2) src/Rask.Core/Routing/RouteRegistry.cs:85— src/Rask.Core/Routing/RouteRegistry.cs:85-101 | src/Rask.Jobs/JobSerializerRegistry.cs:65-81 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `src/Rask.Core/Routing/RouteRegistry.cs:85` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (17 lines × 2) src/Rask.Postgres/PostgresFullTextSearchQueryInterceptor.cs:69— src/Rask.Postgres/PostgresFullTextSearchQueryInterceptor.cs:69-85 | src/Rask.SQLite.EntityFrameworkCore/FullTextSearchQueryInterceptor.cs:69-85 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (17 lines × 2) src/Rask.Ui/UiCheckboxGroup.cs:54— src/Rask.Ui/UiCheckboxGroup.cs:54-70 | src/Rask.Ui/UiPillbox.cs:34-50 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (13 lines × 2) src/Rask.Ui/UiDatePickerControl.cs:291— src/Rask.Ui/UiDatePickerControl.cs:291-303 | src/Rask.Ui/UiDatetimePickerControl.cs:285-297 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `src/Rask.Ui/UiDatePickerControl.cs:291` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (13 lines × 2) src/Rask.Cli/Commands/CompletionCommand.cs:103— src/Rask.Cli/Commands/CompletionCommand.cs:103-119 | src/Rask.Cli/Commands/CompletionCommand.cs:144-156 — 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/Rask.Cli/Commands/CompletionCommand.cs:103` 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 (13 lines × 2) src/Rask.Generators/Analyzers/BuilderEntry.cs:319— src/Rask.Generators/Analyzers/BuilderEntry.cs:319-331 | src/Rask.Generators/ComponentFactoryGenerator.ComponentModel.cs:127-139 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `src/Rask.Generators/Analyzers/BuilderEntry.cs:319` 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 (13 lines × 2) src/Rask.Ui/UiDatePickerScope.cs:24— src/Rask.Ui/UiDatePickerScope.cs:24-37 | src/Rask.Ui/UiDatetimePickerScope.cs:13-25 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (13 lines × 2) src/Rask.Ui/UiPhone.cs:181— src/Rask.Ui/UiPhone.cs:181-193 | src/Rask.Ui/UiSelectControl.Native.cs:50-62 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (13 lines × 2) scripts/flux/Flux/Commands/ParityMenu.cs:1231— scripts/flux/Flux/Commands/ParityMenu.cs:1231-1243 | scripts/flux/Flux/Commands/ParityTooltip.cs:567-579 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (10 lines × 2 locations) src/Rask.Core/Resources/rask-calendar.ts:179— src/Rask.Core/Resources/rask-calendar.ts:179 · src/Rask.Core/Resources/rask-datetime.ts:53 — 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.
Duplicated block (10 lines × 2 locations) src/Rask.Core/Resources/rask-color.ts:608— src/Rask.Core/Resources/rask-color.ts:608 · src/Rask.Core/Resources/rask-color.ts:628 — 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/Rask.Core/Resources/rask-scoped.ts:37— src/Rask.Core/Resources/rask-scoped.ts:37 · src/Rask.Core/Resources/rask-scoped.ts:75 — 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 (10 lines × 2 locations) src/Rask.Server/Resources/rask.ts:174— src/Rask.Server/Resources/rask.ts:174 · src/Rask.Wasm/Resources/rask.wasm.ts:126 — 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.
Duplicated block (10 lines × 2 locations) src/Rask.Server/Resources/rask.ts:1912— src/Rask.Server/Resources/rask.ts:1912 · src/Rask.Wasm/Resources/rask.wasm.ts:710 — 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.
Duplicated block (10 lines × 2 locations) src/Rask.Server/Resources/rask.ts:1929— src/Rask.Server/Resources/rask.ts:1929 · src/Rask.Wasm/Resources/rask.wasm.ts:726 — 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.
D10 · Test Quality· Fixed-sleep synchronisation · ×5
Fixed-sleep synchronisation: Editing_a_render_body_reaches_the_open_session_without_restarting_it tests/Rask.Cli.E2E.Tests/WatchHotReloadE2ETests.cs:78— This test starts a spawned process and then orders itself against it with `Task.Delay(TimeSpan.FromSeconds(3))` — a fixed wait, not a signal that the work is done. Whether it passes depends on how loaded the machine is, which is why a test written this way is green on a developer's box and random in CI. Wait for the event itself instead: the process's own exit or output, a completion handle, or a condition polled to a timeout.
Fixed-sleep synchronisation: An_applied_hot_reload_is_announced_to_the_browser tests/Rask.Cli.E2E.Tests/WatchHotReloadE2ETests.cs:116— This test starts a spawned process and then orders itself against it with `Task.Delay(TimeSpan.FromSeconds(3))` — a fixed wait, not a signal that the work is done. Whether it passes depends on how loaded the machine is, which is why a test written this way is green on a developer's box and random in CI. Wait for the event itself instead: the process's own exit or output, a completion handle, or a condition polled to a timeout.
Fixed-sleep synchronisation: Editing_a_route_template_serves_the_new_url tests/Rask.Cli.E2E.Tests/WatchHotReloadE2ETests.cs:143— This test starts a spawned process and then orders itself against it with `Task.Delay(TimeSpan.FromSeconds(3))` — a fixed wait, not a signal that the work is done. Whether it passes depends on how loaded the machine is, which is why a test written this way is green on a developer's box and random in CI. Wait for the event itself instead: the process's own exit or output, a completion handle, or a condition polled to a timeout.
Fixed-sleep synchronisation: A_trailing_await_in_OnMountAsync_fires_exactly_one_render tests/Rask.Core.Tests/Lifecycle/AsyncLifecycleRenderingTests.cs:33— This test starts a background task and then orders itself against it with `Task.Delay(50)` — a fixed wait, not a signal that the work is done. Whether it passes depends on how loaded the machine is, which is why a test written this way is green on a developer's box and random in CI. Wait for the event itself instead: the process's own exit or output, a completion handle, or a condition polled to a timeout.
Fixed-sleep synchronisation: A_long_lived_context_still_retries_a_later_contention tests/Rask.SQLite.EntityFrameworkCore.Tests/RaskSqliteExecutionStrategyTests.cs:95— This test starts a background task and then orders itself against it with `Task.Delay(TimeSpan.FromMilliseconds(2500))` — a fixed wait, not a signal that the work is done. Whether it passes depends on how loaded the machine is, which is why a test written this way is green on a developer's box and random in CI. Wait for the event itself instead: the process's own exit or output, a completion handle, or a condition polled to a timeout.
Duplicated block (16 lines × 2) src/Rask.Jobs/JobProcessor.cs:512— src/Rask.Jobs/JobProcessor.cs:512-527 | src/Rask.Outbox/OutboxProcessor.cs:271-286 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `src/Rask.Jobs/JobProcessor.cs:512` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (16 lines × 2) src/Rask.Ui/UiNavbarItem.cs:57— src/Rask.Ui/UiNavbarItem.cs:57-72 | src/Rask.Ui/UiNavlistItem.cs:38-53 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (16 lines × 2) src/Rask.Postgres/RaskPostgresDbContextOptionsExtensions.cs:50— src/Rask.Postgres/RaskPostgresDbContextOptionsExtensions.cs:50-65 | src/Rask.SqlServer/RaskSqlServerDbContextOptionsExtensions.cs:48-63 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `src/Rask.Postgres/RaskPostgresDbContextOptionsExtensions.cs:50` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (16 lines × 2) src/Rask.Postgres/PostgresFullTextSearchQueryInterceptor.cs:181— src/Rask.Postgres/PostgresFullTextSearchQueryInterceptor.cs:181-196 | src/Rask.SQLite.EntityFrameworkCore/FullTextSearchQueryInterceptor.cs:121-136 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (16 lines × 2) src/Rask.SQLite.Litestream/LitestreamServiceCollectionExtensions.cs:64— src/Rask.SQLite.Litestream/LitestreamServiceCollectionExtensions.cs:64-79 | src/Rask.SQLite.Snapshots/SqliteSnapshotsServiceCollectionExtensions.cs:68-83 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (9 lines × 2 locations) src/Rask.Core/Resources/browser/auth.ts:393— src/Rask.Core/Resources/browser/auth.ts:393 · src/Rask.Core/Resources/browser/auth.ts:423 — 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/Rask.Core/Resources/rask-calendar.ts:1159— src/Rask.Core/Resources/rask-calendar.ts:1159 · src/Rask.Core/Resources/rask-calendar.ts:1186 — 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) REDACTED:1001— REDACTED:1001 · REDACTED:1249 — 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/Rask.Server/Resources/rask.ts:1821— src/Rask.Server/Resources/rask.ts:1821 · src/Rask.Wasm/Resources/rask.wasm.ts:677 — 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.
Duplicated block (9 lines × 2 locations) src/Rask.Server/Resources/rask.ts:2014— src/Rask.Server/Resources/rask.ts:2014 · src/Rask.Wasm/Resources/rask.wasm.ts:751 — 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.
Duplicated block (7 lines × 2 locations) src/Rask.Core/Resources/rask-calendar.ts:1088— src/Rask.Core/Resources/rask-calendar.ts:1088 · src/Rask.Core/Resources/rask-calendar.ts:1130 — 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 (7 lines × 2 locations) src/Rask.Core/Resources/rask-carousel.ts:338— src/Rask.Core/Resources/rask-carousel.ts:338 · src/Rask.Core/Resources/rask-grow.ts:61 — 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.
Duplicated block (7 lines × 2 locations) src/Rask.Core/Resources/rask-list.ts:124— src/Rask.Core/Resources/rask-list.ts:124 · src/Rask.Core/Resources/rask-time-list.ts:52 — 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.
Duplicated block (7 lines × 2 locations) src/Rask.Core/Resources/rask-menu-keys.ts:249— src/Rask.Core/Resources/rask-menu-keys.ts:249 · src/Rask.Core/Resources/rask-overlay.ts:100 — 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.
Duplicated block (7 lines × 2 locations) src/Rask.Core/Resources/rask-morph.ts:233— src/Rask.Core/Resources/rask-morph.ts:233 · src/Rask.Core/Resources/rask-morph.ts:259 — 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.
BarePragmaDisable src/Rask.Core/Routing/RaskDefaultFallback.cs:9— #pragma warning disable CA2255 — the disable is closed again below, so its scope is not the problem; what it records is no reason: there is nothing on the directive line, and no ordinary comment attached to it either side. A suppression is a decision somebody made, and without the reason the next reader cannot tell a considered exception from an unexamined one, so it is never revisited and it outlives the code it was written for. Put the reason on the directive line — what makes this site legitimately different — or fix what the rule is pointing at and delete the pair. A rationale in the member's documentation comment does not clear this row and is not meant to: it explains the member to its callers, and the next person to touch the suppression is not reading it for that.
BarePragmaDisable tests/Rask.Benchmarks.VsBlazor/Components/AttributeHeavyElements.cs:120— #pragma warning disable ASP0006 — the disable is closed again below, so its scope is not the problem; what it records is no reason: there is nothing on the directive line, and no ordinary comment attached to it either side. A suppression is a decision somebody made, and without the reason the next reader cannot tell a considered exception from an unexamined one, so it is never revisited and it outlives the code it was written for. Put the reason on the directive line — what makes this site legitimately different — or fix what the rule is pointing at and delete the pair. A rationale in the member's documentation comment does not clear this row and is not meant to: it explains the member to its callers, and the next person to touch the suppression is not reading it for that.
BarePragmaDisable tests/Rask.Core.Tests/BuilderCallbackTests.cs:173— #pragma warning disable RASK044 — the disable is closed again below, so its scope is not the problem; what it records is no reason: there is nothing on the directive line, and no ordinary comment attached to it either side. A suppression is a decision somebody made, and without the reason the next reader cannot tell a considered exception from an unexamined one, so it is never revisited and it outlives the code it was written for. Put the reason on the directive line — what makes this site legitimately different — or fix what the rule is pointing at and delete the pair. A rationale in the member's documentation comment does not clear this row and is not meant to: it explains the member to its callers, and the next person to touch the suppression is not reading it for that.
BarePragmaDisable tests/Rask.Core.Tests/BuilderCallbackTests.cs:184— #pragma warning disable RASK044 — the disable is closed again below, so its scope is not the problem; what it records is no reason: there is nothing on the directive line, and no ordinary comment attached to it either side. A suppression is a decision somebody made, and without the reason the next reader cannot tell a considered exception from an unexamined one, so it is never revisited and it outlives the code it was written for. Put the reason on the directive line — what makes this site legitimately different — or fix what the rule is pointing at and delete the pair. A rationale in the member's documentation comment does not clear this row and is not meant to: it explains the member to its callers, and the next person to touch the suppression is not reading it for that.
FunctionTooLong: panel-client.installPanelClient REDACTED:54— FunctionTooLong — installPanelClient runs 128 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 28 over it, 1.28× 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.
FunctionTooLong: rask-morph.morphNode src/Rask.Core/Resources/rask-morph.ts:583— FunctionTooLong — morphNode runs 119 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 19 over it, 1.19× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: rask-dom.applyOps REDACTED:199— FunctionTooLong — applyOps runs 107 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 7 over it, 1.07× 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.
FunctionTooLong: overlay.installOverlay src/Rask.DevTools/Resources/host/overlay.ts:70— FunctionTooLong — installOverlay runs 101 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 1 over it, 1.01× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
Change coupling: RaskBrowserJsonContext.cs ↔ rask-api.ts src/Rask.Core/Browser/RaskBrowserJsonContext.cs:1— `src/Rask.Core/Browser/RaskBrowserJsonContext.cs` and `src/Rask.Core/Resources/rask-api.ts` change together 100% of the time (16 of the 16 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 16 shared commits counted here, the most recent 3 are `55d0aa8e` feat(core): add IWebAnimations over Element.animate() (#740) (at that commit the file was still `src/Rask.Core/Resources/rask-api.js`); `01f55ff3` feat(core): add IWebRtc — peer connections and data channels on every… (at that commit the file was still `src/Rask.Core/Resources/rask-api.js`); `b491b38a` feat(core): add ISpeechRecognition typed wrapper for the SpeechRecogn… (at that commit the file was still `src/Rask.Core/Resources/rask-api.js`) — run `git show` on any of them.
Change coupling: rask-hook-loader.ts ↔ rask-hooks.ts src/Rask.Core/Resources/rask-hook-loader.ts:1— `src/Rask.Core/Resources/rask-hook-loader.ts` and `src/Rask.Core/Resources/rask-hooks.ts` change together 74% of the time (14 of the 19 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) with no explicit dependency between them. They sit in the same directory, but in this ecosystem each file is its own module — a sibling reference still needs an import — so the missing import edge is real: the coupling runs through shared behaviour, not a declared dependency. If they duplicate structure, extract the common part into one unit; otherwise the coupling is hidden and worth breaking. You can check this without leaving the row: of the 14 shared commits counted here, the most recent 3 are `5f9b9cfe` fix(core): a confirmed press survives a redrawn button; one Escape cl…; `c4bf95e4` feat(core): a NavLink to a section of its page lights up while that s…; `0d6eb341` perf(ui): wip — the calendar and the date picker are drawn in the bro… — run `git show` on any of them.
Change coupling: ProjectGenerator.Server.cs ↔ TemplateCatalog.cs src/Rask.Cli/Scaffolding/ProjectGenerator.Server.cs:1— `src/Rask.Cli/Scaffolding/ProjectGenerator.Server.cs` and `src/Rask.Cli/Templates/TemplateCatalog.cs` change together 64% of the time (9 of the 14 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 9 shared commits counted here, the most recent 3 are `90b560f1` feat(cli): rask new scaffolds a test project with one passing test; `2f3fc33c` feat(cli): rask new scaffolds file storage, and --no-storage leaves i…; `42fec38c` feat(cli)!: languages are configured in Program.cs, not on the comman… — run `git show` on any of them.
Change coupling: rask-wasm-api.ts ↔ WasmHostBuilder.cs src/Rask.Wasm/Resources/rask-wasm-api.ts:1— `src/Rask.Wasm/Resources/rask-wasm-api.ts` and `src/Rask.Wasm/WasmHostBuilder.cs` change together 53% of the time (9 of the 17 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 9 shared commits counted here, the most recent 3 are `37b0cb40` feat(interop): Web Bluetooth — IBluetooth (WASM-only, Rask.Wasm.Brows… (at that commit the file was still `src/Rask.Wasm/Resources/rask-wasm-api.js`); `9085d427` feat(interop): WebHID — IHid (WASM-only, Rask.Wasm.Browser) (#195) (at that commit the file was still `src/Rask.Wasm/Resources/rask-wasm-api.js`); `db530a53` feat(interop): WebUSB — IUsb (WASM-only, Rask.Wasm.Browser) (#193) (at that commit the file was still `src/Rask.Wasm/Resources/rask-wasm-api.js`) — run `git show` on any of them.
Duplicated block (23 lines × 2) src/Rask.Core/AutoCallback.cs:97— src/Rask.Core/AutoCallback.cs:97-119 | src/Rask.Core/AutoCallback.cs:151-173 — 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 (23 lines × 2) src/Rask.Core/AutoCallback.cs:124— src/Rask.Core/AutoCallback.cs:124-146 | src/Rask.Core/AutoCallback.cs:178-200 — 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 (23 lines × 2) src/Rask.Core/AutoCallback.cs:238— src/Rask.Core/AutoCallback.cs:238-260 | src/Rask.Core/AutoCallback.cs:265-287 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. 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 (23 lines × 2) src/Rask.Core/Live/RaskPath.cs:16— src/Rask.Core/Live/RaskPath.cs:16-38 | src/Rask.Spa.Hosting/SpaPath.cs:20-42 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (12 lines × 2) src/Rask.Ui/UiCheckboxGroup.cs:120— src/Rask.Ui/UiCheckboxGroup.cs:120-131 | src/Rask.Ui/UiRadioGroup.cs:107-118 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `src/Rask.Ui/UiCheckboxGroup.cs:120` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (12 lines × 2) src/Rask.Dom.Tasks/RaskDomEmit.cs:49— src/Rask.Dom.Tasks/RaskDomEmit.cs:49-60 | src/Rask.Dom.Tasks/RaskWebEmit.cs:39-50 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `src/Rask.Dom.Tasks/RaskDomEmit.cs:49` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `src/Rask.Dom.Tasks/RaskDomEmit.cs:62` calls `OrderBy`, `Select`, `TaskItem` and `src/Rask.Dom.Tasks/RaskWebEmit.cs:52` does not — after which the two agree again for 3 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (12 lines × 2) src/Rask.Jobs/JobProcessor.cs:334— src/Rask.Jobs/JobProcessor.cs:334-345 | src/Rask.Outbox/OutboxProcessor.cs:166-177 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `src/Rask.Jobs/JobProcessor.cs:334` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `src/Rask.Jobs/JobProcessor.cs:333` calls `EnqueueDueRecurringAsync`, `ConfigureAwait` and `src/Rask.Outbox/OutboxProcessor.cs:165` does not — after which the two agree again for 4 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 (12 lines × 2) src/Rask.Batteries.Generators/EquatableArray.cs:46— src/Rask.Batteries.Generators/EquatableArray.cs:46-57 | src/Rask.Generators/EquatableArray.cs:43-54 — `src/Rask.Batteries.Generators/EquatableArray.cs` and `src/Rask.Generators/EquatableArray.cs` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 2 separate duplicated blocks between them, totalling at least 29 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (10 lines × 2) src/Rask.Generators.Shared/AggregateShape.cs:276— src/Rask.Generators.Shared/AggregateShape.cs:276-285 | src/Rask.Generators.Shared/GeneratedModelShape.cs:881-890 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (10 lines × 2) src/Rask.Generators/Analyzers/MissingKeyAnalyzer.cs:215— src/Rask.Generators/Analyzers/MissingKeyAnalyzer.cs:215-224 | src/Rask.Generators/Analyzers/RedundantStateHasChangedAnalyzer.cs:174-183 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (10 lines × 2) src/Rask.Jobs/JobsOptions.cs:92— src/Rask.Jobs/JobsOptions.cs:92-101 | src/Rask.Mail/MailOptions.cs:87-96 — before extracting anything, compare `src/Rask.Jobs/JobsOptions.cs` and `src/Rask.Mail/MailOptions.cs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 69 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (10 lines × 2) src/Rask.Site/Features/UiDocs/Examples/ContextExample.cs:15— src/Rask.Site/Features/UiDocs/Examples/ContextExample.cs:15-24 | src/Rask.Site/Features/UiDocs/Examples/DropdownExample.cs:15-24 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `src/Rask.Site/Features/UiDocs/Examples/ContextExample.cs:15` 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.
AC6 · Visual & motion safety· Focus outline removed in CSS without a · ×3
Focus outline removed in CSS without a :focus replacement src/Rask.Ui/Styles/ui.css:1124— `:where([data-ui-date-picker], [data-ui-time-picker], [data-ui-color-picker-trigger], [data-ui-pillbox-trigger]) :where(input, [role="spinbutton"], [contenteditable]):not([data-ui-control]):focus-visible` 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/Rask.Ui/Styles/ui.css:1311— `[data-ui-editor] [data-slot="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 src/Rask.Ui/Styles/ui.css:1316— `[data-ui-editor] [data-slot="content"] :focus-visible` 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.
Duplicated block (15 lines × 2) src/Rask.Dashboard/Pages/CachePage.cs:42— src/Rask.Dashboard/Pages/CachePage.cs:42-56 | src/Rask.Dashboard/Pages/StoragePage.cs:42-56 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `src/Rask.Dashboard/Pages/CachePage.cs:42` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (15 lines × 2) src/Rask.Jobs/JobMetrics.cs:45— src/Rask.Jobs/JobMetrics.cs:45-59 | src/Rask.Outbox/OutboxMetrics.cs:45-59 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `src/Rask.Jobs/JobMetrics.cs:45` 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 (15 lines × 2) src/Rask.Generators/RoutesGenerator.Factories.cs:211— src/Rask.Generators/RoutesGenerator.Factories.cs:211-225 | src/Rask.Generators/RoutesGenerator.Factories.cs:401-416 — 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/Rask.Generators/RoutesGenerator.Factories.cs:211` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
Duplicated block (11 lines × 2 locations) src/Rask.Core/Resources/rask-calendar.ts:1005— src/Rask.Core/Resources/rask-calendar.ts:1005 · src/Rask.Core/Resources/rask-color.ts:558 — 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.
Duplicated block (11 lines × 2 locations) REDACTED:290— REDACTED:290 · REDACTED:304 — 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 (11 lines × 2 locations) REDACTED:519— REDACTED:519 · REDACTED:702 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
R10 · Code Duplication· Duplicated block with local edits (10 matched lines × 2 locations) · ×3
Duplicated block with local edits (10 matched lines × 2 locations) src/Rask.Core/Resources/rask-otp.ts:102— src/Rask.Core/Resources/rask-otp.ts:102 · src/Rask.Core/Resources/rask-otp.ts:169 — the two spans are one implementation copied and then locally edited — 72 tokens are still identical, in the same order in both spans, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one.
Duplicated block with local edits (10 matched lines × 2 locations) REDACTED:410— REDACTED:410 · src/Rask.Core/Resources/rask-time-list.ts:136 — the two spans are one implementation copied and then locally edited — 61 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one.
Duplicated block with local edits (10 matched lines × 2 locations) src/Rask.Core/Resources/rask-toggle.ts:142— src/Rask.Core/Resources/rask-toggle.ts:142 · src/Rask.Core/Resources/rask-toggle.ts:165 — the two spans are one implementation copied and then locally edited — 68 tokens are still identical, in the same order in both spans, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one.
X18 · Disposal-pattern correctness· Owned disposable field is never released · ×3
Owned disposable field is never released src/Rask.Core/Live/LiveSessionBase.cs:40— `LiveSessionBase` implements `IDisposable` — so it has told every caller it holds something worth releasing — and it constructs `_htmlBuffers` itself (line 40), which makes that instance its own. But `_htmlBuffers` is named in none of the methods the disposal search covered: `Dispose` (line 46), `Dispose` (line 54), `Dispose` (line 46), `Dispose` (line 54) — 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` (`_htmlBuffers?.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/Rask.Pdf/ChromiumPrinter.cs:13— `ChromiumPrinter` implements `IDisposable` — so it has told every caller it holds something worth releasing — and it constructs `_turns` itself (line 13), which makes that instance its own. But `_turns` is named in none of the methods the disposal search covered: `DisposeAsync` (line 66) — 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` (`_turns?.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/Rask.Wasm/WasmLiveSession.cs:30— `WasmLiveSession` implements `IDisposable` — so it has told every caller it holds something worth releasing — and it constructs `_inScopeRender` itself (line 30), which makes that instance its own. But `_inScopeRender` is named in none of the methods the disposal search covered: `Dispose` (line 98) — 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` (`_inScopeRender?.Dispose();`), or, if it truly does not need releasing, drop `IDisposable` from the type so the claim and the behaviour agree.
D10 · Test Quality· Depends on a live external host · ×2
Depends on a live external host: Markdown_rules_the_heading_list_and_the_link_panel_shape_the_document tests/Rask.Site.E2E.Tests/UiKitEditorTests.cs:73— This test fetches `https://rask.sh` while it runs, so it passes only while rask.sh is up, reachable from the build machine, and still serving what this test expects — none of which this repository controls. It goes red on an aeroplane, behind a corporate proxy, in a sealed CI network, and on the day the third party edits that document. Serve the payload from the repository instead (a checked-in fixture file), or stub the transport; if the point really is to check the remote contract, move it out of the unit suite into a separately-scheduled integration job that is allowed to fail for someone else's reasons.
Depends on a live external host: A_static_member_is_on_the_class_and_reached_from_the_window tests/Rask.Web.Tests/WebApiTests.cs:172— This test fetches `https://rask.sh` while it runs, so it passes only while rask.sh is up, reachable from the build machine, and still serving what this test expects — none of which this repository controls. It goes red on an aeroplane, behind a corporate proxy, in a sealed CI network, and on the day the third party edits that document. Serve the payload from the repository instead (a checked-in fixture file), or stub the transport; if the point really is to check the remote contract, move it out of the unit suite into a separately-scheduled integration job that is allowed to fail for someone else's reasons.
MethodTooLong: ParityMenu.MeasureExample scripts/flux/Flux/Commands/ParityMenu.cs:554— MethodTooLong — MeasureExample runs 162 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 62 over it, 1.62× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: ParityModal.Run scripts/flux/Flux/Commands/ParityModal.cs:155— MethodTooLong — Run runs 106 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 6 over it, 1.06× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
D4 · Code Duplication· Members sharing a duplicated core (4 members, 50+ identical tokens) · ×2
Members sharing a duplicated core (4 members, 50+ identical tokens) src/Rask.Generators/ComponentFactoryGenerator.cs:111— src/Rask.Generators/ComponentFactoryGenerator.cs:111-123 | src/Rask.Generators/ComponentScopedCssGenerator.cs:50-68 | src/Rask.Generators/ComponentScopedJsGenerator.cs:98-141 | src/Rask.Generators/ScopedScripts/ScopedScriptCallsGenerator.cs:45-97 — These 4 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 4 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 4 times.
Members sharing a duplicated core (4 members, 50+ identical tokens) src/Rask.Site/Features/UiDocs/Examples/SidebarCollapsibleExample.cs:48— src/Rask.Site/Features/UiDocs/Examples/SidebarCollapsibleExample.cs:48-55 | src/Rask.Site/Features/UiDocs/Examples/SidebarInsetExample.cs:48-55 | src/Rask.Site/Features/UiDocs/Examples/SidebarLayoutExample.cs:49-56 | src/Rask.Site/Features/UiDocs/Examples/SidebarSecondaryHeaderExample.cs:49-64 — These 4 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 4 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 4 times.
Duplicated block (18 lines × 2) src/Rask.Ui/UiCheckbox.cs:78— src/Rask.Ui/UiCheckbox.cs:78-95 | src/Rask.Ui/UiSwitch.cs:51-68 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (18 lines × 2) src/Rask.Jobs/JobConfiguration.cs:14— src/Rask.Jobs/JobConfiguration.cs:14-31 | src/Rask.Outbox/OutboxMessageConfiguration.cs:13-30 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. 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. Note first that the copies are not typed on the same thing: the declarations holding them bind `builder` to `EntityTypeBuilder<Job>` in one and `EntityTypeBuilder<OutboxMessage>` in another, and the duplicated lines use it. The extracted unit therefore needs a parameter type that fits BOTH — their common supertype where they have one, or a new abstraction over them where they do not — and settling that is the step that comes BEFORE the extraction above. Where the two types are deliberately unrelated, the duplication is the price of that separation and the honest resolution is to record the decision rather than to extract. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `src/Rask.Jobs/JobConfiguration.cs:12` calls `ThrowIfNull` and `src/Rask.Outbox/OutboxMessageConfiguration.cs:11` does not — after which the two agree again for 4 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 (9 lines × 2) src/Rask.Generators.Shared/WireShape.cs:365— src/Rask.Generators.Shared/WireShape.cs:365-373 | src/Rask.Generators.Shared/WireShape.cs:491-499 — 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/Rask.Generators.Shared/WireShape.cs:365` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The `return` at the foot of the matched lines is the enclosing body's own terminal exit, not an early one: it moves with them unchanged, and each site calls the extracted unit from the position that `return` occupied — no decision has to be handed back and re-acted on.
Duplicated block (9 lines × 2) src/Rask.Ui/UiMenuCheckbox.cs:62— src/Rask.Ui/UiMenuCheckbox.cs:62-70 | src/Rask.Ui/UiMenuRadio.cs:51-59 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `src/Rask.Ui/UiMenuCheckbox.cs:62` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (14 lines × 2) src/Rask.Auth.Api/AccountService.cs:387— src/Rask.Auth.Api/AccountService.cs:387-400 | src/Rask.Auth.Api/AccountService.cs:438-451 — 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/Rask.Auth.Api/AccountService.cs:387` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (14 lines × 2) src/Rask.DevTools/Panel/DevToolsErrorsTab.cs:62— src/Rask.DevTools/Panel/DevToolsErrorsTab.cs:62-76 | src/Rask.DevTools/Panel/DevToolsTabs.cs:58-71 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (11 lines × 2) src/Rask.Jobs/JobMetrics.cs:26— src/Rask.Jobs/JobMetrics.cs:26-36 | src/Rask.Outbox/OutboxMetrics.cs:26-36 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (11 lines × 2) src/Rask.Jobs/JobProcessor.cs:790— src/Rask.Jobs/JobProcessor.cs:790-800 | src/Rask.Mail/MailProcessor.cs:367-377 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (5 lines × 3) src/Rask.Dashboard/Pages/CachePage.cs:43— src/Rask.Dashboard/Pages/CachePage.cs:43-47 | src/Rask.Dashboard/Pages/QueuePage.cs:57-61 | src/Rask.Dashboard/Pages/StoragePage.cs:43-47 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from all 3 call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `src/Rask.Dashboard/Pages/CachePage.cs:43` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (5 lines × 3) src/Rask.Generators/ComponentScopedCssGenerator.cs:51— src/Rask.Generators/ComponentScopedCssGenerator.cs:51-55 | src/Rask.Generators/ComponentScopedJsGenerator.cs:99-103 | src/Rask.Generators/ScopedScripts/ScopedScriptCallsGenerator.cs:46-50 — before extracting anything, compare `src/Rask.Generators/ComponentScopedCssGenerator.cs` and `src/Rask.Generators/ComponentScopedJsGenerator.cs` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 86 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/Rask.Generators/ComponentScopedCssGenerator.cs:51` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (6 lines × 4) src/Rask.Generators/ComponentFactoryGenerator.cs:111— src/Rask.Generators/ComponentFactoryGenerator.cs:111-116 | src/Rask.Generators/ComponentScopedCssGenerator.cs:50-56 | src/Rask.Generators/ComponentScopedJsGenerator.cs:98-104 | src/Rask.Generators/ScopedScripts/ScopedScriptCallsGenerator.cs:45-51 — before extracting anything, compare `src/Rask.Generators/ComponentScopedCssGenerator.cs` and `src/Rask.Generators/ComponentScopedJsGenerator.cs` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 86 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/Rask.Generators/ComponentFactoryGenerator.cs:111` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (6 lines × 4) src/Rask.Site/Features/UiDocs/Examples/SidebarCollapsibleExample.cs:49— src/Rask.Site/Features/UiDocs/Examples/SidebarCollapsibleExample.cs:49-54 | src/Rask.Site/Features/UiDocs/Examples/SidebarInsetExample.cs:49-54 | src/Rask.Site/Features/UiDocs/Examples/SidebarLayoutExample.cs:50-55 | src/Rask.Site/Features/UiDocs/Examples/SidebarSecondaryHeaderExample.cs:51-56 — before extracting anything, compare `src/Rask.Site/Features/UiDocs/Examples/SidebarCollapsibleExample.cs` and `src/Rask.Site/Features/UiDocs/Examples/SidebarInsetExample.cs` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 49 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `src/Rask.Site/Features/UiDocs/Examples/SidebarSecondaryHeaderExample.cs:49` calls `Class` and `src/Rask.Site/Features/UiDocs/Examples/SidebarCollapsibleExample.cs:47` does not — after which the two agree again for 3 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (9 lines × 3) src/Rask.Site/Features/UiDocs/Examples/HeaderInsetExample.cs:38— src/Rask.Site/Features/UiDocs/Examples/HeaderInsetExample.cs:38-46 | src/Rask.Site/Features/UiDocs/Examples/HeaderLayoutExample.cs:38-46 | src/Rask.Site/Features/UiDocs/Examples/HeaderSecondarySidebarExample.cs:55-63 — before extracting anything, compare `src/Rask.Site/Features/UiDocs/Examples/HeaderInsetExample.cs` and `src/Rask.Site/Features/UiDocs/Examples/HeaderLayoutExample.cs` as WHOLE FILES: this scan already matched 8 separate duplicated blocks between them, totalling at least 70 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/Rask.Site/Features/UiDocs/Examples/HeaderInsetExample.cs:38` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (9 lines × 3) src/Rask.Site/Features/UiDocs/Examples/SidebarCollapsibleExample.cs:7— src/Rask.Site/Features/UiDocs/Examples/SidebarCollapsibleExample.cs:7-15 | src/Rask.Site/Features/UiDocs/Examples/SidebarLayoutExample.cs:7-15 | src/Rask.Site/Features/UiDocs/Examples/SidebarSecondaryHeaderExample.cs:7-15 — before extracting anything, compare `src/Rask.Site/Features/UiDocs/Examples/SidebarCollapsibleExample.cs` and `src/Rask.Site/Features/UiDocs/Examples/SidebarLayoutExample.cs` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 50 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Low cohesion: LiveRenderContext (LCOM4 5) src/Rask.Core/Live/LiveRenderContext.cs:10— LiveRenderContext's methods fall into 5 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 5 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
Low cohesion: Job (LCOM4 4) src/Rask.Jobs/Job.cs:14— Job's methods fall into 4 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 4 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
P8 · Schema migrations· Schema created with EnsureCreated() outside the migrations · ×2
Schema created with EnsureCreated() outside the migrations src/Rask.Data/SchemaStep.cs:11— This repository evolves its schema with versioned migrations, but `EnsureCreated()` here builds a schema straight from the model instead — with no migrations-history row, so a database it creates can't be upgraded by `Migrate()` afterwards and the two paths can disagree about the shape. Apply the migrations here (`Migrate()` / a migrations bundle) rather than creating the schema.
Schema created with EnsureCreated() outside the migrations src/Rask.Data/SchemaStep.cs:21— This repository evolves its schema with versioned migrations, but `EnsureCreated()` here builds a schema straight from the model instead — with no migrations-history row, so a database it creates can't be upgraded by `Migrate()` afterwards and the two paths can disagree about the shape. Apply the migrations here (`Migrate()` / a migrations bundle) rather than creating the schema.
P8 · Schema migrations· Schema created by a CREATE TABLE statement outside the migrations · ×2
Schema created by a CREATE TABLE statement outside the migrations REDACTED:328— This repository evolves its schema with versioned migrations, but a CREATE TABLE statement here creates schema at runtime outside them — structure no migration created and the migration history does not describe, so a later migration that touches it fails on a fresh environment and the environments drift apart. Create it in a migration instead.
Schema created by a CREATE TABLE statement outside the migrations src/Rask.SQLite.Litestream/LitestreamVerifier.cs:19— This repository evolves its schema with versioned migrations, but a CREATE TABLE statement here creates schema at runtime outside them — structure no migration created and the migration history does not describe, so a later migration that touches it fails on a fresh environment and the environments drift apart. Create it in a migration instead.
R10 · Code Duplication· Duplicated block with local edits (12 matched lines × 2 locations) · ×2
Duplicated block with local edits (12 matched lines × 2 locations) src/Rask.Core/Resources/rask-dom-path.ts:70— src/Rask.Core/Resources/rask-dom-path.ts:70 · REDACTED:64 — the two spans are one implementation copied and then locally edited — 83 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one.
Duplicated block with local edits (12 matched lines × 2 locations) src/Rask.Core/Resources/rask-list.ts:153— src/Rask.Core/Resources/rask-list.ts:153 · src/Rask.Core/Resources/rask-menu.ts:59 — the two spans are one implementation copied and then locally edited — 75 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one.
Duplicated block (8 lines × 2 locations) REDACTED:904— REDACTED:904 · src/Rask.Core/Resources/rask-overlay.ts:257 — 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.
Duplicated block (8 lines × 2 locations) src/Rask.Server/Resources/rask.ts:1898— src/Rask.Server/Resources/rask.ts:1898 · src/Rask.Wasm/Resources/rask.wasm.ts:697 — 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.
R10 · Code Duplication· Duplicated block with local edits (8 matched lines × 2 locations) · ×2
Duplicated block with local edits (8 matched lines × 2 locations) src/Rask.Core/Resources/rask-menu.ts:59— src/Rask.Core/Resources/rask-menu.ts:59 · src/Rask.Core/Resources/rask-time-list.ts:71 — the two spans are one implementation copied and then locally edited — 53 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one.
Duplicated block with local edits (8 matched lines × 2 locations) src/Rask.Core/Resources/rask-persist.ts:71— src/Rask.Core/Resources/rask-persist.ts:71 · src/Rask.Core/Resources/rask-requires.ts:33 — the two spans are one implementation copied and then locally edited — 59 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one.
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/Rask.Cli/Dev/DevStatusServer.cs:89— `probe` is a `TcpListener`, which implements `IDisposable`, and it is created here (line 89). Every use of it in `TryStart` 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 probe = …;`), 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 scripts/flux/Flux/Commands/ParityPhone.cs:106— `probe` is a `TcpListener`, which implements `IDisposable`, and it is created here (line 106). Every use of it in `FreePort` 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 probe = …;`), which releases it at the end of the scope on every path including a throw.
AC7 · A11y enforcement· Accessibility enforcement below the top rung · ×1
Accessibility enforcement below the top rung — No accessibility enforcement found — no automated accessibility check runs over the HTML your app renders. Assert the accessibility invariants over that HTML in the test suite you already have (parse the output and assert, or drive a browser), and gate that test in CI so a regression blocks the merge. What was searched, so you can tell an absence from a miss: the 7 markup file(s) this pass actually assessed, the linter configuration checked in beside them, and this repository's test and CI files — matched by name against the accessibility checkers this dimension carries. An audit run outside the repository, a hosted scanner, or a check whose name is not one of those, is not seen here.
rask-morph.morphNode (cyclomatic 97) src/Rask.Core/Resources/rask-morph.ts:583— rask-morph.morphNode has cyclomatic complexity 97 (threshold 15). Of this number, 94 points are the body's own statements and 3 belong to 2 function items inside it that branch. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
panel-client.installPanelClient (cyclomatic 52) REDACTED:54— panel-client.installPanelClient has cyclomatic complexity 52 (threshold 15). Most of this is not in the body itself: 2 of the 52 points are its own statements and the rest belongs to 10 function items inside it that branch (a function literal at line 201, syncFlash, a function literal at line 66, …). 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.
rask-dom.applyOps (cyclomatic 45) REDACTED:199— rask-dom.applyOps has cyclomatic complexity 45 (threshold 15). Of this number, 43 points are the body's own statements and 2 belong to one function item inside it that branches. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
rask-color.draw (cyclomatic 41) src/Rask.Core/Resources/rask-color.ts:314— rask-color.draw has cyclomatic complexity 41 (threshold 15). Of this number, 38 points are the body's own statements and 3 belong to one function literal inside it that branches. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
rask-overlay.installModal (cyclomatic 40) src/Rask.Core/Resources/rask-overlay.ts:255— rask-overlay.installModal has cyclomatic complexity 40 (threshold 15). Most of this is not in the body itself: 2 of the 40 points are its own statements and the rest belongs to 8 function literals inside it that branch (lines 322, 293, 309, …). 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.
affected_projects.main (cyclomatic 38) scripts/lib/affected_projects.py:139— affected_projects.main has cyclomatic complexity 38 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
OpenList.MeasureOpen (cyclomatic 37) scripts/flux/Flux/Lib/OpenList.cs:308— OpenList.MeasureOpen has cyclomatic complexity 37 (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.
ParityComparer.CompareTree (cyclomatic 37) scripts/flux/Flux/Lib/ParityComparer.cs:310— ParityComparer.CompareTree has cyclomatic complexity 37 (threshold 15). Of this number, 30 points are the body's own statements and 7 belong to 5 function items inside it that branch. To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
OpenList.Run (cyclomatic 36) scripts/flux/Flux/Lib/OpenList.cs:39— OpenList.Run has cyclomatic complexity 36 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
(anonymous) (cyclomatic 36) src/Rask.Pdf/PrintTables.js:6— (anonymous) has cyclomatic complexity 36 (threshold 15). Most of this is not in the body itself: 5 of the 36 points are its own statements and the rest belongs to 20 function items inside it that branch (fixColumns, cut, a function literal at line 123, …). 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.
ParityMenu.Run (cyclomatic 35) scripts/flux/Flux/Commands/ParityMenu.cs:307— ParityMenu.Run has cyclomatic complexity 35 (threshold 15). Of this number, 34 points are the body's own statements and 1 belongs to one function literal inside it that branches. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
Sync.Run (cyclomatic 35) scripts/flux/Flux/Commands/Sync.cs:54— Sync.Run has cyclomatic complexity 35 (threshold 15). Of this number, 34 points are the body's own statements and 1 belongs to one function literal inside it that branches. To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
ParityMenu.MeasureExample (cyclomatic 34) scripts/flux/Flux/Commands/ParityMenu.cs:554— ParityMenu.MeasureExample has cyclomatic complexity 34 (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.
ParityModal.Run (cyclomatic 33) scripts/flux/Flux/Commands/ParityModal.cs:155— ParityModal.Run has cyclomatic complexity 33 (threshold 15). Of this number, 29 points are the body's own statements and 4 belong to 2 function items inside it that branch. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
ParityPopover.Run (cyclomatic 33) scripts/flux/Flux/Commands/ParityPopover.cs:147— ParityPopover.Run has cyclomatic complexity 33 (threshold 15). Of this number, 31 points are the body's own statements and 2 belong to 2 function literals inside it that branch. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
rask-calendar.paintDay (cyclomatic 33) src/Rask.Core/Resources/rask-calendar.ts:447— rask-calendar.paintDay has cyclomatic complexity 33 (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.
UiChartFormat.Pattern (cyclomatic 32) src/Rask.Ui/UiChartFormat.cs:188— UiChartFormat.Pattern has cyclomatic complexity 32 (threshold 15). To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Where every arm is uniform — the same kind of value, with no behaviour of its own — a table keyed by the case is the shorter form; wherever the arms carry different data or different behaviour, keep them as cases, because collapsing those trades an explicit, reviewable set of cases for nothing.
ParityMenu.CompareExample (cyclomatic 32) scripts/flux/Flux/Commands/ParityMenu.cs:913— ParityMenu.CompareExample has cyclomatic complexity 32 (threshold 15). Of this number, 28 points are the body's own statements and 4 belong to 3 function literals inside it that branch. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
rask-menu-keys.cursorKey (cyclomatic 31) src/Rask.Core/Resources/rask-menu-keys.ts:78— rask-menu-keys.cursorKey has cyclomatic complexity 31 (threshold 15). Of this number, 29 points are the body's own statements and 2 belong to one function literal inside it that branches. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
DeclarationReader.ReadToken (cyclomatic 30) src/Rask.Generators/ScopedScripts/DeclarationReader.cs:87— DeclarationReader.ReadToken has cyclomatic complexity 30 (threshold 15). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
ui-phone.handle (cyclomatic 30) src/Rask.Ui/Resources/phone/ui-phone.ts:397— ui-phone.handle has cyclomatic complexity 30 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
rask-field.maskMoney (cyclomatic 28) src/Rask.Core/Resources/rask-field.ts:67— rask-field.maskMoney has cyclomatic complexity 28 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
rask-overlay.installPopoverFocus (cyclomatic 28) src/Rask.Core/Resources/rask-overlay.ts:60— rask-overlay.installPopoverFocus has cyclomatic complexity 28 (threshold 15). Most of this is not in the body itself: 1 of the 28 points is its own statement and the rest belongs to 3 function literals inside it that branch (lines 96, 80, 61). 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.
Parser.ReadClassMember (cyclomatic 26) src/Rask.Generators/ScopedScripts/DeclarationReader.cs:386— Parser.ReadClassMember has cyclomatic complexity 26 (threshold 15). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
Refresh.describe (cyclomatic 26) scripts/mdn/refresh.py:473— Refresh.describe has cyclomatic complexity 26 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
rask.onFrame (cyclomatic 26) src/Rask.Server/Resources/rask.ts:593— rask.onFrame has cyclomatic complexity 26 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
Component.TryFindHandler (cyclomatic 25) src/Rask.Core/Component.StaleEvents.cs:77— Component.TryFindHandler has cyclomatic complexity 25 (threshold 15). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
DomValueTypes.Map (cyclomatic 25) src/Rask.Dom.Tasks/DomValueTypes.cs:194— DomValueTypes.Map has cyclomatic complexity 25 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
overlay.installOverlay (cyclomatic 25) src/Rask.DevTools/Resources/host/overlay.ts:70— overlay.installOverlay has cyclomatic complexity 25 (threshold 15). Most of this is not in the body itself: 6 of the 25 points are its own statements and the rest belongs to 7 function items inside it that branch (pointAt, draw, schedule, …). 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.
rask-api.raskWebData (cyclomatic 24) src/Rask.Core/Resources/rask-api.ts:120— rask-api.raskWebData 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.
ContentSniffer.IsoMedia (cyclomatic 23) src/Rask.Storage/Upload/ContentSniffer.cs:215— ContentSniffer.IsoMedia has cyclomatic complexity 23 (threshold 15). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
ParityColorPicker.WalkBoth (cyclomatic 23) scripts/flux/Flux/Commands/ParityColorPicker.cs:287— ParityColorPicker.WalkBoth has cyclomatic complexity 23 (threshold 15). Of this number, 20 points are the body's own statements and 3 belong to 2 function literals inside it that branch. To reduce it, 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.
ParityComparer.CompareLook (cyclomatic 23) scripts/flux/Flux/Lib/ParityComparer.cs:399— ParityComparer.CompareLook has cyclomatic complexity 23 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
top-level statements (cyclomatic 23) scripts/tools/RaskRename/Program.cs:15— top-level statements has cyclomatic complexity 23 (threshold 15). Of this number, 13 points are the body's own statements and 10 belong to 5 function items inside it that branch. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
Refresh.read_events (cyclomatic 23) scripts/mdn/refresh.py:357— Refresh.read_events has cyclomatic complexity 23 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
Walker.Walk (cyclomatic 22) scripts/flux/Flux/Commands/ParityCarousel.cs:142— Walker.Walk has cyclomatic complexity 22 (threshold 15). Of this number, 20 points are the body's own statements and 2 belong to 2 function literals inside it that branch. To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
ParityTooltip.Run (cyclomatic 22) scripts/flux/Flux/Commands/ParityTooltip.cs:184— ParityTooltip.Run has cyclomatic complexity 22 (threshold 15). Of this number, 20 points are the body's own statements and 2 belong to one function literal inside it that branches. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
rask.applyFullReply::commit (cyclomatic 22) src/Rask.Server/Resources/rask.ts:1724— rask.applyFullReply::commit has cyclomatic complexity 22 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
DomValueTypes.Named (cyclomatic 21) src/Rask.Dom.Tasks/DomValueTypes.cs:348— DomValueTypes.Named has cyclomatic complexity 21 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
ParityFocus.Run (cyclomatic 21) scripts/flux/Flux/Commands/ParityFocus.cs:171— ParityFocus.Run has cyclomatic complexity 21 (threshold 15). Of this number, 16 points are the body's own statements and 5 belong to 3 function literals inside it that branch. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
ParityMenu.CompareTree (cyclomatic 21) scripts/flux/Flux/Commands/ParityMenu.cs:1075— ParityMenu.CompareTree has cyclomatic complexity 21 (threshold 15). Of this number, 20 points are the body's own statements and 1 belongs to one function item inside it that branches. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
Refresh.Unlisted (cyclomatic 21) scripts/flux/Flux/Commands/Refresh.cs:204— Refresh.Unlisted has cyclomatic complexity 21 (threshold 15). Of this number, 20 points are the body's own statements and 1 belongs to one function literal inside it that branches. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
Js.Num (cyclomatic 21) scripts/flux/Flux/Lib/Js.cs:24— Js.Num has cyclomatic complexity 21 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
Refresh.members_of (cyclomatic 21) scripts/mdn/refresh.py:429— Refresh.members_of 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.
Refresh.extras_of (cyclomatic 21) scripts/mdn/refresh.py:532— Refresh.extras_of 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.
rask-calendar.formatDay (cyclomatic 21) src/Rask.Core/Resources/rask-calendar.ts:177— rask-calendar.formatDay has cyclomatic complexity 21 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
rask-calendar.drawTimes (cyclomatic 21) src/Rask.Core/Resources/rask-calendar.ts:886— rask-calendar.drawTimes has cyclomatic complexity 21 (threshold 15). Most of this is not in the body itself: 5 of the 21 points are its own statements and the rest belongs to 4 function literals inside it that branch (lines 898, 913, 890, …). 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.
ParityToast.CompareScreens (cyclomatic 20) scripts/flux/Flux/Commands/ParityToast.cs:537— ParityToast.CompareScreens has cyclomatic complexity 20 (threshold 15). Of this number, 19 points are the body's own statements and 1 belongs to one function literal inside it that branches. To reduce it, 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.
rask-deverror.showDevError (cyclomatic 20) src/Rask.Core/Resources/rask-deverror.ts:232— rask-deverror.showDevError has cyclomatic complexity 20 (threshold 15). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
rask-head-assets.createInvokeGate.trackHeadAsset (cyclomatic 20) src/Rask.Core/Resources/rask-head-assets.ts:53— rask-head-assets.createInvokeGate.trackHeadAsset has cyclomatic complexity 20 (threshold 15). Of this number, 17 points are the body's own statements and 3 belong to one function item inside it that branches. To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
LiveSessionBase.TryWriteDiff (cyclomatic 19) src/Rask.Core/Live/LiveSessionBase.cs:1028— LiveSessionBase.TryWriteDiff has cyclomatic complexity 19 (threshold 15). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
DomValueTypes.Record (cyclomatic 19) src/Rask.Dom.Tasks/DomValueTypes.cs:771— DomValueTypes.Record has cyclomatic complexity 19 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
HeroCode.Highlight (cyclomatic 19) src/Rask.Site/Features/Home/HeroCode.cs:137— HeroCode.Highlight has cyclomatic complexity 19 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
Parity.Run (cyclomatic 19) scripts/flux/Flux/Commands/Parity.cs:61— Parity.Run has cyclomatic complexity 19 (threshold 15). Of this number, 17 points are the body's own statements and 2 belong to one function literal inside it that branches. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
Parity.Report (cyclomatic 19) scripts/flux/Flux/Commands/Parity.cs:168— Parity.Report has cyclomatic complexity 19 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
ParityDate.Run (cyclomatic 19) scripts/flux/Flux/Commands/ParityDate.cs:67— ParityDate.Run has cyclomatic complexity 19 (threshold 15). Of this number, 17 points are the body's own statements and 2 belong to one function literal inside it that branches. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
OpenList.CompareTree (cyclomatic 19) scripts/flux/Flux/Lib/OpenList.cs:594— OpenList.CompareTree has cyclomatic complexity 19 (threshold 15). Of this number, 18 points are the body's own statements and 1 belongs to one function item inside it that branches. To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
rask-events.domEvents.forEach() (cyclomatic 19) src/Rask.Core/Resources/rask-events.ts:40— rask-events.domEvents.forEach() has cyclomatic complexity 19 (threshold 15). Most of this is not in the body itself: 3 of the 19 points are its own statements and the rest belongs to one function literal inside it that branches (line 44). 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.
rask-list.place (cyclomatic 19) src/Rask.Core/Resources/rask-list.ts:247— rask-list.place has cyclomatic complexity 19 (threshold 15). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
ExpressionAccessor.TryEvaluate (cyclomatic 18) src/Rask.Core/Forms/ExpressionAccessor.cs:158— ExpressionAccessor.TryEvaluate has cyclomatic complexity 18 (threshold 15). To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Where every arm is uniform — the same kind of value, with no behaviour of its own — a table keyed by the case is the shorter form; wherever the arms carry different data or different behaviour, keep them as cases, because collapsing those trades an explicit, reviewable set of cases for nothing.
FormData.FromJson (cyclomatic 18) src/Rask.Core/Live/FormData.cs:48— FormData.FromJson has cyclomatic complexity 18 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
SafeFileName.Clean (cyclomatic 18) src/Rask.Storage/Upload/SafeFileName.cs:33— SafeFileName.Clean has cyclomatic complexity 18 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
ClearPlacement.Run (cyclomatic 18) scripts/flux/Flux/Commands/ClearPlacement.cs:65— ClearPlacement.Run has cyclomatic complexity 18 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
ParityChart.Run (cyclomatic 18) scripts/flux/Flux/Commands/ParityChart.cs:137— ParityChart.Run has cyclomatic complexity 18 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
ParityCommand.Run (cyclomatic 18) scripts/flux/Flux/Commands/ParityCommand.cs:87— ParityCommand.Run has cyclomatic complexity 18 (threshold 15). Of this number, 17 points are the body's own statements and 1 belongs to one function literal inside it that branches. To reduce it, 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.
Placement.Landings (cyclomatic 18) scripts/flux/Flux/Lib/Placement.cs:101— Placement.Landings has cyclomatic complexity 18 (threshold 15). Of this number, 16 points are the body's own statements and 2 belong to one function literal inside it that branches. To reduce it, 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.
Refresh.wanted (cyclomatic 18) scripts/mdn/refresh.py:394— Refresh.wanted has cyclomatic complexity 18 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
Refresh.reflected_names (cyclomatic 18) scripts/mdn/refresh.py:568— Refresh.reflected_names has cyclomatic complexity 18 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
rask-datetime.formatTime (cyclomatic 18) src/Rask.Core/Resources/rask-datetime.ts:52— rask-datetime.formatTime has cyclomatic complexity 18 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
rask-calendar.drawPresets (cyclomatic 18) src/Rask.Core/Resources/rask-calendar.ts:729— rask-calendar.drawPresets has cyclomatic complexity 18 (threshold 15). Of this number, 12 points are the body's own statements and 6 belong to one function literal inside it that branches. To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
rask-morph.raskNotePendingFormState (cyclomatic 18) src/Rask.Core/Resources/rask-morph.ts:421— rask-morph.raskNotePendingFormState has cyclomatic complexity 18 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
rask-dom.syncFormProperty (cyclomatic 18) REDACTED:129— rask-dom.syncFormProperty has cyclomatic complexity 18 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
rask-list.picked (cyclomatic 18) src/Rask.Core/Resources/rask-list.ts:562— rask-list.picked has cyclomatic complexity 18 (threshold 15). Of this number, 14 points are the body's own statements and 4 belong to one function literal inside it that branches. To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
GeneratedModelShape.EntitiesFor (cyclomatic 17) src/Rask.Generators.Shared/GeneratedModelShape.cs:124— GeneratedModelShape.EntitiesFor has cyclomatic complexity 17 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
ModelGraphWalker.StepInto (cyclomatic 17) src/Rask.Core/Forms/ModelGraphWalker.cs:200— ModelGraphWalker.StepInto has cyclomatic complexity 17 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
WebMember.Expand (cyclomatic 17) src/Rask.Dom.Tasks/WebMember.cs:148— WebMember.Expand has cyclomatic complexity 17 (threshold 15). Of this number, 16 points are the body's own statements and 1 belongs to one function literal inside it that branches. To reduce it, 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.
WebMember.Call (cyclomatic 17) src/Rask.Dom.Tasks/WebMember.cs:462— WebMember.Call has cyclomatic complexity 17 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
BuilderEntry.IsGroupedEntry (cyclomatic 17) src/Rask.Generators/Analyzers/BuilderEntry.cs:318— BuilderEntry.IsGroupedEntry has cyclomatic complexity 17 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
ComponentFactoryGenerator.ChainGroupOf (cyclomatic 17) src/Rask.Generators/ComponentFactoryGenerator.ComponentModel.cs:126— ComponentFactoryGenerator.ChainGroupOf has cyclomatic complexity 17 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
ClearPlacement.Judge (cyclomatic 17) scripts/flux/Flux/Commands/ClearPlacement.cs:169— ClearPlacement.Judge has cyclomatic complexity 17 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
Flags.Run (cyclomatic 17) scripts/flux/Flux/Commands/Flags.cs:40— Flags.Run has cyclomatic complexity 17 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
ParityChart.Compare (cyclomatic 17) scripts/flux/Flux/Commands/ParityChart.cs:277— ParityChart.Compare has cyclomatic complexity 17 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
ProbeList.Run (cyclomatic 17) scripts/flux/Flux/Commands/ProbeList.cs:72— ProbeList.Run has cyclomatic complexity 17 (threshold 15). Of this number, 16 points are the body's own statements and 1 belongs to one function literal inside it that branches. To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Where every arm is uniform — the same kind of value, with no behaviour of its own — a table keyed by the case is the shorter form; wherever the arms carry different data or different behaviour, keep them as cases, because collapsing those trades an explicit, reviewable set of cases for nothing.
Rail.LongMenu (cyclomatic 17) scripts/flux/Flux/Commands/Rail.cs:201— Rail.LongMenu has cyclomatic complexity 17 (threshold 15). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
Js.Quote (cyclomatic 17) scripts/flux/Flux/Lib/Js.cs:252— Js.Quote has cyclomatic complexity 17 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
Refresh.reach_all (cyclomatic 17) scripts/mdn/refresh.py:645— Refresh.reach_all has cyclomatic complexity 17 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
Parser.definition (cyclomatic 17) scripts/mdn/webidl.py:163— Parser.definition has cyclomatic complexity 17 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
rask-segments.step (cyclomatic 17) src/Rask.Core/Resources/rask-segments.ts:275— rask-segments.step has cyclomatic complexity 17 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
rask-calendar.drawMoments (cyclomatic 17) src/Rask.Core/Resources/rask-calendar.ts:677— rask-calendar.drawMoments has cyclomatic complexity 17 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
flash.changedElements (cyclomatic 17) src/Rask.DevTools/Resources/host/flash.ts:40— flash.changedElements has cyclomatic complexity 17 (threshold 15). Of this number, 15 points are the body's own statements and 2 belong to one function literal inside it that branches. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
flash.installFlash (cyclomatic 17) src/Rask.DevTools/Resources/host/flash.ts:69— flash.installFlash has cyclomatic complexity 17 (threshold 15). Of this number, 9 points are the body's own statements and 8 belong to 3 function items inside it that branch. To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
bridge.createBridge.handle (cyclomatic 17) src/Rask.DevTools/Resources/host/bridge.ts:48— bridge.createBridge.handle has cyclomatic complexity 17 (threshold 15). Of this number, 15 points are the body's own statements and 2 belong to one function literal inside it that branches. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
ui-phone.mount (cyclomatic 17) src/Rask.Ui/Resources/phone/ui-phone.ts:61— ui-phone.mount has cyclomatic complexity 17 (threshold 15). Of this number, 12 points are the body's own statements and 5 belong to 2 function items inside it that branch. To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
PasskeyVerifier.IsExpectedClientData (cyclomatic 16) src/Rask.Auth.Api/PasskeyVerifier.cs:173— PasskeyVerifier.IsExpectedClientData has cyclomatic complexity 16 (threshold 15). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
DomEventEmitter.MembersOf (cyclomatic 16) src/Rask.Dom.Tasks/DomEventEmitter.cs:188— DomEventEmitter.MembersOf has cyclomatic complexity 16 (threshold 15). Of this number, 15 points are the body's own statements and 1 belongs to one function literal inside it that branches. To reduce it, 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.
WebPayloads.Class (cyclomatic 16) src/Rask.Dom.Tasks/WebPayloads.cs:211— WebPayloads.Class has cyclomatic complexity 16 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
ContentSniffer.OtherSignature (cyclomatic 16) src/Rask.Storage/Upload/ContentSniffer.cs:148— ContentSniffer.OtherSignature has cyclomatic complexity 16 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
ParityMenu.CompareStyles (cyclomatic 16) scripts/flux/Flux/Commands/ParityMenu.cs:1167— ParityMenu.CompareStyles has cyclomatic complexity 16 (threshold 15). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
ParityTooltip.CompareShown (cyclomatic 16) scripts/flux/Flux/Commands/ParityTooltip.cs:467— ParityTooltip.CompareShown has cyclomatic complexity 16 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
Js.Write (cyclomatic 16) scripts/flux/Flux/Lib/Js.cs:163— Js.Write has cyclomatic complexity 16 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
OpenList.WalkBoth (cyclomatic 16) scripts/flux/Flux/Lib/OpenList.cs:180— OpenList.WalkBoth has cyclomatic complexity 16 (threshold 15). Of this number, 14 points are the body's own statements and 2 belong to 2 function literals inside it that branch. To reduce it, 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.
publish_packages.cmd_push (cyclomatic 16) scripts/lib/publish_packages.py:431— publish_packages.cmd_push has cyclomatic complexity 16 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
Refresh.read_spec_index (cyclomatic 16) scripts/mdn/refresh.py:166— Refresh.read_spec_index has cyclomatic complexity 16 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
Refresh.read_elements (cyclomatic 16) scripts/mdn/refresh.py:337— Refresh.read_elements has cyclomatic complexity 16 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
rask-segments.value (cyclomatic 16) src/Rask.Core/Resources/rask-segments.ts:157— rask-segments.value has cyclomatic complexity 16 (threshold 15). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
rask-calendar.drawText (cyclomatic 16) src/Rask.Core/Resources/rask-calendar.ts:643— rask-calendar.drawText has cyclomatic complexity 16 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
rask-list.filter (cyclomatic 16) src/Rask.Core/Resources/rask-list.ts:283— rask-list.filter has cyclomatic complexity 16 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
Mounted.wireSelect (cyclomatic 16) src/Rask.Ui/Resources/editor/ui-editor.ts:275— Mounted.wireSelect has cyclomatic complexity 16 (threshold 15). Most of this is not in the body itself: 1 of the 16 points is its own statement and the rest belongs to 6 function items inside it that branch (a function literal at line 303, activate, close, …). 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.
Races the wall clock: A_store_created_before_scopes_existed_is_migrated_rather_than_broken tests/Rask.Logging.Tests/LogScopeTests.cs:15— This test reads `DateTimeOffset.UtcNow` and compares it against the real system clock (`TimeProvider.System`) handed to the code under test. Those are two independent clock reads, so the test passes only while no boundary falls between them — a second ticking over between the code's read and the test's, or, for a date, a day that differs between the machine's local zone and UTC. It passes or fails on the time of day and the build agent's time zone, and re-running the suite on one machine cannot reveal it. Read the clock once: give the code under test a clock the test controls (a fake time provider, fake timers with a fixed system time) and build the expectation from that same instant, or assert a range rather than an exact value.
BarePragmaDisable repeated across 13 files tests/Rask.Benchmarks.VsBlazor/Benchmarks/Dispatch_PinnedBenchmarks.cs:82— The identical BarePragmaDisable (`#pragma warning disable RASK014`) appears in 13 files (31 occurrences) — a single repo-wide policy (e.g. a Directory.Build.props decision or an idiomatic suppression), not 31 independent debts. Decide it once centrally rather than file-by-file. (Every occurrence still counts toward the score and metrics.)
rask-morph.morphNode (cognitive 145) src/Rask.Core/Resources/rask-morph.ts:583— rask-morph.morphNode has cognitive complexity 145 (threshold 15). Drivers by points: if/else 42 (84 pts), boolean chains 28, ternaries 7 (17 pts), loops 11 (16 pts) (nesting depth added 57). Of this number, 140 points are the body's own statements and 5 belong to 2 function items inside it that branch. To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
OpenList.MeasureOpen (cognitive 95) scripts/flux/Flux/Lib/OpenList.cs:308— OpenList.MeasureOpen has cognitive complexity 95 (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.
rask-dom.applyOps (cognitive 91) REDACTED:199— rask-dom.applyOps has cognitive complexity 91 (threshold 15). Drivers by points: if/else 20 (62 pts), loops 5 (13 pts), boolean chains 7, ternaries 2 (7 pts), match/switch 1 (2 pts) (nesting depth added 56). Of this number, 89 points are the body's own statements and 2 belong to one function item inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
affected_projects.main (cognitive 80) scripts/lib/affected_projects.py:139— affected_projects.main has cognitive complexity 80 (threshold 15). Drivers by points: if/else 16 (42 pts), loops 13 (23 pts), ternaries 2 (6 pts), error handling 2 (5 pts), boolean chains 4 (nesting depth added 43). 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.
OpenList.Run (cognitive 68) scripts/flux/Flux/Lib/OpenList.cs:39— OpenList.Run has cognitive complexity 68 (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.
rask-color.draw (cognitive 68) src/Rask.Core/Resources/rask-color.ts:314— rask-color.draw has cognitive complexity 68 (threshold 15). Drivers by points: ternaries 16 (37 pts), if/else 6 (14 pts), loops 12 (13 pts), boolean chains 4 (nesting depth added 30). Of this number, 62 points are the body's own statements and 6 belong to one function literal inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
ParityMenu.Run (cognitive 65) scripts/flux/Flux/Commands/ParityMenu.cs:307— ParityMenu.Run has cognitive complexity 65 (threshold 15). Of this number, 63 points are the body's own statements and 2 belong to one function literal inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
ParityMenu.CompareExample (cognitive 61) scripts/flux/Flux/Commands/ParityMenu.cs:913— ParityMenu.CompareExample has cognitive complexity 61 (threshold 15). Of this number, 56 points are the body's own statements and 5 belong to 3 function literals inside it that branch. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
ParityColorPicker.WalkBoth (cognitive 60) scripts/flux/Flux/Commands/ParityColorPicker.cs:287— ParityColorPicker.WalkBoth has cognitive complexity 60 (threshold 15). Of this number, 56 points are the body's own statements and 4 belong to 2 function literals inside it that branch. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
ParityToast.CompareScreens (cognitive 55) scripts/flux/Flux/Commands/ParityToast.cs:537— ParityToast.CompareScreens has cognitive complexity 55 (threshold 15). Of this number, 54 points are the body's own statements and 1 belongs to one function literal inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
ParityMenu.MeasureExample (cognitive 53) scripts/flux/Flux/Commands/ParityMenu.cs:554— ParityMenu.MeasureExample has cognitive complexity 53 (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.
Measure.MeasureLayouts (cognitive 52) scripts/flux/Flux/Lib/Measure.cs:286— Measure.MeasureLayouts has cognitive complexity 52 (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.
ParityModal.Run (cognitive 51) scripts/flux/Flux/Commands/ParityModal.cs:155— ParityModal.Run has cognitive complexity 51 (threshold 15). Of this number, 42 points are the body's own statements and 9 belong to 2 function items inside it that branch. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
panel-client.installPanelClient (cognitive 49) REDACTED:54— panel-client.installPanelClient has cognitive complexity 49 (threshold 15). Drivers by points: if/else 29 (33 pts), ternaries 7 (8 pts), boolean chains 6, loops 2 (nesting depth added 5). Most of this is not in the body itself: 1 of the 49 points is its own statement and the rest belongs to 10 function items inside it that branch (syncFlash, a function literal at line 201, a function literal at line 66, …). 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.
rask-overlay.installModal (cognitive 48) src/Rask.Core/Resources/rask-overlay.ts:255— rask-overlay.installModal has cognitive complexity 48 (threshold 15). Drivers by points: if/else 18 (24 pts), boolean chains 12, ternaries 4 (10 pts), loops 1 (2 pts) (nesting depth added 13). Most of this is not in the body itself: 1 of the 48 points is its own statement and the rest belongs to 8 function literals inside it that branch (lines 322, 293, 309, …). 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.
ParityPopover.Run (cognitive 46) scripts/flux/Flux/Commands/ParityPopover.cs:147— ParityPopover.Run has cognitive complexity 46 (threshold 15). Of this number, 43 points are the body's own statements and 3 belong to 2 function literals inside it that branch. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
Refresh.Unlisted (cognitive 46) scripts/flux/Flux/Commands/Refresh.cs:204— Refresh.Unlisted has cognitive complexity 46 (threshold 15). Of this number, 45 points are the body's own statements and 1 belongs to one function literal inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
(anonymous) (cognitive 45) src/Rask.Pdf/PrintTables.js:6— (anonymous) has cognitive complexity 45 (threshold 15). Drivers by points: if/else 15 (21 pts), loops 6 (9 pts), ternaries 6 (9 pts), boolean chains 4, error handling 1, other 1 (nesting depth added 12). Most of this is not in the body itself: 5 of the 45 points are its own statements and the rest belongs to 20 function items inside it that branch (a function literal at line 123, fixColumns, cut, …). 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.
Sync.Run (cognitive 42) scripts/flux/Flux/Commands/Sync.cs:54— Sync.Run has cognitive complexity 42 (threshold 15). Of this number, 41 points are the body's own statements and 1 belongs to one function literal inside it that branches. To reduce it, 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.
ClearPlacement.Run (cognitive 40) scripts/flux/Flux/Commands/ClearPlacement.cs:65— ClearPlacement.Run has cognitive complexity 40 (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.
ParityTooltip.Run (cognitive 40) scripts/flux/Flux/Commands/ParityTooltip.cs:184— ParityTooltip.Run has cognitive complexity 40 (threshold 15). Of this number, 38 points are the body's own statements and 2 belong to one function literal inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
Refresh.extras_of (cognitive 39) scripts/mdn/refresh.py:532— Refresh.extras_of has cognitive complexity 39 (threshold 15). Drivers by points: if/else 9 (21 pts), ternaries 3 (9 pts), boolean chains 8, loops 1 (nesting depth added 18). 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.
ui-phone.handle (cognitive 39) src/Rask.Ui/Resources/phone/ui-phone.ts:397— ui-phone.handle has cognitive complexity 39 (threshold 15). Drivers by points: if/else 13 (25 pts), boolean chains 7, ternaries 3 (6 pts), match/switch 1 (nesting depth added 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.
Parity.Report (cognitive 38) scripts/flux/Flux/Commands/Parity.cs:168— Parity.Report has cognitive complexity 38 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
ParityChart.Compare (cognitive 38) scripts/flux/Flux/Commands/ParityChart.cs:277— ParityChart.Compare has cognitive complexity 38 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
ParityComparer.CompareLook (cognitive 38) scripts/flux/Flux/Lib/ParityComparer.cs:399— ParityComparer.CompareLook has cognitive complexity 38 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
Refresh.read_spec_index (cognitive 38) scripts/mdn/refresh.py:166— Refresh.read_spec_index has cognitive complexity 38 (threshold 15). Drivers by points: if/else 4 (15 pts), loops 5 (14 pts), boolean chains 5, ternaries 1 (4 pts) (nesting depth added 23). 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.
Refresh.wanted (cognitive 38) scripts/mdn/refresh.py:394— Refresh.wanted has cognitive complexity 38 (threshold 15). Drivers by points: if/else 4 (13 pts), ternaries 4 (12 pts), loops 5 (9 pts), boolean chains 4 (nesting depth added 21). 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.
rask-color.areaKey (cognitive 38) src/Rask.Core/Resources/rask-color.ts:423— rask-color.areaKey has cognitive complexity 38 (threshold 15). Drivers by points: ternaries 9 (37 pts), if/else 1 (nesting depth added 28). To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
Refresh.describe (cognitive 37) scripts/mdn/refresh.py:473— Refresh.describe has cognitive complexity 37 (threshold 15). Drivers by points: if/else 7 (15 pts), boolean chains 9, ternaries 5 (7 pts), loops 4 (6 pts) (nesting depth added 12). 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.
Refresh.members_of (cognitive 36) scripts/mdn/refresh.py:429— Refresh.members_of has cognitive complexity 36 (threshold 15). Drivers by points: if/else 13 (25 pts), boolean chains 5, ternaries 2 (5 pts), loops 1 (nesting depth added 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.
ParityComparer.CompareTree (cognitive 35) scripts/flux/Flux/Lib/ParityComparer.cs:310— ParityComparer.CompareTree has cognitive complexity 35 (threshold 15). Of this number, 28 points are the body's own statements and 7 belong to 5 function items inside it that branch. To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
webidl.tokenise (cognitive 35) scripts/mdn/webidl.py:73— webidl.tokenise has cognitive complexity 35 (threshold 15). Drivers by points: if/else 7 (21 pts), ternaries 2 (8 pts), loops 2 (4 pts), boolean chains 2 (nesting depth added 22). 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.
rask.onFrame (cognitive 35) src/Rask.Server/Resources/rask.ts:593— rask.onFrame has cognitive complexity 35 (threshold 15). Drivers by points: if/else 20 (28 pts), boolean chains 4, ternaries 1 (2 pts), error handling 1 (nesting depth added 9). 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.
rask-menu-keys.cursorKey (cognitive 33) src/Rask.Core/Resources/rask-menu-keys.ts:78— rask-menu-keys.cursorKey has cognitive complexity 33 (threshold 15). Drivers by points: ternaries 7 (12 pts), boolean chains 11, if/else 7 (10 pts) (nesting depth added 8). Of this number, 30 points are the body's own statements and 3 belong to one function literal inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
FormData.FromJson (cognitive 32) src/Rask.Core/Live/FormData.cs:48— FormData.FromJson has cognitive complexity 32 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
ParityChart.Run (cognitive 32) scripts/flux/Flux/Commands/ParityChart.cs:137— ParityChart.Run has cognitive complexity 32 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
Refresh.read_events (cognitive 32) scripts/mdn/refresh.py:357— Refresh.read_events has cognitive complexity 32 (threshold 15). Drivers by points: if/else 7 (14 pts), boolean chains 9, ternaries 3 (5 pts), loops 3 (4 pts) (nesting depth added 10). 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.
DomValueTypes.Map (cognitive 31) src/Rask.Dom.Tasks/DomValueTypes.cs:194— DomValueTypes.Map has cognitive complexity 31 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
top-level statements (cognitive 31) scripts/tools/RaskRename/Program.cs:15— top-level statements has cognitive complexity 31 (threshold 15). Most of this is not in the body itself: 14 of the 31 points are its own statements and the rest belongs to 5 function items inside it that branch (SweepUncompiledText, Find, a function literal at line 111, …). 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.
Refresh.reflected_names (cognitive 31) scripts/mdn/refresh.py:568— Refresh.reflected_names has cognitive complexity 31 (threshold 15). Drivers by points: ternaries 5 (16 pts), boolean chains 6, if/else 2 (6 pts), loops 2 (3 pts) (nesting depth added 16). 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.
Refresh.reach_all (cognitive 31) scripts/mdn/refresh.py:645— Refresh.reach_all has cognitive complexity 31 (threshold 15). Drivers by points: loops 7 (13 pts), if/else 3 (9 pts), ternaries 3 (6 pts), boolean chains 3 (nesting depth added 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.
rask-segments.step (cognitive 31) src/Rask.Core/Resources/rask-segments.ts:275— rask-segments.step has cognitive complexity 31 (threshold 15). Drivers by points: ternaries 11 (26 pts), if/else 4, boolean chains 1 (nesting depth added 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.
rask-field.maskMoney (cognitive 30) src/Rask.Core/Resources/rask-field.ts:67— rask-field.maskMoney has cognitive complexity 30 (threshold 15). Drivers by points: if/else 9 (15 pts), boolean chains 8, ternaries 4, loops 3 (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
HeroCode.Highlight (cognitive 29) src/Rask.Site/Features/Home/HeroCode.cs:137— HeroCode.Highlight has cognitive complexity 29 (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.
ParityFocus.Run (cognitive 29) scripts/flux/Flux/Commands/ParityFocus.cs:171— ParityFocus.Run has cognitive complexity 29 (threshold 15). Of this number, 23 points are the body's own statements and 6 belong to 3 function literals inside it that branch. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
SymbolRegistration.DescribeUnnameableWithRemedy (cognitive 28) src/Rask.Generators.Shared/SymbolRegistration.cs:86— SymbolRegistration.DescribeUnnameableWithRemedy has cognitive complexity 28 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
DateFlip.Run (cognitive 28) scripts/flux/Flux/Commands/DateFlip.cs:69— DateFlip.Run has cognitive complexity 28 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
OpenList.WalkBoth (cognitive 28) scripts/flux/Flux/Lib/OpenList.cs:180— OpenList.WalkBoth has cognitive complexity 28 (threshold 15). Of this number, 26 points are the body's own statements and 2 belong to 2 function literals inside it that branch. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
ParityCommand.Run (cognitive 27) scripts/flux/Flux/Commands/ParityCommand.cs:87— ParityCommand.Run has cognitive complexity 27 (threshold 15). Of this number, 26 points are the body's own statements and 1 belongs to one function literal inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
Placement.Landings (cognitive 27) scripts/flux/Flux/Lib/Placement.cs:101— Placement.Landings has cognitive complexity 27 (threshold 15). Of this number, 25 points are the body's own statements and 2 belong to one function literal inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
Refresh.reach (cognitive 27) scripts/mdn/refresh.py:670— Refresh.reach has cognitive complexity 27 (threshold 15). Drivers by points: if/else 5 (12 pts), loops 3 (7 pts), ternaries 2 (5 pts), boolean chains 3 (nesting depth added 14). 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.
rask-http-transport.openHttpConnection.parse (cognitive 27) src/Rask.Server/Resources/rask-http-transport.ts:393— rask-http-transport.openHttpConnection.parse has cognitive complexity 27 (threshold 15). Drivers by points: if/else 6 (14 pts), ternaries 2 (5 pts), boolean chains 3, loops 1 (3 pts), error handling 1 (2 pts) (nesting depth added 14). 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.
ReadModelGenerator.AppendFaceMembers (cognitive 26) src/Rask.Batteries.Generators/ReadModelGenerator.cs:490— ReadModelGenerator.AppendFaceMembers has cognitive complexity 26 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
DomEventEmitter.MembersOf (cognitive 26) src/Rask.Dom.Tasks/DomEventEmitter.cs:188— DomEventEmitter.MembersOf has cognitive complexity 26 (threshold 15). Of this number, 25 points are the body's own statements and 1 belongs to one function literal inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
Parity.Run (cognitive 26) scripts/flux/Flux/Commands/Parity.cs:61— Parity.Run has cognitive complexity 26 (threshold 15). Of this number, 24 points are the body's own statements and 2 belong to one function literal inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
Parser.definition (cognitive 26) scripts/mdn/webidl.py:163— Parser.definition has cognitive complexity 26 (threshold 15). Drivers by points: if/else 15 (24 pts), loops 1 (2 pts) (nesting depth added 10). 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.
rask-calendar.paintDay (cognitive 26) src/Rask.Core/Resources/rask-calendar.ts:447— rask-calendar.paintDay has cognitive complexity 26 (threshold 15). Drivers by points: boolean chains 10, ternaries 5 (8 pts), if/else 5 (7 pts), loops 1 (nesting depth added 5). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
rask-calendar.drawTimes (cognitive 26) src/Rask.Core/Resources/rask-calendar.ts:886— rask-calendar.drawTimes has cognitive complexity 26 (threshold 15). Drivers by points: ternaries 9 (13 pts), if/else 8 (9 pts), boolean chains 4 (nesting depth added 5). Most of this is not in the body itself: 4 of the 26 points are its own statements and the rest belongs to 4 function literals inside it that branch (lines 898, 913, 890, …). 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.
flash.changedElements (cognitive 26) src/Rask.DevTools/Resources/host/flash.ts:40— flash.changedElements has cognitive complexity 26 (threshold 15). Drivers by points: if/else 8 (18 pts), boolean chains 5, ternaries 1 (2 pts), loops 1 (nesting depth added 11). Of this number, 20 points are the body's own statements and 6 belong to one function literal inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
rask.applyFullReply::commit (cognitive 26) src/Rask.Server/Resources/rask.ts:1724— rask.applyFullReply::commit has cognitive complexity 26 (threshold 15). Drivers by points: if/else 12 (17 pts), boolean chains 7, ternaries 1 (2 pts) (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
DeclarationReader.ReadToken (cognitive 25) src/Rask.Generators/ScopedScripts/DeclarationReader.cs:87— DeclarationReader.ReadToken has cognitive complexity 25 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
ClearPlacement.Judge (cognitive 25) scripts/flux/Flux/Commands/ClearPlacement.cs:169— ClearPlacement.Judge has cognitive complexity 25 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
Flags.Run (cognitive 25) scripts/flux/Flux/Commands/Flags.cs:40— Flags.Run has cognitive complexity 25 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
Refresh.read_elements (cognitive 25) scripts/mdn/refresh.py:337— Refresh.read_elements has cognitive complexity 25 (threshold 15). Drivers by points: if/else 4 (11 pts), boolean chains 7, loops 3 (4 pts), ternaries 1 (3 pts) (nesting depth added 10). 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.
rask-color.swatchKey (cognitive 25) src/Rask.Core/Resources/rask-color.ts:506— rask-color.swatchKey has cognitive complexity 25 (threshold 15). Drivers by points: ternaries 6 (21 pts), boolean chains 2, if/else 2 (nesting depth added 15). To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
rask-list.filter (cognitive 25) src/Rask.Core/Resources/rask-list.ts:283— rask-list.filter has cognitive complexity 25 (threshold 15). Drivers by points: loops 3 (7 pts), ternaries 3 (7 pts), boolean chains 6, if/else 3 (5 pts) (nesting depth added 10). 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.
Element.AppendPrefixedAttrs (cognitive 24) src/Rask.Core/Element.cs:629— Element.AppendPrefixedAttrs has cognitive complexity 24 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
Walker.Walk (cognitive 24) scripts/flux/Flux/Commands/ParityCarousel.cs:142— Walker.Walk has cognitive complexity 24 (threshold 15). Of this number, 22 points are the body's own statements and 2 belong to 2 function literals inside it that branch. To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
ParityDate.Run (cognitive 24) scripts/flux/Flux/Commands/ParityDate.cs:67— ParityDate.Run has cognitive complexity 24 (threshold 15). Of this number, 22 points are the body's own statements and 2 belong to one function literal inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
ParityMenu.CompareTree (cognitive 24) scripts/flux/Flux/Commands/ParityMenu.cs:1075— ParityMenu.CompareTree has cognitive complexity 24 (threshold 15). Of this number, 23 points are the body's own statements and 1 belongs to one function item inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
ParityTooltip.Report (cognitive 24) scripts/flux/Flux/Commands/ParityTooltip.cs:626— ParityTooltip.Report has cognitive complexity 24 (threshold 15). Of this number, 20 points are the body's own statements and 4 belong to 2 function literals inside it that branch. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
Sync.Fingerprints (cognitive 24) scripts/flux/Flux/Commands/Sync.cs:293— Sync.Fingerprints has cognitive complexity 24 (threshold 15). Of this number, 21 points are the body's own statements and 3 belong to one function item inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
ParityComparer.CompareExample (cognitive 24) scripts/flux/Flux/Lib/ParityComparer.cs:194— ParityComparer.CompareExample has cognitive complexity 24 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
rask-api.raskWebData (cognitive 24) src/Rask.Core/Resources/rask-api.ts:120— rask-api.raskWebData has cognitive complexity 24 (threshold 15). Drivers by points: if/else 10 (12 pts), boolean chains 9, error handling 1 (2 pts), loops 1 (nesting depth added 3). 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.
rask-bound.observed (cognitive 24) src/Rask.Core/Resources/rask-bound.ts:154— rask-bound.observed has cognitive complexity 24 (threshold 15). Drivers by points: if/else 7 (16 pts), loops 3 (6 pts), boolean chains 2 (nesting depth added 12). Of this number, 17 points are the body's own statements and 7 belong to 3 function items inside it that branch. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
SafeFileName.Clean (cognitive 23) src/Rask.Storage/Upload/SafeFileName.cs:33— SafeFileName.Clean has cognitive complexity 23 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
Js.Write (cognitive 23) scripts/flux/Flux/Lib/Js.cs:163— Js.Write has cognitive complexity 23 (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.
Measure.Examples (cognitive 23) scripts/flux/Flux/Lib/Measure.cs:61— Measure.Examples has cognitive complexity 23 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
Placement.MeasureSide (cognitive 23) scripts/flux/Flux/Lib/Placement.cs:223— Placement.MeasureSide has cognitive complexity 23 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
Refresh.find_reflecting (cognitive 23) scripts/mdn/refresh.py:593— Refresh.find_reflecting has cognitive complexity 23 (threshold 15). Drivers by points: ternaries 4 (12 pts), if/else 3 (6 pts), boolean chains 4, loops 1 (nesting depth added 11). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
rask-calendar.key (cognitive 23) src/Rask.Core/Resources/rask-calendar.ts:983— rask-calendar.key has cognitive complexity 23 (threshold 15). Drivers by points: ternaries 6 (13 pts), if/else 5 (8 pts), boolean chains 2 (nesting depth added 10). 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.
rask-morph.raskNotePendingFormState (cognitive 23) src/Rask.Core/Resources/rask-morph.ts:421— rask-morph.raskNotePendingFormState has cognitive complexity 23 (threshold 15). Drivers by points: ternaries 5 (8 pts), if/else 5 (6 pts), loops 2 (5 pts), boolean chains 4 (nesting depth added 7). 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.
FieldPath.Children (cognitive 22) src/Rask.Core/Forms/FieldPath.cs:49— FieldPath.Children has cognitive complexity 22 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
DomValueTypes.Record (cognitive 22) src/Rask.Dom.Tasks/DomValueTypes.cs:771— DomValueTypes.Record has cognitive complexity 22 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
ParityTooltip.CompareShown (cognitive 22) scripts/flux/Flux/Commands/ParityTooltip.cs:467— ParityTooltip.CompareShown has cognitive complexity 22 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
Js.Num (cognitive 22) scripts/flux/Flux/Lib/Js.cs:24— Js.Num has cognitive complexity 22 (threshold 15). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
publish_packages.cmd_push (cognitive 22) scripts/lib/publish_packages.py:431— publish_packages.cmd_push has cognitive complexity 22 (threshold 15). Drivers by points: if/else 7 (12 pts), ternaries 4 (6 pts), boolean chains 3, loops 1 (nesting depth added 7). 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.
bridge.createBridge.handle (cognitive 22) src/Rask.DevTools/Resources/host/bridge.ts:48— bridge.createBridge.handle has cognitive complexity 22 (threshold 15). Drivers by points: if/else 9 (16 pts), ternaries 1 (3 pts), boolean chains 2, match/switch 1 (nesting depth added 9). Of this number, 21 points are the body's own statements and 1 belongs to one function literal inside it that branches. 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.
CqrsCodecGenerator.DiscoverMessages (cognitive 21) src/Rask.Batteries.Generators/CqrsCodecGenerator.cs:202— CqrsCodecGenerator.DiscoverMessages has cognitive complexity 21 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
ConstraintNameConvention.ProcessModelFinalizing (cognitive 21) src/Rask.Data/ConstraintNameConvention.cs:17— ConstraintNameConvention.ProcessModelFinalizing has cognitive complexity 21 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
DomValueTypes.HandedOver (cognitive 21) src/Rask.Dom.Tasks/DomValueTypes.cs:500— DomValueTypes.HandedOver has cognitive complexity 21 (threshold 15). To reduce it, break up the iteration: give each loop body a named function, and split a multi-phase loop into one function per phase so no single body carries the whole pipeline.
WebPayloads.Class (cognitive 21) src/Rask.Dom.Tasks/WebPayloads.cs:211— WebPayloads.Class has cognitive complexity 21 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
AuthBeforeRaskAnalyzer.Analyze (cognitive 21) src/Rask.Generators/Analyzers/AuthBeforeRaskAnalyzer.cs:52— AuthBeforeRaskAnalyzer.Analyze has cognitive complexity 21 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
ComponentFactoryGenerator.GetSetterHost (cognitive 21) src/Rask.Generators/ComponentFactoryGenerator.Setters.cs:19— ComponentFactoryGenerator.GetSetterHost has cognitive complexity 21 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
ParityChart.Differing (cognitive 21) scripts/flux/Flux/Commands/ParityChart.cs:469— ParityChart.Differing has cognitive complexity 21 (threshold 15). Of this number, 20 points are the body's own statements and 1 belongs to one function item inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
publish_packages.push_one (cognitive 21) scripts/lib/publish_packages.py:236— publish_packages.push_one has cognitive complexity 21 (threshold 15). Drivers by points: if/else 7 (13 pts), boolean chains 3, error handling 1 (2 pts), ternaries 1 (2 pts), loops 1 (nesting depth added 8). 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.
rask-api.raskWebWalk (cognitive 21) src/Rask.Core/Resources/rask-api.ts:46— rask-api.raskWebWalk has cognitive complexity 21 (threshold 15). Drivers by points: if/else 10 (19 pts), boolean chains 1, loops 1 (nesting depth added 9). 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.
rask-dom.syncFormProperty (cognitive 21) REDACTED:129— rask-dom.syncFormProperty has cognitive complexity 21 (threshold 15). Drivers by points: if/else 10 (15 pts), boolean chains 6 (nesting depth added 5). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
rask-place.fit (cognitive 21) REDACTED:102— rask-place.fit has cognitive complexity 21 (threshold 15). Drivers by points: ternaries 4 (9 pts), if/else 4 (8 pts), boolean chains 3, loops 1 (nesting depth added 9). 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.
overlay.installOverlay (cognitive 21) src/Rask.DevTools/Resources/host/overlay.ts:70— overlay.installOverlay has cognitive complexity 21 (threshold 15). Drivers by points: if/else 9 (10 pts), boolean chains 8, ternaries 2, loops 1 (nesting depth added 1). Most of this is not in the body itself: 4 of the 21 points are its own statements and the rest belongs to 7 function items inside it that branch (pointAt, draw, schedule, …). 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.
rask.saveRestoreFields (cognitive 21) src/Rask.Server/Resources/rask.ts:1007— rask.saveRestoreFields has cognitive complexity 21 (threshold 15). Drivers by points: if/else 7 (13 pts), boolean chains 4, ternaries 1 (2 pts), error handling 1, loops 1 (nesting depth added 7). 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.
CqrsCodecGenerator.DiscoverHandlers (cognitive 20) src/Rask.Batteries.Generators/CqrsCodecGenerator.cs:246— CqrsCodecGenerator.DiscoverHandlers has cognitive complexity 20 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
ModelInputGenerator.AppendCollect (cognitive 20) src/Rask.Batteries.Generators/ModelInputGenerator.WriteRules.cs:154— ModelInputGenerator.AppendCollect has cognitive complexity 20 (threshold 15). Of this number, 18 points are the body's own statements and 2 belong to one function literal inside it that branches. To reduce it, 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.
PositionIndex.RemoveAt (cognitive 20) src/Rask.Core/Live/PositionIndex.cs:161— PositionIndex.RemoveAt has cognitive complexity 20 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
WebMember.Call (cognitive 20) src/Rask.Dom.Tasks/WebMember.cs:462— WebMember.Call has cognitive complexity 20 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
ComponentConstructionCodeFixProvider.EntryName (cognitive 20) src/Rask.Generators.CodeFixes/ComponentConstructionCodeFixProvider.cs:118— ComponentConstructionCodeFixProvider.EntryName has cognitive complexity 20 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
TypeMapper.MapReturn (cognitive 20) src/Rask.Generators/ScopedScripts/TypeMapper.cs:126— TypeMapper.MapReturn has cognitive complexity 20 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
ParityCarousel.Run (cognitive 20) scripts/flux/Flux/Commands/ParityCarousel.cs:94— ParityCarousel.Run has cognitive complexity 20 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
OpenList.CompareTree (cognitive 20) scripts/flux/Flux/Lib/OpenList.cs:594— OpenList.CompareTree has cognitive complexity 20 (threshold 15). Of this number, 19 points are the body's own statements and 1 belongs to one function item inside it that branches. To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition.
no_node.lines (cognitive 20) scripts/lib/no_node.py:94— no_node.lines has cognitive complexity 20 (threshold 15). Drivers by points: loops 5 (10 pts), if/else 5 (6 pts), ternaries 1 (3 pts), boolean chains 1 (nesting depth added 8). To reduce it, break up the iteration: give each loop body a named function, and split a multi-phase loop into one function per phase so no single body carries the whole pipeline.
cldr.step (cognitive 20) scripts/upstream/cldr.py:135— cldr.step has cognitive complexity 20 (threshold 15). Drivers by points: if/else 9 (13 pts), loops 3 (4 pts), boolean chains 3 (nesting depth added 5). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
rask-head-assets.createInvokeGate.trackHeadAsset (cognitive 20) src/Rask.Core/Resources/rask-head-assets.ts:53— rask-head-assets.createInvokeGate.trackHeadAsset has cognitive complexity 20 (threshold 15). Drivers by points: if/else 9, boolean chains 8, ternaries 2 (3 pts) (nesting depth added 1). Of this number, 16 points are the body's own statements and 4 belong to one function item inside it that branches. To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
rask-tabs.draw (cognitive 20) src/Rask.Core/Resources/rask-tabs.ts:98— rask-tabs.draw has cognitive complexity 20 (threshold 15). Drivers by points: ternaries 6 (15 pts), boolean chains 2, if/else 1 (2 pts), loops 1 (nesting depth added 10). 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.
ApiClientGenerator.Emit (cognitive 19) src/Rask.Api.Generators/ApiClientGenerator.cs:134— ApiClientGenerator.Emit has cognitive complexity 19 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
Component.TryFindHandler (cognitive 19) src/Rask.Core/Component.StaleEvents.cs:77— Component.TryFindHandler has cognitive complexity 19 (threshold 15). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
Parser.ReadClassMember (cognitive 19) src/Rask.Generators/ScopedScripts/DeclarationReader.cs:386— Parser.ReadClassMember has cognitive complexity 19 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
Parser.ext_attr (cognitive 19) scripts/mdn/webidl.py:388— Parser.ext_attr has cognitive complexity 19 (threshold 15). Drivers by points: if/else 8 (13 pts), boolean chains 3, loops 1 (3 pts) (nesting depth added 7). 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.
rask-deverror.showDevError (cognitive 19) src/Rask.Core/Resources/rask-deverror.ts:232— rask-deverror.showDevError has cognitive complexity 19 (threshold 15). Drivers by points: if/else 8 (10 pts), boolean chains 9 (nesting depth added 2). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
flash.installFlash (cognitive 19) src/Rask.DevTools/Resources/host/flash.ts:69— flash.installFlash has cognitive complexity 19 (threshold 15). Drivers by points: if/else 12 (13 pts), boolean chains 2, loops 2, ternaries 1 (2 pts) (nesting depth added 2). Of this number, 10 points are the body's own statements and 9 belong to 3 function items inside it that branch. To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
GeneratedModelShape.EntitiesFor (cognitive 18) src/Rask.Generators.Shared/GeneratedModelShape.cs:124— GeneratedModelShape.EntitiesFor has cognitive complexity 18 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
ModelGraphWalker.StepInto (cognitive 18) src/Rask.Core/Forms/ModelGraphWalker.cs:200— ModelGraphWalker.StepInto has cognitive complexity 18 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
ModelGraphWalker.SplitPath (cognitive 18) src/Rask.Core/Forms/ModelGraphWalker.cs:260— ModelGraphWalker.SplitPath has cognitive complexity 18 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
DeclaredUniqueRules.Predicate (cognitive 18) src/Rask.Data/DeclaredUniqueRules.cs:123— DeclaredUniqueRules.Predicate has cognitive complexity 18 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
BuilderEntry.IsGroupedEntry (cognitive 18) src/Rask.Generators/Analyzers/BuilderEntry.cs:318— BuilderEntry.IsGroupedEntry has cognitive complexity 18 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
ComponentFactoryGenerator.ChainGroupOf (cognitive 18) src/Rask.Generators/ComponentFactoryGenerator.ComponentModel.cs:126— ComponentFactoryGenerator.ChainGroupOf has cognitive complexity 18 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
Parser.ReadParameters (cognitive 18) src/Rask.Generators/ScopedScripts/DeclarationReader.cs:437— Parser.ReadParameters has cognitive complexity 18 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
Parser.ReadTuple (cognitive 18) src/Rask.Generators/ScopedScripts/DeclarationReader.cs:701— Parser.ReadTuple has cognitive complexity 18 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
HttpFetchDemo.OnMount (cognitive 18) src/Rask.Site/Features/Http/HttpFetchDemo.cs:23— HttpFetchDemo.OnMount has cognitive complexity 18 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
JsonIndexDdl.Build (cognitive 18) src/Rask.SQLite.EntityFrameworkCore/JsonIndexDdl.cs:61— JsonIndexDdl.Build has cognitive complexity 18 (threshold 15). To reduce it, break up the iteration: give each loop body a named function, and split a multi-phase loop into one function per phase so no single body carries the whole pipeline.
UiChartDrawing.Marks (cognitive 18) src/Rask.Ui/UiChartDrawing.cs:151— UiChartDrawing.Marks has cognitive complexity 18 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
Icons.Run (cognitive 18) REDACTED:50— Icons.Run has cognitive complexity 18 (threshold 15). Of this number, 17 points are the body's own statements and 1 belongs to one function literal inside it that branches. To reduce it, 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.
ParityColorPicker.Sheets (cognitive 18) scripts/flux/Flux/Commands/ParityColorPicker.cs:175— ParityColorPicker.Sheets has cognitive complexity 18 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
ParityTooltip.Show (cognitive 18) scripts/flux/Flux/Commands/ParityTooltip.cs:357— ParityTooltip.Show has cognitive complexity 18 (threshold 15). To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
Refresh.Reference (cognitive 18) scripts/flux/Flux/Commands/Refresh.cs:106— Refresh.Reference has cognitive complexity 18 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
publish_packages.load_set (cognitive 18) scripts/lib/publish_packages.py:111— publish_packages.load_set has cognitive complexity 18 (threshold 15). Drivers by points: if/else 6 (13 pts), loops 4 (5 pts) (nesting depth added 8). 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.
rask-carousel.sync (cognitive 18) src/Rask.Core/Resources/rask-carousel.ts:116— rask-carousel.sync has cognitive complexity 18 (threshold 15). Drivers by points: if/else 4 (6 pts), loops 4 (5 pts), boolean chains 4, ternaries 1 (3 pts) (nesting depth added 5). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
rask-events.domEvents.forEach() (cognitive 18) src/Rask.Core/Resources/rask-events.ts:40— rask-events.domEvents.forEach() has cognitive complexity 18 (threshold 15). Drivers by points: boolean chains 8, if/else 8, ternaries 1 (2 pts) (nesting depth added 1). Most of this is not in the body itself: 2 of the 18 points are its own statements and the rest belongs to one function literal inside it that branches (line 44). 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.
rask.applyDiffReply (cognitive 18) src/Rask.Server/Resources/rask.ts:1668— rask.applyDiffReply has cognitive complexity 18 (threshold 15). Drivers by points: if/else 9 (15 pts), ternaries 2, boolean chains 1 (nesting depth added 6). Most of this is not in the body itself: 6 of the 18 points are its own statements and the rest belongs to one function item inside it that branches (applyBody). Those helpers are already separate functions, so extracting the branching again is not available. To reduce it, move them out of the body to the enclosing scope, where each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
CqrsCodecGenerator.Authorization (cognitive 17) src/Rask.Batteries.Generators/CqrsCodecGenerator.cs:288— CqrsCodecGenerator.Authorization 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.
ModelInputGenerator.AggregateReferencesOf (cognitive 17) src/Rask.Batteries.Generators/ModelInputGenerator.Model.cs:242— ModelInputGenerator.AggregateReferencesOf has cognitive complexity 17 (threshold 15). Of this number, 16 points are the body's own statements and 1 belongs to one function item inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
CliApplication.RunAsync (cognitive 17) src/Rask.Cli/CliApplication.cs:44— CliApplication.RunAsync 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.
LiveSessionBase.TryWriteDiff (cognitive 17) src/Rask.Core/Live/LiveSessionBase.cs:1028— LiveSessionBase.TryWriteDiff 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.
ComponentFactoryGenerator.BuildConstraintsClause (cognitive 17) src/Rask.Generators/ComponentFactoryGenerator.ComponentModel.cs:292— ComponentFactoryGenerator.BuildConstraintsClause 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.
ComponentFactoryGenerator.ScanExternalEntries (cognitive 17) src/Rask.Generators/ComponentFactoryGenerator.EntryHosts.cs:526— ComponentFactoryGenerator.ScanExternalEntries 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.
RoutesGenerator.ReportRouteCollisions (cognitive 17) src/Rask.Generators/RoutesGenerator.Diagnostics.cs:246— RoutesGenerator.ReportRouteCollisions 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.
RoutesGenerator.AppendPathExpression (cognitive 17) src/Rask.Generators/RoutesGenerator.Factories.cs:231— RoutesGenerator.AppendPathExpression 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.
RoutesGenerator.NormalizeTemplate (cognitive 17) src/Rask.Generators/RoutesGenerator.Model.cs:120— RoutesGenerator.NormalizeTemplate 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.
Parser.ReadObjectBody (cognitive 17) src/Rask.Generators/ScopedScripts/DeclarationReader.cs:767— Parser.ReadObjectBody 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.
LogScopes.Flatten (cognitive 17) src/Rask.Logging/LogScopes.cs:75— LogScopes.Flatten has cognitive complexity 17 (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.
RaskApiValidation.ValidateEndpointAsync (cognitive 17) src/Rask.Server/App/RaskApiValidation.cs:141— RaskApiValidation.ValidateEndpointAsync 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.
SqliteBusyRetry.ExecAsync (cognitive 17) src/Rask.SQLite/SqliteBusyRetry.cs:28— SqliteBusyRetry.ExecAsync 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.
ParityEditor.Run (cognitive 17) scripts/flux/Flux/Commands/ParityEditor.cs:159— ParityEditor.Run 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.
ParityFiltersBleed.Run (cognitive 17) scripts/flux/Flux/Commands/ParityFiltersBleed.cs:77— ParityFiltersBleed.Run 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.
rask-owned.replayMissed (cognitive 17) src/Rask.Core/Resources/rask-owned.ts:305— rask-owned.replayMissed has cognitive complexity 17 (threshold 15). Drivers by points: loops 3 (6 pts), error handling 1 (5 pts), if/else 2 (5 pts), boolean chains 1 (nesting depth added 10). 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.
rask-calendar.walkTimes (cognitive 17) src/Rask.Core/Resources/rask-calendar.ts:959— rask-calendar.walkTimes has cognitive complexity 17 (threshold 15). Drivers by points: ternaries 5 (11 pts), if/else 3 (4 pts), boolean chains 2 (nesting depth added 7). 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.
rask-events.document.addEventListener("click") (cognitive 17) src/Rask.Core/Resources/rask-events.ts:239— rask-events.document.addEventListener("click") has cognitive complexity 17 (threshold 15). Drivers by points: if/else 8 (10 pts), ternaries 2 (4 pts), error handling 2, boolean chains 1 (nesting depth added 4). 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.
rask-plot.write (cognitive 17) src/Rask.Core/Resources/rask-plot.ts:102— rask-plot.write has cognitive complexity 17 (threshold 15). Drivers by points: if/else 5 (9 pts), boolean chains 5, ternaries 1 (2 pts), loops 1 (nesting depth added 5). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
rask-list.picked (cognitive 17) src/Rask.Core/Resources/rask-list.ts:562— rask-list.picked has cognitive complexity 17 (threshold 15). Drivers by points: if/else 7, boolean chains 5, ternaries 1 (3 pts), loops 1 (2 pts) (nesting depth added 3). Of this number, 14 points are the body's own statements and 3 belong to one function literal inside it that branches. To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
rask.restoreOneField (cognitive 17) src/Rask.Server/Resources/rask.ts:1066— rask.restoreOneField has cognitive complexity 17 (threshold 15). Drivers by points: if/else 7 (10 pts), loops 2 (4 pts), boolean chains 2, ternaries 1 (nesting depth added 5). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
Mounted.wireSelect (cognitive 17) src/Rask.Ui/Resources/editor/ui-editor.ts:275— Mounted.wireSelect has cognitive complexity 17 (threshold 15). Drivers by points: if/else 9 (10 pts), boolean chains 4, loops 2, ternaries 1 (nesting depth added 1). None of this is in the body itself: all 17 points belong to 6 function items inside it that branch (a function literal at line 303, activate, close, …). 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.
ProblemDocument.Read (cognitive 16) src/Rask.Client.Shared/ProblemDocument.cs:22— ProblemDocument.Read 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.
ModelStateMutationAnalyzer.CanNarrow (cognitive 16) src/Rask.Batteries.Generators/Analyzers/ModelStateMutationAnalyzer.cs:185— ModelStateMutationAnalyzer.CanNarrow 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.
CqrsDispatchGenerator.GetCandidate (cognitive 16) src/Rask.Batteries.Generators/CqrsDispatchGenerator.cs:65— CqrsDispatchGenerator.GetCandidate has cognitive complexity 16 (threshold 15). Of this number, 15 points are the body's own statements and 1 belongs to one function literal inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
ModelRegistryGenerator.ValueObjectPaths (cognitive 16) src/Rask.Batteries.Generators/ModelRegistryGenerator.cs:219— ModelRegistryGenerator.ValueObjectPaths has cognitive complexity 16 (threshold 15). Of this number, 15 points are the body's own statements and 1 belongs to one function literal inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
LivePayload.WriteJsonTail (cognitive 16) src/Rask.Core/Live/LivePayload.cs:871— LivePayload.WriteJsonTail 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.
LivePayload.IndexOfBodyOpenUtf8 (cognitive 16) src/Rask.Core/Live/LivePayload.cs:1093— LivePayload.IndexOfBodyOpenUtf8 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.
RoutePattern.TryMatch (cognitive 16) src/Rask.Core/Routing/RoutePattern.cs:129— RoutePattern.TryMatch 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.
AggregateSave.StageOver (cognitive 16) src/Rask.Data/AggregateSave.cs:215— AggregateSave.StageOver 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.
Builder.AddRange (cognitive 16) src/Rask.DevTools/Probe/DevToolsTreeSnapshotter.cs:283— Builder.AddRange 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.
WebMember.Attribute (cognitive 16) src/Rask.Dom.Tasks/WebMember.cs:305— WebMember.Attribute 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.
DuplicateAddRaskAnalyzer.Analyze (cognitive 16) src/Rask.Generators/Analyzers/DuplicateAddRaskAnalyzer.cs:62— DuplicateAddRaskAnalyzer.Analyze 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.
ComponentFactoryGenerator.OverridesLifecycleHook (cognitive 16) src/Rask.Generators/ComponentFactoryGenerator.ComponentModel.cs:395— ComponentFactoryGenerator.OverridesLifecycleHook 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.
ComponentFactoryGenerator.PinSets (cognitive 16) src/Rask.Generators/ComponentFactoryGenerator.TypeParameters.cs:135— ComponentFactoryGenerator.PinSets 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.
RoutesGenerator.PathParamTypeFqn (cognitive 16) src/Rask.Generators/RoutesGenerator.Factories.cs:454— RoutesGenerator.PathParamTypeFqn 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.
MessageParser.Parse (cognitive 16) src/Rask.Generators/Translations/MessageParser.cs:42— MessageParser.Parse has cognitive complexity 16 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
TranslationCatalogGenerator.FrameworkValuesDefect (cognitive 16) src/Rask.Generators/Translations/TranslationCatalogGenerator.cs:659— TranslationCatalogGenerator.FrameworkValuesDefect 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.
JobProcessor.RunCycleAsync (cognitive 16) src/Rask.Jobs/JobProcessor.cs:329— JobProcessor.RunCycleAsync 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.
RaskEndpointExtensions.RunSocketLoop (cognitive 16) REDACTED:1822— RaskEndpointExtensions.RunSocketLoop 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.
Icons.Read (cognitive 16) REDACTED:115— Icons.Read has cognitive complexity 16 (threshold 15). Of this number, 14 points are the body's own statements and 2 belong to one function literal inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
ParityChart.PointerWalk (cognitive 16) scripts/flux/Flux/Commands/ParityChart.cs:380— ParityChart.PointerWalk 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.
analyzer_report.main (cognitive 16) scripts/lib/analyzer_report.py:25— analyzer_report.main has cognitive complexity 16 (threshold 15). Drivers by points: if/else 6 (13 pts), loops 2, boolean chains 1 (nesting depth added 7). 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.
css.read_css (cognitive 16) scripts/mdn/css.py:27— css.read_css has cognitive complexity 16 (threshold 15). Drivers by points: if/else 4 (7 pts), boolean chains 5, loops 2, ternaries 1 (2 pts) (nesting depth added 4). 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.
rask-calendar.draw (cognitive 16) src/Rask.Core/Resources/rask-calendar.ts:572— rask-calendar.draw has cognitive complexity 16 (threshold 15). Drivers by points: if/else 5 (6 pts), boolean chains 4, ternaries 2 (4 pts), loops 1 (2 pts) (nesting depth added 4). Of this number, 11 points are the body's own statements and 5 belong to 2 function literals inside it that branch. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
rask-morph.raskApplySelectSelection (cognitive 16) src/Rask.Core/Resources/rask-morph.ts:299— rask-morph.raskApplySelectSelection has cognitive complexity 16 (threshold 15). Drivers by points: if/else 6 (10 pts), loops 3 (5 pts), boolean chains 1 (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
rask-color.rgb (cognitive 16) src/Rask.Core/Resources/rask-color.ts:98— rask-color.rgb has cognitive complexity 16 (threshold 15). Drivers by points: ternaries 5 (15 pts), if/else 1 (nesting depth added 10). To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
rask-dom-payload.raskRead (cognitive 16) src/Rask.Core/Resources/rask-dom-payload.ts:19— rask-dom-payload.raskRead has cognitive complexity 16 (threshold 15). Drivers by points: if/else 6 (12 pts), boolean chains 3, loops 1 (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
rask-skeleton.boxFor (cognitive 16) src/Rask.Core/Resources/rask-skeleton.ts:78— rask-skeleton.boxFor has cognitive complexity 16 (threshold 15). Drivers by points: if/else 5 (11 pts), boolean chains 3, loops 1 (2 pts) (nesting depth added 7). 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.
Mounted.wireLink (cognitive 16) src/Rask.Ui/Resources/editor/ui-editor.ts:327— Mounted.wireLink has cognitive complexity 16 (threshold 15). Drivers by points: if/else 11, boolean chains 3, ternaries 1 (2 pts) (nesting depth added 1). None of this is in the body itself: all 16 points belong to 5 function items inside it that branch (a function literal at line 360, dismiss, a function literal at line 364, …). 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.
D22 · Internal API Consistency· `Files.Get` signals absence with a nullable value (null when absent) where its 3 sibling single-key reads use a plain value (absence must throw) · ×1
`Files.Get` signals absence with a nullable value (null when absent) where its 3 sibling single-key reads use a plain value (absence must throw) src/Rask.Storage/Files.cs:45— 3 of 4 single-key reads of `Files` return a plain value (absence must throw) (3 of 4). Siblings: Files.Url (src/Rask.Storage/Files.cs:57); Files.Share (src/Rask.Storage/Files.cs:60); Files.Download (src/Rask.Storage/Files.cs:64). Return a plain value (absence must throw) like its siblings. [rule A5]
D22 · Internal API Consistency· `Push.Send` is awaitable while an overload of the same name is synchronous · ×1
`Push.Send` is awaitable while an overload of the same name is synchronous src/Rask.WebPush/Push.cs:20— `Push` declares 1 synchronous and 1 awaitable overload(s) named `Send` (1 of 2). Siblings: Push.Send (src/Rask.WebPush/Push.cs:16). Give the awaitable overload its own name (`SendAsync`). [rule A9]
D4 · Code Duplication· Edited copy of a member (23 corresponding lines) · ×1
Edited copy of a member (23 corresponding lines) src/Rask.Dashboard/Pages/CachePage.cs:34— src/Rask.Dashboard/Pages/CachePage.cs:34-56 | src/Rask.Dashboard/Pages/StoragePage.cs:34-56 — These two members are one piece of code written twice and then edited apart: 23 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Duplicated block (43 lines × 2) src/Rask.Jobs/Job.cs:30— src/Rask.Jobs/Job.cs:30-72 | src/Rask.Outbox/OutboxMessage.cs:44-86 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (37–46 lines × 2) src/Rask.Ui/UiAutocomplete.cs:89— src/Rask.Ui/UiAutocomplete.cs:89-125 | src/Rask.Ui/UiInput.cs:45-90 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (40–42 lines × 3) src/Rask.Jobs/JobProcessor.cs:803— src/Rask.Jobs/JobProcessor.cs:803-842 | src/Rask.Mail/MailProcessor.cs:380-419 | src/Rask.Outbox/OutboxProcessor.cs:418-459 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 3 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 3 times. Read the line range as the matched WINDOW rather than a finished unit: at `src/Rask.Jobs/JobProcessor.cs:803` 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 (35 lines × 2) src/Rask.Mail/MailProcessor.cs:52— src/Rask.Mail/MailProcessor.cs:52-86 | src/Rask.Outbox/OutboxProcessor.cs:50-84 — before extracting anything, compare `src/Rask.Mail/MailProcessor.cs` and `src/Rask.Outbox/OutboxProcessor.cs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 94 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/Rask.Mail/MailProcessor.cs:52` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `src/Rask.Mail/MailProcessor.cs:51` calls `ThenBy` and `src/Rask.Outbox/OutboxProcessor.cs:49` 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 (23–33 lines × 3) src/Rask.Ui/UiAutocomplete.cs:31— src/Rask.Ui/UiAutocomplete.cs:31-63 | src/Rask.Ui/UiColorPicker.cs:49-71 | src/Rask.Ui/UiOtp.cs:88-110 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from all 3 call sites, so a change lands once. 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 (29 lines × 2) src/Rask.Generators/ComponentScopedCssGenerator.cs:72— src/Rask.Generators/ComponentScopedCssGenerator.cs:72-100 | src/Rask.Generators/ComponentScopedJsGenerator.cs:145-173 — before extracting anything, compare `src/Rask.Generators/ComponentScopedCssGenerator.cs` and `src/Rask.Generators/ComponentScopedJsGenerator.cs` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 86 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (30 lines × 2) src/Rask.Jobs/JobsOptions.cs:7— src/Rask.Jobs/JobsOptions.cs:7-36 | src/Rask.Mail/MailOptions.cs:26-55 — before extracting anything, compare `src/Rask.Jobs/JobsOptions.cs` and `src/Rask.Mail/MailOptions.cs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 69 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (25–30 lines × 2) src/Rask.Ui/UiMenuCheckbox.cs:27— src/Rask.Ui/UiMenuCheckbox.cs:27-51 | src/Rask.Ui/UiSwitch.cs:66-95 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (26 lines × 2) src/Rask.Ui/UiPillboxSearch.cs:14— src/Rask.Ui/UiPillboxSearch.cs:14-39 | src/Rask.Ui/UiSelectSearch.cs:14-39 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (24–26 lines × 2) src/Rask.Wasm/PrerenderedPageMetadata.cs:38— src/Rask.Wasm/PrerenderedPageMetadata.cs:38-61 | src/Rask.Wasm/PrerenderedPageMetadata.cs:111-136 — 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 (21–24 lines × 2) src/Rask.Jobs/JobConfiguration.cs:18— src/Rask.Jobs/JobConfiguration.cs:18-41 | src/Rask.Mail/QueuedMailConfiguration.cs:19-39 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Note first that the copies are not typed on the same thing: the declarations holding them bind `builder` to `EntityTypeBuilder<Job>` in one and `EntityTypeBuilder<QueuedMail>` in another, and the duplicated lines use it. The extracted unit therefore needs a parameter type that fits BOTH — their common supertype where they have one, or a new abstraction over them where they do not — and settling that is the step that comes BEFORE the extraction above. Where the two types are deliberately unrelated, the duplication is the price of that separation and the honest resolution is to record the decision rather than to extract.
Duplicated block (22 lines × 6) src/Rask.Ui/UiComposer.cs:85— src/Rask.Ui/UiComposer.cs:85-106 | src/Rask.Ui/UiDatePickerControl.cs:162-183 | src/Rask.Ui/UiDatetimePickerControl.cs:153-174 | src/Rask.Ui/UiSlider.cs:72-93 | src/Rask.Ui/UiTextarea.cs:57-78 | src/Rask.Ui/UiTimePicker.cs:101-122 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from all 6 call sites, so a change lands once.
Duplicated block (21–22 lines × 2) src/Rask.Templates/server/Features/Home/HomePage.cs:16— src/Rask.Templates/server/Features/Home/HomePage.cs:16-37 | src/Rask.Templates/wasm/Features/Home/HomePage.cs:12-32 — before extracting anything, compare `src/Rask.Templates/server/Features/Home/HomePage.cs` and `src/Rask.Templates/wasm/Features/Home/HomePage.cs` as WHOLE FILES: 96% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 1 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/Rask.Templates/server/Features/Home/HomePage.cs:16` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `src/Rask.Templates/server/Features/Home/HomePage.cs:16` calls `Href`, `LoginPage` and `src/Rask.Templates/wasm/Features/Home/HomePage.cs:12` does not — after which the two agree again for 5 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (21 lines × 3) src/Rask.Jobs/JobsOptions.cs:10— src/Rask.Jobs/JobsOptions.cs:10-30 | src/Rask.Mail/MailOptions.cs:29-49 | src/Rask.Outbox/OutboxOptions.cs:7-35 — before extracting anything, compare `src/Rask.Jobs/JobsOptions.cs` and `src/Rask.Mail/MailOptions.cs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 69 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (19–21 lines × 2) src/Rask.Server/Diagnostics/RaskServerDiagnostics.cs:69— src/Rask.Server/Diagnostics/RaskServerDiagnostics.cs:69-89 | src/Rask.Wasm/Diagnostics/RaskWasmDiagnostics.cs:65-83 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (21 lines × 2) src/Rask.Ui/UiCalloutLink.cs:45— src/Rask.Ui/UiCalloutLink.cs:45-65 | src/Rask.Ui/UiLink.cs:92-112 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `src/Rask.Ui/UiCalloutLink.cs:45` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (16–21 lines × 2) src/Rask.Ui/UiNavmenu.cs:39— src/Rask.Ui/UiNavmenu.cs:39-54 | src/Rask.Ui/UiPopover.cs:49-69 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `src/Rask.Ui/UiNavmenu.cs:39` 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 (17–20 lines × 3) src/Rask.Generators/Analyzers/ComponentConstructionAnalyzer.cs:36— src/Rask.Generators/Analyzers/ComponentConstructionAnalyzer.cs:36-55 | src/Rask.Generators/Analyzers/MissingKeyAnalyzer.cs:53-69 | src/Rask.Generators/Analyzers/RedundantStateHasChangedAnalyzer.cs:43-59 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from all 3 call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `src/Rask.Generators/Analyzers/ComponentConstructionAnalyzer.cs:36` 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 (17–20 lines × 2) src/Rask.Generators/ComponentScopedCssGenerator.cs:178— src/Rask.Generators/ComponentScopedCssGenerator.cs:178-197 | src/Rask.Generators/ComponentScopedJsGenerator.cs:264-280 — before extracting anything, compare `src/Rask.Generators/ComponentScopedCssGenerator.cs` and `src/Rask.Generators/ComponentScopedJsGenerator.cs` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 86 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (19 lines × 7) src/Rask.Ui/UiCalendarControl.cs:100— src/Rask.Ui/UiCalendarControl.cs:100-119 | src/Rask.Ui/UiDatePickerControl.cs:171-190 | src/Rask.Ui/UiDatetimePickerControl.cs:162-180 | src/Rask.Ui/UiMenuRadioGroup.cs:30-49 | src/Rask.Ui/UiRadioGroup.cs:60-79 | src/Rask.Ui/UiSlider.cs:81-100 | src/Rask.Ui/UiTimePicker.cs:110-129 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from all 7 call sites, so a change lands once.
Duplicated block (17–19 lines × 2) src/Rask.Logging/LogScopes.cs:84— src/Rask.Logging/LogScopes.cs:84-102 | src/Rask.Logging/LogScopes.cs:104-120 — 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/Rask.Logging/LogScopes.cs:84` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (11–17 lines × 2) src/Rask.Generators/ComponentScopedCssGenerator.cs:51— src/Rask.Generators/ComponentScopedCssGenerator.cs:51-61 | src/Rask.Generators/ComponentScopedJsGenerator.cs:99-115 — before extracting anything, compare `src/Rask.Generators/ComponentScopedCssGenerator.cs` and `src/Rask.Generators/ComponentScopedJsGenerator.cs` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 86 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (15–17 lines × 2) src/Rask.Postgres/PostgresFullTextSearchQueryInterceptor.cs:45— src/Rask.Postgres/PostgresFullTextSearchQueryInterceptor.cs:45-59 | src/Rask.SQLite.EntityFrameworkCore/FullTextSearchQueryInterceptor.cs:43-59 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (16–17 lines × 2) src/Rask.Ui/UiDatePickerControl.cs:329— src/Rask.Ui/UiDatePickerControl.cs:329-344 | src/Rask.Ui/UiDatetimePickerControl.cs:303-319 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `src/Rask.Ui/UiDatePickerControl.cs:329` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (13 lines × 10) src/Rask.Ui/UiCalendarControl.cs:100— src/Rask.Ui/UiCalendarControl.cs:100-112 | src/Rask.Ui/UiComposer.cs:94-106 | src/Rask.Ui/UiDatePickerControl.cs:171-183 | src/Rask.Ui/UiDatetimePickerControl.cs:162-174 | src/Rask.Ui/UiInput.cs:114-126 | src/Rask.Ui/UiMenuRadioGroup.cs:30-42 | src/Rask.Ui/UiRadioGroup.cs:60-72 | src/Rask.Ui/UiSlider.cs:81-93 | src/Rask.Ui/UiTextarea.cs:66-78 | src/Rask.Ui/UiTimePicker.cs:110-122 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from all 10 call sites, so a change lands once.
Duplicated block (14–16 lines × 2) src/Rask.Generators.Shared/WireShape.cs:435— src/Rask.Generators.Shared/WireShape.cs:435-450 | src/Rask.Generators.Shared/WireShape.cs:517-530 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (13 lines × 11) src/Rask.Ui/UiCalendarControl.cs:100— src/Rask.Ui/UiCalendarControl.cs:100-112 | src/Rask.Ui/UiComposer.cs:94-106 | src/Rask.Ui/UiDatePickerControl.cs:171-183 | src/Rask.Ui/UiDatetimePickerControl.cs:162-174 | src/Rask.Ui/UiInput.cs:114-126 | src/Rask.Ui/UiMenuRadioGroup.cs:30-42 | src/Rask.Ui/UiRadioGroup.cs:60-72 | src/Rask.Ui/UiSelect.cs:34-46 | src/Rask.Ui/UiSlider.cs:81-93 | src/Rask.Ui/UiTextarea.cs:66-78 | src/Rask.Ui/UiTimePicker.cs:110-122 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from all 11 call sites, so a change lands once.
Duplicated block (13 lines × 3) src/Rask.Ui/UiCheckboxGroup.cs:51— src/Rask.Ui/UiCheckboxGroup.cs:51-63 | src/Rask.Ui/UiPillbox.cs:31-43 | src/Rask.Ui/UiSelectMultiple.cs:33-45 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from all 3 call sites, so a change lands once.
Duplicated block (8 lines × 3) src/Rask.Ui/UiColorPicker.cs:206— src/Rask.Ui/UiColorPicker.cs:206-213 | src/Rask.Ui/UiDatePickerControl.cs:296-303 | src/Rask.Ui/UiDatetimePickerControl.cs:290-297 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from all 3 call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `src/Rask.Ui/UiColorPicker.cs:206` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (9–12 lines × 3) src/Rask.Site/Features/Validation/InlineAsyncValidateDemo.cs:20— src/Rask.Site/Features/Validation/InlineAsyncValidateDemo.cs:20-28 | src/Rask.Site/Features/Validation/InlineValidateDemo.cs:14-25 | src/Rask.Site/Features/Validation/ValidatableObjectDemo.cs:20-28 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from all 3 call sites, so a change lands once. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `src/Rask.Site/Features/Validation/InlineValidateDemo.cs:10` calls `FieldError`, `Select`, `Key` and `src/Rask.Site/Features/Validation/InlineAsyncValidateDemo.cs:17` 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 (10–11 lines × 2) src/Rask.Ui/UiNavmenu.cs:69— src/Rask.Ui/UiNavmenu.cs:69-78 | src/Rask.Ui/UiPopover.cs:80-90 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `src/Rask.Ui/UiNavmenu.cs:69` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (7 lines × 3) src/Rask.Batteries.Generators/AuthUserGenerator.cs:45— src/Rask.Batteries.Generators/AuthUserGenerator.cs:45-51 | src/Rask.Batteries.Generators/ModelRegistryGenerator.cs:84-90 | src/Rask.Batteries.Generators/RaskModelGenerator.cs:38-44 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from all 3 call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `src/Rask.Batteries.Generators/AuthUserGenerator.cs:45` 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 (12 lines × 3) src/Rask.Core/Components/DefaultNotFoundPage.cs:20— src/Rask.Core/Components/DefaultNotFoundPage.cs:20-31 | src/Rask.Core/Components/NavLink.cs:55-67 | src/Rask.Core/Routing/Outlet.cs:24-36 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 3 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 3 times. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (17 lines × 3) src/Rask.Jobs/JobProcessor.cs:859— src/Rask.Jobs/JobProcessor.cs:859-875 | src/Rask.Mail/MailProcessor.cs:434-450 | src/Rask.Outbox/OutboxProcessor.cs:474-490 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 3 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 3 times. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
D4 · Code Duplication· Near-duplicate member family (7 members, 14 shared lines) · ×1
Near-duplicate member family (7 members, 14 shared lines) src/Rask.Site/Features/UiDocs/Examples/HeaderInsetExample.cs:50— src/Rask.Site/Features/UiDocs/Examples/HeaderInsetExample.cs:50-72 | src/Rask.Site/Features/UiDocs/Examples/HeaderLayoutExample.cs:50-72 | src/Rask.Site/Features/UiDocs/Examples/HeaderSecondarySidebarExample.cs:67-89 | src/Rask.Site/Features/UiDocs/Examples/SidebarCollapsibleExample.cs:18-44 | src/Rask.Site/Features/UiDocs/Examples/SidebarInsetExample.cs:18-44 | src/Rask.Site/Features/UiDocs/Examples/SidebarLayoutExample.cs:18-45 | src/Rask.Site/Features/UiDocs/Examples/SidebarSecondaryHeaderExample.cs:18-45 — These 7 members are variants of one another: a block of 14 lines reported below appears in every one of them, and the pairwise near-duplicate rows they would otherwise produce are collapsed into this row. Read them as one construct written 7 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 7 times.
D4 · Code Duplication· Members sharing a duplicated core (6 members, 50+ identical tokens) · ×1
Members sharing a duplicated core (6 members, 50+ identical tokens) src/Rask.Site/Features/UiDocs/Examples/SelectCheckboxIndicatorExample.cs:8— src/Rask.Site/Features/UiDocs/Examples/SelectCheckboxIndicatorExample.cs:8-21 | src/Rask.Site/Features/UiDocs/Examples/SelectComboboxExample.cs:8-19 | src/Rask.Site/Features/UiDocs/Examples/SelectExample.cs:8-19 | src/Rask.Site/Features/UiDocs/Examples/SelectListboxExample.cs:8-19 | src/Rask.Site/Features/UiDocs/Examples/SelectMultipleExample.cs:8-21 | src/Rask.Site/Features/UiDocs/Examples/SelectSearchableExample.cs:8-19 — These 6 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 6 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 6 times.
Duplicated block (14 lines × 3) src/Rask.Site/Features/UiDocs/Examples/HeaderInsetExample.cs:23— src/Rask.Site/Features/UiDocs/Examples/HeaderInsetExample.cs:23-36 | src/Rask.Site/Features/UiDocs/Examples/HeaderLayoutExample.cs:23-36 | src/Rask.Site/Features/UiDocs/Examples/HeaderSecondarySidebarExample.cs:40-53 — before extracting anything, compare `src/Rask.Site/Features/UiDocs/Examples/HeaderInsetExample.cs` and `src/Rask.Site/Features/UiDocs/Examples/HeaderLayoutExample.cs` as WHOLE FILES: this scan already matched 8 separate duplicated blocks between them, totalling at least 70 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/Rask.Site/Features/UiDocs/Examples/HeaderInsetExample.cs:23` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
Duplicated block (13 lines × 4) src/Rask.Site/Features/UiDocs/Examples/SidebarCollapsibleExample.cs:32— src/Rask.Site/Features/UiDocs/Examples/SidebarCollapsibleExample.cs:32-44 | src/Rask.Site/Features/UiDocs/Examples/SidebarInsetExample.cs:32-44 | src/Rask.Site/Features/UiDocs/Examples/SidebarLayoutExample.cs:33-45 | src/Rask.Site/Features/UiDocs/Examples/SidebarSecondaryHeaderExample.cs:33-45 — before extracting anything, compare `src/Rask.Site/Features/UiDocs/Examples/SidebarCollapsibleExample.cs` and `src/Rask.Site/Features/UiDocs/Examples/SidebarInsetExample.cs` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 49 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/Rask.Site/Features/UiDocs/Examples/SidebarCollapsibleExample.cs:32` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `src/Rask.Site/Features/UiDocs/Examples/SidebarSecondaryHeaderExample.cs:50` calls `Class` and `src/Rask.Site/Features/UiDocs/Examples/SidebarCollapsibleExample.cs:49` 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 (12 lines × 5) src/Rask.Site/Features/UiDocs/Examples/HeaderInsetExample.cs:58— src/Rask.Site/Features/UiDocs/Examples/HeaderInsetExample.cs:58-69 | src/Rask.Site/Features/UiDocs/Examples/HeaderLayoutExample.cs:58-69 | src/Rask.Site/Features/UiDocs/Examples/HeaderSecondarySidebarExample.cs:75-86 | src/Rask.Site/Features/UiDocs/Examples/SidebarLayoutExample.cs:27-38 | src/Rask.Site/Features/UiDocs/Examples/SidebarSecondaryHeaderExample.cs:27-38 — before extracting anything, compare `src/Rask.Site/Features/UiDocs/Examples/HeaderInsetExample.cs` and `src/Rask.Site/Features/UiDocs/Examples/HeaderLayoutExample.cs` as WHOLE FILES: this scan already matched 8 separate duplicated blocks between them, totalling at least 70 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/Rask.Site/Features/UiDocs/Examples/HeaderInsetExample.cs:58` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `src/Rask.Site/Features/UiDocs/Examples/SidebarLayoutExample.cs:24` calls `Placeholder` and `src/Rask.Site/Features/UiDocs/Examples/HeaderInsetExample.cs:55` 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 (9 lines × 7) src/Rask.Site/Features/UiDocs/Examples/HeaderInsetExample.cs:62— src/Rask.Site/Features/UiDocs/Examples/HeaderInsetExample.cs:62-70 | src/Rask.Site/Features/UiDocs/Examples/HeaderLayoutExample.cs:62-70 | src/Rask.Site/Features/UiDocs/Examples/HeaderSecondarySidebarExample.cs:79-87 | src/Rask.Site/Features/UiDocs/Examples/SidebarCollapsibleExample.cs:30-38 | src/Rask.Site/Features/UiDocs/Examples/SidebarInsetExample.cs:30-38 | src/Rask.Site/Features/UiDocs/Examples/SidebarLayoutExample.cs:31-39 | src/Rask.Site/Features/UiDocs/Examples/SidebarSecondaryHeaderExample.cs:31-39 — before extracting anything, compare `src/Rask.Site/Features/UiDocs/Examples/HeaderInsetExample.cs` and `src/Rask.Site/Features/UiDocs/Examples/HeaderLayoutExample.cs` as WHOLE FILES: this scan already matched 8 separate duplicated blocks between them, totalling at least 70 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/Rask.Site/Features/UiDocs/Examples/HeaderInsetExample.cs:62` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
Duplicated block (8 lines × 6) src/Rask.Site/Features/UiDocs/Examples/SelectCheckboxIndicatorExample.cs:10— src/Rask.Site/Features/UiDocs/Examples/SelectCheckboxIndicatorExample.cs:10-17 | src/Rask.Site/Features/UiDocs/Examples/SelectComboboxExample.cs:10-17 | src/Rask.Site/Features/UiDocs/Examples/SelectExample.cs:10-17 | src/Rask.Site/Features/UiDocs/Examples/SelectListboxExample.cs:10-17 | src/Rask.Site/Features/UiDocs/Examples/SelectMultipleExample.cs:10-17 | src/Rask.Site/Features/UiDocs/Examples/SelectSearchableExample.cs:10-17 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from all 6 call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `src/Rask.Site/Features/UiDocs/Examples/SelectCheckboxIndicatorExample.cs:10` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (8 lines × 5) src/Rask.Site/Features/UiDocs/Examples/HeaderInsetExample.cs:52— src/Rask.Site/Features/UiDocs/Examples/HeaderInsetExample.cs:52-59 | src/Rask.Site/Features/UiDocs/Examples/HeaderLayoutExample.cs:52-59 | src/Rask.Site/Features/UiDocs/Examples/HeaderSecondarySidebarExample.cs:69-76 | src/Rask.Site/Features/UiDocs/Examples/SidebarCollapsibleExample.cs:20-27 | src/Rask.Site/Features/UiDocs/Examples/SidebarInsetExample.cs:20-27 — before extracting anything, compare `src/Rask.Site/Features/UiDocs/Examples/HeaderInsetExample.cs` and `src/Rask.Site/Features/UiDocs/Examples/HeaderLayoutExample.cs` as WHOLE FILES: this scan already matched 8 separate duplicated blocks between them, totalling at least 70 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/Rask.Site/Features/UiDocs/Examples/HeaderInsetExample.cs:52` 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–8 lines × 3) src/Rask.Site/Features/UiDocs/Examples/TimelineBlockExample.cs:15— src/Rask.Site/Features/UiDocs/Examples/TimelineBlockExample.cs:15-22 | src/Rask.Site/Features/UiDocs/Examples/TimelineExample.cs:16-22 | src/Rask.Site/Features/UiDocs/Examples/TimelineSubgridExample.cs:22-29 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from all 3 call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `src/Rask.Site/Features/UiDocs/Examples/TimelineBlockExample.cs:15` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (5 lines × 7) src/Rask.Site/Features/UiDocs/Examples/HeaderInsetExample.cs:55— src/Rask.Site/Features/UiDocs/Examples/HeaderInsetExample.cs:55-59 | src/Rask.Site/Features/UiDocs/Examples/HeaderLayoutExample.cs:55-59 | src/Rask.Site/Features/UiDocs/Examples/HeaderSecondarySidebarExample.cs:72-76 | src/Rask.Site/Features/UiDocs/Examples/SidebarCollapsibleExample.cs:23-27 | src/Rask.Site/Features/UiDocs/Examples/SidebarInsetExample.cs:23-27 | src/Rask.Site/Features/UiDocs/Examples/SidebarLayoutExample.cs:24-28 | src/Rask.Site/Features/UiDocs/Examples/SidebarSecondaryHeaderExample.cs:24-28 — before extracting anything, compare `src/Rask.Site/Features/UiDocs/Examples/HeaderInsetExample.cs` and `src/Rask.Site/Features/UiDocs/Examples/HeaderLayoutExample.cs` as WHOLE FILES: this scan already matched 8 separate duplicated blocks between them, totalling at least 70 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/Rask.Site/Features/UiDocs/Examples/HeaderInsetExample.cs:55` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `src/Rask.Site/Features/UiDocs/Examples/SidebarLayoutExample.cs:24` calls `Placeholder` and `src/Rask.Site/Features/UiDocs/Examples/HeaderInsetExample.cs:55` does not — after which the two agree again for 5 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 (4–5 lines × 3) src/Rask.Site/Features/UiDocs/Examples/HeaderInsetExample.cs:18— src/Rask.Site/Features/UiDocs/Examples/HeaderInsetExample.cs:18-22 | src/Rask.Site/Features/UiDocs/Examples/HeaderLayoutExample.cs:18-22 | src/Rask.Site/Features/UiDocs/Examples/HeaderSecondarySidebarExample.cs:36-39 — before extracting anything, compare `src/Rask.Site/Features/UiDocs/Examples/HeaderInsetExample.cs` and `src/Rask.Site/Features/UiDocs/Examples/HeaderLayoutExample.cs` as WHOLE FILES: this scan already matched 8 separate duplicated blocks between them, totalling at least 70 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/Rask.Site/Features/UiDocs/Examples/HeaderInsetExample.cs:18` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `src/Rask.Site/Features/UiDocs/Examples/HeaderSecondarySidebarExample.cs:36` calls `Icon` and `src/Rask.Site/Features/UiDocs/Examples/HeaderLayoutExample.cs:18` does not — after which the two agree again for 4 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (8 lines × 7) src/Rask.Site/Features/UiDocs/Examples/HeaderInsetExample.cs:75— src/Rask.Site/Features/UiDocs/Examples/HeaderInsetExample.cs:75-82 | src/Rask.Site/Features/UiDocs/Examples/HeaderLayoutExample.cs:75-82 | src/Rask.Site/Features/UiDocs/Examples/HeaderSecondarySidebarExample.cs:92-99 | src/Rask.Site/Features/UiDocs/Examples/SidebarCollapsibleExample.cs:58-65 | src/Rask.Site/Features/UiDocs/Examples/SidebarInsetExample.cs:58-65 | src/Rask.Site/Features/UiDocs/Examples/SidebarLayoutExample.cs:59-66 | src/Rask.Site/Features/UiDocs/Examples/SidebarSecondaryHeaderExample.cs:67-74 — before extracting anything, compare `src/Rask.Site/Features/UiDocs/Examples/HeaderInsetExample.cs` and `src/Rask.Site/Features/UiDocs/Examples/HeaderLayoutExample.cs` as WHOLE FILES: this scan already matched 8 separate duplicated blocks between them, totalling at least 70 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Unstable project Rask.Server src/Rask.Server/Rask.Server.csproj:1— Rask.Server has instability 0.58 with 18 dependents.
D8 · Code Coverage· No test project references Rask.Site · ×1
No test project references Rask.Site src/Rask.Site/Rask.Site.csproj— No test project in this repository references Rask.Site (969 production source file(s)), so `dotnet test` never loads it and no coverage tool can measure it — its code is absent from the 75.8% above rather than counted at zero. This is the whole assembly, not a gap within one: add a test project that references it (or a ProjectReference from an existing suite) and its coverage starts being measured.
D8 · Code Coverage· No test project references Flux · ×1
No test project references Flux scripts/flux/Flux/Flux.csproj— No test project in this repository references Flux (56 production source file(s)), so `dotnet test` never loads it and no coverage tool can measure it — its code is absent from the 75.8% above rather than counted at zero. This is the whole assembly, not a gap within one: add a test project that references it (or a ProjectReference from an existing suite) and its coverage starts being measured.
D8 · Code Coverage· No test project references KitBundle · ×1
No test project references KitBundle scripts/tools/KitBundle/KitBundle.csproj— No test project in this repository references KitBundle (14 production source file(s)), so `dotnet test` never loads it and no coverage tool can measure it — its code is absent from the 75.8% above rather than counted at zero. This is the whole assembly, not a gap within one: add a test project that references it (or a ProjectReference from an existing suite) and its coverage starts being measured.
D8 · Code Coverage· No test project references Rask.Site.DataDemo · ×1
No test project references Rask.Site.DataDemo src/Rask.Site.DataDemo/Rask.Site.DataDemo.csproj— No test project in this repository references Rask.Site.DataDemo (7 production source file(s)), so `dotnet test` never loads it and no coverage tool can measure it — its code is absent from the 75.8% above rather than counted at zero. This is the whole assembly, not a gap within one: add a test project that references it (or a ProjectReference from an existing suite) and its coverage starts being measured.
D8 · Code Coverage· No test project references RaskRename · ×1
No test project references RaskRename scripts/tools/RaskRename/RaskRename.csproj— No test project in this repository references RaskRename (1 production source file(s)), so `dotnet test` never loads it and no coverage tool can measure it — its code is absent from the 75.8% above rather than counted at zero. This is the whole assembly, not a gap within one: add a test project that references it (or a ProjectReference from an existing suite) and its coverage starts being measured.
DM10 · One transaction, one aggregate· One operation mutates 2 aggregates · ×1
One operation mutates 2 aggregates: FileStore.SaveCoreAsync src/Rask.Storage/FileStore.cs:173— `FileStore.SaveCoreAsync` saves `DatabaseBlobBackend`, `DbSet` in a single operation. Each is its own consistency boundary, so committing them together makes the second's invariants depend on the first's transaction, holds a lock across both for the whole operation, and means the pair can no longer be separated — into different services, or different databases. Mutate one aggregate here and let the others follow from a domain event.
Condition was already decided — an earlier guard makes this test constant src/Rask.Core/Forms/EditContext.Validation.cs:16— Control only reaches here when `state.Messages.Count > 0` is false, because the guard on line 8 exits otherwise. This test is therefore always false and everything it guards is unreachable. Implement the distinction that was intended, or delete the test.
Hollow method — returns a constant without doing the work src/Rask.Wasm/JSInterop.cs:350— `ReadFileChunkAsync` looks like it should compute a result but its body just returns a constant — a placeholder return that was never filled in.
P12 · CI test-gate honesty· Tests run only outside the merge gate · ×1
Tests run only outside the merge gate REDACTED:230— `scripts/flux/parity-all.sh | tee "$RUNNER_TEMP/parity.log"` is the only CI command that runs 2 test(s) (e.g. FluxParityPages.Every_parity_page_is_written_for_the_browser_to_measure, FluxParityPages.Every_layout_demo_is_written_as_a_document_of_its_own), and the workflow runs only on a schedule — a failure there is found after the change merged, when the only remedy is a revert. Run them on pull requests (or in the merge queue).
Duplication concentrated across 3 sibling directories (13 clone groups) src/Rask.Server/Resources/rask.ts:1687— 13 duplicated blocks under src/ have copies in at least two of the sibling directories Rask.Core, Rask.Server, Rask.Wasm — 10 of them are reported below, and 3 are counted here but not reported individually: those copies match on shape but no longer clear R10's bar for an individually reported row — either they kept neither their own names nor their values, or what was copied is too small to stand on its own (it reports near-exact duplication only, and only of substantial extent). What this row states is the concentration, which the detector measured over all 13 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 13 local ones: the siblings replicate behaviour none of them owns, which is the shape of a missing shared module — a common library every sibling imports — rather than 13 separate extractions. Check first whether the siblings are deliberately standalone deliverables (scaffold templates, demo apps that must stay copy-pasteable); where they are, the duplication is the design and the per-block rows are the ones to act on.
Duplicated block (28 lines × 2 locations) src/Rask.Server/Resources/rask.ts:1687— src/Rask.Server/Resources/rask.ts:1687 · src/Rask.Wasm/Resources/rask.wasm.ts:490 — 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 (19 lines × 2 locations) src/Rask.Server/Resources/rask.ts:295— src/Rask.Server/Resources/rask.ts:295 · src/Rask.Wasm/Resources/rask-wasm-auth.ts:74 — 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 × 2 locations) src/Rask.Core/Resources/browser/auth.ts:211— src/Rask.Core/Resources/browser/auth.ts:211 · src/Rask.Core/Resources/browser/auth.ts:281 — 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 × 2 locations) src/Rask.Server/Resources/rask.ts:114— src/Rask.Server/Resources/rask.ts:114 · src/Rask.Wasm/Resources/rask.wasm.ts:73 — 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 (13 lines × 2 locations) src/Rask.Core/Resources/rask-carousel.ts:308— src/Rask.Core/Resources/rask-carousel.ts:308 · src/Rask.Core/Resources/rask-carousel.ts:322 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
R10 · Code Duplication· Duplicated block with local edits (13 matched lines × 2 locations) · ×1
Duplicated block with local edits (13 matched lines × 2 locations) src/Rask.Core/Resources/rask-requires.ts:33— src/Rask.Core/Resources/rask-requires.ts:33 · src/Rask.Core/Resources/rask-toast.ts:81 — the two spans are one implementation copied and then locally edited — 77 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one.
R10 · Code Duplication· Duplicated block with local edits (11 matched lines × 2 locations) · ×1
Duplicated block with local edits (11 matched lines × 2 locations) REDACTED:881— REDACTED:881 · src/Rask.Core/Resources/rask-owned.ts:350 — the two spans are one implementation copied and then locally edited — 55 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one.
Duplicated block (8 lines × 3 locations) src/Rask.Core/Resources/rask-color.ts:265— src/Rask.Core/Resources/rask-color.ts:265 · src/Rask.Core/Resources/rask-command.ts:60 · src/Rask.Core/Resources/rask-tabs.ts:88 — the 3 copies sit in sibling files in one directory, so check first whether one of them (or an existing module there) already owns this behaviour and the others should call it; otherwise extract it into one module in that directory and have each site call it. There is one copy in each of 3 separate files rather than several in one place, so check first whether these are sibling modules that each declare their own version of one shape — one per entity, per provider, per language. Where they are, no single extracted module collapses them: each module still has to be written, and what recurs is the TEMPLATE. The moves that do collapse a template are to generate these modules from the set they enumerate, or to replace the repeated construction with one factory each site calls with its own values — and where the set is the point, each module pinning one distinct thing, the repetition IS the enumeration and there is nothing to delete.
Duplicated block (7 lines × 3 locations) src/Rask.Core/Resources/browser/auth.ts:382— src/Rask.Core/Resources/browser/auth.ts:382 · src/Rask.Core/Resources/browser/webAuthn.ts:94 · src/Rask.Core/Resources/rask-api.ts:259 — 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.
R10 · Code Duplication· Duplicated block with local edits (7 matched lines × 2 locations) · ×1
Duplicated block with local edits (7 matched lines × 2 locations) src/Rask.Core/Resources/rask-persist.ts:72— src/Rask.Core/Resources/rask-persist.ts:72 · src/Rask.Core/Resources/rask-plot.ts:318 — the two spans are one implementation copied and then locally edited — 57 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one.
Duplicated block (6 lines × 2 locations) src/Rask.Core/Resources/rask-color.ts:583— src/Rask.Core/Resources/rask-color.ts:583 · src/Rask.Core/Resources/rask-color.ts:645 — 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.
Complex function morphNode (cyclomatic 95, cognitive 148) src/Rask.Core/Resources/rask-morph.ts:583— morphNode has cyclomatic complexity 95 and cognitive complexity 148; 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.
Complex function (anonymous) (cyclomatic 52, cognitive 57) src/Rask.Core/Resources/rask-list.ts:827— (anonymous) has cyclomatic complexity 52 and cognitive complexity 57; 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.
Complex function applyOps (cyclomatic 43, cognitive 96) REDACTED:199— applyOps has cyclomatic complexity 43 and cognitive complexity 96; 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.
Complex function draw (cyclomatic 38, cognitive 68) src/Rask.Core/Resources/rask-color.ts:314— draw has cyclomatic complexity 38 and cognitive complexity 68; 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.
Complex function (anonymous) (cyclomatic 35, cognitive 32) src/Rask.Core/Resources/rask-list.ts:761— (anonymous) has cyclomatic complexity 35 and cognitive complexity 32; 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 (anonymous) (cyclomatic 34, cognitive 40) src/Rask.Core/Resources/rask-calendar.ts:1036— (anonymous) has cyclomatic complexity 34 and cognitive complexity 40; 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.
Complex function paintDay (cyclomatic 33, cognitive 36) src/Rask.Core/Resources/rask-calendar.ts:447— paintDay has cyclomatic complexity 33 and cognitive complexity 36; 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.
Complex function handle (cyclomatic 30, cognitive 40) src/Rask.Ui/Resources/phone/ui-phone.ts:397— handle has cyclomatic complexity 30 and cognitive complexity 40; 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.
Complex function cursorKey (cyclomatic 29, cognitive 32) src/Rask.Core/Resources/rask-menu-keys.ts:78— cursorKey has cyclomatic complexity 29 and cognitive complexity 32; 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.
Complex function maskMoney (cyclomatic 28, cognitive 30) src/Rask.Core/Resources/rask-field.ts:67— maskMoney has cyclomatic complexity 28 and cognitive complexity 30; 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.
Complex function (anonymous) (cyclomatic 27, cognitive 32) src/Rask.Core/Resources/rask-menu-keys.ts:142— (anonymous) has cyclomatic complexity 27 and cognitive complexity 32; 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.
Complex function (anonymous) (cyclomatic 27, cognitive 23) src/Rask.Core/Resources/rask-keys.ts:56— (anonymous) has cyclomatic complexity 27 and cognitive complexity 23; 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 parseAbsolute (cyclomatic 26, cognitive 39) tests/Rask.TestSupport/ScriptFixtures/web-globals.js:699— parseAbsolute has cyclomatic complexity 26 and cognitive complexity 39; 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.
Complex function onFrame (cyclomatic 26, cognitive 35) src/Rask.Server/Resources/rask.ts:593— onFrame has cyclomatic complexity 26 and cognitive complexity 35; 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.
Complex function (anonymous) (cyclomatic 26, cognitive 30) src/Rask.Core/Resources/rask-plot.ts:167— (anonymous) has cyclomatic complexity 26 and cognitive complexity 30; 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.
Complex function (anonymous) (cyclomatic 24, cognitive 26) src/Rask.Core/Resources/rask-api.ts:120— (anonymous) has cyclomatic complexity 24 and cognitive complexity 26; 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.
Complex function commit (cyclomatic 22, cognitive 28) src/Rask.Server/Resources/rask.ts:1724— commit has cyclomatic complexity 22 and cognitive complexity 28; 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.
Complex function formatDay (cyclomatic 21, cognitive 47) src/Rask.Core/Resources/rask-calendar.ts:177— formatDay has cyclomatic complexity 21 and cognitive complexity 47; 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.
Complex function (anonymous) (cyclomatic 21, cognitive 16) src/Rask.Core/Resources/rask-field.ts:239— (anonymous) has cyclomatic complexity 21 and cognitive complexity 16; 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 (anonymous) (cyclomatic 20, cognitive 25) src/Rask.Core/Resources/rask-color.ts:583— (anonymous) has cyclomatic complexity 20 and cognitive complexity 25; 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/Rask.Server/Resources/rask.ts · ×1
src/Rask.Server/Resources/rask.ts: 2024 lines of code src/Rask.Server/Resources/rask.ts:1— src/Rask.Server/Resources/rask.ts has 2024 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: 1327 lines of code REDACTED:1— REDACTED has 1327 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/Rask.Core/Resources/rask-calendar.ts · ×1
src/Rask.Core/Resources/rask-calendar.ts: 1101 lines of code src/Rask.Core/Resources/rask-calendar.ts:1— src/Rask.Core/Resources/rask-calendar.ts has 1101 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/Rask.Core/Resources/rask-list.ts · ×1
src/Rask.Core/Resources/rask-list.ts: 878 lines of code src/Rask.Core/Resources/rask-list.ts:1— src/Rask.Core/Resources/rask-list.ts has 878 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/Rask.Wasm/Resources/rask.wasm.ts · ×1
src/Rask.Wasm/Resources/rask.wasm.ts: 802 lines of code src/Rask.Wasm/Resources/rask.wasm.ts:1— src/Rask.Wasm/Resources/rask.wasm.ts has 802 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/Rask.Core/Resources/rask-morph.ts · ×1
src/Rask.Core/Resources/rask-morph.ts: 795 lines of code src/Rask.Core/Resources/rask-morph.ts:1— src/Rask.Core/Resources/rask-morph.ts has 795 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/Rask.Core/Resources/rask-color.ts · ×1
src/Rask.Core/Resources/rask-color.ts: 604 lines of code src/Rask.Core/Resources/rask-color.ts:1— src/Rask.Core/Resources/rask-color.ts has 604 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/Rask.Core/Resources/rask-api.ts · ×1
src/Rask.Core/Resources/rask-api.ts: 547 lines of code src/Rask.Core/Resources/rask-api.ts:1— src/Rask.Core/Resources/rask-api.ts has 547 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/Rask.Core/Resources/rask-owned.ts · ×1
src/Rask.Core/Resources/rask-owned.ts: 485 lines of code src/Rask.Core/Resources/rask-owned.ts:1— src/Rask.Core/Resources/rask-owned.ts has 485 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/Rask.Core/Resources/rask-input.ts · ×1
src/Rask.Core/Resources/rask-input.ts: 441 lines of code src/Rask.Core/Resources/rask-input.ts:1— src/Rask.Core/Resources/rask-input.ts has 441 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/Rask.Server/Resources/rask-http-transport.ts · ×1
src/Rask.Server/Resources/rask-http-transport.ts: 436 lines of code src/Rask.Server/Resources/rask-http-transport.ts:1— src/Rask.Server/Resources/rask-http-transport.ts has 436 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: 434 lines of code REDACTED:1— REDACTED has 434 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/Rask.Core/Resources/rask-segments.ts · ×1
src/Rask.Core/Resources/rask-segments.ts: 432 lines of code src/Rask.Core/Resources/rask-segments.ts:1— src/Rask.Core/Resources/rask-segments.ts has 432 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/Rask.Ui/Resources/phone/ui-phone.ts · ×1
src/Rask.Ui/Resources/phone/ui-phone.ts: 421 lines of code src/Rask.Ui/Resources/phone/ui-phone.ts:1— src/Rask.Ui/Resources/phone/ui-phone.ts has 421 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/Rask.Core/Resources/browser/auth.ts · ×1
src/Rask.Core/Resources/browser/auth.ts: 411 lines of code src/Rask.Core/Resources/browser/auth.ts:1— src/Rask.Core/Resources/browser/auth.ts has 411 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
Sync-over-async (deadlock risk) through `.Wait(…)` src/Rask.Core/AppCapture.cs:53— `.Wait(…)` blocks this thread until the task completes or the bound expires — sync-over-async: it can deadlock under a synchronization context and it parks a thread while it waits. `await` the task (with `.WaitAsync(timeout, token)` where the bound matters).
Sync-over-async (deadlock risk) through `.Result` scripts/flux/Flux/Lib/Runtime.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.
X14 · Bypassable address classification· IP classification is bypassable through an IPv4-in-IPv6 embedding · ×1
IP classification is bypassable through an IPv4-in-IPv6 embedding src/Rask.WebPush/PushConnection.cs:35— This method unwraps IPv4-MAPPED IPv6 (`IsIPv4MappedToIPv6`, line 30) and then rejects `10.0.0.0/8` on its IPv4 path — but the IPv6 branch at line 35 classifies the address as written, and IPv4 reaches IPv6 through three MORE embeddings this method never mentions: IPv4-compatible (`::a.b.c.d`), 6to4 (`2002::/16`) and NAT64 (`64:ff9b::/96`). So `::10.0.0.1`, `2002:0a00:0001::` and `64:ff9b::10.0.0.0` all name a host inside `10.0.0.0/8` — the range this same method declares non-public — and all reach the IPv6 branch un-unwrapped, taking the opposite verdict. Unwrap every embedding to its IPv4 form before classifying, or reject any IPv6 address carrying an embedded IPv4 outright.
X18 · Disposal-pattern correctness· Release token given back after an unprotected call · ×1
Release token given back after an unprotected call src/Rask.Core/Globalization/RaskCultureScope.cs:96— `_inner` is declared `IDisposable` and nothing more, and every assignment to it takes a constructor parameter — so `PinnedScope` can do exactly one thing with it, which is the release performed here (line 96), and it is the only reference left that can perform it. That release is the tail of an unprotected sequence: `ReferenceEquals(CultureInfo.CurrentUICulture, _uiCulture)` runs first (line 91), and nothing in `Dispose` catches it. A single throw from that call skips the release entirely — and because a bare `IDisposable` carries no state to inspect and no second holder to fall back on, whatever it represents (a lock taken for this instance, a semaphore lease, a scope) is then held for the remaining lifetime of the process, with nothing left that could ever give it back. Wrap the calls that precede it in a `try` and move the release into the `finally`, so the one statement that must happen is the one that always happens.
X18 · Disposal-pattern correctness· Owned disposable field overwritten without releasing the previous instance · ×1
Owned disposable field overwritten without releasing the previous instance src/Rask.Jobs/JobProcessor.cs:193— `_grace` is a `CancellationTokenSource` this type creates itself, and here (line 193) a new instance is written over it — but `JobProcessor` creates `_grace` when it is constructed, so every later call finds an instance there, and nothing earlier in `ExecuteAsync` disposes, closes, saves or hands on the instance being replaced. The assignment makes it unreachable while it still holds what it holds (a timer that keeps firing, a callback registered on a longer-lived token, a socket, a handle), and no later `Dispose` can reach it: the type's own disposal releases only the CURRENT instance. The cost accumulates once per overwrite. Release the previous instance first (`_grace?.Dispose();` before the assignment), or swap it out with `Interlocked.Exchange` and dispose what comes back.
X18 · Disposal-pattern correctness· DI scope created and never disposed · ×1
DI scope created and never disposed src/Rask.Testing/Page.Visit.cs:56— `app.Services.CreateScope()` (line 56) creates an `IServiceScope`, and it is dropped: `CreateScope().ServiceProvider` never names the scope, so nothing can release it. A scope owns every scoped service resolved from it — the `DbContext`, its connection, anything registered `AddScoped` — and releases them only when the scope itself is disposed; nothing here ever does, so each scope's services stay alive until the process ends. Create it with `using var scope = …CreateScope();` (or `await using` for `CreateAsyncScope`), or, when it must outlive the method, dispose it from the owning type's `Dispose`.
Return leaves holding the primitive src/Rask.Server/LiveSession.cs:713— `Lock.WaitAsync(CancellationToken.None)` has already taken `Lock` when this `return` leaves, and the `finally` that calls `Lock.Release()` belongs to the `try` below it, so it never runs: `Lock` stays held and every later waiter blocks. Move the `return` inside the `try`, or take `Lock` after it.
X5 · Nullable reference types· Symbol treated as nullable, then dereferenced unguarded · ×1
Symbol treated as nullable, then dereferenced unguarded src/Rask.Jobs/JobPrincipal.cs:44— This method contradicts itself about `principal`: line 39 writes `principal?.`, which says `principal` can be null, but line 44 then dereferences it directly as `principal.Claims` with no null test between them and no guard around it. If the `?.` is right, that dereference throws NullReferenceException on the input it was written for; if `principal` truly cannot be null here, the `?.` is misleading. Settle it one way — test `principal` once before the first use and handle the null case, or drop the `?.` — rather than leaving the two readings side by side.
Silent fallback default in catch src/Rask.Auth.Api/AccountService.cs:205— `InsertAsync` swallows `DbUpdateException` into `return false;` — a data error becomes a silent behavior change with no trail. Log the failure or let validation throw.
Silent fallback default in catch src/Rask.Auth.Api/AuthTokens.cs:70— `IsValid` swallows `Exception` into `return false;` — a data error becomes a silent behavior change with no trail. Log the failure or let validation throw.
Silent fallback default in catch src/Rask.Auth.Api/CoseKey.cs:96— `Verify` swallows `CryptographicException` into `return false;` — a data error becomes a silent behavior change with no trail. Log the failure or let validation throw.
Silent fallback default in catch src/Rask.Auth.Api/PasswordHasher.cs:141— `VerifyPbkdf2` swallows `FormatException` into `return PasswordCheck.Failed;` — a data error becomes a silent behavior change with no trail. Log the failure or let validation throw.
Silent fallback default in catch src/Rask.Auth.Api/PasswordHasher.cs:173— `VerifyBcrypt` swallows `Exception` into `return PasswordCheck.Failed;` — a data error becomes a silent behavior change with no trail. Log the failure or let validation throw.
Silent fallback default in catch src/Rask.Auth.Api/PasswordHasher.cs:199— `VerifyIdentityV3` swallows `FormatException` into `return PasswordCheck.Failed;` — a data error becomes a silent behavior change with no trail. Log the failure or let validation throw.
Silent fallback default in catch src/Rask.Cli/BuildxProbe.cs:55— `CheckAsync` swallows `Win32Exception` into `return BuildxStatus.Missing;` — a data error becomes a silent behavior change with no trail. Log the failure or let validation throw.
Silent fallback default in catch src/Rask.Cli/Commands/DbCommand.Backup.cs:244— `BackupLocalAsync` swallows `SqliteException` into `return 1;` — a data error becomes a silent behavior change with no trail. Log the failure or let validation throw.
Silent fallback default in catch src/Rask.Cli/Commands/DbCommand.Backup.cs:352— `RestoreStoredFilesAsync` swallows `Exception` into `return false;` — a data error becomes a silent behavior change with no trail. Log the failure or let validation throw.
Silent fallback default in catch src/Rask.Cli/Commands/DbCommand.Backup.cs:378— `ReplaceDatabaseAsync` swallows `SqliteException` into `return false;` — a data error becomes a silent behavior change with no trail. Log the failure or let validation throw.
Silent fallback default in catch src/Rask.Cli/Dev/DevCertificates.cs:260— `NeedsReissue` swallows `CryptographicException` into `return true;` — a data error becomes a silent behavior change with no trail. Log the failure or let validation throw.
Silent fallback default in catch src/Rask.Cli/Dev/DevHostSetup.cs:308— `IsTrustedAsync` swallows `CryptographicException` into `return false;` — a data error becomes a silent behavior change with no trail. Log the failure or let validation throw.
Silent fallback default in catch src/Rask.Cli/Dev/LinuxDevHostPlatform.cs:99— `IsTrustedAsync` swallows `CryptographicException` into `return false;` — a data error becomes a silent behavior change with no trail. Log the failure or let validation throw.
Silent fallback default in catch src/Rask.Cli/Dev/LinuxDevHostPlatform.cs:331— `HasCertutilAsync` swallows `System.ComponentModel.Win32Exception` into `return false;` — a data error becomes a silent behavior change with no trail. Log the failure or let validation throw.
Silent fallback default in catch src/Rask.Cli/DevTarget.cs:95— `Classify` swallows `IOException` into `return DevTemplateKind.Unknown;` — a data error becomes a silent behavior change with no trail. Log the failure or let validation throw.
Silent fallback default in catch src/Rask.Cli/DevTarget.cs:179— `ReadOrEmpty` swallows `IOException` into `return string.Empty;` — a data error becomes a silent behavior change with no trail. Log the failure or let validation throw.
Silent fallback default in catch src/Rask.Cli/DevTarget.cs:261— `SafeListFiles` swallows `IOException` into `return [];` — a data error becomes a silent behavior change with no trail. Log the failure or let validation throw.
Silent fallback default in catch src/Rask.Cli/DockerProbe.cs:29— `EnsureLocalAsync` swallows `Win32Exception` and sets `exitCode = -1;` — a data error becomes a silent behavior change with no trail. Log the failure or let validation throw.
Silent fallback default in catch src/Rask.Cli/DockerProbe.cs:64— `EnsureBuildxAsync` swallows `Win32Exception` and sets `version = string.Empty;` — a data error becomes a silent behavior change with no trail. Log the failure or let validation throw.
Silent fallback default in catch src/Rask.Core/Browser/SignalingInterop.cs:81— `ParsePeers` swallows `JsonException` into `return [];` — a data error becomes a silent behavior change with no trail. Log the failure or let validation throw.
Silent fallback default in catch src/Rask.Core/Components/Authorize.cs:219— `EvaluatePolicyAsync` swallows every exception and sets `allowed = false;` — a data error becomes a silent behavior change with no trail. Log the failure or let validation throw.
Silent fallback default in catch src/Rask.Core/Components/DefaultErrorPage.cs:307— `ReadSourceExcerpt` swallows every exception into `return null;` — a data error becomes a silent behavior change with no trail. Log the failure or let validation throw.
Silent fallback default in catch src/Rask.Core/Forms/FieldPath.cs:103— `Read` swallows every exception into `return null;` — a data error becomes a silent behavior change with no trail. Log the failure or let validation throw.
Silent fallback default in catch src/Rask.Core/Forms/ModelGraphWalker.cs:216— `StepInto` swallows every exception into `return null;` — a data error becomes a silent behavior change with no trail. Log the failure or let validation throw.
Silent fallback default in catch src/Rask.Core/Globalization/CurrencyMarks.cs:112— `RegionCurrency` swallows `ArgumentException` into `return "";` — a data error becomes a silent behavior change with no trail. Log the failure or let validation throw.
redundant comment scripts/flux/Flux/Commands/ParityCarousel.cs:199— "A click, or a tap on a phone." repeats the code it sits on: 3 of its 3 words (click, tap, phone) are already in `Task Hit(ILocator target, float? timeout = null) => phone`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
redundant comment scripts/flux/Flux/Commands/ParityCommand.cs:158— "A press is a tap on a phone." repeats the code it sits on: 3 of its 3 words (press, tap, phone) are already in `Task Press(IElementHandle? el) => view.Phone ? el!.TapAsync() : el!.ClickAsync();`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
redundant comment scripts/flux/Flux/Commands/ParityEditor.cs:258— "A click, or a tap on a phone." repeats the code it sits on: 3 of its 3 words (click, tap, phone) are already in `private Task Hit(ILocator target) => phone ? target.TapAsync() : target.ClickAsync();`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
redundant comment scripts/flux/Flux/Commands/ParityModal.cs:891— "`String(value)`, and `value ?? '(absent)'`." repeats the code it sits on: 3 of its 3 words (string, value, absent) are already in `private static string Absent(JsonObject? facts, string key) => facts?[key] is { } value ? JsString.Of(value) : "(absent) …`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
redundant comment scripts/tools/KitBundle/BundleFiles.cs:133— ""node_modules/a/node_modules/@b/c" -> "@b/c"; "data/x" -> "x"." repeats the code it sits on: 3 of its 3 words (node, modules, data) are already in `private static string Name(string path)`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
redundant comment src/Rask.Batteries.Generators/CurrentRowsGenerator.cs:201— "The one class that says the marker, or null — with RASK113 when more than one does." repeats the code it sits on: 5 of its 6 words (says, marker, null, rask, 113) are already in `private static Found? One(SourceProductionContext context, System.Collections.Generic.List<Found> all, string marker, st …`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
redundant comment src/Rask.Cqrs.Server/UploadSessionStore.cs:105— "The caller's session for this id, opened if it is new and the caller has room for another." repeats the code it sits on: 5 of its 6 words (caller, session, id, opened, new) are already in `private UploadSession Open(string owner, string uploadId, CqrsServerOptions options)`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
redundant comment src/Rask.Data/ReplacedChildren.cs:80— "Each collection of children `holder` holds, at any depth." repeats the code it sits on: 4 of its 5 words (collection, children, holder, depth) are already in `private static void MatchHeld(`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
redundant comment src/Rask.Dom.Tasks/DomEventEmitter.cs:318— "How the payload constructor reads a member off the JSON." repeats the code it sits on: 4 of its 5 words (payload, reads, member, json) are already in `private static string ReadExpression(Member m) => m.Kind switch`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
redundant comment src/Rask.Generators.Shared/GeneratedModelShape.cs:452— "The expression a getter returns: `=> x`, `get => x` or `get { return x; }`. Null for any other body." repeats the code it sits on: 7 of its 7 words (expression, getter, returns, get, return, null, body) are already in `private static ExpressionSyntax? Returned(PropertyDeclarationSyntax declaration)`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
redundant comment src/Rask.Generators.Shared/ReadModelShape.cs:108— "A collection of values, the columns of a value object, or one plain column." repeats the code it sits on: 6 of its 7 words (collection, values, columns, value, object, column) are already in `private static void AddMember(`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
redundant comment src/Rask.Generators/Translations/PluralRules.cs:156— "Latvian: zero (n%10==0 or n%100 in 11..19), one (n%10==1 && n%100!=11), other." repeats the code it sits on: 6 of its 6 words (latvian, zero, 10, 100, 11, 19) are already in `private static Rule Latvian => new(`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
redundant comment src/Rask.Generators/Translations/TranslationCatalogGenerator.cs:617— "Every key a framework-strings catalog names has to be one of Rask's own, and plain text." repeats the code it sits on: 7 of its 8 words (key, framework, strings, catalog, names, plain, text) are already in `private static bool FrameworkKeysValid(SourceProductionContext spc, List<Catalog> ordered)`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
redundant comment src/Rask.SQLite.EntityFrameworkCore/FullTextSearchQueryInterceptor.cs:311— "The one search of the owner's type in this query: the match the function marks." repeats the code it sits on: 6 of its 7 words (search, owner, type, query, match, marks) are already in `private Expression SingleMatch(string name, Type owner, string member)`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
redundant comment src/Rask.SQLite.EntityFrameworkCore/FullTextSearchQueryInterceptor.cs:331— "f is the owner's index row and matches the search: f.rowid == owner's rowid && f.index == @match" repeats the code it sits on: 7 of its 7 words (owner, index, row, matches, search, rowid, match) are already in `private static BinaryExpression IndexRowOf(Index index, ParameterExpression f, Expression owner, Expression match)`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
redundant comment src/Rask.SQLite.EntityFrameworkCore/RangeExclusionDdl.cs:177— "The soft-delete column a rule that ignores deleted rows reads, or null when the rule counts every row." repeats the code it sits on: 9 of its 11 words (soft, delete, column, rule, ignores, deleted, rows, null, row) are already in `private static string? DeletedAtColumn(IEntityType entityType, RangeExclusionSpec spec, StoreObjectIdentifier store)`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
redundant comment src/Rask.SQLite.Litestream/LitestreamVerifier.cs:119— "Restores the replica until the sentinel shows up, the restore fails, or the time budget runs out." repeats the code it sits on: 8 of its 10 words (restores, replica, until, sentinel, restore, fails, time, runs) are already in `private async Task<LitestreamVerificationStatus> RestoreUntilSentinelAsync(`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
redundant comment REDACTED:1403— "A stream nothing of ours closed ended with the browser's request, or with the drain's deadline." repeats the code it sits on: 7 of its 8 words (stream, closed, ended, browser, request, drain, deadline) are already in `private static void NoteStreamEnd(ConnectionRecord connection, CancellationToken hardStopping)`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
redundant comment src/Rask.Site/Features/Browser/CryptoDemo.cs:33— "crypto.randomUUID()" repeats the code it sits on: 3 of its 3 words (crypto, random, uuid) are already in `private async Task Uuid()`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
redundant comment src/Rask.Ui/UiDatetimePickerControl.cs:391— "A range's start and end, each with its own time field." repeats the code it sits on: 5 of its 5 words (range, start, end, time, field) are already in `private static Component RangeFields(UiDatetimeTimes times, (DateOnly? Day, TimeOnly? Time)[] ends) =>`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
redundant comment tests/Rask.Core.Tests/Routing/OutletTests.cs:23— "Leaf page itself calls Outlet(); cursor is past end of chain → empty Fragment." repeats the code it sits on: 8 of its 10 words (leaf, calls, outlet, past, end, chain, empty, fragment) are already in `var (view, state, sp) = BuildView(new[] { Route.To<LeafWithOutlet>("/leaf") });`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
redundant comment tests/Rask.Dashboard.Tests/DashboardAuthorizationTests.cs:156— "What a host does as it starts: every hosted service, once." repeats the code it sits on: 4 of its 5 words (host, starts, hosted, service) are already in `private static async Task StartAsync(DashboardHarness harness)`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
redundant comment tests/Rask.Data.Tests/TenancyThroughHeldParentTests.cs:323— "Every table of the model the filter selects FROM, in name order." repeats the code it sits on: 5 of its 6 words (table, model, selects, name, order) are already in `private static List<string> TablesAsked(DbContext read, string where) =>`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
redundant comment tests/Rask.Server.E2E.Tests/KitDrawsWithoutAskingTests.Families.cs:350— "The pointer over every part and Tab through them, which every component is put through, then its own." repeats the code it sits on: 4 of its 5 words (pointer, part, tab, component) are already in `private static Family On<TPage>(string part, params KitGesture[] own)`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
redundant comment tests/Rask.Server.E2E.Tests/RuntimeHookLockTests.cs:32— "scrollY, a paragraph's x and width, then what <html> computes to." repeats the code it sits on: 4 of its 5 words (scroll, width, html, computes) are already in `private const string Place = """`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
+ 4 more in this group — see findings.md.
DM2 · Strongly-typed ids· Primitive id on a domain type · ×26
Primitive id on a domain type: Authenticatable.TenantId src/Rask.Auth.Api/Authenticatable.cs:69— `Authenticatable.TenantId` is a raw `Guid` — give it a strongly-typed id: a dedicated single-field type wrapping the `Guid`, in whatever form your language spells that.
Primitive id on a domain type: EmailConfirmed.UserId src/Rask.Auth.Api/EmailConfirmed.cs:9— `EmailConfirmed.UserId` is a raw `Guid` — give it a strongly-typed id: a dedicated single-field type wrapping the `Guid`, in whatever form your language spells that.
Primitive id on a domain type: Passkey.UserId src/Rask.Auth.Api/Passkey.cs:22— `Passkey.UserId` is a raw `Guid` — give it a strongly-typed id: a dedicated single-field type wrapping the `Guid`, in whatever form your language spells that.
Primitive id on a domain type: PasskeyAdded.UserId src/Rask.Auth.Api/PasskeyAdded.cs:10— `PasskeyAdded.UserId` is a raw `Guid` — give it a strongly-typed id: a dedicated single-field type wrapping the `Guid`, in whatever form your language spells that.
Primitive id on a domain type: PasskeyAdded.PasskeyId src/Rask.Auth.Api/PasskeyAdded.cs:10— `PasskeyAdded.PasskeyId` is a raw `Guid` — give it a strongly-typed id: a dedicated single-field type wrapping the `Guid`, in whatever form your language spells that.
Primitive id on a domain type: PasskeyRemoved.UserId src/Rask.Auth.Api/PasskeyRemoved.cs:10— `PasskeyRemoved.UserId` is a raw `Guid` — give it a strongly-typed id: a dedicated single-field type wrapping the `Guid`, in whatever form your language spells that.
Primitive id on a domain type: PasskeyRemoved.PasskeyId src/Rask.Auth.Api/PasskeyRemoved.cs:10— `PasskeyRemoved.PasskeyId` is a raw `Guid` — give it a strongly-typed id: a dedicated single-field type wrapping the `Guid`, in whatever form your language spells that.
Primitive id on a domain type: PasswordReset.UserId src/Rask.Auth.Api/PasswordReset.cs:8— `PasswordReset.UserId` is a raw `Guid` — give it a strongly-typed id: a dedicated single-field type wrapping the `Guid`, in whatever form your language spells that.
Primitive id on a domain type: Session.UserId src/Rask.Auth.Api/Session.cs:22— `Session.UserId` is a raw `Guid` — give it a strongly-typed id: a dedicated single-field type wrapping the `Guid`, in whatever form your language spells that.
Primitive id on a domain type: SignedIn.UserId src/Rask.Auth.Api/SignedIn.cs:9— `SignedIn.UserId` is a raw `Guid` — give it a strongly-typed id: a dedicated single-field type wrapping the `Guid`, in whatever form your language spells that.
Primitive id on a domain type: SignedIn.SessionId src/Rask.Auth.Api/SignedIn.cs:9— `SignedIn.SessionId` is a raw `Guid` — give it a strongly-typed id: a dedicated single-field type wrapping the `Guid`, in whatever form your language spells that.
Primitive id on a domain type: SignedOut.UserId src/Rask.Auth.Api/SignedOut.cs:9— `SignedOut.UserId` is a raw `Guid` — give it a strongly-typed id: a dedicated single-field type wrapping the `Guid`, in whatever form your language spells that.
Primitive id on a domain type: SignedOut.SessionId src/Rask.Auth.Api/SignedOut.cs:9— `SignedOut.SessionId` is a raw `Guid` — give it a strongly-typed id: a dedicated single-field type wrapping the `Guid`, in whatever form your language spells that.
Primitive id on a domain type: UserRegistered.UserId src/Rask.Auth.Api/UserRegistered.cs:9— `UserRegistered.UserId` is a raw `Guid` — give it a strongly-typed id: a dedicated single-field type wrapping the `Guid`, in whatever form your language spells that.
Primitive id on a domain type: CacheEntry.Key src/Rask.Cache/CacheEntry.cs:19— `CacheEntry.Key` is a raw `String` — give it a strongly-typed id: a dedicated single-field type wrapping the `String`, in whatever form your language spells that.
Primitive id on a domain type: Job.UserId src/Rask.Jobs/Job.cs:62— `Job.UserId` is a raw `Guid` — give it a strongly-typed id: a dedicated single-field type wrapping the `Guid`, in whatever form your language spells that.
Primitive id on a domain type: Job.TenantId src/Rask.Jobs/Job.cs:72— `Job.TenantId` is a raw `Guid` — give it a strongly-typed id: a dedicated single-field type wrapping the `Guid`, in whatever form your language spells that.
Primitive id on a domain type: Job.WaitingKey src/Rask.Jobs/Job.cs:99— `Job.WaitingKey` is a raw `String` — give it a strongly-typed id: a dedicated single-field type wrapping the `String`, in whatever form your language spells that.
Primitive id on a domain type: QueuedMail.UserId src/Rask.Mail/QueuedMail.cs:103— `QueuedMail.UserId` is a raw `Guid` — give it a strongly-typed id: a dedicated single-field type wrapping the `Guid`, in whatever form your language spells that.
Primitive id on a domain type: QueuedMail.TenantId src/Rask.Mail/QueuedMail.cs:113— `QueuedMail.TenantId` is a raw `Guid` — give it a strongly-typed id: a dedicated single-field type wrapping the `Guid`, in whatever form your language spells that.
Primitive id on a domain type: OutboxMessage.UserId src/Rask.Outbox/OutboxMessage.cs:76— `OutboxMessage.UserId` is a raw `Guid` — give it a strongly-typed id: a dedicated single-field type wrapping the `Guid`, in whatever form your language spells that.
Primitive id on a domain type: OutboxMessage.TenantId src/Rask.Outbox/OutboxMessage.cs:86— `OutboxMessage.TenantId` is a raw `Guid` — give it a strongly-typed id: a dedicated single-field type wrapping the `Guid`, in whatever form your language spells that.
Primitive id on a domain type: StoredFile.Key src/Rask.Storage/StoredFile.cs:34— `StoredFile.Key` is a raw `String` — give it a strongly-typed id: a dedicated single-field type wrapping the `String`, in whatever form your language spells that.
Primitive id on a domain type: StoredFile.TenantId src/Rask.Storage/StoredFile.cs:45— `StoredFile.TenantId` is a raw `Guid` — give it a strongly-typed id: a dedicated single-field type wrapping the `Guid`, in whatever form your language spells that.
Primitive id on a domain type: PushSubscriber.UserId src/Rask.WebPush/PushSubscriber.cs:29— `PushSubscriber.UserId` is a raw `Guid` — give it a strongly-typed id: a dedicated single-field type wrapping the `Guid`, in whatever form your language spells that.
Duplicated predicate scripts/flux/Flux/Commands/ParityColorPicker.cs:158— `!File.Exists(file) || arg.Flag("refresh")` appears character-identically in 2 files — scripts/flux/Flux/Commands/ParityColorPicker.cs, scripts/flux/Flux/Commands/ParityPopover.cs. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate src/Rask.Dom.Tasks/RaskDomEmit.cs:51— `!File.Exists(path) || !string.Equals(File.ReadAllText(path), file.Value, StringComparison.Ordinal)` appears character-identically in 2 files — src/Rask.Dom.Tasks/RaskDomEmit.cs, src/Rask.Dom.Tasks/RaskWebEmit.cs. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate REDACTED:1417— `!IsSameOrigin(ctx.Request) || IsCrossSiteFetch(ctx.Request)` appears character-identically in 2 files — src/Rask.Server/RaskEndpointExtensions.SessionUser.cs, REDACTED. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate src/Rask.Generators/ComponentScopedCssGenerator.cs:161— `!byDirAndName.TryGetValue(key, out var matches) || matches.Count == 0` appears character-identically in 2 files — src/Rask.Generators/ComponentScopedCssGenerator.cs, src/Rask.Generators/ComponentScopedJsGenerator.cs. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate src/Rask.Batteries.Generators/ModelInputGenerator.ModelClass.cs:123— `!entity.IsChild && entity.IdTypeName is not null` appears character-identically in 3 files — src/Rask.Batteries.Generators/ModelInputGenerator.ModelClass.cs, src/Rask.Batteries.Generators/ModelInputGenerator.Rules.cs, src/Rask.Batteries.Generators/ModelInputGenerator.Writes.cs. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate src/Rask.Generators.Shared/GeneratedModelShape.cs:785— `!p.IsStatic && !p.IsIndexer && p.DeclaredAccessibility == Accessibility.Public && p.GetMethod is { DeclaredAccessibility: Accessibility.Publ…` appears character-identically in 2 files — src/Rask.Generators.Shared/AggregateShape.cs, src/Rask.Generators.Shared/GeneratedModelShape.cs. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate src/Rask.Ui/UiCalendarControl.cs:140— `Bind is null && _own.Held && EqualityComparer<T?>.Default.Equals(Value, _own.Given)` appears character-identically in 3 files — src/Rask.Ui/UiCalendarControl.cs, src/Rask.Ui/UiDatePickerControl.cs, src/Rask.Ui/UiDatetimePickerControl.cs. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate scripts/flux/Flux/Commands/Parity.cs:105— `File.Exists(fluxFile) && !arg.Flag("refresh")` appears character-identically in 4 files — scripts/flux/Flux/Commands/Parity.cs, scripts/flux/Flux/Commands/ParityMenu.cs, scripts/flux/Flux/Commands/ParityModal.cs, scripts/flux/Flux/Lib/OpenList.cs. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate src/Rask.Ui/UiCheckboxGroup.cs:72— `Id is null && Bind is null && Label is null` appears character-identically in 11 files — src/Rask.Ui/UiCheckboxGroup.cs, src/Rask.Ui/UiColorPicker.cs, src/Rask.Ui/UiComposer.cs, src/Rask.Ui/UiDatePickerControl.cs. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate src/Rask.Ui/UiEditor.cs:105— `Id is null && Bound is null && Label is null` appears character-identically in 2 files — src/Rask.Ui/UiEditor.cs, src/Rask.Ui/UiSelectControl.cs. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate src/Rask.DevTools/Panel/DevToolsPanelSession.cs:163— `InHandlerScope && LeaveRenderToTheScope()` appears character-identically in 3 files — src/Rask.DevTools/Panel/DevToolsPanelSession.cs, src/Rask.Server/LiveSession.cs, src/Rask.Wasm/WasmLiveSession.cs. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate src/Rask.Site/Features/UiDocs/Examples/TableSortableExample.cs:62— `IsSortedBy(column) && _direction == Ui.TableColumnDirection.Asc` appears character-identically in 2 files — src/Rask.Site/Features/UiDocs/Examples/TableSortableExample.cs, src/Rask.Site/Features/UiDocs/Examples/TableSteadyColumnsExample.cs. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate src/Rask.Core/Component.Handlers.cs:382— `Refusal.Find(ex) is { } refusal && Refusal.Say(refusal)` appears character-identically in 2 files — src/Rask.Core/Component.Handlers.cs, src/Rask.Core/Component.LiveEvents.cs. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate src/Rask.Site/Features/UiDocs/Examples/EditorDialogExample.cs:55— `Search is null || supplier.Name.Contains(Search, StringComparison.OrdinalIgnoreCase)` appears character-identically in 2 files — src/Rask.Site/Features/UiDocs/Examples/EditorDialogExample.cs, src/Rask.Site/Features/UiDocs/Examples/TableListPageExample.cs. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate src/Rask.Server/LiveSession.cs:488— `_disposed || (_navigator ??= Services.GetRequiredService<Navigator>()).NavigationPending` appears character-identically in 2 files — src/Rask.Server/LiveSession.cs, src/Rask.Wasm/WasmLiveSession.cs. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate src/Rask.Jobs/JobMetrics.cs:76— `_pendingGauge.Enabled || _deadLetterGauge.Enabled` appears character-identically in 3 files — src/Rask.Jobs/JobMetrics.cs, src/Rask.Mail/MailMetrics.cs, src/Rask.Outbox/OutboxMetrics.cs. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate src/Rask.Dashboard/Pages/CachePage.cs:45— `_rows.Count == 0 && _page > DashboardParts.LastPageIndex(_total, options.PageSize)` appears character-identically in 3 files — src/Rask.Dashboard/Pages/CachePage.cs, src/Rask.Dashboard/Pages/QueuePage.cs, src/Rask.Dashboard/Pages/StoragePage.cs. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate src/Rask.Generators/Analyzers/InternalRouteStringAnalyzer.cs:208— `attr.ConstructorArguments.Length > 0 && attr.ConstructorArguments[0].Value is string t` appears character-identically in 2 files — src/Rask.Generators/Analyzers/InternalRouteStringAnalyzer.cs, src/Rask.Generators/RoutesGenerator.Model.cs. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate src/Rask.Api.Generators/MinimalApi.cs:178— `char.IsLetter(value[0]) || value[0] == '_'` appears character-identically in 2 files — src/Rask.Api.Generators/MinimalApi.cs, src/Rask.Cli/Scaffolding/Identifiers.cs. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate src/Rask.Api.Generators/ApiClientGenerator.cs:763— `controller.Name.EndsWith("Controller", StringComparison.Ordinal) && controller.Name.Length > 10` appears character-identically in 2 files — src/Rask.Api.Generators/ApiClientGenerator.cs, src/Rask.Api.Generators/RouteTemplate.cs. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate src/Rask.Batteries.Generators/AuthUserGenerator.cs:58— `ctx.Node is not ClassDeclarationSyntax declaration || ctx.SemanticModel.GetDeclaredSymbol(declaration) is not INamedTypeSymbol symbol` appears character-identically in 2 files — src/Rask.Batteries.Generators/AuthUserGenerator.cs, src/Rask.Batteries.Generators/ModelRegistryGenerator.cs. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate src/Rask.Postgres/PostgresFullTextSearchQueryInterceptor.cs:184— `current is MethodCallExpression { Method: { DeclaringType: var declaring, Name: var name } } call && declaring == typeof(Queryable) && name …` appears character-identically in 2 files — src/Rask.Postgres/PostgresFullTextSearchQueryInterceptor.cs, src/Rask.SQLite.EntityFrameworkCore/FullTextSearchQueryInterceptor.cs. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate src/Rask.Generators/Analyzers/BuilderEntry.cs:422— `current is not null && current.SpecialType != SpecialType.System_Object` appears character-identically in 2 files — src/Rask.Generators/Analyzers/BuilderEntry.cs, src/Rask.Generators/ComponentFactoryGenerator.ComponentModel.cs. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate src/Rask.Jobs/JobsOptions.cs:98— `double.IsInfinity(scaled) || scaled >= MaxRetryDelay.Ticks` appears character-identically in 2 files — src/Rask.Jobs/JobsOptions.cs, src/Rask.Mail/MailOptions.cs. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate src/Rask.Jobs/JobProcessor.cs:792— `e is System.Data.Common.DbException && e.Message.Contains(column, StringComparison.OrdinalIgnoreCase)` appears character-identically in 2 files — src/Rask.Jobs/JobProcessor.cs, src/Rask.Mail/MailProcessor.cs. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Silent fallback default on parse failure src/Rask.Auth.Api/PasswordHasher.cs:248— `BcryptCost` falls back to `0` when `int.TryParse(encoded.AsSpan(4, 2), NumberStyles.None, CultureInfo.InvariantCultu…` is false, with no log or throw — a malformed value silently becomes that default. Log the input or fail validation. If that constant is the correct answer to the test rather than a stand-in for a value that could not be read, this is not a silent default: say so in a comment on the member and the row stops firing.
Silent fallback default on parse failure src/Rask.Cli/Commands/CaddyRouting.cs:34— `ParseDeployedApps` falls back to `DeployCommand.DefaultContainerPort` when `parts.Length > 4 && int.TryParse(Label(parts[4]), NumberStyles.None, CultureInfo…` is false, with no log or throw — a malformed value silently becomes that default. Log the input or fail validation. If that constant is the correct answer to the test rather than a stand-in for a value that could not be read, this is not a silent default: say so in a comment on the member and the row stops firing.
Silent fallback default on parse failure src/Rask.Cli/Commands/DbCommand.Backup.cs:191— `ExecuteFileActionAsync` returns `1` when `SshTarget.TryParse(host, out _, out var hostError)` is false, with no log or throw — a malformed value silently becomes that default. Log the input or fail validation. If that constant is the correct answer to the test rather than a stand-in for a value that could not be read, this is not a silent default: say so in a comment on the member and the row stops firing.
Silent fallback default on parse failure src/Rask.Cli/Commands/DeployCommand.Planning.cs:43— `ResolveEndpoint` returns `1` when `SiteDomains.TryParse(domainValues, out var domain, out var domainError)` is false, with no log or throw — a malformed value silently becomes that default. Log the input or fail validation. If that constant is the correct answer to the test rather than a stand-in for a value that could not be read, this is not a silent default: say so in a comment on the member and the row stops firing.
Silent fallback default on parse failure src/Rask.Cli/Commands/DeployCommand.Planning.cs:90— `ResolveRedirectsAndDns` returns `1` when `SiteDomains.TryParse(redirectValues, out var redirects, out var redirectError)` is false, with no log or throw — a malformed value silently becomes that default. Log the input or fail validation. If that constant is the correct answer to the test rather than a stand-in for a value that could not be read, this is not a silent default: say so in a comment on the member and the row stops firing.
Silent fallback default on parse failure src/Rask.Cli/StopTimeout.cs:60— `Part` falls back to `0` when `match.Groups[unit].Success` is false, with no log or throw — a malformed value silently becomes that default. Log the input or fail validation. If that constant is the correct answer to the test rather than a stand-in for a value that could not be read, this is not a silent default: say so in a comment on the member and the row stops firing.
Silent fallback default on parse failure src/Rask.Core/Routing/QueryList.cs:172— `Classify` falls back to `KeyForm.None` when `rest is ['[', .. var inside, ']'] && long.TryParse(inside, NumberStyles.None, Cu…` is false, with no log or throw — a malformed value silently becomes that default. Log the input or fail validation. If that constant is the correct answer to the test rather than a stand-in for a value that could not be read, this is not a silent default: say so in a comment on the member and the row stops firing.
Silent fallback default on parse failure src/Rask.Dashboard/Pages/QueuePage.cs:39— `Filter` falls back to `QueueFilter.Outstanding` when `Enum.TryParse<QueueFilter>(Show, ignoreCase: true, out var parsed)` is false, with no log or throw — a malformed value silently becomes that default. Log the input or fail validation. If that constant is the correct answer to the test rather than a stand-in for a value that could not be read, this is not a silent default: say so in a comment on the member and the row stops firing.
Silent fallback default on parse failure src/Rask.DevTools/Probe/DevToolsProbe.cs:449— `FrameReceived` falls back to `"?"` when `frame.ValueKind == JsonValueKind.Object && frame.TryGetProperty("type", out var …` is false, with no log or throw — a malformed value silently becomes that default. Log the input or fail validation. If that constant is the correct answer to the test rather than a stand-in for a value that could not be read, this is not a silent default: say so in a comment on the member and the row stops firing.
Silent fallback default on parse failure src/Rask.DevTools/Server/DevHostMachine.cs:27— `UnprivilegedPortStart` falls back to `1024` when `int.TryParse(File.ReadAllText(UnprivilegedPortStartPath).Trim(), CultureInfo.Inv…` is false, with no log or throw — a malformed value silently becomes that default. Log the input or fail validation. If that constant is the correct answer to the test rather than a stand-in for a value that could not be read, this is not a silent default: say so in a comment on the member and the row stops firing.
P2 · Observability· Console output used as the logging channel · ×8
Console output used as the logging channel REDACTED:539— `REDACTED` reports through `Console.Write…` at line 539 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/Rask.Wasm/WasmHostBuilder.cs:350— `src/Rask.Wasm/WasmHostBuilder.cs` reports through `Console.Write…` at line 350 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/Rask.Wasm/WasmHostBuilder.cs:371— `src/Rask.Wasm/WasmHostBuilder.cs` reports through `Console.Write…` at line 371 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/Rask.Wasm/WasmHostBuilder.cs:372— `src/Rask.Wasm/WasmHostBuilder.cs` reports through `Console.Write…` at line 372 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/Rask.Wasm/WasmHostBuilder.cs:412— `src/Rask.Wasm/WasmHostBuilder.cs` reports through `Console.Write…` at line 412 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/Rask.Wasm/WasmHostBuilder.cs:413— `src/Rask.Wasm/WasmHostBuilder.cs` reports through `Console.Write…` at line 413 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/Rask.Wasm/WasmHostBuilder.cs:415— `src/Rask.Wasm/WasmHostBuilder.cs` reports through `Console.Write…` at line 415 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/Rask.Wasm/WasmHostBuilder.cs:425— `src/Rask.Wasm/WasmHostBuilder.cs` reports through `Console.Write…` at line 425 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.
IC1 · Incompleteness & stubs· Placeholder data left in code · ×4
Placeholder data left in code src/Rask.Server/App/RaskBatteryWiring.cs:72— A placeholder e-mail address ("no-reply@example.com") is still in shipped code — its domain is reserved for documentation, so anything sent here is undeliverable by construction. Replace it with the real address, or take it from configuration.
Placeholder data left in code src/Rask.Site/Features/Elements/ElementsFormsDemo.cs:38— A placeholder value ("Jane Doe") is still in shipped code — sample/mock data that was never replaced with the real thing.
Placeholder data left in code src/Rask.Site/Features/Elements/ElementsFormsDemo.cs:40— A placeholder value ("Jane Doe") is still in shipped code — sample/mock data that was never replaced with the real thing.
Placeholder data left in code src/Rask.Site/Features/Elements/ElementsSectionsDemo.cs:33— A placeholder e-mail address ("contact@example.com") is still in shipped code — its domain is reserved for documentation, so anything sent here is undeliverable by construction. Replace it with the real address, or take it from configuration.
Hand-rolled JSON/XML parsing via regex src/Rask.Cli/Scaffolding/PackageFeed.cs:93— A regex whose pattern encodes JSON/XML syntax is parsing a structured format by hand — malformed or differently-typed content (e.g. `"amount": "5"` as a string) silently mis-parses instead of failing validation. .NET ships a real parser for it (System.Text.Json, System.Xml.Linq); use it here.
Hand-rolled JSON/XML parsing via regex src/Rask.Cli/Scaffolding/ProjectContext.cs:66— A regex whose pattern encodes JSON/XML syntax is parsing a structured format by hand — malformed or differently-typed content (e.g. `"amount": "5"` as a string) silently mis-parses instead of failing validation. .NET ships a real parser for it (System.Text.Json, System.Xml.Linq); use it here.
Hand-rolled JSON/XML parsing via regex scripts/flux/Flux/Commands/Flags.cs:177— A regex whose pattern encodes JSON/XML syntax is parsing a structured format by hand — malformed or differently-typed content (e.g. `"amount": "5"` as a string) silently mis-parses instead of failing validation. .NET ships a real parser for it (System.Text.Json, System.Xml.Linq); use it here.
Hand-rolled JSON/XML parsing via regex REDACTED:320— A regex whose pattern encodes JSON/XML syntax is parsing a structured format by hand — malformed or differently-typed content (e.g. `"amount": "5"` as a string) silently mis-parses instead of failing validation. .NET ships a real parser for it (System.Text.Json, System.Xml.Linq); use it here.
Hand-rolled JSON/XML parsing via string slicing src/Rask.Core/Live/LivePayload.cs:163— A JSON key or XML tag is located in the text with IndexOf/Split and the value cut out around it — a reordered, re-spaced or differently-typed document (e.g. `"amount": "5"` as a string) silently mis-parses instead of failing validation. .NET ships a real parser for it (System.Text.Json, System.Xml.Linq); use it here.
Hand-rolled JSON/XML parsing via string slicing src/Rask.Generators/ComponentFactoryGenerator.DocComments.cs:45— A JSON key or XML tag is located in the text with IndexOf/Split and the value cut out around it — a reordered, re-spaced or differently-typed document (e.g. `"amount": "5"` as a string) silently mis-parses instead of failing validation. .NET ships a real parser for it (System.Text.Json, System.Xml.Linq); use it here.
Hand-rolled JSON/XML parsing via string slicing src/Rask.Server/Http/ConnectionTexts.cs:31— A JSON key or XML tag is located in the text with IndexOf/Split and the value cut out around it — a reordered, re-spaced or differently-typed document (e.g. `"amount": "5"` as a string) silently mis-parses instead of failing validation. .NET ships a real parser for it (System.Text.Json, System.Xml.Linq); use it here.
Hand-rolled JSON/XML parsing via string slicing scripts/flux/Flux/Commands/ParityPopover.cs:182— A JSON key or XML tag is located in the text with IndexOf/Split and the value cut out around it — a reordered, re-spaced or differently-typed document (e.g. `"amount": "5"` as a string) silently mis-parses instead of failing validation. .NET ships a real parser for it (System.Text.Json, System.Xml.Linq); use it here.
D26 · Project Cohesion· Projects may be oversized for their cohesion · ×3
Projects may be oversized for their cohesion src/Rask.Site/Rask.Site.csproj:1— `Rask.Site` overshoots its size bounds (31344 LoC, 918 public types across 7 namespaces). 3 of 134 project(s) overshoot their size bounds, lowering Project Cohesion to 9.6/10. Review these for cohesion — split a project that spans unrelated responsibilities.
Projects may be oversized for their cohesion src/Rask.Core/Rask.Core.csproj:1— `Rask.Core(net10.0)` overshoots its size bounds (41110 LoC, 268 public types across 16 namespaces). 3 of 134 project(s) overshoot their size bounds, lowering Project Cohesion to 9.6/10. Review these for cohesion — split a project that spans unrelated responsibilities.
Projects may be oversized for their cohesion src/Rask.Ui/Rask.Ui.csproj:1— `Rask.Ui(net10.0)` overshoots its size bounds (32584 LoC, 389 public types across 1 namespaces). 3 of 134 project(s) overshoot their size bounds, lowering Project Cohesion to 9.6/10. Review these for cohesion — split a project that spans unrelated responsibilities.
Fat interface: IRenderHandle (17 members) src/Rask.Core/Live/IRenderHandle.cs:3— `IRenderHandle` declares 17 members: `RequestRender`, `RequestPublishRender`, `Asked`, `RenderInScopeAsync`, `HandlerStarted`, `HandlerEnded`, `HandlerRepaintBudget`, `IsDevelopment`, `RunInOrder`, `TryNavigate`, `ReportDevError`, `Engine`, `Culture`, `UICulture`, `HasCulture`, `PendingBinds`, `HeardValues`. Counted as the author wrote them — a property is ONE member and its get/set accessors are not counted separately, and an event counts once. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces.
Fat interface: IQueryClient (22 members) src/Rask.Query/IQueryClient.cs:19— `IQueryClient` declares 22 members under just 9 distinct name(s): `Query`, `Query`, `Query`, `Query`, `Load`, `Warm`, `Send`, `Send`, `Command`, `Command`, `Command`, `Subscribe`, `Subscribe`, `Subscribe`, `Subscribe`, `Invalidate`, `Invalidate`, `Invalidate`, `Invalidate`, `InvalidateAll`, `Set`, `Set`. Counted as the author wrote them — a property is ONE member and its get/set accessors are not counted separately, and an event counts once. That is an OVERLOAD SET, not 22 separate responsibilities: a caller binds to 9 operation(s) and uses the overload it selected, so the Interface-Segregation harm does NOT apply on the caller's side and splitting this into role-interfaces would scatter one operation without relieving anything. The burden that does remain is the IMPLEMENTER's — all 22 signatures must be written and kept in step. Reduce it by collapsing overloads (optional or default parameters, or an options object) rather than by segregating the interface.
GD1 · Unfinished & placeholder code· Placeholder literal left in code · ×2
Placeholder literal left in code src/Rask.Wasm/PrerenderedLanguages.cs:175— A placeholder string ("[Rask.Prerender] no hreflang alternates …") is still in shipped code — typical of generated boilerplate that was never filled in.
Placeholder literal left in code src/Rask.Wasm/SitemapWriter.cs:38— A placeholder string ("[Rask.Prerender] no sitemap — set <RaskS…") is still in shipped code — typical of generated boilerplate that was never filled in.
Partial audit-trail evidence — An audit mechanism is present, but the trail is not yet complete — missing: an immutable audit-log / audit-trail type to write to, [Audited] per-entity coverage.
C4 · Data Retention· Partial data-retention evidence · ×1
Partial data-retention evidence — A retention mechanism is present, but the data-lifecycle is not yet complete — missing: a scheduled purge / cleanup job (PurgeOlderThan / CleanupJob).
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/`.
Split Rask.Core(net10.0) src/Rask.Core/Rask.Core.csproj:1— `Rask.Core(net10.0)` overshoots its size bounds (41110 LoC, 268 public types across 16 namespaces). These parts reach the rest of the project only through its shared core (`(root)`, `Authentication`, `Diagnostics`, `Globalization`, `Messaging`, `Virtualization`), so they are the cleanest seams: `Rask.Core.Printing` (5 types in 5 files): 1 of 7 of its type references cross into a sibling namespace, and the rest of the project uses it 0 times and it uses the rest 2 times. Extract each into its own project.
Split Rask.Site src/Rask.Site/Rask.Site.csproj:1— `Rask.Site` overshoots its size bounds (31344 LoC, 918 public types across 7 namespaces). These parts reach the rest of the project only through its shared core (`(root)`, `UiDocs`), so they are the cleanest seams: `Rask.Site.Features.UiKit` (8 types in 8 files): 0 of 111 of its type references cross into a sibling namespace, and the rest of the project uses it 0 times and it uses the rest 104 times. Extract each into its own project.
IL efficiency: 131 authored method(s) exceed the IL budget src/Rask.Site/Features/Elements/ElementsTextDemo.cs:7— 131 of 17497 first-party methods compile to oversized IL bodies (> 250 instructions); worst: Rask.Site.Features.ElementsTextDemo.Render @ src/Rask.Site/Features/Elements/ElementsTextDemo.cs:7, 626 IL instructions; that pulled this dimension to 9.9/10. These bodies are far past the JIT's inline budget, so splitting them does not make them inlinable — what moves the number is emitting less: collapsing LINQ chains and closures on hot paths, and interpolation built eagerly where it is only sometimes used.
DM9 · Scattered domain decisions· Rule about [End, Start] decided in 3 places · ×1
Rule about [End, Start] decided in 3 places — Rask.UiDateRange's [End, Start] are judged in Rask.UiCalendarRangePick, Rask.UiDatePickerPresets, Rask.UiPickerLimits — the same decision, restated. Every copy is a chance to drift, and copies drift silently because each one looks correct on its own. Move the judgement onto the type that owns the members and let the call sites ask it.
Disabled test tests/Rask.Core.Tests/Performance/CounterAllocationPinTests.cs:46— A test is skipped ("diagnostic — run manually to gather allocation deltas") — 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.
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.
Logging is not universal — Only 19/46 service-like projects use logging (pure contract/DTO projects are excluded — they have nothing to log). Of those 46, 7 ship a process this repository operates; the rest are libraries their consumer hosts, where the logging decision belongs to the host.
P4 · Deployment & Rollback· No rollback/health safety · ×1
No rollback/health safety — Deployment automation exists but no readiness/liveness probes, rolling-update strategy, lifecycle hooks or migration job were evidenced — a bad release is harder to detect and reverse.
Unused export 'register' src/Rask.Core/Resources/browser/auth.ts:98— Nothing ultimately consumes this binding: its only referrer is the re-export in src/Rask.Core/Resources/browser/index.ts, whose re-exported name has no consumer either. Removing it is therefore not a one-file change — drop the re-export line in src/Rask.Core/Resources/browser/index.ts in the same commit, or the barrel will import a name that no longer exists.
Unused export 'isSupported' src/Rask.Core/Resources/browser/mediaDevices.ts:25— Nothing ultimately consumes this binding: its only referrer is the re-export in src/Rask.Core/Resources/browser/index.ts, whose re-exported name has no consumer either. Removing it is therefore not a one-file change — drop the re-export line in src/Rask.Core/Resources/browser/index.ts in the same commit, or the barrel will import a name that no longer exists.
Unused export 'enumerate' src/Rask.Core/Resources/browser/mediaDevices.ts:34— Nothing ultimately consumes this binding: its only referrer is the re-export in src/Rask.Core/Resources/browser/index.ts, whose re-exported name has no consumer either. Removing it is therefore not a one-file change — drop the re-export line in src/Rask.Core/Resources/browser/index.ts in the same commit, or the barrel will import a name that no longer exists.
R7 · Dead Code· Unused export 'getDisplayMedia' · ×1
Unused export 'getDisplayMedia' src/Rask.Core/Resources/browser/mediaDevices.ts:48— Nothing ultimately consumes this binding: its only referrer is the re-export in src/Rask.Core/Resources/browser/index.ts, whose re-exported name has no consumer either. Removing it is therefore not a one-file change — drop the re-export line in src/Rask.Core/Resources/browser/index.ts in the same commit, or the barrel will import a name that no longer exists.
Unused export 'stop' src/Rask.Core/Resources/browser/mediaDevices.ts:66— Nothing ultimately consumes this binding: its only referrer is the re-export in src/Rask.Core/Resources/browser/index.ts, whose re-exported name has no consumer either. Removing it is therefore not a one-file change — drop the re-export line in src/Rask.Core/Resources/browser/index.ts in the same commit, or the barrel will import a name that no longer exists.
Security headers incomplete REDACTED:643— Set: Content-Security-Policy, Referrer-Policy, X-Content-Type-Options, X-Frame-Options. Missing: Strict-Transport-Security — the four headers that carry the points of this card's security-headers term (Content-Security-Policy, Strict-Transport-Security, X-Content-Type-Options, X-Frame-Options), 0.5 each. (−0.5 on this card.)
X2 · Cancellation propagation· Not all async methods take a CancellationToken · ×1
Not all async methods take a CancellationToken — Only 614/1375 async methods accept a CancellationToken, so in-flight work can't be stopped early when the caller gives up — whatever ends it in your host (shutdown signal, timeout, abandoned request, user cancel). Thread a token through the call chain and honour it at each await and loop; where a method genuinely cannot be interrupted, omitting it is a deliberate choice — judge against your hosting model.
Null-forgiving operator (`!`) suppressions reduce the NRT score — ~0.8 `!` suppressions per 1k syntax nodes — 790 suppression(s) across the 1021975 syntax node(s) in code where nullable warnings are ENABLED, which is the only code a `!` can suppress anything in (a `!` under `#nullable disable` is inert and is not counted, and its file's nodes are not in the denominator). Each one tells the compiler to trust you about null, suppressing the very safety NRTs provide.
Subsumed condition operand src/Rask.SQLite.Browser/IndexedDbSnapshotStore.cs:90— `dash > 0` can never decide this `&&` — every value satisfying `dash >= 9` also satisfies `dash > 0`, so the `&&` chain is already decided by the former. The expression is equivalent to the chain without it, which means it is narrower than it reads. Delete the dead operand, or narrow the surviving one if IT is the accident.
doc comments repeat the names scripts/flux/Flux/Lib/Measurement.cs:46— 1 of 12 documented parameters and 2 of 222 summaries in `Flux` only repeat the member or parameter name (e.g. "The parent of ." for `ParentOf`). Delete the restating tags, or add what the name does not say.
doc comments repeat the names src/Rask.Api.Client/ApiException.cs:22— 3 of 25 documented parameters and 0 of 30 summaries in `Rask.Api.Client` only repeat the member or parameter name (e.g. "The message." for `message`). Delete the restating tags, or add what the name does not say.
doc comments repeat the names tests/Rask.Api.Client.Tests/Endpoints.cs:7— 6 of 8 documented parameters and 1 of 26 summaries in `Rask.Api.Client.Tests` only repeat the member or parameter name (e.g. "Its title." for `Title`). Delete the restating tags, or add what the name does not say.
doc comments repeat the names src/Rask.Generators.Shared/ModelShape.cs:18— 0 of 31 documented parameters and 4 of 216 summaries in `Rask.Api.Generators` only repeat the member or parameter name (e.g. "The entity." for `Entity`). Delete the restating tags, or add what the name does not say.
doc comments repeat the names tests/Shared.GeneratorTests/GeneratorHarness.cs:23— 0 of 4 documented parameters and 1 of 15 summaries in `Rask.Api.Generators.Tests` only repeat the member or parameter name (e.g. "Runs over ." for `Run`). Delete the restating tags, or add what the name does not say.
doc comments repeat the names src/Rask.Auth.Api/AuthInstanceClaim.cs:41— 17 of 106 documented parameters and 2 of 316 summaries in `Rask.Auth.Api` only repeat the member or parameter name (e.g. "When it was claimed (UTC)." for `ClaimedUtc`). Delete the restating tags, or add what the name does not say.
doc comments repeat the names tests/Rask.Auth.SignInName.Tests/User.cs:22— 1 of 4 documented parameters and 0 of 13 summaries in `Rask.Auth.SignInName.Tests` only repeat the member or parameter name (e.g. "The tenant." for `tenant`). Delete the restating tags, or add what the name does not say.
doc comments repeat the names src/Rask.Generators.Shared/ReadChildCollection.cs:6— 1 of 56 documented parameters and 0 of 97 summaries in `Rask.Batteries.Generators` only repeat the member or parameter name (e.g. "The child's write type — ." for `ChildWriteType`). Delete the restating tags, or add what the name does not say.
doc comments repeat the names src/Rask.Cli/Commands/DeployDeadlines.cs:13— 0 of 31 documented parameters and 8 of 813 summaries in `Rask.Cli` only repeat the member or parameter name (e.g. "The key for ." for `BuildKey`). Delete the restating tags, or add what the name does not say.
doc comments repeat the names src/Rask.Core/Authentication/ClaimsPrincipalExtensions.cs:9— 6 of 427 documented parameters and 21 of 1877 summaries in `Rask.Core(net10.0)` only repeat the member or parameter name (e.g. "The principal, such as ." for `principal`). Delete the restating tags, or add what the name does not say.
doc comments repeat the names src/Rask.Cqrs/IRemoteDispatch.cs:28— 3 of 75 documented parameters and 1 of 211 summaries in `Rask.Cqrs` only repeat the member or parameter name (e.g. "The message instance." for `message`). Delete the restating tags, or add what the name does not say.
doc comments repeat the names src/Rask.Data/BulkInsertOptions.cs:3— 13 of 264 documented parameters and 4 of 624 summaries in `Rask.Data(net10.0)` only repeat the member or parameter name (e.g. "Options for ." for `BulkInsertOptions`). Delete the restating tags, or add what the name does not say.
doc comments repeat the names tests/Rask.Data.Tests/ChildFieldByNameTests.cs:53— 1 of 2 documented parameters and 1 of 294 summaries in `Rask.Data.Tests` only repeat the member or parameter name (e.g. "An entry in a logbook." for `LogbookEntry`). Delete the restating tags, or add what the name does not say.
doc comments repeat the names src/Rask.DevTools/Panel/DevToolsTreeRow.cs:6— 2 of 86 documented parameters and 0 of 234 summaries in `Rask.DevTools(net10.0)` only repeat the member or parameter name (e.g. "The node." for `Node`). Delete the restating tags, or add what the name does not say.
doc comments repeat the names src/Rask.Generators/Json/JsonKind.cs:3— 0 of 2 documented parameters and 2 of 20 summaries in `Rask.Dom.Tasks` only repeat the member or parameter name (e.g. "The kind of a ." for `JsonKind`). Delete the restating tags, or add what the name does not say.
doc comments repeat the names src/Rask.Generators/Analyzers/BuilderEntry.cs:495— 0 of 20 documented parameters and 3 of 140 summaries in `Rask.Generators` only repeat the member or parameter name (e.g. "Whether named ." for `NamedBy`). Delete the restating tags, or add what the name does not say.
doc comments repeat the names src/Rask.Jobs/JobFailedException.cs:15— 0 of 33 documented parameters and 2 of 198 summaries in `Rask.Jobs` only repeat the member or parameter name (e.g. "A job failed with ." for `JobFailedException`). Delete the restating tags, or add what the name does not say.
doc comments repeat the names src/Rask.Mail/OutgoingMail.cs:28— 1 of 10 documented parameters and 4 of 130 summaries in `Rask.Mail` only repeat the member or parameter name (e.g. "The HTML body, if any." for `HtmlBody`). Delete the restating tags, or add what the name does not say.
doc comments repeat the names src/Rask.Outbox/OutboxOptions.cs:3— 0 of 11 documented parameters and 1 of 67 summaries in `Rask.Outbox` only repeat the member or parameter name (e.g. "Options for the ." for `OutboxOptions`). Delete the restating tags, or add what the name does not say.
doc comments repeat the names src/Rask.Server/Prerender/PageRenderInput.cs:7— 0 of 106 documented parameters and 1 of 581 summaries in `Rask.Server` only repeat the member or parameter name (e.g. "What a page is rendered for." for `PageRenderInput`). Delete the restating tags, or add what the name does not say.
doc comments repeat the names tests/Rask.Server.E2E.Tests/Infrastructure/KitGestures.cs:155— 0 of 18 documented parameters and 5 of 437 summaries in `Rask.Server.E2E.Tests` only repeat the member or parameter name (e.g. "A press on ." for `Press`). Delete the restating tags, or add what the name does not say.
doc comments repeat the names tests/Rask.Server.Tests/App/HandWiredDataHostTests.cs:588— 0 of 15 documented parameters and 2 of 411 summaries in `Rask.Server.Tests` only repeat the member or parameter name (e.g. "The page's address: ." for `ThePagesAddress`). Delete the restating tags, or add what the name does not say.
doc comments repeat the names tests/Rask.Site.DataDemo.E2E.Tests/DataDemoHost.cs:15— 0 of 0 documented parameters and 1 of 4 summaries in `Rask.Site.DataDemo.E2E.Tests` only repeat the member or parameter name (e.g. "The demo's own URL." for `DemoUrl`). Delete the restating tags, or add what the name does not say.
doc comments repeat the names src/Rask.Storage/SweepResult.cs:3— 0 of 31 documented parameters and 1 of 213 summaries in `Rask.Storage` only repeat the member or parameter name (e.g. "What one sweep did." for `SweepResult`). Delete the restating tags, or add what the name does not say.
doc comments repeat the names src/Rask.TypeScript.Tasks/ResolveTypeScriptToolTask.cs:171— 1 of 8 documented parameters and 0 of 43 summaries in `Rask.TypeScript.Tasks` only repeat the member or parameter name (e.g. "Where the tarball is." for `tarballUrl`). Delete the restating tags, or add what the name does not say.
Skipped (documented): Counter_allocation_diagnostic_prints_the_delta_between_shell_and_inner tests/Rask.Core.Tests/Performance/CounterAllocationPinTests.cs:46— Skipped with a documented reason — a deferral, not lazy debt: diagnostic — run manually to gather allocation deltas
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.
nuget: not applicable — nuget: the solution did not restore on the analyzer's .NET SDK (an SDK/target-framework/restore mismatch, common for an older codebase), so there was no restored dependency graph to scan
semgrep: not applicable — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that. semgrep could not parse 597 file(s) — `.claude/skills/run-rask/dashboard-driver.cs`, `.claude/skills/run-rask/driver.cs`, `.claude/skills/run-rask/fitprobe.cs`, `.claude/skills/run-rask/frameprobe.cs`, `.claude/skills/run-rask/growprobe.cs`, … (+592 more) — so the PII/GDPR sweep did not cover the unparsed regions of them; rows reported elsewhere in those files are real.
runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here.
runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here.
runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here.
Run 01a1bd03-f8f9-7014-a258-8dfcf430b90f · every finding is also locatable in findings.md, and the complete scoring record (with exit codes + durations) in sidecar.json.
Appendix C — Personal-data map
Every field, property and record parameter whose name is conventional personal data — 25 field(s) across 4 categories, each with an exact repo-relative file:line. This is the data inventory a compliance review starts from — right-to-erasure, retention, minimisation. Detected by NAME, from the C# syntax tree, with a deliberately specific identifier classifier — the same one the C1–C5 compliance cards use to decide whether personal data is present, so CardDefinition or FileName don't trip. Two caveats stated rather than glossed: those cards additionally require corroboration (a persistence/account signal, or two distinct PII categories) that this inventory deliberately does not, so it lists more than they gate on; and D32 Data Compliance shares nothing with it — that dimension is a separate semgrep ruleset for personal data leaking into logs, URLs and browser storage, and a clean D32 result says nothing about this list. Informational — it feeds no score.
Issues: 183 · Warnings: 1055 · Recommendations: 175 · Info: 32 — Appendix A · all findings · full markdown report.
Generated by the Canine Code Analyzer: deterministic code-health analysis. 08-11-2026 @ 21:15 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.