Public report — rask, published 21 Sep 2026.
Concrete security findings (which rule fired, in which file, on which line; CVE IDs, secret matches,
dependency versions) are REDACTED in this version; ask the repo owner for the full report.
Public
Codebase surveyMeasured under the Code Assurance Index · rubric rubric-2026.09.15 (frozen) · verify this surveyFiledcd_bbe365a16abf4dcda21c2be64db9aa1e
Filed 25 September 2026, 05:10 UTC
Public
Large · 142,951 LoC · 173 projects · rebuild ~5.2 person-years · weakest lens: Readiness (31%)
Findings by grade
153 critical1050 serious450 minor3 could not be resolved — could be critical — see Limitations
This survey was produced by
Watchdog
Producer
Canine Development
Analyzer
Watchdog engine 1.0.0
Measured
21 September 2026, 09:25 UTC
A measurement, not a certificate. The Code Assurance Index does not certify,
approve or guarantee this codebase; it records a reproducible number and the evidence it was computed from. The
standard is authored by Canine Development, who also build Watchdog — its only implementation today. That is said
here so the number is checked rather than believed.
Grounded in facts. Every number here is computed, not narrated — reproducible, tool-backed, and traceable to a line of code. How to trust this ▸
1134findings with an exact file:lineof 1653 — the remainder are repo-wide signals (a dimension-level measurement, not a single line); open any file:line and verify
108/139dimensions across the health lenses142951 LoC · 173 projects — wide & deep
Preview (pre-1.0). This repo hasn't declared a stable release, so it's judged against a relaxed, pre-production bar.
The system holds an adequate overall standing of 51%, reflecting a large, valuable asset that is currently carrying significant operational risk. With nearly 143,000 lines of production code and a rebuild cost estimated at €750,000, the business has substantial value tied up in this platform. While the core domain logic is well-modeled and the codebase is generally maintainable, the foundation for safe, reliable operation is fragile. This gap between development quality and production readiness creates a vulnerability where routine changes or failures could lead to costly outages or data corruption.
The most critical risk lies in Production Readiness, which scores a mere 31%. This low score indicates that the system lacks the necessary safeguards for stable operation, such as robust error handling and schema management. Without these protections, the business faces high costs in the form of unplanned downtime, increased defect rates, and the potential for data integrity issues during deployments. The reliance on automatic schema creation rather than versioned migrations means that database changes are not reproducible or safe, exposing the system to unpredictable failures when updates are applied.
A secondary concern is Code Reachability and Testability. A significant portion of the frontend code is unreachable by standard testing tools, meaning that critical user-facing logic is effectively untested. This creates a blind spot where bugs can persist undetected until they impact customers. While the backend logic is sound, the inability to verify these entry points undermines confidence in the system’s reliability and increases the effort required to fix issues when they inevitably arise.
On the positive side, the domain modeling is excellent at 97%, and the code health is solid, suggesting that the core business rules are clear and maintainable. To maximize leverage, the immediate focus must be on making retry-prone mutations idempotent. By ensuring that repeated operations do not double-apply, the business can significantly reduce the risk of data corruption and financial loss with relatively low effort. This single action provides the highest return on investment by addressing the most dangerous operational gap. Until this is resolved, the system remains exposed to avoidable risks despite its strong underlying design.
How the score is built — each lens's share of the headlineWidth is the lens's weight in the worst-heaviest fold (the weakest area pulls hardest); colour is that lens's own band. A lens fixes the score in proportion to its width.
0.7× (at 51% quality) — the last 20% of quality is most of the work
Size & shape
Large · effort split not classified for 22,140 line(s) outside the .NET model (the tier breakdown is a C#-only syntax walk)
Dead frontend code
~2320 LoC unreachable (40 file(s)) — that slice of this estimate buys code with zero runtime value; deleting it is the cheapest win in this report (the R7 card lists every file)
This codebase represents roughly ~5.2 person-years of build effort (about ~€750,000 to rebuild). Its weakest lens is Readiness at 31% — the part of that asset most exposed by the findings below.
How we model this: boilerplate at a scaffolding rate + logic × domain REDACTED (×1.5) — service/app, CQRS, domain model, high decision density × a 0.7× quality factor, at €60–95/h; indicative, ±~30%. Indicative only — most sensitive to the hourly rate and the domain tier (both tunable in config).
Top priorities
The highest-leverage moves; the full ranked list is in the Roadmap below.
1
Resolve the 1 Leaked secret finding(s) in REDACTED Scanning — start with REDACTED.
Make retry-prone mutations idempotent — guard each write with an exists/dedup check, an upsert, an idempotency-key/inbox, or a versioned write, so a re-run doesn't double-apply.
Value concentrated against a weak lens · REDACTED · Value at risk
This is a Large asset (~5.2 person-years to rebuild), and its weakest lens is Readiness at 31%. The operational and business risk on an asset this size concentrates there — that's where remediation buys the most protection.
→ Direct remediation budget at Readiness first — highest risk-reduction per euro on an asset this size.
Highest-leverage move · REDACTED · Leverage
Of everything flagged, the best return on effort is: Make retry-prone mutations idempotent — guard each write with an exists/dedup check, an upsert, an idempotency-key/inbox, or a versioned write, so a re-run doesn't double-apply. The rest can wait behind it.
Evidence: priority ranking: top of 5 ranked by impact/effort
→ Make retry-prone mutations idempotent — guard each write with an exists/dedup check, an upsert, an idempotency-key/inbox, or a versioned write, so a re-run doesn't double-apply.
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 — module dependency matrix
Rows and columns are the same modules, ordered so that a module only depends on ones above it. A cell means the row depends on the column, and its number is how many type pairs create that dependency. Read one thing: is anything above the diagonal? A mark there is a dependency cycle. (A cycle is all this shows — an unusual but cycle-free dependency sits below the diagonal like any other.)
249 modules, 272 dependencies. 7 dependency cycles across 25 modules, marked above the diagonal.
Showing the 40 most-connected modules; 209 more are not drawn.
Module dependency matrix. The row depends on the column; the number is how many type pairs create the dependency. A cell above the diagonal is part of a dependency cycle.
41 distinct (type in Rask.Cli.Commands → type in Rask.Cli) references. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
Rask.Core.Components uses Rask.Core.Live. Changing Rask.Core.Live can break Rask.Core.Components, not the reverse.
Position
Below the diagonal — points down the layering, which is what you want.
22→24 Rask.Core.Components depends on Rask.Corecycle✕
Type pairs
156 distinct (type in Rask.Core.Components → type in Rask.Core) references. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
Rask.Site.Features uses Rask.Core. Changing Rask.Core can break Rask.Site.Features, not the reverse.
Position
Below the diagonal — points down the layering, which is what you want.
35→25 Rask.Site.Features depends on Rask.Core.Browser✕
Type pairs
58 distinct (type in Rask.Site.Features → type in Rask.Core.Browser) references. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
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:2021 — Security Misconfiguration
96
REDACTED / Critical
A03:2021 — Injection
34
REDACTED / Critical
A02:2021 — Cryptographic Failures
15
REDACTED / Critical
A06:2021 — Vulnerable & Outdated Components
4
REDACTED
Roadmap
First, ensure all retry-prone mutations are idempotent to prevent data duplication, and replace ad-hoc schema creation with a versioned migration system for safe production evolution. Next, improve test coverage by refactoring unreachable entry points into importable modules and adding direct imports for the remaining production code. Finally, clean up the dependency list by removing unused packages and explicitly declaring imports, while documenting a tested disaster recovery procedure with clear RTO and RPO targets.
Ranked by impact ÷ effort. "Helps" is the estimated gain on the 0–100 health score.
Do this
Helps
Effort
Dimension
Resolve the 1 Leaked secret finding(s) in REDACTED Scanning — start with REDACTED.
Make retry-prone mutations idempotent — guard each write with an exists/dedup check, an upsert, an idempotency-key/inbox, or a versioned write, so a re-run doesn't double-apply.
16 of the 142 unreached modules are entry points — the browser loads some as a top-level script and something else executes the rest by path, so no import specifier addresses them and no public entry publishes them. An importing test cannot be written for them as they ship, and two different things are worth doing here — they are not the same thing. To EXERCISE them, a browser or end-to-end suite that loads the page, or a test that runs the script the way its caller does; that is worth having, but it will NOT clear this row, because reachability is measured over the import graph and running a file by path adds no edge to it. To CLEAR it, make them addressable: lift the logic into a module a test can import and leave the entry points thin shims over it, or put their bodies behind a main-guard (`import.meta.url === argv[1]`) and export them. Add tests that import the other 126 — directly or through their public entry.
Wire the existing health endpoints into readiness/liveness probes and a rolling-update (or blue/green) strategy in the deployment manifests — or document where that wiring lives — so a bad release is caught and rolled back automatically.
Per-file score 0–10 — a quality signature. Of 324 files carrying findings, judged against the Preview bar: 5% slop · 5% mixed · 90% near-clean.
File
Score
Band
Worst signal
REDACTED
0.7
Slop
IaC & Container Security: REDACTED IaC: REDACTED
REDACTED
0.7
Slop
IaC & Container Security: REDACTED IaC: REDACTED
REDACTED
0.7
Slop
IaC & Container Security: REDACTED IaC: REDACTED
REDACTED
0.7
Slop
IaC & Container Security: REDACTED IaC: REDACTED
REDACTED
0.7
Slop
IaC & Container Security: REDACTED IaC: REDACTED
REDACTED
0.7
Slop
IaC & Container Security: REDACTED IaC: REDACTED
REDACTED
1.4
Slop
IaC & Container Security: REDACTED IaC: REDACTED
REDACTED
1.4
Slop
IaC & Container Security: REDACTED IaC: REDACTED
REDACTED
1.4
Slop
IaC & Container Security: REDACTED IaC: REDACTED
REDACTED
1.4
Slop
IaC & Container Security: REDACTED IaC: REDACTED
REDACTED
1.4
Slop
IaC & Container Security: REDACTED IaC: REDACTED
REDACTED
1.4
Slop
IaC & Container Security: REDACTED IaC: REDACTED
REDACTED
1.4
Slop
IaC & Container Security: REDACTED IaC: REDACTED
src/Rask.Server/RaskEndpointExtensions.cs
2.5
Slop
Explicit Debt: EmptyCatchBlock
REDACTED
2.7
Slop
Static Analysis (SAST): REDACTED: REDACTED
REDACTED
3.0
Mixed
Static Analysis (SAST): REDACTED: REDACTED
REDACTED
3.4
Mixed
IaC & Container Security: REDACTED IaC: REDACTED
REDACTED
4.5
Mixed
Static Analysis (SAST): REDACTED: REDACTED
REDACTED
4.8
Mixed
Static Analysis (SAST): REDACTED: REDACTED
REDACTED
5.1
Mixed
Static Analysis (SAST): REDACTED: REDACTED
How the grades work
Every finding carries one of four grades. Three say how serious it is. The fourth says this
survey could not settle it — and it is a grade, not a gap.
Critical — 153
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 — 1050
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 — 450
Recorded, with no effect on how the codebase functions.
Present so the survey is complete, not because it needs doing.
Could not be resolved — 3
Something this survey could not settle
from the outside, and which could be critical or serious. Either a control was required and no
positive evidence of it exists in the repository — a backup job that nothing shows was ever restored from proves
nothing about restores — or our own analysis could not run over that part of the tree. This is not a clean
result. These are excluded from the score rather than awarded a pass, so the number on the cover neither
rewards nor penalises them: if you act on this survey without resolving them, you carry that risk yourself. Each
one is named under Limitations.
Methodology & how to trust this report
Watchdog is a deep, periodic assessment — run each sprint, monthly, or quarterly, taking the time to go wider and deeper than a quick check and surfacing in one coherent report what you'd otherwise piece together from a dozen separate tools. It scores deterministically: the same commit yields the same score, every run. 102 of 108 evaluated dimensions are computed purely by tools and static analysis (confidence 1.0); 6 documentation/naming judgement(s) are LLM-assisted and labelled advisory. Overall confidence is 0.9 — the weighted average across measured dimensions; it falls as more of the score leans on LLM-assisted judgement and rises when it's fully tool-backed.
Every figure here is one of three kinds, and we label which: ✓ Measured — a deterministic fact (LoC, complexity, coverage); ~ Modeled — an estimate from a stated model (cost, effort, value-at-risk), always a range with its assumptions, never a precise fact; ◐ Advisory — an LLM prose judgement. We never present a modelled estimate as if it were measured. Perfect or absent scores carry their provenance too (ADR-0011): ✓ Tool-verified means the property itself was measured across the surface; ○ Nothing flagged means the probes came back clean — a claim bounded by what a repository can show; ⊘ Not evidenced means a working control (a tested restore, an automated rollback) showed no positive evidence — absence of evidence is not evidence of a control, so it's excluded from the score rather than awarded a spurious 10; ◐ Sampled · advisory marks an LLM verdict over a bounded sample — advisory, never a deterministic measurement.
What we checked — 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, 1134 of 1653 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, a scanner, or (for a handful of documentation/naming dimensions) an LLM labelled sampled · advisory — 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.
D10 Test Quality — measured, with a gap in what it reached — Watchdog measured this, but not all of it. What it did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. The 8,396 test(s) behind this row are the ones the C# collector could read, and this repository also carries at least 39 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 — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Test reliability not scored — the test tier(s) ran but surfaced none of this repository's 8396 test method(s) to the runner, so flakiness couldn't be exercised. This is an analysis-environment limitation, not a finding about the tests.
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 1706 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.
D18 Solution Shape — measured, with a gap in what it reached — Watchdog measured this, but not all of it. What it did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. The build did not finish within its budget on this run; structural metrics are reported, build/warning status is unknown.
D18 Solution Shape — measured, with a gap in what it reached — Watchdog measured this, but not all of it. What it did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. A scan analyzes ONE solution. Every score, lens, and finding here reflects only `Rask.slnx`; 17 further solution(s) found in this tree (`src/Rask.Templates/analog/Company.RaskServer.slnx`, `src/Rask.Templates/angular/Company.RaskServer.slnx`, `src/Rask.Templates/angular/client/node_modules/lmdb/dependencies/lz4/lib/dll/example/fullbench-dll.sln`, `src/Rask.Templates/lit/Company.RaskServer.slnx`, `src/Rask.Templates/nextjs/Company.RaskServer.slnx`, `src/Rask.Templates/nuxt/Company.RaskServer.slnx`, +11 more) are not covered by it, were not analyzed, and are not represented in the headline. (This is a count of the solutions discovery found and could not show to be covered by the analyzed one — not a claim about how many solution files the repository contains.) If one of them is an archived or vendored tree, declaring it — `.gitattributes` (`path/** linguist-vendored`) or `.editorconfig` (`[path/**] generated_code = true`) — excludes it from discovery the same way generated code is. You can widen what we reach: scan each solution separately.
D30 Dependency Vulnerabilities — measured, with a gap in what it reached — This is a true statement about the repository that carries nothing for its owner to act on, so it is reported here rather than as a defect in their code. The 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. 2 of 3 declared ecosystem(s) (npm,osv) WERE scanned and every vulnerability they reported is included in this result; nuget was not, so this dimension's score covers less than the dependency surface this repository declares, and nothing here is evidence that nuget is free of known-vulnerable dependencies.
D32 Data Compliance (PII/GDPR) — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. `.claude/skills/add-html-tag/templates/Component.cs`, `.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`, … (+373 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.
D39 IL Efficiency — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. IL NOT MEASURED: the analyzer's build of this repository exited 1 and the cause could not be attributed, so no assemblies were produced and there was no IL to read. We do not read it as a defect in the repository: an unattributed failure leans OURS. D18 owns the question of whether this repository builds; it was not answered here.
D43 Malicious Dependencies — measured, with a gap in what it reached — This is a true statement about the repository that carries nothing for its owner to act on, so it is reported here rather than as a defect in their code. The 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. 2 of 3 declared ecosystem(s) (npm,osv) WERE scanned and every vulnerability they reported is included in this result; nuget was not, so this dimension's score covers less than the dependency surface this repository declares, and nothing here is evidence that nuget is free of known-vulnerable dependencies.
DM9 Scattered domain decisions — measured, with a gap in what it reached — Watchdog measured this, but not all of it. What it did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. Both arms resolve expressions to symbols (a comparison operand to the member it judges, a construction to the type it constructs) and that resolution comes from a Roslyn compilation, which this run has for the C#/VB projects only. The other languages in this repository were not walked for this dimension, so the counts above speak for part of the codebase.
P1 CI/CD gates — measured, with a gap in what it reached — Watchdog measured this, but not all of it. What it did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. A CI pipeline exists and the word "test" appears, but no explicit test-runner invocation (your stack's test command, or a test job) was matched — so either the gate runs tests through a step this pass could not recognise, or "test" is incidental here (a path, "latest", a reporter). Which of the two it is cannot be settled from this dimension's evidence; the coverage dimensions report whether a suite exists at all. You can widen what we reach: name the test runner explicitly in the pipeline step (your stack's test command, or a job named for the suite) so the gate is unambiguous to a reader and to this pass.
R10 Code Duplication — measured, with a gap in what it reached — Watchdog measured this, but not all of it. What it did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. 35 further occurrence(s) are not listed individually; the score already reflects all 75.
R4 Test Coverage — measured, with a gap in what it reached — Watchdog measured this, but not all of it. What it did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. 102 further occurrence(s) are not listed individually; the score already reflects all 142.
R7 Dead Code — measured, with a gap in what it reached — Watchdog measured this, but not all of it. What it did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. 9 further occurrence(s) are not listed individually; the score already reflects all 49.
X2 Cancellation propagation — measured, with a gap in what it reached — Watchdog measured this, but not all of it. What it did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. 210 further occurrence(s) are not listed individually; the score already reflects all 250.
X8 JS interop contract — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. 125 further occurrence(s) are not listed individually; the score already reflects all 165.
Package restore incomplete — third-party types were unresolved in part of the solution — NuGet restore did not complete for src/Rask.Auth.Api/Rask.Auth.Api.csproj, src/Rask.Auth.Client/Rask.Auth.Client.csproj, src/Rask.Auth/Rask.Auth.csproj, src/Rask.Cache/Rask.Cache.csproj, src/Rask.Cli/Rask.Cli.csproj and 115 more, 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: 156 pattern(s) declared (.gitattributes linguist-generated/vendored, .editorconfig generated_code) excluded 0 source file(s) from code-quality scoring. Declarations are the repo's own visible statement that a tree is machine-written or vendored — auditable in any diff, honored by GitHub the same way.
Limitations & what we did not check
Watchdog assesses the repository exactly as committed, and only the repository. By design it does not reach outside the source tree: the live cloud account, the running CI/CD pipeline, the host's branch-protection and approval rules, the production configuration, or a restore actually exercised against a backup are all out of scope. That boundary is a feature, not a gap — a repo-relative, deterministic scan re-runs identically on any commit and every finding opens at a real file and line, where a live audit can neither be reproduced nor traced. The visible consequence is that controls which leave no in-repo evidence are reported as "not evidenced" and excluded from the score rather than awarded a number a static scan cannot justify.
Per-dimension blind spots
For each dimension that was measured, what a static, repo-only scan structurally cannot see — the honest edge of the measurement, not a failure of it.
D1 Cyclomatic Complexity: Cyclomatic complexity counts branches statically — it cannot tell an essential decision tree from accidental tangle, nor see complexity that lives in data or configuration (large switch-case token tables, DSL lexers/parsers, data-as-code rule tables) rather than control flow: a tokenizer's many single-character cases read as high complexity though each branch is trivial.
D2 Cognitive Complexity: Cognitive-complexity heuristics approximate how hard code is to follow; genuine domain difficulty and well-named intent that eases reading are not captured.
D3 God Classes: "God class" is sized by members and responsibilities visible in the type — a deliberately broad facade over a coherent subsystem can read the same as an accidental grab-bag. For front-end JS the file-length check is cohesion-aware (a single-responsibility module — one class/IIFE — earns a 3× threshold), but cohesion is approximated from top-level declarations, not true dependency structure.
D4 Code Duplication: Duplication is token-similarity — an in-process token-stream comparison over sliding windows, with type-aware normalization — so it finds copy-paste, not semantic duplication expressed differently. Committed machine-written code (scaffolded migrations, designer/codegen output, protobuf/OpenAPI stubs, model snapshots) is EXCLUDED — its repetition is the tool's, not the team's — so the score reflects hand-written duplication only.
D5 Coupling: Coupling is measured between projects/assemblies — runtime coupling through DI, reflection, messaging or shared databases is invisible to a static reference graph.
D6 Cohesion (LCOM4): LCOM4 cohesion is syntactic — it infers connectivity from which methods touch which fields/methods by name, not from real runtime behaviour or intent.
D9 Test Distribution: The test-pyramid shape is inferred from project/folder naming and references, with a single test host bucketed per-file by its path tier and content signals — a suite that names tiers unconventionally and gives no per-file signal can still be mis-bucketed.
D10 Test Quality: Assertion density is structural — it cannot tell a meaningful behavioural assertion from a trivial one, only that an assertion is present.
D12 Dependency Hygiene: Dependency health reads manifests and lockfiles — a vulnerability in a vendored/copied dependency, or risk from how a dependency is actually used, is outside this view.
D13 REDACTED Scanning: REDACTED detection is signature- and entropy-based on the current tree — a secret that does not match a known pattern, or one already rotated, will not be flagged (a clean scan is "nothing matched", not "no secrets exist").
D14 License Compliance: License compatibility is checked against declared package metadata and a policy — mislabelled or missing license metadata, and obligations that depend on how you distribute, are not resolved here.
D15 Churn × Complexity Hotspots: Churn hotspots come from git history — a freshly imported or squashed repository has no churn signal, and recent rewrites can mask a historically risky file.
D17 Explicit Debt: Acknowledged-debt signals (TODO/FIXME, suppressions, dead code) are textual — undocumented debt that nobody marked, and debt that lives in design rather than annotations, is invisible. Committed machine-written code (scaffolded migrations, designer/codegen output, generated stubs) is excluded — it is never the team's dead code to delete.
D18 Solution Shape: Build integrity reflects whether the solution compiled in this environment — a build that needs a private feed, a specific SDK, or a generated file absent from the repo can read as broken when it is merely unreproducible here.
D19 Documentation Quality: Documentation quality is judged by an LLM over a bounded sample of docs — it reads what is written, not whether the docs match the running system, and it is advisory, not a measurement. Its critique rows are drawn from a closed category vocabulary and each row means the same thing in every run, so two scans can be compared row by row; the SET that fires is still a sample, and does not repeat exactly. Measured on one frozen input, six scans at one engine SHA: 2-5 critique rows per scan, 8 distinct rows across the six, 3 of those 8 seen in only one scan. So a D19 row is evidence about the documentation, but a COUNT of D19 rows is not a quantity — never read a change in it as an improvement or a regression.
D20 ADR Quality: ADR quality is an LLM read of the decision records present — it cannot know about decisions made and never recorded, and its verdict is sampled and advisory.
D21 Naming Consistency: Naming quality is an LLM judgement over a bounded sample — it assesses clarity/consistency of the names it sees, not domain-correctness, and is advisory.
D22 Internal API Consistency: API-surface coherence is an LLM judgement over a sample of the public surface — consistency of intent across the whole API is approximated, not exhaustively verified.
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 (WHY vs WHAT) is an LLM judgement over a bounded sample — it is advisory and cannot weigh a comment against the precise code change it was written to explain.
D26 Project Cohesion: Project focus is sized from members/namespaces per project — a project that is broad by deliberate design reads the same as one that has sprawled.
D28 Secrets (history): Secret-history scanning sweeps the git log for known patterns — a secret that predates the available history, or never matched a signature, is not found (clean means "nothing matched in the history we can see").
D29 Static Analysis (SAST): SAST findings are pattern-based (semgrep) — it finds classes of bug it has rules for; logic flaws, auth/authorization gaps and issues needing runtime context are out of reach (and clean means "no rule matched").
D30 Dependency Vulnerabilities: CVE matching depends on accurate package/version metadata and on the advisory databases — a vulnerability with no published advisory, or in code not declared as a dependency, is not seen. Coverage needs a RESOLVED graph: an unpinned requirements.txt, or a pom without a resolved build, yields partial coverage rather than a clean verdict. An ecosystem the analyzer cannot scan is reported as unmeasured, never as clean.
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 judged from the handler body's visible writes and guards — a guard enforced by a database unique constraint, a broker's exactly-once delivery, or a domain method whose no-op-when-applied logic the scan can't follow may read as at-risk; the at-risk candidates are confirmed by a SAMPLED LLM verdict (advisory, not exhaustive) and degrade to heuristic-only when no model is configured. It flags the at-least-once double-apply SHAPE, not a runtime proof of a duplicate effect.
M4 Documentation accuracy: Onboarding quality is an LLM read of the docs/setup present — it cannot run the onboarding or measure how long a real new joiner takes; the verdict is sampled and advisory.
P4 Deployment & Rollback: Approval/branch-protection rules live in repository settings the scan cannot see — only their in-repo evidence (config files, workflows) is checked, so a control enforced purely in the host's settings reads as "not evidenced".
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.
The LLM boundary
LLM-set scores this run (6): D19, D21, D22, D24, ED5, M4 (model: Local LLM). For these, a model reads a bounded sample and sets the numeric score; each names its own sample and method on its card. They are sampled and advisory by design: they vary at the margins between runs and are never a deterministic measurement. Every other score in this report is tool-computed at confidence 1.0.
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.
111 method(s) exceeded the cyclomatic complexity threshold of 15; the worst was rask-morph.morph at 77. A further 11 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 UiIcon.Shapes at 80 — they are counted neither in the figure above nor in this dimension's score. 8 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/UiIcon.cs (UiIcon.Shapes at 80), src/Rask.Core/InputType.cs (InputTypeExtensions.ToHtml at 24), src/Rask.Core/Forms/BindingHelpers.cs (BindingHelpers.DefaultInputType at 21), src/Rask.SQLite.EntityFrameworkCore/RangeExclusionDdl.cs (RangeExclusionDdl.TableOf at 20), src/Rask.Core/Live/HandlerFrameShape.cs (HandlerFrameShape.ShapeOf at 17), and 3 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.
+ 106 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Resolve the 1 rask-morph.morph (cyclomatic 77) finding(s) in Cyclomatic Complexity — start with rask-morph.ts. — One of this dimension's main actionable groups (1 warning-level).
Resolve the 1 ModelInputGenerator.Render (cyclomatic 62) finding(s) in Cyclomatic Complexity — start with ModelInputGenerator.cs. — One of this dimension's main actionable groups (1 warning-level).
Resolve the 1 HtmlSerializer.Serialize (cyclomatic 58) finding(s) in Cyclomatic Complexity — start with HtmlSerializer.cs. — One of this dimension's main actionable groups (1 warning-level).
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.
+ 182 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Resolve the 1 rask-morph.morph (cognitive 136) finding(s) in Cognitive Complexity — start with rask-morph.ts. — One of this dimension's main actionable groups (1 warning-level).
Resolve the 1 HtmlSerializer.Serialize (cognitive 95) finding(s) in Cognitive Complexity — start with HtmlSerializer.cs. — One of this dimension's main actionable groups (1 warning-level).
Resolve the 1 RaskEndpointExtensions.RunSocketLoop (cognitive 79) finding(s) in Cognitive Complexity — start with RaskEndpointExtensions.cs. — One of this dimension's main actionable groups (1 warning-level).
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 Classes8.9 / 10Strong✓ Tool-verified
What it measures: Over-large classes that try to do too much ("god classes").
Method: God-class detection by line and method-count thresholds per logical type (partial classes unified), filtered for generated code and registration/contract false positives. Deterministic.
Resolve the 17 FileTooLong finding(s) in God Classes — start with ComponentFactoryGenerator.cs, RaskEndpointExtensions.cs, ModelInputGenerator.cs. — One of this dimension's main actionable groups (17 warning-level).
Resolve the 17 MethodTooLong finding(s) in God Classes — start with FrameDiffer.cs (2), ModelInputGenerator.cs, UiIcon.cs. — One of this dimension's main actionable groups (17 warning-level).
Resolve the 13 TooManyMethods finding(s) in God Classes — start with ComponentFactoryGenerator.cs, Component.cs, UiClassNames.cs. — One of this dimension's main actionable groups (13 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.
121 duplicated block group(s) detected. One further row reports members as variants of one another; it aggregates block groups already counted above and is not itself counted.
+ 60 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Resolve the 9 Duplicated block (11 lines × 2) finding(s) in Code Duplication — start with ModelInputGenerator.cs (2), EquatableArray.cs, Select.cs. — One of this dimension's main actionable groups (9 warning-level).
Resolve the 7 Duplicated block (12 lines × 2) finding(s) in Code Duplication — start with WireShape.cs, Input.cs, UiCheckboxGroup.cs. — One of this dimension's main actionable groups (7 warning-level).
Resolve the 5 Duplicated block (17 lines × 2) finding(s) in Code Duplication — start with JobSerializerRegistry.cs (2), MailProcessor.cs, RaskServerDiagnostics.cs. — One of this dimension's main actionable groups (5 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.3 / 10Stronggated by 15 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 15 Off the main sequence finding(s) in Coupling. — One of this dimension's main actionable groups (15 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, Component.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.
Do you agree with this assessment?
D9 · Test Distribution9.7 / 10Exemplary✓ Tool-verified
What it measures: Whether the test suite has a healthy mix of unit / integration / end-to-end tests.
Method: Test projects classified (Unit/Integration/BDD/E2E) from compiled metadata; test methods counted exhaustively across projects with placement-agnostic disk fallback. Deterministic.
8399 test methods: 8237 unit, 0 integration, 0 BDD, 162 e2e. The JavaScript/TypeScript suite contributes 3 `it`/`test` case(s) across 2 test file(s) declaring at least one beside 8396 .NET test method(s); its tier split is read from package names and paths only.
✓ On the Gold path — maintain.
Detailed fixes: d9_recommendation.md.
Do you agree with this assessment?
D10 · Test Quality10.0 / 10Stronggated by 23 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), 20 zero-assertion, 3 synchronised by a fixed sleep, no mocking-framework packages referenced (hand-written doubles or no mocking) across 8396 tests. Measured on the C# suite only — at least 39 test source file(s) (.ts) went unread, so its test quality is unmeasured and is not in these counts.
No assertions: WithName_decides_the_client_method_name · ×20tests/Rask.Api.Client.Tests/MinimalApiRoundTripTests.cs:89
Resolve the 20 No assertions finding(s) in Test Quality — start with StateHasChangedTests.cs (2), LiveSessionDirectTests.cs (2), BackendAndOptionsTests.cs (2). — One of this dimension's main actionable groups (20 warning-level).
Resolve the 3 Fixed-sleep synchronisation finding(s) in Test Quality — start with AsyncLifecycleRenderingTests.cs, SendTimeoutTests.cs, RaskSqliteExecutionStrategyTests.cs. — One of this dimension's main actionable groups (3 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.
What it measures: Whether dependencies are current, secure, and not bloated.
Method: Manifest scan via dotnet list package across all projects; worst-signal-per-package deduction (saturating for vulnerabilities, capped-linear for deprecation/outdated) per KLoC. Exhaustive, deterministic.
0 outdated, 0 vulnerable, 0 deprecated packages. Those are the NuGet packages; this repository's npm dependencies were read too — 332 outdated of 891 package(s) across 15 lockfile(s).
Outdated (npm): @angular/animations · ×332
What to do
Enforce Dependency Hygiene in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Verified — provenance only; does not change the score.
Detailed fixes: d12_recommendation.md · top locations in Appendix A, every location in findings.md.
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 1 Leaked secret finding(s) in REDACTED Scanning — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
Enforce REDACTED 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 47 packages use a banned license. ★ DEPTH: every package graded here is one this repository's MSBuild projects declare as a direct `PackageReference` (72 declared), and nothing beyond them was reached — this is the DECLARATION-SITE set, NOT the transitive closure. .NET has no lockfile a checkout is guaranteed to carry and this pass grades an unrestored tree, so a banned licence that only a direct dependency's OWN dependencies pull in is outside this verdict, exactly as the JVM arm's declaration-site verdict is.
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.Server/RaskEndpointExtensions.cs (83×40=3320); src/Rask.Core/Component.cs (55×43=2365); src/Rask.Cli/Commands/NewCommand.cs (50×30=1500) Repeated repair below the complexity floor: src/Rask.Core/Live/QuiescenceScope.cs (4 of 5 changes were fixes); src/Rask.Cqrs.Client/RaskCqrsClientServiceCollectionExtensions.cs (3 of 5 changes were fixes); src/Rask.Storage/RaskStorageServiceCollectionExtensions.cs (3 of 5 changes were fixes)
Resolve the 79 Hotspot finding(s) in Churn × Complexity Hotspots — start with RaskEndpointExtensions.cs, Component.cs, NewCommand.cs. — One of this dimension's main actionable groups (79 warning-level).
Resolve the 4 Repeated repair finding(s) in Churn × Complexity Hotspots — start with QuiescenceScope.cs, RaskCqrsClientServiceCollectionExtensions.cs, RaskStorageServiceCollectionExtensions.cs. — One of this dimension's main actionable groups (4 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.
FileScopedPragmaDisable repeated across 84 filestests/Rask.Core.Tests/Callbacks/AutoCallbackTests.cs:3
+ 4 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Resolve the 40 FileScopedPragmaDisable finding(s) in Explicit Debt — start with BuilderCallbackResetTests.cs, BuilderHoistTests.cs, BuilderLifecycleTests.cs. — One of this dimension's main actionable groups (40 issue-level).
Resolve the 17 NoWarnInCsproj finding(s) in Explicit Debt — start with Rask.Jobs.csproj (2), Rask.Wasm.Tests.csproj, Rask.Ui.Tests.csproj. — One of this dimension's main actionable groups (17 issue-level).
Resolve the 6 EmptyCatchBlock finding(s) in Explicit Debt — start with RaskEndpointExtensions.cs (4), RaskDrainService.cs, BakeScopedAssetsTask.cs. — One of this dimension's main actionable groups (6 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.
173 projects, 5831 source files, 352956 hand-written lines of code (176282 production / 176674 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), 368 inter-project edges (build status unknown — did not finish).
What it measures: Whether the project's documentation is clear, complete, and useful.
Method: Judged by language model at low temperature (0.0-0.1) on a deterministic doc sample (READMEs plus first 25 architecture docs), with two-pass stability filtering. Advisory, sampled.
The Rask documentation is clear, complete, and well-structured. It opens with a strong project description ('the .NET One Person Framework — build, run, and ship a whole product solo, in C#, on one server') plus links to the site and docs, then dives into installation (a one-line curl installer with prerequisites noted as optional), four front ends running on one back end, Rask components, islands composing inside a component tree, and an architecture overview. It is backed by 169 XML-doc coverage figures across 28 documents. The project's documentation is excellent and well-structured. It includes a README for each template (Rask.Templates.solid/README.md to Rask.Templates/vue/client/README.md) describing the front-end framework on an ASP.NET host, its layout, running commands, adding messages, and why the client stays TypeScript. The templates are complete with code examples and cross-reference each other, plus a dedicated TanStack Start README covering getting started, building for production, styling, Nitro deployment, routing, link components, and a recommended IDE setup. A comprehensive architecture/Docs set is not shown but the high-quality template docs alone make this one of the top documentation quality scores. The project's READMEs are clear and complete for a template audience: each one is a focused guide on its own topic (Solid Start, React + TypeScript + Vite, Solid CLI), with concrete commands, real examples, and links to the right documentation. The architecture/Docs files are more comprehensive but not shown in this summary. Coverage across 169 XML-docs ranges from 2% (Rask.Wasm) to 100% (Rask.Templates/solidstart/client/README.md), with most well above 75%.
Documentation: no installation or build instructions · ×5README.md
Detailed fixes: d19_recommendation.md · top locations in Appendix A, every location in findings.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: Per-ADR judgment by language model at low temperature with two-pass stability; confidence is share of ADRs evaluated; enforcement-field presence detected deterministically. Advisory.
What it measures: Whether names — types, methods, variables — are clear and consistent.
Method: Judged by language model at low temperature (0.0-0.1) on a deterministic random symbol sample (fixed size, not exhaustive), with disclosed confidence band. Advisory, sampled.
0 naming inconsistencies across 200 sampled symbols.
✓ On the Gold path — maintain.
Detailed fixes: d21_recommendation.md.
Do you agree with this assessment?
D22 · Internal API ConsistencyStronggated by 3 serious findings◐ Sampled · advisory
What it measures: Whether the internal API surface is consistent and coherent.
Method: Judged by language model at low temperature over a sample of the public API surface (IsPackable or .Contracts types). Sampled, advisory; confidence discounted by model uncertainty.
3 API inconsistencies across a 400-member sample of 1422 exposed types.
Ambiguous overload resolution for SetAsync when both options and typeInfo are provided. The API exposes two overloads that differ only by the presence of JsonTypeInfo, but if a caller wants to specify both, they cannot do so without creating a new overload or using a different method. This forces users to choose between providing options or type info, or requires a third overload.
Same ambiguity issue as SetAsync. If a user wants to provide both JsonTypeInfo and DistributedCacheEntryOptions, they must use the second overload. However, if they only want options, they use the first. This is slightly inconsistent with standard .NET patterns where optional parameters are often combined into a single signature with optional arguments, or distinct overloads are clearly separated by purpose (e.g., one for serialization context, one for caching options). Here, the separation is by parameter presence, which can be confusing.
Same ambiguity issue as SetAsync and GetOrAddAsync. Users cannot provide both JsonTypeInfo and CancellationToken in a way that distinguishes intent clearly if they also want to pass options (though options aren't in GetAsync, the pattern is inconsistent with SetAsync/GetOrAddAsync which have options). More importantly, the existence of two overloads for GetAsync where one adds type info but no options, while SetAsync/GetOrAddAsync have overloads with options, creates a fragmented API surface.
What to do
Resolve the 1 Ambiguous overload resolution for SetAsync when both options and… finding(s) in Internal API Consistency. — One of this dimension's main actionable groups (1 warning-level).
Resolve the 1 Same ambiguity issue as SetAsync. If a user wants to provide both… finding(s) in Internal API Consistency. — One of this dimension's main actionable groups (1 warning-level).
Resolve the 1 Same ambiguity issue as SetAsync and GetOrAddAsync. Users cannot provide… finding(s) in Internal API Consistency. — 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.
556 domain type(s) cross context boundaries across 52 contexts.
Cross-context type Callback (Rask.Core → Rask.Ui) · ×64
Cross-context type Fn (Rask.Core → Rask.Ui) · ×29
Cross-context type Validator (Rask.Core → Rask.Ui) · ×14
Cross-context type RouteUrl (Rask.Core → Rask.Ui) · ×9
Cross-context type AuthResult (Rask.Wire → Rask.Auth.Client) · ×8
+ 10 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Resolve the 64 Cross-context type Callback (Rask.Core → Rask.Ui) finding(s) in Boundary Type-Coupling. — One of this dimension's main actionable groups (64 warning-level).
Resolve the 29 Cross-context type Fn (Rask.Core → Rask.Ui) finding(s) in Boundary Type-Coupling. — One of this dimension's main actionable groups (29 warning-level).
Resolve the 14 Cross-context type Validator (Rask.Core → Rask.Ui) finding(s) in Boundary Type-Coupling. — One of this dimension's main actionable groups (14 warning-level).
Enforce Boundary Type-Coupling in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Verified — provenance only; does not change the score.
Detailed fixes: d23_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D24 · Comment ValueExemplary◐ Sampled · advisory
What it measures: Whether comments are worth it — explaining WHY (valuable) rather than WHAT (redundant).
Method: Judged by language model at low temperature (0.0-0.1) on deterministically sampled inline comments with surrounding code; findings verified back to sampled comments by substring match. Advisory, sampled.
What it measures: Whether any secrets were ever committed — scanned across the full git history, not just now.
Method: REDACTED scan via TWO gitleaks detect passes in an isolated checkout — the full git history, then a second --no-git pass over the working tree as it stands — merged and de-duplicated by (rule, file, line); each match flagged REDACTED. Both invocations are recorded in the audit trail. Exhaustive; when the tool is absent, or when its output cannot be parsed into the expected shape, the dimension is WITHHELD as an explicit measurement gap on our side — unscored and excluded from the lens, never a hedged middling score.
14 finding(s): 0 critical, 14 high, 0 medium, 0 low. Remediation for historically-committed secrets is credential rotation — they remain in history regardless of later deletion.
REDACTED
REDACTED
What to do
Resolve the 13 REDACTED finding(s) in Secrets (history) — start with REDACTED (4), REDACTED (4), REDACTED (2). — One of this dimension's main actionable groups (13 issue-level).
Resolve the 1 Rotate the exposed credentials finding(s) in Secrets (history). — One of this dimension's main actionable groups (1 recommendation-level).
Detailed fixes: d28_recommendation.md · top locations in Appendix A, every location in findings.md.
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).
34 finding(s): 0 critical, 27 high, 7 medium, 0 low. 11 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 390 file(s) — `.claude/skills/add-html-tag/templates/Component.cs` (line 6), `.claude/skills/add-html-tag/templates/ComponentTests.cs` (line 9), `.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), … (+385 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 317 of those file(s) — `src/Rask.Api.Client/RaskApiClientServiceCollectionExtensions.cs`, `src/Rask.Auth.Api/AccountService.cs`, `src/Rask.Auth.Api/AuthContexts.cs`, `src/Rask.Auth.Api/AuthMail.cs`, `src/Rask.Auth.Api/AuthModelCheck.cs`, … (+312 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 9 of those file(s) — `src/Rask.Api.Generators/MinimalApi.cs`, `src/Rask.Cli/Commands/DbCommand.cs`, `src/Rask.Cli/Commands/DeployCommand.cs`, `src/Rask.Cqrs.Server/UploadSessionStore.cs`, `src/Rask.Server/SessionHandoff.cs`, … (+4 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 2 file(s) (e.g. a workflow `run:` block read as shell). Those files WERE scanned and their other rows are unaffected; only those rules' view of those snippets is missing.
REDACTED
REDACTED
What to do
Resolve the 16 REDACTED finding(s) charged to Static Analysis (SAST) — the other 11 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 (27 issue-level, 16 of them charged here).
Resolve the 7 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (3), REDACTED, REDACTED. — One of this dimension's main actionable groups (7 warning-level).
Detailed fixes: d29_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether any dependency has a known published vulnerability (CVE), direct or transitive, in ANY ecosystem the repository declares — Dart pub, Elixir/Hex, Go modules, Java and Kotlin via Maven/Gradle, JavaScript/npm, .NET/NuGet, PHP/Composer, Python/PyPI, RubyGems, Rust/Cargo and Swift.
Method: Dependency-CVE scan across every ecosystem the repository declares, scored ONCE. Three sources are unioned and deduplicated by advisory identity (rule id + alias closure, CVE<->GHSA) scoped to package+version, keeping the worst severity: `osv-scanner --recursive` over osv.dev for Dart pub, Elixir/Hex, Go, Java and Kotlin via Maven/Gradle, npm, PHP/Composer, Python/PyPI, RubyGems, Rust/Cargo and Swift; `trivy fs --scanners vuln` for npm lockfiles; and `dotnet list package --vulnerable --include-transitive` for NuGet (with per-advisory collapse of the project x target-framework fan-out), plus a DECLARED-dependency arm that resolves a published gem's gemspec against rubygems.org where no Gemfile.lock is committed. `SeverityScore(c,h,m,l, normalizer 8.0)`. NotApplicable only when NO ecosystem is readable; if any applicable ecosystem could not be scanned the findings are REPORTED and the score is withheld. Supersedes the npm and OSV arms, retired 2026-09-05.
4 finding(s): 0 critical, 0 high, 2 medium, 2 low. Partial dependency scan: 2 of 3 declared ecosystem(s) were scanned (npm,osv), and the findings above are real and complete for them. nuget was not scanned (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), so this is not the whole dependency surface and the result is reported at reduced confidence.
REDACTED
REDACTED
REDACTED
What to do
Resolve the 2 REDACTED CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (2). — One of this dimension's main actionable groups (2 warning-level).
Resolve the 1 Low vulnerability finding(s) in Dependency Vulnerabilities — start with REDACTED. — One of this dimension's main actionable groups (1 recommendation-level).
Resolve the 1 Low CVE finding(s) in Dependency Vulnerabilities — start with REDACTED. — One of this dimension's main actionable groups (1 recommendation-level).
Detailed fixes: d30_recommendation.md · top locations in Appendix A, every location in findings.md.
Resolve the 47 REDACTED IaC finding(s) in IaC & Container Security — start with REDACTED (47). — One of this dimension's main actionable groups (47 warning-level).
Resolve the 33 REDACTED IaC finding(s) in IaC & Container Security — start with REDACTED (33). — One of this dimension's main actionable groups (33 issue-level).
Resolve the 16 Low IaC finding(s) in IaC & Container Security — start with REDACTED (16). — One of this dimension's main actionable groups (16 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 883 of the 1625 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 3 Change coupling finding(s) in Change Coupling — start with RaskBrowserJsonContext.cs, ProjectGenerator.Server.cs, rask-wasm-api.ts. — One of this dimension's main actionable groups (3 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.
What it measures: Whether any dependency the repository declares is published as MALICIOUS rather than merely vulnerable — a package that is an attacker's work, in any ecosystem osv-scanner reads. Scored apart from D30 because the answer is binary: there is no safe version to upgrade to, and the fix is to remove the package and rotate every credential it could have read.
Method: The same dependency scan D30 reads, partitioned on the scanner's own classification rather than rescanned: a row is MALICIOUS when its id is in the `MAL-` space (the ossf/malicious-packages feed) OR its `database_specific.cwe_ids` carries `CWE-506` ("Embedded Malicious Code"). Both channels are structural; the summary text is deliberately NOT read, because a malicious-package record whose summary says only "Critical severity vulnerability" is a real shape ([GHSA redacted]) and a text matcher misses it. Scored BINARY: any surviving row is 0, whatever its severity and however many CVEs sit beside it — a hostile dependency is not a quantity. Applicability and degradation are D30's: NotApplicable only when no ecosystem is readable, and an unscannable ecosystem degrades rather than reading clean. SCORED, not informational.
No known-vulnerable dependencies in the 2 ecosystem(s) that were scanned (npm,osv). Partial dependency scan: 2 of 3 declared ecosystem(s) were scanned (npm,osv), and the findings above are real and complete for them. nuget was not scanned (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), so this is not the whole dependency surface and the result is reported at reduced confidence.
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 137 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 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/wwwroot/index.html:2, src/Rask.Templates/lit/client/index.html:2, …
A page with no <title> gives no name in the tab, history or screen-reader page list. Add a descriptive <title> in <head>. — src/Rask.Templates/sveltekit/client/src/app.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.
This stylesheet animates but never checks prefers-reduced-motion, so motion-sensitive users can't opt out. Wrap motion in @media (prefers-reduced-motion: no-preference). (×4) — src/Rask.Site/wwwroot/index.html:36, src/Rask.Templates/wasm-hosted/Client/wwwroot/index.html:18, src/Rask.Templates/wasm/wwwroot/index.html:20, …
What to do
Keep a visible focus style (don't remove the outline without a replacement), guard animation with prefers-reduced-motion, and raise low-contrast colour pairs to at least 4.5:1.
Other · 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.
An a11y linter is configured (Documented) but there's no automated a11y test or CI gate. Add vitest-axe to verify at runtime, then gate it in CI. What was searched, so you can tell an absence from a miss: the 81 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
Accessibility linting is already configured — assert with vitest-axe in tests, then gate axe/pa11y/Lighthouse in CI.
Other · Architecture — Whether any singleton service captures a scoped/transient dependency — a silent lifetime/threading bug.
Method: Roslyn scan: DI registrations parsed from AddSingleton/Scoped/Transient; each singleton checked for captured shorter-lifetime dependencies. Exhaustive, deterministic.
Other · Architecture — How the codebase splits by code ROLE — domain, application, infrastructure, test, generated. The significance map behind the knowledge/coupling weighting, and a DDD signal in its own right: a thin domain core under fat infrastructure is the anemic-domain smell, quantified. How each file's role is decided, because the split is only as good as that: a generated name or a build-output tree makes it Generated, a test project makes it Test, and otherwise the file's NAMESPACE and PATH words are matched against fixed vocabularies in a fixed ORDER — domain, then infrastructure, then application — so a file whose words hit two layers is counted under the earlier one. A production file matching none of them counts as application, so that share reads 'application or unclassified' rather than a measured application layer. Roles come from naming convention, never from what the code does.
Method: Roslyn line-count by code ROLE: every source file classified Domain/Application/Infrastructure/Test/Generated by namespace + path convention (the shared CodeRoleClassifier), then significant lines summed per role. Deterministic; the advisory score is the business-logic (domain+application) share of production code.
Coverage: Population: ALL source files, each bucketed into ONE of five roles (Domain/Application/Infrastructure/Test/Generated) by namespace + path convention — a file whose layer isn't named in the convention falls to Application (the neutral default), and the split is line-count, not semantic depth or business value.
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.
`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
`RouteState` is a singleton (one shared instance) but mutates instance state outside any lock (_path, _query; e.g. `_path` at line 35). — src/Rask.Core/Routing/RouteState.cs:16
`Navigator` is a singleton (one shared instance) but mutates instance state outside any lock (_replace, _dirty, _inInitialRender, _inHandler; e.g. `_replace` at line 76). — src/Rask.Core/Routing/Navigator.cs:20
`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
`BrowserSqliteHost` is a singleton (one shared instance) but mutates instance state outside any lock (IsOwner, _takeoverWatch, _ownerHold; e.g. `IsOwner` at line 61). — src/Rask.SQLite.Browser/BrowserSqliteHost.cs:28
`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 65). — src/Rask.Wasm/JSInterop/WasmJSRuntime.cs:26
What to do
Keep singletons stateless or back their state with thread-safe types (Concurrent*/Immutable*); otherwise concurrent callers race.
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.
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. Deterministic, type-level.
`IQueryClient` declares 17 members under just 8 distinct name(s): `Query`, `Query`, `FetchAsync`, `PrefetchAsync`, `SendAsync`, `SendAsync`, `Command`, `Command`, `Command`, `Invalidate`, `Invalidate`, `Invalidate`, `Invalidate`, `Invalidate`, `InvalidateAll`, `SetData`, `SetData`. 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 17 separate responsibilities: a caller binds to 8 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 17 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
Collapse overload sets (optional/default parameters, or an options object) — these interfaces are wide in SIGNATURES, not in responsibilities, so segregating them would relieve no caller.
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.
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 aggregate10.0 / 10Exemplary○ Nothing flagged
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.
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), on a type that also offers no static Create/Of/From/New factory. 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.
Do you agree with this assessment?
DM4 · Rich vs anemic model9.1 / 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.
`QueuedMail` is an aggregate/entity with 15 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service. — src/Rask.Mail/QueuedMail.cs:23
What to do
Move business rules onto the aggregates/entities they govern so invariants are enforced at the source, not in anemic services.
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 clusters of primitives that travel together (a missing value object) are extracted — a low-weight suggestion, LLM-confirmed when configured.
Method: Roslyn (DDD-gated): primitive parameter clusters recurring three or more times across signatures extracted, then confirmed by language model when configured. Advisory, low-weight.
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.SQLite.FullTextSearchQueryInterceptor's [HighlightMarker, SnippetMarker] are judged in Rask.SQLite.FullTextSearchQueryInterceptor.Rewriter, Rask.SQLite.FullTextSearchQueryInterceptor.SearchFinder — 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.
Do you agree with this assessment?
ED5 · Idempotency3.0 / 10Weak◐ Sampled · advisory
Other · Readiness — Whether retry-prone mutations (command handlers + message/event consumers) are idempotent so an at-least-once redelivery or client retry doesn't double-apply the effect — heuristic at-risk detection confirmed by language model, advisory.
Method: Roslyn heuristic (any mutation, ungated): command handlers and message/event consumers that mutate persistent state without a visible idempotency guard (exists/dedup check, upsert, idempotency-key/inbox, conditional/versioned write, fixed-value set) flagged as at-risk; each at-risk candidate then confirmed or cleared by a language model as genuinely non-idempotent versus naturally-idempotent. Advisory without a model (heuristic-only, degraded), per-candidate judged with one.
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. The at-risk subset (no obvious guard) is a HEURISTIC candidate set, each then LLM-JUDGED non-idempotent vs safe; a handler outside those conventions, or a guard the LLM can't confirm, is bounded by the sample. Degrades to heuristic-only when no model is configured.
`Features.IncrementCounterHandler.HandleAsync` mutates persistent state (an event publish) with no idempotency guard, and the model confirms a re-run would double-apply it. A retry or at-least-once redelivery means it can run twice — add an exists/dedup check, an upsert, an idempotency-key/inbox, or a versioned write. — src/Rask.Site/Features/Cqrs/CounterSlice.cs:49
What to do
Make retry-prone mutations idempotent — guard each write with an exists/dedup check, an upsert, an idempotency-key/inbox, or a versioned write, so a re-run doesn't double-apply.
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 sitemap — set <RaskS…") is still in shipped code — typical of generated boilerplate that was never filled in. — src/Rask.Wasm/WasmPrerender.cs:524
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.
`ApplyRender` takes parameters but its body is empty — it accepts inputs and does nothing. Either implement it or remove it. — src/Rask.Wasm/JSInterop.cs:260
`PushHistory` takes parameters but its body is empty — it accepts inputs and does nothing. Either implement it or remove it. — src/Rask.Wasm/JSInterop.cs:267
`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:285
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:22, src/Rask.Site/Features/Elements/ElementsFormsDemo.cs:24
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 placeholder e-mail address ("ada@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/UiKit/UiKitLayoutDemo.cs:93
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/RaskBatteryWiring.cs:69
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:48
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 'Testing' section to the root README — how to run the test suite.
Add an 'Architecture' / 'How it works' section to the root README — the high-level shape.
Add a README to the 119 of 120 project(s) that lack one — worth up to 2 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 significant decisions one document per decision — dated, stating the context, the decision and its consequences — and keep them together wherever your design docs already live (a conventional `docs/adr/` tree, with each file named `NNNN-title` in whatever markup those docs already use, is the most discoverable form).
Maturity · Maturity — Whether the README actually describes the code that exists (LLM-judged, advisory).
Method: Judged by language model at low temperature: README accuracy versus actual projects, within a disclosed tolerance. Advisory, not a measured number.
Do you agree with this assessment?
P1 · CI/CD gates8.5 / 10Exemplary✓ Tool-verified
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.
What to do
Run the test suite in CI via an explicit runner step (`dotnet test` for the toolchain this pipeline already uses) and gate merges on it.
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. Exhaustive, deterministic.
Only 20/47 service-like projects use logging (pure contract/DTO projects are excluded — they have nothing to log). Of those 47, 2 ship a process this repository operates; the rest are libraries their consumer hosts, where the logging decision belongs to the host.
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.
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 and the service already exposes health probe endpoints (healthz/livez/readyz or a container healthcheck), but no manifest in this repository wires them into readiness/liveness probes, a rolling-update strategy, lifecycle hooks or a migration job — a bad release is harder to detect and reverse. If that wiring lives in a separate ops/Helm repository, document the pointer here so release safety is evidenced.
What to do
Wire the existing health endpoints into readiness/liveness probes and a rolling-update (or blue/green) strategy in the deployment manifests — or document where that wiring lives — 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: Roslyn scan: Polly resilience markers (Retry, CircuitBreaker, Timeout) on outbound HTTP invocations. Computed per type, deterministic.
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. Exhaustive per project, deterministic.
`EnsureCreated()` builds the schema once and can't evolve it — there's no upgrade path for an existing production database, and it bypasses the migrations history. Adopt a versioned schema-migration mechanism (with EF Core: `dotnet ef migrations add` + `Migrate()` on startup) so schema changes are versioned and applied safely. — src/Rask.Data/TestDatabase.cs:91
What to do
Replace EnsureCreated() with a versioned schema-migration mechanism (EF Core migrations) so the production schema can evolve safely and reproducibly.
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 — scored as a bonus ladder (absence is neutral, never a deduction). Deterministic, presence detection.
Readiness · Performance — Whether the code is written to minimise allocations so it doesn't pressure its host's memory manager — buffer/slice views over copies, object pooling, stack or value-type allocation, and buffer writers. Reward-only: credited where present, never penalised where a simpler style is fine.
Raise allocation-aware density on the hot paths — currently 842 use(s) across 178,850 production line(s) (~4.7/1k). More Span/Memory, pooling (ArrayPool/ObjectPool), stackalloc and ValueTask on the allocation-heavy paths climbs this toward 10.
Readiness · Performance — Whether asynchronous code stays responsive — it avoids sync-over-async blocking (.Wait()/.GetAwaiter().GetResult()) that wastes threads and risks deadlock, and, where the code is a reusable library, awaits with ConfigureAwait(false) so it never captures and stalls its caller's context.
Method: Production-source scan: sync-over-async blocking (.Wait()/.GetAwaiter().GetResult()) counted everywhere, and — for a library with ≥5 awaits — the share of awaits using ConfigureAwait(false). Deterministic, syntax/text detection.
12 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).
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 Safety10.0 / 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.
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.
26 duplicated blocks under src/Rask.Templates/ have copies in at least two of the sibling directories analog, angular, lit, nextjs, nuxt, preact (+7 more sibling(s) not listed) — 24 of them are reported below, and 2 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 26 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 26 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 26 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.Templates/preact/client/src/app.tsx:2
25 duplicated blocks under src/ have copies in at least two of the sibling directories Rask.Core, Rask.Server, Rask.Site, Rask.Templates, Rask.Wasm — 19 of them are reported below, and 6 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 25 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 25 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 25 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:1461
src/Rask.Templates/preact/client/src/app.tsx:2 · src/Rask.Templates/react/client/src/App.tsx:2 — these 2 files are line-for-line copies of one another — 79 lines are identical, in the same order, in every one of them — so this is one fact about the file set, not a block to extract. An edit made to one file and not the others changes behaviour silently, which is the failure a wholesale copy guarantees. Pick one file as the single source and derive the others from it (re-export it, spread it into the local overrides each variant genuinely needs, or generate the copies at build time) — the few lines that differ between the files are exactly the part each variant should still own. Check first whether the copies are deliberately standalone deliverables (a translation file seeded from its sibling and waiting to be translated); where they are, the duplication is the design, and the honest move is to mark the seeded file as untranslated rather than to let it pass as done. — src/Rask.Templates/preact/client/src/app.tsx:2
src/Rask.Templates/nextjs/client/app/auth-form.tsx:3 · src/Rask.Templates/tanstack-start/client/src/components/AuthForm.tsx:1 — these 2 files are line-for-line copies of one another — 56 lines are identical, in the same order, in every one of them — so this is one fact about the file set, not a block to extract. An edit made to one file and not the others changes behaviour silently, which is the failure a wholesale copy guarantees. Pick one file as the single source and derive the others from it (re-export it, spread it into the local overrides each variant genuinely needs, or generate the copies at build time) — the few lines that differ between the files are exactly the part each variant should still own. Check first whether the copies are deliberately standalone deliverables (a translation file seeded from its sibling and waiting to be translated); where they are, the duplication is the design, and the honest move is to mark the seeded file as untranslated rather than to let it pass as done. — src/Rask.Templates/nextjs/client/app/auth-form.tsx:3
src/Rask.Templates/solid/client/src/Auth.tsx:1 · src/Rask.Templates/solidstart/client/src/components/AuthForm.tsx:1 — these 2 files are line-for-line copies of one another — 54 lines are identical, in the same order, in every one of them — so this is one fact about the file set, not a block to extract. An edit made to one file and not the others changes behaviour silently, which is the failure a wholesale copy guarantees. Pick one file as the single source and derive the others from it (re-export it, spread it into the local overrides each variant genuinely needs, or generate the copies at build time) — the few lines that differ between the files are exactly the part each variant should still own. Check first whether the copies are deliberately standalone deliverables (a translation file seeded from its sibling and waiting to be translated); where they are, the duplication is the design, and the honest move is to mark the seeded file as untranslated rather than to let it pass as done. — src/Rask.Templates/solid/client/src/Auth.tsx:1
src/Rask.Templates/nextjs/client/app/auth-form.tsx:3 · src/Rask.Templates/react/client/src/Auth.tsx:1 — these 2 files are line-for-line copies of one another — 52 lines are identical, in the same order, in every one of them — so this is one fact about the file set, not a block to extract. An edit made to one file and not the others changes behaviour silently, which is the failure a wholesale copy guarantees. Pick one file as the single source and derive the others from it (re-export it, spread it into the local overrides each variant genuinely needs, or generate the copies at build time) — the few lines that differ between the files are exactly the part each variant should still own. Check first whether the copies are deliberately standalone deliverables (a translation file seeded from its sibling and waiting to be translated); where they are, the duplication is the design, and the honest move is to mark the seeded file as untranslated rather than to let it pass as done. — src/Rask.Templates/nextjs/client/app/auth-form.tsx:3
src/Rask.Templates/preact/client/src/auth.tsx:2 · src/Rask.Templates/react/client/src/Auth.tsx:2 — these 2 files are line-for-line copies of one another — 52 lines are identical, in the same order, in every one of them — so this is one fact about the file set, not a block to extract. An edit made to one file and not the others changes behaviour silently, which is the failure a wholesale copy guarantees. Pick one file as the single source and derive the others from it (re-export it, spread it into the local overrides each variant genuinely needs, or generate the copies at build time) — the few lines that differ between the files are exactly the part each variant should still own. Check first whether the copies are deliberately standalone deliverables (a translation file seeded from its sibling and waiting to be translated); where they are, the duplication is the design, and the honest move is to mark the seeded file as untranslated rather than to let it pass as done. — src/Rask.Templates/preact/client/src/auth.tsx:2
src/Rask.Templates/react/client/src/Auth.tsx:1 · src/Rask.Templates/tanstack-start/client/src/components/AuthForm.tsx:1 — these 2 files are line-for-line copies of one another — 52 lines are identical, in the same order, in every one of them — so this is one fact about the file set, not a block to extract. An edit made to one file and not the others changes behaviour silently, which is the failure a wholesale copy guarantees. Pick one file as the single source and derive the others from it (re-export it, spread it into the local overrides each variant genuinely needs, or generate the copies at build time) — the few lines that differ between the files are exactly the part each variant should still own. Check first whether the copies are deliberately standalone deliverables (a translation file seeded from its sibling and waiting to be translated); where they are, the duplication is the design, and the honest move is to mark the seeded file as untranslated rather than to let it pass as done. — src/Rask.Templates/react/client/src/Auth.tsx:1
src/Rask.Templates/svelte/client/eslint.config.mjs:13 · src/Rask.Templates/sveltekit/client/eslint.config.mjs:13 — the 2 copies are spread across 2 files, and the SHAPE of this repetition could not be determined. It is not a run of declarations, a listing, a declaration header, a type body or a slice through a construct — and it was not measured as a run of executable statements either, so this row cannot tell you whether a function can stand where these lines are. Read the two spans before acting, because the move is opposite in the two cases. Where they are statements, the ordinary answer holds: give the shared part one home and call it from each site. Where they turn out to be declarations, a literal's entries, or the cases of an enumeration, there is no call site to call anything from, and collapsing them would delete what each copy pins — a shared base type, a generated set, or one exported constant each site refers to is the move instead, and sometimes the honest answer is that there is nothing to extract at all. Reported because the copies drift apart the first time only one of them is edited, which is true whichever of those they are. — src/Rask.Templates/svelte/client/eslint.config.mjs:13
src/Rask.Templates/nuxt/client/eslint.config.mjs:13 · src/Rask.Templates/vue/client/eslint.config.mjs:13 — the 2 copies are spread across 2 files, and the SHAPE of this repetition could not be determined. It is not a run of declarations, a listing, a declaration header, a type body or a slice through a construct — and it was not measured as a run of executable statements either, so this row cannot tell you whether a function can stand where these lines are. Read the two spans before acting, because the move is opposite in the two cases. Where they are statements, the ordinary answer holds: give the shared part one home and call it from each site. Where they turn out to be declarations, a literal's entries, or the cases of an enumeration, there is no call site to call anything from, and collapsing them would delete what each copy pins — a shared base type, a generated set, or one exported constant each site refers to is the move instead, and sometimes the honest answer is that there is nothing to extract at all. Reported because the copies drift apart the first time only one of them is edited, which is true whichever of those they are. — src/Rask.Templates/nuxt/client/eslint.config.mjs:13
src/Rask.Templates/preact/client/eslint.config.mjs:13 · src/Rask.Templates/react/client/eslint.config.mjs:13 · src/Rask.Templates/tanstack-start/client/eslint.config.mjs:13 — the 3 copies are spread across 3 files, and the SHAPE of this repetition could not be determined. It is not a run of declarations, a listing, a declaration header, a type body or a slice through a construct — and it was not measured as a run of executable statements either, so this row cannot tell you whether a function can stand where these lines are. Read the two spans before acting, because the move is opposite in the two cases. Where they are statements, the ordinary answer holds: give the shared part one home and call it from each site. Where they turn out to be declarations, a literal's entries, or the cases of an enumeration, there is no call site to call anything from, and collapsing them would delete what each copy pins — a shared base type, a generated set, or one exported constant each site refers to is the move instead, and sometimes the honest answer is that there is nothing to extract at all. Reported because the copies drift apart the first time only one of them is edited, which is true whichever of those they are. — src/Rask.Templates/preact/client/eslint.config.mjs:13
src/Rask.Core/Resources/browser/deviceMotion.ts:40 · src/Rask.Core/Resources/browser/deviceOrientation.ts:51 — the two spans are one implementation copied and then locally edited — 215 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/browser/deviceMotion.ts:40
src/Rask.Templates/solid/client/eslint.config.mjs:13 · src/Rask.Templates/solidstart/client/eslint.config.mjs:13 — the 2 copies are spread across 2 files, and the SHAPE of this repetition could not be determined. It is not a run of declarations, a listing, a declaration header, a type body or a slice through a construct — and it was not measured as a run of executable statements either, so this row cannot tell you whether a function can stand where these lines are. Read the two spans before acting, because the move is opposite in the two cases. Where they are statements, the ordinary answer holds: give the shared part one home and call it from each site. Where they turn out to be declarations, a literal's entries, or the cases of an enumeration, there is no call site to call anything from, and collapsing them would delete what each copy pins — a shared base type, a generated set, or one exported constant each site refers to is the move instead, and sometimes the honest answer is that there is nothing to extract at all. Reported because the copies drift apart the first time only one of them is edited, which is true whichever of those they are. — src/Rask.Templates/solid/client/eslint.config.mjs:13
src/Rask.Templates/analog/client/eslint.config.mjs:12 · src/Rask.Templates/angular/client/eslint.config.mjs:12 · src/Rask.Templates/nextjs/client/eslint.config.mjs:12 — the 3 copies are spread across 3 files, and the SHAPE of this repetition could not be determined. It is not a run of declarations, a listing, a declaration header, a type body or a slice through a construct — and it was not measured as a run of executable statements either, so this row cannot tell you whether a function can stand where these lines are. Read the two spans before acting, because the move is opposite in the two cases. Where they are statements, the ordinary answer holds: give the shared part one home and call it from each site. Where they turn out to be declarations, a literal's entries, or the cases of an enumeration, there is no call site to call anything from, and collapsing them would delete what each copy pins — a shared base type, a generated set, or one exported constant each site refers to is the move instead, and sometimes the honest answer is that there is nothing to extract at all. Reported because the copies drift apart the first time only one of them is edited, which is true whichever of those they are. — src/Rask.Templates/analog/client/eslint.config.mjs:12
src/Rask.Templates/preact/client/src/app.tsx:35 · src/Rask.Templates/react/client/src/App.tsx:39 · src/Rask.Templates/solid/client/src/App.tsx:19 — the 3 copies are spread across 3 files, and the CITED SPAN is a DECLARATION HEADER — the name, parameter list with its constraints and defaults, and base-type clause of a declaration — rather than statements inside a body. A header cannot be lifted into a helper: there is no expression position for a call to stand in, and the copies are frequently required to match, because one declaration passes its parameters straight through to the other. So the move is not extraction. Give the repeated pieces names — factor a long constraint or base-type expression into one named type both declarations refer to — and where the headers must stay identical, derive one from the other (a shared base declaration, or a single alias that spells the parameter set once) so that changing it once changes both. Where the language offers neither, treat the two as a pair that must be edited together: they drift apart the first time only one of them is changed, which is why this is reported. — src/Rask.Templates/preact/client/src/app.tsx:35
src/Rask.Templates/angular/client/src/push.ts:20 · src/Rask.Templates/lit/client/src/push.ts:20 · src/Rask.Templates/preact/client/src/push.ts:20 · src/Rask.Templates/react/client/src/push.ts:20 · +3 more site(s) not listed — the 7 copies are spread across 7 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. There is one copy in each of 7 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.Templates/angular/client/src/push.ts:20
src/Rask.Server/Resources/rask.ts:1461 · src/Rask.Wasm/Resources/rask.wasm.ts:641 — 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:1461
src/Rask.Wasm/Resources/rask-wasm-api.ts:302 · src/Rask.Wasm/Resources/rask-wasm-api.ts:439 — 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.Wasm/Resources/rask-wasm-api.ts:302
src/Rask.Templates/svelte/client/src/lib/Greeting.svelte:7 · src/Rask.Templates/vue/client/src/App.vue:8 — the two spans are one implementation copied and then locally edited — 134 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.Templates/svelte/client/src/lib/Greeting.svelte:7
src/Rask.Server/Resources/rask.ts:1955 · src/Rask.Wasm/Resources/rask.wasm.ts:1000 — 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:1955
src/Rask.Server/Resources/rask.ts:1674 · src/Rask.Wasm/Resources/rask.wasm.ts:763 — 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:1674
src/Rask.Templates/analog/client/src/app/pages/auth-form.ts:68 · src/Rask.Templates/angular/client/src/app/auth.ts:71 — 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.Templates/analog/client/src/app/pages/auth-form.ts:68
src/Rask.Templates/angular/client/public/rask-sw.js:4 · src/Rask.Templates/lit/client/public/rask-sw.js:4 · src/Rask.Templates/preact/client/public/rask-sw.js:4 · src/Rask.Templates/react/client/public/rask-sw.js:4 · +3 more site(s) not listed — the 7 copies are spread across 7 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. There is one copy in each of 7 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.Templates/angular/client/public/rask-sw.js:4
src/Rask.Wasm/Resources/rask-wasm-api.ts:504 · src/Rask.Wasm/Resources/rask-wasm-api.ts:710 — 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.Wasm/Resources/rask-wasm-api.ts:504
src/Rask.Server/Resources/rask.ts:1362 · src/Rask.Wasm/Resources/rask.wasm.ts:157 — 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:1362
src/Rask.Templates/_islands/preact/Features/Islands/Preact/PreactCounter.tsx:5 · src/Rask.Templates/_islands/react/Features/Islands/React/ReactCounter.tsx:5 — 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.Templates/_islands/preact/Features/Islands/Preact/PreactCounter.tsx:5
src/Rask.Core/Resources/browser/auth.ts:213 · src/Rask.Core/Resources/browser/auth.ts:283 — 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:213
src/Rask.Core/Resources/browser/globals.ts:719 · src/Rask.Core/Resources/browser/globals.ts:771 · src/Rask.Core/Resources/browser/globals.ts:793 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. — src/Rask.Core/Resources/browser/globals.ts:719
src/Rask.Server/Resources/rask.ts:1775 · src/Rask.Wasm/Resources/rask.wasm.ts:852 — 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:1775
src/Rask.Core/Resources/browser/globals.ts:377 · src/Rask.Core/Resources/browser/globals.ts:444 · src/Rask.Core/Resources/rask-api.ts:64 · src/Rask.Wasm/Resources/rask-wasm-api.ts:135 · +3 more site(s) not listed — the 3 copies are spread across 3 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.Core/Resources/browser/globals.ts:377
src/Rask.Site/Features/Islands/React/ReactCounter.tsx:13 · src/Rask.Templates/_islands/preact/Features/Islands/Preact/PreactCounter.tsx:5 · src/Rask.Templates/_islands/react/Features/Islands/React/ReactCounter.tsx:5 — the 3 copies are spread across 3 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — src/Rask.Site/Features/Islands/React/ReactCounter.tsx:13
src/Rask.Wasm/Resources/rask-wasm-api.ts:366 · src/Rask.Wasm/Resources/rask-wasm-api.ts:478 — 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.Wasm/Resources/rask-wasm-api.ts:366
src/Rask.External/client/preact.ts:45 · src/Rask.External/client/react.ts:42 — 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.External/client/preact.ts:45
src/Rask.Wasm/Resources/rask-wasm-api.ts:246 · src/Rask.Wasm/Resources/rask-wasm-api.ts:378 — 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.Wasm/Resources/rask-wasm-api.ts:246
src/Rask.Core/Resources/rask-dom-path.ts:70 · src/Rask.Core/Resources/rask-dom.ts:60 — 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.Templates/solidstart/client/src/routes/about.tsx:4 · src/Rask.Templates/solidstart/client/src/routes/index.tsx:4 — the 2 copies are spread across 2 files, and the CITED SPAN is a DECLARATION HEADER — the name, parameter list with its constraints and defaults, and base-type clause of a declaration — rather than statements inside a body. A header cannot be lifted into a helper: there is no expression position for a call to stand in, and the copies are frequently required to match, because one declaration passes its parameters straight through to the other. So the move is not extraction. Give the repeated pieces names — factor a long constraint or base-type expression into one named type both declarations refer to — and where the headers must stay identical, derive one from the other (a shared base declaration, or a single alias that spells the parameter set once) so that changing it once changes both. Where the language offers neither, treat the two as a pair that must be edited together: they drift apart the first time only one of them is changed, which is why this is reported. — src/Rask.Templates/solidstart/client/src/routes/about.tsx:4
src/Rask.Templates/svelte/client/src/lib/Auth.svelte:17 · src/Rask.Templates/sveltekit/client/src/lib/AuthForm.svelte:17 — 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.Templates/svelte/client/src/lib/Auth.svelte:17
src/Rask.Core/Resources/rask-dom.ts:463 · src/Rask.Core/Resources/rask-dom.ts:646 — 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-dom.ts:463
src/Rask.Server/Resources/rask.ts:1573 · src/Rask.Wasm/Resources/rask.wasm.ts:214 — 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:1573
src/Rask.Server/Resources/rask.ts:1894 · src/Rask.Wasm/Resources/rask.wasm.ts:908 — 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:1894
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.
morph has cyclomatic complexity 74 and cognitive complexity 132; 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:503
serialize has cyclomatic complexity 38 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. — src/Rask.External/extractor/extract-props.ts:499
applyDiff has cyclomatic complexity 34 and cognitive complexity 71; 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-dom.ts:158
extractIsland has cyclomatic complexity 29 and cognitive complexity 46; 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.External/extractor/extract-props.ts:231
extractAngular has cyclomatic complexity 26 and cognitive complexity 41; 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.External/extractor/extract-props.ts:1188
renderChildren 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. — src/Rask.External/client/angular.ts:223
renderChildren has cyclomatic complexity 25 and cognitive complexity 37; 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.External/client/lit.ts:128
extractLit has cyclomatic complexity 25 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.External/extractor/extract-props.ts:941
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:1496
showDevError has cyclomatic complexity 20 and cognitive complexity 21; 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-deverror.ts:232
onFrame has cyclomatic complexity 19 and cognitive complexity 22; 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:400
trackHeadAsset has cyclomatic complexity 19 and cognitive complexity 17; 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.Wasm/Resources/rask.wasm.ts:115
applyManifest has cyclomatic complexity 18 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.Wasm/Resources/rask-wasm-api.ts:15
(anonymous) has cyclomatic complexity 18 and cognitive complexity 18; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive 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-dom.ts:901
raskNotePendingFormState has cyclomatic complexity 17 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 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:344
(anonymous) has cyclomatic complexity 16 and cognitive complexity 12; 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.DevTools/Resources/panel/panel-client.ts:201
(anonymous) has cyclomatic complexity 15 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.Server/Resources/rask-http-transport.ts:356
handle has cyclomatic complexity 15 and cognitive complexity 21; 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.DevTools/Resources/host/bridge.ts:52
saveRestoreFields has cyclomatic complexity 15 and cognitive complexity 21; 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:778
(anonymous) has cyclomatic complexity 15 and cognitive complexity 20; 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-events.ts:319
What to do
Break down the listed branch-heavy functions; aim P95 cyclomatic ≤ 5.
Do you agree with this assessment?
R3 · Large Files7.9 / 10Strong✓ Tool-verified
React / JS · Code Health — How many source files exceed the large-file threshold.
Method: Components/modules exceeding the large-file threshold, counted exhaustively across the frontend source tree. Deterministic.
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 Coverage1.8 / 10Weak✓ 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. (×40) — src/Rask.Server/Resources/rask.ts, src/Rask.External/extractor/extract-props.ts, src/Rask.Wasm/Resources/rask.wasm.ts, …
What to do
16 of the 142 unreached modules are entry points — the browser loads some as a top-level script and something else executes the rest by path, so no import specifier addresses them and no public entry publishes them. An importing test cannot be written for them as they ship, and two different things are worth doing here — they are not the same thing. To EXERCISE them, a browser or end-to-end suite that loads the page, or a test that runs the script the way its caller does; that is worth having, but it will NOT clear this row, because reachability is measured over the import graph and running a file by path adds no edge to it. To CLEAR it, make them addressable: lift the logic into a module a test can import and leave the entry points thin shims over it, or put their bodies behind a main-guard (`import.meta.url === argv[1]`) and export them. Add tests that import the other 126 — directly or through their public entry.
React / JS · Readiness — How outdated the npm dependencies are (a maturity signal). JS/npm CVEs are scored separately in D30 (JS/npm Dependency Vulnerabilities).
Method: npm dependency staleness from manifest/registry metadata (a maturity signal; JS/npm CVEs are scored separately in D30, which answers dependency vulnerabilities for every ecosystem). Deterministic.
Do you agree with this assessment?
R6 · Tooling10.0 / 10Exemplary✓ Tool-verified
React / JS · Readiness — Whether the project wires up test, lint and typecheck — detected from each package.json script's COMMAND (eslint / tsc / vitest / jest / playwright), not just its name, and corroborated against CI-workflow invocations so a tool run only in CI still counts.
Method: package.json scanned for test/lint/typecheck script wiring. Deterministic presence check.
Do you agree with this assessment?
R7 · Dead Code8.2 / 10Strong✓ 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.
10 file(s) (~477 LoC) were excluded from dead-code analysis — declare main/module/exports or a conventional entry (src/index.*, an index.html script) so reachability can see this package. — src/Rask.Site
5 file(s) (~442 LoC) were excluded from dead-code analysis. This package's entry point(s) resolved, but the walk stopped one hop in: src/Rask.Templates/lit/client/src/my-element.ts imports './rask/client', 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. — src/Rask.Templates/lit/client
12 file(s) (~548 LoC) were excluded from dead-code analysis. This package's entry point(s) resolved, but the walk stopped one hop in: src/Rask.Templates/tanstack-start/client/src/router.tsx imports './routeTree.gen', 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. — src/Rask.Templates/tanstack-start/client
Unreachable from the 50 application, 70 tooling and 54 test entry point(s) detected in this repo. Gate removals on `npm run build` — an undetected custom entry would make these reachable.
no import path from any entry point (50 application, 70 tooling, 54 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (src/Rask.Spa.Hosting/client/query.ts) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it — src/Rask.Spa.Hosting/client/client.ts
no import path from any entry point (50 application, 70 tooling, 54 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make (×30) — src/Rask.External/client/angular.ts, src/Rask.External/client/svelte.svelte.ts, src/Rask.Spa.Hosting/client/query.ts, …
no import path from any entry point (50 application, 70 tooling, 54 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (src/Rask.Templates/analog/client/src/app/pages/index.page.ts) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it — src/Rask.Templates/analog/client/src/app/pages/analog-welcome.ts
no import path from any entry point (50 application, 70 tooling, 54 test roots considered), but 2 in-repo import(s) from 2 other file(s) do name it (src/Rask.Templates/analog/client/src/app/pages/login.page.ts, src/Rask.Templates/analog/client/src/app/pages/register.page.ts) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it — src/Rask.Templates/analog/client/src/app/pages/auth-form.ts
no import path from any entry point (50 application, 70 tooling, 54 test roots considered), but 2 in-repo import(s) from 2 other file(s) do name it (src/Rask.Templates/solidstart/client/src/routes/login.tsx, src/Rask.Templates/solidstart/client/src/routes/register.tsx) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it — src/Rask.Templates/solidstart/client/src/components/AuthForm.tsx
no import path from any entry point (50 application, 70 tooling, 54 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (src/Rask.External/client/svelte.svelte.ts) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it — src/Rask.External/client/RaskHost.svelte
no import path from any entry point (50 application, 70 tooling, 54 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (src/Rask.External/client/RaskHost.svelte) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it — src/Rask.External/client/RaskTree.svelte
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 · Readiness — npm dependency truthfulness (D-386): unused dependencies, imports not declared anywhere, and type-/test-only packages shipped as production deps.
Method: npm dependency truthfulness: unused dependencies, imports declared nowhere, and type-/test-only packages shipped as production deps — from the manifest + import graph. Deterministic.
Imported but not declared in any reachable package.json — installs work only by hoisting accident. (×4) — src/Rask.External/client/preact.ts:14, src/Rask.External/client/react.ts:9, src/Rask.External/client/react.ts:10, …
Imported only as a TYPE and declared in no reachable package.json. The import is erased at compile time, so nothing is installed and no runtime resolution depends on it — but type-checking a clean clone will fail. Declare the typings it resolves through (or the package itself) in the owning package.json. (×2) — src/Rask.External/extractor/extract-props.ts:19, tests/Rask.External.Tasks.Tests/ExtractorFixtures/modules/fixture-button/index.d.ts:4
Declared in src/Rask.Site/package.json but never imported anywhere in that package or its workspace members — no static import reaches it. Usually that is dead weight and attack surface, but two shapes are indistinguishable from source and are NOT dead: an optional or native peer that another dependency loads dynamically at runtime, and a package a build, docs or test step installs and invokes separately. Confirm which of the three this is before removing it. (×3)
What to do
Remove unused dependencies, declare unlisted imports explicitly, and demote type-/test-only packages to devDependencies.
React / JS · Architecture — Import cycles in the module graph (D-386) — files that can only be understood and changed together.
Method: Import cycles in the module graph, detected exhaustively over JS/TS imports (the same cycle detection as the .NET coupling dimension). Deterministic.
Other · Security — Transport security, security headers, secure cookies, input validation, middleware order and crypto hygiene (presence, not runtime).
`SaltBytes` 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. This repository constructs key or salt material fixed at compile time at 2 sites, not one: `src/Rask.Auth.Api/PasswordHasher.cs:61` (key-derivation salt, `SaltBytes`), `src/Rask.DevTools/Endpoints/DevToolsPanelTokens.cs:24` (MAC key, `TokenBytes`). Each is a separate decision — fixing only the line this row cites leaves the others in place. — src/Rask.Auth.Api/PasswordHasher.cs:61
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. This repository constructs key or salt material fixed at compile time at 2 sites, not one: `src/Rask.Auth.Api/PasswordHasher.cs:61` (key-derivation salt, `SaltBytes`), `src/Rask.DevTools/Endpoints/DevToolsPanelTokens.cs:24` (MAC key, `TokenBytes`). Each is a separate decision — fixing only the line this row cites leaves the others in place.
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. (×12) — src/Rask.Cache/RaskDistributedCache.cs:36, src/Rask.Cache/RaskDistributedCache.cs:110, src/Rask.Cache/RaskDistributedCache.cs:118, …
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. 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. 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. Deterministic, provable per finding. Advisory.
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. 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.
Only 372/621 async methods accept a CancellationToken, so in-flight work can't be stopped early when the caller gives up — whatever ends it in your host (shutdown signal, timeout, abandoned request, user cancel). Thread a token through the call chain and honour it at each await and loop; where a method genuinely cannot be interrupted, omitting it is a deliberate choice — judge against your hosting model.
No CancellationToken parameter — this work can't be stopped early once started. (×39) — src/Rask.Api/RaskApiEndpointExtensions.cs:75, src/Rask.Auth.Api/AuthSessions.cs:222, src/Rask.Auth.Api/RaskAuthEndpointExtensions.cs:108, …
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.
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.
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. Deterministic, provable per finding. Advisory.
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. 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. 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. 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 guard6.9 / 10Strong✓ Tool-verified
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.
This condition tests `url` for emptiness and then indexes it on a branch that test does not reach. `url[0]` is evaluated whenever the guarded half is false — which includes the case the guard exists to anticipate, `url` being empty — so an empty `url` indexes position 0 of nothing and throws. This same condition already shows the intended bracketing at line 27: `url[1]` sits INSIDE the guard. Either the guard is load-bearing, in which case this access escapes it and crashes, or `url` cannot be empty here, in which case the guard beside it is dead code — the condition is wrong under both readings. Move the parenthesis so the emptiness test brackets every access to `url`. — src/Rask.Core/Routing/LocalUrl.cs:26
What to do
Each finding names the index access that escapes the guard and the line of the correctly bracketed access beside it. Compare the two: they differ only in where one parenthesis sits. Move it so the emptiness test brackets every access to that symbol — and if the value provably cannot be empty at this point, delete the test rather than leave a condition that guards one access and not its neighbour.
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. 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)` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter. — src/Rask.Blazor/BlazorComponent.cs:432
`catch` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter. (×3) — src/Rask.Core/Forms/ModelGraphWalker.cs:162, src/Rask.Core/Forms/ModelGraphWalker.cs:216, src/Rask.Wasm/RouteSeeder.cs:30
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. (×6) — src/Rask.Server/RaskDrainService.cs:127, src/Rask.Server/RaskEndpointExtensions.cs:1364, src/Rask.Server/RaskEndpointExtensions.cs:1443, …
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. 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.
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 — 1 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 — 9 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
X6 Hand-rolled structured-format parsing — 7 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
X7 Silent fallback defaults — 3 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
X8 JS interop contract — 40 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
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 — 24 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.
D11 Test Reliability — Test runner surfaced no tests
D16 Bus Factor — single-contributor repository — bus factor is not applicable
D25 ADR Conformance — no ADRs to check
D27 Navigability — symbol resolution incomplete — navigability not assessed
D32 Data Compliance (PII/GDPR) — 378 file(s) were not parsed by semgrep — the PII/GDPR ruleset never ran over them
D39 IL Efficiency — IL not measured — the analyzer's build of the target did not succeed
D40 Network Egress Confinement — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here.
D41 Kernel & Syscall Confinement — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here.
D42 Runtime Threat Enforcement — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here.
D7 Architectural Integrity — no checkable ADRs and no dependency cycles — architectural integrity not assessed
D8 Code Coverage — Coverage NOT MEASURED: the .NET half could not be measured — no coverage produced (collector absent, or test run exceeded the inline budget); the JavaScript/TypeScript half could not be measured — src/Rask.Templates/analog/client/ runs vitest but declares no coverage provider, so the suite can run and still produce no lcov — add `@vitest/coverage-v8` (or `@vitest/coverage-istanbul`) as a devDependency. This repository's production source spans both ecosystems, and no partial figure is published as if it were the whole: coverage is excluded from the score rather than counted as a near-zero. The named suite step is one the repository's maintainers can perform; once it passes, the real number is measured on the next scan. Alternatively, commit the lcov/Cobertura report your CI produces and it is read without a re-run.
DM12 Ambient inputs in the domain — no domain-layer types detected — ambient-input check not applicable
DM2 Strongly-typed ids — no id-bearing domain types detected — strongly-typed-id adoption not assessable
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)
ED1 Event-Driven — applicable but not scored (2 of 3 signals for this style — below the bar we score at): 1 event handler(s); 9 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 — no coverage report found on disk — produce a coverage report in a standard format (Cobertura — `dotnet test --collect:"XPlat Code Coverage"` with a `coverlet.collector` PackageReference) and commit it — a hosted scan measures a clone of the repository, so a report that exists only in a working tree, a CI runner's or your own, never reaches it; the artefact is commonly gitignored, so `git add -f` that one file (or un-ignore its path) and commit it alongside the code it measures, or wire coverage collection into CI, to enable this cross-layer check
R11 Import Boundaries — No recognizable feature-sliced/layered src layout — boundary rules not applicable.
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/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: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/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/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/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/MouseModifiersHandlerTests.cs:3— #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:6— #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: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/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/RaskPrerenderTests.cs:5— #pragma warning disable RASK014 // test-defined Component subclasses have no generated chain entries — 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.Server.Tests/WebSockets/MountNavigationTests.cs:7— #pragma warning disable RASK014 // test-defined Component subclasses have no generated chain entries — 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.Wasm.Tests/Hosting/PrerenderBatteryWiringTests.cs:6— #pragma warning disable RASK014 // test-defined Component subclasses have no generated chain entries — 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.Wasm.Tests/Hosting/WasmPrerenderTests.cs:7— #pragma warning disable RASK014 // test-defined Component subclasses have no generated chain entries — 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.Server.Tests/Authentication/DeferredAuthNavTestApp.cs:7— #pragma warning disable RASK019 // test-infra app predates framework-managed <head> — 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.
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.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.Tests/Rask.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.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.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.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.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.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 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 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.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.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.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 Directory.Build.props:109— 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.
EmptyCatchBlock src/Rask.Server/RaskDrainService.cs:127— empty catch block — the error is discarded with nothing recorded, so a failure here leaves no trace anywhere. Narrow the catch to the exception you actually expect, record it through whatever this codebase already uses to report problems, or — where swallowing really is correct, as it often is on a teardown/dispose path where throwing would mask the original failure — write down WHY in a comment on the catch. The comment has to give the reason: a note that only restates the swallow ("ignored", "do nothing") is read as no explanation at all and leaves this row in place. Any of the three makes the decision reviewable; all three clear this row.
EmptyCatchBlock src/Rask.Server/RaskEndpointExtensions.cs:1364— empty catch block — the error is discarded with nothing recorded, so a failure here leaves no trace anywhere. Narrow the catch to the exception you actually expect, record it through whatever this codebase already uses to report problems, or — where swallowing really is correct, as it often is on a teardown/dispose path where throwing would mask the original failure — write down WHY in a comment on the catch. The comment has to give the reason: a note that only restates the swallow ("ignored", "do nothing") is read as no explanation at all and leaves this row in place. Any of the three makes the decision reviewable; all three clear this row.
EmptyCatchBlock src/Rask.Server/RaskEndpointExtensions.cs:1443— empty catch block — the error is discarded with nothing recorded, so a failure here leaves no trace anywhere. Narrow the catch to the exception you actually expect, record it through whatever this codebase already uses to report problems, or — where swallowing really is correct, as it often is on a teardown/dispose path where throwing would mask the original failure — write down WHY in a comment on the catch. The comment has to give the reason: a note that only restates the swallow ("ignored", "do nothing") is read as no explanation at all and leaves this row in place. Any of the three makes the decision reviewable; all three clear this row.
EmptyCatchBlock src/Rask.Server/RaskEndpointExtensions.cs:1600— empty catch block — the error is discarded with nothing recorded, so a failure here leaves no trace anywhere. Narrow the catch to the exception you actually expect, record it through whatever this codebase already uses to report problems, or — where swallowing really is correct, as it often is on a teardown/dispose path where throwing would mask the original failure — write down WHY in a comment on the catch. The comment has to give the reason: a note that only restates the swallow ("ignored", "do nothing") is read as no explanation at all and leaves this row in place. Any of the three makes the decision reviewable; all three clear this row.
EmptyCatchBlock src/Rask.Server/RaskEndpointExtensions.cs:2218— empty catch block — the error is discarded with nothing recorded, so a failure here leaves no trace anywhere. Narrow the catch to the exception you actually expect, record it through whatever this codebase already uses to report problems, or — where swallowing really is correct, as it often is on a teardown/dispose path where throwing would mask the original failure — write down WHY in a comment on the catch. The comment has to give the reason: a note that only restates the swallow ("ignored", "do nothing") is read as no explanation at all and leaves this row in place. Any of the three makes the decision reviewable; all three clear this row.
EmptyCatchBlock src/Rask.Wasm.Tasks/BakeScopedAssetsTask.cs:206— empty catch block — the error is discarded with nothing recorded, so a failure here leaves no trace anywhere. Narrow the catch to the exception you actually expect, record it through whatever this codebase already uses to report problems, or — where swallowing really is correct, as it often is on a teardown/dispose path where throwing would mask the original failure — write down WHY in a comment on the catch. The comment has to give the reason: a note that only restates the swallow ("ignored", "do nothing") is read as no explanation at all and leaves this row in place. Any of the three makes the decision reviewable; all three clear this row.
AnalyzerSeverityNone .editorconfig:272— 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:273— 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:290— 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:305— BL0016 — 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:308— BL0016 — 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:316— BL0016 — 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.
AC3 · Page structure· Document without a <title> · ×1
Document without a <title> src/Rask.Templates/sveltekit/client/src/app.html:2— A page with no <title> gives no name in the tab, history or screen-reader page list. Add a descriptive <title> in <head>.
FileScopedPragmaDisable repeated across 84 files tests/Rask.Core.Tests/Callbacks/AutoCallbackTests.cs:3— The identical FileScopedPragmaDisable (`#pragma warning disable RASK014 // test-defined Component subclasses have no generated factories`) appears in 84 files (84 occurrences) — a single repo-wide policy (e.g. a Directory.Build.props decision or an idiomatic suppression), not 84 independent debts. Decide it once centrally rather than file-by-file. (Every occurrence still counts toward the score and metrics.)
FileScopedPragmaDisable repeated across 33 files tests/Rask.Server.Tests/Authentication/SignInTestApp.cs:7— The identical FileScopedPragmaDisable (`#pragma warning disable RASK019 // test-infra apps predate framework-managed <head>`) appears in 33 files (33 occurrences) — a single repo-wide policy (e.g. a Directory.Build.props decision or an idiomatic suppression), not 33 independent debts. Decide it once centrally rather than file-by-file. (Every occurrence still counts toward the score and metrics.)
AnalyzerSeverityNone repeated across 16 files src/Rask.Templates/wasm/.editorconfig:17— The identical AnalyzerSeverityNone (`CA2007`) appears in 16 files (16 occurrences) — a single repo-wide policy (e.g. a Directory.Build.props decision or an idiomatic suppression), not 16 independent debts. Decide it once centrally rather than file-by-file. (Every occurrence still counts toward the score and metrics.)
Unlisted import 'preact' src/Rask.External/client/preact.ts:14— Imported but not declared in any reachable package.json — installs work only by hoisting accident.
Unlisted import 'react' src/Rask.External/client/react.ts:9— Imported but not declared in any reachable package.json — installs work only by hoisting accident.
Unlisted import 'react-dom' src/Rask.External/client/react.ts:10— Imported but not declared in any reachable package.json — installs work only by hoisting accident.
Unlisted import 'solid-js' src/Rask.External/client/solid.ts:12— Imported but not declared in any reachable package.json — installs work only by hoisting accident.
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:61— `SaltBytes` 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. This repository constructs key or salt material fixed at compile time at 2 sites, not one: `src/Rask.Auth.Api/PasswordHasher.cs:61` (key-derivation salt, `SaltBytes`), `src/Rask.DevTools/Endpoints/DevToolsPanelTokens.cs:24` (MAC key, `TokenBytes`). Each is a separate decision — fixing only the line this row cites leaves the others in place.
Hotspot: src/Rask.Server/RaskEndpointExtensions.cs src/Rask.Server/RaskEndpointExtensions.cs:1357— src/Rask.Server/RaskEndpointExtensions.cs changed 83 times in last 90 days, max cyclomatic complexity 40 in RaskEndpointExtensions.RunSocketLoop at line 1357. 13 of those changes were fix/bug commits, and the other 70 changed it for other reasons — this file is under both repair and feature pressure. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-06-23..2026-09-21, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-06-23 10:50:14 +02:00' --until='2026-09-21 10:50:14 +02:00' --full-history --no-merges -- src/Rask.Server/RaskEndpointExtensions.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.cs src/Rask.Core/Component.cs:2270— src/Rask.Core/Component.cs changed 55 times in last 90 days, max cyclomatic complexity 43 in Component.TryInvokeHandlerCoreAsync at line 2270. 12 of those changes were fix/bug commits, and the other 43 changed it for other reasons — this file is under both repair and feature pressure. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-06-23..2026-09-21, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-06-23 10:50:14 +02:00' --until='2026-09-21 10:50:14 +02:00' --full-history --no-merges -- src/Rask.Core/Component.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.Cli/Commands/NewCommand.cs src/Rask.Cli/Commands/NewCommand.cs:147— src/Rask.Cli/Commands/NewCommand.cs changed 50 times in last 90 days, max cyclomatic complexity 30 in NewCommand.ExecuteAsync at line 147. 6 of those changes were fix/bug commits, and the other 44 changed it for other reasons — this file is under both repair and feature pressure. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-06-23..2026-09-21, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-06-23 10:50:14 +02:00' --until='2026-09-21 10:50:14 +02:00' --full-history --no-merges -- src/Rask.Cli/Commands/NewCommand.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-morph.ts src/Rask.Core/Resources/rask-morph.ts:503— src/Rask.Core/Resources/rask-morph.ts changed 20 times in last 90 days, max cyclomatic complexity 74 in morph at line 503. 3 of those changes were fix/bug commits, and the other 17 changed it for other reasons — this file is under both repair and feature pressure. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-06-23..2026-09-21, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-06-23 10:50:14 +02:00' --until='2026-09-21 10:50:14 +02: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: src/Rask.Generators/ComponentFactoryGenerator.cs src/Rask.Generators/ComponentFactoryGenerator.cs:5119— src/Rask.Generators/ComponentFactoryGenerator.cs changed 44 times in last 90 days, max cyclomatic complexity 33 in ComponentFactoryGenerator.GetFactoryProperties at line 5119. 5 of those changes were fix/bug commits, and the other 39 changed it for other reasons — this file is under both repair and feature pressure. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-06-23..2026-09-21, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-06-23 10:50:14 +02:00' --until='2026-09-21 10:50:14 +02:00' --full-history --no-merges -- src/Rask.Generators/ComponentFactoryGenerator.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.Cli/Commands/DeployCommand.cs src/Rask.Cli/Commands/DeployCommand.cs:144— src/Rask.Cli/Commands/DeployCommand.cs changed 21 times in last 90 days, max cyclomatic complexity 44 in DeployCommand.ExecuteAsync at line 144. 5 of those changes were fix/bug commits, and the other 16 changed it for other reasons — this file is under both repair and feature pressure. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-06-23..2026-09-21, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-06-23 10:50:14 +02:00' --until='2026-09-21 10:50:14 +02:00' --full-history --no-merges -- src/Rask.Cli/Commands/DeployCommand.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-dom.ts src/Rask.Core/Resources/rask-dom.ts:158— src/Rask.Core/Resources/rask-dom.ts changed 23 times in last 90 days, max cyclomatic complexity 34 in applyDiff at line 158. 1 of those changes was a fix/bug commit, and the other 22 changed it for other reasons — this file is under both repair and feature pressure. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-06-23..2026-09-21, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-06-23 10:50:14 +02:00' --until='2026-09-21 10:50:14 +02:00' --full-history --no-merges -- src/Rask.Core/Resources/rask-dom.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.ts src/Rask.Server/Resources/rask.ts:1496— src/Rask.Server/Resources/rask.ts changed 34 times in last 90 days, max cyclomatic complexity 22 in commit at line 1496. 2 of those changes were fix/bug commits, and the other 32 changed it for other reasons — this file is under both repair and feature pressure. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-06-23..2026-09-21, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-06-23 10:50:14 +02:00' --until='2026-09-21 10:50:14 +02: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.Batteries.Generators/ModelInputGenerator.cs src/Rask.Batteries.Generators/ModelInputGenerator.cs:686— src/Rask.Batteries.Generators/ModelInputGenerator.cs changed 12 times in last 90 days, max cyclomatic complexity 62 in ModelInputGenerator.Render at line 686. 1 of those changes was a fix/bug commit, 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-06-23..2026-09-21, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-06-23 10:50:14 +02:00' --until='2026-09-21 10:50:14 +02:00' --full-history --no-merges -- src/Rask.Batteries.Generators/ModelInputGenerator.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/Components/Input.cs src/Rask.Core/Components/Input.cs:237— src/Rask.Core/Components/Input.cs changed 12 times in last 90 days, max cyclomatic complexity 53 in Input.WriteAttributes at line 237. 1 of those changes was a fix/bug commit, 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-06-23..2026-09-21, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-06-23 10:50:14 +02:00' --until='2026-09-21 10:50:14 +02:00' --full-history --no-merges -- src/Rask.Core/Components/Input.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/Resources/rask.wasm.ts src/Rask.Wasm/Resources/rask.wasm.ts:115— src/Rask.Wasm/Resources/rask.wasm.ts changed 32 times in last 90 days, max cyclomatic complexity 19 in trackHeadAsset at line 115. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-06-23..2026-09-21, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-06-23 10:50:14 +02:00' --until='2026-09-21 10:50:14 +02:00' --full-history --no-merges -- src/Rask.Wasm/Resources/rask.wasm.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/LivePayload.cs src/Rask.Core/Live/LivePayload.cs:394— src/Rask.Core/Live/LivePayload.cs changed 14 times in last 90 days, max cyclomatic complexity 38 in LivePayload.BuildPayloadUtf8Diff at line 394. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-06-23..2026-09-21, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-06-23 10:50:14 +02:00' --until='2026-09-21 10:50:14 +02:00' --full-history --no-merges -- src/Rask.Core/Live/LivePayload.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/Live/LiveSessionBase.cs src/Rask.Core/Live/LiveSessionBase.cs:439— src/Rask.Core/Live/LiveSessionBase.cs changed 21 times in last 90 days, max cyclomatic complexity 22 in LiveSessionBase.WritePayload at line 439. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-06-23..2026-09-21, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-06-23 10:50:14 +02:00' --until='2026-09-21 10:50:14 +02: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.Ui/UiSelect.cs src/Rask.Ui/UiSelect.cs:528— src/Rask.Ui/UiSelect.cs changed 18 times in last 90 days, max cyclomatic complexity 24 in UiSelect.OnKeyAsync at line 528. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-06-23..2026-09-21, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-06-23 10:50:14 +02:00' --until='2026-09-21 10:50:14 +02:00' --full-history --no-merges -- src/Rask.Ui/UiSelect.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.Site/Features/UiKit/UiKitDataInputDemo.cs src/Rask.Site/Features/UiKit/UiKitDataInputDemo.cs:47— src/Rask.Site/Features/UiKit/UiKitDataInputDemo.cs changed 18 times in last 90 days, max cyclomatic complexity 23 in UiKitDataInputDemo.Render at line 47. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-06-23..2026-09-21, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-06-23 10:50:14 +02:00' --until='2026-09-21 10:50:14 +02:00' --full-history --no-merges -- src/Rask.Site/Features/UiKit/UiKitDataInputDemo.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/External/ExternalGenerator.cs src/Rask.Generators/External/ExternalGenerator.cs:792— src/Rask.Generators/External/ExternalGenerator.cs changed 10 times in last 90 days, max cyclomatic complexity 41 in ExternalGenerator.Emit at line 792. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-06-23..2026-09-21, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-06-23 10:50:14 +02:00' --until='2026-09-21 10:50:14 +02:00' --full-history --no-merges -- src/Rask.Generators/External/ExternalGenerator.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/Resources/rask-wasm-api.ts src/Rask.Wasm/Resources/rask-wasm-api.ts:15— src/Rask.Wasm/Resources/rask-wasm-api.ts changed 21 times in last 90 days, max cyclomatic complexity 18 in applyManifest at line 15. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-06-23..2026-09-21, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-06-23 10:50:14 +02:00' --until='2026-09-21 10:50:14 +02: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/RaskBatteryWiring.cs src/Rask/RaskBatteryWiring.cs:90— src/Rask/RaskBatteryWiring.cs changed 16 times in last 90 days, max cyclomatic complexity 22 in RaskBatteryWiring.Apply at line 90. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-06-23..2026-09-21, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-06-23 10:50:14 +02:00' --until='2026-09-21 10:50:14 +02:00' --full-history --no-merges -- src/Rask/RaskBatteryWiring.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.Cli/Commands/DbCommand.cs src/Rask.Cli/Commands/DbCommand.cs:87— src/Rask.Cli/Commands/DbCommand.cs changed 11 times in last 90 days, max cyclomatic complexity 32 in DbCommand.ExecuteAsync at line 87. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-06-23..2026-09-21, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-06-23 10:50:14 +02:00' --until='2026-09-21 10:50:14 +02:00' --full-history --no-merges -- src/Rask.Cli/Commands/DbCommand.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/Element.cs src/Rask.Core/Element.cs:359— src/Rask.Core/Element.cs changed 13 times in last 90 days, max cyclomatic complexity 25 in Element.WriteAttributes at line 359. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-06-23..2026-09-21, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-06-23 10:50:14 +02:00' --until='2026-09-21 10:50:14 +02:00' --full-history --no-merges -- src/Rask.Core/Element.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/UiIcon.cs src/Rask.Ui/UiIcon.cs:94— src/Rask.Ui/UiIcon.cs changed 4 times in last 90 days, max cyclomatic complexity 80 in UiIcon.Shapes at line 94. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-06-23..2026-09-21, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-06-23 10:50:14 +02:00' --until='2026-09-21 10:50:14 +02:00' --full-history --no-merges -- src/Rask.Ui/UiIcon.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.Cli/Commands/DevCommand.cs src/Rask.Cli/Commands/DevCommand.cs:86— src/Rask.Cli/Commands/DevCommand.cs changed 20 times in last 90 days, max cyclomatic complexity 16 in DevCommand.ExecuteAsync at line 86. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-06-23..2026-09-21, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-06-23 10:50:14 +02:00' --until='2026-09-21 10:50:14 +02:00' --full-history --no-merges -- src/Rask.Cli/Commands/DevCommand.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/RoutesGenerator.cs src/Rask.Generators/RoutesGenerator.cs:649— src/Rask.Generators/RoutesGenerator.cs changed 12 times in last 90 days, max cyclomatic complexity 26 in RoutesGenerator.Emit at line 649. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-06-23..2026-09-21, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-06-23 10:50:14 +02:00' --until='2026-09-21 10:50:14 +02:00' --full-history --no-merges -- src/Rask.Generators/RoutesGenerator.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/Live/FrameDiffer.cs src/Rask.Core/Live/FrameDiffer.cs:814— src/Rask.Core/Live/FrameDiffer.cs changed 12 times in last 90 days, max cyclomatic complexity 26 in FrameDiffer.DiffKeyedSiblings at line 814. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-06-23..2026-09-21, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-06-23 10:50:14 +02:00' --until='2026-09-21 10:50:14 +02:00' --full-history --no-merges -- src/Rask.Core/Live/FrameDiffer.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/WasmPrerender.cs src/Rask.Wasm/WasmPrerender.cs:414— src/Rask.Wasm/WasmPrerender.cs changed 12 times in last 90 days, max cyclomatic complexity 22 in WasmPrerender.PatchManifest at line 414. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-06-23..2026-09-21, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-06-23 10:50:14 +02:00' --until='2026-09-21 10:50:14 +02:00' --full-history --no-merges -- src/Rask.Wasm/WasmPrerender.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.
Cross-context type Callback (Rask.Core → Rask.Ui) — Callback (context Rask.Core) is exposed in Rask.Ui's public surface via UiAccordion.OnOpen — couples the contexts.
Cross-context type Callback (Rask.Core → Rask.Ui) — Callback (context Rask.Core) is exposed in Rask.Ui's public surface via UiAccordionState..ctor — couples the contexts.
Cross-context type Callback (Rask.Core → Rask.Ui) — Callback (context Rask.Core) is exposed in Rask.Ui's public surface via UiAccordionState.OnOpen — couples the contexts.
Cross-context type Callback (Rask.Core → Rask.Ui) — Callback (context Rask.Core) is exposed in Rask.Ui's public surface via UiAccordionState.Deconstruct — couples the contexts.
Cross-context type Callback (Rask.Core → Rask.Ui) — Callback (context Rask.Core) is exposed in Rask.Ui's public surface via UiCalendar.OnMonth — couples the contexts.
Cross-context type Callback (Rask.Core → Rask.Ui) — Callback (context Rask.Core) is exposed in Rask.Ui's public surface via UiCalendar.OnChange — couples the contexts.
Cross-context type Callback (Rask.Core → Rask.Ui) — Callback (context Rask.Core) is exposed in Rask.Ui's public surface via UiCalendar.AfterBind — couples the contexts.
Cross-context type Callback (Rask.Core → Rask.Ui) — Callback (context Rask.Core) is exposed in Rask.Ui's public surface via UiCalendarMultiple.OnMonth — couples the contexts.
Cross-context type Callback (Rask.Core → Rask.Ui) — Callback (context Rask.Core) is exposed in Rask.Ui's public surface via UiCalendarMultiple.OnChange — couples the contexts.
Cross-context type Callback (Rask.Core → Rask.Ui) — Callback (context Rask.Core) is exposed in Rask.Ui's public surface via UiCalendarMultiple.AfterBind — couples the contexts.
Cross-context type Callback (Rask.Core → Rask.Ui) — Callback (context Rask.Core) is exposed in Rask.Ui's public surface via UiCalendarRange.OnMonth — couples the contexts.
Cross-context type Callback (Rask.Core → Rask.Ui) — Callback (context Rask.Core) is exposed in Rask.Ui's public surface via UiCheckbox.OnChange — couples the contexts.
Cross-context type Callback (Rask.Core → Rask.Ui) — Callback (context Rask.Core) is exposed in Rask.Ui's public surface via UiCheckbox.AfterBind — couples the contexts.
Cross-context type Callback (Rask.Core → Rask.Ui) — Callback (context Rask.Core) is exposed in Rask.Ui's public surface via UiCollapse.OnToggle — couples the contexts.
Cross-context type Callback (Rask.Core → Rask.Ui) — Callback (context Rask.Core) is exposed in Rask.Ui's public surface via UiCrumbSwitcher.OnSelect — couples the contexts.
Cross-context type Callback (Rask.Core → Rask.Ui) — Callback (context Rask.Core) is exposed in Rask.Ui's public surface via UiDataGrid.OnSelectionChange — couples the contexts.
Cross-context type Callback (Rask.Core → Rask.Ui) — Callback (context Rask.Core) is exposed in Rask.Ui's public surface via UiDataGrid.OnPageChange — couples the contexts.
Cross-context type Callback (Rask.Core → Rask.Ui) — Callback (context Rask.Core) is exposed in Rask.Ui's public surface via UiDataGrid.OnRowClick — couples the contexts.
Cross-context type Callback (Rask.Core → Rask.Ui) — Callback (context Rask.Core) is exposed in Rask.Ui's public surface via UiDataGrid.OnHiddenColumnsChange — couples the contexts.
Cross-context type Callback (Rask.Core → Rask.Ui) — Callback (context Rask.Core) is exposed in Rask.Ui's public surface via UiDataGrid.OnColumnOrderChange — couples the contexts.
Cross-context type Callback (Rask.Core → Rask.Ui) — Callback (context Rask.Core) is exposed in Rask.Ui's public surface via UiDataGrid.OnGroupedChange — couples the contexts.
Cross-context type Callback (Rask.Core → Rask.Ui) — Callback (context Rask.Core) is exposed in Rask.Ui's public surface via UiDrawer.OnToggle — couples the contexts.
Cross-context type Callback (Rask.Core → Rask.Ui) — Callback (context Rask.Core) is exposed in Rask.Ui's public surface via UiFileInput.OnFiles — couples the contexts.
Cross-context type Callback (Rask.Core → Rask.Ui) — Callback (context Rask.Core) is exposed in Rask.Ui's public surface via UiFileInput.OnChange — couples the contexts.
Cross-context type Callback (Rask.Core → Rask.Ui) — Callback (context Rask.Core) is exposed in Rask.Ui's public surface via UiFileInput.AfterBind — couples the contexts.
R4 · Test Coverage· No test reaches this file · ×40
No test reaches this file src/Rask.Server/Resources/rask.ts— 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.External/extractor/extract-props.ts— 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— 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/browser/globals.ts— 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— 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.Spa.Hosting/client/client.ts— 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-api.ts— 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— 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.External/client/angular.ts— 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— 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.Templates/analog/client/src/app/pages/analog-welcome.ts— 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.Templates/lit/client/src/my-element.ts— 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/browser/webAuthn.ts— 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/browser/originPrivateFileSystem.ts— 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/browser/fileSystem.ts— 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/browser/speechRecognition.ts— 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— 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 scripts/capture-devtools-screenshots.mjs— 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.Templates/react/client/src/App.tsx— 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/browser/battery.ts— 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.Templates/preact/client/src/app.tsx— 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/browser/webPush.ts— 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.Templates/solid/client/src/App.tsx— 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/Islands/LitBadge.ts— 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/browser/gamepad.ts— 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.
Unresolved JS interop binding src/Rask.Core/Browser/IBadge.cs:41— `__raskBadge.isSupported` is invoked from C# here, and no definition of that name was found by the search this dimension ran: 23 first-party JavaScript file(s) (.js/.mjs/.cjs, vendored trees excluded) plus 23 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 `__raskBadge.isSupported`. 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/IBattery.cs:101— `__raskBattery.isSupported` is invoked from C# here, and no definition of that name was found by the search this dimension ran: 23 first-party JavaScript file(s) (.js/.mjs/.cjs, vendored trees excluded) plus 23 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 `__raskBattery.isSupported`. 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/IBattery.cs:105— `__raskBattery.getStatus` is invoked from C# here, and no definition of that name was found by the search this dimension ran: 23 first-party JavaScript file(s) (.js/.mjs/.cjs, vendored trees excluded) plus 23 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 `__raskBattery.getStatus`. 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/ICookies.cs:84— `__raskApi.cookieGet` is invoked from C# here, and no definition of that name was found by the search this dimension ran: 23 first-party JavaScript file(s) (.js/.mjs/.cjs, vendored trees excluded) plus 23 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 `__raskApi.cookieGet`. 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/ICookies.cs:95— `__raskApi.cookieSet` is invoked from C# here, and no definition of that name was found by the search this dimension ran: 23 first-party JavaScript file(s) (.js/.mjs/.cjs, vendored trees excluded) plus 23 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 `__raskApi.cookieSet`. 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/ICookies.cs:110— `__raskApi.cookieDelete` is invoked from C# here, and no definition of that name was found by the search this dimension ran: 23 first-party JavaScript file(s) (.js/.mjs/.cjs, vendored trees excluded) plus 23 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 `__raskApi.cookieDelete`. 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/ICookies.cs:115— `__raskApi.cookieAll` is invoked from C# here, and no definition of that name was found by the search this dimension ran: 23 first-party JavaScript file(s) (.js/.mjs/.cjs, vendored trees excluded) plus 23 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 `__raskApi.cookieAll`. 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/ICrypto.cs:58— `__raskCrypto.randomUuid` is invoked from C# here, and no definition of that name was found by the search this dimension ran: 23 first-party JavaScript file(s) (.js/.mjs/.cjs, vendored trees excluded) plus 23 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 `__raskCrypto.randomUuid`. 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/ICrypto.cs:64— `__raskCrypto.randomBytes` is invoked from C# here, and no definition of that name was found by the search this dimension ran: 23 first-party JavaScript file(s) (.js/.mjs/.cjs, vendored trees excluded) plus 23 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 `__raskCrypto.randomBytes`. 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/ICrypto.cs:71— `__raskCrypto.digestHex` is invoked from C# here, and no definition of that name was found by the search this dimension ran: 23 first-party JavaScript file(s) (.js/.mjs/.cjs, vendored trees excluded) plus 23 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 `__raskCrypto.digestHex`. 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/IDeviceMotion.cs:104— `__raskDeviceMotion.isSupported` is invoked from C# here, and no definition of that name was found by the search this dimension ran: 23 first-party JavaScript file(s) (.js/.mjs/.cjs, vendored trees excluded) plus 23 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 `__raskDeviceMotion.isSupported`. 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/IDeviceMotion.cs:108— `__raskDeviceMotion.requestPermission` is invoked from C# here, and no definition of that name was found by the search this dimension ran: 23 first-party JavaScript file(s) (.js/.mjs/.cjs, vendored trees excluded) plus 23 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 `__raskDeviceMotion.requestPermission`. 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/IDeviceOrientation.cs:103— `__raskDeviceOrientation.isSupported` is invoked from C# here, and no definition of that name was found by the search this dimension ran: 23 first-party JavaScript file(s) (.js/.mjs/.cjs, vendored trees excluded) plus 23 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 `__raskDeviceOrientation.isSupported`. 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/IDeviceOrientation.cs:107— `__raskDeviceOrientation.requestPermission` is invoked from C# here, and no definition of that name was found by the search this dimension ran: 23 first-party JavaScript file(s) (.js/.mjs/.cjs, vendored trees excluded) plus 23 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 `__raskDeviceOrientation.requestPermission`. 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/IFileSystemAccess.cs:137— `__raskFs.isSupported` is invoked from C# here, and no definition of that name was found by the search this dimension ran: 23 first-party JavaScript file(s) (.js/.mjs/.cjs, vendored trees excluded) plus 23 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 `__raskFs.isSupported`. 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/IFileSystemAccess.cs:142— `__raskFs.openFile` is invoked from C# here, and no definition of that name was found by the search this dimension ran: 23 first-party JavaScript file(s) (.js/.mjs/.cjs, vendored trees excluded) plus 23 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 `__raskFs.openFile`. 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/IFileSystemAccess.cs:149— `__raskFs.openFiles` is invoked from C# here, and no definition of that name was found by the search this dimension ran: 23 first-party JavaScript file(s) (.js/.mjs/.cjs, vendored trees excluded) plus 23 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 `__raskFs.openFiles`. 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/IFileSystemAccess.cs:156— `__raskFs.saveFile` is invoked from C# here, and no definition of that name was found by the search this dimension ran: 23 first-party JavaScript file(s) (.js/.mjs/.cjs, vendored trees excluded) plus 23 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 `__raskFs.saveFile`. 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/IFileSystemAccess.cs:163— `__raskFs.openDirectory` is invoked from C# here, and no definition of that name was found by the search this dimension ran: 23 first-party JavaScript file(s) (.js/.mjs/.cjs, vendored trees excluded) plus 23 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 `__raskFs.openDirectory`. 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/IFileSystemAccess.cs:173— `__raskFs.readText` is invoked from C# here, and no definition of that name was found by the search this dimension ran: 23 first-party JavaScript file(s) (.js/.mjs/.cjs, vendored trees excluded) plus 23 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 `__raskFs.readText`. 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/IFileSystemAccess.cs:177— `__raskFs.readBytes` is invoked from C# here, and no definition of that name was found by the search this dimension ran: 23 first-party JavaScript file(s) (.js/.mjs/.cjs, vendored trees excluded) plus 23 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 `__raskFs.readBytes`. 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/IFileSystemAccess.cs:184— `__raskFs.writeText` is invoked from C# here, and no definition of that name was found by the search this dimension ran: 23 first-party JavaScript file(s) (.js/.mjs/.cjs, vendored trees excluded) plus 23 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 `__raskFs.writeText`. 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/IFileSystemAccess.cs:190— `__raskFs.writeBytes` is invoked from C# here, and no definition of that name was found by the search this dimension ran: 23 first-party JavaScript file(s) (.js/.mjs/.cjs, vendored trees excluded) plus 23 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 `__raskFs.writeBytes`. 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/IFileSystemAccess.cs:201— `__raskFs.release` is invoked from C# here, and no definition of that name was found by the search this dimension ran: 23 first-party JavaScript file(s) (.js/.mjs/.cjs, vendored trees excluded) plus 23 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 `__raskFs.release`. 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/IFileSystemAccess.cs:217— `__raskFs.getFile` is invoked from C# here, and no definition of that name was found by the search this dimension ran: 23 first-party JavaScript file(s) (.js/.mjs/.cjs, vendored trees excluded) plus 23 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 `__raskFs.getFile`. 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.
Cross-context type Fn (Rask.Core → Rask.Ui) — Fn (context Rask.Core) is exposed in Rask.Ui's public surface via UiCheckboxGroup.OptionDescription — couples the contexts.
Cross-context type Fn (Rask.Core → Rask.Ui) — Fn (context Rask.Core) is exposed in Rask.Ui's public surface via UiCheckboxGroup.OptionDisabled — couples the contexts.
Cross-context type Fn (Rask.Core → Rask.Ui) — Fn (context Rask.Core) is exposed in Rask.Ui's public surface via UiColumn.Value — couples the contexts.
Cross-context type Fn (Rask.Core → Rask.Ui) — Fn (context Rask.Core) is exposed in Rask.Ui's public surface via UiColumn.Cell — couples the contexts.
Cross-context type Fn (Rask.Core → Rask.Ui) — Fn (context Rask.Core) is exposed in Rask.Ui's public surface via UiColumn.SortKey — couples the contexts.
Cross-context type Fn (Rask.Core → Rask.Ui) — Fn (context Rask.Core) is exposed in Rask.Ui's public surface via UiColumn.GroupKey — couples the contexts.
Cross-context type Fn (Rask.Core → Rask.Ui) — Fn (context Rask.Core) is exposed in Rask.Ui's public surface via UiColumn.GroupHeader — couples the contexts.
Cross-context type Fn (Rask.Core → Rask.Ui) — Fn (context Rask.Core) is exposed in Rask.Ui's public surface via UiColumn.Footer — couples the contexts.
Cross-context type Fn (Rask.Core → Rask.Ui) — Fn (context Rask.Core) is exposed in Rask.Ui's public surface via UiColumn.FooterCell — couples the contexts.
Cross-context type Fn (Rask.Core → Rask.Ui) — Fn (context Rask.Core) is exposed in Rask.Ui's public surface via UiDataGrid.Source — couples the contexts.
Cross-context type Fn (Rask.Core → Rask.Ui) — Fn (context Rask.Core) is exposed in Rask.Ui's public surface via UiDataGrid.PageHref — couples the contexts.
Cross-context type Fn (Rask.Core → Rask.Ui) — Fn (context Rask.Core) is exposed in Rask.Ui's public surface via UiDataGrid.Detail — couples the contexts.
Cross-context type Fn (Rask.Core → Rask.Ui) — Fn (context Rask.Core) is exposed in Rask.Ui's public surface via UiDataGrid.RowClass — couples the contexts.
Cross-context type Fn (Rask.Core → Rask.Ui) — Fn (context Rask.Core) is exposed in Rask.Ui's public surface via UiDataGrid.RowTone — couples the contexts.
Cross-context type Fn (Rask.Core → Rask.Ui) — Fn (context Rask.Core) is exposed in Rask.Ui's public surface via UiDataGrid.Card — couples the contexts.
Cross-context type Fn (Rask.Core → Rask.Ui) — Fn (context Rask.Core) is exposed in Rask.Ui's public surface via UiMenuRadioGroup.OptionDisabled — couples the contexts.
Cross-context type Fn (Rask.Core → Rask.Ui) — Fn (context Rask.Core) is exposed in Rask.Ui's public surface via UiMultiSelect.OptionDisabled — couples the contexts.
Cross-context type Fn (Rask.Core → Rask.Ui) — Fn (context Rask.Core) is exposed in Rask.Ui's public surface via UiMultiSelect.OptionGroup — couples the contexts.
Cross-context type Fn (Rask.Core → Rask.Ui) — Fn (context Rask.Core) is exposed in Rask.Ui's public surface via UiMultiSelect.OptionTemplate — couples the contexts.
Cross-context type Fn (Rask.Core → Rask.Ui) — Fn (context Rask.Core) is exposed in Rask.Ui's public surface via UiMultiSelect.ChipTemplate — couples the contexts.
Cross-context type Fn (Rask.Core → Rask.Ui) — Fn (context Rask.Core) is exposed in Rask.Ui's public surface via UiMultiSelect.Filter — couples the contexts.
Cross-context type Fn (Rask.Core → Rask.Ui) — Fn (context Rask.Core) is exposed in Rask.Ui's public surface via UiPagination.Href — couples the contexts.
Cross-context type Fn (Rask.Core → Rask.Ui) — Fn (context Rask.Core) is exposed in Rask.Ui's public surface via UiRadioGroup.OptionDescription — couples the contexts.
Cross-context type Fn (Rask.Core → Rask.Ui) — Fn (context Rask.Core) is exposed in Rask.Ui's public surface via UiRadioGroup.OptionDisabled — couples the contexts.
Cross-context type Fn (Rask.Core → Rask.Ui) — Fn (context Rask.Core) is exposed in Rask.Ui's public surface via UiSelect.Filter — couples the contexts.
No assertions: 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* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, 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: Changed_DoesNotThrowWhenSubscribedAndUnsubscribed tests/Rask.Core.Tests/Authentication/AnonymousUserProviderTests.cs:15— 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* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, 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: MessagesForAnUnknownConnectionAreIgnored tests/Rask.Core.Tests/Browser/SignalingTests.cs:199— 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* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, 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: Pushes_ForAnUnknownIdAreIgnored tests/Rask.Core.Tests/Browser/WebRtcTests.cs:484— 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* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, 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: Report_NullSink_IsNoOp tests/Rask.Core.Tests/Diagnostics/RaskDiagnosticsTests.cs:35— 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* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, 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: NotifyAndValidateFieldAsync_NullContext_IsNoOp tests/Rask.Core.Tests/Forms/PublicBindingApiTests.cs:103— 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* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, 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: Changed_UnknownId_IsNoOp tests/Rask.Core.Tests/Interop/BatteryTests.cs:77— 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* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, 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: Receive_UnknownId_IsNoOp tests/Rask.Core.Tests/Interop/BroadcastChannelTests.cs:69— 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* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, 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: Result_UnknownId_IsNoOp tests/Rask.Core.Tests/Interop/SpeechRecognitionTests.cs:77— 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* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, 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: RerenderAllAsync_NoSessions_ReturnsCompletedTask tests/Rask.Core.Tests/Live/LiveSessionStoreTests.cs:135— 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* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, 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_NoHandle_DoesNotThrow 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* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, 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_NoHandle_ReturnsCompletedTask 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* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, 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:121— 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* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, 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: RequestRenderAsync_NoSocket_NoOps tests/Rask.Server.Tests/Live/LiveSessionDirectTests.cs:12— 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* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, 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: Constructor_AssignsRenderHandleSoStateHasChangedAsyncRoutesToSession 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* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, 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: Leave_IsSafeTwice tests/Rask.Signaling.Tests/SignalingHubTests.cs:128— 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* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, 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:49— 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* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, 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_sibling_of_wwwroot_that_shares_its_name_prefix_is_fine tests/Rask.Storage.Tests/BackendAndOptionsTests.cs:259— 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* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, 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: Localhost_may_use_http tests/Rask.Storage.Tests/BackendAndOptionsTests.cs:301— 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* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, 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: AFiredSyncWithNoSubscribers_IsHarmless 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* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, 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.
FileTooLong: Rask.Generators/ComponentFactoryGenerator.cs src/Rask.Generators/ComponentFactoryGenerator.cs— FileTooLong — 2627 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 2127 over it, 5.25× 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/RaskEndpointExtensions.cs src/Rask.Server/RaskEndpointExtensions.cs— FileTooLong — 1459 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 959 over it, 2.92× 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/ModelInputGenerator.cs src/Rask.Batteries.Generators/ModelInputGenerator.cs— FileTooLong — 1144 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 644 over it, 2.29× 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 — 1136 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 636 over it, 2.27× 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.Core/Component.cs src/Rask.Core/Component.cs— FileTooLong — 1110 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 610 over it, 2.22× 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: extractor/extract-props.ts src/Rask.External/extractor/extract-props.ts— FileTooLong — 928 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 428 over it, 1.86× 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.Generators/RoutesGenerator.cs src/Rask.Generators/RoutesGenerator.cs— FileTooLong — 907 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 407 over it, 1.81× 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-dom.ts src/Rask.Core/Resources/rask-dom.ts— FileTooLong — 753 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 253 over it, 1.51× 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.Ui/UiDataGrid.cs src/Rask.Ui/UiDataGrid.cs— FileTooLong — 723 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 223 over it, 1.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: External/ExternalGenerator.cs src/Rask.Generators/External/ExternalGenerator.cs— FileTooLong — 610 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 110 over it, 1.22× 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/DeployCommand.cs src/Rask.Cli/Commands/DeployCommand.cs— FileTooLong — 589 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 89 over it, 1.18× 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.Ui/UiClassNames.cs src/Rask.Ui/UiClassNames.cs— FileTooLong — 558 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 58 over it, 1.12× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: Commands/NewCommand.cs src/Rask.Cli/Commands/NewCommand.cs— FileTooLong — 537 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 37 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: Resources/rask.wasm.ts src/Rask.Wasm/Resources/rask.wasm.ts— FileTooLong — 532 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 32 over it, 1.06× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: Live/LivePayload.cs src/Rask.Core/Live/LivePayload.cs— FileTooLong — 515 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 15 over it, 1.03× 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 — 514 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 14 over it, 1.03× 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 — 503 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 3 over it, 1.01× 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.
MethodTooLong: ModelInputGenerator.Render src/Rask.Batteries.Generators/ModelInputGenerator.cs:686— MethodTooLong — Render runs 410 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 310 over it, 4.10× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: UiIcon.Shapes src/Rask.Ui/UiIcon.cs:94— MethodTooLong — Shapes runs 285 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 185 over it, 2.85× 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: UiKitDataInputDemo.Render src/Rask.Site/Features/UiKit/UiKitDataInputDemo.cs:47— MethodTooLong — Render runs 265 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 165 over it, 2.65× 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: UiKitActionsDemo.Render src/Rask.Site/Features/UiKit/UiKitActionsDemo.cs:26— MethodTooLong — Render runs 209 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 109 over it, 2.09× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: Component.TryInvokeHandlerCoreAsync src/Rask.Core/Component.cs:2270— MethodTooLong — TryInvokeHandlerCoreAsync runs 163 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 63 over it, 1.63× 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: ExternalGenerator.Emit src/Rask.Generators/External/ExternalGenerator.cs:792— MethodTooLong — Emit runs 154 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 54 over it, 1.54× 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: PwaPage.Sections src/Rask.Site/Features/PwaPage.cs:132— MethodTooLong — Sections runs 151 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 51 over it, 1.51× 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: FrameDiffer.DiffKeyedSiblings src/Rask.Core/Live/FrameDiffer.cs:814— MethodTooLong — DiffKeyedSiblings runs 139 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 39 over it, 1.39× 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: CqrsCodecGenerator.Build src/Rask.Batteries.Generators/CqrsCodecGenerator.cs:488— MethodTooLong — Build runs 135 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 35 over it, 1.35× 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: Input.WriteAttributes src/Rask.Core/Components/Input.cs:237— MethodTooLong — WriteAttributes runs 121 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 21 over it, 1.21× 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: ComponentFactoryGenerator.GetFactoryProperties src/Rask.Generators/ComponentFactoryGenerator.cs:5119— MethodTooLong — GetFactoryProperties runs 117 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 17 over it, 1.17× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: FrameDiffer.DiffSiblings src/Rask.Core/Live/FrameDiffer.cs:271— MethodTooLong — DiffSiblings runs 111 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 11 over it, 1.11× 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: UiKitDataDisplayDemo.Render src/Rask.Site/Features/UiKit/UiKitDataDisplayDemo.cs:22— MethodTooLong — Render runs 111 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 11 over it, 1.11× 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: DeployCommand.ExecuteAsync src/Rask.Cli/Commands/DeployCommand.cs:144— MethodTooLong — ExecuteAsync runs 108 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 8 over it, 1.08× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: LivePayload.BuildPayloadUtf8Diff src/Rask.Core/Live/LivePayload.cs:394— MethodTooLong — BuildPayloadUtf8Diff 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.
MethodTooLong: RaskEndpointExtensions.RunSocketLoop src/Rask.Server/RaskEndpointExtensions.cs:1357— MethodTooLong — RunSocketLoop 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.
MethodTooLong: UiKitLayoutDemo.Render src/Rask.Site/Features/UiKit/UiKitLayoutDemo.cs:11— MethodTooLong — Render 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.
Off the main sequence: Rask.Api(net10.0) — Rask.Api(net10.0): abstractness 0.00, instability 0.00, distance 1.00 — zone of pain — concrete and depended on by 1 project(s), so it's rigid to change.
Off the main sequence: Rask.Postgres(net10.0) — Rask.Postgres(net10.0): abstractness 0.00, instability 0.00, distance 1.00 — zone of pain — concrete and depended on by 1 project(s), so it's rigid to change.
Off the main sequence: Rask.SqlServer(net10.0) — Rask.SqlServer(net10.0): abstractness 0.00, instability 0.00, distance 1.00 — zone of pain — concrete and depended on by 1 project(s), so it's rigid to change.
Off the main sequence: Rask.WebPush(net10.0) — Rask.WebPush(net10.0): abstractness 0.05, instability 0.00, distance 0.95 — zone of pain — concrete and depended on by 1 project(s), so it's rigid to change.
Off the main sequence: Rask.Wire(net10.0) — Rask.Wire(net10.0): abstractness 0.05, instability 0.00, distance 0.95 — zone of pain — concrete and depended on by 6 project(s), so it's rigid to change.
Off the main sequence: Rask.SQLite(net10.0) — Rask.SQLite(net10.0): abstractness 0.07, instability 0.00, distance 0.93 — zone of pain — concrete and depended on by 3 project(s), so it's rigid to change.
Off the main sequence: Rask.Ui(net10.0) — Rask.Ui(net10.0): abstractness 0.04, instability 0.08, distance 0.88 — zone of pain — concrete and depended on by 4 project(s), so it's rigid to change.
Off the main sequence: Rask.SQLite.Snapshots(net10.0) — Rask.SQLite.Snapshots(net10.0): 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.Validation.FluentValidation(net10.0) — Rask.Validation.FluentValidation(net10.0): abstractness 0.00, instability 0.17, 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.Core(net10.0) — Rask.Core(net10.0): abstractness 0.16, instability 0.02, distance 0.82 — zone of pain — concrete and depended on by 18 project(s), so it's rigid to change.
Off the main sequence: Rask.Api.Client(net10.0) — Rask.Api.Client(net10.0): abstractness 0.00, instability 0.20, distance 0.80 — zone of pain — concrete and depended on by 1 project(s), so it's rigid to change.
Off the main sequence: Rask.Data(net10.0) — Rask.Data(net10.0): abstractness 0.18, instability 0.06, distance 0.76 — zone of pain — concrete and depended on by 8 project(s), so it's rigid to change.
Off the main sequence: Rask.Server(net10.0) — Rask.Server(net10.0): abstractness 0.05, instability 0.20, distance 0.75 — zone of pain — concrete and depended on by 2 project(s), so it's rigid to change.
Off the main sequence: Rask.Logging(net10.0) — Rask.Logging(net10.0): abstractness 0.07, instability 0.20, distance 0.73 — zone of pain — concrete and depended on by 2 project(s), so it's rigid to change.
Off the main sequence: Rask.Storage(net10.0) — Rask.Storage(net10.0): abstractness 0.08, instability 0.20, distance 0.72 — zone of pain — concrete and depended on by 2 project(s), so it's rigid to change.
Cross-context type Validator (Rask.Core → Rask.Ui) — Validator (context Rask.Core) is exposed in Rask.Ui's public surface via UiCalendar.Validate — couples the contexts.
Cross-context type Validator (Rask.Core → Rask.Ui) — Validator (context Rask.Core) is exposed in Rask.Ui's public surface via UiCalendarMultiple.Validate — couples the contexts.
Cross-context type Validator (Rask.Core → Rask.Ui) — Validator (context Rask.Core) is exposed in Rask.Ui's public surface via UiCheckbox.Validate — couples the contexts.
Cross-context type Validator (Rask.Core → Rask.Ui) — Validator (context Rask.Core) is exposed in Rask.Ui's public surface via UiFileInput.Validate — couples the contexts.
Cross-context type Validator (Rask.Core → Rask.Ui) — Validator (context Rask.Core) is exposed in Rask.Ui's public surface via UiFilter.Validate — couples the contexts.
Cross-context type Validator (Rask.Core → Rask.Ui) — Validator (context Rask.Core) is exposed in Rask.Ui's public surface via UiFormField.Validate — couples the contexts.
Cross-context type Validator (Rask.Core → Rask.Ui) — Validator (context Rask.Core) is exposed in Rask.Ui's public surface via UiMenuCheckbox.Validate — couples the contexts.
Cross-context type Validator (Rask.Core → Rask.Ui) — Validator (context Rask.Core) is exposed in Rask.Ui's public surface via UiMenuRadioGroup.Validate — couples the contexts.
Cross-context type Validator (Rask.Core → Rask.Ui) — Validator (context Rask.Core) is exposed in Rask.Ui's public surface via UiMultiSelect.Validate — couples the contexts.
Cross-context type Validator (Rask.Core → Rask.Ui) — Validator (context Rask.Core) is exposed in Rask.Ui's public surface via UiOtp.Validate — couples the contexts.
Cross-context type Validator (Rask.Core → Rask.Ui) — Validator (context Rask.Core) is exposed in Rask.Ui's public surface via UiRadio.Validate — couples the contexts.
Cross-context type Validator (Rask.Core → Rask.Ui) — Validator (context Rask.Core) is exposed in Rask.Ui's public surface via UiRange.Validate — couples the contexts.
Cross-context type Validator (Rask.Core → Rask.Ui) — Validator (context Rask.Core) is exposed in Rask.Ui's public surface via UiRating.Validate — couples the contexts.
Cross-context type Validator (Rask.Core → Rask.Ui) — Validator (context Rask.Core) is exposed in Rask.Ui's public surface via UiToggle.Validate — couples the contexts.
TooManyMethods: ComponentFactoryGenerator src/Rask.Generators/ComponentFactoryGenerator.cs— TooManyMethods — 2467 significant lines (blank, comment-only and punctuation-only lines excluded), 159 methods. The bar is 30 methods; this is 129 over it, 5.30× 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: Component src/Rask.Core/Component.cs— TooManyMethods — 1066 significant lines (blank, comment-only and punctuation-only lines excluded), 111 methods, declared across 2 files: Rask.Core/Component.cs (108), Builder/BuilderEntries.cs (3). The bar is 30 methods; this is 81 over it, 3.70× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: UiClassNames src/Rask.Ui/UiClassNames.cs— TooManyMethods — 557 significant lines (blank, comment-only and punctuation-only lines excluded), 76 methods. The bar is 30 methods; this is 46 over it, 2.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: UiDataGrid src/Rask.Ui/UiDataGrid.cs— TooManyMethods — 716 significant lines (blank, comment-only and punctuation-only lines excluded), 72 methods. The bar is 30 methods; this is 42 over it, 2.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: RaskEndpointExtensions src/Rask.Server/RaskEndpointExtensions.cs— TooManyMethods — 1396 significant lines (blank, comment-only and punctuation-only lines excluded), 67 methods. The bar is 30 methods; this is 37 over it, 2.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: DeployCommand src/Rask.Cli/Commands/DeployCommand.cs— TooManyMethods — 737 significant lines (blank, comment-only and punctuation-only lines excluded), 62 methods, declared across 2 files: Commands/DeployCommand.cs (49), Commands/DeployCommand.Ops.cs (13). 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: EditContext src/Rask.Core/Forms/EditContext.cs— TooManyMethods — 365 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: ModelInputGenerator src/Rask.Batteries.Generators/ModelInputGenerator.cs— TooManyMethods — 1051 significant lines (blank, comment-only and punctuation-only lines excluded), 35 methods. 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: LiveSession src/Rask.Server/LiveSession.cs— TooManyMethods — 294 significant lines (blank, comment-only and punctuation-only lines excluded), 35 methods. 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.
TooManyMethods: WireJson src/Rask.Wire/WireJson.cs— TooManyMethods — 120 significant lines (blank, comment-only and punctuation-only lines excluded), 34 methods. The bar is 30 methods; this is 4 over it, 1.13× the bar. 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 — 116 significant lines (blank, comment-only and punctuation-only lines excluded), 33 methods. The bar is 30 methods; this is 3 over it, 1.10× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: GeneratedModelShape src/Rask.Generators.Shared/GeneratedModelShape.cs— TooManyMethods — 242 significant lines (blank, comment-only and punctuation-only lines excluded), 32 methods. The bar is 30 methods; this is 2 over it, 1.07× 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: LiveRenderContext src/Rask.Core/Live/LiveRenderContext.cs— TooManyMethods — 183 significant lines (blank, comment-only and punctuation-only lines excluded), 32 methods. The bar is 30 methods; this is 2 over it, 1.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.
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:110— 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:118— 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:132— 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:25— 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/DomainEventInterceptor.cs:78— 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/RemoteBlobBackend.cs:352— 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:170— 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:173— 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: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.TypeScript.Tasks/ResolveTypeScriptToolTask.cs:182— 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/RaskApp.cs:233— 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.
ClassTooLong: RoutesGenerator src/Rask.Generators/RoutesGenerator.cs— ClassTooLong — 841 significant lines (blank, comment-only and punctuation-only lines excluded), 29 methods. The bar is 400 significant lines; this is 441 over it, 2.10× 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: ExternalGenerator src/Rask.Generators/External/ExternalGenerator.cs— ClassTooLong — 575 significant lines (blank, comment-only and punctuation-only lines excluded), 19 methods. The bar is 400 significant lines; this is 175 over it, 1.44× 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: NewCommand src/Rask.Cli/Commands/NewCommand.cs— ClassTooLong — 532 significant lines (blank, comment-only and punctuation-only lines excluded), 24 methods. The bar is 400 significant lines; this is 132 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.
ClassTooLong: LivePayload src/Rask.Core/Live/LivePayload.cs— ClassTooLong — 508 significant lines (blank, comment-only and punctuation-only lines excluded), 29 methods. The bar is 400 significant lines; this is 108 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.
ClassTooLong: DbCommand src/Rask.Cli/Commands/DbCommand.Backup.cs— ClassTooLong — 507 significant lines (blank, comment-only and punctuation-only lines excluded), 30 methods, declared across 2 files: Commands/DbCommand.Backup.cs (22), Commands/DbCommand.cs (8). The bar is 400 significant lines; this is 107 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.
ClassTooLong: TranslationCatalogGenerator src/Rask.Generators/Translations/TranslationCatalogGenerator.cs— ClassTooLong — 492 significant lines (blank, comment-only and punctuation-only lines excluded), 22 methods. The bar is 400 significant lines; this is 92 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.
ClassTooLong: GuideCatalog src/Rask.Site/Features/Guides/GuideCatalog.cs— ClassTooLong — 454 significant lines (blank, comment-only and punctuation-only lines excluded), 4 methods. The bar is 400 significant lines; this is 54 over it, 1.14× 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: FrameDiffer src/Rask.Core/Live/FrameDiffer.cs— ClassTooLong — 444 significant lines (blank, comment-only and punctuation-only lines excluded), 19 methods. The bar is 400 significant lines; this is 44 over it, 1.11× 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: ModelRegistryGenerator src/Rask.Batteries.Generators/ModelRegistryGenerator.cs— ClassTooLong — 430 significant lines (blank, comment-only and punctuation-only lines excluded), 19 methods. The bar is 400 significant lines; this is 30 over it, 1.08× 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 — 415 significant lines (blank, comment-only and punctuation-only lines excluded), 22 methods. The bar is 400 significant lines; this is 15 over it, 1.04× 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.
Cross-context type RouteUrl (Rask.Core → Rask.Ui) — RouteUrl (context Rask.Core) is exposed in Rask.Ui's public surface via UiBrand.Href — couples the contexts.
Cross-context type RouteUrl (Rask.Core → Rask.Ui) — RouteUrl (context Rask.Core) is exposed in Rask.Ui's public surface via UiButton.Href — couples the contexts.
Cross-context type RouteUrl (Rask.Core → Rask.Ui) — RouteUrl (context Rask.Core) is exposed in Rask.Ui's public surface via UiCard.Href — couples the contexts.
Cross-context type RouteUrl (Rask.Core → Rask.Ui) — RouteUrl (context Rask.Core) is exposed in Rask.Ui's public surface via UiLink.Href — couples the contexts.
Cross-context type RouteUrl (Rask.Core → Rask.Ui) — RouteUrl (context Rask.Core) is exposed in Rask.Ui's public surface via UiNavItem.Href — couples the contexts.
Cross-context type RouteUrl (Rask.Core → Rask.Ui) — RouteUrl (context Rask.Core) is exposed in Rask.Ui's public surface via UiNavItem.Match — couples the contexts.
Cross-context type RouteUrl (Rask.Core → Rask.Ui) — RouteUrl (context Rask.Core) is exposed in Rask.Ui's public surface via UiNavTab.Href — couples the contexts.
Cross-context type RouteUrl (Rask.Core → Rask.Ui) — RouteUrl (context Rask.Core) is exposed in Rask.Ui's public surface via UiNavTab.Match — couples the contexts.
Cross-context type RouteUrl (Rask.Core → Rask.Ui) — RouteUrl (context Rask.Core) is exposed in Rask.Ui's public surface via UiStat.Href — couples the contexts.
Duplicated block (11 lines × 2) src/Rask.Batteries.Generators/EquatableArray.cs:24— src/Rask.Batteries.Generators/EquatableArray.cs:24-34 | src/Rask.Generators/ComponentFactoryGenerator.cs:5887-5897 — before extracting anything, compare `src/Rask.Batteries.Generators/EquatableArray.cs` and `src/Rask.Generators/ComponentFactoryGenerator.cs` as WHOLE FILES: 85% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 2 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. 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.Batteries.Generators/EquatableArray.cs:24` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (11 lines × 2) src/Rask.Batteries.Generators/ModelInputGenerator.cs:899— src/Rask.Batteries.Generators/ModelInputGenerator.cs:899-909 | src/Rask.Batteries.Generators/ModelInputGenerator.cs:942-952 — 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `src/Rask.Batteries.Generators/ModelInputGenerator.cs:954` calls `AppendLine` and `src/Rask.Batteries.Generators/ModelInputGenerator.cs:911` 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 (11 lines × 2) src/Rask.Batteries.Generators/ModelInputGenerator.cs:984— src/Rask.Batteries.Generators/ModelInputGenerator.cs:984-994 | src/Rask.Batteries.Generators/ModelInputGenerator.cs:1016-1026 — 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 (11 lines × 2) src/Rask.Core/Components/Select.cs:224— src/Rask.Core/Components/Select.cs:224-234 | src/Rask.Core/Components/Textarea.cs:114-125 — 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.Core/Components/Select.cs:224` 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 (11 lines × 2) src/Rask.Core/Live/FrameDiffer.cs:882— src/Rask.Core/Live/FrameDiffer.cs:882-892 | src/Rask.Core/Live/FrameDiffer.cs:1064-1074 — 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:1064` 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) src/Rask.Generators.Shared/AggregateShape.cs:160— src/Rask.Generators.Shared/AggregateShape.cs:160-170 | src/Rask.Generators.Shared/GeneratedModelShape.cs:941-951 — 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.Generators.Shared/SymbolRegistration.cs:212— src/Rask.Generators.Shared/SymbolRegistration.cs:212-222 | src/Rask.Generators/ComponentFactoryGenerator.cs:4607-4617 — 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 (11 lines × 2) src/Rask.Generators/Analyzers/MissingKeyAnalyzer.cs:167— src/Rask.Generators/Analyzers/MissingKeyAnalyzer.cs:167-177 | src/Rask.Generators/Analyzers/RedundantStateHasChangedAnalyzer.cs:175-185 — 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/JobOptions.cs:152— src/Rask.Jobs/JobOptions.cs:152-162 | src/Rask.Mail/MailOptions.cs:198-208 — before extracting anything, compare `src/Rask.Jobs/JobOptions.cs` and `src/Rask.Mail/MailOptions.cs` as WHOLE FILES: this scan already matched 3 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. 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. 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.
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: RouteState src/Rask.Core/Routing/RouteState.cs:16— `RouteState` is a singleton (one shared instance) but mutates instance state outside any lock (_path, _query; e.g. `_path` at line 35).
Stateful singleton: Navigator src/Rask.Core/Routing/Navigator.cs:20— `Navigator` is a singleton (one shared instance) but mutates instance state outside any lock (_replace, _dirty, _inInitialRender, _inHandler; e.g. `_replace` at line 76).
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: BrowserSqliteHost src/Rask.SQLite.Browser/BrowserSqliteHost.cs:28— `BrowserSqliteHost` is a singleton (one shared instance) but mutates instance state outside any lock (IsOwner, _takeoverWatch, _ownerHold; e.g. `IsOwner` at line 61).
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:26— `WasmJSRuntime` is a singleton (one shared instance) but mutates instance state outside any lock (_host; e.g. `_host` at line 65).
Cross-context type AuthResult (Rask.Wire → Rask.Auth.Client) — AuthResult (context Rask.Wire) is exposed in Rask.Auth.Client's public surface via BrowserAuth.RegisterAsync — couples the contexts.
Cross-context type AuthResult (Rask.Wire → Rask.Auth.Client) — AuthResult (context Rask.Wire) is exposed in Rask.Auth.Client's public surface via BrowserAuth.SignInAsync — couples the contexts.
Cross-context type AuthResult (Rask.Wire → Rask.Auth.Client) — AuthResult (context Rask.Wire) is exposed in Rask.Auth.Client's public surface via BrowserAuth.SendPasswordResetAsync — couples the contexts.
Cross-context type AuthResult (Rask.Wire → Rask.Auth.Client) — AuthResult (context Rask.Wire) is exposed in Rask.Auth.Client's public surface via BrowserAuth.ResetPasswordAsync — couples the contexts.
Cross-context type AuthResult (Rask.Wire → Rask.Auth.Client) — AuthResult (context Rask.Wire) is exposed in Rask.Auth.Client's public surface via BrowserAuth.ConfirmEmailAsync — couples the contexts.
Cross-context type AuthResult (Rask.Wire → Rask.Auth.Client) — AuthResult (context Rask.Wire) is exposed in Rask.Auth.Client's public surface via BrowserAuth.AddPasskeyAsync — couples the contexts.
Cross-context type AuthResult (Rask.Wire → Rask.Auth.Client) — AuthResult (context Rask.Wire) is exposed in Rask.Auth.Client's public surface via BrowserAuth.SignInWithPasskeyAsync — couples the contexts.
Cross-context type AuthResult (Rask.Wire → Rask.Auth.Client) — AuthResult (context Rask.Wire) is exposed in Rask.Auth.Client's public surface via BrowserAuth.RemovePasskeyAsync — couples the contexts.
Cross-context type AuthResult (Rask.Wire → Rask.Core) — AuthResult (context Rask.Wire) is exposed in Rask.Core's public surface via IAuth.RegisterAsync — couples the contexts.
Cross-context type AuthResult (Rask.Wire → Rask.Core) — AuthResult (context Rask.Wire) is exposed in Rask.Core's public surface via IAuth.SignInAsync — couples the contexts.
Cross-context type AuthResult (Rask.Wire → Rask.Core) — AuthResult (context Rask.Wire) is exposed in Rask.Core's public surface via IAuth.SendPasswordResetAsync — couples the contexts.
Cross-context type AuthResult (Rask.Wire → Rask.Core) — AuthResult (context Rask.Wire) is exposed in Rask.Core's public surface via IAuth.ResetPasswordAsync — couples the contexts.
Cross-context type AuthResult (Rask.Wire → Rask.Core) — AuthResult (context Rask.Wire) is exposed in Rask.Core's public surface via IAuth.ConfirmEmailAsync — couples the contexts.
Cross-context type AuthResult (Rask.Wire → Rask.Core) — AuthResult (context Rask.Wire) is exposed in Rask.Core's public surface via IAuth.AddPasskeyAsync — couples the contexts.
Cross-context type AuthResult (Rask.Wire → Rask.Core) — AuthResult (context Rask.Wire) is exposed in Rask.Core's public surface via IAuth.SignInWithPasskeyAsync — couples the contexts.
Cross-context type AuthResult (Rask.Wire → Rask.Core) — AuthResult (context Rask.Wire) is exposed in Rask.Core's public surface via IAuth.RemovePasskeyAsync — couples the contexts.
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/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/lit/client/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>.
Duplicated block (12 lines × 2) src/Rask.Generators.Shared/WireShape.cs:472— src/Rask.Generators.Shared/WireShape.cs:472-483 | src/Rask.Generators.Shared/WireShape.cs:579-590 — 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:472` 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 (12 lines × 2) src/Rask.Core/Components/Input.cs:497— src/Rask.Core/Components/Input.cs:497-508 | src/Rask.Core/Components/Textarea.cs:222-233 — 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.Core/Components/Textarea.cs:222` 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 (12 lines × 2) src/Rask.Ui/UiCheckboxGroup.cs:138— src/Rask.Ui/UiCheckboxGroup.cs:138-149 | src/Rask.Ui/UiRadioGroup.cs:105-116 — before extracting anything, compare `src/Rask.Ui/UiCheckboxGroup.cs` and `src/Rask.Ui/UiRadioGroup.cs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 40 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.Ui/UiCheckboxGroup.cs:138` 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 (12 lines × 2) src/Rask.Ui/UiInput.cs:202— src/Rask.Ui/UiInput.cs:202-213 | src/Rask.Ui/UiInput.cs:222-233 — 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.Ui/UiInput.cs:202` 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 (12 lines × 2) src/Rask.Ui/UiOtp.cs:92— src/Rask.Ui/UiOtp.cs:92-103 | src/Rask.Ui/UiOtp.cs:109-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.Ui/UiOtp.cs:92` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (12 lines × 2) src/Rask.Core/Components/Base.cs:22— src/Rask.Core/Components/Base.cs:22-33 | src/Rask.Core/Components/Svg/SvgA.cs:23-34 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (12 lines × 2) src/Rask.Core/Components/Svg/Polygon.cs:22— src/Rask.Core/Components/Svg/Polygon.cs:22-33 | src/Rask.Core/Components/Svg/Polyline.cs:23-34 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Dead file (~69 LoC) src/Rask.Templates/angular/client/src/push.ts— no import path from any entry point (50 application, 70 tooling, 54 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
Dead file (~69 LoC) src/Rask.Templates/preact/client/src/push.ts— no import path from any entry point (50 application, 70 tooling, 54 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
Dead file (~69 LoC) src/Rask.Templates/react/client/src/push.ts— no import path from any entry point (50 application, 70 tooling, 54 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
Dead file (~69 LoC) src/Rask.Templates/solid/client/src/push.ts— no import path from any entry point (50 application, 70 tooling, 54 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
Dead file (~69 LoC) src/Rask.Templates/svelte/client/src/push.ts— no import path from any entry point (50 application, 70 tooling, 54 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
Dead file (~69 LoC) src/Rask.Templates/vue/client/src/push.ts— no import path from any entry point (50 application, 70 tooling, 54 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
Swallowed exception (empty catch) src/Rask.Server/RaskDrainService.cs:127— 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/RaskEndpointExtensions.cs:1364— 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/RaskEndpointExtensions.cs:1443— 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/RaskEndpointExtensions.cs:1600— 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/RaskEndpointExtensions.cs:2218— 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.Wasm.Tasks/BakeScopedAssetsTask.cs:206— 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.
Duplicated block (17 lines × 2) src/Rask.Jobs/JobSerializerRegistry.cs:13— src/Rask.Jobs/JobSerializerRegistry.cs:13-29 | src/Rask.Outbox/OutboxSerializerRegistry.cs:13-29 — before extracting anything, compare `src/Rask.Jobs/JobSerializerRegistry.cs` and `src/Rask.Outbox/OutboxSerializerRegistry.cs` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 91 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.Jobs/JobSerializerRegistry.cs:13` 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.Jobs/JobSerializerRegistry.cs:94— src/Rask.Jobs/JobSerializerRegistry.cs:94-110 | src/Rask.Outbox/OutboxSerializerRegistry.cs:94-110 — before extracting anything, compare `src/Rask.Jobs/JobSerializerRegistry.cs` and `src/Rask.Outbox/OutboxSerializerRegistry.cs` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 91 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 (17 lines × 2) src/Rask.Mail/MailProcessor.cs:395— src/Rask.Mail/MailProcessor.cs:395-411 | src/Rask.Outbox/OutboxProcessor.cs:401-417 — before extracting anything, compare `src/Rask.Mail/MailProcessor.cs` and `src/Rask.Outbox/OutboxProcessor.cs` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 136 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 (17 lines × 2) src/Rask.Server/Diagnostics/RaskServerDiagnostics.cs:69— src/Rask.Server/Diagnostics/RaskServerDiagnostics.cs:69-87 | src/Rask.Wasm/Diagnostics/RaskWasmDiagnostics.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.
Duplicated block (17 lines × 2) src/Rask.SQLite.Litestream/LitestreamServiceCollectionExtensions.cs:63— src/Rask.SQLite.Litestream/LitestreamServiceCollectionExtensions.cs:63-79 | src/Rask.SQLite.Snapshots/SqliteSnapshotsServiceCollectionExtensions.cs:67-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 (6 lines × 2) src/Rask.Generators/ComponentFactoryGenerator.cs:1764— src/Rask.Generators/ComponentFactoryGenerator.cs:1764-1769 | src/Rask.Generators/ComponentFactoryGenerator.cs:1772-1777 — 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 (6 lines × 2) src/Rask.Site/Features/ErrorBoundary/BoomHandlerDemo.cs:19— src/Rask.Site/Features/ErrorBoundary/BoomHandlerDemo.cs:19-24 | src/Rask.Site/Features/ErrorBoundary/BoomRenderDemo.cs:49-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.
Duplicated block (6 lines × 2) src/Rask.External.Tasks/ExternalPackageSpecifier.cs:42— src/Rask.External.Tasks/ExternalPackageSpecifier.cs:42-47 | src/Rask.Generators/External/PackageIslands/PackageIslandProps.cs:165-170 — 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 (6 lines × 2) src/Rask.SQLite.EntityFrameworkCore/RaskSqliteRangeExclusionSqlGenerator.cs:38— src/Rask.SQLite.EntityFrameworkCore/RaskSqliteRangeExclusionSqlGenerator.cs:38-43 | src/Rask.SQLite.EntityFrameworkCore/RaskSqliteStrictRangeExclusionSqlGenerator.cs:33-38 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. 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 (6 lines × 2) src/Rask.Ui/UiMultiSelect.cs:692— src/Rask.Ui/UiMultiSelect.cs:692-697 | src/Rask.Ui/UiSelect.cs:662-667 — 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.
AC6 · Visual & motion safety· Animation without a prefers-reduced-motion guard · ×4
Animation without a prefers-reduced-motion guard src/Rask.Site/wwwroot/index.html:36— This stylesheet animates but never checks prefers-reduced-motion, so motion-sensitive users can't opt out. Wrap motion in @media (prefers-reduced-motion: no-preference).
Animation without a prefers-reduced-motion guard src/Rask.Templates/wasm-hosted/Client/wwwroot/index.html:18— This stylesheet animates but never checks prefers-reduced-motion, so motion-sensitive users can't opt out. Wrap motion in @media (prefers-reduced-motion: no-preference).
Animation without a prefers-reduced-motion guard src/Rask.Templates/wasm/wwwroot/index.html:20— This stylesheet animates but never checks prefers-reduced-motion, so motion-sensitive users can't opt out. Wrap motion in @media (prefers-reduced-motion: no-preference).
Animation without a prefers-reduced-motion guard src/Rask.Wasm/Browser/index.html:79— This stylesheet animates but never checks prefers-reduced-motion, so motion-sensitive users can't opt out. Wrap motion in @media (prefers-reduced-motion: no-preference).
Repeated repair: src/Rask.Core/Live/QuiescenceScope.cs src/Rask.Core/Live/QuiescenceScope.cs:173— src/Rask.Core/Live/QuiescenceScope.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 4 (its worst body is QuiescenceScope.TrySnapshotPending at line 173), 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): 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”; “fix(core): let the running flow's quiescence scope beat a live one left on the thread”. 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-06-23..2026-09-21, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-06-23 10:50:14 +02:00' --until='2026-09-21 10:50:14 +02: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.Cqrs.Client/RaskCqrsClientServiceCollectionExtensions.cs src/Rask.Cqrs.Client/RaskCqrsClientServiceCollectionExtensions.cs:86— src/Rask.Cqrs.Client/RaskCqrsClientServiceCollectionExtensions.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 5 (its worst body is RaskCqrsClientServiceCollectionExtensions.InstallRemoteInvokers at line 86), 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(cqrs): install client invokers under the gate, so a concurrent registration waits”; “fix(cqrs): honour the client timeout, and resume a dropped upload chunk (#907)”; “fix: clear the native leftovers the prose kept, including the ones that shipped (#825)”. 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-06-23..2026-09-21, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-06-23 10:50:14 +02:00' --until='2026-09-21 10:50:14 +02:00' --full-history --no-merges -- src/Rask.Cqrs.Client/RaskCqrsClientServiceCollectionExtensions.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.Storage/RaskStorageServiceCollectionExtensions.cs src/Rask.Storage/RaskStorageServiceCollectionExtensions.cs:123— src/Rask.Storage/RaskStorageServiceCollectionExtensions.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 5 (its worst body is RaskStorageServiceCollectionExtensions.CreateBackend 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(batteries): stop the pollers filling the console with their own SQL”; “fix(storage): run without Rask.Core on every lane; bind Rask:Storage”; “fix(storage): the sweep keeps off buckets it cannot prove are its own”. 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-06-23..2026-09-21, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-06-23 10:50:14 +02:00' --until='2026-09-21 10:50:14 +02:00' --full-history --no-merges -- src/Rask.Storage/RaskStorageServiceCollectionExtensions.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.SQLite/SqliteBusyRetry.cs src/Rask.SQLite/SqliteBusyRetry.cs:28— src/Rask.SQLite/SqliteBusyRetry.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 11 (its worst body is SqliteBusyRetry.ExecAsync at line 28), 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(sqlite): re-run the transaction when SQLite rolls a contended COMMIT back (#582)”; “fix(sqlite): stop the busy retry re-issuing BEGIN inside its own transaction (#540)”; “fix(sqlite): harden and diagnose the raw immediate-transaction path against pooled-handle reuse (#431)”. 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-06-23..2026-09-21, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-06-23 10:50:14 +02:00' --until='2026-09-21 10:50:14 +02:00' --full-history --no-merges -- src/Rask.SQLite/SqliteBusyRetry.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.
BarePragmaDisable src/Rask.Core/Routing/__RaskDefaultFallback.cs:8— #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:163— #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:174— #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.
Cross-context type ShareData (Rask.Core → Rask.Wasm) — ShareData (context Rask.Core) is exposed in Rask.Wasm's public surface via IShare.ShareAsync — couples the contexts.
Cross-context type ShareData (Rask.Core → Rask.Wasm) — ShareData (context Rask.Core) is exposed in Rask.Wasm's public surface via IShare.CanShareAsync — couples the contexts.
Cross-context type ShareData (Rask.Core → Rask.Wasm) — ShareData (context Rask.Core) is exposed in Rask.Wasm's public surface via Share.ShareAsync — couples the contexts.
Cross-context type ShareData (Rask.Core → Rask.Wasm) — ShareData (context Rask.Core) is exposed in Rask.Wasm's public surface via Share.CanShareAsync — couples the contexts.
FunctionTooLong: client.httpTransport src/Rask.Spa.Hosting/client/client.ts:354— FunctionTooLong — httpTransport runs 133 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 33 over it, 1.33× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: panel-client.installPanelClient src/Rask.DevTools/Resources/panel/panel-client.ts: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.morph src/Rask.Core/Resources/rask-morph.ts:503— FunctionTooLong — morph runs 103 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 3 over it, 1.03× 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.
Duplicated block (19 lines × 2) src/Rask.Core/Components/A.cs:65— src/Rask.Core/Components/A.cs:65-83 | src/Rask.Core/Components/Area.cs:67-85 — 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 (19 lines × 2) src/Rask.Core/Components/Iframe.cs:87— src/Rask.Core/Components/Iframe.cs:87-105 | src/Rask.Core/Components/Img.cs:99-117 — 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.Core/Components/Iframe.cs:87` 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 (19 lines × 2) src/Rask.Server/RaskEndpointExtensions.cs:3041— src/Rask.Server/RaskEndpointExtensions.cs:3041-3059 | src/Rask.Server/RaskEndpointExtensions.cs:3150-3168 — 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.Server/RaskEndpointExtensions.cs:3041` 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 (19 lines × 2) src/Rask.Ui/UiDatePicker.cs:25— src/Rask.Ui/UiDatePicker.cs:25-43 | src/Rask.Ui/UiDatePickerMultiple.cs:15-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. Read the line range as the matched WINDOW rather than a finished unit: at `src/Rask.Ui/UiDatePicker.cs:25` 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 (18 lines × 2) src/Rask.Core/Components/Svg/Circle.cs:29— src/Rask.Core/Components/Svg/Circle.cs:29-46 | src/Rask.Core/Components/Svg/RadialGradient.cs:46-63 — 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.Core/Components/Svg/Circle.cs:29` 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 (18 lines × 2) src/Rask.Core/Components/Svg/FeDropShadow.cs:35— src/Rask.Core/Components/Svg/FeDropShadow.cs:35-52 | src/Rask.Core/Components/Svg/FeOffset.cs:26-43 — 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.Core/Components/Svg/FeDropShadow.cs:35` 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 (18 lines × 2) src/Rask.Postgres/RaskPostgresDbContextOptionsExtensions.cs:47— src/Rask.Postgres/RaskPostgresDbContextOptionsExtensions.cs:47-64 | src/Rask.SqlServer/RaskSqlServerDbContextOptionsExtensions.cs:47-64 — 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:47` 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 (18 lines × 2) src/Rask.Ui/UiFileInput.cs:92— src/Rask.Ui/UiFileInput.cs:92-110 | src/Rask.Ui/UiOtp.cs:57-74 — 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.Generators/ComponentFactoryGenerator.cs:2326— src/Rask.Generators/ComponentFactoryGenerator.cs:2326-2341 | src/Rask.Generators/ComponentFactoryGenerator.cs:2843-2858 — 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.cs:2326` 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 (16 lines × 2) src/Rask.Generators/Translations/MessageParser.cs:198— src/Rask.Generators/Translations/MessageParser.cs:198-213 | src/Rask.Generators/Translations/TranslationCatalogGenerator.cs:838-853 — 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 (16 lines × 2) src/Rask.Jobs/JobMetrics.cs:44— src/Rask.Jobs/JobMetrics.cs:44-59 | src/Rask.Outbox/OutboxMetrics.cs:44-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:44` 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.Generators/ComponentScopedCssGenerator.cs:233— src/Rask.Generators/ComponentScopedCssGenerator.cs:233-248 | src/Rask.Generators/ComponentScopedJsGenerator.cs:462-477 — 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 93 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 (13 lines × 2) src/Rask.Generators/ComponentScopedCssGenerator.cs:129— src/Rask.Generators/ComponentScopedCssGenerator.cs:129-141 | src/Rask.Generators/ComponentScopedJsGenerator.cs:235-247 — 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 93 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 (13 lines × 2) src/Rask.Jobs/JobMetrics.cs:24— src/Rask.Jobs/JobMetrics.cs:24-36 | src/Rask.Outbox/OutboxMetrics.cs:24-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 (13 lines × 2) src/Rask.Batteries.Generators/EquatableArray.cs:45— src/Rask.Batteries.Generators/EquatableArray.cs:45-57 | src/Rask.Generators/ComponentFactoryGenerator.cs:5908-5920 — before extracting anything, compare `src/Rask.Batteries.Generators/EquatableArray.cs` and `src/Rask.Generators/ComponentFactoryGenerator.cs` as WHOLE FILES: 85% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 2 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. 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 (13 lines × 2) src/Rask.DevTools/Panel/DevToolsErrorsTab.cs:62— src/Rask.DevTools/Panel/DevToolsErrorsTab.cs:62-75 | src/Rask.DevTools/Panel/DevToolsTabs.cs:74-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.
Duplicated block (7 lines × 2) src/Rask.Batteries.Generators/AuthUserGenerator.cs:44— src/Rask.Batteries.Generators/AuthUserGenerator.cs:44-50 | src/Rask.Batteries.Generators/ModelRegistryGenerator.cs:85-91 — 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/AuthUserGenerator.cs:44` 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 (7 lines × 2) src/Rask.Generators/ComponentFactoryGenerator.cs:1774— src/Rask.Generators/ComponentFactoryGenerator.cs:1774-1780 | src/Rask.Generators/ComponentFactoryGenerator.cs:3664-3671 — 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.cs:1774` 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 after the matched lines, `src/Rask.Generators/ComponentFactoryGenerator.cs:1781` calls `AddSource`, `From`, `ToString` and `src/Rask.Generators/ComponentFactoryGenerator.cs:3672` 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 (7 lines × 2) src/Rask.Jobs/Job.cs:110— src/Rask.Jobs/Job.cs:110-117 | src/Rask.Outbox/OutboxMessage.cs:116-122 — 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 `entity` 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/Job.cs:109` calls `ThrowIfNull` and `src/Rask.Outbox/OutboxMessage.cs:115` 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 (7 lines × 2) src/Rask.DevTools/Panel/DevToolsErrorsTab.cs:52— src/Rask.DevTools/Panel/DevToolsErrorsTab.cs:52-58 | src/Rask.DevTools/Panel/DevToolsTabs.cs:64-70 — 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.DevTools/Panel/DevToolsPerfTab.cs:221— src/Rask.DevTools/Panel/DevToolsPerfTab.cs:221-225 | src/Rask.DevTools/Panel/DevToolsWireTab.cs:123-127 — 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:221` 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.cs:1187— src/Rask.Generators/ComponentFactoryGenerator.cs:1187-1191 | src/Rask.Generators/ComponentFactoryGenerator.cs:1201-1205 — 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.cs:1187` 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.Generators.Shared/AggregateShape.cs:176— src/Rask.Generators.Shared/AggregateShape.cs:176-180 | src/Rask.Generators.Shared/GeneratedModelShape.cs:934-938 — 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.Site/Features/Virtualize/VirtualizeItemsDemo.cs:73— src/Rask.Site/Features/Virtualize/VirtualizeItemsDemo.cs:73-77 | src/Rask.Site/Features/Virtualize/VirtualizeProviderDemo.cs:80-84 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Dead file (~10 LoC) src/Rask.Templates/_islands/svelte/Features/Islands/Svelte/SvelteCounter.svelte— no import path from any entry point (50 application, 70 tooling, 54 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
Dead file (~10 LoC) src/Rask.Templates/analog/client/src/app/pages/index.page.ts— no import path from any entry point (50 application, 70 tooling, 54 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
Dead file (~10 LoC) src/Rask.Templates/analog/client/src/app/pages/login.page.ts— no import path from any entry point (50 application, 70 tooling, 54 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
Dead file (~10 LoC) src/Rask.Templates/analog/client/src/app/pages/register.page.ts— no import path from any entry point (50 application, 70 tooling, 54 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
Swallowed exception (caught, then discarded) src/Rask.Blazor/BlazorComponent.cs:432— `catch (Exception)` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter.
Swallowed exception (caught, then discarded) src/Rask.Core/Forms/ModelGraphWalker.cs:162— `catch` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter.
Swallowed exception (caught, then discarded) src/Rask.Core/Forms/ModelGraphWalker.cs:216— `catch` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter.
Swallowed exception (caught, then discarded) src/Rask.Wasm/RouteSeeder.cs:30— `catch` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter.
D10 · Test Quality· Fixed-sleep synchronisation · ×3
Fixed-sleep synchronisation: OnMountAsync_TrailingAwait_FiresExactlyOneRender 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: The_session_is_usable_again_after_a_send_times_out tests/Rask.Server.Tests/Live/SendTimeoutTests.cs:57— This test starts a background task and then orders itself against it with `Task.Delay(TimeSpan.FromSeconds(5))` — 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.
Change coupling: RaskBrowserJsonContext.cs ↔ rask-api.ts src/Rask.Core/Browser/RaskBrowserJsonContext.cs— `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: ProjectGenerator.Server.cs ↔ TemplateCatalog.cs src/Rask.Cli/Scaffolding/ProjectGenerator.Server.cs— `src/Rask.Cli/Scaffolding/ProjectGenerator.Server.cs` and `src/Rask.Cli/Templates/TemplateCatalog.cs` change together 67% of the time (8 of the 12 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets). They sit in different directories, but in this ecosystem the namespace is declared in the FILE, not by the folder — so the two may well share one namespace and reference each other with no import for this pass to see. Read the pair before acting: if one derives from or overrides the other, the dependency is explicit in the type declaration and the co-change is definitional; if one registers itself into the other through a hook or an initialiser, the missing dependency is DELIBERATE and the thing to add is a comment saying so; if they simply belong together, co-locate them; if none of these holds, the coupling is hidden and worth breaking. You can check this without leaving the row: of the 8 shared commits counted here, the most recent 3 are `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…; `c0d3f51d` feat(cli): scaffold real localization on the browser-WASM templates (… — run `git show` on any of them.
Change coupling: rask-wasm-api.ts ↔ WasmHostBuilder.cs src/Rask.Wasm/Resources/rask-wasm-api.ts— `src/Rask.Wasm/Resources/rask-wasm-api.ts` and `src/Rask.Wasm/WasmHostBuilder.cs` change together 60% of the time (9 of the 15 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/Components/Svg/Line.cs:32— src/Rask.Core/Components/Svg/Line.cs:32-54 | src/Rask.Core/Components/Svg/LinearGradient.cs:44-66 — 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.Core/Components/Svg/Line.cs:32` 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 (23 lines × 2) src/Rask.Core/Components/Svg/LinearGradient.cs:63— src/Rask.Core/Components/Svg/LinearGradient.cs:63-85 | src/Rask.Core/Components/Svg/RadialGradient.cs:75-97 — 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.Core/Components/Svg/LinearGradient.cs:63` 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 (23 lines × 2) src/Rask.Dashboard/Pages/CachePage.cs:34— src/Rask.Dashboard/Pages/CachePage.cs:34-56 | src/Rask.Dashboard/Pages/StoragePage.cs:34-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.
Duplicated block (21 lines × 2) src/Rask.Core/Components/Svg/Svg.cs:61— src/Rask.Core/Components/Svg/Svg.cs:61-81 | src/Rask.Core/Components/Svg/Symbol.cs:48-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 (21 lines × 2) src/Rask.Core/Components/Svg/SvgText.cs:18— src/Rask.Core/Components/Svg/SvgText.cs:18-41 | src/Rask.Core/Components/Svg/Tspan.cs:15-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.
Duplicated block (21 lines × 2) src/Rask.Core/ScopedCss/CssScoper.cs:219— src/Rask.Core/ScopedCss/CssScoper.cs:219-239 | src/Rask.Core/ScopedCss/CssScoper.cs:258-278 — 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/ScopedCss/CssScoper.cs:219` 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 (10 lines × 2) src/Rask.External.Tasks/ExternalIslandMetadata.cs:44— src/Rask.External.Tasks/ExternalIslandMetadata.cs:44-54 | src/Rask.External.Tasks/ExternalIslandMetadata.cs:70-79 — 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.External.Tasks/ExternalIslandMetadata.cs:44` 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 (10 lines × 2) src/Rask.Ui/UiRadioGroup.cs:47— src/Rask.Ui/UiRadioGroup.cs:47-56 | src/Rask.Ui/UiSelect.cs:255-264 — 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. 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 (10 lines × 2) src/Rask.Meta.Hosting/NodeSupervisor.cs:276— src/Rask.Meta.Hosting/NodeSupervisor.cs:276-285 | src/Rask.Spa.Hosting/SpaDevServer.cs:135-144 — 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 (9 lines × 2) src/Rask.External.Tasks/ExternalPackageScan.cs:187— src/Rask.External.Tasks/ExternalPackageScan.cs:187-196 | src/Rask.External.Tasks/ExternalPackageScan.cs:198-206 — 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.External.Tasks/ExternalPackageScan.cs:187` 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 (9 lines × 2) src/Rask.Generators/ComponentFactoryGenerator.cs:142— src/Rask.Generators/ComponentFactoryGenerator.cs:142-150 | src/Rask.Generators/RoutesGenerator.cs:201-211 — 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.Generators/ComponentFactoryGenerator.cs:142` 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 (9 lines × 2) src/Rask.Jobs/JobSerializerRegistry.cs:33— src/Rask.Jobs/JobSerializerRegistry.cs:33-41 | src/Rask.Outbox/OutboxSerializerRegistry.cs:33-41 — before extracting anything, compare `src/Rask.Jobs/JobSerializerRegistry.cs` and `src/Rask.Outbox/OutboxSerializerRegistry.cs` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 91 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 (8 lines × 2) src/Rask.Auth.Api/AccountService.cs:344— src/Rask.Auth.Api/AccountService.cs:344-351 | src/Rask.Auth.Api/AccountService.cs:378-385 — 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:344` 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 (8 lines × 2) src/Rask.Batteries.Generators/ModelInputGenerator.cs:1238— src/Rask.Batteries.Generators/ModelInputGenerator.cs:1238-1245 | src/Rask.Batteries.Generators/ModelInputGenerator.cs:1249-1256 — 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.cs:1238` 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.Ui/UiCheckboxGroup.cs:123— src/Rask.Ui/UiCheckboxGroup.cs:123-130 | src/Rask.Ui/UiRadioGroup.cs:87-94 — before extracting anything, compare `src/Rask.Ui/UiCheckboxGroup.cs` and `src/Rask.Ui/UiRadioGroup.cs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 40 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 after the matched lines, `src/Rask.Ui/UiRadioGroup.cs:95` calls `Name` and `src/Rask.Ui/UiCheckboxGroup.cs:131` 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.
Wholesale file copy (52 identical lines × 2 files) src/Rask.Templates/nextjs/client/app/auth-form.tsx:3— src/Rask.Templates/nextjs/client/app/auth-form.tsx:3 · src/Rask.Templates/react/client/src/Auth.tsx:1 — these 2 files are line-for-line copies of one another — 52 lines are identical, in the same order, in every one of them — so this is one fact about the file set, not a block to extract. An edit made to one file and not the others changes behaviour silently, which is the failure a wholesale copy guarantees. Pick one file as the single source and derive the others from it (re-export it, spread it into the local overrides each variant genuinely needs, or generate the copies at build time) — the few lines that differ between the files are exactly the part each variant should still own. Check first whether the copies are deliberately standalone deliverables (a translation file seeded from its sibling and waiting to be translated); where they are, the duplication is the design, and the honest move is to mark the seeded file as untranslated rather than to let it pass as done.
Wholesale file copy (52 identical lines × 2 files) src/Rask.Templates/preact/client/src/auth.tsx:2— src/Rask.Templates/preact/client/src/auth.tsx:2 · src/Rask.Templates/react/client/src/Auth.tsx:2 — these 2 files are line-for-line copies of one another — 52 lines are identical, in the same order, in every one of them — so this is one fact about the file set, not a block to extract. An edit made to one file and not the others changes behaviour silently, which is the failure a wholesale copy guarantees. Pick one file as the single source and derive the others from it (re-export it, spread it into the local overrides each variant genuinely needs, or generate the copies at build time) — the few lines that differ between the files are exactly the part each variant should still own. Check first whether the copies are deliberately standalone deliverables (a translation file seeded from its sibling and waiting to be translated); where they are, the duplication is the design, and the honest move is to mark the seeded file as untranslated rather than to let it pass as done.
Wholesale file copy (52 identical lines × 2 files) src/Rask.Templates/react/client/src/Auth.tsx:1— src/Rask.Templates/react/client/src/Auth.tsx:1 · src/Rask.Templates/tanstack-start/client/src/components/AuthForm.tsx:1 — these 2 files are line-for-line copies of one another — 52 lines are identical, in the same order, in every one of them — so this is one fact about the file set, not a block to extract. An edit made to one file and not the others changes behaviour silently, which is the failure a wholesale copy guarantees. Pick one file as the single source and derive the others from it (re-export it, spread it into the local overrides each variant genuinely needs, or generate the copies at build time) — the few lines that differ between the files are exactly the part each variant should still own. Check first whether the copies are deliberately standalone deliverables (a translation file seeded from its sibling and waiting to be translated); where they are, the duplication is the design, and the honest move is to mark the seeded file as untranslated rather than to let it pass as done.
Duplicated block (11 lines × 2 locations) src/Rask.Core/Resources/rask-dom.ts:463— src/Rask.Core/Resources/rask-dom.ts:463 · src/Rask.Core/Resources/rask-dom.ts:646 — 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) src/Rask.Server/Resources/rask.ts:1573— src/Rask.Server/Resources/rask.ts:1573 · src/Rask.Wasm/Resources/rask.wasm.ts:214 — 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) src/Rask.Server/Resources/rask.ts:1894— src/Rask.Server/Resources/rask.ts:1894 · src/Rask.Wasm/Resources/rask.wasm.ts:908 — 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.
Dead file (~24 LoC) src/Rask.Templates/_islands/preact/Features/Islands/Preact/PreactCounter.tsx— no import path from any entry point (50 application, 70 tooling, 54 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
Dead file (~24 LoC) src/Rask.Templates/_islands/react/Features/Islands/React/ReactCounter.tsx— no import path from any entry point (50 application, 70 tooling, 54 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
Dead file (~24 LoC) src/Rask.Templates/_islands/solid/Features/Islands/Solid/SolidCounter.tsx— no import path from any entry point (50 application, 70 tooling, 54 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
Dead file (~5 LoC) src/Rask.Templates/solidstart/client/src/routes/login.tsx— no import path from any entry point (50 application, 70 tooling, 54 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
Dead file (~5 LoC) src/Rask.Templates/solidstart/client/src/routes/register.tsx— no import path from any entry point (50 application, 70 tooling, 54 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
Dead file (~5 LoC) src/Rask.Templates/svelte/client/src/lib/Counter.svelte— no import path from any entry point (50 application, 70 tooling, 54 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
Cross-context type FieldIdentifier (Rask.Core → Rask.Site) — FieldIdentifier (context Rask.Core) is exposed in Rask.Site's public surface via UniqueUsernameValidator.ValidateFieldAsync — couples the contexts.
Cross-context type FieldIdentifier (Rask.Core → Rask.Site) — FieldIdentifier (context Rask.Core) is exposed in Rask.Site's public surface via SlowTitleValidator.ValidateFieldAsync — couples the contexts.
Cross-context type WebAppManifest (Rask.Core → Rask.Wasm) — WebAppManifest (context Rask.Core) is exposed in Rask.Wasm's public surface via WasmHostBuilder.UsePwa — couples the contexts.
Cross-context type WebAppManifest (Rask.Core → Rask.Wasm) — WebAppManifest (context Rask.Core) is exposed in Rask.Wasm's public surface via WasmHostBuilder.UseManifest — couples the contexts.
Duplicated block (30 lines × 2) src/Rask.Jobs/JobOptions.cs:7— src/Rask.Jobs/JobOptions.cs:7-36 | src/Rask.Mail/MailOptions.cs:61-90 — before extracting anything, compare `src/Rask.Jobs/JobOptions.cs` and `src/Rask.Mail/MailOptions.cs` as WHOLE FILES: this scan already matched 3 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. 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 (30 lines × 2) src/Rask.Jobs/JobSerializerRegistry.cs:60— src/Rask.Jobs/JobSerializerRegistry.cs:60-89 | src/Rask.Outbox/OutboxSerializerRegistry.cs:60-89 — before extracting anything, compare `src/Rask.Jobs/JobSerializerRegistry.cs` and `src/Rask.Outbox/OutboxSerializerRegistry.cs` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 91 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 (24 lines × 2) src/Rask.Core/Components/Input.cs:304— src/Rask.Core/Components/Input.cs:304-327 | src/Rask.Core/Components/Textarea.cs:146-169 — 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.Core/Components/Input.cs:304` 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 (24 lines × 2) src/Rask.Core/Live/LiveOptions.cs:180— src/Rask.Core/Live/LiveOptions.cs:180-203 | src/Rask.Spa.Hosting/SpaPath.cs:19-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. 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 (20 lines × 2) src/Rask.Server/RaskEndpointExtensions.cs:167— src/Rask.Server/RaskEndpointExtensions.cs:167-210 | src/Rask.Spa.Hosting/RaskSpaServiceCollectionExtensions.cs:66-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.
Duplicated block (20 lines × 2) src/Rask.Ui/UiCheckbox.cs:21— src/Rask.Ui/UiCheckbox.cs:21-40 | src/Rask.Ui/UiToggle.cs:20-41 — 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/UiCheckbox.cs:21` 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 (15 lines × 2) src/Rask.External.Tasks/ExternalBuildPlan.cs:747— src/Rask.External.Tasks/ExternalBuildPlan.cs:747-761 | src/Rask.Spa.Tasks/GeneratedTypeScript.cs:117-131 — 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 (15 lines × 2) src/Rask.Server/RaskEndpointExtensions.cs:2447— src/Rask.Server/RaskEndpointExtensions.cs:2447-2461 | src/Rask.Wasm/WasmLiveSession.cs:365-379 — 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.Server/RaskEndpointExtensions.cs:2447` 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 (14 lines × 2) src/Rask.Generators/External/ExternalGenerator.cs:334— src/Rask.Generators/External/ExternalGenerator.cs:334-347 | src/Rask.Generators/External/ExternalGenerator.cs:379-392 — 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/External/ExternalGenerator.cs:334` 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 (14 lines × 2) src/Rask.Ui/UiMultiSelect.cs:475— src/Rask.Ui/UiMultiSelect.cs:475-488 | src/Rask.Ui/UiSelect.cs:415-428 — 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 (8 lines × 5) src/Rask.Site/Features/UiKit/UiKitDataDisplayDemo.cs:172— src/Rask.Site/Features/UiKit/UiKitDataDisplayDemo.cs:172-191 | src/Rask.Site/Features/UiKit/UiKitDataGridDemo.cs:145-152 | src/Rask.Site/Features/UiKit/UiKitDataInputDemo.cs:390-411 | src/Rask.Site/Features/UiKit/UiKitFeedbackDemo.cs:135-157 | src/Rask.Site/Features/UiKit/UiKitLayoutDemo.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 all 5 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/UiKit/UiKitDataDisplayDemo.cs:170` calls `Month` and `src/Rask.Site/Features/UiKit/UiKitDataGridDemo.cs:143` 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 × 5) src/Rask.Generators/Analyzers/ChainAssignedAfterwardsAnalyzer.cs:170— src/Rask.Generators/Analyzers/ChainAssignedAfterwardsAnalyzer.cs:170-179 | src/Rask.Generators/Analyzers/DuplicateChainCallAnalyzer.cs:110-117 | src/Rask.Generators/Analyzers/GridColumnTokenAnalyzer.cs:250-259 | src/Rask.Generators/Analyzers/KeyOpensChainAnalyzer.cs:140-147 | src/Rask.Generators/Analyzers/OptionTemplateNativeAnalyzer.cs:136-145 — 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 5 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. Note first that the copies are not typed on the same thing: the declarations holding them bind `operation` to `IOperation?` in one and `IInvocationOperation` 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.Generators/Analyzers/DuplicateChainCallAnalyzer.cs:105` calls `Unwrap` and `src/Rask.Generators/Analyzers/ChainAssignedAfterwardsAnalyzer.cs:166` 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 (11 lines × 3) src/Rask.Core/Components/DefaultNotFoundPage.cs:19— src/Rask.Core/Components/DefaultNotFoundPage.cs:19-29 | src/Rask.Core/Components/NavLink.cs:52-63 | src/Rask.Core/Routing/Outlet.cs:24-35 — 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.
Duplicated block (11 lines × 3) src/Rask.Generators/ComponentScopedCssGenerator.cs:104— src/Rask.Generators/ComponentScopedCssGenerator.cs:104-114 | src/Rask.Generators/ComponentScopedJsGenerator.cs:180-190 | src/Rask.Generators/RoutesGenerator.cs:382-392 — 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 93 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.
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: Component (LCOM4 4) src/Rask.Core/Component.cs:21— Component's methods fall into 4 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 4 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
IC1 · Incompleteness & stubs· Empty method body · ×2
Empty method body — does nothing with its inputs src/Rask.Wasm/JSInterop.cs:260— `ApplyRender` takes parameters but its body is empty — it accepts inputs and does nothing. Either implement it or remove it.
Empty method body — does nothing with its inputs src/Rask.Wasm/JSInterop.cs:267— `PushHistory` takes parameters but its body is empty — it accepts inputs and does nothing. Either implement it or remove it.
Duplicated block (20 lines × 2 locations) src/Rask.Server/Resources/rask.ts:1674— src/Rask.Server/Resources/rask.ts:1674 · src/Rask.Wasm/Resources/rask.wasm.ts:763 — 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 (20 lines × 2 locations) src/Rask.Templates/analog/client/src/app/pages/auth-form.ts:68— src/Rask.Templates/analog/client/src/app/pages/auth-form.ts:68 · src/Rask.Templates/angular/client/src/app/auth.ts:71 — 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 (17 lines × 2 locations) src/Rask.Server/Resources/rask.ts:1362— src/Rask.Server/Resources/rask.ts:1362 · src/Rask.Wasm/Resources/rask.wasm.ts:157 — 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 (17 lines × 2 locations) src/Rask.Templates/_islands/preact/Features/Islands/Preact/PreactCounter.tsx:5— src/Rask.Templates/_islands/preact/Features/Islands/Preact/PreactCounter.tsx:5 · src/Rask.Templates/_islands/react/Features/Islands/React/ReactCounter.tsx:5 — 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:213— src/Rask.Core/Resources/browser/auth.ts:213 · src/Rask.Core/Resources/browser/auth.ts:283 — 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 (16 lines × 2 locations) src/Rask.Server/Resources/rask.ts:1775— src/Rask.Server/Resources/rask.ts:1775 · src/Rask.Wasm/Resources/rask.wasm.ts:852 — 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.External/client/preact.ts:45— src/Rask.External/client/preact.ts:45 · src/Rask.External/client/react.ts:42 — 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 (13 lines × 2 locations) src/Rask.Wasm/Resources/rask-wasm-api.ts:246— src/Rask.Wasm/Resources/rask-wasm-api.ts:246 · src/Rask.Wasm/Resources/rask-wasm-api.ts:378 — 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 (12 lines × 2 locations) src/Rask.Templates/solidstart/client/src/routes/about.tsx:4— src/Rask.Templates/solidstart/client/src/routes/about.tsx:4 · src/Rask.Templates/solidstart/client/src/routes/index.tsx:4 — the 2 copies are spread across 2 files, and the CITED SPAN is a DECLARATION HEADER — the name, parameter list with its constraints and defaults, and base-type clause of a declaration — rather than statements inside a body. A header cannot be lifted into a helper: there is no expression position for a call to stand in, and the copies are frequently required to match, because one declaration passes its parameters straight through to the other. So the move is not extraction. Give the repeated pieces names — factor a long constraint or base-type expression into one named type both declarations refer to — and where the headers must stay identical, derive one from the other (a shared base declaration, or a single alias that spells the parameter set once) so that changing it once changes both. Where the language offers neither, treat the two as a pair that must be edited together: they drift apart the first time only one of them is changed, which is why this is reported.
Duplicated block (12 lines × 2 locations) src/Rask.Templates/svelte/client/src/lib/Auth.svelte:17— src/Rask.Templates/svelte/client/src/lib/Auth.svelte:17 · src/Rask.Templates/sveltekit/client/src/lib/AuthForm.svelte:17 — 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.
Dead file (~29 LoC) src/Rask.Templates/_islands/angular/Features/Islands/Angular/AngularCounter.ts— no import path from any entry point (50 application, 70 tooling, 54 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
Dead file (~29 LoC) src/Rask.Templates/nuxt/client/app/components/AuthForm.vue— no import path from any entry point (50 application, 70 tooling, 54 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
Dead file (~25 LoC) src/Rask.Templates/solidstart/client/src/routes/[...404].tsx— no import path from any entry point (50 application, 70 tooling, 54 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
Dead file (~25 LoC) src/Rask.Templates/solidstart/client/src/routes/index.tsx— no import path from any entry point (50 application, 70 tooling, 54 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
Dead file (~12 LoC) src/Rask.External/client/RaskHost.svelte— no import path from any entry point (50 application, 70 tooling, 54 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (src/Rask.External/client/svelte.svelte.ts) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it
Dead file (~12 LoC) src/Rask.External/client/RaskTree.svelte— no import path from any entry point (50 application, 70 tooling, 54 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (src/Rask.External/client/RaskHost.svelte) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it
rask-morph.morph (cyclomatic 77) src/Rask.Core/Resources/rask-morph.ts:503— rask-morph.morph has cyclomatic complexity 77 (threshold 15). Of this number, 74 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.
ModelInputGenerator.Render (cyclomatic 62) src/Rask.Batteries.Generators/ModelInputGenerator.cs:686— ModelInputGenerator.Render has cyclomatic complexity 62 (threshold 15). Of this number, 61 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.
HtmlSerializer.Serialize (cyclomatic 58) src/Rask.Core/HtmlSerializer.cs:194— HtmlSerializer.Serialize has cyclomatic complexity 58 (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.
Input.WriteAttributes (cyclomatic 53) src/Rask.Core/Components/Input.cs:237— Input.WriteAttributes has cyclomatic complexity 53 (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.
panel-client.installPanelClient (cyclomatic 52) src/Rask.DevTools/Resources/panel/panel-client.ts: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 literals inside it that branch (lines 201, 147, 66, …). 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.
DeployCommand.ExecuteAsync (cyclomatic 44) src/Rask.Cli/Commands/DeployCommand.cs:144— DeployCommand.ExecuteAsync has cyclomatic complexity 44 (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.
Component.TryInvokeHandlerCoreAsync (cyclomatic 43) src/Rask.Core/Component.cs:2270— Component.TryInvokeHandlerCoreAsync has cyclomatic complexity 43 (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.
ExternalGenerator.Emit (cyclomatic 41) src/Rask.Generators/External/ExternalGenerator.cs:792— ExternalGenerator.Emit has cyclomatic complexity 41 (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.Signature (cyclomatic 41) src/Rask.Storage/Upload/ContentSniffer.cs:61— ContentSniffer.Signature has cyclomatic complexity 41 (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.
RaskEndpointExtensions.RunSocketLoop (cyclomatic 40) src/Rask.Server/RaskEndpointExtensions.cs:1357— RaskEndpointExtensions.RunSocketLoop has cyclomatic complexity 40 (threshold 15). Of this number, 39 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.
LivePayload.BuildPayloadUtf8Diff (cyclomatic 38) src/Rask.Core/Live/LivePayload.cs:394— LivePayload.BuildPayloadUtf8Diff 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.
CssScoper.AppendScopedSelector (cyclomatic 37) src/Rask.Core/ScopedCss/CssScoper.cs:198— CssScoper.AppendScopedSelector has cyclomatic complexity 37 (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.
rask-dom.applyDiff (cyclomatic 36) src/Rask.Core/Resources/rask-dom.ts:158— rask-dom.applyDiff 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.
TypeWalker.serialize (cyclomatic 36) src/Rask.External/extractor/extract-props.ts:499— TypeWalker.serialize has cyclomatic complexity 36 (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.
ComponentFactoryGenerator.GetFactoryProperties (cyclomatic 33) src/Rask.Generators/ComponentFactoryGenerator.cs:5119— ComponentFactoryGenerator.GetFactoryProperties has cyclomatic complexity 33 (threshold 15). Of this number, 31 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.
client.httpTransport (cyclomatic 33) src/Rask.Spa.Hosting/client/client.ts:354— client.httpTransport has cyclomatic complexity 33 (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.
DbCommand.ExecuteAsync (cyclomatic 32) src/Rask.Cli/Commands/DbCommand.cs:87— DbCommand.ExecuteAsync has cyclomatic complexity 32 (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.
affected_projects.main (cyclomatic 31) scripts/lib/affected_projects.py:103— affected_projects.main has cyclomatic complexity 31 (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-http-transport.openHttpConnection (cyclomatic 31) src/Rask.Server/Resources/rask-http-transport.ts:307— rask-http-transport.openHttpConnection has cyclomatic complexity 31 (threshold 15). Most of this is not in the body itself: 12 of the 31 points are its own statements and the rest belongs to 3 function literals inside it that branch (lines 356, 396, 353). 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.
NewCommand.ExecuteAsync (cyclomatic 30) src/Rask.Cli/Commands/NewCommand.cs:147— NewCommand.ExecuteAsync has cyclomatic complexity 30 (threshold 15). Of this number, 25 points are the body's own statements and 5 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.
NewCommand.GenerateDirectAsync (cyclomatic 30) src/Rask.Cli/Commands/NewCommand.cs:681— NewCommand.GenerateDirectAsync 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.
extract-props.extractIsland (cyclomatic 29) src/Rask.External/extractor/extract-props.ts:231— extract-props.extractIsland has cyclomatic complexity 29 (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.EmitConsumerEntries (cyclomatic 28) src/Rask.Generators/ComponentFactoryGenerator.cs:3417— ComponentFactoryGenerator.EmitConsumerEntries 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.
EditContext.ValidateFieldAsync (cyclomatic 27) src/Rask.Core/Forms/EditContext.cs:716— EditContext.ValidateFieldAsync has cyclomatic complexity 27 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
HostFacts.Parse (cyclomatic 26) src/Rask.Cli/HostProbe.cs:54— HostFacts.Parse has cyclomatic complexity 26 (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.
FrameDiffer.DiffKeyedSiblings (cyclomatic 26) src/Rask.Core/Live/FrameDiffer.cs:814— FrameDiffer.DiffKeyedSiblings 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.
ExternalPackageScan.Blank (cyclomatic 26) src/Rask.External.Tasks/ExternalPackageScan.cs:237— ExternalPackageScan.Blank 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.
RoutesGenerator.Emit (cyclomatic 26) src/Rask.Generators/RoutesGenerator.cs:649— RoutesGenerator.Emit has cyclomatic 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, 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.
BakeScopedAssetsTask.BakeFromAssemblies (cyclomatic 26) src/Rask.Wasm.Tasks/BakeScopedAssetsTask.cs:176— BakeScopedAssetsTask.BakeFromAssemblies has cyclomatic complexity 26 (threshold 15). Of this number, 22 points are the body's own statements and 4 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.
extract-props.extractAngular (cyclomatic 26) src/Rask.External/extractor/extract-props.ts:1188— extract-props.extractAngular 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.
ValueObjectCollector.Of (cyclomatic 25) src/Rask.Generators.Shared/GeneratedModelShape.cs:798— ValueObjectCollector.Of has cyclomatic complexity 25 (threshold 15). Of this number, 17 points are the body's own statements and 8 belong to 4 function literals 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.
Element.WriteAttributes (cyclomatic 25) src/Rask.Core/Element.cs:359— Element.WriteAttributes has cyclomatic complexity 25 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
FrameDiffer.DiffSiblings (cyclomatic 25) src/Rask.Core/Live/FrameDiffer.cs:271— FrameDiffer.DiffSiblings 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 literals inside it that branch (lines 127, 95, 115, …). 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.
extract-props.extractLit (cyclomatic 25) src/Rask.External/extractor/extract-props.ts:941— extract-props.extractLit 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.
rask.applyFullReply (cyclomatic 25) src/Rask.Server/Resources/rask.ts:1489— rask.applyFullReply has cyclomatic complexity 25 (threshold 15). Most of this is not in the body itself: 4 of the 25 points are its own statements and the rest belongs to one function literal inside it that branches (line 1496). 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.
CssScoper.RewriteBlock (cyclomatic 24) src/Rask.Core/ScopedCss/CssScoper.cs:44— CssScoper.RewriteBlock has cyclomatic complexity 24 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
PropsSnapshotReader.ReadType (cyclomatic 24) src/Rask.Generators/External/PackageIslands/PropsSnapshotReader.cs:155— PropsSnapshotReader.ReadType has cyclomatic complexity 24 (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.
UiSelect.OnKeyAsync (cyclomatic 24) src/Rask.Ui/UiSelect.cs:528— UiSelect.OnKeyAsync has cyclomatic complexity 24 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
ExternalPackageScan.ReadLiteral (cyclomatic 23) src/Rask.External.Tasks/ExternalPackageScan.cs:313— ExternalPackageScan.ReadLiteral 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.
WriteExternalBuildInputsTask.Execute (cyclomatic 23) src/Rask.External.Tasks/WriteExternalBuildInputsTask.cs:71— WriteExternalBuildInputsTask.Execute 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.
UiKitDataInputDemo.Render (cyclomatic 23) src/Rask.Site/Features/UiKit/UiKitDataInputDemo.cs:47— UiKitDataInputDemo.Render has cyclomatic complexity 23 (threshold 15). Of this number, 16 points are the body's own statements and 7 belong to 5 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.
ContentSniffer.IsoMedia (cyclomatic 23) src/Rask.Storage/Upload/ContentSniffer.cs:190— 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.
HtmlTree.TryReadStartTag (cyclomatic 23) src/Rask.Testing/HtmlTree.cs:165— HtmlTree.TryReadStartTag has cyclomatic complexity 23 (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.
rask.wasm.trackHeadAsset (cyclomatic 23) src/Rask.Wasm/Resources/rask.wasm.ts:115— rask.wasm.trackHeadAsset has cyclomatic complexity 23 (threshold 15). Of this number, 19 points are the body's own statements and 4 belong to one function literal inside it that branches. 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.
HostSetup.EnsureReadyAsync (cyclomatic 22) src/Rask.Cli/HostSetup.cs:54— HostSetup.EnsureReadyAsync has cyclomatic complexity 22 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
LiveSessionBase.WritePayload (cyclomatic 22) src/Rask.Core/Live/LiveSessionBase.cs:439— LiveSessionBase.WritePayload 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.
MessageParser.Parse (cyclomatic 22) src/Rask.Generators/Translations/MessageParser.cs:59— MessageParser.Parse 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.
TranslationCatalogGenerator.EmitFamily (cyclomatic 22) src/Rask.Generators/Translations/TranslationCatalogGenerator.cs:133— TranslationCatalogGenerator.EmitFamily 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.
RaskEndpointExtensions.UseRask (cyclomatic 22) src/Rask.Server/RaskEndpointExtensions.cs:455— RaskEndpointExtensions.UseRask has cyclomatic complexity 22 (threshold 15). Most of this is not in the body itself: 9 of the 22 points are its own statements and the rest belongs to one function literal inside it that branches (line 521). 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.
WasmPrerender.PatchManifest (cyclomatic 22) src/Rask.Wasm/WasmPrerender.cs:414— WasmPrerender.PatchManifest 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.
RaskBatteryWiring.Apply (cyclomatic 22) src/Rask/RaskBatteryWiring.cs:90— RaskBatteryWiring.Apply has cyclomatic complexity 22 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
ArgumentSchema.Parse (cyclomatic 21) src/Rask.Cli/ArgumentSchema.cs:164— ArgumentSchema.Parse 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.
Component.RenderForLive (cyclomatic 21) src/Rask.Core/Component.cs:1253— Component.RenderForLive 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.
Textarea.WriteAttributes (cyclomatic 21) src/Rask.Core/Components/Textarea.cs:113— Textarea.WriteAttributes 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.
BuilderEntry.TryReadChain (cyclomatic 21) src/Rask.Generators/Analyzers/BuilderEntry.cs:173— BuilderEntry.TryReadChain has cyclomatic complexity 21 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
AzureAccount.Parse (cyclomatic 21) src/Rask.Storage/Backends/AzureAccount.cs:41— AzureAccount.Parse 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.
UiTree.OnKeyAsync (cyclomatic 21) src/Rask.Ui/UiTree.cs:365— UiTree.OnKeyAsync has cyclomatic complexity 21 (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.
angular.renderChildren (cyclomatic 21) src/Rask.External/client/angular.ts:223— angular.renderChildren 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.
WireShape.Classify (cyclomatic 20) src/Rask.Generators.Shared/WireShape.cs:172— WireShape.Classify has cyclomatic complexity 20 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
CssMinifier.Minify (cyclomatic 20) src/Rask.Core/ScopedAssets/CssMinifier.cs:28— CssMinifier.Minify has cyclomatic complexity 20 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
BlazorParameters.Read (cyclomatic 20) src/Rask.Generators/Blazor/BlazorParameters.cs:122— BlazorParameters.Read has cyclomatic complexity 20 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
RaskSpaEndpointExtensions.UseRaskSpa (cyclomatic 20) src/Rask.Spa.Hosting/RaskSpaEndpointExtensions.cs:100— RaskSpaEndpointExtensions.UseRaskSpa has cyclomatic complexity 20 (threshold 15). Of this number, 16 points are the body's own statements and 4 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.
UiSelect.Custom (cyclomatic 20) src/Rask.Ui/UiSelect.cs:253— UiSelect.Custom has cyclomatic 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: 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-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.
lit.renderChildren (cyclomatic 20) src/Rask.External/client/lit.ts:128— lit.renderChildren has cyclomatic complexity 20 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
CqrsDispatchGenerator.GetCandidate (cyclomatic 19) src/Rask.Batteries.Generators/CqrsDispatchGenerator.cs:65— CqrsDispatchGenerator.GetCandidate has cyclomatic complexity 19 (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.
BulkInsertPlan.Build (cyclomatic 19) src/Rask.Data/BulkInsertPlan.cs:94— BulkInsertPlan.Build 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.
ReadModelRegistry.MapColumns (cyclomatic 19) src/Rask.Data/ReadModelRegistry.cs:202— ReadModelRegistry.MapColumns 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.
PackageIslandProps.Facts (cyclomatic 19) src/Rask.Generators/External/PackageIslands/PackageIslandProps.cs:224— PackageIslandProps.Facts has cyclomatic complexity 19 (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.
Resolver.Map (cyclomatic 19) src/Rask.Generators/External/PackageIslands/PackageIslandProps.cs:634— Resolver.Map has cyclomatic complexity 19 (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.
RoutesGenerator.GetPageProperties (cyclomatic 19) src/Rask.Generators/RoutesGenerator.cs:394— RoutesGenerator.GetPageProperties 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.
RoutesGenerator.EmitFactoryBody (cyclomatic 19) src/Rask.Generators/RoutesGenerator.cs:1071— RoutesGenerator.EmitFactoryBody has cyclomatic complexity 19 (threshold 15). Of this number, 18 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.
UiMenuSurface.OnKeyAsync (cyclomatic 19) src/Rask.Ui/UiMenuSurface.cs:166— UiMenuSurface.OnKeyAsync has cyclomatic complexity 19 (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.
PrerenderShell.StripComments (cyclomatic 19) src/Rask.Wasm/PrerenderShell.cs:390— PrerenderShell.StripComments 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.
rask.onFrame (cyclomatic 19) src/Rask.Server/Resources/rask.ts:400— rask.onFrame has cyclomatic complexity 19 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
CqrsCodecGenerator.Build (cyclomatic 18) src/Rask.Batteries.Generators/CqrsCodecGenerator.cs:488— CqrsCodecGenerator.Build 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.
SvgElement.WriteAttributes (cyclomatic 18) src/Rask.Core/Components/Svg/SvgElement.cs:110— SvgElement.WriteAttributes 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.
ExpressionAccessor.TryEvaluate (cyclomatic 18) src/Rask.Core/Forms/ExpressionAccessor.cs:161— 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:46— 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.
RaskCqrsEndpointExtensions.HandleAsync (cyclomatic 18) src/Rask.Cqrs.Server/RaskCqrsEndpointExtensions.cs:217— RaskCqrsEndpointExtensions.HandleAsync 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.
DevToolsPageErrorReceiver.Record (cyclomatic 18) src/Rask.DevTools/Panel/DevToolsPageErrorReceiver.cs:62— DevToolsPageErrorReceiver.Record has cyclomatic complexity 18 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
DevToolsTreeSnapshotter.BadgeOf (cyclomatic 18) src/Rask.DevTools/Probe/DevToolsComponentNode.cs:202— DevToolsTreeSnapshotter.BadgeOf 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.
ComponentFactoryGenerator.GetCandidate (cyclomatic 18) src/Rask.Generators/ComponentFactoryGenerator.cs:4493— ComponentFactoryGenerator.GetCandidate 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.
ExternalGenerator.Execute (cyclomatic 18) src/Rask.Generators/External/ExternalGenerator.cs:182— ExternalGenerator.Execute 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.
PropsSnapshotReader.Read (cyclomatic 18) src/Rask.Generators/External/PackageIslands/PropsSnapshotReader.cs:28— PropsSnapshotReader.Read 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.
RoutesGenerator.EmitRouteFactory (cyclomatic 18) src/Rask.Generators/RoutesGenerator.cs:923— RoutesGenerator.EmitRouteFactory 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.
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.
RaskApp.Build (cyclomatic 18) src/Rask/RaskApp.cs:137— RaskApp.Build 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, 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.
speechRecognition.start (cyclomatic 18) src/Rask.Core/Resources/browser/speechRecognition.ts:82— speechRecognition.start has cyclomatic complexity 18 (threshold 15). Of this number, 10 points are the body's own statements and 8 belong to 4 function literals inside it that branch. To reduce it, separate the branches: extract each independent case into its own named function so the top-level body reads as a short sequence of named decisions.
bridge.createBridge (cyclomatic 18) src/Rask.DevTools/Resources/host/bridge.ts:46— bridge.createBridge 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.
TypeWalker.serializeUnion (cyclomatic 18) src/Rask.External/extractor/extract-props.ts:601— TypeWalker.serializeUnion has cyclomatic complexity 18 (threshold 15). Of this number, 15 points are the body's own statements and 3 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.
WireShape.ClassifyObject (cyclomatic 17) src/Rask.Generators.Shared/WireShape.cs:364— WireShape.ClassifyObject 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.
GeneratedModelShape.EntitiesFor (cyclomatic 17) src/Rask.Generators.Shared/GeneratedModelShape.cs:361— 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.
TemplateMarkers.Apply (cyclomatic 17) src/Rask.Cli/Scaffolding/TemplateMarkers.cs:56— TemplateMarkers.Apply 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.
Select.WriteAttributes (cyclomatic 17) src/Rask.Core/Components/Select.cs:223— Select.WriteAttributes 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.
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.
MissingKeyAnalyzer.Analyze (cyclomatic 17) src/Rask.Generators/Analyzers/MissingKeyAnalyzer.cs:77— MissingKeyAnalyzer.Analyze 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.
JsonScanner.TryReadString (cyclomatic 17) src/Rask.Generators/Json/JsonScanner.cs:101— JsonScanner.TryReadString 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.
RoutesGenerator.GetCandidate (cyclomatic 17) src/Rask.Generators/RoutesGenerator.cs:231— RoutesGenerator.GetCandidate 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.
RoutesGenerator.GetOrphanCandidate (cyclomatic 17) src/Rask.Generators/RoutesGenerator.cs:499— RoutesGenerator.GetOrphanCandidate 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-morph.raskNotePendingFormState (cyclomatic 17) src/Rask.Core/Resources/rask-morph.ts:344— rask-morph.raskNotePendingFormState 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 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.
PasskeyVerifier.IsExpectedClientData (cyclomatic 16) src/Rask.Auth.Api/PasskeyVerifier.cs:186— 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.
DevCommand.ExecuteAsync (cyclomatic 16) src/Rask.Cli/Commands/DevCommand.cs:86— DevCommand.ExecuteAsync 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.
Button.WriteAttributes (cyclomatic 16) src/Rask.Core/Components/Button.cs:94— Button.WriteAttributes 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.
Link.WriteAttributes (cyclomatic 16) src/Rask.Core/Components/Link.cs:91— Link.WriteAttributes 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.
RequiredBuilderPropertyAnalyzer.Analyze (cyclomatic 16) src/Rask.Generators/Analyzers/RequiredBuilderPropertyAnalyzer.cs:83— RequiredBuilderPropertyAnalyzer.Analyze 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.
ExternalGenerator.Describe (cyclomatic 16) src/Rask.Generators/External/ExternalGenerator.cs:524— ExternalGenerator.Describe 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.trackHeadAsset (cyclomatic 16) src/Rask.Server/Resources/rask.ts:1346— rask.trackHeadAsset has cyclomatic complexity 16 (threshold 15). Of this number, 12 points are the body's own statements and 4 belong to one function literal inside it that branches. To reduce it, split the body: 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.
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.morph (cognitive 136) src/Rask.Core/Resources/rask-morph.ts:503— rask-morph.morph has cognitive complexity 136 (threshold 15). Drivers by points: if/else 42 (84 pts), boolean chains 22, loops 11 (16 pts), ternaries 5 (14 pts) (nesting depth added 56). Of this number, 131 points are the body's own statements and 5 belong to 2 function literals 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.
HtmlSerializer.Serialize (cognitive 95) src/Rask.Core/HtmlSerializer.cs:194— HtmlSerializer.Serialize 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.
RaskEndpointExtensions.RunSocketLoop (cognitive 79) src/Rask.Server/RaskEndpointExtensions.cs:1357— RaskEndpointExtensions.RunSocketLoop has cognitive complexity 79 (threshold 15). Of this number, 78 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.
ModelInputGenerator.Render (cognitive 75) src/Rask.Batteries.Generators/ModelInputGenerator.cs:686— ModelInputGenerator.Render has cognitive complexity 75 (threshold 15). Of this number, 74 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.
ComponentFactoryGenerator.GetFactoryProperties (cognitive 66) src/Rask.Generators/ComponentFactoryGenerator.cs:5119— ComponentFactoryGenerator.GetFactoryProperties has cognitive complexity 66 (threshold 15). Of this number, 64 points are the body's own statements and 2 belong to one function literal inside it that branches. To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
rask-dom.applyDiff (cognitive 66) src/Rask.Core/Resources/rask-dom.ts:158— rask-dom.applyDiff has cognitive complexity 66 (threshold 15). Drivers by points: if/else 13 (39 pts), loops 5 (13 pts), ternaries 2 (7 pts), boolean chains 5, match/switch 1 (2 pts) (nesting depth added 40). 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.
ExternalGenerator.Emit (cognitive 65) src/Rask.Generators/External/ExternalGenerator.cs:792— ExternalGenerator.Emit has cognitive complexity 65 (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.
Input.WriteAttributes (cognitive 62) src/Rask.Core/Components/Input.cs:237— Input.WriteAttributes has cognitive complexity 62 (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.
FrameDiffer.DiffKeyedSiblings (cognitive 59) src/Rask.Core/Live/FrameDiffer.cs:814— FrameDiffer.DiffKeyedSiblings has cognitive complexity 59 (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 58) src/Rask.Generators/Translations/MessageParser.cs:59— MessageParser.Parse has cognitive complexity 58 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
EditContext.ValidateFieldAsync (cognitive 57) src/Rask.Core/Forms/EditContext.cs:716— EditContext.ValidateFieldAsync has cognitive complexity 57 (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.BuildPayloadUtf8Diff (cognitive 55) src/Rask.Core/Live/LivePayload.cs:394— LivePayload.BuildPayloadUtf8Diff has cognitive complexity 55 (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.
affected_projects.main (cognitive 55) scripts/lib/affected_projects.py:103— affected_projects.main has cognitive complexity 55 (threshold 15). Drivers by points: if/else 12 (27 pts), loops 11 (16 pts), error handling 3 (8 pts), boolean chains 3, ternaries 1 (nesting depth added 25). 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.EmitFamily (cognitive 54) src/Rask.Generators/Translations/TranslationCatalogGenerator.cs:133— TranslationCatalogGenerator.EmitFamily has cognitive complexity 54 (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.
ExternalPackageScan.Blank (cognitive 52) src/Rask.External.Tasks/ExternalPackageScan.cs:237— ExternalPackageScan.Blank 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.
panel-client.installPanelClient (cognitive 49) src/Rask.DevTools/Resources/panel/panel-client.ts: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 literals inside it that branch (lines 147, 201, 66, …). 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.
DeployCommand.ExecuteAsync (cognitive 47) src/Rask.Cli/Commands/DeployCommand.cs:144— DeployCommand.ExecuteAsync has cognitive complexity 47 (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.
ContentSniffer.Signature (cognitive 47) src/Rask.Storage/Upload/ContentSniffer.cs:61— ContentSniffer.Signature has cognitive complexity 47 (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.
extract-props.extractIsland (cognitive 47) src/Rask.External/extractor/extract-props.ts:231— extract-props.extractIsland has cognitive complexity 47 (threshold 15). Drivers by points: ternaries 8 (20 pts), if/else 11 (18 pts), boolean chains 5, error handling 1 (2 pts), loops 2 (nesting depth added 20). 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.
ArgumentSchema.Parse (cognitive 45) src/Rask.Cli/ArgumentSchema.cs:164— ArgumentSchema.Parse has cognitive complexity 45 (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-http-transport.openHttpConnection (cognitive 44) src/Rask.Server/Resources/rask-http-transport.ts:307— rask-http-transport.openHttpConnection has cognitive complexity 44 (threshold 15). Drivers by points: if/else 15 (24 pts), boolean chains 6, ternaries 3 (6 pts), error handling 3 (4 pts), loops 2 (4 pts) (nesting depth added 15). Most of this is not in the body itself: 11 of the 44 points are its own statements and the rest belongs to 3 function literals inside it that branch (lines 356, 396, 353). 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.
DbCommand.ExecuteAsync (cognitive 43) src/Rask.Cli/Commands/DbCommand.cs:87— DbCommand.ExecuteAsync has cognitive complexity 43 (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.EmitConsumerEntries (cognitive 43) src/Rask.Generators/ComponentFactoryGenerator.cs:3417— ComponentFactoryGenerator.EmitConsumerEntries has cognitive complexity 43 (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.Emit (cognitive 43) src/Rask.Generators/RoutesGenerator.cs:649— RoutesGenerator.Emit has cognitive complexity 43 (threshold 15). Of this number, 42 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.
extract-props.extractAngular (cognitive 42) src/Rask.External/extractor/extract-props.ts:1188— extract-props.extractAngular has cognitive complexity 42 (threshold 15). Drivers by points: ternaries 11 (24 pts), if/else 6 (9 pts), boolean chains 5, error handling 1 (2 pts), loops 2 (nesting depth added 17). 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.
NewCommand.GenerateDirectAsync (cognitive 41) src/Rask.Cli/Commands/NewCommand.cs:681— NewCommand.GenerateDirectAsync has cognitive complexity 41 (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.
client.httpTransport (cognitive 41) src/Rask.Spa.Hosting/client/client.ts:354— client.httpTransport has cognitive complexity 41 (threshold 15). Drivers by points: if/else 16 (22 pts), ternaries 5 (8 pts), boolean chains 6, loops 3 (4 pts), error handling 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.
BakeScopedAssetsTask.BakeFromAssemblies (cognitive 40) src/Rask.Wasm.Tasks/BakeScopedAssetsTask.cs:176— BakeScopedAssetsTask.BakeFromAssemblies has cognitive complexity 40 (threshold 15). Of this number, 33 points are the body's own statements and 7 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.
CssScoper.RewriteBlock (cognitive 38) src/Rask.Core/ScopedCss/CssScoper.cs:44— CssScoper.RewriteBlock 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.
RoutesGenerator.EmitFactoryBody (cognitive 37) src/Rask.Generators/RoutesGenerator.cs:1071— RoutesGenerator.EmitFactoryBody has cognitive complexity 37 (threshold 15). Of this number, 36 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.
WasmPrerender.PatchManifest (cognitive 37) src/Rask.Wasm/WasmPrerender.cs:414— WasmPrerender.PatchManifest has cognitive complexity 37 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
TypeWalker.serialize (cognitive 37) src/Rask.External/extractor/extract-props.ts:499— TypeWalker.serialize has cognitive complexity 37 (threshold 15). Drivers by points: if/else 22 (25 pts), boolean chains 8, ternaries 2 (4 pts) (nesting depth added 5). 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.
CssMinifier.Minify (cognitive 36) src/Rask.Core/ScopedAssets/CssMinifier.cs:28— CssMinifier.Minify has cognitive complexity 36 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
angular.renderChildren (cognitive 34) src/Rask.External/client/angular.ts:223— angular.renderChildren has cognitive complexity 34 (threshold 15). Drivers by points: if/else 12 (22 pts), boolean chains 4, loops 4, ternaries 2 (4 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.
ExternalPackageScan.FindOverride (cognitive 33) src/Rask.External.Tasks/ExternalPackageScan.cs:173— ExternalPackageScan.FindOverride has cognitive complexity 33 (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.
BlazorParameters.Read (cognitive 33) src/Rask.Generators/Blazor/BlazorParameters.cs:122— BlazorParameters.Read has cognitive complexity 33 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
extract-props.extractLit (cognitive 33) src/Rask.External/extractor/extract-props.ts:941— extract-props.extractLit has cognitive complexity 33 (threshold 15). Drivers by points: if/else 10 (14 pts), ternaries 4 (9 pts), boolean chains 6, error handling 1 (2 pts), loops 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.
Component.RenderForLive (cognitive 32) src/Rask.Core/Component.cs:1253— Component.RenderForLive has cognitive complexity 32 (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.
FormData.FromJson (cognitive 32) src/Rask.Core/Live/FormData.cs:46— 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.
CssScoper.AppendScopedSelector (cognitive 32) src/Rask.Core/ScopedCss/CssScoper.cs:198— CssScoper.AppendScopedSelector has cognitive complexity 32 (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.
WriteExternalBuildInputsTask.Execute (cognitive 32) src/Rask.External.Tasks/WriteExternalBuildInputsTask.cs:71— WriteExternalBuildInputsTask.Execute 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.
lit.renderChildren (cognitive 32) src/Rask.External/client/lit.ts:128— lit.renderChildren has cognitive complexity 32 (threshold 15). Drivers by points: if/else 11 (22 pts), boolean chains 4, loops 4, ternaries 1 (2 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.
ExternalGenerator.Execute (cognitive 31) src/Rask.Generators/External/ExternalGenerator.cs:182— ExternalGenerator.Execute 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.
RoutesGenerator.GetPageProperties (cognitive 31) src/Rask.Generators/RoutesGenerator.cs:394— RoutesGenerator.GetPageProperties 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.
HtmlTree.TryReadStartTag (cognitive 31) src/Rask.Testing/HtmlTree.cs:165— HtmlTree.TryReadStartTag has cognitive complexity 31 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
TemplateMarkers.Apply (cognitive 30) src/Rask.Cli/Scaffolding/TemplateMarkers.cs:56— TemplateMarkers.Apply has cognitive complexity 30 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
RoutesGenerator.EmitRouteFactory (cognitive 30) src/Rask.Generators/RoutesGenerator.cs:923— RoutesGenerator.EmitRouteFactory has cognitive complexity 30 (threshold 15). Of this number, 29 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.
PrerenderShell.StripComments (cognitive 30) src/Rask.Wasm/PrerenderShell.cs:390— PrerenderShell.StripComments has cognitive complexity 30 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
rask.applyFullReply (cognitive 30) src/Rask.Server/Resources/rask.ts:1489— rask.applyFullReply has cognitive complexity 30 (threshold 15). Drivers by points: if/else 15 (21 pts), boolean chains 7, ternaries 1 (2 pts) (nesting depth added 7). Most of this is not in the body itself: 4 of the 30 points are its own statements and the rest belongs to one function literal inside it that branches (line 1496). 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.
SymbolRegistration.DescribeUnnameableWithRemedy (cognitive 28) src/Rask.Generators.Shared/SymbolRegistration.cs:84— 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.
NewCommand.ExecuteAsync (cognitive 28) src/Rask.Cli/Commands/NewCommand.cs:147— NewCommand.ExecuteAsync has cognitive complexity 28 (threshold 15). Of this number, 26 points are the body's own statements and 2 belong 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.
Element.AppendPrefixedAttrs (cognitive 28) src/Rask.Core/Element.cs:510— Element.AppendPrefixedAttrs 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.
FrameDiffer.DiffSiblings (cognitive 28) src/Rask.Core/Live/FrameDiffer.cs:271— FrameDiffer.DiffSiblings 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.
PropsSnapshotReader.ReadType (cognitive 28) src/Rask.Generators/External/PackageIslands/PropsSnapshotReader.cs:155— PropsSnapshotReader.ReadType 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.
HtmlTree.Parse (cognitive 28) src/Rask.Testing/HtmlTree.cs:41— HtmlTree.Parse 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.
RaskBatteryWiring.Apply (cognitive 28) src/Rask/RaskBatteryWiring.cs:90— RaskBatteryWiring.Apply has cognitive complexity 28 (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.
Element.WriteAttributes (cognitive 27) src/Rask.Core/Element.cs:359— Element.WriteAttributes has cognitive complexity 27 (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.
LiveSessionBase.WritePayload (cognitive 27) src/Rask.Core/Live/LiveSessionBase.cs:439— LiveSessionBase.WritePayload has cognitive complexity 27 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
UiSelect.OnKeyAsync (cognitive 27) src/Rask.Ui/UiSelect.cs:528— UiSelect.OnKeyAsync has cognitive complexity 27 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
HostSetup.EnsureReadyAsync (cognitive 26) src/Rask.Cli/HostSetup.cs:54— HostSetup.EnsureReadyAsync has cognitive complexity 26 (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.
ModelBuilderExtensions.Apply (cognitive 26) src/Rask.Data/ModelBuilderExtensions.cs:76— ModelBuilderExtensions.Apply 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.
ReadModelRegistry.MapColumns (cognitive 26) src/Rask.Data/ReadModelRegistry.cs:202— ReadModelRegistry.MapColumns 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.
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.
CqrsCodecGenerator.Build (cognitive 25) src/Rask.Batteries.Generators/CqrsCodecGenerator.cs:488— CqrsCodecGenerator.Build 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.
ModelInputGenerator.Emit (cognitive 25) src/Rask.Batteries.Generators/ModelInputGenerator.cs:595— ModelInputGenerator.Emit has cognitive complexity 25 (threshold 15). Of this number, 24 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.
ExternalPackageScan.ReadLiteral (cognitive 25) src/Rask.External.Tasks/ExternalPackageScan.cs:313— ExternalPackageScan.ReadLiteral 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.
RoutesGenerator.TryParseTemplate (cognitive 25) src/Rask.Generators/RoutesGenerator.cs:1460— RoutesGenerator.TryParseTemplate 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.
JobProcessor.DrainAsync (cognitive 25) src/Rask.Jobs/JobProcessor.cs:165— JobProcessor.DrainAsync 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.
OutboxProcessor.DrainAsync (cognitive 25) src/Rask.Outbox/OutboxProcessor.cs:187— OutboxProcessor.DrainAsync 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.
AzureAccount.Parse (cognitive 25) src/Rask.Storage/Backends/AzureAccount.cs:41— AzureAccount.Parse 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.
WireShape.Classify (cognitive 24) src/Rask.Generators.Shared/WireShape.cs:172— WireShape.Classify has cognitive complexity 24 (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.
ModelRegistryGenerator.EmitDbSets (cognitive 24) src/Rask.Batteries.Generators/ModelRegistryGenerator.cs:373— ModelRegistryGenerator.EmitDbSets 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.
FramePathWalker.TryResolve (cognitive 24) src/Rask.Core/Live/FramePathWalker.cs:35— FramePathWalker.TryResolve 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.
ExternalSourceScan.IslandRuntimes (cognitive 24) src/Rask.External.Tasks/ExternalSourceScan.cs:108— ExternalSourceScan.IslandRuntimes 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.
PackageIslandEmitter.Types (cognitive 23) src/Rask.Generators/External/PackageIslands/PackageIslandEmitter.cs:219— PackageIslandEmitter.Types 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.
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.
bridge.createBridge (cognitive 23) src/Rask.DevTools/Resources/host/bridge.ts:46— bridge.createBridge has cognitive complexity 23 (threshold 15). Drivers by points: if/else 10 (17 pts), ternaries 1 (3 pts), boolean chains 2, match/switch 1 (nesting depth added 9). Of this number, 22 points are the body's own statements and 1 belongs to one function literal inside it that branches. To reduce it, 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.
BulkInsertPlan.Build (cognitive 22) src/Rask.Data/BulkInsertPlan.cs:94— BulkInsertPlan.Build 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.
ComponentFactoryGenerator.EmitBoundEntry (cognitive 22) src/Rask.Generators/ComponentFactoryGenerator.cs:3219— ComponentFactoryGenerator.EmitBoundEntry 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.
PropsSnapshotReader.Read (cognitive 22) src/Rask.Generators/External/PackageIslands/PropsSnapshotReader.cs:28— PropsSnapshotReader.Read 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.
rask.onFrame (cognitive 22) src/Rask.Server/Resources/rask.ts:400— rask.onFrame has cognitive complexity 22 (threshold 15). Drivers by points: if/else 14 (17 pts), boolean chains 4, error handling 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, 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.
rask.wasm.trackHeadAsset (cognitive 22) src/Rask.Wasm/Resources/rask.wasm.ts:115— rask.wasm.trackHeadAsset has cognitive complexity 22 (threshold 15). Drivers by points: boolean chains 10, if/else 9, ternaries 2 (3 pts) (nesting depth added 1). Of this number, 17 points are the body's own statements and 5 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.
revive (cognitive 22) src/Rask.External/wwwroot/rask-external.js:183— revive has cognitive complexity 22 (threshold 15). Drivers by points: ternaries 3 (9 pts), if/else 5 (6 pts), boolean chains 4, loops 2 (3 pts) (nesting depth added 8). Of this number, 18 points are the body's own statements and 4 belong to 4 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.
CqrsCodecGenerator.DiscoverMessages (cognitive 21) src/Rask.Batteries.Generators/CqrsCodecGenerator.cs:208— 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.
ExternalBuildPlan.Refuse (cognitive 21) src/Rask.External.Tasks/ExternalBuildPlan.cs:548— ExternalBuildPlan.Refuse 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.
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.cs:261— 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.
ComponentScopedJsGenerator.Emit (cognitive 21) src/Rask.Generators/ComponentScopedJsGenerator.cs:229— ComponentScopedJsGenerator.Emit 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.
RoutesGenerator.GetCandidate (cognitive 21) src/Rask.Generators/RoutesGenerator.cs:231— RoutesGenerator.GetCandidate 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.
Reader.ReadObject (cognitive 21) src/Rask.Generators/Translations/JsonCatalogReader.cs:55— Reader.ReadObject 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.
TranslationCatalogGenerator.IsCultureTag (cognitive 21) src/Rask.Generators/Translations/TranslationCatalogGenerator.cs:792— TranslationCatalogGenerator.IsCultureTag 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.
UiSelect.Custom (cognitive 21) src/Rask.Ui/UiSelect.cs:253— UiSelect.Custom has cognitive complexity 21 (threshold 15). Of this number, 19 points are the body's own statements and 2 belong 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.
rask-morph.raskNotePendingFormState (cognitive 21) src/Rask.Core/Resources/rask-morph.ts:344— rask-morph.raskNotePendingFormState has cognitive complexity 21 (threshold 15). Drivers by points: if/else 5 (6 pts), ternaries 4 (6 pts), loops 2 (5 pts), boolean chains 4 (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.
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 literals inside it that branch (lines 127, 95, 115, …). 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.
rask.saveRestoreFields (cognitive 21) src/Rask.Server/Resources/rask.ts:778— 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.
WireShape.ClassifyObject (cognitive 20) src/Rask.Generators.Shared/WireShape.cs:364— WireShape.ClassifyObject 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.
ValueObjectCollector.Of (cognitive 20) src/Rask.Generators.Shared/GeneratedModelShape.cs:798— ValueObjectCollector.Of has cognitive complexity 20 (threshold 15). Of this number, 15 points are the body's own statements and 5 belong to 4 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.
CqrsCodecGenerator.DiscoverHandlers (cognitive 20) src/Rask.Batteries.Generators/CqrsCodecGenerator.cs:252— 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.
Textarea.WriteAttributes (cognitive 20) src/Rask.Core/Components/Textarea.cs:113— Textarea.WriteAttributes has cognitive complexity 20 (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.
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.
ComponentFactoryGenerator.EmitPropsDescribers (cognitive 20) src/Rask.Generators/ComponentFactoryGenerator.cs:3699— ComponentFactoryGenerator.EmitPropsDescribers has cognitive complexity 20 (threshold 15). Of this number, 19 points are the body's own statements and 1 belongs to one function literal inside it that branches. To reduce it, split the body 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.GetForwarderInfos (cognitive 20) src/Rask.Generators/ComponentFactoryGenerator.cs:4646— ComponentFactoryGenerator.GetForwarderInfos 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.
RoutesGenerator.GetOrphanCandidate (cognitive 20) src/Rask.Generators/RoutesGenerator.cs:499— RoutesGenerator.GetOrphanCandidate 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.
RaskEndpointExtensions.UseRask (cognitive 20) src/Rask.Server/RaskEndpointExtensions.cs:455— RaskEndpointExtensions.UseRask has cognitive complexity 20 (threshold 15). Most of this is not in the body itself: 7 of the 20 points are its own statements and the rest belongs to one function literal inside it that branches (line 521). 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.
RaskSpaEndpointExtensions.UseRaskSpa (cognitive 20) src/Rask.Spa.Hosting/RaskSpaEndpointExtensions.cs:100— RaskSpaEndpointExtensions.UseRaskSpa has cognitive complexity 20 (threshold 15). Of this number, 16 points are the body's own statements and 4 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.
RaskApp.Build (cognitive 20) src/Rask/RaskApp.cs:137— RaskApp.Build 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: 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.
TypeWalker.serializeUnion (cognitive 20) src/Rask.External/extractor/extract-props.ts:601— TypeWalker.serializeUnion has cognitive complexity 20 (threshold 15). Drivers by points: if/else 9 (11 pts), boolean chains 5, ternaries 2 (3 pts), loops 1 (nesting depth added 3). Of this number, 18 points are the body's own statements and 2 belong to 2 function literals inside it that branch. To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
ApiClientGenerator.Emit (cognitive 19) src/Rask.Api.Generators/ApiClientGenerator.cs:135— 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.
ApiClientGenerator.Compose (cognitive 19) src/Rask.Api.Generators/ApiClientGenerator.cs:330— ApiClientGenerator.Compose has cognitive complexity 19 (threshold 15). Of this number, 18 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.
DevCommand.ExecuteAsync (cognitive 19) src/Rask.Cli/Commands/DevCommand.cs:86— DevCommand.ExecuteAsync has cognitive complexity 19 (threshold 15). To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
Select.WriteAttributes (cognitive 19) src/Rask.Core/Components/Select.cs:223— Select.WriteAttributes has cognitive complexity 19 (threshold 15). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
RoutePattern.TryMatch (cognitive 19) src/Rask.Core/Routing/RoutePattern.cs:113— RoutePattern.TryMatch 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.
ModelBuilderExtensions.MapValueCollections (cognitive 19) src/Rask.Data/ModelBuilderExtensions.cs:309— ModelBuilderExtensions.MapValueCollections 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.
ComponentFactoryGenerator.EmitCandidateResets (cognitive 19) src/Rask.Generators/ComponentFactoryGenerator.cs:792— ComponentFactoryGenerator.EmitCandidateResets 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.
JsonScanner.TryReadString (cognitive 19) src/Rask.Generators/Json/JsonScanner.cs:101— JsonScanner.TryReadString 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.
RaskEndpointExtensions.AttachAsync (cognitive 19) src/Rask.Server/RaskEndpointExtensions.cs:1755— RaskEndpointExtensions.AttachAsync 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.
UiChartScale.Nice (cognitive 19) src/Rask.Ui/UiChartScale.cs:60— UiChartScale.Nice has cognitive complexity 19 (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.
UiDataGrid.Rows (cognitive 19) src/Rask.Ui/UiDataGrid.cs:1175— UiDataGrid.Rows 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.
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 literals inside it that branch. To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
extract-props.literalOf (cognitive 19) src/Rask.External/extractor/extract-props.ts:1358— extract-props.literalOf has cognitive complexity 19 (threshold 15). Drivers by points: if/else 5 (8 pts), ternaries 3 (7 pts), boolean chains 2, loops 1 (2 pts) (nesting depth added 8). 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, 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.
GeneratedModelShape.EntitiesFor (cognitive 18) src/Rask.Generators.Shared/GeneratedModelShape.cs:361— 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.
CqrsCodecGenerator.Authorization (cognitive 18) src/Rask.Batteries.Generators/CqrsCodecGenerator.cs:289— CqrsCodecGenerator.Authorization 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.
ReadModelShape.Describe (cognitive 18) src/Rask.Generators.Shared/ReadModelShape.cs:190— ReadModelShape.Describe 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.
NewCommand.RetiredFlagError (cognitive 18) src/Rask.Cli/Commands/NewCommand.cs:375— NewCommand.RetiredFlagError 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.
ScopedAssetRegistry.EnsureBundle (cognitive 18) src/Rask.Core/ScopedAssets/ScopedAssetRegistry.cs:576— ScopedAssetRegistry.EnsureBundle has cognitive complexity 18 (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.
RaskCqrsEndpointExtensions.HandleAsync (cognitive 18) src/Rask.Cqrs.Server/RaskCqrsEndpointExtensions.cs:217— RaskCqrsEndpointExtensions.HandleAsync has cognitive complexity 18 (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.
BlazorGenerator.Emit (cognitive 18) src/Rask.Generators/Blazor/BlazorGenerator.cs:84— BlazorGenerator.Emit 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.EmitBuilderEntries (cognitive 18) src/Rask.Generators/ComponentFactoryGenerator.cs:1693— ComponentFactoryGenerator.EmitBuilderEntries 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.
ComponentScopedCssGenerator.Emit (cognitive 18) src/Rask.Generators/ComponentScopedCssGenerator.cs:116— ComponentScopedCssGenerator.Emit 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.
ExternalGenerator.Describe (cognitive 18) src/Rask.Generators/External/ExternalGenerator.cs:524— ExternalGenerator.Describe 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.
PackageIslandProps.Facts (cognitive 18) src/Rask.Generators/External/PackageIslands/PackageIslandProps.cs:224— PackageIslandProps.Facts 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.
RaskEndpointExtensions.RunInSessionAsync (cognitive 18) src/Rask.Server/RaskEndpointExtensions.cs:2065— RaskEndpointExtensions.RunInSessionAsync 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.OnMountAsync (cognitive 18) src/Rask.Site/Features/Http/HttpFetchDemo.cs:23— HttpFetchDemo.OnMountAsync 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.
UiKitDataInputDemo.Render (cognitive 18) src/Rask.Site/Features/UiKit/UiKitDataInputDemo.cs:47— UiKitDataInputDemo.Render has cognitive complexity 18 (threshold 15). Of this number, 14 points are the body's own statements and 4 belong to 5 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.
OrphanSweeper.SweepAsync (cognitive 18) src/Rask.Storage/OrphanSweeper.cs:182— OrphanSweeper.SweepAsync 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.
lit.assign (cognitive 18) src/Rask.External/client/lit.ts:67— lit.assign has cognitive complexity 18 (threshold 15). Drivers by points: if/else 7 (15 pts), loops 3 (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.applyDiffReply (cognitive 18) src/Rask.Server/Resources/rask.ts:1444— 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 literal inside it that branches (line 1445). 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.
ApiCall.ReadProblem (cognitive 17) src/Rask.Api.Client/ApiCall.cs:177— ApiCall.ReadProblem 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.cs:309— ModelInputGenerator.AggregateReferencesOf 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.
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.
SvgElement.WriteAttributes (cognitive 17) src/Rask.Core/Components/Svg/SvgElement.cs:110— SvgElement.WriteAttributes has cognitive complexity 17 (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.
ExternalPackageScan.StringEnd (cognitive 17) src/Rask.External.Tasks/ExternalPackageScan.cs:444— ExternalPackageScan.StringEnd 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.
InternalRouteStringAnalyzer.TryAddPage (cognitive 17) src/Rask.Generators/Analyzers/InternalRouteStringAnalyzer.cs:192— InternalRouteStringAnalyzer.TryAddPage 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.cs:4020— 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.
ComponentFactoryGenerator.BuildConstraintsClause (cognitive 17) src/Rask.Generators/ComponentFactoryGenerator.cs:4806— 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.
RoutesGenerator.NormalizeTemplate (cognitive 17) src/Rask.Generators/RoutesGenerator.cs:347— 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.
LogScopes.Flatten (cognitive 17) src/Rask.Logging/LogScopes.cs:77— 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.
RaskEndpointExtensions.EnforceAuthAndRenderAsync (cognitive 17) src/Rask.Server/RaskEndpointExtensions.cs:2554— RaskEndpointExtensions.EnforceAuthAndRenderAsync has cognitive complexity 17 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
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.
SqlitePragmas.BuildScript (cognitive 17) src/Rask.SQLite/SqlitePragmas.cs:20— SqlitePragmas.BuildScript has cognitive complexity 17 (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.
UiDataGrid.ResolveQuery (cognitive 17) src/Rask.Ui/UiDataGrid.cs:755— UiDataGrid.ResolveQuery 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.
UiFileInput.Render (cognitive 17) src/Rask.Ui/UiFileInput.cs:114— UiFileInput.Render has cognitive complexity 17 (threshold 15). Of this number, 15 points are the body's own statements and 2 belong to one function literal inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
RaskApiValidation.ValidateEndpointAsync (cognitive 17) src/Rask/ApiValidation.cs:140— 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.
ActionFilter.OnActionExecutionAsync (cognitive 17) src/Rask/ApiValidation.cs:199— ActionFilter.OnActionExecutionAsync 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-dom.syncFormProperty (cognitive 17) src/Rask.Core/Resources/rask-dom.ts:103— rask-dom.syncFormProperty has cognitive complexity 17 (threshold 15). Drivers by points: if/else 9 (13 pts), boolean chains 4 (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.
extract-props.synthesizeEmits (cognitive 17) src/Rask.External/extractor/extract-props.ts:1399— extract-props.synthesizeEmits has cognitive complexity 17 (threshold 15). Drivers by points: if/else 2 (6 pts), ternaries 2 (5 pts), boolean chains 3, loops 2 (3 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.restoreOneField (cognitive 17) src/Rask.Server/Resources/rask.ts:837— 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.
ModelStateMutationAnalyzer.CanNarrow (cognitive 16) src/Rask.Batteries.Generators/Analyzers/ModelStateMutationAnalyzer.cs:186— 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.Emit (cognitive 16) src/Rask.Batteries.Generators/CqrsDispatchGenerator.cs:185— CqrsDispatchGenerator.Emit 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.
ModelRegistryGenerator.EmitConventions (cognitive 16) src/Rask.Batteries.Generators/ModelRegistryGenerator.cs:527— ModelRegistryGenerator.EmitConventions 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.
ReadModelGenerator.EmitFace (cognitive 16) src/Rask.Batteries.Generators/ReadModelGenerator.cs:185— ReadModelGenerator.EmitFace 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.
Component.RenderAsLiveRootCore (cognitive 16) src/Rask.Core/Component.cs:2594— Component.RenderAsLiveRootCore 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.
DataAnnotationsFieldValidator.ResultsFor (cognitive 16) src/Rask.Core/Forms/DataAnnotationsFieldValidator.cs:140— DataAnnotationsFieldValidator.ResultsFor 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:1015— 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.
PageBinder.TryGetRawValue (cognitive 16) src/Rask.Core/Routing/PageBinder.cs:92— PageBinder.TryGetRawValue 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.
RemoteDispatch.UploadLargeFilesAsync (cognitive 16) src/Rask.Cqrs.Client/RemoteDispatch.cs:230— RemoteDispatch.UploadLargeFilesAsync 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, 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.
SystemPage.BackupStats (cognitive 16) src/Rask.Dashboard/Pages/SystemPage.cs:126— SystemPage.BackupStats 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.Builder.ctor (cognitive 16) src/Rask.DevTools/Probe/DevToolsComponentNode.cs:250— Builder.Builder.ctor 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/DevToolsComponentNode.cs:467— 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.
ExternalBuildPlan.EntryModule (cognitive 16) src/Rask.External.Tasks/ExternalBuildPlan.cs:64— ExternalBuildPlan.EntryModule 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.
SyncExternalPropsSnapshotsTask.Execute (cognitive 16) src/Rask.External.Tasks/SyncExternalPropsSnapshotsTask.cs:59— SyncExternalPropsSnapshotsTask.Execute 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.PinSets (cognitive 16) src/Rask.Generators/ComponentFactoryGenerator.cs:2860— 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.
ComponentFactoryGenerator.GetCandidate (cognitive 16) src/Rask.Generators/ComponentFactoryGenerator.cs:4493— ComponentFactoryGenerator.GetCandidate has cognitive complexity 16 (threshold 15). To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
ComponentFactoryGenerator.OverridesLifecycleHook (cognitive 16) src/Rask.Generators/ComponentFactoryGenerator.cs:4945— 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.
RoutesGenerator.PathParamTypeFqn (cognitive 16) src/Rask.Generators/RoutesGenerator.cs:1344— 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.
RaskEndpointExtensions.ReceiveFramesAsync (cognitive 16) src/Rask.Server/RaskEndpointExtensions.cs:1198— RaskEndpointExtensions.ReceiveFramesAsync 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.HandleUploadAsync (cognitive 16) src/Rask.Server/RaskEndpointExtensions.cs:3035— RaskEndpointExtensions.HandleUploadAsync 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.
UiDataGrid.Band (cognitive 16) src/Rask.Ui/UiDataGrid.cs:1296— UiDataGrid.Band has cognitive complexity 16 (threshold 15). To reduce it, break up the iteration: give each loop body a named function, and split a multi-phase loop into one function per phase so no single body carries the whole pipeline.
UiNavTab.Render (cognitive 16) src/Rask.Ui/UiNavTab.cs:58— UiNavTab.Render 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.
gamepad.watch (cognitive 16) src/Rask.Core/Resources/browser/gamepad.ts:38— gamepad.watch has cognitive complexity 16 (threshold 15). Drivers by points: if/else 5 (10 pts), boolean chains 2, loops 1 (2 pts), ternaries 1 (2 pts) (nesting depth added 7). Most of this is not in the body itself: 2 of the 16 points are its own statements and the rest belongs to 3 function literals inside it that branch (lines 48, 78, 91). 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.
rask-morph.raskApplySelectSelection (cognitive 16) src/Rask.Core/Resources/rask-morph.ts:222— 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.
extract-props.propsOf (cognitive 16) src/Rask.External/extractor/extract-props.ts:383— extract-props.propsOf has cognitive complexity 16 (threshold 15). Drivers by points: if/else 7 (10 pts), ternaries 2 (4 pts), boolean chains 2 (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-http-transport.createSseParser (cognitive 16) src/Rask.Server/Resources/rask-http-transport.ts:35— rask-http-transport.createSseParser has cognitive complexity 16 (threshold 15). Drivers by points: if/else 8 (11 pts), boolean chains 2, ternaries 2, loops 1 (nesting depth added 3). Of this number, 10 points are the body's own statements and 6 belong 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.
D22 · Internal API Consistency· Ambiguous overload resolution for SetAsync when both options and typeInfo are provided. The API exposes two overloads that differ only by the presence of JsonTypeInfo, but if a caller wants to specify both, they cannot do so without creating a new overload or using a different method. This forces users to choose between providing options or type info, or requires a third overload. · ×1
Ambiguous overload resolution for SetAsync when both options and typeInfo are provided. The API exposes two overloads that differ only by the presence of JsonTypeInfo, but if a caller wants to specify both, they cannot do so without creating a new overload or using a different method. This forces users to choose between providing options or type info, or requires a third overload. — Add a third overload: SetAsync<T>(string key, T value, JsonTypeInfo<T> typeInfo, DistributedCacheEntryOptions? options, CancellationToken) to allow specifying both, or remove the options parameter from the typeInfo overload if it is rarely used with type info. (signatures: Rask.Cache.Cache.SetAsync<T>(string key, T value, DistributedCacheEntryOptions? options, CancellationToken) | Rask.Cache.Cache.SetAsync<T>(string key, T value, JsonTypeInfo<T> typeInfo, DistributedCacheEntryOptions? options, CancellationToken))
D22 · Internal API Consistency· Same ambiguity issue as SetAsync. If a user wants to provide both JsonTypeInfo and DistributedCacheEntryOptions, they must use the second overload. However, if they only want options, they use the first. This is slightly inconsistent with standard .NET patterns where optional parameters are often combined into a single signature with optional arguments, or distinct overloads are clearly separated by purpose (e.g., one for serialization context, one for caching options). Here, the separation is by parameter presence, which can be confusing. · ×1
Same ambiguity issue as SetAsync. If a user wants to provide both JsonTypeInfo and DistributedCacheEntryOptions, they must use the second overload. However, if they only want options, they use the first. This is slightly inconsistent with standard .NET patterns where optional parameters are often combined into a single signature with optional arguments, or distinct overloads are clearly separated by purpose (e.g., one for serialization context, one for caching options). Here, the separation is by parameter presence, which can be confusing. — Consider consolidating into a single method with optional parameters: GetOrAddAsync<T>(string key, Func<CancellationToken, Task<T>> factory, JsonTypeInfo<T>? typeInfo = null, DistributedCacheEntryOptions? options = null, CancellationToken cancellationToken = default). (signatures: Rask.Cache.Cache.GetOrAddAsync<T>(string key, Func<CancellationToken, Task<T>> factory, DistributedCacheEntryOptions? options, CancellationToken) | Rask.Cache.Cache.GetOrAddAsync<T>(string key, Func<CancellationToken, Task<T>> factory, JsonTypeInfo<T> typeInfo, DistributedCacheEntryOptions? options, CancellationToken))
D22 · Internal API Consistency· Same ambiguity issue as SetAsync and GetOrAddAsync. Users cannot provide both JsonTypeInfo and CancellationToken in a way that distinguishes intent clearly if they also want to pass options (though options aren't in GetAsync, the pattern is inconsistent with SetAsync/GetOrAddAsync which have options). More importantly, the existence of two overloads for GetAsync where one adds type info but no options, while SetAsync/GetOrAddAsync have overloads with options, creates a fragmented API surface. · ×1
Same ambiguity issue as SetAsync and GetOrAddAsync. Users cannot provide both JsonTypeInfo and CancellationToken in a way that distinguishes intent clearly if they also want to pass options (though options aren't in GetAsync, the pattern is inconsistent with SetAsync/GetOrAddAsync which have options). More importantly, the existence of two overloads for GetAsync where one adds type info but no options, while SetAsync/GetOrAddAsync have overloads with options, creates a fragmented API surface. — Align GetAsync with the pattern of SetAsync/GetOrAddAsync by adding an overload that accepts both JsonTypeInfo and DistributedCacheEntryOptions, or unify all methods to use optional parameters for typeInfo and options. (signatures: Rask.Cache.Cache.GetAsync<T>(string key, CancellationToken) | Rask.Cache.Cache.GetAsync<T>(string key, JsonTypeInfo<T> typeInfo, CancellationToken))
Cross-context type WebAppManifest (Rask.Core → Rask.Server) — WebAppManifest (context Rask.Core) is exposed in Rask.Server's public surface via RaskPwaExtensions.AddRaskPwa — couples the contexts.
Cross-context type RouteUrl (Rask.Core → Rask.Site) — RouteUrl (context Rask.Core) is exposed in Rask.Site's public surface via PageMeta.LinkTo — couples the contexts.
Cross-context type PendingDownload (Rask.Core → Rask.Testing) — PendingDownload (context Rask.Core) is exposed in Rask.Testing's public surface via TestDownloadSink.TryConsume — couples the contexts.
Cross-context type FieldIdentifier (Rask.Core → Rask.Validation.FluentValidation) — FieldIdentifier (context Rask.Core) is exposed in Rask.Validation.FluentValidation's public surface via FluentValidationFieldValidator.ValidateFieldAsync — couples the contexts.
Cross-context type MediaStreamId (Rask.Core → Rask.Wasm) — MediaStreamId (context Rask.Core) is exposed in Rask.Wasm's public surface via IMediaStreamHandle.Id — couples the contexts.
Cross-context type WebAppManifest (Rask.Core → Rask) — WebAppManifest (context Rask.Core) is exposed in Rask's public surface via RaskAppOptions.Pwa — couples the contexts.
D4 · Code Duplication· Members sharing a duplicated core (4 members, 50+ identical tokens) · ×1
Members sharing a duplicated core (4 members, 50+ identical tokens) src/Rask.Generators/ComponentFactoryGenerator.cs:139— src/Rask.Generators/ComponentFactoryGenerator.cs:139-256 | src/Rask.Generators/ComponentScopedCssGenerator.cs:51-69 | src/Rask.Generators/ComponentScopedJsGenerator.cs:102-145 | src/Rask.Generators/RoutesGenerator.cs:193-229 — 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 (38–44 lines × 3) src/Rask.Jobs/JobProcessor.cs:62— src/Rask.Jobs/JobProcessor.cs:62-105 | src/Rask.Mail/MailProcessor.cs:51-88 | src/Rask.Outbox/OutboxProcessor.cs:48-85 — before extracting anything, compare `src/Rask.Jobs/JobProcessor.cs` and `src/Rask.Mail/MailProcessor.cs` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 119 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.Jobs/JobProcessor.cs:62` 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 (39–41 lines × 3) src/Rask.Jobs/JobProcessor.cs:458— src/Rask.Jobs/JobProcessor.cs:458-496 | src/Rask.Mail/MailProcessor.cs:343-381 | src/Rask.Outbox/OutboxProcessor.cs:347-387 — before extracting anything, compare `src/Rask.Jobs/JobProcessor.cs` and `src/Rask.Mail/MailProcessor.cs` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 119 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.Jobs/JobProcessor.cs:458` 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 (39–41 lines × 2) src/Rask.Core/Components/Button.cs:114— src/Rask.Core/Components/Button.cs:114-154 | src/Rask.Core/Components/Input.cs:408-446 — 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.Core/Components/Button.cs:114` 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 (23–36 lines × 2) src/Rask.Core/Component.cs:1834— src/Rask.Core/Component.cs:1834-1869 | src/Rask.Core/Component.cs:1880-1902 — 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.cs:1834` 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 (36 lines × 2) src/Rask.Ui/UiMultiSelect.cs:68— src/Rask.Ui/UiMultiSelect.cs:68-110 | src/Rask.Ui/UiSelect.cs:122-157 — 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. 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 (32–33 lines × 2) src/Rask.Auth.Client/BrowserAuth.cs:97— src/Rask.Auth.Client/BrowserAuth.cs:97-129 | src/Rask.Auth/ServerAuth.cs:93-124 — 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.Auth.Client/BrowserAuth.cs:97` 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 (28–33 lines × 2) src/Rask.Core/Components/Button.cs:30— src/Rask.Core/Components/Button.cs:30-62 | src/Rask.Core/Components/Input.cs:119-146 — 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 (33 lines × 2) src/Rask.Core/Components/Svg/SvgText.cs:61— src/Rask.Core/Components/Svg/SvgText.cs:61-93 | src/Rask.Core/Components/Svg/Tspan.cs:41-73 — 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.Core/Components/Svg/SvgText.cs:61` 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 (25–32 lines × 3) src/Rask.Ui/UiCalendar.cs:42— src/Rask.Ui/UiCalendar.cs:42-73 | src/Rask.Ui/UiCalendarMultiple.cs:25-49 | src/Rask.Ui/UiCalendarRange.cs:25-49 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from 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 (26–30 lines × 2) src/Rask.Ui/UiRadio.cs:30— src/Rask.Ui/UiRadio.cs:30-59 | src/Rask.Ui/UiToggle.cs:26-51 — before extracting anything, compare `src/Rask.Ui/UiRadio.cs` and `src/Rask.Ui/UiToggle.cs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 90 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 (29 lines × 2) src/Rask.Generators/ComponentScopedCssGenerator.cs:72— src/Rask.Generators/ComponentScopedCssGenerator.cs:72-100 | src/Rask.Generators/ComponentScopedJsGenerator.cs:148-176 — 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 93 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:72` 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 (18–28 lines × 3) src/Rask.Ui/UiMenuCheckbox.cs:32— src/Rask.Ui/UiMenuCheckbox.cs:32-49 | src/Rask.Ui/UiRadio.cs:36-63 | src/Rask.Ui/UiToggle.cs:32-55 — before extracting anything, compare `src/Rask.Ui/UiRadio.cs` and `src/Rask.Ui/UiToggle.cs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 90 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 (27 lines × 2) src/Rask.Core/HtmlSerializer.cs:242— src/Rask.Core/HtmlSerializer.cs:242-268 | src/Rask.Core/HtmlSerializer.cs:295-321 — 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/HtmlSerializer.cs:242` 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 (18–26 lines × 3) src/Rask.Ui/UiFilter.cs:32— src/Rask.Ui/UiFilter.cs:32-57 | src/Rask.Ui/UiFormField.cs:158-175 | src/Rask.Ui/UiMenuRadioGroup.cs:32-49 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from all 3 call sites, so a change lands once.
Duplicated block (24–26 lines × 2) src/Rask.Wasm/WasmPrerender.cs:700— src/Rask.Wasm/WasmPrerender.cs:700-723 | src/Rask.Wasm/WasmPrerender.cs:778-803 — 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 (24–25 lines × 2) src/Rask.Generators/ComponentFactoryGenerator.cs:5150— src/Rask.Generators/ComponentFactoryGenerator.cs:5150-5174 | src/Rask.Generators/RoutesGenerator.cs:399-422 — 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 (25 lines × 2) src/Rask.Jobs/Job.cs:34— src/Rask.Jobs/Job.cs:34-58 | src/Rask.Outbox/OutboxMessage.cs:45-69 — 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 (23–25 lines × 2) src/Rask.Server/RaskEndpointExtensions.cs:2576— src/Rask.Server/RaskEndpointExtensions.cs:2576-2600 | src/Rask.Wasm/WasmLiveSession.cs:490-512 — 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.Server/RaskEndpointExtensions.cs:2576` 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 (23–24 lines × 3) src/Rask.Generators/Blazor/BlazorGenerator.cs:319— src/Rask.Generators/Blazor/BlazorGenerator.cs:319-342 | src/Rask.Generators/External/ExternalGenerator.cs:486-509 | src/Rask.Generators/Validation/ValidatorRegistryGenerator.cs:226-248 — 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.
Duplicated block (21–23 lines × 2) src/Rask.Api.Client/ApiCall.cs:253— src/Rask.Api.Client/ApiCall.cs:253-273 | src/Rask.Cqrs.Client/RemoteDispatch.cs:592-614 — 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.
Duplicated block (21 lines × 3) src/Rask.Jobs/JobOptions.cs:10— src/Rask.Jobs/JobOptions.cs:10-30 | src/Rask.Mail/MailOptions.cs:64-84 | src/Rask.Outbox/OutboxOptions.cs:7-35 — before extracting anything, compare `src/Rask.Jobs/JobOptions.cs` and `src/Rask.Mail/MailOptions.cs` as WHOLE FILES: this scan already matched 3 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. 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 (20–21 lines × 2) src/Rask.Generators.Shared/WireShape.cs:538— src/Rask.Generators.Shared/WireShape.cs:538-558 | src/Rask.Generators.Shared/WireShape.cs:609-628 — 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–20 lines × 2) src/Rask.Ui/UiCheckboxGroup.cs:22— src/Rask.Ui/UiCheckboxGroup.cs:22-38 | src/Rask.Ui/UiRadioGroup.cs:22-41 — before extracting anything, compare `src/Rask.Ui/UiCheckboxGroup.cs` and `src/Rask.Ui/UiRadioGroup.cs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 40 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.Ui/UiCheckboxGroup.cs:22` 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 (19 lines × 8) src/Rask.Core/Components/Svg/Filter.cs:43— src/Rask.Core/Components/Svg/Filter.cs:43-61 | src/Rask.Core/Components/Svg/ForeignObject.cs:29-47 | src/Rask.Core/Components/Svg/Image.cs:35-53 | src/Rask.Core/Components/Svg/Mask.cs:48-66 | src/Rask.Core/Components/Svg/Pattern.cs:49-67 | src/Rask.Core/Components/Svg/Rect.cs:41-59 | src/Rask.Core/Components/Svg/Symbol.cs:58-76 | src/Rask.Core/Components/Svg/Use.cs:41-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 8 call sites, so a change lands once.
Duplicated block (19 lines × 3) src/Rask.Jobs/JobProcessor.cs:136— src/Rask.Jobs/JobProcessor.cs:136-154 | src/Rask.Mail/MailProcessor.cs:156-174 | src/Rask.Outbox/OutboxProcessor.cs:158-176 — before extracting anything, compare `src/Rask.Jobs/JobProcessor.cs` and `src/Rask.Mail/MailProcessor.cs` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 119 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.Jobs/JobProcessor.cs:136` 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:135` calls `EnqueueDueRecurringAsync`, `ConfigureAwait` and `src/Rask.Mail/MailProcessor.cs:155` 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 (17–19 lines × 2) src/Rask.Logging/LogScopes.cs:86— src/Rask.Logging/LogScopes.cs:86-104 | src/Rask.Logging/LogScopes.cs:106-122 — 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:86` 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 (18 lines × 3) src/Rask.Core/Routing/RouteRegistry.cs:84— src/Rask.Core/Routing/RouteRegistry.cs:84-101 | src/Rask.Jobs/JobSerializerRegistry.cs:64-81 | src/Rask.Outbox/OutboxSerializerRegistry.cs:64-81 — before extracting anything, compare `src/Rask.Jobs/JobSerializerRegistry.cs` and `src/Rask.Outbox/OutboxSerializerRegistry.cs` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 91 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.Core/Routing/RouteRegistry.cs:84` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note first that the copies are not typed on the same thing: the declarations holding them bind `registrations` to `IEnumerable<RouteRegistration>` in one and `IEnumerable<(string TypeName, Type Type)>` 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 (15–18 lines × 3) src/Rask.Generators/Analyzers/ComponentConstructionAnalyzer.cs:36— src/Rask.Generators/Analyzers/ComponentConstructionAnalyzer.cs:36-53 | src/Rask.Generators/Analyzers/MissingKeyAnalyzer.cs:47-61 | src/Rask.Generators/Analyzers/RedundantStateHasChangedAnalyzer.cs:44-58 — 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.
Duplicated block (17–18 lines × 2) src/Rask.Ui/UiMultiSelect.cs:499— src/Rask.Ui/UiMultiSelect.cs:499-515 | src/Rask.Ui/UiSelect.cs:439-456 — 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/UiMultiSelect.cs:499` 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–17 lines × 2) src/Rask.Core/Live/LivePayload.cs:515— src/Rask.Core/Live/LivePayload.cs:515-530 | src/Rask.Core/Live/LivePayload.cs:535-551 — 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/LivePayload.cs:515` 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 (11–17 lines × 2) src/Rask.Generators/ComponentScopedCssGenerator.cs:52— src/Rask.Generators/ComponentScopedCssGenerator.cs:52-62 | src/Rask.Generators/ComponentScopedJsGenerator.cs:103-119 — 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 93 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 (16 lines × 4) src/Rask.Ui/UiCheckbox.cs:40— src/Rask.Ui/UiCheckbox.cs:40-71 | src/Rask.Ui/UiMenuCheckbox.cs:34-49 | src/Rask.Ui/UiRadio.cs:38-63 | src/Rask.Ui/UiToggle.cs:34-55 — before extracting anything, compare `src/Rask.Ui/UiRadio.cs` and `src/Rask.Ui/UiToggle.cs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 90 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 (12–16 lines × 2) src/Rask.Batteries.Generators/ModelInputGenerator.cs:160— src/Rask.Batteries.Generators/ModelInputGenerator.cs:160-171 | src/Rask.Batteries.Generators/ModelRegistryGenerator.cs:89-104 — 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/ModelInputGenerator.cs:160` 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.Batteries.Generators/ModelRegistryGenerator.cs:109` calls `EmitConventions` and `src/Rask.Batteries.Generators/ModelInputGenerator.cs:172` 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 (15–16 lines × 2) src/Rask.Core/Live/EventPayload.cs:23— src/Rask.Core/Live/EventPayload.cs:23-38 | src/Rask.Core/Live/ScrollEvent.cs:23-37 — 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 (9–12 lines × 3) src/Rask.Site/Features/Validation/InlineAsyncValidateDemo.cs:19— src/Rask.Site/Features/Validation/InlineAsyncValidateDemo.cs:19-27 | 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:16` 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–11 lines × 2) src/Rask.Server/RaskEndpointExtensions.cs:1156— src/Rask.Server/RaskEndpointExtensions.cs:1156-1166 | src/Rask.Server/RaskEndpointExtensions.cs:1323-1331 — 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.Server/RaskEndpointExtensions.cs:1156` 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 (7–10 lines × 2) src/Rask.Ui/UiMultiSelect.cs:244— src/Rask.Ui/UiMultiSelect.cs:244-250 | src/Rask.Ui/UiSelect.cs:266-275 — 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/UiSelect.cs:266` 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 (7 lines × 3) src/Rask.Dashboard/Pages/CachePage.cs:42— src/Rask.Dashboard/Pages/CachePage.cs:42-48 | src/Rask.Dashboard/Pages/QueuePage.cs:56-62 | src/Rask.Dashboard/Pages/StoragePage.cs:42-48 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from 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: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 (6 lines × 3) src/Rask.Generators/ComponentFactoryGenerator.cs:139— src/Rask.Generators/ComponentFactoryGenerator.cs:139-144 | src/Rask.Generators/ComponentScopedCssGenerator.cs:51-57 | src/Rask.Generators/ComponentScopedJsGenerator.cs:102-108 — 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 93 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:139` 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 × 3) src/Rask.Generators/ComponentFactoryGenerator.cs:1765— src/Rask.Generators/ComponentFactoryGenerator.cs:1765-1769 | src/Rask.Generators/ComponentFactoryGenerator.cs:1773-1777 | src/Rask.Generators/ComponentFactoryGenerator.cs:3663-3668 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/Rask.Generators/ComponentFactoryGenerator.cs:1765` 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 × 3) src/Rask.Generators/Analyzers/DuplicateChainCallAnalyzer.cs:99— src/Rask.Generators/Analyzers/DuplicateChainCallAnalyzer.cs:99-106 | src/Rask.Generators/Analyzers/GridColumnTokenAnalyzer.cs:238-245 | src/Rask.Generators/Analyzers/OptionTemplateNativeAnalyzer.cs:124-131 — 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. 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 (15 lines × 3) src/Rask.Jobs/JobProcessor.cs:115— src/Rask.Jobs/JobProcessor.cs:115-129 | src/Rask.Mail/MailProcessor.cs:136-150 | src/Rask.Outbox/OutboxProcessor.cs:132-146 — before extracting anything, compare `src/Rask.Jobs/JobProcessor.cs` and `src/Rask.Mail/MailProcessor.cs` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 119 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.
Coverage not measured — .NET and JavaScript/TypeScript suite — Coverage NOT MEASURED: the .NET half could not be measured — no coverage produced (collector absent, or test run exceeded the inline budget); the JavaScript/TypeScript half could not be measured — src/Rask.Templates/analog/client/ runs vitest but declares no coverage provider, so the suite can run and still produce no lcov — add `@vitest/coverage-v8` (or `@vitest/coverage-istanbul`) as a devDependency. This repository's production source spans both ecosystems, and no partial figure is published as if it were the whole: coverage is excluded from the score rather than counted as a near-zero. The named suite step is one the repository's maintainers can perform; once it passes, the real number is measured on the next scan. Alternatively, commit the lcov/Cobertura report your CI produces and it is read without a re-run.
Anemic entity: QueuedMail src/Rask.Mail/QueuedMail.cs:23— `QueuedMail` is an aggregate/entity with 15 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service.
Non-idempotent mutation: Features.IncrementCounterHandler.HandleAsync src/Rask.Site/Features/Cqrs/CounterSlice.cs:49— `Features.IncrementCounterHandler.HandleAsync` mutates persistent state (an event publish) with no idempotency guard, and the model confirms a re-run would double-apply it. A retry or at-least-once redelivery means it can run twice — add an exists/dedup check, an upsert, an idempotency-key/inbox, or a versioned write.
Hollow method — returns a constant without doing the work src/Rask.Wasm/JSInterop.cs:285— `ReadFileChunkAsync` looks like it should compute a result but its body just returns a constant — a placeholder return that was never filled in.
P8 · Schema migrations· Schema created with EnsureCreated() (no migration path) · ×1
Schema created with EnsureCreated() (no migration path) src/Rask.Data/TestDatabase.cs:91— `EnsureCreated()` builds the schema once and can't evolve it — there's no upgrade path for an existing production database, and it bypasses the migrations history. Adopt a versioned schema-migration mechanism (with EF Core: `dotnet ef migrations add` + `Migrate()` on startup) so schema changes are versioned and applied safely.
Sync-over-async blocking — 12 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).
Duplication concentrated across 13 sibling directories (26 clone groups) src/Rask.Templates/preact/client/src/app.tsx:2— 26 duplicated blocks under src/Rask.Templates/ have copies in at least two of the sibling directories analog, angular, lit, nextjs, nuxt, preact (+7 more sibling(s) not listed) — 24 of them are reported below, and 2 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 26 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 26 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 26 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.
Duplication concentrated across 5 sibling directories (25 clone groups) src/Rask.Server/Resources/rask.ts:1461— 25 duplicated blocks under src/ have copies in at least two of the sibling directories Rask.Core, Rask.Server, Rask.Site, Rask.Templates, Rask.Wasm — 19 of them are reported below, and 6 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 25 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 25 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 25 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.
Wholesale file copy (79 identical lines × 2 files) src/Rask.Templates/preact/client/src/app.tsx:2— src/Rask.Templates/preact/client/src/app.tsx:2 · src/Rask.Templates/react/client/src/App.tsx:2 — these 2 files are line-for-line copies of one another — 79 lines are identical, in the same order, in every one of them — so this is one fact about the file set, not a block to extract. An edit made to one file and not the others changes behaviour silently, which is the failure a wholesale copy guarantees. Pick one file as the single source and derive the others from it (re-export it, spread it into the local overrides each variant genuinely needs, or generate the copies at build time) — the few lines that differ between the files are exactly the part each variant should still own. Check first whether the copies are deliberately standalone deliverables (a translation file seeded from its sibling and waiting to be translated); where they are, the duplication is the design, and the honest move is to mark the seeded file as untranslated rather than to let it pass as done.
Wholesale file copy (56 identical lines × 2 files) src/Rask.Templates/nextjs/client/app/auth-form.tsx:3— src/Rask.Templates/nextjs/client/app/auth-form.tsx:3 · src/Rask.Templates/tanstack-start/client/src/components/AuthForm.tsx:1 — these 2 files are line-for-line copies of one another — 56 lines are identical, in the same order, in every one of them — so this is one fact about the file set, not a block to extract. An edit made to one file and not the others changes behaviour silently, which is the failure a wholesale copy guarantees. Pick one file as the single source and derive the others from it (re-export it, spread it into the local overrides each variant genuinely needs, or generate the copies at build time) — the few lines that differ between the files are exactly the part each variant should still own. Check first whether the copies are deliberately standalone deliverables (a translation file seeded from its sibling and waiting to be translated); where they are, the duplication is the design, and the honest move is to mark the seeded file as untranslated rather than to let it pass as done.
Wholesale file copy (54 identical lines × 2 files) src/Rask.Templates/solid/client/src/Auth.tsx:1— src/Rask.Templates/solid/client/src/Auth.tsx:1 · src/Rask.Templates/solidstart/client/src/components/AuthForm.tsx:1 — these 2 files are line-for-line copies of one another — 54 lines are identical, in the same order, in every one of them — so this is one fact about the file set, not a block to extract. An edit made to one file and not the others changes behaviour silently, which is the failure a wholesale copy guarantees. Pick one file as the single source and derive the others from it (re-export it, spread it into the local overrides each variant genuinely needs, or generate the copies at build time) — the few lines that differ between the files are exactly the part each variant should still own. Check first whether the copies are deliberately standalone deliverables (a translation file seeded from its sibling and waiting to be translated); where they are, the duplication is the design, and the honest move is to mark the seeded file as untranslated rather than to let it pass as done.
Duplicated block (39 lines × 2 locations) src/Rask.Templates/svelte/client/eslint.config.mjs:13— src/Rask.Templates/svelte/client/eslint.config.mjs:13 · src/Rask.Templates/sveltekit/client/eslint.config.mjs:13 — the 2 copies are spread across 2 files, and the SHAPE of this repetition could not be determined. It is not a run of declarations, a listing, a declaration header, a type body or a slice through a construct — and it was not measured as a run of executable statements either, so this row cannot tell you whether a function can stand where these lines are. Read the two spans before acting, because the move is opposite in the two cases. Where they are statements, the ordinary answer holds: give the shared part one home and call it from each site. Where they turn out to be declarations, a literal's entries, or the cases of an enumeration, there is no call site to call anything from, and collapsing them would delete what each copy pins — a shared base type, a generated set, or one exported constant each site refers to is the move instead, and sometimes the honest answer is that there is nothing to extract at all. Reported because the copies drift apart the first time only one of them is edited, which is true whichever of those they are.
Duplicated block (38 lines × 2 locations) src/Rask.Templates/nuxt/client/eslint.config.mjs:13— src/Rask.Templates/nuxt/client/eslint.config.mjs:13 · src/Rask.Templates/vue/client/eslint.config.mjs:13 — the 2 copies are spread across 2 files, and the SHAPE of this repetition could not be determined. It is not a run of declarations, a listing, a declaration header, a type body or a slice through a construct — and it was not measured as a run of executable statements either, so this row cannot tell you whether a function can stand where these lines are. Read the two spans before acting, because the move is opposite in the two cases. Where they are statements, the ordinary answer holds: give the shared part one home and call it from each site. Where they turn out to be declarations, a literal's entries, or the cases of an enumeration, there is no call site to call anything from, and collapsing them would delete what each copy pins — a shared base type, a generated set, or one exported constant each site refers to is the move instead, and sometimes the honest answer is that there is nothing to extract at all. Reported because the copies drift apart the first time only one of them is edited, which is true whichever of those they are.
Duplicated block (37 lines × 3 locations) src/Rask.Templates/preact/client/eslint.config.mjs:13— src/Rask.Templates/preact/client/eslint.config.mjs:13 · src/Rask.Templates/react/client/eslint.config.mjs:13 · src/Rask.Templates/tanstack-start/client/eslint.config.mjs:13 — the 3 copies are spread across 3 files, and the SHAPE of this repetition could not be determined. It is not a run of declarations, a listing, a declaration header, a type body or a slice through a construct — and it was not measured as a run of executable statements either, so this row cannot tell you whether a function can stand where these lines are. Read the two spans before acting, because the move is opposite in the two cases. Where they are statements, the ordinary answer holds: give the shared part one home and call it from each site. Where they turn out to be declarations, a literal's entries, or the cases of an enumeration, there is no call site to call anything from, and collapsing them would delete what each copy pins — a shared base type, a generated set, or one exported constant each site refers to is the move instead, and sometimes the honest answer is that there is nothing to extract at all. Reported because the copies drift apart the first time only one of them is edited, which is true whichever of those they are.
R10 · Code Duplication· Duplicated block with local edits (34 matched lines × 2 locations) · ×1
Duplicated block with local edits (34 matched lines × 2 locations) src/Rask.Core/Resources/browser/deviceMotion.ts:40— src/Rask.Core/Resources/browser/deviceMotion.ts:40 · src/Rask.Core/Resources/browser/deviceOrientation.ts:51 — the two spans are one implementation copied and then locally edited — 215 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 (32 lines × 2 locations) src/Rask.Templates/solid/client/eslint.config.mjs:13— src/Rask.Templates/solid/client/eslint.config.mjs:13 · src/Rask.Templates/solidstart/client/eslint.config.mjs:13 — the 2 copies are spread across 2 files, and the SHAPE of this repetition could not be determined. It is not a run of declarations, a listing, a declaration header, a type body or a slice through a construct — and it was not measured as a run of executable statements either, so this row cannot tell you whether a function can stand where these lines are. Read the two spans before acting, because the move is opposite in the two cases. Where they are statements, the ordinary answer holds: give the shared part one home and call it from each site. Where they turn out to be declarations, a literal's entries, or the cases of an enumeration, there is no call site to call anything from, and collapsing them would delete what each copy pins — a shared base type, a generated set, or one exported constant each site refers to is the move instead, and sometimes the honest answer is that there is nothing to extract at all. Reported because the copies drift apart the first time only one of them is edited, which is true whichever of those they are.
Duplicated block (31 lines × 3 locations) src/Rask.Templates/analog/client/eslint.config.mjs:12— src/Rask.Templates/analog/client/eslint.config.mjs:12 · src/Rask.Templates/angular/client/eslint.config.mjs:12 · src/Rask.Templates/nextjs/client/eslint.config.mjs:12 — the 3 copies are spread across 3 files, and the SHAPE of this repetition could not be determined. It is not a run of declarations, a listing, a declaration header, a type body or a slice through a construct — and it was not measured as a run of executable statements either, so this row cannot tell you whether a function can stand where these lines are. Read the two spans before acting, because the move is opposite in the two cases. Where they are statements, the ordinary answer holds: give the shared part one home and call it from each site. Where they turn out to be declarations, a literal's entries, or the cases of an enumeration, there is no call site to call anything from, and collapsing them would delete what each copy pins — a shared base type, a generated set, or one exported constant each site refers to is the move instead, and sometimes the honest answer is that there is nothing to extract at all. Reported because the copies drift apart the first time only one of them is edited, which is true whichever of those they are.
Duplicated block (30 lines × 3 locations) src/Rask.Templates/preact/client/src/app.tsx:35— src/Rask.Templates/preact/client/src/app.tsx:35 · src/Rask.Templates/react/client/src/App.tsx:39 · src/Rask.Templates/solid/client/src/App.tsx:19 — the 3 copies are spread across 3 files, and the CITED SPAN is a DECLARATION HEADER — the name, parameter list with its constraints and defaults, and base-type clause of a declaration — rather than statements inside a body. A header cannot be lifted into a helper: there is no expression position for a call to stand in, and the copies are frequently required to match, because one declaration passes its parameters straight through to the other. So the move is not extraction. Give the repeated pieces names — factor a long constraint or base-type expression into one named type both declarations refer to — and where the headers must stay identical, derive one from the other (a shared base declaration, or a single alias that spells the parameter set once) so that changing it once changes both. Where the language offers neither, treat the two as a pair that must be edited together: they drift apart the first time only one of them is changed, which is why this is reported.
Duplicated block (29 lines × 7 locations) src/Rask.Templates/angular/client/src/push.ts:20— src/Rask.Templates/angular/client/src/push.ts:20 · src/Rask.Templates/lit/client/src/push.ts:20 · src/Rask.Templates/preact/client/src/push.ts:20 · src/Rask.Templates/react/client/src/push.ts:20 · +3 more site(s) not listed — the 7 copies are spread across 7 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. There is one copy in each of 7 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 (28 lines × 2 locations) src/Rask.Server/Resources/rask.ts:1461— src/Rask.Server/Resources/rask.ts:1461 · src/Rask.Wasm/Resources/rask.wasm.ts:641 — 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 (26 lines × 2 locations) src/Rask.Wasm/Resources/rask-wasm-api.ts:302— src/Rask.Wasm/Resources/rask-wasm-api.ts:302 · src/Rask.Wasm/Resources/rask-wasm-api.ts:439 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
R10 · Code Duplication· Duplicated block with local edits (22 matched lines × 2 locations) · ×1
Duplicated block with local edits (22 matched lines × 2 locations) src/Rask.Templates/svelte/client/src/lib/Greeting.svelte:7— src/Rask.Templates/svelte/client/src/lib/Greeting.svelte:7 · src/Rask.Templates/vue/client/src/App.vue:8 — the two spans are one implementation copied and then locally edited — 134 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 (21 lines × 2 locations) src/Rask.Server/Resources/rask.ts:1955— src/Rask.Server/Resources/rask.ts:1955 · src/Rask.Wasm/Resources/rask.wasm.ts:1000 — 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 (20 lines × 7 locations) src/Rask.Templates/angular/client/public/rask-sw.js:4— src/Rask.Templates/angular/client/public/rask-sw.js:4 · src/Rask.Templates/lit/client/public/rask-sw.js:4 · src/Rask.Templates/preact/client/public/rask-sw.js:4 · src/Rask.Templates/react/client/public/rask-sw.js:4 · +3 more site(s) not listed — the 7 copies are spread across 7 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. There is one copy in each of 7 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 (19 lines × 2 locations) src/Rask.Wasm/Resources/rask-wasm-api.ts:504— src/Rask.Wasm/Resources/rask-wasm-api.ts:504 · src/Rask.Wasm/Resources/rask-wasm-api.ts:710 — 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 (16 lines × 3 locations) src/Rask.Core/Resources/browser/globals.ts:719— src/Rask.Core/Resources/browser/globals.ts:719 · src/Rask.Core/Resources/browser/globals.ts:771 · src/Rask.Core/Resources/browser/globals.ts:793 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
Duplicated block (14 lines × 7 locations) src/Rask.Core/Resources/browser/globals.ts:377— src/Rask.Core/Resources/browser/globals.ts:377 · src/Rask.Core/Resources/browser/globals.ts:444 · src/Rask.Core/Resources/rask-api.ts:64 · src/Rask.Wasm/Resources/rask-wasm-api.ts:135 · +3 more site(s) not listed — the 3 copies are spread across 3 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 (14 lines × 3 locations) src/Rask.Site/Features/Islands/React/ReactCounter.tsx:13— src/Rask.Site/Features/Islands/React/ReactCounter.tsx:13 · src/Rask.Templates/_islands/preact/Features/Islands/Preact/PreactCounter.tsx:5 · src/Rask.Templates/_islands/react/Features/Islands/React/ReactCounter.tsx:5 — the 3 copies are spread across 3 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
Duplicated block (14 lines × 2 locations) src/Rask.Wasm/Resources/rask-wasm-api.ts:366— src/Rask.Wasm/Resources/rask-wasm-api.ts:366 · src/Rask.Wasm/Resources/rask-wasm-api.ts:478 — 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 (12 matched lines × 2 locations) · ×1
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 · src/Rask.Core/Resources/rask-dom.ts:60 — 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.
Complex function morph (cyclomatic 74, cognitive 132) src/Rask.Core/Resources/rask-morph.ts:503— morph has cyclomatic complexity 74 and cognitive complexity 132; 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 serialize (cyclomatic 38, cognitive 39) src/Rask.External/extractor/extract-props.ts:499— serialize has cyclomatic complexity 38 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 applyDiff (cyclomatic 34, cognitive 71) src/Rask.Core/Resources/rask-dom.ts:158— applyDiff has cyclomatic complexity 34 and cognitive complexity 71; 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 extractIsland (cyclomatic 29, cognitive 46) src/Rask.External/extractor/extract-props.ts:231— extractIsland has cyclomatic complexity 29 and cognitive complexity 46; 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 extractAngular (cyclomatic 26, cognitive 41) src/Rask.External/extractor/extract-props.ts:1188— extractAngular has cyclomatic complexity 26 and cognitive complexity 41; 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 renderChildren (cyclomatic 26, cognitive 39) src/Rask.External/client/angular.ts:223— renderChildren 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 renderChildren (cyclomatic 25, cognitive 37) src/Rask.External/client/lit.ts:128— renderChildren has cyclomatic complexity 25 and cognitive complexity 37; 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 extractLit (cyclomatic 25, cognitive 36) src/Rask.External/extractor/extract-props.ts:941— extractLit has cyclomatic complexity 25 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 commit (cyclomatic 22, cognitive 28) src/Rask.Server/Resources/rask.ts:1496— 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 showDevError (cyclomatic 20, cognitive 21) src/Rask.Core/Resources/rask-deverror.ts:232— showDevError has cyclomatic complexity 20 and cognitive complexity 21; 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 19, cognitive 22) src/Rask.Server/Resources/rask.ts:400— onFrame has cyclomatic complexity 19 and cognitive complexity 22; 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 trackHeadAsset (cyclomatic 19, cognitive 17) src/Rask.Wasm/Resources/rask.wasm.ts:115— trackHeadAsset has cyclomatic complexity 19 and cognitive complexity 17; 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 applyManifest (cyclomatic 18, cognitive 25) src/Rask.Wasm/Resources/rask-wasm-api.ts:15— applyManifest has cyclomatic complexity 18 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.
Complex function (anonymous) (cyclomatic 18, cognitive 18) src/Rask.Core/Resources/rask-dom.ts:901— (anonymous) has cyclomatic complexity 18 and cognitive complexity 18; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive 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 raskNotePendingFormState (cyclomatic 17, cognitive 23) src/Rask.Core/Resources/rask-morph.ts:344— raskNotePendingFormState has cyclomatic complexity 17 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 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 16, cognitive 12) src/Rask.DevTools/Resources/panel/panel-client.ts:201— (anonymous) has cyclomatic complexity 16 and cognitive complexity 12; 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 15, cognitive 26) src/Rask.Server/Resources/rask-http-transport.ts:356— (anonymous) has cyclomatic complexity 15 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 handle (cyclomatic 15, cognitive 21) src/Rask.DevTools/Resources/host/bridge.ts:52— handle has cyclomatic complexity 15 and cognitive complexity 21; 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 saveRestoreFields (cyclomatic 15, cognitive 21) src/Rask.Server/Resources/rask.ts:778— saveRestoreFields has cyclomatic complexity 15 and cognitive complexity 21; 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 15, cognitive 20) src/Rask.Core/Resources/rask-events.ts:319— (anonymous) has cyclomatic complexity 15 and cognitive complexity 20; 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.
Dead file (~578 LoC) src/Rask.Spa.Hosting/client/client.ts— no import path from any entry point (50 application, 70 tooling, 54 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (src/Rask.Spa.Hosting/client/query.ts) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it
Dead file (~341 LoC) src/Rask.External/client/angular.ts— no import path from any entry point (50 application, 70 tooling, 54 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
Dead file (~271 LoC) src/Rask.Templates/analog/client/src/app/pages/analog-welcome.ts— no import path from any entry point (50 application, 70 tooling, 54 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (src/Rask.Templates/analog/client/src/app/pages/index.page.ts) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it
Dead file (~91 LoC) src/Rask.Templates/analog/client/src/app/pages/auth-form.ts— no import path from any entry point (50 application, 70 tooling, 54 test roots considered), but 2 in-repo import(s) from 2 other file(s) do name it (src/Rask.Templates/analog/client/src/app/pages/login.page.ts, src/Rask.Templates/analog/client/src/app/pages/register.page.ts) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it
Dead file (~85 LoC) src/Rask.Templates/solidstart/client/src/components/AuthForm.tsx— no import path from any entry point (50 application, 70 tooling, 54 test roots considered), but 2 in-repo import(s) from 2 other file(s) do name it (src/Rask.Templates/solidstart/client/src/routes/login.tsx, src/Rask.Templates/solidstart/client/src/routes/register.tsx) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it
Dead file (~75 LoC) src/Rask.External/client/svelte.svelte.ts— no import path from any entry point (50 application, 70 tooling, 54 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
Dead file (~72 LoC) src/Rask.Spa.Hosting/client/query.ts— no import path from any entry point (50 application, 70 tooling, 54 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
Dead file (~54 LoC) src/Rask.Core/Resources/browser/index.ts— no import path from any entry point (50 application, 70 tooling, 54 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
Dead file (~33 LoC) src/Rask.Templates/_islands/lit/Features/Islands/Lit/LitBadge.ts— no import path from any entry point (50 application, 70 tooling, 54 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
Dead file (~28 LoC) src/Rask.Templates/sveltekit/client/src/lib/AuthForm.svelte— no import path from any entry point (50 application, 70 tooling, 54 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
Dead file (~9 LoC) src/Rask.Templates/_islands/vue/Features/Islands/Vue/VueCounter.vue— no import path from any entry point (50 application, 70 tooling, 54 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
Dead file (~7 LoC) src/Rask.Templates/vue/client/src/components/HelloWorld.vue— no import path from any entry point (50 application, 70 tooling, 54 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
Dead file (~3 LoC) src/Rask.Templates/analog/client/src/server/routes/api/v1/hello.ts— no import path from any entry point (50 application, 70 tooling, 54 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
Dead file (~0 LoC) src/Rask.Templates/nuxt/client/app/app.vue— no import path from any entry point (50 application, 70 tooling, 54 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
Unlisted import 'typescript' src/Rask.External/extractor/extract-props.ts:19— Imported only as a TYPE and declared in no reachable package.json. The import is erased at compile time, so nothing is installed and no runtime resolution depends on it — but type-checking a clean clone will fail. Declare the typings it resolves through (or the package itself) in the owning package.json.
Unlisted import 'react' tests/Rask.External.Tasks.Tests/ExtractorFixtures/modules/fixture-button/index.d.ts:4— Imported only as a TYPE and declared in no reachable package.json. The import is erased at compile time, so nothing is installed and no runtime resolution depends on it — but type-checking a clean clone will fail. Declare the typings it resolves through (or the package itself) in the owning package.json.
Unused dependency 'react-colorful' — Declared in src/Rask.Site/package.json but never imported anywhere in that package or its workspace members — no static import reaches it. Usually that is dead weight and attack surface, but two shapes are indistinguishable from source and are NOT dead: an optional or native peer that another dependency loads dynamically at runtime, and a package a build, docs or test step installs and invokes separately. Confirm which of the three this is before removing it.
Unused dependency 'svelte-check' — Declared in src/Rask.Site/package.json but never imported anywhere in that package or its workspace members — no static import reaches it. Usually that is dead weight and attack surface, but two shapes are indistinguishable from source and are NOT dead: an optional or native peer that another dependency loads dynamically at runtime, and a package a build, docs or test step installs and invokes separately. Confirm which of the three this is before removing it.
Unused dependency 'vue-tsc' — Declared in src/Rask.Site/package.json but never imported anywhere in that package or its workspace members — no static import reaches it. Usually that is dead weight and attack surface, but two shapes are indistinguishable from source and are NOT dead: an optional or native peer that another dependency loads dynamically at runtime, and a package a build, docs or test step installs and invokes separately. Confirm which of the three this is before removing it.
X28 · Index access outside its own emptiness guard· Index access outside its own emptiness guard · ×1
Index access outside its own emptiness guard src/Rask.Core/Routing/LocalUrl.cs:26— This condition tests `url` for emptiness and then indexes it on a branch that test does not reach. `url[0]` is evaluated whenever the guarded half is false — which includes the case the guard exists to anticipate, `url` being empty — so an empty `url` indexes position 0 of nothing and throws. This same condition already shows the intended bracketing at line 27: `url[1]` sits INSIDE the guard. Either the guard is load-bearing, in which case this access escapes it and crashes, or `url` cannot be empty here, in which case the guard beside it is dead code — the condition is wrong under both readings. Move the parenthesis so the emptiness test brackets every access to `url`.
Duplicated predicate src/Rask.External.Tasks/FindExternalIslandsTask.cs:81— `!string.IsNullOrEmpty(path) && path.EndsWith(".cs", StringComparison.OrdinalIgnoreCase)` appears character-identically in 2 files — src/Rask.External.Tasks/FindExternalIslandsTask.cs, src/Rask.External.Tasks/FindExternalPackageIslandsTask.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:760— `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.Testing/TestFileBackend.cs:73— `metadata.TryGetProperty("ref", out var r) && r.ValueKind == JsonValueKind.String` appears character-identically in 2 files — src/Rask.Testing/TestFileBackend.cs, src/Rask.Wasm/Files/WasmFileBackend.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.Cli/Commands/DeployCommand.cs:714— `result.ExitCode == 0 && result.StandardOutput.Trim().Equals("true", StringComparison.OrdinalIgnoreCase)` appears character-identically in 2 files — src/Rask.Cli/Commands/DeployCommand.cs, src/Rask.Cli/Commands/NewCommand.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/RaskEndpointExtensions.cs:1671— `root.TryGetProperty("id", out var idEl) && idEl.ValueKind == JsonValueKind.String` appears character-identically in 2 files — src/Rask.Server/RaskEndpointExtensions.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.Server/RaskEndpointExtensions.cs:2442— `root.TryGetProperty("path", out var p) && p.ValueKind == JsonValueKind.String` appears character-identically in 2 files — src/Rask.Server/RaskEndpointExtensions.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.Server/RaskEndpointExtensions.cs:2450— `root.TryGetProperty("query", out var q) && q.ValueKind == JsonValueKind.String` appears character-identically in 2 files — src/Rask.Server/RaskEndpointExtensions.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.Server/RaskEndpointExtensions.cs:2453— `root.TryGetProperty("replace", out var rEl) && rEl.ValueKind == JsonValueKind.True` appears character-identically in 2 files — src/Rask.Server/RaskEndpointExtensions.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.Server/RaskEndpointExtensions.cs:1521— `root.TryGetProperty("type", out var t) && t.ValueKind == JsonValueKind.String` appears character-identically in 2 files — src/Rask.Server/RaskEndpointExtensions.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.
Hand-rolled JSON/XML parsing via regex src/Rask.Cli/DevTarget.cs:228— 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. This project already references a real parser; use it here too.
Hand-rolled JSON/XML parsing via regex src/Rask.Cli/DevTarget.cs:235— 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. This project already references a real parser; use it here too.
Hand-rolled JSON/XML parsing via regex src/Rask.Cli/DevTarget.cs:266— 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. This project already references a real parser; use it here too.
Hand-rolled JSON/XML parsing via regex src/Rask.Cli/DevTarget.cs:276— 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. This project already references a real parser; use it here too.
Hand-rolled JSON/XML parsing via regex src/Rask.Cli/DevTarget.cs:286— 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. This project already references a real parser; use it here too.
Hand-rolled JSON/XML parsing via regex src/Rask.Cli/Scaffolding/ProjectContext.cs:64— 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. This project already references a real parser; use it here too.
Hand-rolled JSON/XML parsing via regex src/Rask.Site/Shared/Markdown.cs:341— 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. This project already references a real parser; use it here too.
Documentation: no installation or build instructions README.md— The install section is present but terse: the one-line curl installer with prerequisites noted as optional ('Prerequisites: none. The installer adds whatever is missing') and a brief add-package command for existing projects, but no full installation/run steps. Expand to include how to set up the .NET SDK/wasm-tools/workload, run the one-command install, and verify it works (dotnet --version).
Documentation: no usage examples README.md— Usage examples are sparse: a Counter component snippet is shown but no runnable 'how to run it' example for any of the four front ends. Add a short runnable demo showing how each front end (React, Vue, Svelte, Blazor) gets started and routed via Rask.
Documentation: no installation or build instructions src/Rask.Templates/solid/README.md— The README describes how to run the Solid front end (`rask dev`) and add a message, but it omits any installation or build steps for the ASP.NET host. Add install commands for the ASP.NET project (e.g. `dotnet new`), the create-vite scaffolding, and the required Rask client NuGet reference.
Documentation: no installation or build instructions src/Rask.Templates/react/README.md— The README describes how to run the React front end (`rask dev`) and add a message but omits any installation or build steps for the ASP.NET host. Add install commands for the ASP.NET project, create-vite scaffolding, and the required Rask client NuGet reference.
Documentation: no architecture or design documentation src/Rask.Templates/react/client/README.md— The React + Vite README mentions Oxlint plugins and a recommended type-aware lint config but does not link to any architecture or design documentation. Add an 'Architecture' section describing the template's plugin ecosystem (React, SWC/oxide) so readers can find it.
IC1 · Incompleteness & stubs· Placeholder data left in code · ×5
Placeholder data left in code src/Rask.Site/Features/Elements/ElementsFormsDemo.cs:22— 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:24— 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.
Placeholder data left in code src/Rask.Site/Features/UiKit/UiKitLayoutDemo.cs:93— A placeholder e-mail address ("ada@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/RaskBatteryWiring.cs:69— 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.
Silent fallback default on parse failure src/Rask.Auth.Api/PasswordHasher.cs:278— `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.External.Tasks/WriteExternalPropsRequestTask.cs:94— `LineOf` falls back to `0` when `int.TryParse(item.GetMetadata("ModuleLine"), out var line)` 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.Generators/ComponentFactoryGenerator.cs:453— `Bit` falls back to `-1` when `bits.TryGetValue(name, out var bit)` 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.
AC7 · A11y enforcement· Accessibility enforcement below the top rung · ×1
Accessibility enforcement below the top rung — An a11y linter is configured (Documented) but there's no automated a11y test or CI gate. Add vitest-axe to verify at runtime, then gate it in CI. What was searched, so you can tell an absence from a miss: the 81 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.
Fat interface: IQueryClient (17 members) src/Rask.Query/IQueryClient.cs:19— `IQueryClient` declares 17 members under just 8 distinct name(s): `Query`, `Query`, `FetchAsync`, `PrefetchAsync`, `SendAsync`, `SendAsync`, `Command`, `Command`, `Command`, `Invalidate`, `Invalidate`, `Invalidate`, `Invalidate`, `Invalidate`, `InvalidateAll`, `SetData`, `SetData`. 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 17 separate responsibilities: a caller binds to 8 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 17 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.
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/`.
D26 · Project Cohesion· Projects may be oversized for their cohesion · ×1
Projects may be oversized for their cohesion — 3 of 120 project(s) overshoot their size bounds, lowering Project Cohesion to 9.5/10. The most over is `Rask.Core(net10.0)` (35183 LoC, 529 public types across 15 namespaces). Review these for cohesion — split a project that spans unrelated responsibilities.
D28 · Secrets (history)· Rotate the exposed credentials · ×1
DM9 · Scattered domain decisions· Rule about [HighlightMarker, SnippetMarker] decided in 2 places · ×1
Rule about [HighlightMarker, SnippetMarker] decided in 2 places — Rask.SQLite.FullTextSearchQueryInterceptor's [HighlightMarker, SnippetMarker] are judged in Rask.SQLite.FullTextSearchQueryInterceptor.Rewriter, Rask.SQLite.FullTextSearchQueryInterceptor.SearchFinder — 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.
GD1 · Unfinished & placeholder code· Placeholder literal left in code · ×1
Placeholder literal left in code src/Rask.Wasm/WasmPrerender.cs:524— A placeholder string ("[Rask.Prerender] no sitemap — set <RaskS…") is still in shipped code — typical of generated boilerplate that was never filled in.
Disabled test tests/Rask.Core.Tests/Performance/CounterAllocationPinTests.cs:48— 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.
P12 · CI test-gate honesty· Sleep-based test synchronization · ×1
Sleep-based test synchronization — 138 Task.Delay/Thread.Sleep call(s) in test code synchronize with background work by sleeping — a known flakiness precursor on slow runners. Prefer polling with a deadline or completion signals.
Logging is not universal — Only 20/47 service-like projects use logging (pure contract/DTO projects are excluded — they have nothing to log). Of those 47, 2 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 and the service already exposes health probe endpoints (healthz/livez/readyz or a container healthcheck), but no manifest in this repository wires them into readiness/liveness probes, a rolling-update strategy, lifecycle hooks or a migration job — a bad release is harder to detect and reverse. If that wiring lives in a separate ops/Helm repository, document the pointer here so release safety is evidenced.
X2 · Cancellation propagation· Not all async methods take a CancellationToken · ×1
Not all async methods take a CancellationToken — Only 372/621 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.
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.
Skipped (documented): CounterAllocation_Diagnostic_PrintDeltaBetweenShellAndInner tests/Rask.Core.Tests/Performance/CounterAllocationPinTests.cs:48— 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 378 file(s) — `.claude/skills/add-html-tag/templates/Component.cs`, `.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`, … (+373 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.
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
Run 01a0c348-9cae-72f8-b3e4-11c67f8f1c46 · 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 — 19 field(s) across 3 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: 153 · Warnings: 1050 · Recommendations: 68 · Info: 382 — Appendix A · all findings · full markdown report.
Generated by Watchdog — deterministic code-health analysis. 21-09-2026 @ 09:25 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.