Public report of rasimme/FlowBoard, published 22 October 2026. It has the same score, grades and number of
findings as the full report. The details of security findings (where they are in the code, which known
vulnerabilities and which passwords or keys were found) are left out, so nobody can use them against the project.
Public
Executive reportMeasured under the Code Assurance Index, an open standard for code quality, using its published scoring rules (rubric version 2026.10.5). Watchdog signed this survey and filed it in the standard's public register, where anyone can look it up by its survey ID. Check this survey →
Signed and filed in the standard's public register, 22 October 2026, 09:47 UTC · Survey ID cd_dbe8d51087524c13a8f47b5d9d502211
rasimme/FlowBoard
Measured 22 October 2026, 09:29 UTC, at code version 922d6e3
Test distribution is not measured: No automated tests.
Supply-chain provenance & signing is not measured: Supply-chain provenance is not scored (this pipeline releases no artifact), but its build steps or GitHub Actions workflows have integrity defects, or nothing watches its dependency set for published advisories.
CAI scoreAt riskDown 3 since the last survey
The score is built from these lenses. Each lens grades one area of the code, such as how easy it is to change or how well it is protected. The weakest lens counts most, so one weak area pulls the score down instead of being averaged away.
A medium codebase: 81,000 lines of product code in 2 projects, tests not counted · Estimated rebuild effort: about 0.5 person-years · Weakest lens: Production Readiness, 26
Findings by how serious they are
70 critical960 serious125 minor
8 dimensions are left out of the score. For each one, Watchdog either couldn't measure it in this code, or found no evidence of the safeguard it looks for, such as a tested backup restore. They count neither for nor against the score, and Limitations lists each one with its reason.
This survey was produced by
Watchdog
Producer
Canine Development
Analyzer
Watchdog engine 1.0.0
Measured
22 October 2026, 09:29 UTC
A measurement, not a certificate. The Code Assurance Index records a number
together with the evidence it was worked out from, so anyone can recalculate it, but it doesn't certify or guarantee
the code. The standard was written by Canine Development, which also builds Watchdog. It is open to any tool that
implements it, and today Watchdog is the only one that does.
A critical security finding is open, such as a library with a known critical vulnerability or a password or key found in the code. The score itself is unchanged, but its band shows At risk until the finding is fixed. See the Security and Compliance lens.
The score is deterministic, which means the same code always gets the same score. Watchdog works it out with tools that follow published rules, and an AI model never decides it, so anyone who applies the same rules to the same code gets the same number. How it is done is explained under Methodology ▸
72of 78 dimensions measured by tools. The other 6 are advisory notes from an AI model, which explain the code but don't count towards the score.
1134of 1155 findings point to an exact file and line, so you can open each one in the code. The other 21 concern the repository as a whole, such as missing documentation.
78dimensions across 7 lenses, read from 81,000 lines of product code in 2 projects.
rasimme/FlowBoard scores 36 out of 100, but it is rated At risk while a critical security finding is open; the score itself is unchanged.
The weakest lens counts most in the score, and here that is Production Readiness, which scores 26 and is rated Weak. Its Code Coverage dimension scores 0 out of 10, and until that reaches 4, Production Readiness can't be rated higher than Adequate. The first actions are to resolve the 2 Leaked secret finding(s) in Secret Scanning and to resolve the 1 No automated tests finding(s) in Code Coverage, and if Production Readiness rose to 70, the score would rise from 36 to about 44.
70 findings are critical: 37 in Keyboard semantics, 19 in Forms & labels, four in Dependency Vulnerabilities, three in ADR Conformance, two in Secret Scanning, two in Static Analysis (SAST), one in Code Coverage, one in Dependency Hygiene and one in Web-Security Posture.
Watchdog couldn't measure 7 dimensions in this code, among them Code Duplication, Internal API Consistency and Navigability, so they are left out of the score. The product code is 81,000 lines, which would take an estimated 0.5 person-years, around €69,000, to rebuild.
A lens is capped at Adequate while one of its dimensions scores below 4 out of 10, however well the rest of the lens does. That way a serious problem in one place always shows in the lens's rating.
How the score is built: what each lens counts forThe lenses don't count equally. The weakest lens counts most, the next weakest a little less, and so on, so a weak area pulls the score down instead of being averaged away. In the bar below, each part's width shows how much that lens counts and its colour shows its rating. Improving the widest part moves the score most, and as that lens improves, it counts for less, because another lens becomes the weakest.
If Production Readiness rose from 26 to 70, the lowest score rated Strong, the score would rise from 36 to about 44.
Code composition: what the lines of code are
Product code 100%
New since the last survey: 288 findings
These 288 critical or serious findings weren't in the previous survey, on 8 October 2026. The first 100 are listed here, and the findings file in the download package lists them all.
Watchdog compares every finding with the previous survey's. A finding that has only moved to another line in the same file counts as the same finding, so only new findings appear here. Advisory notes from the AI model are left out, because the model words them afresh in every survey.
Fixed since the last survey: 570 findings
These 570 critical or serious findings were in the previous survey, on 8 October 2026, and are gone from this one. The first 100 are listed here.
€23,000 to €120,000, for 382 to 1,211 hours of work, about 0.5 person-years for one engineer
Difficulty of the problem
Standard, judged from the kind of software and how it is built. Code that solves a harder problem, such as payments or medical bookings, costs more per line to write.
Quality factor
×0.7 at a score of 36. Better code takes more work to write, so the factor is ×1.0 at a score of 70, lower below it and higher above it.
Size
Medium: 81,000 lines of product code
How the estimate is made: Watchdog prices the hours a team would need to write this code again, at €60 to €95 an hour. Declarations and boilerplate are priced at a fast rate and logic at a slower one, and the logic is then multiplied by the difficulty of the problem and by the quality factor. The estimate can be about 30% off either way, and it moves most with the hourly rate and the difficulty. For this code, every line is priced as straight logic, which keeps the estimate on the low side.
Top priorities
The three actions that raise the score most for the work they take. The full ranked list is in the Roadmap.
1
Resolve the 2 Leaked secret finding(s) in Secret Scanning — start with REDACTED, REDACTED.
Raises the score by about 9 points · Low effort · Secret Scanning
2
Resolve the 1 No automated tests finding(s) in Code Coverage.
Raises the score by about 9 points · Low effort · Code Coverage
3
Resolve the 1 No tests found finding(s) in Test Distribution.
Each conclusion below combines several dimensions into one point that no single dimension shows, and lists the measurements it rests on.
Where the investment is most exposed · Value at risk
This code would cost about €69,000 to build again, about 0.5 person-years of work. Its weakest lens is Production Readiness, at 26 (Weak). Production Readiness is about whether the product is ready to run in production and to change without breaking. Because the weakest lens counts most in the score, work on Production Readiness also moves the score most.
Based on: the rebuild estimate · the Production Readiness grade · how much each lens counts
What to do: Start with the Production Readiness actions in Top priorities.
If you do one thing first · First action
Resolve the 2 Leaked secret finding(s) in Secret Scanning. Of all the actions in this report, it raises the score most for the work it takes: about 9 points for low effort, because it clears the 2 Secret Scanning findings. The next survey will show the change in the score.
Based on: the ranked actions in Top priorities, by score gain and effort
What hard-to-read code costs each year · Cost
Four dimensions measure how easy the code is to work in: two measure how tangled its logic is, one how much of it is copied, and one how well each part sticks to a single job. In this codebase they average 4.7 out of 10. Code at that level is slower to change than clean code, and Watchdog estimates the extra work at 8% to 19% on every change. The history of the code shows how much it changes: about 49,400 lines over the last 90 days, which is about 200,344 lines a year. At that pace, the extra work comes to an estimated 41.7 to 250.4 engineer-days a year, and it grows as more code changes.
How this is estimated: The number of changed lines is measured from the history of the code. The rest rests on two assumptions of Watchdog's own: code scoring 8 out of 10 or more adds no extra work, and each point below 8 adds 2.5% to 5.6% to every change; and an engineer changes 150 to 400 lines in a day. The result is a range for planning, not a measurement.
Based on: Cyclomatic Complexity · Cognitive Complexity · Cohesion (LCOM4) · the code's change history
What to do: Start with the files listed under Churn × Complexity Hotspots, which change often and are hard to read, because that is where the extra work is paid most often.
At a glance — Code Health · 38% · Weak · gated by D1, D2, R1, R2 ·
Findings mapped to OWASP categories; the specific CVEs/secrets are in the Security dimension cards below and findings.md (redacted only on the public version of this report).
OWASP category
Findings
Severity
A05:2025 — Injection
158
High / Critical
A03:2025 — Software Supply Chain Failures
5
High / Critical
A07:2025 — Authentication Failures
2
High / Critical
Roadmap
Immediately resolve the two leaked secrets in REDACTED and REDACTED to secure the codebase. Establish a testing foundation by adding automated tests for uncovered code and ensuring test distribution is functional. Implement structured logging with pino or winston across services to improve observability, and begin adopting TypeScript by adding a typecheck step to the build process.
Ranked by impact ÷ effort. "Helps" is the estimated gain on the 0–100 health score.
Do this
Helps
Effort
Dimension
Resolve the 2 Leaked secret finding(s) in Secret Scanning — start with REDACTED, REDACTED.
Adopt TypeScript for the frontend: add a typecheck step to the build, then either type-check the existing JavaScript in place (`checkJs`/JSDoc types) or convert the highest-traffic modules first — no file is typed today, so this is an adoption, not a clean-up.
Add a SAST step to CI running what this repository's stack ships: CodeQL's javascript-typescript pack, `semgrep --config=p/javascript`, or eslint-plugin-security — so a security regression fails the build instead of landing.
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 — 70
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 — 960
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 — 125
Recorded, with no effect on how the codebase functions.
Present so the survey is complete, not because it needs doing.
Could not be resolved — 8
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. 72 of 78 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 — 78 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 1155 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.
D4 Code Duplication — 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. The language model for this repository listed its production source (.html) but exposed no token stream for any of it, so nothing reached the token comparison.
D16 Bus Factor — not measured this run — This is a true statement about the repository that carries nothing for its owner to act on, so it is reported here rather than as a defect in their code. Single-maintainer repository — bus factor is not applicable (2 contributor(s) across 1120 commit(s) sampled, automation and bot accounts excluded). One of them holds 100% of the history; the other 1 hold 0% each on average, below the 5% at which there is somebody to hand the work to. That is a single maintainer with drive-by contributors, not a team whose knowledge has concentrated — so the bus factor is not applicable and there is nothing here for the owner to act on.
D22 Internal API Consistency — 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. D22 identifies the intentionally-exposed surface from `IsPackable` and `.Contracts` project names, MSBuild conventions read off the loaded project set. This target exposed no such projects, so the probe never ran; this says nothing about whether the repository has a public API. This repository commits no C#/VB source at all, so there was never an MSBuild project set to read these conventions off. That is OUR side and it is an ADMISSION gap, not an environment fault: it declares a published package (dashboard/package.json), but no published-package marker D22 reads admitted any project here. D22 DOES collect the public API of every language in this tree, and admits a project only when its manifest makes that ecosystem's publication act in a form the marker recognises — so what is missing is not a collector but an admission rule for the publication act this repository makes, if it makes one. The remedy is a better discriminator for that marker — not a collector, and no change to the scan image can close it. The marker's rules are measured to refuse applications, so one refused repository is the rule working as calibrated; several are the evidence that it is too strict. For npm the surface is what a published package.json's entry points (exports, main, module, types) export, followed through the source; an entry that names build output the tree does not commit (dist/, build/) is not followed back to source, because only a tsconfig outDir/rootDir pair states that mapping and a bundler's input lives in executable configuration this engine does not evaluate.
D27 Navigability — 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. Navigability is taken over call sites whose callee resolved. For C# that population includes calls into referenced assemblies; for this language only calls declared inside the repository count, so the abstention threshold reads the repository's use of its standard library as a resolution failure. That is a limit of this analyzer, not a build problem in this repository.
D44 Platform End-of-Life — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This dimension reads a project's own statement about the platform it runs on: a TargetFramework in a .NET project file, a .nvmrc or .python-version, a capped requires-python, a Rust toolchain file or Cargo.toml rust-version, a .go-version, .java-version, .ruby-version, .tool-versions or .sdkmanrc, a go.mod go directive, a Maven or Gradle Java level or toolchain, a Gemfile's ruby directive, a mix.exs elixir requirement, a rebar.config minimum_otp_vsn, a pubspec.yaml SDK constraint, a build.sbt scalaVersion, or a framework major pinned by a dependency constraint. This repository carries none of them, so nothing about its platform was established. That is a gap in this analyzer's coverage, NOT a finding that the platform is supported — a language whose runtime is declared elsewhere (Package.swift, a Dockerfile) is simply not read here yet.
AC4 Keyboard semantics — 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.
AX6 Interface segregation — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is computed over the public interfaces this run's compilations declare, and none was loaded, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
AXR1 Runtime accessibility — 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. Render strategy: boot via DevServer (dev). the dev server did not expose a crawlable HTTP endpoint in time — no runtime evidence.
PF3 Async & latency hygiene — 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. 28 further occurrence(s) are not listed individually; the score already reflects all 68.
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. 383 further occurrence(s) are not listed individually; the score already reflects all 423.
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. 155 further occurrence(s) are not listed individually; the score already reflects all 195.
X3 Exception handling — measured, with a gap in what it reached — Watchdog measured this, but not all of it. What it did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. 59 further occurrence(s) are not listed individually; the score already reflects all 99.
X4 Structured logging — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Java, Kotlin, Python, PHP, Dart, Ruby, Scala and Rust source only, and no C# was loaded, and this repository's JavaScript/TypeScript, Python and PHP make no call through a named logger, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
Repo exclusion declarations (.gitattributes linguist-generated/vendored, .editorconfig generated_code): none declared — every source file was scored.
Limitations & what we did not check
Watchdog assesses the repository exactly as committed, and only the repository. By design it does not reach outside the source tree: the live cloud account, the running CI/CD pipeline, the host's branch-protection and approval rules, the production configuration, or a restore actually exercised against a backup are all out of scope. That boundary is a feature, not a gap — a repo-relative, deterministic scan re-runs identically on any commit and every finding opens at a real file and line, where a live audit can neither be reproduced nor traced. The visible consequence is that controls which leave no in-repo evidence are reported as "not evidenced" and excluded from the score rather than awarded a number a static scan cannot justify.
Per-dimension blind spots
For each dimension that was measured, what a static, repo-only scan structurally cannot see — the honest edge of the measurement, not a failure of it.
D1 Cyclomatic Complexity: Cyclomatic complexity counts branches statically — it cannot tell an essential decision tree from accidental tangle, nor see complexity that lives in data or configuration (large switch-case token tables, DSL lexers/parsers, data-as-code rule tables) rather than control flow: a tokenizer's many single-character cases read as high complexity though each branch is trivial.
D2 Cognitive Complexity: Cognitive-complexity heuristics approximate how hard code is to follow; genuine domain difficulty and well-named intent that eases reading are not captured.
D3 God Classes: "God class" is sized by members and responsibilities visible in the type — a deliberately broad facade over a coherent subsystem can read the same as an accidental grab-bag. For front-end JS the file-length check is cohesion-aware (a single-responsibility module — one class/IIFE — earns a 3× threshold), but cohesion is approximated from top-level declarations, not true dependency structure.
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.
D7 Architectural Integrity: Layering is checked against detected/declared rules — an architecture whose boundaries live in convention or in code review, not in a rule a scanner can read, is not enforced here.
D8 Code Coverage: Coverage is measured by building and running the test suite inside Watchdog's isolated image — the target repo is never modified, and nothing on your systems runs. So coverage exists only when the suite builds and runs within the inline time budget; one that needs external services, can't build, or exceeds the budget yields no coverage (D8 then degrades to not-measured, not a low score). Line coverage also says nothing about assertion quality.
D9 Test Distribution: The test-pyramid shape is inferred from project/folder naming and references, with a single test host bucketed per-file by its path tier and content signals — a suite that names tiers unconventionally and gives no per-file signal can still be mis-bucketed.
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 Secret Scanning: Secret detection is signature- and entropy-based on the current tree — a secret that does not match a known pattern, or one already rotated, will not be flagged (a clean scan is "nothing matched", not "no secrets exist").
D14 License Compliance: License compatibility is checked against declared package metadata and a policy — mislabelled or missing license metadata, and obligations that depend on how you distribute, are not resolved here.
D15 Churn × Complexity Hotspots: Churn hotspots come from git history — a freshly imported or squashed repository has no churn signal, and recent rewrites can mask a historically risky file.
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.
D25 ADR Conformance: ADR conformance is the LLM-scored fraction of sampled code that follows recorded decisions — it checks the decisions that were written down and the slices it sampled, not unrecorded rules or the whole tree.
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.
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.
AC2 Forms & labels: Label association is read from static markup — a label wired up at runtime (JS-set aria-labelledby, framework-injected ids) reads as missing, a present label says nothing about whether its text is correct. A known UI-library field component (e.g. a JSX <TextField>) is now checked conservatively — flagged only when it carries NO label/aria-label/aria-labelledby/id/name — but wrapper/context-labelled libraries (Chakra/Radix FormControl+FormLabel) aren't statically visible (possible false positive) and non-JSX lowercased components are still skipped. A click handler on a plain element is now asked for a name too (it is a control the author declared), but the subtree test that answers it is deliberately generous: any DYNAMIC text expression in the subtree counts as a name, so an icon chosen by a ternary ({cond ? <IconA/> : <IconB/>}) reads as named, and a glyph component from a library the icon-import list does not know still names its parent. A clean result is "no unlabelled control found", not a labelling proof.
AC3 Page structure: Page structure is read from the static markup tree — landmarks, headings and lang injected at runtime aren't seen, heading ORDER is checked structurally (not against the rendered visual hierarchy), and lang/title/main fire only on full documents, never partials, and the data-table check sees header-cell presence (a <th> exists), not whether each header correctly associates with its cells. Static readiness, not conformance.
AC4 Keyboard semantics: Keyboard semantics are inferred from markup attributes — interactivity wired purely in script, focus managed at runtime, and component-level handlers are invisible. A clean result means "no static keyboard-trap shape", not a keyboard-operability proof.
AC5 ARIA correctness: ARIA correctness is checked against the static role/attribute shape — roles/attributes set dynamically aren't seen, a valid role says nothing about whether it matches the element's real behaviour, and required-state checks are suppressed when a JSX spread could supply them. The two-branch toggle check (a control whose state is conveyed only by which of two mutually exclusive branches renders) reads CONDITIONALS THAT ARE ATTRIBUTES — Vue v-if/v-else/v-show and Alpine x-if/x-show — so the same toggle written as a Svelte {#if} block or a JSX ternary is control flow the markup model never projects as a branch and is not seen at all.
AC6 Visual & motion safety: Contrast and motion safety are PARTIAL by construction — literal colours (hex/rgb/hsl/named) in inline styles, in-repo <style> blocks, in-repo .css files, var() tokens, Tailwind neutral utilities and CSS-in-JS top-level declarations are read (same-rule/same-element colour+background pairs only); computed/runtime/theme colour, external-CDN stylesheets, CSS-in-JS dynamic (${…}) and nested-selector colours, cross-element pairs and image contrast stay out of reach, so a clean result is bounded by what the static CSS itself shows.
AC7 A11y enforcement: Enforcement is scored from in-repo config/CI evidence only — an a11y gate enforced in external tooling with no in-repo trace can't be credited, and a configured linter is presence, not proof the rules actually run or block a merge.
AX10 Code composition: Role is inferred from namespace/folder convention, not semantics — a domain concept living in a folder named "Services" reads as application, and the split is lines-of-code, not business value. The business-logic-share score is a SOFT, FLOORED signal: it contributes to the Architecture lens but is floored at the Critical gate, so an infrastructure-heavy design (a gateway, an ETL, a driver) is legitimately low without being nuked to zero.
M4 Documentation accuracy: Onboarding quality is an LLM read of the docs/setup present — it cannot run the onboarding or measure how long a real new joiner takes; the verdict is sampled and advisory.
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, D20, D21, D25, D26, 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.
+ 178 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Bring the 19 bodies over 60 down to 60 or less in Cyclomatic Complexity — start with CanvasView.CanvasView (cyclomatic 307), DetailPanel.DetailPanel (cyclomatic 296), FilesView.FilesView (cyclomatic 173). — This score is capped by its worst body, so a finding fixed alone moves it by almost nothing — the next one down takes its place. Refactoring these 19 together lifts Cyclomatic Complexity from 2.0 to about 3.2/10, projected with the scoring formula itself and assuming each lands exactly at 60; a cleaner split scores higher.
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.
+ 218 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Bring the 29 bodies over 60 down to 60 or less in Cognitive Complexity — start with CanvasView.CanvasView (cognitive 377), DetailPanel.DetailPanel (cognitive 267), TasksView.TasksView (cognitive 183). — This score is capped by its worst body, so a finding fixed alone moves it by almost nothing — the next one down takes its place. Refactoring these 29 together lifts Cognitive Complexity from 2.0 to about 3.2/10, projected with the scoring formula itself and assuming each lands exactly at 60; a cleaner split scores higher.
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.2 / 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 27 FunctionTooLong finding(s) in God Classes — start with REDACTED (3), hzl-service.js (3), FilesView.jsx (2). — One of this dimension's main actionable groups (27 warning-level).
Resolve the 15 FileTooLong finding(s) in God Classes — start with REDACTED, hzl-service.js, TasksView.jsx. — One of this dimension's main actionable groups (15 warning-level).
Resolve the 4 ClassTooLong finding(s) in God Classes — start with REDACTED, FilesView.jsx, Sidebar.jsx. — One of this dimension's main actionable groups (4 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: 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.
What it measures: Whether the code respects its intended layering / architecture rules.
Method: Enforcement rung (Prevented/Verified/Documented) per checkable ADR via Roslyn, plus dependency cycles via the engine shared with D5/AX3. Deterministic, exact.
All 29 mechanizable ADR(s) are enforced: 19 by analyzers, 10 by tests. Dependency cycles not checked (no project-reference graph; where this repository's language has an import-cycle lens, cycles are reported there).
✓ On the Gold path — maintain.
Detailed fixes: d7_recommendation.md.
Do you agree with this assessment?
D8 · Code Coverage0.0 / 10Critical✓ Tool-verified
What it measures: How much of the code is actually exercised by tests.
Method: Coverage from coverlet runs or committed reports (Cobertura/OpenCover/lcov), computed per-file with structured exclusions for generated, trivial, and glue code. When the suite can't be built/run in-image AND no report is committed, coverage is reported NOT-MEASURED (excluded from the score) with the precondition to make it measurable — never a LoC-ratio proxy folded in as if measured. Deterministic.
No automated tests — no test code was found in this repository.
No automated tests
What to do
Resolve the 1 No automated tests finding(s) in Code Coverage. — One of this dimension's main actionable groups (1 issue-level).
Enforce Code Coverage in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Verified — provenance only; does not change the score.
Detailed fixes: d8_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D9 · Test Distribution0.0 / 10Critical✓ 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.
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.
11 outdated direct production npm dependency(ies) of 21 graded, 0 pinning defect(s), across 1 package.json (1 of them the product) and 1 committed lockfile(s). Development dependencies are deliberately not graded for currency: that grade is about what SHIPS. 0 direct dependency(ies) — production, development or optional — are marked DEPRECATED by their publisher (the registry's per-version mark, or the lockfile's copy of it when the registry could not be asked); deprecated transitive packages are listed but not charged. Whether any is UNMAINTAINED is not graded — the registry publishes no maintenance status, and release age does not stand in for one. Whether any is UNUSED is not graded either: that is a source question, and the frontend dependency lens (R8) answers it in this same run. Known CVEs in this dependency graph are D30's question, read from the manifest there.
Outdated (npm): @codemirror/lang-markdown · ×11
✓ On the Gold path — maintain.
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 2 Leaked secret finding(s) in Secret Scanning — start with REDACTED, REDACTED. — One of this dimension's main actionable groups (2 issue-level).
Enforce Secret Scanning in CI to reach Prevented (currently Verified). — Hardens enforcement from Verified 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 21 shipped npm package(s) use a banned license. Licences were resolved from registry.npmjs.org over the 21 production dependency(ies) this repository's committed lockfile resolves, across 1 product package.json manifest(s). Its 6 `devDependencies` declaration(s) are excluded: a consumer installs none of them. ★ DEPTH: this is the DIRECT production set the lockfile resolves, NOT the transitive closure — only one of the four lock dialects this pass reads states a full graph, so a banned licence pulled in only by a dependency's OWN dependencies is outside this verdict, exactly as the JVM arm's declaration-site verdict is. ★ Each licence is the one the registry publishes for the package's CURRENT release rather than for the pinned version, which is the same caveat the Hex and RubyGems arms carry. This repository publishes itself under ISC / MIT, which is its own choice and is not judged here.
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: REDACTED (70×92=6440); dashboard/src/components/DetailPanel.jsx (18×296=5328); dashboard/hzl-service.js (29×84=2436) Repeated repair below the complexity floor: dashboard/test-dashboard-api.mjs (7 of 8 changes were fixes); dashboard/src/bootstrap.js (7 of 7 changes were fixes); dashboard/test-work-state-backend.js (6 of 8 changes were fixes)
Resolve the 39 Hotspot finding(s) in Churn × Complexity Hotspots — start with REDACTED, DetailPanel.jsx, hzl-service.js. — One of this dimension's main actionable groups (39 warning-level).
Resolve the 22 Repeated repair finding(s) in Churn × Complexity Hotspots — start with test-dashboard-api.mjs, bootstrap.js, test-work-state-backend.js. — One of this dimension's main actionable groups (22 warning-level).
Detailed fixes: d15_recommendation.md · top locations in Appendix A, every location in findings.md.
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.
FlowBoard's documentation is clear and complete for its audience. The root README (project workspaces for AI agents) gives an overview, license, quick-start, and a compelling problem statement before diving into features like project context on demand, Kanban, and the Idea Canvas. The docs directory is split cleanly: the README of each subdirectory documents that directory (the docs/README.md, docs/adr/, docs/concepts/, etc.) rather than the repository, so its own scope is not judged against the root. Architecture Decision Records (ADRs) are well written with a concrete template and numbered index, covering live-inject context delivery, explicit /api/status agentId, and structural fingerprinting for snippet drift detection. The design guidelines document UI/typography, color palettes, and icons in full. The project's documentation is excellent — every ADR document (8 total) is well written with status, source, context, decision, and consequences, and the architecture/Docs markdown files are a comprehensive design repository (99). The READMEs for each directory are individually strong: they describe what the directory contains and how to use it. There are no missing-overview or missing-installation findings because every document is scoped to its own directory. This repository's documentation is excellent. The READMEs and architecture/ADR markdown files are well written: each ADR document (from ADR-0012 to ADR-016) states its scope, status, source, context, decision, consequences, and references the outline sections it covers; none of them is clipped by the scanner. The overview is present in the root README, which documents the repository as a whole rather than each directory (and does not appear to be missing installation/usage/contribution guidance).
Documentation: written for insidersdocs/design-guidelines.md
✓ On the Gold path — maintain.
Detailed fixes: d19_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D20 · ADR QualityExemplary◐ Sampled · advisory
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.
What it measures: Whether the code actually follows the decisions recorded in the project's ADRs.
Method: Judged by language model at low temperature against ADRs plus a deterministic structural code summary; findings linked to repo-rooted ADR paths for traceability. Advisory.
ADR not followed: ADR-0002: /api/status requires an explicit agentId · ×3docs/adr/0002-api-status-requires-agent-id.md
ADR not followed: ADR-0031: Canonical work state and transient stuck indicator · ×5docs/adr/0031-canonical-work-state-and-transient-indicator.md:53detected by adr-prohibition
What to do
Resolve the 3 ADR not followed finding(s) in ADR Conformance — start with 0002-api-status-requires-agent-id.md, 0003-dashboard-has-no-agent-identity.md, 0021-specify-worker-openclaw-cli.md. — One of this dimension's main actionable groups (3 issue-level).
Resolve the 5 ADR not followed finding(s) in ADR Conformance — start with 0031-canonical-work-state-and-transient-indicator.md (2), 0026-frontend-architecture-invariants.md (2), 0019-frontend-runtime-foundation.md. — One of this dimension's main actionable groups (5 recommendation-level).
Detailed fixes: d25_recommendation.md · top locations in Appendix A, every location in findings.md.
1 of 2 build units (npm) flagged as possibly oversized/incoherent.
Projects may be oversized for their cohesion
What to do
Resolve the 1 Projects may be oversized for their cohesion finding(s) in Project Cohesion. — One of this dimension's main actionable groups (1 recommendation-level).
Detailed fixes: d26_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether any secrets were ever committed — scanned across the full git history, not just now.
Method: Secret scan via TWO gitleaks detect passes in an isolated checkout — the full git history, then a second --no-git pass over the working tree as it stands — merged and de-duplicated by (rule, file, line); each match flagged High. Both invocations are recorded in the audit trail. Exhaustive; when the tool is absent, or when its output cannot be parsed into the expected shape, the dimension is WITHHELD as an explicit measurement gap on our side — unscored and excluded from the lens, never a hedged middling score.
What it measures: Real static-analysis (SAST) findings — likely security bugs in the code, any language.
Method: Polyglot static analysis via semgrep across the repo using the pinned, image-baked p/security-audit + p/owasp-top-ten rulesets (no scan-time registry fetch); severity rules (ERROR/WARNING/INFO) map to a full-band severity-weighted score. Exhaustive, deterministic; degrades on parse failure.
Coverage: semgrep pattern rules over all files — exhaustive for the rule set, blind to classes of bug without a rule (clean = no rule matched).
161 finding(s): 0 critical, 2 high, 155 medium, 4 low. semgrep hit a parse error in 4 file(s) — `dashboard/hzl-service.js`, `REDACTED`, `REDACTED`, `dashboard/test-snippets-doctor.js` — so no absence of findings in them is evidence of anything, and nothing in them was analysed. Fix the syntax error (or exclude the file deliberately) and re-scan to cover them.
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
+ 5 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Resolve the 92 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (82), REDACTED (4), REDACTED (3). — One of this dimension's main actionable groups (92 warning-level).
Resolve the 1 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
Resolve the 1 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
Detailed fixes: d29_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether any dependency has a known published vulnerability (CVE), direct or transitive, in ANY ecosystem the repository declares — Dart pub, Elixir and Erlang via Hex, Go modules, Java and Kotlin via Maven/Gradle, JavaScript/npm, .NET/NuGet, PHP/Composer, Python/PyPI, RubyGems, Rust/Cargo and Swift.
Method: Dependency-CVE scan across every ecosystem the repository declares, scored ONCE. Three sources are unioned and deduplicated by advisory identity (rule id + alias closure, CVE<->GHSA) scoped to package+version, keeping the worst severity: `osv-scanner --recursive` over osv.dev for Dart pub, Elixir/Hex (and Erlang, whose `rebar.lock` syft first converts to a CycloneDX SBOM the scanner reads, with rows attributed back to the lock), Go, Java and Kotlin via Maven/Gradle (and Scala, whose sbt build's pinned direct declarations are written into a CycloneDX SBOM the scanner reads, with rows attributed back to the build file), npm, PHP/Composer, Python/PyPI, RubyGems, Rust/Cargo and Swift; `trivy fs --scanners vuln` for npm lockfiles; and `dotnet list package --vulnerable --include-transitive` for NuGet (with per-advisory collapse of the project x target-framework fan-out), plus a DECLARED-dependency arm that resolves a published gem's gemspec against rubygems.org where no Gemfile.lock is committed. `SeverityScore(c,h,m,l, normalizer 8.0)`. NotApplicable only when NO ecosystem is readable; if any applicable ecosystem could not be scanned the findings are REPORTED and the score is withheld. Supersedes the npm and OSV arms, retired 2026-09-05.
Resolve the 3 High CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (3). — One of this dimension's main actionable groups (3 issue-level).
Resolve the 1 Critical CVE finding(s) in Dependency Vulnerabilities — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
Resolve the 1 Medium CVE finding(s) in Dependency Vulnerabilities — start with REDACTED. — One of this dimension's main actionable groups (1 warning-level).
Detailed fixes: d30_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether anyone still has living knowledge of each file, or it has been orphaned — last understood long ago by someone now gone quiet. The sibling of the bus factor: D16 asks who owns it, D34 asks whether anyone still knows it.
Method: File orphaning as total living-knowledge decay below one focused-commit's worth within a year, computed per-file from the D16 decay model. Exhaustive, deterministic over fixed history.
Every significant source file has living knowledge — recently and meaningfully worked. Counted over 283 of the 348 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 2 Change coupling finding(s) in Change Coupling — start with DetailPanel.jsx, REDACTED. — One of this dimension's main actionable groups (2 warning-level).
Detailed fixes: d35_recommendation.md · top locations in Appendix A, every location in findings.md.
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 dependency in any ecosystem this repository declares is published as malicious.
✓ On the Gold path — maintain.
Detailed fixes: d43_recommendation.md.
Do you agree with this assessment?
Frontend & cross-cutting dimensions
R = React/JS · M = Maturity · P = Readiness.
AC2 · Forms & labels5.5 / 10Adequate✓ Tool-verified
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.
A button with no text and no aria-label has no accessible name. Add visible text or an aria-label (an icon-only button still needs one). (×2) — dashboard/src/components/DetailPanel.jsx:1003, dashboard/src/components/DetailPanel.jsx:1654
This control has no associated label. Add a <label htmlFor> / wrapping <label> / aria-label / aria-labelledby so assistive tech can name it. (×2) — dashboard/src/components/DetailPanel.jsx:1014, dashboard/src/components/Sidebar.jsx:163
This UI-library field component is named only by a placeholder — a placeholder is not a label (it vanishes as soon as the user types, and many assistive technologies ignore it). Give it a real name whichever way this library supports: a label prop, an aria-label, or an id on the rendered control with a <label htmlFor> pointing at it. For a group of controls, name the group itself (aria-label, or a fieldset with a legend) — labelling each item leaves the set unnamed. (×4) — dashboard/src/components/DetailPanel.jsx:1478, dashboard/src/components/DetailPanel.jsx:1646, dashboard/src/components/SpecifyStepper.jsx:357, …
This control has only a placeholder — a placeholder is not a label (it vanishes on input and many AT ignore it). Add a <label htmlFor>, a wrapping <label>, or aria-label. (×9) — dashboard/src/components/DetailPanel.jsx:1535, REDACTED:107, REDACTED:211, …
This <span> carries a click handler, which makes it a control, and its only name is a title attribute. A plain element maps to role="generic", which does not support a name from the author, so the title is announced as nothing at all — it is a mouse-only tooltip, unreachable on touch. Give it role="button" (which it needs anyway to be operable) so the title becomes a real name, or add an aria-label. — dashboard/src/components/canvas/CanvasToolbar.jsx:132
This <path> carries a click handler, which makes it a control, but it has no text, aria-label or labelled child (the icon-only case), so assistive tech has no name to announce for it. Note that switching it to <button type="button"> — the right fix for its keyboard operability — does not give it a name either: an icon-only button still needs one. Add visible text or an aria-label. — dashboard/src/components/canvas/ConnectionLayer.jsx:110
This <span> carries a click handler, which makes it a control, but it has no text, aria-label or labelled child (the icon-only case), so assistive tech has no name to announce for it. Note that switching it to <button type="button"> — the right fix for its keyboard operability — does not give it a name either: an icon-only button still needs one. Add visible text or an aria-label. (×3) — dashboard/src/pages/TasksView.jsx:245, dashboard/src/pages/TasksView.jsx:617, dashboard/src/pages/TasksView.jsx:624
This <div> carries a click handler, which makes it a control, but it has no text, aria-label or labelled child (the icon-only case), so assistive tech has no name to announce for it. Note that switching it to <button type="button"> — the right fix for its keyboard operability — does not give it a name either: an icon-only button still needs one. Add visible text or an aria-label. — dashboard/src/pages/TasksView.jsx:1820
What to do
Give every control a programmatic label (a <label for> / wrapping <label> / aria-label) and every button text — a placeholder is not a label.
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>. — dashboard/index.html:2
What to do
Declare <html lang>, a document <title> and a <main> landmark, keep headings in order, leave zoom enabled, title iframes and drop meta-refresh.
Other · Accessibility — Whether interactive behaviour is keyboard-reachable — no click handler on a non-interactive element lacking a role, tabindex and key handler, no element the repo's own CSS styles `cursor: pointer` without giving it any of the three, no unfocusable element whose only binding is a mouse enter/leave pair or a double-click, no positive tabindex, no href-less anchor, no placeholder-href (#/javascript) link acting as a button. Static markup readiness, not a WCAG conformance claim.
Method: Static markup-model scan: click handlers on non-interactive elements lacking role+tabindex+key handler, positive tabindex values, and href-less anchors. Components skipped, spreads suppressed. Deterministic, hard fact per element.
Coverage: Population: elements that pose a keyboard-semantics question, in the PARSED MARKUP files only (.html/.htm/.cshtml/.razor/.vue/.svelte/.jsx/.tsx) — a non-natively-interactive element carrying a click handler, a double-click or hover enter/leave binding, a pointer-only gesture on a tabindex="0" element, or `cursor: pointer` from the repo's own CSS; an href-less or placeholder-href (#, javascript:) anchor; and any element with a positive tabindex. Natively interactive elements used correctly (<button>, <a href>, form controls) are NOT in the population — there is nothing to judge — so a page of nothing but correct controls gives AC4 nothing to measure. Keyboard reachability is judged from the markup, never from a rendered page. ★ An interactive element declared in a tagged-template (html`…`) or hyperscript frontend is NOT in this population — no producer reads either — so an empty population is reported as an analyzer gap, never as "this repository has no interactive elements".
This <div role="dialog"> is a modal dialog, but nothing moves focus into it when it opens and nothing keeps focus inside it while it is open, so a keyboard or screen-reader user keeps acting on the content behind it (WCAG 2.4.3). Use a native <dialog> opened with showModal(), a dialog component that traps focus, or move focus to the dialog on open, trap Tab inside it (or make the page behind inert) and return focus to the control that opened it on close. (×2) — dashboard/src/components/ActiveAgentsBar.jsx:242, dashboard/src/components/SnippetUpgrade.jsx:381
A click handler on a plain element with no role and no tabindex: even where another element's key handler can reach it, assistive tech can neither focus it nor announce what it is. Use a <button>, or add role + tabIndex={0}. (×10) — dashboard/src/components/DetailPanel.jsx:1037, dashboard/src/components/DetailPanel.jsx:1495, dashboard/src/components/DetailPanel.jsx:1580, …
A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabIndex={0} + a key handler. (×17) — dashboard/src/components/Dropdown.jsx:68, dashboard/src/components/Panel.jsx:31, dashboard/src/components/SnippetUpgrade.jsx:904, …
This <div role="dialog"> is a modal dialog, but focus is moved into it, but nothing keeps it there: Tab walks out to the page behind, so a keyboard or screen-reader user keeps acting on the content behind it (WCAG 2.4.3). Use a native <dialog> opened with showModal(), a dialog component that traps focus, or move focus to the dialog on open, trap Tab inside it (or make the page behind inert) and return focus to the control that opened it on close. — dashboard/src/components/SearchPalette.jsx:103
The repo's own CSS styles .archive-head with `cursor: pointer`, so this <div> is a control — but it has no role, no tabIndex={0} and no key handler, so it can only be reached with a mouse. Use a <button>, or add role + tabIndex={0} + a key handler. — dashboard/src/components/Sidebar.jsx:922
The repo's own CSS styles .file-row-main with `cursor: pointer`, so this <div> is a control — but it has no role, no tabIndex={0} and no key handler, so it can only be reached with a mouse. Use a <button>, or add role + tabIndex={0} + a key handler. (×6) — dashboard/src/components/SnippetUpgrade.jsx:728, dashboard/src/components/SnippetUpgrade.jsx:761, dashboard/src/components/SnippetUpgrade.jsx:791, …
This <div> binds mouse-enter and mouse-leave and nothing else — no click, no key handler, no focus handler, and no tabIndex={0}, so it cannot even take focus. A keyboard user cannot hover, so whatever the pair reveals or highlights is reachable with a mouse only. Bind the same state to focus/blur as well, and add tabIndex={0}="0" so the element can receive that focus. — dashboard/src/components/UndoToast.jsx:48
The repo's own CSS styles .conn-path with `cursor: pointer`, so this <path> is a control — but it has no role, no tabIndex={0} and no key handler, so it can only be reached with a mouse. Use a <button>, or add role + tabIndex={0} + a key handler. — dashboard/src/components/canvas/ConnectionLayer.jsx:109
This <div> binds mousedown, mouseup, mousemove and double-click — pointer gestures with no keyboard form, a double-click among them. No click, no key handler, and no tabIndex={0}, so it cannot even take focus. Nothing synthesises a double-click from the keyboard: Enter and Space fire a single click, and only on a native <button> or <a href>. So this behaviour has no keyboard path at all. Expose the same action on a real control, or add role + tabIndex={0} + a key handler alongside the double-click. — REDACTED:1282
What to do
Make custom controls keyboard-operable (role + tabindex + key handler), drop positive tabindex, and give anchors a real href.
Other · Accessibility — Whether ARIA is used correctly — valid non-abstract roles, the ARIA state a role requires, valid (non-misspelled) aria-* attribute names, in-enum values for token-typed aria-* attributes, and no aria-hidden on (or wrapping) a focusable element. Static markup readiness, not a WCAG conformance claim.
Method: Static markup-model scan: role values checked against the WAI-ARIA role set (abstract/invalid flagged), required ARIA state for a role, and aria-hidden on a focusable element. Deterministic, role/attribute level.
Coverage: Population: elements in the PARSED MARKUP files (.html/.htm/.cshtml/.razor/.vue/.svelte/.jsx/.tsx) that carry a role or an aria-* attribute; roles and token values are checked against the ARIA enums exhaustively within that set. An expression-valued (dynamic) role or aria-* value is skipped rather than guessed, and markup built in script — tagged-template (html`…`) UIs and hyperscript DOM factories — is not read at all.
Other · Accessibility — Whether focus outlines aren't removed without a replacement, motion respects prefers-reduced-motion, and literal CSS colour pairs meet contrast — PARTIAL: inline styles, in-repo <style> blocks, in-repo .css files, var() tokens, Tailwind neutral utilities and CSS-in-JS literals are read (hex/rgb/hsl/named), never computed/runtime/external-CDN colour. Static markup readiness, not a WCAG conformance claim.
Method: Static markup/CSS scan: inline outline:none/0, literal inline colour/background contrast against the 4.5:1 AA floor, and <style>-block animation without a prefers-reduced-motion guard. Deterministic but PARTIAL — only inline styles and in-repo CSS literals are visible.
Coverage: Population: styled elements in the PARSED MARKUP files (.html/.htm/.cshtml/.razor/.vue/.svelte/.jsx/.tsx), plus in-repo <style> blocks, in-repo .css files and CSS-in-JS literals. Colour contrast is computed from LITERAL colour pairs only (hex/rgb/hsl/named, including var() tokens and Tailwind neutral utilities) — computed, runtime-themed and external-CDN colour is never resolved, so this is a partial read of contrast by construction. Markup built in script — tagged-template (html`…`) UIs and hyperscript DOM factories — is not read at all.
<button> takes keyboard focus, and its outline-none utility removes the focus ring with no focus-state ring, shadow, border or outline utility in its place. Add one (e.g. focus-visible:ring-2). (×5) — dashboard/src/components/Button.jsx:41, dashboard/src/components/ClaimStateLine.jsx:135, dashboard/src/components/TrashPanel.jsx:107, …
<textarea> takes keyboard focus, and its outline-none utility removes the focus ring with no focus-state ring, shadow, border or outline utility in its place. Add one (e.g. focus-visible:ring-2). (×2) — dashboard/src/components/DetailPanel.jsx:1014, dashboard/src/components/Textarea.jsx:16
<input> takes keyboard focus, and its outline-none utility removes the focus ring with no focus-state ring, shadow, border or outline utility in its place. Add one (e.g. focus-visible:ring-2). (×3) — dashboard/src/components/DetailPanel.jsx:1535, dashboard/src/components/Input.jsx:20, dashboard/src/components/SearchBar.jsx:28
<svg> moves — its `animate-spin` utility runs with no motion-safe:/motion-reduce: variant — and nothing reads prefers-reduced-motion for it, so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Gate it on @media (prefers-reduced-motion: no-preference) or motion-safe:. — dashboard/src/components/Spinner.jsx:20
`.canvas-sidebar-textarea` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible. — dashboard/styles/canvas.css:357
`.project-item .proj-rename` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible. — dashboard/styles/dashboard.css:817
`.subtask-title-input` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible. — dashboard/styles/dashboard.css:1570
`.file-editor` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible. — dashboard/styles/dashboard.css:2027
`.file-editor:focus` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible. — dashboard/styles/dashboard.css:2040
`.note-textarea` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible. — dashboard/styles/dashboard.css:2352
`.gh-branch` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible. — dashboard/styles/overview.css:854
`.fv-pick` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible. — dashboard/styles/overview.css:1046
`.toolbar-popover` moves (`animation: toolbarPopIn 0.12s ease-out`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce. — dashboard/styles/canvas.css:179
`.canvas-sidebar` moves (`transition: transform 0.2s ease-out`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce. — dashboard/styles/canvas.css:269
`.task-card.new-card` moves (`animation: rise var(--duration-slow) var(--ease-out) both`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce. — dashboard/styles/dashboard.css:1047
`.task-card.removing` moves (`animation: shrink 0.25s var(--ease-out) forwards`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce. — dashboard/styles/dashboard.css:1050
`.stale-warning` moves (`animation: stale-pulse 2s infinite ease-in-out`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce. — dashboard/styles/dashboard.css:1215
`.priority-popover` moves (`animation: popIn var(--duration-fast) var(--ease-out)`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce. — dashboard/styles/dashboard.css:1328
`.status-popover` moves (`animation: popIn var(--duration-fast) var(--ease-out)`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce. — dashboard/styles/dashboard.css:1622
`.toast` moves (`animation: slideUp 0.25s var(--ease-out)`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce. — dashboard/styles/dashboard.css:1689
`.toast.removing` moves (`animation: slideDown 0.2s var(--ease-out) forwards`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce. — dashboard/styles/dashboard.css:1696
`.toast-spinner` moves (`animation: spin 0.8s linear infinite`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce. — dashboard/styles/dashboard.css:1700
`.spin` moves (`animation: spin 0.8s linear infinite`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce. — dashboard/styles/dashboard.css:1704
`.modal` moves (`animation: modalIn 0.2s var(--ease-out)`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce. — dashboard/styles/dashboard.css:1717
`.sidebar` moves (`transition: transform 0.25s ease, box-shadow 0.25s ease`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce. — dashboard/styles/dashboard.css:2146
`.color-popover` moves (`animation: popIn var(--duration-normal) var(--ease-out)`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce. — dashboard/styles/dashboard.css:2424
`.upgrade-modal` moves (`animation: snippetModalIn 0.22s var(--ease-out)`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce. — dashboard/styles/dashboard.css:2564
What to do
Keep a visible focus style (don't remove the outline without a replacement), guard animation with prefers-reduced-motion, and raise low-contrast colour pairs to at least 4.5:1.
Do you agree with this assessment?
AC7 · A11y enforcement4.0 / 10Weak✓ Tool-verified
Other · Accessibility — Whether accessibility is ENFORCED in the toolchain — an accessibility checker configured over the markup (an a11y lint rule set, e.g. eslint-plugin-jsx-a11y or vuejs-accessibility where the project lints JavaScript) and an automated accessibility assertion wired into tests or CI (axe/pa11y/Lighthouse or an equivalent) — on the Documented→Verified→Prevented ladder.
Method: Repo config/CI scan: an accessibility checker configured over the markup (an a11y lint rule set such as eslint-plugin-jsx-a11y / vuejs-accessibility where JavaScript is linted) and an automated accessibility assertion in tests or CI (axe/pa11y/Lighthouse or equivalent), graded on the Documented→Verified→Prevented rungs. Deterministic, presence/rung detection.
Coverage: Population: the repository's own tooling configuration — lint config, test and CI files — NOT the markup. It is read for a configured accessibility checker and an automated accessibility assertion (axe/pa11y/Lighthouse, or a native-toolkit equivalent), and it credits an INVOCATION, never a mention: a licence filename, an import comment or a doc reference earns no rung. Enforcement configured entirely outside the repository leaves no evidence here and cannot be credited.
No accessibility enforcement found — no a11y linter (eslint-plugin-jsx-a11y) and no axe/pa11y/Lighthouse in tests or CI. Start with the linter to catch issues at author time. What was searched, so you can tell an absence from a miss: the 70 markup file(s) this pass actually assessed, the linter configuration checked in beside them, and this repository's test and CI files — matched by name against the accessibility checkers this dimension carries. An audit run outside the repository, a hosted scanner, or a check whose name is not one of those, is not seen here.
What to do
Enforce accessibility in the toolchain: add eslint-plugin-jsx-a11y, then assert with your test runner's axe binding (jest-axe, vitest-axe, cypress-axe or @axe-core/playwright) in tests, then gate axe/pa11y/Lighthouse in CI.
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. On this repository the split was taken from the source tree on disk rather than from a loaded .NET workspace, so a file's role is decided by its PATH segments alone — no declared namespace was available to add to the evidence — and generated output is excluded from the census entirely rather than counted as a generated share.
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 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 dependencies point inward (Domain ← Application ← Infrastructure/Web) — the clean-architecture dependency rule, checked across the project graph.
Method: Layer violations by name-segment inference (Domain/Core to Application to Infrastructure/Web) over the project-reference graph. Exhaustive over all projects, deterministic.
Do you agree with this assessment?
C2 · Access Controls7.0 / 10Strong✓ Tool-verified
Other · Security — Whether access is authorized by default — a framework authorization attribute/decorator or policy, or imperative guard methods (throw-on-violation) called from handlers.
Method: Roslyn scan: [Authorize] usage and authorization policies, plus imperative throw-on-violation guard methods detected via syntax. Deterministic.
Authorization IS enforced here (by route guards, auth middleware or checks that refuse a caller) — this is NOT a claim that endpoints are unprotected. What's missing is a NAMED rule set: who may do what is encoded inline where it is checked, so the rules can't be listed, reviewed or tested apart from the code that applies them. Recommendation, not a defect.
What to do
Name the access rules — roles/permissions declared once (a @Roles/@Permissions decorator with its guard, a CASL ability, a casbin model, or Supabase CREATE POLICY) and consulted where access is checked, so the rule set is reviewable and testable on its own.
Other · Code Health — Unreviewed-generation residue in this repository's JavaScript/TypeScript: functions whose whole body still throws a "not implemented" error, and placeholder text (lorem ipsum, changeme/replace_me…) left in strings and JSX of 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 ("changeme") is still in shipped code — typical of generated boilerplate that was never filled in. — scripts/privacy-scan.mjs:18
What to do
Finish or delete the functions that still throw "not implemented", and replace placeholder text before shipping.
Other · Code Health — Unfinished work detected by code SHAPE, not keywords, in this repository's JavaScript/TypeScript: functions that only throw a "not implemented" error, functions that take inputs and return a constant or do nothing, async functions that never await, dead `if (false)` branches, and skeleton classes most of whose methods are holes.
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.
Maturity · Maturity — Whether the repo and its projects have a README, and whether it's substantive and current.
Method: Filesystem scan: README presence, word count, and headings for depth; git history for staleness. Exhaustive across root and project dirs, deterministic.
What to do
Explain in the README how to run the tests. Add a section called Testing to the README in the repository's top folder, saying how to run the test suite.
Add a README to the 1 of 1 project(s) that lack one — worth up to 2 pts.
Maturity · Maturity — Whether the repo is organised deliberately — src/test separation and consistent project naming.
Method: Filesystem scan: src/test folder separation and namespace-prefix consistency (majority RootNamespace agreement). Exhaustive across projects, deterministic.
What to do
Start a test surface where your build system looks for one (tests/, test/, spec/, or your ecosystem's test source set) — the separation follows from putting the first tests in the right place.
Maturity · Maturity — Whether the README actually describes the code that exists (LLM-judged, advisory).
Method: Judged by language model at low temperature: README accuracy versus actual projects, within a disclosed tolerance. Advisory, not a measured number.
README.md changes into `FlowBoard/dashboard`, but no such folder exists. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — README.md:198
README.md names `CONVENTIONS.md`, but no file or folder `CONVENTIONS.md` exists. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — README.md:423
docs/concepts/README.md names `SESSIONS.md`, but no file or folder `SESSIONS.md` exists. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — docs/concepts/README.md:38
docs/concepts/README.md names `context/specify-prompt.md`, but no file or folder `context/specify-prompt.md` exists. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — docs/concepts/README.md:109
docs/concepts/idea-canvas.md names `context/specify-prompt.md`, but no file or folder `context/specify-prompt.md` exists. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — docs/concepts/idea-canvas.md:107
docs/concepts/multi-agent-model.md names `ACTIVE-PROJECT.md`, but no file or folder `ACTIVE-PROJECT.md` exists. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — docs/concepts/multi-agent-model.md:46
docs/concepts/project-file-structure.md names `SESSIONS.md`, but no file or folder `SESSIONS.md` exists. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — docs/concepts/project-file-structure.md:5
docs/concepts/project-file-structure.md names `ACTIVE-PROJECT.md`, but no file or folder `ACTIVE-PROJECT.md` exists. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — docs/concepts/project-file-structure.md:17
docs/concepts/snippet-doctor.md names `BOOT.md`, but no file or folder `BOOT.md` exists. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — docs/concepts/snippet-doctor.md:5
docs/concepts/specify-workflow.md names `context/specify-prompt.md`, but no file or folder `context/specify-prompt.md` exists. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — docs/concepts/specify-workflow.md:21
docs/concepts/specify-workflow.md names `context/specify-spec-template.md`, but no file or folder `context/specify-spec-template.md` exists. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — docs/concepts/specify-workflow.md:157
docs/project-mode/agent-bridge.md names `SESSIONS.md`, but no file or folder `SESSIONS.md` exists. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — docs/project-mode/agent-bridge.md:66
docs/project-mode/compliance.md names `BOOTSTRAP.md`, but no file or folder `BOOTSTRAP.md` exists. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — docs/project-mode/compliance.md:65
docs/project-mode/error-handling.md names `ACTIVE-PROJECT.md`, but no file or folder `ACTIVE-PROJECT.md` exists. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — docs/project-mode/error-handling.md:13
docs/project-mode/error-handling.md names `_index.md`, but no file or folder `_index.md` exists. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — docs/project-mode/error-handling.md:13
docs/project-mode/hzl.md names `SESSIONS.md`, but no file or folder `SESSIONS.md` exists. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — docs/project-mode/hzl.md:70
docs/project-mode/hzl.md names `.pre-db.bak`, but no file or folder `.pre-db.bak` exists. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — docs/project-mode/hzl.md:73
docs/project-mode/hzl.md names `_index.md`, but no file or folder `_index.md` exists. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — docs/project-mode/hzl.md:79
docs/project-mode/hzl.md names `ACTIVE-PROJECT.md`, but no file or folder `ACTIVE-PROJECT.md` exists. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — docs/project-mode/hzl.md:79
docs/project-mode/key-principles.md names `ACTIVE-PROJECT.md`, but no file or folder `ACTIVE-PROJECT.md` exists. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — docs/project-mode/key-principles.md:20
docs/project-mode/key-principles.md names `_index.md`, but no file or folder `_index.md` exists. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — docs/project-mode/key-principles.md:20
docs/project-mode/key-principles.md names `SESSION-STATE.md`, but no file or folder `SESSION-STATE.md` exists. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — docs/project-mode/key-principles.md:20
docs/project-mode/key-principles.md names `SESSIONS.md`, but no file or folder `SESSIONS.md` exists. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — docs/project-mode/key-principles.md:46
docs/project-mode/project-files.md names `SESSIONS.md`, but no file or folder `SESSIONS.md` exists. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — docs/project-mode/project-files.md:12
docs/project-mode/project-files.md names `.pre-db.bak`, but no file or folder `.pre-db.bak` exists. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — docs/project-mode/project-files.md:14
docs/project-mode/specify-workflow.md names `specify-prompt.md`, but no file or folder `specify-prompt.md` exists. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — docs/project-mode/specify-workflow.md:5
docs/project-mode/tasks-api.md names `_index.md`, but no file or folder `_index.md` exists. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — docs/project-mode/tasks-api.md:12
docs/project-mode/tasks-api.md names `SESSIONS.md`, but no file or folder `SESSIONS.md` exists. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — docs/project-mode/tasks-api.md:257
docs/reference/env-vars.md names `ACTIVE-PROJECT.md`, but no file or folder `ACTIVE-PROJECT.md` exists. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — docs/reference/env-vars.md:39
docs/guide/how-to/browse-and-edit-files.md names `SESSIONS.md`, but no file or folder `SESSIONS.md` exists. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — docs/guide/how-to/browse-and-edit-files.md:7
docs/guide/reference/widget-catalog.md names `context/NOTES.md`, but no file or folder `context/NOTES.md` exists. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — docs/guide/reference/widget-catalog.md:52
docs/project-mode/legacy/PROJECT-RULES.md names `SESSIONS.md`, but no file or folder `SESSIONS.md` exists. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — docs/project-mode/legacy/PROJECT-RULES.md:10
docs/project-mode/legacy/PROJECT-RULES.md names `BOOTSTRAP.md`, but no file or folder `BOOTSTRAP.md` exists. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — docs/project-mode/legacy/PROJECT-RULES.md:20
docs/project-mode/legacy/PROJECT-RULES.md names `ACTIVE-PROJECT.md`, but no file or folder `ACTIVE-PROJECT.md` exists. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — docs/project-mode/legacy/PROJECT-RULES.md:33
docs/reference/api/discovery.md documents `GET /api/projects/:name/export[?includeHistory=true]`, but no route, string or file in the code carries the segment `export[`. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — docs/reference/api/discovery.md:122
docs/reference/api/projects.md names `SESSIONS.md`, but no file or folder `SESSIONS.md` exists. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — docs/reference/api/projects.md:59
What to do
Reconcile the README with reality: README.md changes into `FlowBoard/dashboard`, but no such folder exists; README.md names `CONVENTIONS.md`, but no file or folder `CONVENTIONS.md` exists; docs/concepts/README.md names `SESSIONS.md`, but no file or folder `SESSIONS.md` exists; docs/concepts/README.md names `context/specify-prompt.md`, but no file or folder `context/specify-prompt.md` exists; docs/concepts/idea-canvas.md names `context/specify-prompt.md`, but no file or folder `context/specify-prompt.md` exists.
Readiness · Readiness — Whether an automated pipeline builds and tests every change.
Method: Filesystem scan: CI workflow files (.github/workflows, .gitlab-ci.yml, etc.) for build and test stages. Exhaustive, deterministic.
Do you agree with this assessment?
P10 · Library API & versioning10.0 / 10Exemplary○ Nothing flagged
Readiness · Readiness — For a library: a deliberate (small) public API surface and explicit semantic versioning so consumers can depend on it safely.
Method: Roslyn scan: public API surface area and semantic-versioning markers (SemVer attributes, changelog entries) for libraries; off .NET, a library is the ecosystem's publication act (an npm package that is not private and names an entry point, a PyPI distribution with a build system, a Rust library crate, a Maven/Gradle module that publishes, a Go module with no package main, a gemspec, a Composer library, a SwiftPM library product, a pub.dev or Hex package), its surface is the share of types the language model records as public (Rust, Swift, Java, Kotlin, Go, Dart; not measured where the model records no type visibility or, as in TypeScript, only module-level export), and its version is read from the manifest, a semver CHANGELOG, release tooling or semver git tags. Exhaustive, deterministic.
Do you agree with this assessment?
P2 · Observability1.0 / 10Critical✓ Tool-verified
Readiness · Readiness — Whether the code is diagnosable in production — structured logging, tracing/metrics, health checks.
No logging call was found in the 338 JavaScript/TypeScript production file(s) this check read across 2 module(s). Each was searched for its ecosystem's logging libraries (JavaScript/TypeScript: pino, winston, bunyan, log4js, loglevel, consola, the NestJS Logger) and for a call on a receiver named `log`/`logger` (or ending in `Logger`/`_logger`) with a level verb. It cannot see logging through a repo-local wrapper named otherwise, or in source it did not read — this is 'no logging found by this walk', not a verdict that nothing here logs. If it is right, production issues will be hard to diagnose.
What to do
Adopt pino (or winston) and log at meaningful points in the services you run.
Add OpenTelemetry tracing/metrics (@opentelemetry/sdk-node) so requests are traceable across the system, not just health-probable.
Readiness · Readiness — Whether SAST, secret/dependency scanning and performance benchmarking are wired in (presence, not runtime).
Method: Filesystem scan: SAST configuration, dependency-update automation, secret scanning, and a benchmark harness or benchmark step — in this repository's own ecosystem. Exhaustive, deterministic.
No static application security testing detected. For this repository's stack, add CodeQL's javascript-typescript pack, `semgrep --config=p/javascript`, or eslint-plugin-security as a CI step. What was searched, so you can tell an absence from a miss: the 2483 CI workflow file(s) in this repository, and the scanner and linter configuration checked in beside them. A scan that runs outside CI, one configured in your forge's web UI rather than in a committed file, or a tool whose name is none of those this check carries, is not seen — if that is your case the row is wrong, and saying so is more useful than adding a second scanner.
What to do
Add a SAST step to CI running what this repository's stack ships: CodeQL's javascript-typescript pack, `semgrep --config=p/javascript`, or eslint-plugin-security — so a security regression fails the build instead of landing.
Add gitleaks/trufflehog in CI to block PRs that introduce committed secrets.
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).
Readiness · Readiness — Whether outbound HTTP calls are wrapped in resilience (retry/timeout/circuit-breaker) so a failing dependency doesn't cascade.
Method: Source scan: outbound HTTP clients and what bounds them — resilience handlers (Polly, AddStandardResilienceHandler) on .NET; on Go, the JVM, Python, JavaScript/TypeScript, Ruby, PHP, Rust, Elixir, Swift, Dart and Erlang, a timeout, deadline, retry or breaker beside each call, or a process-wide client default (a framework-wide deadline such as Drupal core's, Laravel's or actix's awc counts). Exhaustive, deterministic.
`fetch(` makes an outbound HTTP call, and nothing bounds it: no timeout, deadline, retry or circuit breaker is set for it here, and the client has no process-wide default. A slow or failing dependency will hold this service's request, thread or connection until the call gives up on its own — or never, for a client with no default timeout. (×4) — dashboard/github.js:36, dashboard/scripts/migrate-canvas-to-db.mjs:44, dashboard/tools/ov-audit.mjs:12, …
`fetchImpl(` makes an outbound HTTP call, and nothing bounds it: no timeout, deadline, retry or circuit breaker is set for it here, and the client has no process-wide default. A slow or failing dependency will hold this service's request, thread or connection until the call gives up on its own — or never, for a client with no default timeout. (×6) — dashboard/src/utils/appUpdate.mjs:32, dashboard/src/utils/appUpdate.mjs:54, dashboard/src/utils/appUpdate.mjs:91, …
What to do
Bound every outbound call: pass `signal: AbortSignal.timeout(ms)` to `fetch`, set `timeout` on the axios instance (`axios.create({ timeout })`), and add retries with back-off (`axios-retry`, `p-retry`) and a breaker (`opossum`, `cockatiel`) around dependencies that fail.
Readiness · Performance — Whether asynchronous code stays responsive — it avoids sync-over-async blocking (a .NET .Wait()/.GetAwaiter().GetResult(), a time.sleep or blocking HTTP call inside a Python coroutine, a *Sync call inside an async JavaScript function, block_on inside a Rust async fn, runBlocking inside a Kotlin suspend function, block() inside a Reactor publisher) that stalls a thread or event loop and risks deadlock, and, where the code is a reusable library on .NET, awaits with ConfigureAwait(false) so it never captures and stalls its caller's context.
Method: Production-source scan: sync-over-async blocking counted everywhere — .Wait()/.GetAwaiter().GetResult() in .NET; off .NET, read from the language model, a blocking call inside an async function (Python, TS/JS, Rust, Kotlin, Swift, Dart) or inside a Java method returning a Reactor Mono/Flux or a Scala method returning a Future or effect — and, for a .NET library with ≥5 awaits, the share of awaits using ConfigureAwait(false). Deterministic, syntax/text detection.
`fs.existsSync` in `init` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. (×2) — dashboard/hzl-service.js:542, dashboard/hzl-service.js:557
`fs.mkdirSync` in `init` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. — dashboard/hzl-service.js:542
`fs.chmodSync` in `init` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. — dashboard/hzl-service.js:557
`fs.existsSync` in `importBundle` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. (×2) — dashboard/project-bundle-import.js:929, dashboard/project-bundle-import.js:956
`fs.rmSync` in `importBundle` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. (×2) — dashboard/project-bundle-import.js:929, dashboard/project-bundle-import.js:957
`fs.existsSync` in `app.get("/")` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. — REDACTED:612
`fs.readFileSync` in `app.get("/")` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. — REDACTED:622
`fs.existsSync` in `app.get("/*path")` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. — REDACTED:648
`fs.statSync` in `app.get("/*path")` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. — REDACTED:648
`fs.readFileSync` in `app.get("/*path")` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. — REDACTED:653
`fs.readFileSync` in `app.get("/api/info")` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. — REDACTED:1459
`fs.existsSync` in `app.put("/api/projects/:name/tasks/:id")` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. — REDACTED:2899
`fs.statSync` in `app.put("/api/projects/:name/tasks/:id")` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. — REDACTED:2899
`fs.existsSync` in `app.delete("/api/projects/:name/tasks/:id")` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. — REDACTED:3191
`fs.unlinkSync` in `app.delete("/api/projects/:name/tasks/:id")` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. — REDACTED:3191
`fs.statSync` in `app.get("/api/projects/:name/files/{*filePath}")` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. (×2) — REDACTED:3386, REDACTED:3390
`fs.readFileSync` in `app.get("/api/projects/:name/files/{*filePath}")` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. — REDACTED:3396
`fs.existsSync` in `app.put("/api/projects/:name/files/{*filePath}")` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. — REDACTED:3438
`fs.mkdirSync` in `app.put("/api/projects/:name/files/{*filePath}")` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. — REDACTED:3438
`fs.writeFileSync` in `app.put("/api/projects/:name/files/{*filePath}")` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. — REDACTED:3440
`fs.statSync` in `app.put("/api/projects/:name/files/{*filePath}")` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. — REDACTED:3441
`fs.mkdirSync` in `app.post("/api/projects/:name/files/context")` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. — REDACTED:3492
`fs.writeFileSync` in `app.post("/api/projects/:name/files/context")` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. — REDACTED:3493
`fs.statSync` in `app.post("/api/projects/:name/files/context")` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. — REDACTED:3494
`fs.existsSync` in `app.delete("/api/projects/:name/files/{*filePath}")` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. — REDACTED:3528
`fs.statSync` in `app.delete("/api/projects/:name/files/{*filePath}")` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. — REDACTED:3532
`fs.unlinkSync` in `app.delete("/api/projects/:name/files/{*filePath}")` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. — REDACTED:3537
`fs.existsSync` in `app.post("/api/projects/:name/specs/:taskId")` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. — REDACTED:3569
`fs.statSync` in `app.post("/api/projects/:name/specs/:taskId")` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. — REDACTED:3569
`fs.readFileSync` in `app.post("/api/projects/:name/sessions")` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. — REDACTED:3611
`fs.writeFileSync` in `app.post("/api/projects/:name/sessions")` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. — REDACTED:3616
`fs.mkdirSync` in `startServer` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. — REDACTED:5193
`fs.readdirSync` in `startServer` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. — REDACTED:5302
`fs.existsSync` in `callback to some` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. — REDACTED:5303
`fs.mkdtempSync` in `run` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. — dashboard/test-canvas-promote-integration.js:109
`fs.mkdirSync` in `run` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. — dashboard/test-canvas-promote-integration.js:112
What to do
TypeScript/JavaScript: use the promise APIs (fs/promises, a promisified child_process.execFile, the async zlib/crypto functions) and await them instead of the *Sync variants.
Do you agree with this assessment?
R1 · Type Safety0.0 / 10Critical✓ 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.
0 typed · 357 plain JS — the untyped files are dashboard/agent-identity.js, dashboard/audit-log.js, dashboard/bundle-freshness.js, dashboard/canvas-placement.js, dashboard/content-hygiene-doctor.js, dashboard/dashboard-snapshot.js (+351 more).
What to do
Adopt TypeScript for the frontend: add a typecheck step to the build, then either type-check the existing JavaScript in place (`checkJs`/JSDoc types) or convert the highest-traffic modules first — no file is typed today, so this is an adoption, not a clean-up.
React / JS · Code Health — Near-exact copy-pasted blocks of substantial extent across the frontend (the D4 clone algorithm over JS/TS tokens, D-386): a block is reported only where its copies still agree on most of their own identifiers and literals, or were renamed as they were pasted but kept most of their constants, and where the copies carry enough code to stand on their own or the copied extent reaches 30 lines — so a re-implementation sharing neither names nor values, and a small pasted declaration, are both found and deliberately not reported, and a clean R10 is not a claim that nothing was copied.
Method: Near-exact copy-pasted blocks of substantial extent across the frontend (the D4 clone algorithm run over JS/TS tokens). Masking finds the candidates; a block is reported when its copies still agree on most of their own identifiers and literals, or when a renamed copy still agrees on most of its constants, AND the copies carry enough code to stand on their own — or when the copied extent reaches 30 lines. So a re-implementation sharing neither names nor values, and a small pasted declaration, are deliberately not counted. Deterministic.
13 duplicated blocks under dashboard/src/ have copies in at least two of the sibling directories components, context, pages, state, utils — 8 of them are reported below, and 5 are counted here but not reported individually: those copies match on shape but no longer clear R10's bar for an individually reported row — either they kept neither their own names nor their values, or what was copied is too small to stand on its own (it reports near-exact duplication only, and only of substantial extent). What this row states is the concentration, which the detector measured over all 13 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 13 local ones: the siblings replicate behaviour none of them owns, which is the shape of a missing shared module — a common library every sibling imports — rather than 13 separate extractions. Check first whether the siblings are deliberately standalone deliverables (scaffold templates, demo apps that must stay copy-pasteable); where they are, the duplication is the design and the per-block rows are the ones to act on. — dashboard/src/components/Sidebar.jsx:491
REDACTED:15 · REDACTED:18 — the two spans are one implementation copied and then locally edited — 924 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — REDACTED:15
dashboard/test-canvas-dblclick.js:31 · dashboard/test-canvas-links.js:38 — the two spans are one implementation copied and then locally edited — 982 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. — dashboard/test-canvas-dblclick.js:31
dashboard/test-canvas-dblclick.js:221 · dashboard/test-canvas-links.js:221 — the two spans are one implementation copied and then locally edited — 904 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. — dashboard/test-canvas-dblclick.js:221
dashboard/test-canvas-db-drift.js:32 · dashboard/test-canvas-db-import.js:23 — the two spans are one implementation copied and then locally edited — 925 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. — dashboard/test-canvas-db-drift.js:32
dashboard/test-specify-e2e-complex.js:10 · dashboard/test-specify-e2e-simple.js:10 — the 2 copies sit in sibling files in one directory, so check first whether one of them (or an existing module there) already owns this behaviour and the others should call it; otherwise extract it into one module in that directory and have each site call it. — dashboard/test-specify-e2e-complex.js:10
dashboard/test-specify-api-confirm.js:41 · dashboard/test-specify-failure-scenarios.js:39 — the two spans are one implementation copied and then locally edited — 652 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. — dashboard/test-specify-api-confirm.js:41
scripts/capture-v5-gif.mjs:15 · scripts/capture-v5-screenshots.mjs:7 — the two spans are one implementation copied and then locally edited — 903 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. — scripts/capture-v5-gif.mjs:15
dashboard/test-canvas-promote-integration.js:104 · dashboard/test-canvas-promote-stepper-visible.js:59 — the two spans are one implementation copied and then locally edited — 567 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. — dashboard/test-canvas-promote-integration.js:104
dashboard/test-setup-linux-systemd.mjs:493 · dashboard/test-setup-linux-systemd.mjs:574 — the two spans are one implementation copied and then locally edited — 470 tokens are still identical, in the same order in both spans, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — dashboard/test-setup-linux-systemd.mjs:493
dashboard/test-search-api.js:10 · dashboard/test-task-move-reparent.js:10 — the 2 copies sit in sibling files in one directory, so check first whether one of them (or an existing module there) already owns this behaviour and the others should call it; otherwise extract it into one module in that directory and have each site call it. — dashboard/test-search-api.js:10
dashboard/test-specify-api-answer.js:9 · dashboard/test-specify-api-next.js:9 — the 2 copies sit in sibling files in one directory, so check first whether one of them (or an existing module there) already owns this behaviour and the others should call it; otherwise extract it into one module in that directory and have each site call it. — dashboard/test-specify-api-answer.js:9
dashboard/test-structure-review-retire.js:25 · dashboard/test-t458-spec-on-create.js:20 — the 2 copies sit in sibling files in one directory, so check first whether one of them (or an existing module there) already owns this behaviour and the others should call it; otherwise extract it into one module in that directory and have each site call it. — dashboard/test-structure-review-retire.js:25
dashboard/test-handoff-package.js:74 · dashboard/test-handoff-package.js:184 — the two spans are one implementation copied and then locally edited — 263 tokens are still identical, in the same order in both spans, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — dashboard/test-handoff-package.js:74
dashboard/test-canvas-promote-integration.js:12 · dashboard/test-canvas-promote-stepper-visible.js:12 — the 2 copies sit in sibling files in one directory, so check first whether one of them (or an existing module there) already owns this behaviour and the others should call it; otherwise extract it into one module in that directory and have each site call it. — dashboard/test-canvas-promote-integration.js:12
dashboard/test-canvas-create-task-smoke.js:16 · dashboard/test-canvas-db-endpoints.js:23 — the 2 copies sit in sibling files in one directory, so check first whether one of them (or an existing module there) already owns this behaviour and the others should call it; otherwise extract it into one module in that directory and have each site call it. — dashboard/test-canvas-create-task-smoke.js:16
dashboard/test-agent-delete-guard.js:19 · dashboard/test-destructive-confirmation.js:17 · dashboard/test-task-archive-errors.js:16 — the 3 copies sit in sibling files in one directory, so check first whether one of them (or an existing module there) already owns this behaviour and the others should call it; otherwise extract it into one module in that directory and have each site call it. There is one copy in each of 3 separate files rather than several in one place, so check first whether these are sibling modules that each declare their own version of one shape — one per entity, per provider, per language. Where they are, no single extracted module collapses them: each module still has to be written, and what recurs is the TEMPLATE. The moves that do collapse a template are to generate these modules from the set they enumerate, or to replace the repeated construction with one factory each site calls with its own values — and where the set is the point, each module pinning one distinct thing, the repetition IS the enumeration and there is nothing to delete. — dashboard/test-agent-delete-guard.js:19
dashboard/github.js:52 · dashboard/github.js:121 — the two spans are one implementation copied and then locally edited — 366 tokens are still identical, in the same order in both spans, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — dashboard/github.js:52
REDACTED:4089 · REDACTED:4238 — 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. — REDACTED:4089
REDACTED:23 · REDACTED:24 — the two spans are one implementation copied and then locally edited — 283 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — REDACTED:23
dashboard/test-canvas-browser-smoke.js:81 · dashboard/test-canvas-dblclick.js:289 · dashboard/test-canvas-links.js:338 — 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. — dashboard/test-canvas-browser-smoke.js:81
dashboard/test-dashboard-api.mjs:39 · dashboard/test-dashboard-race-regressions-e2e.js:30 — the two spans are one implementation copied and then locally edited — 149 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. — dashboard/test-dashboard-api.mjs:39
REDACTED:1171 · REDACTED:29 — the two spans are one implementation copied and then locally edited — 348 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — REDACTED:1171
dashboard/test-snippets-doctor.js:203 · dashboard/test-snippets-doctor.js:828 — the two spans are one implementation copied and then locally edited — 268 tokens are still identical, in the same order in both spans, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — dashboard/test-snippets-doctor.js:203
dashboard/test-app-state-bridge.mjs:35 · dashboard/test-dashboard-api.mjs:43 — the two spans are one implementation copied and then locally edited — 140 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. — dashboard/test-app-state-bridge.mjs:35
dashboard/test-handoff-endpoint.js:20 · dashboard/test-kanban-subtask-state.js:16 — the two spans are one implementation copied and then locally edited — 357 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. — dashboard/test-handoff-endpoint.js:20
dashboard/test-specify-e2e-chat-origin.js:27 · dashboard/test-specify-e2e-complex.js:32 · dashboard/test-specify-e2e-simple.js:32 — the 3 copies sit in sibling files in one directory, so check first whether one of them (or an existing module there) already owns this behaviour and the others should call it; otherwise extract it into one module in that directory and have each site call it. There is one copy in each of 3 separate files rather than several in one place, so check first whether these are sibling modules that each declare their own version of one shape — one per entity, per provider, per language. Where they are, no single extracted module collapses them: each module still has to be written, and what recurs is the TEMPLATE. The moves that do collapse a template are to generate these modules from the set they enumerate, or to replace the repeated construction with one factory each site calls with its own values — and where the set is the point, each module pinning one distinct thing, the repetition IS the enumeration and there is nothing to delete. — dashboard/test-specify-e2e-chat-origin.js:27
dashboard/test-canvas-db-endpoints.js:53 · dashboard/test-canvas-db-import.js:48 — 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. — dashboard/test-canvas-db-endpoints.js:53
dashboard/test-content-hygiene-api.js:17 · dashboard/test-task-description.js:15 — 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. — dashboard/test-content-hygiene-api.js:17
dashboard/test-momentum-bytype.js:15 · dashboard/test-task-entered-status.js:12 — the two spans are one implementation copied and then locally edited — 411 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. — dashboard/test-momentum-bytype.js:15
dashboard/test-work-state-e2e.js:178 · dashboard/test-work-state-poll-race-e2e.js:170 — the two spans are one implementation copied and then locally edited — 299 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. — dashboard/test-work-state-e2e.js:178
dashboard/src/components/SnippetUpgrade.jsx:777 · dashboard/src/components/SnippetUpgrade.jsx:807 · dashboard/src/components/SnippetUpgrade.jsx:837 — all 3 copies are in the same file, and the SHAPE of this repetition could not be determined. It is not a run of declarations, a listing, a declaration header, a type body or a slice through a construct — and it was not measured as a run of executable statements either, so this row cannot tell you whether a function can stand where these lines are. Read the two spans before acting, because the move is opposite in the two cases. Where they are statements, the ordinary answer holds: give the shared part one home and call it from each site. Where they turn out to be declarations, a literal's entries, or the cases of an enumeration, there is no call site to call anything from, and collapsing them would delete what each copy pins — a shared base type, a generated set, or one exported constant each site refers to is the move instead, and sometimes the honest answer is that there is nothing to extract at all. Reported because the copies drift apart the first time only one of them is edited, which is true whichever of those they are. — dashboard/src/components/SnippetUpgrade.jsx:777
dashboard/test-canvas-create-task-smoke.js:72 · dashboard/test-canvas-promote-integration.js:118 · dashboard/test-canvas-promote-stepper-visible.js:70 — the 3 copies sit in sibling files in one directory, so check first whether one of them (or an existing module there) already owns this behaviour and the others should call it; otherwise extract it into one module in that directory and have each site call it. There is one copy in each of 3 separate files rather than several in one place, so check first whether these are sibling modules that each declare their own version of one shape — one per entity, per provider, per language. Where they are, no single extracted module collapses them: each module still has to be written, and what recurs is the TEMPLATE. The moves that do collapse a template are to generate these modules from the set they enumerate, or to replace the repeated construction with one factory each site calls with its own values — and where the set is the point, each module pinning one distinct thing, the repetition IS the enumeration and there is nothing to delete. — dashboard/test-canvas-create-task-smoke.js:72
dashboard/test-work-state-e2e.js:109 · dashboard/test-work-state-poll-race-e2e.js:114 — the two spans are one implementation copied and then locally edited — 242 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. — dashboard/test-work-state-e2e.js:109
REDACTED:2120 · REDACTED:2227 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — REDACTED:2120
dashboard/test-file-endpoints-security.js:27 · dashboard/test-project-delete-guard.js:32 — the two spans are one implementation copied and then locally edited — 303 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. — dashboard/test-file-endpoints-security.js:27
dashboard/test-specify-clarify-regression.js:92 · dashboard/test-specify-e2e-complex.js:80 · dashboard/test-specify-e2e-simple.js:80 — 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. — dashboard/test-specify-clarify-regression.js:92
dashboard/test-heal-project.js:306 · dashboard/test-hzl-integrity.js:211 — 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. — dashboard/test-heal-project.js:306
dashboard/test-setup-linux-systemd.mjs:21 · dashboard/test-setup-macos-launchd.mjs:24 — the 2 copies sit in sibling files in one directory, so check first whether one of them (or an existing module there) already owns this behaviour and the others should call it; otherwise extract it into one module in that directory and have each site call it. — dashboard/test-setup-linux-systemd.mjs:21
dashboard/test-t168-t177-integration.js:30 · dashboard/test-v5-integration.js:21 — the 2 copies sit in sibling files in one directory, so check first whether one of them (or an existing module there) already owns this behaviour and the others should call it; otherwise extract it into one module in that directory and have each site call it. — dashboard/test-t168-t177-integration.js:30
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 · Architecture — Conformance to the detected frontend architecture layout (feature-sliced / layered src) plus cross-package deep-import rules (D-386).
Method: Conformance to the detected frontend layout (feature-sliced / layered src) plus cross-package deep-import rules, over the module graph. Deterministic.
dashboard/test-project-context-retry.mjs:7 reaches into another package with a relative path (../hooks/project-context/handler.js) — import the package by name instead. — dashboard/test-project-context-retry.mjs:7
What to do
Fix the listed violations: import through public entries (package exports / slice index), never reach into another layer or package's internals.
React / JS · Code Health — Per-function cyclomatic/cognitive complexity from the token-level function scanner (D-386) — real branching, not a regex heuristic.
Method: Per-function cyclomatic/cognitive complexity from a token-level function scanner (real branching, not a regex heuristic), computed over every frontend function. Deterministic.
(anonymous) has cyclomatic complexity 93 and cognitive complexity 131; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — REDACTED:2875
UpgradeModal has cyclomatic complexity 93 and cognitive complexity 85; 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. — dashboard/src/components/SnippetUpgrade.jsx:152
updateTask has cyclomatic complexity 82 and cognitive complexity 121; 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. — dashboard/hzl-service.js:1431
(anonymous) has cyclomatic complexity 76 and cognitive complexity 107; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — REDACTED:2702
DetailPanel has cyclomatic complexity 75 and cognitive complexity 62; 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. — dashboard/src/components/DetailPanel.jsx:182
run has cyclomatic complexity 69 and cognitive complexity 55; 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. — dashboard/test-canvas-db-import.js:92
run has cyclomatic complexity 64 and cognitive complexity 50; 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. — dashboard/test-overview-api.js:30
SpecifyStepper has cyclomatic complexity 63 and cognitive complexity 59; 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. — dashboard/src/components/SpecifyStepper.jsx:40
run has cyclomatic complexity 60 and cognitive complexity 48; 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. — dashboard/test-canvas-db-store.js:62
run has cyclomatic complexity 58 and cognitive complexity 61; 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. — dashboard/test-dashboard-shell.js:46
routePath has cyclomatic complexity 49 and cognitive complexity 144; 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. — dashboard/src/utils/canvasGeometry.mjs:48
main has cyclomatic complexity 47 and cognitive complexity 48; 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. — dashboard/test-work-state-api.js:12
parseSystemdEnvironmentFile has cyclomatic complexity 46 and cognitive complexity 78; 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. — scripts/systemd-config.mjs:349
createTaskRaw has cyclomatic complexity 45 and cognitive complexity 50; 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. — dashboard/hzl-service.js:1248
(anonymous) has cyclomatic complexity 44 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 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. — dashboard/test-dashboard-race-regressions-e2e.js:149
exerciseEndpoints has cyclomatic complexity 42 and cognitive complexity 32; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — dashboard/test-canvas-db-endpoints.js:90
runTests has cyclomatic complexity 40 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 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. — dashboard/test-specify-clarify-regression.js:95
evaluateCreationPolicy has cyclomatic complexity 38 and cognitive complexity 48; 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. — dashboard/task-creation-policy.js:107
MilestonesWidget has cyclomatic complexity 38 and cognitive complexity 45; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — REDACTED:262
_canonicalAdmission has cyclomatic complexity 38 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 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. — dashboard/project-bundle-import.js:367
What to do
Break down the listed branch-heavy functions; aim P95 cyclomatic ≤ 5.
Do you agree with this assessment?
R3 · Large Files5.7 / 10Adequate✓ Tool-verified
React / JS · Code Health — How many source files exceed the large-file threshold.
Method: Components/modules exceeding the large-file threshold, counted exhaustively across the frontend source tree. Deterministic.
REDACTED has 4965 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — REDACTED:1
dashboard/hzl-service.js has 4518 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — dashboard/hzl-service.js:1
dashboard/src/pages/TasksView.jsx has 1874 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — dashboard/src/pages/TasksView.jsx:1
dashboard/src/components/DetailPanel.jsx has 1628 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — dashboard/src/components/DetailPanel.jsx:1
REDACTED has 1329 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — REDACTED:1
REDACTED has 1310 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — REDACTED:1
dashboard/src/pages/FilesView.jsx has 1137 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — dashboard/src/pages/FilesView.jsx:1
dashboard/src/components/Sidebar.jsx has 977 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — dashboard/src/components/Sidebar.jsx:1
dashboard/test-setup-linux-systemd.mjs has 954 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — dashboard/test-setup-linux-systemd.mjs:1
dashboard/project-bundle-import.js has 943 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — dashboard/project-bundle-import.js:1
dashboard/src/components/SnippetUpgrade.jsx has 909 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — dashboard/src/components/SnippetUpgrade.jsx:1
dashboard/snippets-doctor.js has 887 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — dashboard/snippets-doctor.js:1
dashboard/test-snippets-doctor.js has 846 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — dashboard/test-snippets-doctor.js:1
dashboard/test-t168-t177-integration.js has 773 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — dashboard/test-t168-t177-integration.js:1
REDACTED has 767 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — REDACTED:1
dashboard/src/components/ProjectBundleModals.jsx has 756 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — dashboard/src/components/ProjectBundleModals.jsx:1
dashboard/src/context/DashboardContext.jsx has 690 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — dashboard/src/context/DashboardContext.jsx:1
dashboard/project-bundle-validator.js has 628 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — dashboard/project-bundle-validator.js:1
dashboard/test-dashboard-shell.js has 628 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — dashboard/test-dashboard-shell.js:1
dashboard/flowboard-metadata.js has 620 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — dashboard/flowboard-metadata.js:1
dashboard/overview.js has 603 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — dashboard/overview.js:1
dashboard/project-lifecycle.js has 602 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — dashboard/project-lifecycle.js:1
dashboard/src/utils/canvasGeometry.mjs has 586 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — dashboard/src/utils/canvasGeometry.mjs:1
dashboard/src/components/ActiveAgentsBar.jsx has 583 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — dashboard/src/components/ActiveAgentsBar.jsx:1
dashboard/project-bundle-export.js has 545 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — dashboard/project-bundle-export.js:1
dashboard/src/pages/OverviewView.jsx has 521 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — dashboard/src/pages/OverviewView.jsx:1
dashboard/src/components/SpecifyStepper.jsx has 512 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — dashboard/src/components/SpecifyStepper.jsx:1
dashboard/test-hzl-integration.js has 506 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — dashboard/test-hzl-integration.js:1
dashboard/project-bundle-schema.js has 494 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — dashboard/project-bundle-schema.js:1
dashboard/test-work-state-e2e.js has 494 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — dashboard/test-work-state-e2e.js:1
dashboard/test-snippets-integration.js has 479 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — dashboard/test-snippets-integration.js:1
dashboard/test-setup-macos-launchd.mjs has 475 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — dashboard/test-setup-macos-launchd.mjs:1
dashboard/project-bundle-import-preview.js has 461 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — dashboard/project-bundle-import-preview.js:1
dashboard/test-dashboard-api.mjs has 460 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — dashboard/test-dashboard-api.mjs:1
dashboard/test-work-state-backend.js has 443 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — dashboard/test-work-state-backend.js:1
REDACTED has 433 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — REDACTED:1
REDACTED has 421 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — REDACTED:1
dashboard/migrations.js has 420 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — dashboard/migrations.js:1
What to do
Split each oversized file along the responsibilities already in it, into smaller focused modules in the same package.
Do you agree with this assessment?
R4 · Test Coverage4.3 / 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) — scripts/setup.mjs:1, dashboard/test-setup-linux-systemd.mjs:1, dashboard/test-snippets-doctor.js:1, …
What to do
Add tests that import the unreached modules (directly or through their public entry).
React / JS · Readiness — How outdated the npm dependencies are (a maturity signal). JS/npm CVEs are scored separately in D30 (JS/npm Dependency Vulnerabilities).
Method: npm dependency staleness from manifest/registry metadata (a maturity signal; JS/npm CVEs are scored separately in D30, which answers dependency vulnerabilities for every ecosystem). Deterministic.
What to do
Bump outdated dependencies to current versions to limit upgrade debt.
Do you agree with this assessment?
R6 · Tooling3.4 / 10Weak✓ Tool-verified
React / JS · Readiness — Whether the project wires up test, lint and typecheck — detected from each package.json script's COMMAND (eslint / tsc / vitest / jest / playwright), not just its name, and corroborated against CI-workflow invocations so a tool run only in CI still counts.
Method: package.json scanned for test/lint/typecheck script wiring. Deterministic presence check.
test ✓ · lint ✗ · typecheck ✗ — read from this repository's package.json scripts and corroborated against its CI workflows. A script counts when its name or command matches the step: `test` for the suite, `lint` or `prettier` for linting, `typecheck`/`type-check`/`tsc` for type checking. ✗ therefore means no script or CI step under those names was found, NOT that the step is absent from your pipeline — a task invoked by a runner this check does not read, or named something else entirely, is not seen and is worth confirming before acting on a cross. A ✓ means the wiring is DECLARED — a script or CI step under those names exists. It is not a statement that the step passes, or that it runs at all: nothing here installs a dependency or executes a suite.
What to do
Add eslint and type checking (adopt TypeScript, or type-check the existing JavaScript with `checkJs`) as package.json scripts and run them in CI.
Do you agree with this assessment?
R7 · Dead Code9.0 / 10Exemplary✓ Tool-verified
React / JS · Code Health — Files unreachable from every application/tooling/test entry point, and exports nothing imports (module-graph reachability, D-386).
Method: Dead code: files unreachable from every application/tooling/test entry point plus exports nothing imports, via module-graph reachability. Deterministic, exhaustive over the import graph.
Unreachable from the 234 application, 19 tooling and 10 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 (234 application, 19 tooling, 10 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 (×2) — dashboard/tools/ov-resize-probe.mjs, openclaw/flowboard-plugin.js
Nothing ultimately consumes this binding: its only referrer is the re-export in dashboard/src/components/index.js, whose re-exported name has no consumer either. Removing it is therefore not a one-file change — drop the re-export line in dashboard/src/components/index.js in the same commit, or the barrel will import a name that no longer exists. (×6) — dashboard/src/components/AgentChip.jsx:136, dashboard/src/components/Card.jsx:11, dashboard/src/components/DataList.jsx:8, …
Nothing imports this binding — it is safe to review for removal. (×4) — dashboard/src/context/NavigationContext.jsx:62, dashboard/src/utils/exceptionReview.mjs:21, dashboard/src/utils/leaseHealth.js:9, …
This top-level declaration is not exported and its name occurs nowhere else in its module — not called, read, typed against, re-exported or named by a string. Nothing outside the module can reach a non-exported binding, so this is the whole search: remove it, or use it. (×9) — dashboard/project-bundle-import.js:73, dashboard/project-bundle-import.js:77, REDACTED:1575, …
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. — dashboard/test-canvas-db-endpoints.js:76
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 — Read from this repository's JavaScript/TypeScript source: cryptographic hygiene (weak hash or cipher, key material fixed in the source) and outbound TLS (certificate validation, protocol version) — facts about code that hold whether or not it serves anything itself. Markup this repository SHIPS is scored for third-party script integrity whether or not the repository serves it itself, since a page handed to a consumer runs in that consumer’s origin. The server controls — HTTPS enforcement, HSTS, cookie flags, input validation — are NOT assessed for JavaScript/TypeScript: each is scored as an absence, an absence is only reportable over the production HTTP server, and in this ecosystem the file that opens the port is build output or a framework launcher rather than a file in the source tree. Their absence here is not a finding about this repository. Its Node HTTP listeners were read for HTTPS enforcement alone — TLS served, a redirect to https:// or HSTS, or a TLS-terminating proxy configuration committed beside the server — each judged per server package.
Method: Roslyn plus filesystem scan: HSTS/security headers, secure cookies, input validation, middleware order, weak crypto (MD5/SHA1/DES); HTTPS-metadata context-aware. On a repository with no .NET source it reads JavaScript/TypeScript, Dart, Ruby, Scala, Rust or Elixir source itself (test, vendored, generated and minified paths not) for the arms that hold whether or not the code serves HTTP: a weak hash or cipher, key material fixed in the source, a TLS client that accepts any certificate, and (JavaScript/TypeScript, Ruby, Scala, Rust and Elixir) an obsolete TLS version; the server controls are not assessed there, and a Dart, Ruby, Scala, Rust or Elixir repository that serves no HTTP of its own is N/A on them. Deterministic.
`TELEGRAM_WEBAPP_HMAC_SALT` is the MAC key 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. — dashboard/telegram-auth.js:6
`https://telegram.org/js/telegram-web-app.js` is executed by this page with no Subresource Integrity. Whoever can answer that request — the CDN, anyone who compromises it, anyone on the network path — runs arbitrary script in this page's origin, with its session. The URL also names no version, so it resolves to whatever that origin serves at fetch time — the executed bytes can change with nobody touching this repository. — dashboard/index.html:24
`app.listen(…)` serves plain HTTP on a network address, and nothing in its package enforces HTTPS: no TLS served (`https.createServer`, Fastify `https`, Nest `httpsOptions`), no redirect of plain requests to `https://`, no `Strict-Transport-Security` (helmet sends it by default), and no TLS-terminating proxy configuration committed beside it — so a browser may talk to it in clear text. (−2.0 on this card.) — REDACTED:5347
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.
Pin third-party scripts and verify them: name an exact version in the URL and add an `integrity="sha384-…"` hash alongside `crossorigin="anonymous"` (both are required — an integrity hash on a cross-origin script without `crossorigin` is not evaluated, it blocks the script). Where the vendor ships a continuously-updated loader and publishes no stable hash (tag managers, analytics, chat widgets), Subresource Integrity is not available: constrain it instead with a `Content-Security-Policy` that names the exact origins allowed to execute, and drop the script from the pages that do not need it. Where the page is shipped inside a package that others host, prefer vendoring the asset and serving it from the app’s own origin, so no consumer inherits a third-party dependency they did not choose.
Enforce HTTPS on each listed server: serve TLS itself, or redirect plain requests to `https://` and send `Strict-Transport-Security` (`helmet()` does by default) behind the TLS-terminating proxy — and commit that proxy's configuration beside the service. A server only this machine reaches should bind `127.0.0.1`.
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.
Other · Code Health — Whether any branch is dead by construction — a switch arm whose label can never equal a case-normalised subject, or an `else if` whose predicate the arm above has already swallowed.
Method: Roslyn syntax + semantics: switch labels compared against the subject's own case normaliser, and if/else-if chains checked for a literal an earlier arm's containment test already swallows. Deterministic, provable per finding. Advisory.
Do you agree with this assessment?
X13 · Undrained process stream10.0 / 10Exemplary○ Nothing flagged
Other · Code Health — Whether a child process that has BOTH standard streams redirected drains both — reading one to the end while the other is never read deadlocks once the child fills the unread pipe.
Method: Roslyn syntax + semantics: ProcessStartInfo launches with both streams redirected, checked for a drain of each stream across the enclosing type. On a repository with no .NET source it reads JavaScript/TypeScript off the engine’s own token stream (test, vendored and minified paths not) with the same rule: a `spawn` imported from `child_process` whose stdout and stderr are both pipes (no options, no `stdio`, or `stdio` of `'pipe'`), bound to a local that never leaves its scope, where exactly one of the two streams is read, the other never, and the child’s `close`/`exit` (or the read stream’s end) is awaited; a shell redirect in the call’s arguments or a `kill` of the child suppresses it. The same rule reads Python’s `subprocess.Popen`, Dart’s `Process.start`, Ruby’s `Open3.popen3`, and Scala’s JDK process starts (`new ProcessBuilder(…).start()` with no `redirectErrorStream`/`redirectError`/`redirectOutput`/`inheritIO`, `Runtime.getRuntime.exec`) where one of `getInputStream`/`getErrorStream` is read and the other never while `waitFor()` is called or the read stream is read to its end. Deterministic, provable per finding. Advisory.
Other · Security — Whether a hand-rolled public/private IP check can be walked past — a method that unwraps IPv4-mapped IPv6 but returns the opposite verdict for the same host written as IPv4-compatible, 6to4 or NAT64.
Method: Roslyn syntax + semantics: methods that unwrap IPv4-mapped IPv6 and hand-roll IPv4 range carve-outs, checked for whether the IPv6 branch also accounts for the IPv4-compatible, 6to4 and NAT64 embeddings. Deterministic, provable per finding. Advisory.
Do you agree with this assessment?
X15 · Unvalidated length from an untrusted reader10.0 / 10Exemplary○ Nothing flagged
Other · Security — Whether a length read out of the stream being parsed is bounded before it is allocated or read — an unchecked count taken from the input lets the input choose the allocation.
Method: Roslyn syntax + semantics: integer lengths read from a BinaryReader and spent on a bulk read or an array allocation, checked for any comparison or bounding call on the value anywhere in the method. Deterministic, provable per finding. Advisory.
Other · Code Health — Whether a loop that shortens a string until it fits a length budget has a floor — one with none grinds the value down to the empty string, or past it into a negative-length `Substring`.
Method: Roslyn syntax + semantics: while/do loops whose body's only effect on a string is to drop its last character, checked for whether anything — a direct comparison on the length, a body guard, a break — bounds that length below. On a repository with no .NET source it reads JavaScript/TypeScript off the engine’s own token stream (test, vendored and minified paths not) with the same rule: a `while`/`do` loop whose body’s one assignment to a value is `x = x.slice(0, -1)` or `x = x.slice|substring|substr(0, x.length - 1)`, driven by a condition that reads `x.length` only as a term of a larger expression — never compared directly, never tested for truthiness, and with no other read of `x` — and whose body has no `break`, `return`, `throw` or `if` naming `x`. Deterministic, provable per finding. Advisory.
Do you agree with this assessment?
X17 · Uncapped recursion over a caller-supplied document10.0 / 10Exemplary○ Nothing flagged
Other · Security — Whether a walk that recurses through a JSON/XML tree handed in by its caller bounds how deep it will go — an uncapped walk lets the document's nesting choose the stack depth, and the resulting StackOverflowException cannot be caught.
Method: Roslyn syntax + semantics: methods that take a JSON/XML document node and call themselves with a child of it, reachable from an externally-callable member of the same type that accepts a document, checked for any depth parameter, descent counter or threaded arithmetic anywhere in the walk. On a repository with no .NET source it reads TypeScript off the engine’s own token stream (test, vendored, generated and minified paths and `.d.ts` not) with the same rule: a function or method with a parameter typed as a document value — `unknown`, `any`, `object`, `Record<string, unknown|any>`, a JSON alias (`JsonValue`, `JSONObject`, …) or a DOM node global the file does not rebind — that calls itself (bare, or through `this` for a method, or hands itself to a call over the value as in `value.map(walk)`) with something it took out of that value and never through an ancestor accessor such as `closest()` or `parentElement`, that is exported or reached from an exported function (a public method of the same exported class) taking such a value, and that names no depth, level, nesting, recursion, remaining or budget anywhere and threads no `+`/`-` arithmetic through a self-call. Plain JavaScript is not read: with no annotation nothing tells a parsed document from a tree the code built itself. Deterministic, provable per finding. Advisory.
Other · Code Health — Whether a type's disposal matches what it OWNS — releasing what it created, leaving alone what it was handed, and not declaring a finalizer for state that has nothing unmanaged to finalize.
Method: Roslyn syntax + semantics: every assignment to a disposable field is read to decide whether the type CREATED the value or was handed it, and the type's disposal is checked against that answer — an injected interface it disposes, a value it constructed and never releases, a finalizer on a type holding nothing unmanaged, and a disposable local whose every reference is a plain member read. A value handed to a container that disposes its contents (a parent control's `Controls` collection, a component `IContainer`) is released by that container and is not reported; generated code is out of population. On a repository with no .NET source the same ownership questions are read in JavaScript/TypeScript off the engine’s own token stream (test, vendored, generated and minified paths not): a class declaring `dispose()`, `[Symbol.dispose]()` or `[Symbol.asyncDispose]()` that disposes a field it was handed through a constructor parameter typed as a repository interface or resolved by a dependency-injection container; that assigns a field only ever from `new X(…)` of a disposable class and neither releases it anywhere in the class nor names it in its disposal member or a method that member calls, nor hands it to anything else; and a `const`/`let` local built from literals only whose every reference opens a statement operating on a non-release member of it. A class is disposable when every repository declaration of its name declares or inherits a disposal member, or when it is a documented library disposable (`vscode` EventEmitter, CancellationTokenSource and Disposable; three.js geometries, materials, textures, render targets, renderers, controls and composers). The finalizer arm has no JavaScript counterpart: a class cannot declare one. Dart is read for the owned-and-never-released arm: a Flutter `State` (or a class declaring `dispose()`/`close()`) whose library-private field is written only with direct creations of a framework controller, `FocusNode`, `StreamController` or periodic `Timer` (or a `.listen(…)` into a field declared `StreamSubscription`), which nothing in the class or its library releases (`dispose`/`close`/`cancel`) and which is never handed on except as a named argument. Ruby is read for the owned-and-never-released arm and the abandoned-local arm: a class declaring an instance `close`, `dispose`, `shutdown`, `stop`, `disconnect` or `terminate` whose instance variable is written only with a blockless core descriptor creation (`File.open`/`new`, `Tempfile`, `Dir.open`, `IO.popen`, the `socket` and `openssl` socket classes) that no method of the class closes and that is never handed on (passed, returned, stored, exposed by `attr_reader`, delegated) — a class whose superclass or mixin lies outside the repository is not judged — and a blockless creation read through and dropped (`File.open(path).read`) or held in a local that is never closed, returned, passed or stored (a `&:read` block-pass, an `autoclose: false` borrow and a `fileno` hand-over are not abandonment). PHP is read for the same two arms: a class (not a trait, and not one using a trait) declaring an instance `close`, `dispose`, `shutdown`, `stop`, `disconnect` or `terminate` whose `private` property (or a `final` class's `protected` one) is written only with a direct core `fopen`, `tmpfile`, `popen`, `proc_open`, `fsockopen`, `stream_socket_client`/`server` or `opendir` that nothing in the class closes (`fclose`, `pclose`, `closedir`, `unset`, a reset to `null`) and that is never handed on, and a handle held in a function's local, or read through as the argument of a reader, that is never closed, returned, passed, captured or stored; a `php://` stream, `curl_init`, `SplFileObject`, `PDO` and a function the repository declares under the core name are not read. Deterministic, provable per finding. Advisory.
Other · Code Health — Whether a method that temporarily changes state belonging to the whole process — the working directory, an environment variable — puts it back on EVERY path: a restore reached only when nothing throws leaks the change to the rest of the process.
Method: Roslyn syntax + semantics: method bodies that write the process working directory or an environment variable and write it back in the same body, checked for whether that restore sits in a `finally`/`catch` or only on the straight-line path. On a repository with no .NET source the same rule reads production JavaScript/TypeScript off the engine’s own token stream (test, vendored and minified paths not): `process.chdir`, `process.env.NAME =`/`["NAME"] =` and `delete process.env.NAME`, and Deno’s `Deno.chdir`/`Deno.env.set`/`Deno.env.delete`, paired per function body (a nested function or arrow is its own body, and module top-level code is none), where the last write puts back a local the body captured from the same global or deletes a variable the first write set, with at least one statement between them; a write in a `catch`/`finally` of that body silences it. Deterministic, provable per finding. Advisory.
Other · Code Health — Whether async functions that make a cancellable request accept or pass on an AbortSignal (adoption curve).
Method: Roslyn scan: every async method (excluding framework-fixed overrides/Blazor handlers) checked for CancellationToken parameter presence. Deterministic, adoption percentage. On a repository with no .NET source it reads JavaScript/TypeScript off the engine’s own token stream (test, vendored and minified paths not) with the same question: every named async function that itself makes a request an AbortSignal can cancel (global `fetch`, axios and its file-local instances, ky, ofetch) counts, and it is compliant when its parameters or body name a signal or it hands one of its own parameters to the request as options; signatures a framework fixes (JSX event handlers, route and lifecycle exports, request-first handlers, `override`, `'use server'` modules, TanStack `mutationFn`) are exempt unless they take a signal. Deterministic, adoption percentage.
Only 3/6 async functions that make a cancellable request (fetch, axios, ky, ofetch) accept an AbortSignal or pass one on, so a request keeps running after whatever wanted it has given up — a page navigated away from, an unmounted component, a timed-out job. Take a `signal` (or an options object that carries one) and hand it to the request; where nothing could ever cancel the call, omitting it is a deliberate choice — judge against how the function is used.
`sendWakeEvent` awaits `fetch(…)` but neither accepts an AbortSignal nor passes one on, so its caller cannot stop the request once it has started. Accept `{ signal }` and pass it through: `fetch(url, { signal })`. — REDACTED:1191
`gh` awaits `fetch(…)` but neither accepts an AbortSignal nor passes one on, so its caller cannot stop the request once it has started. Accept `{ signal }` and pass it through: `fetch(url, { signal })`. — dashboard/github.js:34
`api` awaits `fetch(…)` but neither accepts an AbortSignal nor passes one on, so its caller cannot stop the request once it has started. Accept `{ signal }` and pass it through: `fetch(url, { signal })`. — dashboard/scripts/migrate-canvas-to-db.mjs:41
What to do
Thread an AbortSignal through async functions that make requests, so the work stops when its caller gives up.
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. On a repository with no .NET source it reads JavaScript/TypeScript off the engine’s own token stream (test, vendored and minified paths not) with the same rule: a `debug`/`trace`/`verbose` call on a receiver named for a logger, or a `log`-prefixed method naming the level, whose argument calls an array operator (`map`/`filter`/`reduce`/`sort`/…), `Array.from`, `Object.keys/values/entries`, `JSON.stringify`/`util.inspect` over anything but a literal, or an array `join` — outside any arrow or function passed as an argument, which the logger calls only when the level is on — with no enclosing `if`, `&&` or `?:` whose condition names a level, a level string, or the `NODE_ENV`/`__DEV__`/`DEV` build switch. Deterministic, provable per finding. Advisory.
Do you agree with this assessment?
X24 · Document value interpolated into markup unescaped10.0 / 10Exemplary○ Nothing flagged
Other · Security — Whether text read out of the document being converted is escaped before it is written into generated markup — a value the document's author chose, interpolated into an attribute the surrounding literal delimits, can close that attribute and open another.
Method: Roslyn semantic model over the whole compilation: a string-typed `Value`/`InnerText`/`InnerXml`/`Text` member declared inside `DocumentFormat.OpenXml` or `System.Xml` is a taint SOURCE, propagated through assignments, returns, arguments, tuple elements and string composition to its transitive closure, then read at interpolated-string holes that sit in a markup position the surrounding literal itself delimits. Escaper/encoder calls and enclosing validator conditions cut the flow. Flow- and container-insensitive by construction. A second arm needs no provenance at all and reports a type that CONTRADICTS ITSELF — the same expression escaped at one delimited markup hole and interpolated raw at another hole in the same markup position of the same type, which the type's own escaping proves is a defect without knowing where the value came from. On a repository with no .NET source it reads JavaScript/TypeScript off the token stream with the same rule: a DOM read of raw document text (`getAttribute`, `textContent`, `innerText`, `nodeValue`) is the source, propagated through local bindings and string composition, and judged at template-literal and concatenation holes in the same two delimited markup positions; escapers and validating conditions cut it, and documentation-site, test, vendored and minified scripts are not read. Deterministic, provable per finding. Advisory.
Other · Code Health — Whether a value the caller is invited to supply is the value the type actually uses — a constructor parameter stored in a private field that nothing ever reads while the default it was given is spelled out a second time at the site that should have read it, a keyed lookup that falls back to a different setting than the one its key names while the same type falls back to the matching one for that same key, or a culture-sensitive parse given no format provider by a type that feeds its own settable culture to the same kind of parse elsewhere, or a number an entry point writes to standard output under the host's culture while the same entry point formats with the invariant culture elsewhere. Either way, every caller who supplies a value silently gets something else.
Method: Roslyn syntax: private instance fields of a non-partial type assigned in a constructor from one of its own parameters with a `??` fallback, checked for whether anything in the type body reads the field and whether that same fallback expression is spelled out again outside the constructor; and `??` fallbacks onto a member access from a lookup call carrying exactly one string literal, grouped by that key across the type and checked for a fallback member whose folded name disagrees with the key while a sibling site for the same key agrees with it. On a repository with no .NET source the first two arms read JavaScript/TypeScript off the engine’s own token stream (tests included, bundles and vendored paths not): a `#x`, `private` or `private` parameter-property instance field filled in the constructor from a parameter (or one member of one) through `??`/`||` or a parameter default, never read anywhere in the file by name, whose constructed default is spelled again in the class body; and `lookup("key") ?? s.member` grouped by key per class, or per module outside every class. The culture arm has no JavaScript counterpart: its parses take no locale. Deterministic, provable per finding. Advisory.
Do you agree with this assessment?
X28 · Index access outside its own emptiness guard10.0 / 10Exemplary○ Nothing flagged
Other · Code Health — Whether a condition that tests a value for emptiness indexes that same value only where the test holds — an `||` written one parenthesis too far to the left leaves an index access outside the guard beside it, so the empty case the guard exists to anticipate reaches the index and throws.
Method: Roslyn syntax only, no semantic model: the OUTERMOST `&&`/`||` of every boolean condition, read for a symbol the condition tests for emptiness (`string.IsNullOrEmpty`/`IsNullOrWhiteSpace`, a `Length`/`Count` comparison against a literal, `Any()`, a `Length`/`Count` pattern, or a comparison against `""`) and ALSO indexes. Each `symbol[...]` access is placed by a boolean-reachability walk from the access up to the outermost connective: an access is COVERED when some enclosing step has it in the right operand and the left operand, under the truth value that step forces, proves the symbol non-empty — a recursion over `&&`/`||` whose true- and false-directions are asymmetric. A finding needs BOTH an uncovered access and a covered one on the same symbol in the same condition, which is the agreeing twin that separates a misplaced parenthesis from an unrelated length test. Bare index accesses with no emptiness test in the condition are neither counted nor reported; a non-identifier receiver and a lambda nested inside the condition are outside the population. Deterministic, provable per finding. Advisory.
Do you agree with this assessment?
X29 · Per-element action decided by a fixed element10.0 / 10Exemplary○ Nothing flagged
Other · Code Health — Whether a decision taken once per element is taken ABOUT that element — a test inside a counted loop that reads a fixed subscript of the very collection its guarded statement indexes by the loop variable applies element zero's answer to all of them, so the elements that differ from it are all handled wrongly, and in the same direction.
Method: Roslyn syntax only, no semantic model: every `for` statement declaring exactly ONE loop variable, and every `if` inside its body that is not under a nested loop or a lambda. A site enters the population when the `if`’s condition never mentions the loop variable while the statement it guards indexes some collection by that variable ALONE (`c[i]`; `c[i + 1]` and `c[i, j]` are outside it). A finding additionally needs the AGREEING TWIN at the same-collection grain: the condition must read THAT SAME collection at a subscript that does not move — written into the condition, or reached through a local declared BEFORE the loop, so an alias bound inside the body is not followed. Both collection expressions must be simple identifiers. On a repository with no .NET source the same rule reads JavaScript/TypeScript off the engine’s own token stream (tests included, bundles and vendored paths not): a `for (let|var|const x = …; …; …)` with one declarator and a braced body, an alias followed only when it is declared before the loop in a block that encloses it and never assigned inside the loop. Deterministic, provable per finding. Advisory.
Other · Code Health — Whether exceptions are handled rather than silently swallowed or rethrown with lost stack traces.
Method: Roslyn syntax scan: every catch clause counted; empty catches and bare rethrows flagged. Population is all catch clauses, not estimated. Deterministic, hard fact.
`catch` 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. (×8) — dashboard/snippets-doctor.js:290, dashboard/snippets-doctor.js:633, dashboard/snippets-doctor.js:673, …
An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it. (×32) — dashboard/snippets-doctor.js:646, REDACTED:349, REDACTED:1036, …
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?
WCAG coverage — what static analysis assessed
Statically assessed 12 of 55 WCAG 2.2 Level A/AA success criteria (22%; ≈24% of the 50 WCAG 2.1 AA criteria for EN 301 549). The other 43 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 — 3 check(s) recorded observations but carry no score
These checks ran and found something, but they do not carry a score — either by design (an advisory check reports evidence rather than grading it) or because they could not be scored here. They are excluded from the score for that reason, not because there was nothing to see.
D36 Supply-chain Provenance & Signing — 1 observation(s) recorded · The CI pipeline builds and tests but publishes no released artifact — no package publish, container push, GitHub release or deployment step. Supply-chain provenance, signing and SBOM attest RELEASED artifacts, so there is nothing to attest here. Add them to the release pipeline when this repo starts shipping artifacts (a published package, a container image, a deployed service or a tagged release). Build integrity and workflow-token hygiene are reported below: they describe what the CI runs and the token it runs with, neither of which is affected by whether the pipeline ships an artifact.
X10 Duplicated predicate — 25 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
X7 Silent fallback defaults — 17 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.
P4 Deployment & Rollback — not evidenced — no deploy/rollback/approval signal in the repo; absence of evidence is not evidence of a manual release
Not included — 50 check(s) not relevant to this codebase
These checks had nothing to measure here (no tests, no git history, the codebase is small, or the architecture style doesn't apply), so they're omitted above rather than scored low.
AC1 Text alternatives — No image/media element found in the parsed markup — AC1 not applicable here.
AX1 Captive dependencies — Not applicable: this repository's JavaScript imports no dependency-injection container and defines no container of its own — nothing that both registers and resolves bindings, and nothing that names two lifetimes — so nothing holds one lifetime's instance while handing out another's.
AX2 Stateful singletons — Not applicable: TypeScript/JavaScript runs each process's requests on one event loop, so no two requests write a shared object at the same instant (interleaving across an await is a different defect).
AX5 Architecture & structure — not assessed — architecture style/structure is computed from a project graph (projects, types, module namespaces) that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
AX6 Interface segregation — not assessed — interface segregation is computed over a type surface that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
AX7 Slice cohesion — not applicable — not a vertical-slice architecture
AX8 Test isolation — no test/production split to check
AX9 CQS / query purity — no CQRS query handlers detected — query purity is not applicable to this codebase
AXB2 Runtime readiness — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
AXR1 Runtime accessibility — the dev server did not expose a crawlable HTTP endpoint in time — no runtime evidence This is a statement about this run, not a statement about your application: nothing here says the surface is inaccessible, only that it was never rendered.
C1 Data Protection — No personal data detected in a persisted data model — no PII-named field (email, firstName, dateOfBirth, phoneNumber, …) or stored credential on a TypeORM/MikroORM/sequelize-typescript/NestJS-Mongoose entity, a Mongoose schema, a Sequelize or Drizzle table, a Knex migration or a Prisma model — and no database or data-store client in the source either, so this repository keeps no data at rest for these controls to protect. If it does persist personal data (through a hosted backend configured outside this repository, for instance), the controls belong to wherever that data is stored.
C3 Audit Trail — No personal data detected in a persisted data model — no PII-named field (email, firstName, dateOfBirth, phoneNumber, …) or stored credential on a TypeORM/MikroORM/sequelize-typescript/NestJS-Mongoose entity, a Mongoose schema, a Sequelize or Drizzle table, a Knex migration or a Prisma model — and no database or data-store client in the source either, so this repository keeps no sensitive data whose changes an audit trail would record. If it does (through a hosted backend configured outside this repository, for instance), the trail belongs to wherever that data is stored.
C4 Data Retention — No personal data detected in a persisted data model — no PII-named field (email, firstName, dateOfBirth, phoneNumber, …) or stored credential on a TypeORM/MikroORM/sequelize-typescript/NestJS-Mongoose entity, a Mongoose schema, a Sequelize or Drizzle table, a Knex migration or a Prisma model — and no database or data-store client in the source either, so this repository keeps no personal data whose lifetime a retention limit would bound. If it does (through a hosted backend configured outside this repository, for instance), the limit belongs wherever that data is stored.
C5 Data-Subject Rights — No personal data detected in a persisted data model — no PII-named field (email, firstName, dateOfBirth, phoneNumber, …) or stored credential on a TypeORM/MikroORM/sequelize-typescript/NestJS-Mongoose entity, a Mongoose schema, a Sequelize or Drizzle table, a Knex migration or a Prisma model — and no database or data-store client in the source either, so this repository keeps no personal data for a data subject to erase, export or consent over. If it does (through a hosted backend configured outside this repository, for instance), the rights are served wherever that data is stored.
D10 Test Quality — No tests were found in the analyzed repository to assess for quality.
D11 Test Reliability — No test suite was found to re-run, so reliability couldn't be assessed. Two searches produced that zero and both came back empty: the classifier that reads the loaded workspace recognised no suite it could run, and a walk of the source on disk — which covers the JS/TS `*.test.*` and `*.spec.*` conventions and probes for a Pester suite — found no test source in any other ecosystem either. Neither search reaches a suite that is missing from the loaded workspace and carries no name either walk recognises, so this is 'no suite found by those two searches', not a verdict that the repository has none.
D16 Bus Factor — single-maintainer repository — bus factor is not applicable
D17 Explicit Debt — explicit-debt markers are read through a C# workspace today, so they were not read for this repository's language — this asserts nothing about how many markers the code carries. Not scored — this is a gap in the analyzer, not a finding about this repository
D18 Solution Shape — D18 scores the shape of a .NET solution; this repository has no .NET solution or project files, so the dimension does not apply.
D22 Internal API Consistency — The exposed public-API surface could not be collected — no C#/VB projects loaded.
D23 Boundary Type-Coupling — No bounded-context organisation was detected either — neither a context-shaped layout, nor 2+ sibling source directories each declaring an aggregate root, nor 2+ projects each declaring an entity of their own. Declaring this codebase's bounded contexts (≥2) would let cross-boundary type coupling be assessed. Declare them in `.codehealth/config.yaml` at the repository root (create it if absent), mapping each context name to the module-path or namespace prefixes that belong to it — e.g. `architecture:` → `contexts:` → `Billing: ["src/billing", "Acme.Billing"]`, `Catalog: ["src/catalog", "Acme.Catalog"]`.
D24 Comment Value — No inline comments to assess — comment value is not applicable here.
D27 Navigability — D27 counts a call into the standard library or a dependency as unresolved for this repository's language (.cjs,.html,.js,.mjs), so too few call sites counted as resolved to assess navigability. Not scored: this is a gap in the analyzer, not a verdict about this repository.
D31 IaC & Container Security — No Infrastructure-as-Code or container manifests found (Dockerfile, Docker Compose, Terraform, Kubernetes/Helm, CloudFormation, ARM, Bicep, Ansible); nothing to scan.
D32 Data Compliance (PII/GDPR) — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that.
D39 IL Efficiency — D39 measures the IL emitted by a .NET build; this repository has no .NET solution or project files, so the dimension does not apply.
D4 Code Duplication — Duplication not measured — .html not exposed to the token comparison
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.
D44 Platform End-of-Life — Platform end-of-life not assessed — this repository declares no platform this pass reads
D5 Coupling — Not applicable — this npm build ships 1 production module(s), so there is no coupling BETWEEN modules to measure. (Its test and non-production modules are not part of the shipped graph.)
DM1 Domain Modelling — not scored — this repository shows none of the 3 signals this lens looks for
ED1 Event-Driven — not scored — this repository shows none of the 3 signals this lens looks for
ED5 Idempotency — no mutating command handlers or message consumers detected — idempotency check not applicable
ES1 Event Sourcing — not scored — this repository shows none of the 3 signals this lens looks for
P12 CI test-gate honesty — Reported, not scored — and nothing was matched here. The coverage check applies to any stack, and the automatic-re-run check to any GitHub-Actions workflow, but the checks for excluded tests, skipped tests and sleep-based synchronisation currently recognise only some ecosystems' test-runner idioms, so on a repository built with another stack the zeros below mean 'not checked', not 'clean'.
P8 Schema migrations — no ORM, schema-migration tool or schema auto-create was found in this repository's dependency manifests or source, so there is no database schema for this check to judge
P9 Domain vs controller coverage — no coverage report found on disk — produce a coverage report in a standard format (lcov — `vitest --coverage`, `jest --coverage`, `bun test --coverage --coverage-reporter=lcov`, or `nyc`) and commit it — a hosted scan measures a clone of the repository, so a report that exists only in a working tree, a CI runner's or your own, never reaches it; the artefact is commonly gitignored, so `git add -f` that one file (or un-ignore its path) and commit it alongside the code it measures, or wire coverage collection into CI, to enable this cross-layer check
PF1 Benchmark discipline — Not applicable: no benchmark suite was found. This check searched for tinybench, mitata, benchmark.js, benny or vitest `bench(...)` calls in files that import them (or `*.bench.*` files), or one of those in a package.json, and for a `*benchmark*` script that this repository's CI runs. Benchmarks are credited as a bonus, so their absence is neither scored nor deducted.
PF2 Allocation hygiene — Not applicable: TypeScript/JavaScript runs on a garbage-collected runtime that gives a program no allocation-control idiom to choose on a hot path — no pools, stack allocation or value types — so allocation awareness is not something this code can be rated on.
SC1 Supply-chain hygiene — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
X20 Mistyped argument guard — This check asks whether an argument guard reports an EMPTY value as a NULL one, which needs a language that throws a null-specific argument exception — .NET's ArgumentNullException, the JVM's NullPointerException, Dart's ArgumentError.notNull. This repository contains none of those languages: the ones it is written in have a single exception for a bad argument, so there is no pair of exceptions to confuse and nothing here for it to assess. Not a gap in the analyzer and not a finding about your code.
X26 Unsynchronised callback handoff — Not applicable: this check looks for a collection written by a callback on one thread while the body waiting on it touches it on another, and in this repository's languages no collection is reachable from two threads at once. TypeScript/JavaScript runs every callback on the one thread that owns its objects: a callback runs only when the body waiting on it has yielded, never alongside it, and a worker thread receives a COPY of what it is sent. A SharedArrayBuffer carries raw bytes, never an Array, Map or Set, so no collection is reachable from two threads at once. Not a gap in the analyzer and not a finding about your code.
X27 Collection changed while being enumerated — Not applicable: this check looks for a loop whose body adds to or removes from the very collection the loop is walking, invalidating the enumerator it holds, and in this repository's languages that cannot happen. JavaScript and TypeScript have no iterator that a change can invalidate: an `Array` is walked by index against its live length, and a `Map` or `Set` by the ECMAScript specification's live entry list, so a body that adds to, removes from or empties what it walks raises nothing — every loop form (`for…of`, `for…in`, `forEach`, `map`, `filter`, `reduce`, `entries()`) on every built-in collection (`Array`, `Map`, `Set`, plain objects, `URLSearchParams`, `Headers`, `FormData`) runs to completion. Such a loop can still skip an element or never end, which is a different defect and not the one this check asks about. Not a gap in the analyzer and not a finding about your code.
X32 Type resolved by simple name across every loaded assembly — This check is about how a .NET program searches the assemblies loaded into its process for a type, and this repository contains no .NET source, so there is nothing here for it to assess. Not a gap in the analyzer and not a finding about your code.
X4 Structured logging — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
X5 Nullable reference types — Not applicable: this check asks whether the null-typed discipline a language offers is switched on, and how much of that the assertion operator takes back, and in this repository's languages there is no such switch and no such operator. Plain JavaScript carries no type annotations and commits no tsconfig, so it states no null-typed discipline for this check to grade: there is nothing here that switches null checking on or off, and TypeScript (or `// @ts-check`) is how a repository acquires one — advice, not a defect this card measures. Not a gap in the analyzer and not a finding about your code.
X6 Hand-rolled structured-format parsing — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
X9 Subsumed condition operand — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
Appendix A — Findings (grouped)
The findings behind the scores, grouped by severity, then by dimension and kind. The high-severity issues are enumerated in full below; items per group are capped at 25 with any overflow stated explicitly per group, never silently truncated. The complete machine-readable list of every finding (all severities) is the companion findings.md in this report's bundle.
Critical — 70 finding(s)
AC4 · Keyboard semantics· Click handler on a non-interactive <div> · ×20
Click handler on a non-interactive <div> dashboard/src/components/DetailPanel.jsx:1495— A click handler on a plain element with no role and no tabindex: even where another element's key handler can reach it, assistive tech can neither focus it nor announce what it is. Use a <button>, or add role + tabIndex={0}.
Click handler on a non-interactive <div> dashboard/src/components/DetailPanel.jsx:1580— A click handler on a plain element with no role and no tabindex: even where another element's key handler can reach it, assistive tech can neither focus it nor announce what it is. Use a <button>, or add role + tabIndex={0}.
Click handler on a non-interactive <div> dashboard/src/components/Panel.jsx:31— A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabIndex={0} + a key handler.
Click handler on a non-interactive <div> dashboard/src/components/SnippetUpgrade.jsx:904— A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabIndex={0} + a key handler.
Click handler on a non-interactive <div> REDACTED:179— A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabIndex={0} + a key handler.
Click handler on a non-interactive <div> REDACTED:387— A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabIndex={0} + a key handler.
Click handler on a non-interactive <div> REDACTED:457— A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabIndex={0} + a key handler.
Click handler on a non-interactive <div> REDACTED:494— A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabIndex={0} + a key handler.
Click handler on a non-interactive <div> REDACTED:543— A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabIndex={0} + a key handler.
Click handler on a non-interactive <div> REDACTED:625— A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabIndex={0} + a key handler.
Click handler on a non-interactive <div> REDACTED:667— A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabIndex={0} + a key handler.
Click handler on a non-interactive <div> REDACTED:695— A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabIndex={0} + a key handler.
Click handler on a non-interactive <div> REDACTED:744— A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabIndex={0} + a key handler.
Click handler on a non-interactive <div> REDACTED:464— A click handler on a plain element with no role and no tabindex: even where another element's key handler can reach it, assistive tech can neither focus it nor announce what it is. Use a <button>, or add role + tabIndex={0}.
Click handler on a non-interactive <div> REDACTED:563— A click handler on a plain element with no role and no tabindex: even where another element's key handler can reach it, assistive tech can neither focus it nor announce what it is. Use a <button>, or add role + tabIndex={0}.
Click handler on a non-interactive <div> REDACTED:615— A click handler on a plain element with no role and no tabindex: even where another element's key handler can reach it, assistive tech can neither focus it nor announce what it is. Use a <button>, or add role + tabIndex={0}.
Click handler on a non-interactive <div> dashboard/src/pages/FilesView.jsx:105— A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabIndex={0} + a key handler.
Click handler on a non-interactive <div> dashboard/src/pages/FilesView.jsx:133— A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabIndex={0} + a key handler.
Click handler on a non-interactive <div> dashboard/src/pages/TasksView.jsx:158— A click handler on a plain element with no role and no tabindex: even where another element's key handler can reach it, assistive tech can neither focus it nor announce what it is. Use a <button>, or add role + tabIndex={0}.
Click handler on a non-interactive <div> dashboard/src/pages/TasksView.jsx:242— A click handler on a plain element with no role and no tabindex: even where another element's key handler can reach it, assistive tech can neither focus it nor announce what it is. Use a <button>, or add role + tabIndex={0}.
AC2 · Forms & labels· <input> without a programmatic label · ×10
<input> without a programmatic label dashboard/src/components/DetailPanel.jsx:1535— This control has only a placeholder — a placeholder is not a label (it vanishes on input and many AT ignore it). Add a <label htmlFor>, a wrapping <label>, or aria-label.
<input> without a programmatic label dashboard/src/components/Sidebar.jsx:163— This control has no associated label. Add a <label htmlFor> / wrapping <label> / aria-label / aria-labelledby so assistive tech can name it.
<input> without a programmatic label REDACTED:107— This control has only a placeholder — a placeholder is not a label (it vanishes on input and many AT ignore it). Add a <label htmlFor>, a wrapping <label>, or aria-label.
<input> without a programmatic label REDACTED:211— This control has only a placeholder — a placeholder is not a label (it vanishes on input and many AT ignore it). Add a <label htmlFor>, a wrapping <label>, or aria-label.
<input> without a programmatic label REDACTED:376— This control has only a placeholder — a placeholder is not a label (it vanishes on input and many AT ignore it). Add a <label htmlFor>, a wrapping <label>, or aria-label.
<input> without a programmatic label REDACTED:1211— This control has only a placeholder — a placeholder is not a label (it vanishes on input and many AT ignore it). Add a <label htmlFor>, a wrapping <label>, or aria-label.
<input> without a programmatic label REDACTED:88— This control has only a placeholder — a placeholder is not a label (it vanishes on input and many AT ignore it). Add a <label htmlFor>, a wrapping <label>, or aria-label.
<input> without a programmatic label REDACTED:421— This control has only a placeholder — a placeholder is not a label (it vanishes on input and many AT ignore it). Add a <label htmlFor>, a wrapping <label>, or aria-label.
<input> without a programmatic label dashboard/src/pages/TasksView.jsx:756— This control has only a placeholder — a placeholder is not a label (it vanishes on input and many AT ignore it). Add a <label htmlFor>, a wrapping <label>, or aria-label.
<input> without a programmatic label dashboard/src/pages/TasksView.jsx:1019— This control has only a placeholder — a placeholder is not a label (it vanishes on input and many AT ignore it). Add a <label htmlFor>, a wrapping <label>, or aria-label.
AC4 · Keyboard semantics· Clickable element isn't keyboard-operable · ×8
Clickable element isn't keyboard-operable dashboard/src/components/Sidebar.jsx:922— The repo's own CSS styles .archive-head with `cursor: pointer`, so this <div> is a control — but it has no role, no tabIndex={0} and no key handler, so it can only be reached with a mouse. Use a <button>, or add role + tabIndex={0} + a key handler.
Clickable element isn't keyboard-operable dashboard/src/components/SnippetUpgrade.jsx:728— The repo's own CSS styles .file-row-main with `cursor: pointer`, so this <div> is a control — but it has no role, no tabIndex={0} and no key handler, so it can only be reached with a mouse. Use a <button>, or add role + tabIndex={0} + a key handler.
Clickable element isn't keyboard-operable dashboard/src/components/SnippetUpgrade.jsx:761— The repo's own CSS styles .file-row-main with `cursor: pointer`, so this <div> is a control — but it has no role, no tabIndex={0} and no key handler, so it can only be reached with a mouse. Use a <button>, or add role + tabIndex={0} + a key handler.
Clickable element isn't keyboard-operable dashboard/src/components/SnippetUpgrade.jsx:791— The repo's own CSS styles .file-row-main with `cursor: pointer`, so this <div> is a control — but it has no role, no tabIndex={0} and no key handler, so it can only be reached with a mouse. Use a <button>, or add role + tabIndex={0} + a key handler.
Clickable element isn't keyboard-operable dashboard/src/components/SnippetUpgrade.jsx:821— The repo's own CSS styles .file-row-main with `cursor: pointer`, so this <div> is a control — but it has no role, no tabIndex={0} and no key handler, so it can only be reached with a mouse. Use a <button>, or add role + tabIndex={0} + a key handler.
Clickable element isn't keyboard-operable dashboard/src/components/SnippetUpgrade.jsx:851— The repo's own CSS styles .file-row-main with `cursor: pointer`, so this <div> is a control — but it has no role, no tabIndex={0} and no key handler, so it can only be reached with a mouse. Use a <button>, or add role + tabIndex={0} + a key handler.
Clickable element isn't keyboard-operable dashboard/src/components/SnippetUpgrade.jsx:880— The repo's own CSS styles .file-row-main with `cursor: pointer`, so this <div> is a control — but it has no role, no tabIndex={0} and no key handler, so it can only be reached with a mouse. Use a <button>, or add role + tabIndex={0} + a key handler.
Clickable element isn't keyboard-operable dashboard/src/components/canvas/ConnectionLayer.jsx:109— The repo's own CSS styles .conn-path with `cursor: pointer`, so this <path> is a control — but it has no role, no tabIndex={0} and no key handler, so it can only be reached with a mouse. Use a <button>, or add role + tabIndex={0} + a key handler.
AC4 · Keyboard semantics· Click handler on a non-interactive <span> · ×4
Click handler on a non-interactive <span> dashboard/src/components/canvas/CanvasToolbar.jsx:132— A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabIndex={0} + a key handler.
Click handler on a non-interactive <span> REDACTED:552— A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabIndex={0} + a key handler.
Click handler on a non-interactive <span> REDACTED:245— A click handler on a plain element with no role and no tabindex: even where another element's key handler can reach it, assistive tech can neither focus it nor announce what it is. Use a <button>, or add role + tabIndex={0}.
Click handler on a non-interactive <span> dashboard/src/pages/TasksView.jsx:245— A click handler on a plain element with no role and no tabindex: even where another element's key handler can reach it, assistive tech can neither focus it nor announce what it is. Use a <button>, or add role + tabIndex={0}.
AC2 · Forms & labels· Custom control with no accessible name on <span> · ×3
Custom control with no accessible name on <span> dashboard/src/pages/TasksView.jsx:245— This <span> carries a click handler, which makes it a control, but it has no text, aria-label or labelled child (the icon-only case), so assistive tech has no name to announce for it. Note that switching it to <button type="button"> — the right fix for its keyboard operability — does not give it a name either: an icon-only button still needs one. Add visible text or an aria-label.
Custom control with no accessible name on <span> dashboard/src/pages/TasksView.jsx:617— This <span> carries a click handler, which makes it a control, but it has no text, aria-label or labelled child (the icon-only case), so assistive tech has no name to announce for it. Note that switching it to <button type="button"> — the right fix for its keyboard operability — does not give it a name either: an icon-only button still needs one. Add visible text or an aria-label.
Custom control with no accessible name on <span> dashboard/src/pages/TasksView.jsx:624— This <span> carries a click handler, which makes it a control, but it has no text, aria-label or labelled child (the icon-only case), so assistive tech has no name to announce for it. Note that switching it to <button type="button"> — the right fix for its keyboard operability — does not give it a name either: an icon-only button still needs one. Add visible text or an aria-label.
ADR not followed: ADR-0002: /api/status requires an explicit agentId docs/adr/0002-api-status-requires-agent-id.md— /api/status still takes no agentId parameter despite requiring an explicit one; its type dependency line shows it derives from nothing, contradicting the decision. (docs/adr/0002-api-status-requires-agent-id.md)
ADR not followed: ADR-0003: The dashboard service has no agent identity docs/adr/0003-dashboard-has-no-agent-identity.md— The public constant AGENT_ID is present in the summary, contradicting the decision that the dashboard has no agent identity. (docs/adr/0003-dashboard-has-no-agent-identity.md)
ADR not followed: ADR-0021: Specify worker runs as OpenClaw CLI one-shot — no dedicated agent, no FlowBoard LLM layer docs/adr/0021-specify-worker-openclaw-cli.md— The worker agent is an explicitly registered OpenClaw CLI one-shot per the ADR's one-shot requirement. (docs/adr/0021-specify-worker-openclaw-cli.md)
AC2 · Forms & labels· <button> with no accessible text · ×2
<button> with no accessible text dashboard/src/components/DetailPanel.jsx:1003— A button with no text and no aria-label has no accessible name. Add visible text or an aria-label (an icon-only button still needs one).
<button> with no accessible text dashboard/src/components/DetailPanel.jsx:1654— A button with no text and no aria-label has no accessible name. Add visible text or an aria-label (an icon-only button still needs one).
AC2 · Forms & labels· <textarea> without a programmatic label · ×1
<textarea> without a programmatic label dashboard/src/components/DetailPanel.jsx:1014— This control has no associated label. Add a <label htmlFor> / wrapping <label> / aria-label / aria-labelledby so assistive tech can name it.
AC2 · Forms & labels· Custom control named only by title on <span> · ×1
Custom control named only by title on <span> dashboard/src/components/canvas/CanvasToolbar.jsx:132— This <span> carries a click handler, which makes it a control, and its only name is a title attribute. A plain element maps to role="generic", which does not support a name from the author, so the title is announced as nothing at all — it is a mouse-only tooltip, unreachable on touch. Give it role="button" (which it needs anyway to be operable) so the title becomes a real name, or add an aria-label.
AC2 · Forms & labels· Custom control with no accessible name on <path> · ×1
Custom control with no accessible name on <path> dashboard/src/components/canvas/ConnectionLayer.jsx:110— This <path> carries a click handler, which makes it a control, but it has no text, aria-label or labelled child (the icon-only case), so assistive tech has no name to announce for it. Note that switching it to <button type="button"> — the right fix for its keyboard operability — does not give it a name either: an icon-only button still needs one. Add visible text or an aria-label.
AC2 · Forms & labels· Custom control with no accessible name on <div> · ×1
Custom control with no accessible name on <div> dashboard/src/pages/TasksView.jsx:1820— This <div> carries a click handler, which makes it a control, but it has no text, aria-label or labelled child (the icon-only case), so assistive tech has no name to announce for it. Note that switching it to <button type="button"> — the right fix for its keyboard operability — does not give it a name either: an icon-only button still needs one. Add visible text or an aria-label.
AC4 · Keyboard semantics· Click handler on a non-interactive <h2> · ×1
Click handler on a non-interactive <h2> dashboard/src/components/DetailPanel.jsx:1037— A click handler on a plain element with no role and no tabindex: even where another element's key handler can reach it, assistive tech can neither focus it nor announce what it is. Use a <button>, or add role + tabIndex={0}.
AC4 · Keyboard semantics· Click handler on a non-interactive <li> · ×1
Click handler on a non-interactive <li> dashboard/src/components/Dropdown.jsx:68— A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabIndex={0} + a key handler.
AC4 · Keyboard semantics· Hover-only interaction on <div> · ×1
Hover-only interaction on <div> dashboard/src/components/UndoToast.jsx:48— This <div> binds mouse-enter and mouse-leave and nothing else — no click, no key handler, no focus handler, and no tabIndex={0}, so it cannot even take focus. A keyboard user cannot hover, so whatever the pair reveals or highlights is reachable with a mouse only. Bind the same state to focus/blur as well, and add tabIndex={0}="0" so the element can receive that focus.
AC4 · Keyboard semantics· Click handler on a non-interactive <path> · ×1
Click handler on a non-interactive <path> dashboard/src/components/canvas/ConnectionLayer.jsx:110— A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabIndex={0} + a key handler.
AC4 · Keyboard semantics· Double-click handler on a non-interactive <div> · ×1
Double-click handler on a non-interactive <div> REDACTED:1282— This <div> binds mousedown, mouseup, mousemove and double-click — pointer gestures with no keyboard form, a double-click among them. No click, no key handler, and no tabIndex={0}, so it cannot even take focus. Nothing synthesises a double-click from the keyboard: Enter and Space fire a single click, and only on a native <button> or <a href>. So this behaviour has no keyboard path at all. Expose the same action on a real control, or add role + tabIndex={0} + a key handler alongside the double-click.
No automated tests — No automated tests — no test code was found in this repository. Untested code is the largest single risk to changing it safely. Start with the code you change most often: add a suite in a framework a runner can collect (Vitest, Jest, Mocha, or the runtime's built-in runner (`node --test`, `bun test`, `deno test`)), and run it in CI so the gap cannot reopen.
Unlisted import 'libsql' dashboard/test-canvas-db-endpoints.js:76— 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 dashboard/telegram-auth.js:6— `TELEGRAM_WEBAPP_HMAC_SALT` is the MAC key 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.
Sync-over-async blocking dashboard/hzl-service.js:542— `fs.existsSync` in `init` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs.
Sync-over-async blocking dashboard/hzl-service.js:542— `fs.mkdirSync` in `init` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs.
Sync-over-async blocking dashboard/hzl-service.js:557— `fs.existsSync` in `init` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs.
Sync-over-async blocking dashboard/hzl-service.js:557— `fs.chmodSync` in `init` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs.
Sync-over-async blocking dashboard/project-bundle-import.js:929— `fs.existsSync` in `importBundle` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs.
Sync-over-async blocking dashboard/project-bundle-import.js:929— `fs.rmSync` in `importBundle` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs.
Sync-over-async blocking dashboard/project-bundle-import.js:956— `fs.existsSync` in `importBundle` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs.
Sync-over-async blocking dashboard/project-bundle-import.js:957— `fs.rmSync` in `importBundle` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs.
Sync-over-async blocking REDACTED:612— `fs.existsSync` in `app.get("/")` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs.
Sync-over-async blocking REDACTED:622— `fs.readFileSync` in `app.get("/")` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs.
Sync-over-async blocking REDACTED:648— `fs.existsSync` in `app.get("/*path")` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs.
Sync-over-async blocking REDACTED:648— `fs.statSync` in `app.get("/*path")` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs.
Sync-over-async blocking REDACTED:653— `fs.readFileSync` in `app.get("/*path")` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs.
Sync-over-async blocking REDACTED:1459— `fs.readFileSync` in `app.get("/api/info")` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs.
Sync-over-async blocking REDACTED:2899— `fs.existsSync` in `app.put("/api/projects/:name/tasks/:id")` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs.
Sync-over-async blocking REDACTED:2899— `fs.statSync` in `app.put("/api/projects/:name/tasks/:id")` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs.
Sync-over-async blocking REDACTED:3191— `fs.existsSync` in `app.delete("/api/projects/:name/tasks/:id")` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs.
Sync-over-async blocking REDACTED:3191— `fs.unlinkSync` in `app.delete("/api/projects/:name/tasks/:id")` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs.
Sync-over-async blocking REDACTED:3386— `fs.statSync` in `app.get("/api/projects/:name/files/{*filePath}")` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs.
Sync-over-async blocking REDACTED:3390— `fs.statSync` in `app.get("/api/projects/:name/files/{*filePath}")` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs.
Sync-over-async blocking REDACTED:3396— `fs.readFileSync` in `app.get("/api/projects/:name/files/{*filePath}")` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs.
Sync-over-async blocking REDACTED:3438— `fs.existsSync` in `app.put("/api/projects/:name/files/{*filePath}")` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs.
Sync-over-async blocking REDACTED:3438— `fs.mkdirSync` in `app.put("/api/projects/:name/files/{*filePath}")` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs.
Sync-over-async blocking REDACTED:3440— `fs.writeFileSync` in `app.put("/api/projects/:name/files/{*filePath}")` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs.
Sync-over-async blocking REDACTED:3441— `fs.statSync` in `app.put("/api/projects/:name/files/{*filePath}")` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs.
+ 15 more in this group — see findings.md.
R4 · Test Coverage· No test reaches this file · ×40
No test reaches this file scripts/setup.mjs:1— No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
No test reaches this file dashboard/test-setup-linux-systemd.mjs:1— No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
No test reaches this file dashboard/test-snippets-doctor.js:1— No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
No test reaches this file dashboard/test-t168-t177-integration.js:1— No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
No test reaches this file dashboard/test-dashboard-shell.js:1— No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
No test reaches this file dashboard/test-hzl-integration.js:1— No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
No test reaches this file scripts/systemd-config.mjs:1— No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
No test reaches this file dashboard/test-snippets-integration.js:1— No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
No test reaches this file dashboard/test-work-state-e2e.js:1— No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
No test reaches this file dashboard/test-setup-macos-launchd.mjs:1— No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
No test reaches this file REDACTED:1— No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
No test reaches this file dashboard/test-dashboard-api.mjs:1— No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
No test reaches this file dashboard/test-work-state-backend.js:1— No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
No test reaches this file scripts/v5-demo-fixture.mjs:1— No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
No test reaches this file dashboard/test-specify-clarify-regression.js:1— No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
No test reaches this file dashboard/test-canvas-links.js:1— No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
No test reaches this file dashboard/test-canvas-update-e2e.js:1— No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
No test reaches this file dashboard/test-canvas-migration-ui.mjs:1— No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
No test reaches this file dashboard/test-dashboard-race-regressions-e2e.js:1— No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
No test reaches this file dashboard/test-canvas-db-import.js:1— No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
No test reaches this file dashboard/test-canvas-dblclick.js:1— No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
No test reaches this file dashboard/test-canvas-db-store.js:1— No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
No test reaches this file dashboard/test-canvas-db-endpoints.js:1— No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
No test reaches this file hooks/project-context/handler.js:1— No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
No test reaches this file dashboard/test-work-state.mjs:1— No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
Hotspot: REDACTED REDACTED:2875— REDACTED changed 70 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 92 in server.app.put("/api/projects/:name/tasks/:id") at line 2875. 29 of those changes were fix/bug commits, and the other 41 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-21..2026-09-19, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-06-21 14:00:14 +02:00' --until='2026-09-19 14:00:14 +02:00' --full-history --no-merges -- REDACTED`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: dashboard/src/components/DetailPanel.jsx dashboard/src/components/DetailPanel.jsx:182— dashboard/src/components/DetailPanel.jsx changed 18 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 296 in DetailPanel.DetailPanel at line 182. 10 of those changes were fix/bug commits, so the churn is repair rather than feature work. 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-21..2026-09-19, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-06-21 14:00:14 +02:00' --until='2026-09-19 14:00:14 +02:00' --full-history --no-merges -- dashboard/src/components/DetailPanel.jsx`: 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: dashboard/hzl-service.js dashboard/hzl-service.js:1431— dashboard/hzl-service.js changed 29 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 84 in hzl-service.updateTask at line 1431. 13 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-21..2026-09-19, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-06-21 14:00:14 +02:00' --until='2026-09-19 14:00:14 +02:00' --full-history --no-merges -- dashboard/hzl-service.js`: 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: dashboard/src/context/DashboardContext.jsx dashboard/src/context/DashboardContext.jsx:75— dashboard/src/context/DashboardContext.jsx changed 12 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 142 in DashboardContext.DashboardProvider at line 75. 9 of those changes were fix/bug commits, so the churn is repair rather than feature work. 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-21..2026-09-19, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-06-21 14:00:14 +02:00' --until='2026-09-19 14:00:14 +02:00' --full-history --no-merges -- dashboard/src/context/DashboardContext.jsx`: 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: dashboard/src/pages/TasksView.jsx dashboard/src/pages/TasksView.jsx:1170— dashboard/src/pages/TasksView.jsx changed 9 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 158 in TasksView.TasksView at line 1170. 6 of those changes were fix/bug commits, so the churn is repair rather than feature work. 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-21..2026-09-19, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-06-21 14:00:14 +02:00' --until='2026-09-19 14:00:14 +02:00' --full-history --no-merges -- dashboard/src/pages/TasksView.jsx`: 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: dashboard/src/components/ActiveAgentsBar.jsx dashboard/src/components/ActiveAgentsBar.jsx:285— dashboard/src/components/ActiveAgentsBar.jsx changed 11 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 80 in ActiveAgentsBar.ActiveAgentsBar at line 285. 7 of those changes were fix/bug commits, so the churn is repair rather than feature work. 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-21..2026-09-19, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-06-21 14:00:14 +02:00' --until='2026-09-19 14:00:14 +02:00' --full-history --no-merges -- dashboard/src/components/ActiveAgentsBar.jsx`: 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: dashboard/src/components/ProjectBundleModals.jsx dashboard/src/components/ProjectBundleModals.jsx:494— dashboard/src/components/ProjectBundleModals.jsx changed 10 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 84 in ProjectBundleModals.ImportProjectModal at line 494. 9 of those changes were fix/bug commits, so the churn is repair rather than feature work. 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-21..2026-09-19, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-06-21 14:00:14 +02:00' --until='2026-09-19 14:00:14 +02:00' --full-history --no-merges -- dashboard/src/components/ProjectBundleModals.jsx`: 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: dashboard/src/pages/FilesView.jsx dashboard/src/pages/FilesView.jsx:466— dashboard/src/pages/FilesView.jsx changed 4 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 173 in FilesView.FilesView at line 466. 2 of those changes were fix/bug commits, and the other 2 changed it for other reasons — this file is under both repair and feature pressure. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-06-21..2026-09-19, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-06-21 14:00:14 +02:00' --until='2026-09-19 14:00:14 +02:00' --full-history --no-merges -- dashboard/src/pages/FilesView.jsx`: 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: dashboard/src/components/Sidebar.jsx dashboard/src/components/Sidebar.jsx:201— dashboard/src/components/Sidebar.jsx changed 3 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 147 in Sidebar.Sidebar at line 201. 2 of those changes were fix/bug commits, so the churn is repair rather than feature work. 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-21..2026-09-19, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-06-21 14:00:14 +02:00' --until='2026-09-19 14:00:14 +02:00' --full-history --no-merges -- dashboard/src/components/Sidebar.jsx`: 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: dashboard/src/utils/apiFetch.js dashboard/src/utils/apiFetch.js:37— dashboard/src/utils/apiFetch.js changed 12 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 36 in apiFetch.apiFetch at line 37. 7 of those changes were fix/bug commits, so the churn is repair rather than feature work. 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-21..2026-09-19, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-06-21 14:00:14 +02:00' --until='2026-09-19 14:00:14 +02:00' --full-history --no-merges -- dashboard/src/utils/apiFetch.js`: 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: dashboard/src/utils/dashboardApi.js dashboard/src/utils/dashboardApi.js:131— dashboard/src/utils/dashboardApi.js changed 12 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 26 in dashboardApi.validateTask at line 131. 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-21..2026-09-19, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-06-21 14:00:14 +02:00' --until='2026-09-19 14:00:14 +02:00' --full-history --no-merges -- dashboard/src/utils/dashboardApi.js`: 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: dashboard/test-work-state-api.js dashboard/test-work-state-api.js:12— dashboard/test-work-state-api.js changed 6 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 48 in test-work-state-api.main at line 12. 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-21..2026-09-19, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-06-21 14:00:14 +02:00' --until='2026-09-19 14:00:14 +02:00' --full-history --no-merges -- dashboard/test-work-state-api.js`: 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: dashboard/test-work-state-e2e.js dashboard/test-work-state-e2e.js:112— dashboard/test-work-state-e2e.js changed 6 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 43 in test-work-state-e2e.main at line 112. 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-21..2026-09-19, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-06-21 14:00:14 +02:00' --until='2026-09-19 14:00:14 +02:00' --full-history --no-merges -- dashboard/test-work-state-e2e.js`: 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: dashboard/test-dashboard-race-regressions-e2e.js dashboard/test-dashboard-race-regressions-e2e.js:81— dashboard/test-dashboard-race-regressions-e2e.js changed 4 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 63 in test-dashboard-race-regressions-e2e.main at line 81. 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-21..2026-09-19, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-06-21 14:00:14 +02:00' --until='2026-09-19 14:00:14 +02:00' --full-history --no-merges -- dashboard/test-dashboard-race-regressions-e2e.js`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: scripts/setup.mjs scripts/setup.mjs:448— scripts/setup.mjs changed 11 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 22 in setup.readExistingServiceConfig at line 448. 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-21..2026-09-19, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-06-21 14:00:14 +02:00' --until='2026-09-19 14:00:14 +02:00' --full-history --no-merges -- scripts/setup.mjs`: 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: dashboard/src/components/SpecifyStepper.jsx dashboard/src/components/SpecifyStepper.jsx:40— dashboard/src/components/SpecifyStepper.jsx changed 2 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 108 in SpecifyStepper.SpecifyStepper at line 40. 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-21..2026-09-19, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-06-21 14:00:14 +02:00' --until='2026-09-19 14:00:14 +02:00' --full-history --no-merges -- dashboard/src/components/SpecifyStepper.jsx`: 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: dashboard/rules-api.js dashboard/rules-api.js:217— dashboard/rules-api.js changed 6 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 33 in rules-api.buildOperationalTaskStateMarkdown at line 217. 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-21..2026-09-19, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-06-21 14:00:14 +02:00' --until='2026-09-19 14:00:14 +02:00' --full-history --no-merges -- dashboard/rules-api.js`: 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: dashboard/project-bundle-validator.js dashboard/project-bundle-validator.js:313— dashboard/project-bundle-validator.js changed 5 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 36 in project-bundle-validator.validateTasks at line 313. 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-21..2026-09-19, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-06-21 14:00:14 +02:00' --until='2026-09-19 14:00:14 +02:00' --full-history --no-merges -- dashboard/project-bundle-validator.js`: 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: dashboard/task-creation-policy.js dashboard/task-creation-policy.js:107— dashboard/task-creation-policy.js changed 4 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 38 in task-creation-policy.evaluateCreationPolicy at line 107. 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-21..2026-09-19, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-06-21 14:00:14 +02:00' --until='2026-09-19 14:00:14 +02:00' --full-history --no-merges -- dashboard/task-creation-policy.js`: 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: dashboard/test-project-bundle-export.js dashboard/test-project-bundle-export.js:95— dashboard/test-project-bundle-export.js changed 8 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 18 in test-project-bundle-export.main at line 95. 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-21..2026-09-19, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-06-21 14:00:14 +02:00' --until='2026-09-19 14:00:14 +02:00' --full-history --no-merges -- dashboard/test-project-bundle-export.js`: 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: dashboard/test-setup-linux-systemd.mjs dashboard/test-setup-linux-systemd.mjs:107— dashboard/test-setup-linux-systemd.mjs changed 9 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 15 in test-setup-linux-systemd.makeHarness at line 107. 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-21..2026-09-19, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-06-21 14:00:14 +02:00' --until='2026-09-19 14:00:14 +02:00' --full-history --no-merges -- dashboard/test-setup-linux-systemd.mjs`: 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: dashboard/project-bundle-import.js dashboard/project-bundle-import.js:849— dashboard/project-bundle-import.js changed 4 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 33 in ProjectBundleImporter.importBundle at line 849. 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-21..2026-09-19, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-06-21 14:00:14 +02:00' --until='2026-09-19 14:00:14 +02:00' --full-history --no-merges -- dashboard/project-bundle-import.js`: 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: dashboard/test-canvas-update-e2e.js dashboard/test-canvas-update-e2e.js:171— dashboard/test-canvas-update-e2e.js changed 3 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 43 in test-canvas-update-e2e.run at line 171. 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-21..2026-09-19, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-06-21 14:00:14 +02:00' --until='2026-09-19 14:00:14 +02:00' --full-history --no-merges -- dashboard/test-canvas-update-e2e.js`: 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: dashboard/test-overview-api.js dashboard/test-overview-api.js:30— dashboard/test-overview-api.js changed 2 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 64 in test-overview-api.run at line 30. 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-21..2026-09-19, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-06-21 14:00:14 +02:00' --until='2026-09-19 14:00:14 +02:00' --full-history --no-merges -- dashboard/test-overview-api.js`: 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: dashboard/work-state.js dashboard/work-state.js:43— dashboard/work-state.js changed 5 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 25 in work-state.isValidDateString at line 43. 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-21..2026-09-19, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-06-21 14:00:14 +02:00' --until='2026-09-19 14:00:14 +02:00' --full-history --no-merges -- dashboard/work-state.js`: 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.
Swallowed exception (empty catch) dashboard/snippets-doctor.js:646— An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Swallowed exception (empty catch) REDACTED:349— An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Swallowed exception (empty catch) REDACTED:1036— An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Swallowed exception (empty catch) REDACTED:1257— An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Swallowed exception (empty catch) REDACTED:1450— An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Swallowed exception (empty catch) REDACTED:2456— An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Swallowed exception (empty catch) REDACTED:2547— An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Swallowed exception (empty catch) REDACTED:2697— An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Swallowed exception (empty catch) REDACTED:3344— An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Swallowed exception (empty catch) REDACTED:3346— An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Swallowed exception (empty catch) REDACTED:3358— An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Swallowed exception (empty catch) REDACTED:3767— 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) dashboard/project-lifecycle.js:364— 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) dashboard/project-lifecycle.js:634— 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) dashboard/project-bundle-validator.js:621— 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) dashboard/project-bundle-validator.js:625— 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) dashboard/project-bundle-schema.js:262— 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) dashboard/project-bundle-schema.js:269— 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) dashboard/project-bundle-schema.js:277— 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) dashboard/project-bundle-schema.js:313— 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) dashboard/project-bundle-import.js:462— 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) dashboard/project-bundle-import.js:491— 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) dashboard/project-bundle-import.js:542— 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) dashboard/project-bundle-import.js:934— 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) dashboard/project-bundle-import.js:954— 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.
FunctionTooLong: CanvasView.CanvasView REDACTED:80— FunctionTooLong — CanvasView runs 998 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 898 over it, 9.98× 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: FilesView.FilesView dashboard/src/pages/FilesView.jsx:466— FunctionTooLong — FilesView runs 605 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 505 over it, 6.05× 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: Sidebar.Sidebar dashboard/src/components/Sidebar.jsx:201— FunctionTooLong — Sidebar runs 586 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 486 over it, 5.86× 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: DashboardContext.DashboardProvider dashboard/src/context/DashboardContext.jsx:75— FunctionTooLong — DashboardProvider runs 426 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 326 over it, 4.26× 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: SpecifyStepper.SpecifyStepper dashboard/src/components/SpecifyStepper.jsx:40— FunctionTooLong — SpecifyStepper runs 381 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 281 over it, 3.81× 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: SnippetUpgrade.UpgradeModal dashboard/src/components/SnippetUpgrade.jsx:152— FunctionTooLong — UpgradeModal runs 315 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 215 over it, 3.15× 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: ActiveAgentsBar.ActiveAgentsBar dashboard/src/components/ActiveAgentsBar.jsx:285— FunctionTooLong — ActiveAgentsBar runs 272 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 172 over it, 2.72× 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: ProjectBundleModals.ImportProjectModal dashboard/src/components/ProjectBundleModals.jsx:494— FunctionTooLong — ImportProjectModal runs 253 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 153 over it, 2.53× 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: CreateProjectModal.CreateProjectModal dashboard/src/components/CreateProjectModal.jsx:26— FunctionTooLong — CreateProjectModal runs 236 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 136 over it, 2.36× 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: WorkStatePopover.WorkStatePopover dashboard/src/components/WorkStatePopover.jsx:126— FunctionTooLong — WorkStatePopover runs 223 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 123 over it, 2.23× 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: widgets2.MilestonesWidget REDACTED:262— FunctionTooLong — MilestonesWidget runs 214 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 114 over it, 2.14× 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: FilesView.FilePreview dashboard/src/pages/FilesView.jsx:148— FunctionTooLong — FilePreview runs 207 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 107 over it, 2.07× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: ProjectBundleModals.ExportProjectModal dashboard/src/components/ProjectBundleModals.jsx:201— FunctionTooLong — ExportProjectModal runs 183 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 83 over it, 1.83× 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: ProjectActionsMenu.ProjectActionsMenu dashboard/src/components/ProjectActionsMenu.jsx:27— FunctionTooLong — ProjectActionsMenu runs 177 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 77 over it, 1.77× 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: hzl-service.buildHandoffMarkdown dashboard/hzl-service.js:4037— FunctionTooLong — buildHandoffMarkdown runs 176 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 76 over it, 1.76× 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: CanvasMiniMap.CanvasMiniMap REDACTED:37— FunctionTooLong — CanvasMiniMap 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.
FunctionTooLong: MarkdownEditor.MarkdownEditor dashboard/src/components/MarkdownEditor.jsx:157— FunctionTooLong — MarkdownEditor runs 137 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 37 over it, 1.37× 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: SearchPalette.SearchPalette dashboard/src/components/SearchPalette.jsx:19— FunctionTooLong — SearchPalette runs 137 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 37 over it, 1.37× 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: widgets2.NotesWidget REDACTED:681— FunctionTooLong — NotesWidget runs 136 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 36 over it, 1.36× 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: systemd-config.parseSystemdEnvironmentFile scripts/systemd-config.mjs:349— FunctionTooLong — parseSystemdEnvironmentFile runs 129 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 29 over it, 1.29× 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: hzl-service.updateTask dashboard/hzl-service.js:1431— FunctionTooLong — updateTask 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: widgets2.LinksWidget REDACTED:864— FunctionTooLong — LinksWidget 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.
FunctionTooLong: hzl-service.createTaskRaw dashboard/hzl-service.js:1248— FunctionTooLong — createTaskRaw runs 115 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 15 over it, 1.15× 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: TrashPanel.TrashPanel dashboard/src/components/TrashPanel.jsx:22— FunctionTooLong — TrashPanel runs 113 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 13 over it, 1.13× 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: MoveTaskModal.MoveTaskModal dashboard/src/components/MoveTaskModal.jsx:15— FunctionTooLong — MoveTaskModal runs 112 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 12 over it, 1.12× 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.
Repeated repair: dashboard/test-dashboard-api.mjs dashboard/test-dashboard-api.mjs:341— dashboard/test-dashboard-api.mjs changed 8 times in last 90 days and 7 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 6 (its worst body is test-dashboard-api.fetch at line 341), 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(T-452-7): tolerate retired blocked projection”; “fix(T-445): close stale Files and auth race gaps”; “fix(T-443-5): close final no-go gaps”; “fix(T-443-4): close frontend high re-review findings”. 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-21..2026-09-19, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-06-21 14:00:14 +02:00' --until='2026-09-19 14:00:14 +02:00' --full-history --no-merges -- dashboard/test-dashboard-api.mjs`: 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: dashboard/src/bootstrap.js dashboard/src/bootstrap.js:30— dashboard/src/bootstrap.js changed 7 times in last 90 days and 7 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 5 (its worst body is bootstrap.document.addEventListener("click") at line 30), 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(T-445): ignore domain 403s in auth breaker”; “fix(T-445): close stale Files and auth race gaps”; “fix(T-445): close auth and files lane review gaps”; “fix(dashboard): finalize StrictMode coordination and defer microtask removal (T-440 finalize)”. 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-21..2026-09-19, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-06-21 14:00:14 +02:00' --until='2026-09-19 14:00:14 +02:00' --full-history --no-merges -- dashboard/src/bootstrap.js`: 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: dashboard/test-work-state-backend.js dashboard/test-work-state-backend.js:34— dashboard/test-work-state-backend.js changed 8 times in last 90 days and 6 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 5 (its worst body is test-work-state-backend.main at line 34), 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(T-452-7): tolerate retired blocked projection”; “fix(T-443-5): close final no-go gaps”; “fix(T-443-5): finish integration threshold and coverage docs”; “fix(T-443-3): add transient stuck indicator actions”. 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-21..2026-09-19, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-06-21 14:00:14 +02:00' --until='2026-09-19 14:00:14 +02:00' --full-history --no-merges -- dashboard/test-work-state-backend.js`: 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: dashboard/test-project-bundle-ui-e2e.js dashboard/test-project-bundle-ui-e2e.js:15— dashboard/test-project-bundle-ui-e2e.js changed 6 times in last 90 days and 6 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 2 (its worst body is test-project-bundle-ui-e2e.jsonFile at line 15), UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “fix: complete safe sensitive bundle imports”; “fix: surface bundle integrity recovery diagnostics”; “fix: harden export recovery diagnostics”; “fix: recover sensitive project exports safely”. 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-21..2026-09-19, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-06-21 14:00:14 +02:00' --until='2026-09-19 14:00:14 +02:00' --full-history --no-merges -- dashboard/test-project-bundle-ui-e2e.js`: 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: dashboard/src/utils/activeAgents.js dashboard/src/utils/activeAgents.js:73— dashboard/src/utils/activeAgents.js changed 7 times in last 90 days and 5 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 13 (its worst body is activeAgents.buildActiveAgentRows at line 73), UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “fix: constrain active agent strip overflow”; “fix(T-457): one claim predicate for the overview widgets too”; “fix(T-455): trim the claim chip, centre the avatar, shrink the route list”; “fix(T-448-1): align lease health stale threshold”. 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-21..2026-09-19, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-06-21 14:00:14 +02:00' --until='2026-09-19 14:00:14 +02:00' --full-history --no-merges -- dashboard/src/utils/activeAgents.js`: 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: dashboard/test-project-bundle-export-api.js dashboard/test-project-bundle-export-api.js:13— dashboard/test-project-bundle-export-api.js changed 6 times in last 90 days and 5 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 9 (its worst body is test-project-bundle-export-api.main at line 13), 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: surface bundle integrity recovery diagnostics”; “fix: close sensitive export proxy bypass”; “fix: harden export recovery diagnostics”; “fix: recover sensitive project exports safely”. 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-21..2026-09-19, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-06-21 14:00:14 +02:00' --until='2026-09-19 14:00:14 +02:00' --full-history --no-merges -- dashboard/test-project-bundle-export-api.js`: 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: dashboard/test-active-agents.mjs dashboard/test-active-agents.mjs:19— dashboard/test-active-agents.mjs changed 6 times in last 90 days and 5 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 1 (its worst body is test-active-agents.claim at line 19), 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: constrain active agent strip overflow”; “fix(T-457): one claim predicate for the overview widgets too”; “fix(T-455): trim the claim chip, centre the avatar, shrink the route list”; “fix(T-448-1): align lease health stale threshold”. 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-21..2026-09-19, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-06-21 14:00:14 +02:00' --until='2026-09-19 14:00:14 +02:00' --full-history --no-merges -- dashboard/test-active-agents.mjs`: 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: dashboard/test-setup-macos-launchd.mjs dashboard/test-setup-macos-launchd.mjs:130— dashboard/test-setup-macos-launchd.mjs changed 6 times in last 90 days and 4 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 10 (its worst body is test-setup-macos-launchd.makeHarness.artifact at line 130), 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(setup): harden service config preservation”; “fix(setup): harden escape parsing and launchd log checks”; “fix(setup): harden service config roundtrip”; “fix(setup): address service preservation review”. 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-21..2026-09-19, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-06-21 14:00:14 +02:00' --until='2026-09-19 14:00:14 +02:00' --full-history --no-merges -- dashboard/test-setup-macos-launchd.mjs`: 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: dashboard/test-auth-middleware.js dashboard/test-auth-middleware.js:42— dashboard/test-auth-middleware.js 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 6 (its worst body is test-auth-middleware.run at line 42), UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “test: fix remaining scanner fixture hits”; “fix(T-450-2): restore trusted principal import”; “fix(T-441): verify trusted proxy before CF rate keys”; “fix(auth): secure multi-bot Telegram sessions (T-441)”. 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-21..2026-09-19, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-06-21 14:00:14 +02:00' --until='2026-09-19 14:00:14 +02:00' --full-history --no-merges -- dashboard/test-auth-middleware.js`: 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: dashboard/src/state/taskMutations.mjs dashboard/src/state/taskMutations.mjs:53— dashboard/src/state/taskMutations.mjs 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 11 (its worst body is taskMutations.mutate at line 53), 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(T-454): stop a stale poll from reverting a just-set work state”; “fix(T-443-5): close final no-go gaps”; “fix(T-443-4): close frontend high re-review findings”; “fix(T-443-4): close frontend work-state review findings”. 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-21..2026-09-19, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-06-21 14:00:14 +02:00' --until='2026-09-19 14:00:14 +02:00' --full-history --no-merges -- dashboard/src/state/taskMutations.mjs`: 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: dashboard/test-work-state.js dashboard/test-work-state.js:78— dashboard/test-work-state.js 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 2 (its worst body is test-work-state.assert.throws() at line 78), 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(T-443-5): close final no-go gaps”; “fix(T-443): scope stuck routing to active claims”; “fix(T-443): reject invalid scheduler datetimes”; “fix(T-443): close backend work-state review findings”. 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-21..2026-09-19, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-06-21 14:00:14 +02:00' --until='2026-09-19 14:00:14 +02:00' --full-history --no-merges -- dashboard/test-work-state.js`: 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: REDACTED REDACTED:109— REDACTED changed 4 times in last 90 days and 3 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 10 (its worst body is test-t441-security-review-findings.run at line 109), UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “fix(T-441): verify trusted proxy before CF rate keys”; “fix(T-441): close final security review findings”; “fix(T-441): close auth security review gaps”. 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-21..2026-09-19, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-06-21 14:00:14 +02:00' --until='2026-09-19 14:00:14 +02:00' --full-history --no-merges -- REDACTED`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Repeated repair: dashboard/src/components/LeaseIndicator.jsx dashboard/src/components/LeaseIndicator.jsx:27— dashboard/src/components/LeaseIndicator.jsx changed 4 times in last 90 days and 3 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 3 (its worst body is LeaseIndicator.computeHealth at line 27), 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(T-448-1): thread scheduler lease threshold through task UI”; “fix: make stale lease tooltip threshold-agnostic”; “fix(T-448-1): retain active claims with lease health”. 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-21..2026-09-19, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-06-21 14:00:14 +02:00' --until='2026-09-19 14:00:14 +02:00' --full-history --no-merges -- dashboard/src/components/LeaseIndicator.jsx`: 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: dashboard/test-work-state.mjs dashboard/test-work-state.mjs:276— dashboard/test-work-state.mjs changed 4 times in last 90 days and 3 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 1 (its worst body is dispatchEvent at line 276), 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(T-443-5): close final no-go gaps”; “fix(T-443-4): close frontend high re-review findings”; “fix(T-443-4): close frontend work-state review findings”. 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-21..2026-09-19, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-06-21 14:00:14 +02:00' --until='2026-09-19 14:00:14 +02:00' --full-history --no-merges -- dashboard/test-work-state.mjs`: 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: dashboard/test-app-state-bridge.mjs dashboard/test-app-state-bridge.mjs:6— dashboard/test-app-state-bridge.mjs changed 4 times in last 90 days and 3 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 1 (its worst body is CustomEvent.constructor at line 6), 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(T-443-4): close frontend work-state review findings”; “T-440: Fix fatal auth Retry and add E2E assertion”; “fix(dashboard): robust race/fatal API state handling (T-440 fixup)”. 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-21..2026-09-19, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-06-21 14:00:14 +02:00' --until='2026-09-19 14:00:14 +02:00' --full-history --no-merges -- dashboard/test-app-state-bridge.mjs`: 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: dashboard/test-project-bundle-import-preview.js dashboard/test-project-bundle-import-preview.js:150— dashboard/test-project-bundle-import-preview.js changed 3 times in last 90 days and 3 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 4 (its worst body is test-project-bundle-import-preview.rawRequest at line 150), 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: complete safe sensitive bundle imports”; “fix: whitelist preview bundle counts”; “fix: harden project bundle preview redaction”. 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-21..2026-09-19, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-06-21 14:00:14 +02:00' --until='2026-09-19 14:00:14 +02:00' --full-history --no-merges -- dashboard/test-project-bundle-import-preview.js`: 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: dashboard/host-utils.js dashboard/host-utils.js:17— dashboard/host-utils.js changed 3 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 7 (its worst body is host-utils.isLoopbackHost at line 17), 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: close sensitive export proxy bypass”; “fix: harden export recovery diagnostics”; “fix: recover sensitive project exports safely”. 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-21..2026-09-19, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-06-21 14:00:14 +02:00' --until='2026-09-19 14:00:14 +02:00' --full-history --no-merges -- dashboard/host-utils.js`: 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: dashboard/test-host-utils.js dashboard/test-host-utils.js:16— dashboard/test-host-utils.js changed 3 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 2 (its worst body is test-host-utils.ok at line 16), 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: close sensitive export proxy bypass”; “fix: harden export recovery diagnostics”; “fix: recover sensitive project exports safely”. 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-21..2026-09-19, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-06-21 14:00:14 +02:00' --until='2026-09-19 14:00:14 +02:00' --full-history --no-merges -- dashboard/test-host-utils.js`: 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: dashboard/src/state/appStore.mjs dashboard/src/state/appStore.mjs:72— dashboard/src/state/appStore.mjs changed 3 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 appStore.installAppStateProxy at line 72), 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(T-448-1): align lease health stale threshold”; “fix(auth): secure multi-bot Telegram sessions (T-441)”; “fix(dashboard): surface API failures and retry (T-440)”. 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-21..2026-09-19, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-06-21 14:00:14 +02:00' --until='2026-09-19 14:00:14 +02:00' --full-history --no-merges -- dashboard/src/state/appStore.mjs`: 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: dashboard/test-t445-rate-limit.mjs dashboard/test-t445-rate-limit.mjs:190— dashboard/test-t445-rate-limit.mjs changed 3 times in last 90 days and 3 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 4 (its worst body is test-t445-rate-limit.assert.rejects("429 exposes structured scope and Retry-After metadata to the client") at line 190), 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(T-445): ignore domain 403s in auth breaker”; “fix(T-445): close stale Files and auth race gaps”; “fix(T-445): close auth and files lane review gaps”. 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-21..2026-09-19, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-06-21 14:00:14 +02:00' --until='2026-09-19 14:00:14 +02:00' --full-history --no-merges -- dashboard/test-t445-rate-limit.mjs`: 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: dashboard/src/state/connectionState.mjs dashboard/src/state/connectionState.mjs:20— dashboard/src/state/connectionState.mjs changed 3 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 7 (its worst body is connectionState.classifyConnectionError at line 20), 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: “T-440: Fix fatal auth Retry and add E2E assertion”; “fix(dashboard): robust race/fatal API state handling (T-440 fixup)”; “fix(dashboard): harden API recovery races (T-440)”. 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-21..2026-09-19, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-06-21 14:00:14 +02:00' --until='2026-09-19 14:00:14 +02:00' --full-history --no-merges -- dashboard/src/state/connectionState.mjs`: 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: dashboard/test-connection-state.mjs dashboard/test-connection-state.mjs:87— dashboard/test-connection-state.mjs changed 3 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 3 (its worst body is test-connection-state.assert.rejects("apiJson preserves HTTP status for auth classification") at line 87), 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: “T-440: Fix fatal auth Retry and add E2E assertion”; “fix(dashboard): robust race/fatal API state handling (T-440 fixup)”; “fix(dashboard): harden API recovery races (T-440)”. 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-21..2026-09-19, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-06-21 14:00:14 +02:00' --until='2026-09-19 14:00:14 +02:00' --full-history --no-merges -- dashboard/test-connection-state.mjs`: 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.
AC6 · Visual & motion safety· Animation without a prefers-reduced-motion guard · ×16
Animation without a prefers-reduced-motion guard dashboard/src/components/Spinner.jsx:20— <svg> moves — its `animate-spin` utility runs with no motion-safe:/motion-reduce: variant — and nothing reads prefers-reduced-motion for it, so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Gate it on @media (prefers-reduced-motion: no-preference) or motion-safe:.
Animation without a prefers-reduced-motion guard dashboard/styles/canvas.css:179— `.toolbar-popover` moves (`animation: toolbarPopIn 0.12s ease-out`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce.
Animation without a prefers-reduced-motion guard dashboard/styles/canvas.css:269— `.canvas-sidebar` moves (`transition: transform 0.2s ease-out`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce.
Animation without a prefers-reduced-motion guard dashboard/styles/dashboard.css:1047— `.task-card.new-card` moves (`animation: rise var(--duration-slow) var(--ease-out) both`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce.
Animation without a prefers-reduced-motion guard dashboard/styles/dashboard.css:1050— `.task-card.removing` moves (`animation: shrink 0.25s var(--ease-out) forwards`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce.
Animation without a prefers-reduced-motion guard dashboard/styles/dashboard.css:1215— `.stale-warning` moves (`animation: stale-pulse 2s infinite ease-in-out`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce.
Animation without a prefers-reduced-motion guard dashboard/styles/dashboard.css:1328— `.priority-popover` moves (`animation: popIn var(--duration-fast) var(--ease-out)`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce.
Animation without a prefers-reduced-motion guard dashboard/styles/dashboard.css:1622— `.status-popover` moves (`animation: popIn var(--duration-fast) var(--ease-out)`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce.
Animation without a prefers-reduced-motion guard dashboard/styles/dashboard.css:1689— `.toast` moves (`animation: slideUp 0.25s var(--ease-out)`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce.
Animation without a prefers-reduced-motion guard dashboard/styles/dashboard.css:1696— `.toast.removing` moves (`animation: slideDown 0.2s var(--ease-out) forwards`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce.
Animation without a prefers-reduced-motion guard dashboard/styles/dashboard.css:1700— `.toast-spinner` moves (`animation: spin 0.8s linear infinite`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce.
Animation without a prefers-reduced-motion guard dashboard/styles/dashboard.css:1704— `.spin` moves (`animation: spin 0.8s linear infinite`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce.
Animation without a prefers-reduced-motion guard dashboard/styles/dashboard.css:1717— `.modal` moves (`animation: modalIn 0.2s var(--ease-out)`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce.
Animation without a prefers-reduced-motion guard dashboard/styles/dashboard.css:2146— `.sidebar` moves (`transition: transform 0.25s ease, box-shadow 0.25s ease`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce.
Animation without a prefers-reduced-motion guard dashboard/styles/dashboard.css:2424— `.color-popover` moves (`animation: popIn var(--duration-normal) var(--ease-out)`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce.
Animation without a prefers-reduced-motion guard dashboard/styles/dashboard.css:2564— `.upgrade-modal` moves (`animation: snippetModalIn 0.22s var(--ease-out)`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce.
FileTooLong: REDACTED REDACTED— FileTooLong — 3279 significant lines (blank, comment-only and punctuation-only lines excluded; the length bar is tripled for a single-responsibility module of 4 or fewer top-level units). The bar is 500 significant lines; this is 2779 over it, 6.56× 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: dashboard/hzl-service.js dashboard/hzl-service.js— FileTooLong — 3017 significant lines (blank, comment-only and punctuation-only lines excluded; the length bar is tripled for a single-responsibility module of 4 or fewer top-level units). The bar is 500 significant lines; this is 2517 over it, 6.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: pages/TasksView.jsx dashboard/src/pages/TasksView.jsx— FileTooLong — 1463 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 963 over it, 2.93× 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: components/DetailPanel.jsx dashboard/src/components/DetailPanel.jsx— FileTooLong — 1281 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 781 over it, 2.56× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: REDACTED REDACTED— FileTooLong — 1087 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 587 over it, 2.17× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: REDACTED REDACTED— FileTooLong — 1038 significant lines (blank, comment-only and punctuation-only lines excluded), about 96% of them inside a single declaration: CanvasView (80-1442). The bar is 500 significant lines; this is 538 over it, 2.08× the bar. Moving the declarations that sit BESIDE it into sibling files will not shorten this file. Extract from INSIDE that declaration instead: lift each cohesive group of its body — the parts that share the same inputs and are named together — into its own unit in a sibling file, and have the original call them.
FileTooLong: pages/FilesView.jsx dashboard/src/pages/FilesView.jsx— FileTooLong — 966 significant lines (blank, comment-only and punctuation-only lines excluded), about 63% of them inside a single declaration: FilesView (466-1217). The bar is 500 significant lines; this is 466 over it, 1.93× the bar. Moving the declarations that sit BESIDE it into sibling files will not shorten this file. Extract from INSIDE that declaration instead: lift each cohesive group of its body — the parts that share the same inputs and are named together — into its own unit in a sibling file, and have the original call them.
FileTooLong: scripts/setup.mjs scripts/setup.mjs— FileTooLong — 821 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 321 over it, 1.64× 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: components/Sidebar.jsx dashboard/src/components/Sidebar.jsx— FileTooLong — 794 significant lines (blank, comment-only and punctuation-only lines excluded), about 74% of them inside a single declaration: Sidebar (201-991). The bar is 500 significant lines; this is 294 over it, 1.59× the bar. Moving the declarations that sit BESIDE it into sibling files will not shorten this file. Extract from INSIDE that declaration instead: lift each cohesive group of its body — the parts that share the same inputs and are named together — into its own unit in a sibling file, and have the original call them.
FileTooLong: dashboard/project-bundle-import.js dashboard/project-bundle-import.js— FileTooLong — 746 significant lines (blank, comment-only and punctuation-only lines excluded; the length bar is tripled for a single-responsibility module of 4 or fewer top-level units), about 77% of them inside a single declaration: ProjectBundleImporter (217-966). The bar is 500 significant lines; this is 246 over it, 1.49× the bar. Moving the declarations that sit BESIDE it into sibling files will not shorten this file. Extract from INSIDE that declaration instead: lift each cohesive group of its body — the parts that share the same inputs and are named together — into its own unit in a sibling file, and have the original call them.
FileTooLong: components/SnippetUpgrade.jsx dashboard/src/components/SnippetUpgrade.jsx— FileTooLong — 736 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 236 over it, 1.47× 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: components/ProjectBundleModals.jsx dashboard/src/components/ProjectBundleModals.jsx— FileTooLong — 665 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 165 over it, 1.33× 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: dashboard/snippets-doctor.js dashboard/snippets-doctor.js— FileTooLong — 626 significant lines (blank, comment-only and punctuation-only lines excluded; the length bar is tripled for a single-responsibility module of 4 or fewer top-level units). The bar is 500 significant lines; this is 126 over it, 1.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: REDACTED REDACTED— FileTooLong — 611 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 111 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: dashboard/project-bundle-validator.js dashboard/project-bundle-validator.js— FileTooLong — 508 significant lines (blank, comment-only and punctuation-only lines excluded; the length bar is tripled for a single-responsibility module of 4 or fewer top-level units). The bar is 500 significant lines; this is 8 over it, 1.02× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
Focus outline removed inline dashboard/src/components/Button.jsx:41— <button> takes keyboard focus, and its outline-none utility removes the focus ring with no focus-state ring, shadow, border or outline utility in its place. Add one (e.g. focus-visible:ring-2).
Focus outline removed inline dashboard/src/components/ClaimStateLine.jsx:135— <button> takes keyboard focus, and its outline-none utility removes the focus ring with no focus-state ring, shadow, border or outline utility in its place. Add one (e.g. focus-visible:ring-2).
Focus outline removed inline dashboard/src/components/DetailPanel.jsx:1014— <textarea> takes keyboard focus, and its outline-none utility removes the focus ring with no focus-state ring, shadow, border or outline utility in its place. Add one (e.g. focus-visible:ring-2).
Focus outline removed inline dashboard/src/components/DetailPanel.jsx:1535— <input> takes keyboard focus, and its outline-none utility removes the focus ring with no focus-state ring, shadow, border or outline utility in its place. Add one (e.g. focus-visible:ring-2).
Focus outline removed inline dashboard/src/components/Input.jsx:20— <input> takes keyboard focus, and its outline-none utility removes the focus ring with no focus-state ring, shadow, border or outline utility in its place. Add one (e.g. focus-visible:ring-2).
Focus outline removed inline dashboard/src/components/SearchBar.jsx:28— <input> takes keyboard focus, and its outline-none utility removes the focus ring with no focus-state ring, shadow, border or outline utility in its place. Add one (e.g. focus-visible:ring-2).
Focus outline removed inline dashboard/src/components/Textarea.jsx:16— <textarea> takes keyboard focus, and its outline-none utility removes the focus ring with no focus-state ring, shadow, border or outline utility in its place. Add one (e.g. focus-visible:ring-2).
Focus outline removed inline dashboard/src/components/TrashPanel.jsx:107— <button> takes keyboard focus, and its outline-none utility removes the focus ring with no focus-state ring, shadow, border or outline utility in its place. Add one (e.g. focus-visible:ring-2).
Focus outline removed inline dashboard/src/components/WorkStateChip.jsx:53— <button> takes keyboard focus, and its outline-none utility removes the focus ring with no focus-state ring, shadow, border or outline utility in its place. Add one (e.g. focus-visible:ring-2).
Focus outline removed inline dashboard/src/components/WorkStateChip.jsx:70— <button> takes keyboard focus, and its outline-none utility removes the focus ring with no focus-state ring, shadow, border or outline utility in its place. Add one (e.g. focus-visible:ring-2).
Outbound HTTP without resilience dashboard/github.js:36— `fetch(` makes an outbound HTTP call, and nothing bounds it: no timeout, deadline, retry or circuit breaker is set for it here, and the client has no process-wide default. A slow or failing dependency will hold this service's request, thread or connection until the call gives up on its own — or never, for a client with no default timeout.
Outbound HTTP without resilience dashboard/scripts/migrate-canvas-to-db.mjs:44— `fetch(` makes an outbound HTTP call, and nothing bounds it: no timeout, deadline, retry or circuit breaker is set for it here, and the client has no process-wide default. A slow or failing dependency will hold this service's request, thread or connection until the call gives up on its own — or never, for a client with no default timeout.
Outbound HTTP without resilience dashboard/src/utils/appUpdate.mjs:32— `fetchImpl(` makes an outbound HTTP call, and nothing bounds it: no timeout, deadline, retry or circuit breaker is set for it here, and the client has no process-wide default. A slow or failing dependency will hold this service's request, thread or connection until the call gives up on its own — or never, for a client with no default timeout.
Outbound HTTP without resilience dashboard/src/utils/appUpdate.mjs:54— `fetchImpl(` makes an outbound HTTP call, and nothing bounds it: no timeout, deadline, retry or circuit breaker is set for it here, and the client has no process-wide default. A slow or failing dependency will hold this service's request, thread or connection until the call gives up on its own — or never, for a client with no default timeout.
Outbound HTTP without resilience dashboard/src/utils/appUpdate.mjs:91— `fetchImpl(` makes an outbound HTTP call, and nothing bounds it: no timeout, deadline, retry or circuit breaker is set for it here, and the client has no process-wide default. A slow or failing dependency will hold this service's request, thread or connection until the call gives up on its own — or never, for a client with no default timeout.
Outbound HTTP without resilience dashboard/src/utils/appUpdate.mjs:93— `fetchImpl(` makes an outbound HTTP call, and nothing bounds it: no timeout, deadline, retry or circuit breaker is set for it here, and the client has no process-wide default. A slow or failing dependency will hold this service's request, thread or connection until the call gives up on its own — or never, for a client with no default timeout.
Outbound HTTP without resilience dashboard/src/utils/canvasMigration.mjs:37— `fetchImpl(` makes an outbound HTTP call, and nothing bounds it: no timeout, deadline, retry or circuit breaker is set for it here, and the client has no process-wide default. A slow or failing dependency will hold this service's request, thread or connection until the call gives up on its own — or never, for a client with no default timeout.
Outbound HTTP without resilience dashboard/src/utils/canvasMigration.mjs:53— `fetchImpl(` makes an outbound HTTP call, and nothing bounds it: no timeout, deadline, retry or circuit breaker is set for it here, and the client has no process-wide default. A slow or failing dependency will hold this service's request, thread or connection until the call gives up on its own — or never, for a client with no default timeout.
Outbound HTTP without resilience dashboard/tools/ov-audit.mjs:12— `fetch(` makes an outbound HTTP call, and nothing bounds it: no timeout, deadline, retry or circuit breaker is set for it here, and the client has no process-wide default. A slow or failing dependency will hold this service's request, thread or connection until the call gives up on its own — or never, for a client with no default timeout.
Outbound HTTP without resilience dashboard/tools/ov-audit.mjs:36— `fetch(` makes an outbound HTTP call, and nothing bounds it: no timeout, deadline, retry or circuit breaker is set for it here, and the client has no process-wide default. A slow or failing dependency will hold this service's request, thread or connection until the call gives up on its own — or never, for a client with no default timeout.
AC6 · Visual & motion safety· Focus outline removed in CSS without a · ×8
Focus outline removed in CSS without a :focus replacement dashboard/styles/canvas.css:357— `.canvas-sidebar-textarea` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible.
Focus outline removed in CSS without a :focus replacement dashboard/styles/dashboard.css:817— `.project-item .proj-rename` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible.
Focus outline removed in CSS without a :focus replacement dashboard/styles/dashboard.css:1570— `.subtask-title-input` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible.
Focus outline removed in CSS without a :focus replacement dashboard/styles/dashboard.css:2027— `.file-editor` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible.
Focus outline removed in CSS without a :focus replacement dashboard/styles/dashboard.css:2040— `.file-editor:focus` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible.
Focus outline removed in CSS without a :focus replacement dashboard/styles/dashboard.css:2352— `.note-textarea` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible.
Focus outline removed in CSS without a :focus replacement dashboard/styles/overview.css:854— `.gh-branch` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible.
Focus outline removed in CSS without a :focus replacement dashboard/styles/overview.css:1046— `.fv-pick` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible.
Swallowed exception (caught, then discarded) dashboard/snippets-doctor.js:290— `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) dashboard/snippets-doctor.js:633— `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) dashboard/snippets-doctor.js:673— `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) REDACTED:1080— `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) REDACTED:3233— `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) dashboard/project-bundle-import-preview.js:290— `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) dashboard/migrations.js:248— `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) dashboard/migrations.js:302— `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.
AC2 · Forms & labels· <Textarea> field component without a label · ×4
<Textarea> field component without a label dashboard/src/components/DetailPanel.jsx:1478— This UI-library field component is named only by a placeholder — a placeholder is not a label (it vanishes as soon as the user types, and many assistive technologies ignore it). Give it a real name whichever way this library supports: a label prop, an aria-label, or an id on the rendered control with a <label htmlFor> pointing at it. For a group of controls, name the group itself (aria-label, or a fieldset with a legend) — labelling each item leaves the set unnamed.
<Textarea> field component without a label dashboard/src/components/DetailPanel.jsx:1646— This UI-library field component is named only by a placeholder — a placeholder is not a label (it vanishes as soon as the user types, and many assistive technologies ignore it). Give it a real name whichever way this library supports: a label prop, an aria-label, or an id on the rendered control with a <label htmlFor> pointing at it. For a group of controls, name the group itself (aria-label, or a fieldset with a legend) — labelling each item leaves the set unnamed.
<Textarea> field component without a label dashboard/src/components/SpecifyStepper.jsx:357— This UI-library field component is named only by a placeholder — a placeholder is not a label (it vanishes as soon as the user types, and many assistive technologies ignore it). Give it a real name whichever way this library supports: a label prop, an aria-label, or an id on the rendered control with a <label htmlFor> pointing at it. For a group of controls, name the group itself (aria-label, or a fieldset with a legend) — labelling each item leaves the set unnamed.
<Textarea> field component without a label dashboard/src/components/SpecifyStepper.jsx:467— This UI-library field component is named only by a placeholder — a placeholder is not a label (it vanishes as soon as the user types, and many assistive technologies ignore it). Give it a real name whichever way this library supports: a label prop, an aria-label, or an id on the rendered control with a <label htmlFor> pointing at it. For a group of controls, name the group itself (aria-label, or a fieldset with a legend) — labelling each item leaves the set unnamed.
ClassTooLong: CanvasView REDACTED:1— ClassTooLong — 998 significant lines (blank, comment-only and punctuation-only lines excluded), 2 methods. The bar is 400 significant lines; this is 598 over it, 2.50× 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: FilesView dashboard/src/pages/FilesView.jsx:1— ClassTooLong — 605 significant lines (blank, comment-only and punctuation-only lines excluded), 16 methods. The bar is 400 significant lines; this is 205 over it, 1.51× 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: Sidebar dashboard/src/components/Sidebar.jsx:1— ClassTooLong — 586 significant lines (blank, comment-only and punctuation-only lines excluded), 12 methods. The bar is 400 significant lines; this is 186 over it, 1.47× 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: ProjectBundleImporter dashboard/project-bundle-import.js:217— ClassTooLong — 578 significant lines (blank, comment-only and punctuation-only lines excluded), 20 methods. The bar is 400 significant lines; this is 178 over it, 1.45× 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.
AC4 · Keyboard semantics· Modal dialog does not manage focus · ×3
Modal dialog does not manage focus dashboard/src/components/ActiveAgentsBar.jsx:242— This <div role="dialog"> is a modal dialog, but nothing moves focus into it when it opens and nothing keeps focus inside it while it is open, so a keyboard or screen-reader user keeps acting on the content behind it (WCAG 2.4.3). Use a native <dialog> opened with showModal(), a dialog component that traps focus, or move focus to the dialog on open, trap Tab inside it (or make the page behind inert) and return focus to the control that opened it on close.
Modal dialog does not manage focus dashboard/src/components/SearchPalette.jsx:103— This <div role="dialog"> is a modal dialog, but focus is moved into it, but nothing keeps it there: Tab walks out to the page behind, so a keyboard or screen-reader user keeps acting on the content behind it (WCAG 2.4.3). Use a native <dialog> opened with showModal(), a dialog component that traps focus, or move focus to the dialog on open, trap Tab inside it (or make the page behind inert) and return focus to the control that opened it on close.
Modal dialog does not manage focus dashboard/src/components/SnippetUpgrade.jsx:381— This <div role="dialog"> is a modal dialog, but nothing moves focus into it when it opens and nothing keeps focus inside it while it is open, so a keyboard or screen-reader user keeps acting on the content behind it (WCAG 2.4.3). Use a native <dialog> opened with showModal(), a dialog component that traps focus, or move focus to the dialog on open, trap Tab inside it (or make the page behind inert) and return focus to the control that opened it on close.
server.app.post("/api/projects/:name/tasks") (cyclomatic 82) REDACTED:2702— server.app.post("/api/projects/:name/tasks") has cyclomatic complexity 82 (threshold 15). Of this number, 75 points are the body's own statements and 7 belong to one function item inside it that branches. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
server.app.post("/api/projects/:name/canvas/promote") (cyclomatic 29) REDACTED:3818— server.app.post("/api/projects/:name/canvas/promote") has cyclomatic complexity 29 (threshold 15). Of this number, 27 points are the body's own statements and 2 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.
server.app.post("/api/projects/:name/files/context") (cyclomatic 17) REDACTED:3461— server.app.post("/api/projects/:name/files/context") 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.
(anonymous) (cognitive 16) REDACTED:1342— (anonymous) has cognitive complexity 16 (threshold 15). Drivers by points: boolean chains 4, error handling 2 (4 pts), if/else 4, loops 1 (2 pts), ternaries 2 (nesting depth added 3). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
(anonymous) (cognitive 16) REDACTED:1758— (anonymous) has cognitive complexity 16 (threshold 15). Drivers by points: if/else 8 (12 pts), error handling 2, boolean chains 1, ternaries 1 (nesting depth added 4). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
(anonymous) (cognitive 16) REDACTED:1889— (anonymous) has cognitive complexity 16 (threshold 15). Drivers by points: if/else 7 (10 pts), boolean chains 3, error handling 2, loops 1 (nesting depth added 3). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
Duplicated block (24 lines × 2 locations) dashboard/test-heal-project.js:306— dashboard/test-heal-project.js:306 · dashboard/test-hzl-integrity.js:211 — 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 (24 lines × 2 locations) dashboard/test-setup-linux-systemd.mjs:21— dashboard/test-setup-linux-systemd.mjs:21 · dashboard/test-setup-macos-launchd.mjs:24 — the 2 copies sit in sibling files in one directory, so check first whether one of them (or an existing module there) already owns this behaviour and the others should call it; otherwise extract it into one module in that directory and have each site call it.
Duplicated block (24 lines × 2 locations) dashboard/test-t168-t177-integration.js:30— dashboard/test-t168-t177-integration.js:30 · dashboard/test-v5-integration.js:21 — the 2 copies sit in sibling files in one directory, so check first whether one of them (or an existing module there) already owns this behaviour and the others should call it; otherwise extract it into one module in that directory and have each site call it.
X2 · Cancellation propagation· Async function without AbortSignal · ×3
Async function without AbortSignal: sendWakeEvent REDACTED:1191— `sendWakeEvent` awaits `fetch(…)` but neither accepts an AbortSignal nor passes one on, so its caller cannot stop the request once it has started. Accept `{ signal }` and pass it through: `fetch(url, { signal })`.
Async function without AbortSignal: gh dashboard/github.js:34— `gh` awaits `fetch(…)` but neither accepts an AbortSignal nor passes one on, so its caller cannot stop the request once it has started. Accept `{ signal }` and pass it through: `fetch(url, { signal })`.
Async function without AbortSignal: api dashboard/scripts/migrate-canvas-to-db.mjs:41— `api` awaits `fetch(…)` but neither accepts an AbortSignal nor passes one on, so its caller cannot stop the request once it has started. Accept `{ signal }` and pass it through: `fetch(url, { signal })`.
server.app.post("/api/specify/sessions/:id/answer") (cyclomatic 34) REDACTED:4149— server.app.post("/api/specify/sessions/:id/answer") has cyclomatic complexity 34 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
server.app.post("/api/specify/sessions/:id/confirm") (cyclomatic 24) REDACTED:4289— server.app.post("/api/specify/sessions/:id/confirm") has cyclomatic complexity 24 (threshold 15). Of this number, 22 points are the body's own statements and 2 belong to one function literal inside it that branches. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
(anonymous) (cyclomatic 24) REDACTED:2598— (anonymous) has cyclomatic complexity 24 (threshold 15). Of this number, 19 points are the body's own statements and 5 belong to 9 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.
(anonymous) (cyclomatic 24) REDACTED:4289— (anonymous) has cyclomatic complexity 24 (threshold 15). Of this number, 22 points are the body's own statements and 2 belong to one function literal inside it that branches. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
(anonymous) (cyclomatic 16) REDACTED:2332— (anonymous) has cyclomatic complexity 16 (threshold 15). Of this number, 12 points are the body's own statements and 4 belong to 4 function items inside it that branch. To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
(anonymous) (cyclomatic 16) REDACTED:4894— (anonymous) has cyclomatic complexity 16 (threshold 15). Of this number, 10 points are the body's own statements and 6 belong to 3 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.
server.app.post("/api/projects/:name/tasks") (cognitive 117) REDACTED:2702— server.app.post("/api/projects/:name/tasks") has cognitive complexity 117 (threshold 15). Drivers by points: if/else 26 (48 pts), boolean chains 29, ternaries 14 (21 pts), error handling 7 (14 pts), loops 2 (5 pts) (nesting depth added 39). Of this number, 105 points are the body's own statements and 12 belong to one function item inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
server.app.post("/api/projects/:name/canvas/promote") (cognitive 24) REDACTED:3818— server.app.post("/api/projects/:name/canvas/promote") has cognitive complexity 24 (threshold 15). Drivers by points: boolean chains 13, if/else 6 (7 pts), error handling 2 (3 pts), ternaries 1 (nesting depth added 2). Of this number, 22 points are the body's own statements and 2 belong to one function literal inside it that branches. To reduce it, 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.
server.app.post("/api/specify/sessions/:id/answer") (cognitive 38) REDACTED:4149— server.app.post("/api/specify/sessions/:id/answer") has cognitive complexity 38 (threshold 15). Drivers by points: if/else 16 (22 pts), boolean chains 15, error handling 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.
server.app.post("/api/specify/sessions/:id/confirm") (cognitive 32) REDACTED:4289— server.app.post("/api/specify/sessions/:id/confirm") has cognitive complexity 32 (threshold 15). Drivers by points: boolean chains 9, if/else 6 (9 pts), ternaries 7 (9 pts), error handling 2 (5 pts) (nesting depth added 8). Of this number, 30 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.
server.app.delete("/api/projects/:name/tasks/:id") (cognitive 25) REDACTED:3154— server.app.delete("/api/projects/:name/tasks/:id") has cognitive complexity 25 (threshold 15). Drivers by points: if/else 8 (13 pts), boolean chains 4, error handling 2 (4 pts), loops 2, ternaries 2 (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
server.app.delete("/api/projects/:name") (cognitive 16) REDACTED:1889— server.app.delete("/api/projects/:name") has cognitive complexity 16 (threshold 15). Drivers by points: if/else 7 (10 pts), boolean chains 3, error handling 2, loops 1 (nesting depth added 3). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
Change coupling: DetailPanel.jsx ↔ taskMutations.mjs dashboard/src/components/DetailPanel.jsx:1— `dashboard/src/components/DetailPanel.jsx` and `dashboard/src/state/taskMutations.mjs` change together 60% of the time (6 of the 10 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) with no explicit dependency — the edge is real but nothing declares it. Read the pair before acting: if one registers itself into the other through a hook or an initialiser, the missing dependency is DELIBERATE — the registration is the link, and it is meant not to be an import — and the thing to add is a comment on each side naming the other, not a merge; if they simply belong together, co-locate them; if neither holds, the coupling is hidden and worth breaking. You can check this without leaving the row: of the 6 shared commits counted here, the most recent 3 are `dbf3de9a` fix(T-454): stop a stale poll from reverting a just-set work state; `4f1b4b2a` fix(T-443-5): close final no-go gaps; `3ce30036` fix(T-443-4): close frontend high re-review findings — run `git show` on any of them.
Change coupling: REDACTED ↔ apiFetch.js REDACTED:1— `REDACTED` and `dashboard/src/utils/apiFetch.js` change together 53% of the time (8 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) with no explicit dependency — the edge is real but nothing declares it. Read the pair before acting: if one registers itself into the other through a hook or an initialiser, the missing dependency is DELIBERATE — the registration is the link, and it is meant not to be an import — and the thing to add is a comment on each side naming the other, not a merge; if they simply belong together, co-locate them; if neither 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 `dc71ae37` feat(T-450-1, T-450-4): stop polling a board nobody is looking at; `5d4fcd50` reconcile(T-447-1): restore secure principal confirmation contract; `0b40876a` fix(T-445): close auth and files lane review gaps — run `git show` on any of them.
Duplicated block (51 lines × 2 locations) dashboard/test-specify-api-answer.js:9— dashboard/test-specify-api-answer.js:9 · dashboard/test-specify-api-next.js:9 — the 2 copies sit in sibling files in one directory, so check first whether one of them (or an existing module there) already owns this behaviour and the others should call it; otherwise extract it into one module in that directory and have each site call it.
Duplicated block (51 lines × 2 locations) dashboard/test-structure-review-retire.js:25— dashboard/test-structure-review-retire.js:25 · dashboard/test-t458-spec-on-create.js:20 — the 2 copies sit in sibling files in one directory, so check first whether one of them (or an existing module there) already owns this behaviour and the others should call it; otherwise extract it into one module in that directory and have each site call it.
R10 · Code Duplication· Duplicated block with local edits (34 matched lines × 2 locations) · ×2
Duplicated block with local edits (34 matched lines × 2 locations) dashboard/test-app-state-bridge.mjs:35— dashboard/test-app-state-bridge.mjs:35 · dashboard/test-dashboard-api.mjs:43 — the two spans are one implementation copied and then locally edited — 140 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one.
Duplicated block with local edits (34 matched lines × 2 locations) dashboard/test-handoff-endpoint.js:20— dashboard/test-handoff-endpoint.js:20 · dashboard/test-kanban-subtask-state.js:16 — the two spans are one implementation copied and then locally edited — 357 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 (30 lines × 2 locations) dashboard/test-canvas-db-endpoints.js:53— dashboard/test-canvas-db-endpoints.js:53 · dashboard/test-canvas-db-import.js:48 — 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 (30 lines × 2 locations) dashboard/test-content-hygiene-api.js:17— dashboard/test-content-hygiene-api.js:17 · dashboard/test-task-description.js:15 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
R10 · Code Duplication· Duplicated block with local edits (30 matched lines × 2 locations) · ×2
Duplicated block with local edits (30 matched lines × 2 locations) dashboard/test-momentum-bytype.js:15— dashboard/test-momentum-bytype.js:15 · dashboard/test-task-entered-status.js:12 — the two spans are one implementation copied and then locally edited — 411 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one.
Duplicated block with local edits (30 matched lines × 2 locations) dashboard/test-work-state-e2e.js:178— dashboard/test-work-state-e2e.js:178 · dashboard/test-work-state-poll-race-e2e.js:170 — the two spans are one implementation copied and then locally edited — 299 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 (29 lines × 3 locations) dashboard/src/components/SnippetUpgrade.jsx:777— dashboard/src/components/SnippetUpgrade.jsx:777 · dashboard/src/components/SnippetUpgrade.jsx:807 · dashboard/src/components/SnippetUpgrade.jsx:837 — all 3 copies are in the same file, and the SHAPE of this repetition could not be determined. It is not a run of declarations, a listing, a declaration header, a type body or a slice through a construct — and it was not measured as a run of executable statements either, so this row cannot tell you whether a function can stand where these lines are. Read the two spans before acting, because the move is opposite in the two cases. Where they are statements, the ordinary answer holds: give the shared part one home and call it from each site. Where they turn out to be declarations, a literal's entries, or the cases of an enumeration, there is no call site to call anything from, and collapsing them would delete what each copy pins — a shared base type, a generated set, or one exported constant each site refers to is the move instead, and sometimes the honest answer is that there is nothing to extract at all. Reported because the copies drift apart the first time only one of them is edited, which is true whichever of those they are.
Duplicated block (29 lines × 3 locations) dashboard/test-canvas-create-task-smoke.js:72— dashboard/test-canvas-create-task-smoke.js:72 · dashboard/test-canvas-promote-integration.js:118 · dashboard/test-canvas-promote-stepper-visible.js:70 — the 3 copies sit in sibling files in one directory, so check first whether one of them (or an existing module there) already owns this behaviour and the others should call it; otherwise extract it into one module in that directory and have each site call it. There is one copy in each of 3 separate files rather than several in one place, so check first whether these are sibling modules that each declare their own version of one shape — one per entity, per provider, per language. Where they are, no single extracted module collapses them: each module still has to be written, and what recurs is the TEMPLATE. The moves that do collapse a template are to generate these modules from the set they enumerate, or to replace the repeated construction with one factory each site calls with its own values — and where the set is the point, each module pinning one distinct thing, the repetition IS the enumeration and there is nothing to delete.
AC3 · Page structure· Page without a main landmark · ×1
Page without a main landmark dashboard/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>.
AC7 · A11y enforcement· Accessibility enforcement below the top rung · ×1
Accessibility enforcement below the top rung — No accessibility enforcement found — no a11y linter (eslint-plugin-jsx-a11y) and no axe/pa11y/Lighthouse in tests or CI. Start with the linter to catch issues at author time. What was searched, so you can tell an absence from a miss: the 70 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.
CanvasView.CanvasView (cyclomatic 307) REDACTED:80— CanvasView.CanvasView has cyclomatic complexity 307 (threshold 15). Of this number, 22 points are the body's own statements and 285 belong to 62 function items inside it that branch. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
DetailPanel.DetailPanel (cyclomatic 296) dashboard/src/components/DetailPanel.jsx:182— DetailPanel.DetailPanel has cyclomatic complexity 296 (threshold 15). Of this number, 83 points are the body's own statements and 213 belong to 54 function items inside it that branch. To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
FilesView.FilesView (cyclomatic 173) dashboard/src/pages/FilesView.jsx:466— FilesView.FilesView has cyclomatic complexity 173 (threshold 15). Of this number, 17 points are the body's own statements and 156 belong to 37 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.
TasksView.TasksView (cyclomatic 158) dashboard/src/pages/TasksView.jsx:1170— TasksView.TasksView has cyclomatic complexity 158 (threshold 15). Most of this is not in the body itself: 11 of the 158 points are its own statements and the rest belongs to 32 function literals inside it that branch (lines 1435, 1670, 1581, …). 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.
Sidebar.Sidebar (cyclomatic 147) dashboard/src/components/Sidebar.jsx:201— Sidebar.Sidebar has cyclomatic complexity 147 (threshold 15). Most of this is not in the body itself: 13 of the 147 points are its own statements and the rest belongs to 42 function items inside it that branch (a function literal at line 265, handleItemKeyDown, onGripPointerDown::autoScrollTick, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
DashboardContext.DashboardProvider (cyclomatic 142) dashboard/src/context/DashboardContext.jsx:75— DashboardContext.DashboardProvider has cyclomatic complexity 142 (threshold 15). Most of this is not in the body itself: 2 of the 142 points are its own statements and the rest belongs to 33 function literals inside it that branch (lines 376, 495, 215, …). 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.
SpecifyStepper.SpecifyStepper (cyclomatic 108) dashboard/src/components/SpecifyStepper.jsx:40— SpecifyStepper.SpecifyStepper has cyclomatic complexity 108 (threshold 15). Of this number, 66 points are the body's own statements and 42 belong to 11 function items inside it that branch. To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
SnippetUpgrade.UpgradeModal (cyclomatic 93) dashboard/src/components/SnippetUpgrade.jsx:152— SnippetUpgrade.UpgradeModal has cyclomatic complexity 93 (threshold 15). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators. This shape REPEATS in the file: one other method here (SnippetUpgrade.UpgradeModal::handleApply) has the same decision points, in the same order, at the same nesting depths — so this is one pattern written twice rather than two separate problems. Splitting this body alone leaves the other exactly as it is. Where these are variations on one operation, the change that clears both is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
(anonymous) (cyclomatic 93) REDACTED:2875— (anonymous) has cyclomatic complexity 93 (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.
server.app.put("/api/projects/:name/tasks/:id") (cyclomatic 92) REDACTED:2875— server.app.put("/api/projects/:name/tasks/:id") has cyclomatic complexity 92 (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.
updateTask (cyclomatic 85) dashboard/hzl-service.js:1431— updateTask has cyclomatic complexity 85 (threshold 15). Of this number, 82 points are the body's own statements and 3 belong to 4 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.
ProjectBundleModals.ImportProjectModal (cyclomatic 84) dashboard/src/components/ProjectBundleModals.jsx:494— ProjectBundleModals.ImportProjectModal has cyclomatic complexity 84 (threshold 15). Of this number, 36 points are the body's own statements and 48 belong to 12 function items inside it that branch. To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
(anonymous) (cyclomatic 83) REDACTED:2702— (anonymous) has cyclomatic complexity 83 (threshold 15). Of this number, 76 points are the body's own statements and 7 belong to 5 function items inside it that branch. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
OverviewView.OverviewView (cyclomatic 82) dashboard/src/pages/OverviewView.jsx:64— OverviewView.OverviewView has cyclomatic complexity 82 (threshold 15). Of this number, 19 points are the body's own statements and 63 belong to 32 function items inside it that branch. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
ActiveAgentsBar.ActiveAgentsBar (cyclomatic 80) dashboard/src/components/ActiveAgentsBar.jsx:285— ActiveAgentsBar.ActiveAgentsBar has cyclomatic complexity 80 (threshold 15). Most of this is not in the body itself: 12 of the 80 points are its own statements and the rest belongs to 30 function literals inside it that branch (lines 511, 434, 346, …). 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.
widgets2.MilestonesWidget (cyclomatic 66) REDACTED:262— widgets2.MilestonesWidget has cyclomatic complexity 66 (threshold 15). Of this number, 39 points are the body's own statements and 27 belong to 10 function items inside it that branch. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
TasksView.TaskCard (cyclomatic 64) dashboard/src/pages/TasksView.jsx:304— TasksView.TaskCard has cyclomatic complexity 64 (threshold 15). Of this number, 32 points are the body's own statements and 32 belong to 12 function items inside it that branch. To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
widgets2.LinksWidget (cyclomatic 59) REDACTED:864— widgets2.LinksWidget has cyclomatic complexity 59 (threshold 15). Most of this is not in the body itself: 15 of the 59 points are its own statements and the rest belongs to 15 function items inside it that branch (a function literal at line 947, saveEdit, removeLink, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
FilesView.FilePreview (cyclomatic 59) dashboard/src/pages/FilesView.jsx:148— FilesView.FilePreview has cyclomatic complexity 59 (threshold 15). Of this number, 26 points are the body's own statements and 33 belong to 6 function items inside it that branch. To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
WorkStatePopover.WorkStatePopover (cyclomatic 58) dashboard/src/components/WorkStatePopover.jsx:126— WorkStatePopover.WorkStatePopover has cyclomatic complexity 58 (threshold 15). Of this number, 20 points are the body's own statements and 38 belong to 11 function items inside it that branch. To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
systemd-config.parseSystemdEnvironmentFile (cyclomatic 54) scripts/systemd-config.mjs:349— systemd-config.parseSystemdEnvironmentFile has cyclomatic complexity 54 (threshold 15). Of this number, 46 points are the body's own statements and 8 belong to 2 function items inside it that branch. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
canvasGeometry.routePath (cyclomatic 52) dashboard/src/utils/canvasGeometry.mjs:48— canvasGeometry.routePath has cyclomatic complexity 52 (threshold 15). Of this number, 49 points are the body's own statements and 3 belong to one function item inside it that branches. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
ProjectBundleModals.ExportProjectModal (cyclomatic 51) dashboard/src/components/ProjectBundleModals.jsx:201— ProjectBundleModals.ExportProjectModal has cyclomatic complexity 51 (threshold 15). Of this number, 23 points are the body's own statements and 28 belong to 7 function items inside it that branch. To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
startServer (cyclomatic 47) REDACTED:5089— startServer has cyclomatic complexity 47 (threshold 15). Of this number, 21 points are the body's own statements and 26 belong to 11 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.
overview.validateOverview (cyclomatic 46) dashboard/overview.js:525— overview.validateOverview has cyclomatic complexity 46 (threshold 15). Most of this is not in the body itself: 11 of the 46 points are its own statements and the rest belongs to one function literal inside it that branches (line 538). 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.
hzl-service.createTaskRaw (cyclomatic 45) dashboard/hzl-service.js:1248— hzl-service.createTaskRaw has cyclomatic complexity 45 (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.
widgets2.StallDetectionWidget (cyclomatic 43) REDACTED:1025— widgets2.StallDetectionWidget has cyclomatic complexity 43 (threshold 15). Of this number, 30 points are the body's own statements and 13 belong to 8 function items inside it that branch. To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
CreateProjectModal.CreateProjectModal (cyclomatic 42) dashboard/src/components/CreateProjectModal.jsx:26— CreateProjectModal.CreateProjectModal has cyclomatic complexity 42 (threshold 15). Of this number, 23 points are the body's own statements and 19 belong to 9 function items inside it that branch. To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
canonicalizeBundle (cyclomatic 42) dashboard/project-bundle-schema.js:229— canonicalizeBundle has cyclomatic complexity 42 (threshold 15). Of this number, 35 points are the body's own statements and 7 belong to 4 function items inside it that branch. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
server.persistSpecifyProposal (cyclomatic 40) REDACTED:726— server.persistSpecifyProposal has cyclomatic complexity 40 (threshold 15). Of this number, 24 points are the body's own statements and 16 belong to one function literal inside it that branches. 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.
widgets2.RepoStatusWidget (cyclomatic 40) REDACTED:1160— widgets2.RepoStatusWidget has cyclomatic complexity 40 (threshold 15). Of this number, 22 points are the body's own statements and 18 belong to 11 function items inside it that branch. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
canvasReducer (cyclomatic 40) dashboard/src/state/canvasStore.mjs:28— canvasReducer has cyclomatic complexity 40 (threshold 15). Of this number, 26 points are the body's own statements and 14 belong to 8 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.
ProjectBundleImporter._canonicalAdmission (cyclomatic 39) dashboard/project-bundle-import.js:367— ProjectBundleImporter._canonicalAdmission has cyclomatic complexity 39 (threshold 15). Of this number, 38 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.
CanvasMiniMap.CanvasMiniMap (cyclomatic 39) REDACTED:37— CanvasMiniMap.CanvasMiniMap has cyclomatic complexity 39 (threshold 15). Of this number, 19 points are the body's own statements and 20 belong to 10 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.
task-creation-policy.evaluateCreationPolicy (cyclomatic 38) dashboard/task-creation-policy.js:107— task-creation-policy.evaluateCreationPolicy 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.
SearchPalette.SearchPalette (cyclomatic 37) dashboard/src/components/SearchPalette.jsx:19— SearchPalette.SearchPalette has cyclomatic complexity 37 (threshold 15). Of this number, 16 points are the body's own statements and 21 belong to 7 function items inside it that branch. To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
systemd-config.unescapeSystemdString (cyclomatic 37) scripts/systemd-config.mjs:88— systemd-config.unescapeSystemdString has cyclomatic complexity 37 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
apiFetch (cyclomatic 37) dashboard/src/utils/apiFetch.js:37— apiFetch has cyclomatic complexity 37 (threshold 15). Of this number, 32 points are the body's own statements and 5 belong to 6 function items inside it that branch. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
project-bundle-validator.validateTasks (cyclomatic 36) dashboard/project-bundle-validator.js:313— project-bundle-validator.validateTasks has cyclomatic complexity 36 (threshold 15). Most of this is not in the body itself: 15 of the 36 points are its own statements and the rest belongs to 3 function items inside it that branch (a function literal at line 317, visitDependencies, visit). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
getStuckTasks (cyclomatic 36) dashboard/hzl-service.js:3513— getStuckTasks 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.
overview.applyOps (cyclomatic 35) dashboard/overview.js:395— overview.applyOps has cyclomatic complexity 35 (threshold 15). Most of this is not in the body itself: 4 of the 35 points are its own statements and the rest belongs to 3 function items inside it that branch (a function literal at line 417, a function literal at line 402, sizeToWidth). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
widgets2.FileViewerWidget (cyclomatic 35) REDACTED:1293— widgets2.FileViewerWidget has cyclomatic complexity 35 (threshold 15). Most of this is not in the body itself: 11 of the 35 points are its own statements and the rest belongs to 11 function items inside it that branch (a function literal at line 1312, pickFile, a function literal at line 1327, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
canvasTextFormat.applyFormattingToTextarea (cyclomatic 35) dashboard/src/utils/canvasTextFormat.mjs:7— canvasTextFormat.applyFormattingToTextarea has cyclomatic complexity 35 (threshold 15). Most of this is not in the body itself: 9 of the 35 points are its own statements and the rest belongs to 8 function items inside it that branch (isWrapped, isSurrounded, wrapInline, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
project-bundle-validator.validateManifest (cyclomatic 34) dashboard/project-bundle-validator.js:196— project-bundle-validator.validateManifest has cyclomatic complexity 34 (threshold 15). Of this number, 33 points are the body's own statements and 1 belongs to one function literal inside it that branches. To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
(anonymous) (cyclomatic 34) REDACTED:4149— (anonymous) has cyclomatic complexity 34 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
_toFbTask (cyclomatic 34) dashboard/hzl-service.js:198— _toFbTask has cyclomatic complexity 34 (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.
ProjectBundleImporter.importBundle (cyclomatic 33) dashboard/project-bundle-import.js:849— ProjectBundleImporter.importBundle has cyclomatic complexity 33 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
rules-api.buildOperationalTaskStateMarkdown (cyclomatic 33) dashboard/rules-api.js:217— rules-api.buildOperationalTaskStateMarkdown 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.
_restoreHistory (cyclomatic 32) dashboard/project-bundle-import.js:707— _restoreHistory has cyclomatic complexity 32 (threshold 15). Of this number, 21 points are the body's own statements and 11 belong to 12 function items inside it that branch. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
hzl-service.getProjectActivity (cyclomatic 31) dashboard/hzl-service.js:2931— hzl-service.getProjectActivity 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.
widgets.TaskStatsWidget (cyclomatic 31) REDACTED:217— widgets.TaskStatsWidget has cyclomatic complexity 31 (threshold 15). Of this number, 16 points are the body's own statements and 15 belong to 8 function items inside it that branch. To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
hzl-service.getNotifiableStuckTasks (cyclomatic 30) dashboard/hzl-service.js:3676— hzl-service.getNotifiableStuckTasks 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.
hzl-service.buildHandoffMarkdown (cyclomatic 30) dashboard/hzl-service.js:4037— hzl-service.buildHandoffMarkdown has cyclomatic complexity 30 (threshold 15). Of this number, 27 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.
snippets-doctor.runCli (cyclomatic 30) dashboard/snippets-doctor.js:821— snippets-doctor.runCli 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.
fetchInsight (cyclomatic 30) dashboard/github.js:120— fetchInsight has cyclomatic complexity 30 (threshold 15). Of this number, 23 points are the body's own statements and 7 belong to 9 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.
project-bundle-validator.validateOverview (cyclomatic 29) dashboard/project-bundle-validator.js:483— project-bundle-validator.validateOverview has cyclomatic complexity 29 (threshold 15). Most of this is not in the body itself: 5 of the 29 points are its own statements and the rest belongs to one function literal inside it that branches (line 489). 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.
ProjectBundleModals.WarningList (cyclomatic 29) dashboard/src/components/ProjectBundleModals.jsx:102— ProjectBundleModals.WarningList has cyclomatic complexity 29 (threshold 15). Most of this is not in the body itself: 5 of the 29 points are its own statements and the rest belongs to one function literal inside it that branches (line 110). 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.
(anonymous) (cyclomatic 29) REDACTED:3818— (anonymous) has cyclomatic complexity 29 (threshold 15). Of this number, 27 points are the body's own statements and 2 belong to 3 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.
server.app.post("/api/projects/import") (cyclomatic 28) REDACTED:2254— server.app.post("/api/projects/import") 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.
apiFetch.apiJson (cyclomatic 28) dashboard/src/utils/apiFetch.js:285— apiFetch.apiJson 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.
CanvasToolbar.CanvasToolbar (cyclomatic 28) dashboard/src/components/canvas/CanvasToolbar.jsx:23— CanvasToolbar.CanvasToolbar has cyclomatic complexity 28 (threshold 15). Most of this is not in the body itself: 8 of the 28 points are its own statements and the rest belongs to 9 function literals inside it that branch (lines 48, 143, 101, …). 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.
(anonymous) (cyclomatic 28) REDACTED:2254— (anonymous) 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.
hzl-service.rebuildCache (cyclomatic 27) dashboard/hzl-service.js:618— hzl-service.rebuildCache has cyclomatic complexity 27 (threshold 15). Of this number, 25 points are the body's own statements and 2 belong to one function literal inside it that branches. To reduce it, 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.
hzl-service.deleteTask (cyclomatic 27) dashboard/hzl-service.js:1747— hzl-service.deleteTask 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.
snippets-doctor.collectStatus (cyclomatic 27) dashboard/snippets-doctor.js:623— snippets-doctor.collectStatus has cyclomatic complexity 27 (threshold 15). 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.
rate-limiter.parseIpAddress (cyclomatic 27) dashboard/rate-limiter.js:154— rate-limiter.parseIpAddress has cyclomatic complexity 27 (threshold 15). Of this number, 26 points are the body's own statements and 1 belongs to one function literal inside it that branches. To reduce it, split the body: 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.
specify-policy.decisionFields (cyclomatic 27) dashboard/specify-policy.js:149— specify-policy.decisionFields has cyclomatic complexity 27 (threshold 15). Most of this is not in the body itself: 10 of the 27 points are its own statements and the rest belongs to 3 function items inside it that branch (addNamedFields, a function literal at line 171, addField). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
stuck-notify.buildStuckNotifications (cyclomatic 27) REDACTED:48— stuck-notify.buildStuckNotifications has cyclomatic complexity 27 (threshold 15). Of this number, 18 points are the body's own statements and 9 belong to 3 function items inside it that branch. To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
Modal.Modal (cyclomatic 27) dashboard/src/components/Modal.jsx:28— Modal.Modal has cyclomatic complexity 27 (threshold 15). Most of this is not in the body itself: 10 of the 27 points are its own statements and the rest belongs to 5 function items inside it that branch (a function literal at line 42, a function literal at line 73, handleOverlayPointerDown, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
ConnectionLayer.ConnectionLayer (cyclomatic 27) dashboard/src/components/canvas/ConnectionLayer.jsx:16— ConnectionLayer.ConnectionLayer has cyclomatic complexity 27 (threshold 15). Of this number, 21 points are the body's own statements and 6 belong to 2 function items inside it that branch. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
rankTasks (cyclomatic 27) dashboard/smart-search.js:140— rankTasks has cyclomatic complexity 27 (threshold 15). Of this number, 18 points are the body's own statements and 9 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.
smart-search.passesFilters (cyclomatic 26) dashboard/smart-search.js:113— smart-search.passesFilters 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.
hzl-service.getProjectHistory (cyclomatic 26) dashboard/hzl-service.js:2693— hzl-service.getProjectHistory 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.
migrate-tasks.migrateProject (cyclomatic 26) dashboard/migrate-tasks.js:159— migrate-tasks.migrateProject 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.
server.telegramAuthMiddleware (cyclomatic 26) REDACTED:389— server.telegramAuthMiddleware has cyclomatic complexity 26 (threshold 15). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
dashboardApi.validateTask (cyclomatic 26) dashboard/src/utils/dashboardApi.js:131— dashboardApi.validateTask has cyclomatic complexity 26 (threshold 15). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
MoveTaskModal.MoveTaskModal (cyclomatic 26) dashboard/src/components/MoveTaskModal.jsx:15— MoveTaskModal.MoveTaskModal has cyclomatic complexity 26 (threshold 15). Of this number, 13 points are the body's own statements and 13 belong to 6 function items inside it that branch. To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
buildFileTree (cyclomatic 26) REDACTED:3224— buildFileTree has cyclomatic complexity 26 (threshold 15). Most of this is not in the body itself: 11 of the 26 points are its own statements and the rest belongs to 4 function items inside it that branch (walk, a function literal at line 3290, sortEntries, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
(anonymous) (cyclomatic 26) REDACTED:3952— (anonymous) has cyclomatic complexity 26 (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.
_importTasks (cyclomatic 26) dashboard/project-bundle-import.js:618— _importTasks 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.
fetchRepoStatus (cyclomatic 26) dashboard/github.js:51— fetchRepoStatus has cyclomatic complexity 26 (threshold 15). Of this number, 20 points are the body's own statements and 6 belong to 7 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.
dashboard-snapshot.buildDashboardSnapshot (cyclomatic 25) dashboard/dashboard-snapshot.js:45— dashboard-snapshot.buildDashboardSnapshot has cyclomatic complexity 25 (threshold 15). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
work-state.isValidDateString (cyclomatic 25) dashboard/work-state.js:43— work-state.isValidDateString has cyclomatic complexity 25 (threshold 15). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
project-bundle-validator.validateCanvas (cyclomatic 25) dashboard/project-bundle-validator.js:442— project-bundle-validator.validateCanvas has cyclomatic complexity 25 (threshold 15). Most of this is not in the body itself: 5 of the 25 points are its own statements and the rest belongs to 2 function literals inside it that branch (lines 462, 448). 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.
NoteCard.NoteCard (cyclomatic 25) dashboard/src/components/canvas/NoteCard.jsx:49— NoteCard.NoteCard has cyclomatic complexity 25 (threshold 15). Of this number, 13 points are the body's own statements and 12 belong to 7 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.
widgets3.GhCiWidget (cyclomatic 25) REDACTED:167— widgets3.GhCiWidget has cyclomatic complexity 25 (threshold 15). Of this number, 16 points are the body's own statements and 9 belong to 3 function literals inside it that branch. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
widgets3.AgentQuestionsWidget (cyclomatic 25) REDACTED:352— widgets3.AgentQuestionsWidget has cyclomatic complexity 25 (threshold 15). Most of this is not in the body itself: 5 of the 25 points are its own statements and the rest belongs to 7 function items inside it that branch (a function literal at line 411, sendAnswer, a function literal at line 363, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
project-bundle-schema.createBundle (cyclomatic 24) dashboard/project-bundle-schema.js:433— project-bundle-schema.createBundle has cyclomatic complexity 24 (threshold 15). Of this number, 23 points are the body's own statements and 1 belongs 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.
project-bundle-validator.validateHistory (cyclomatic 24) dashboard/project-bundle-validator.js:543— project-bundle-validator.validateHistory has cyclomatic complexity 24 (threshold 15). Most of this is not in the body itself: 8 of the 24 points are its own statements and the rest belongs to 3 function items inside it that branch (a function literal at line 553, a function literal at line 574, validateHistoryId). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
server.app.get("/api/projects/:name/tasks") (cyclomatic 24) REDACTED:2598— server.app.get("/api/projects/:name/tasks") has cyclomatic complexity 24 (threshold 15). Of this number, 19 points are the body's own statements and 5 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.
TasksView.Column (cyclomatic 24) dashboard/src/pages/TasksView.jsx:1051— TasksView.Column has cyclomatic complexity 24 (threshold 15). Of this number, 19 points are the body's own statements and 5 belong to 2 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.
systemd-config.parseSystemdEnvironment (cyclomatic 24) scripts/systemd-config.mjs:246— systemd-config.parseSystemdEnvironment has cyclomatic complexity 24 (threshold 15). Of this number, 21 points are the body's own statements and 3 belong to one function literal inside it that branches. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
_normalizeResponse (cyclomatic 24) dashboard/specify-worker-bridge.js:110— _normalizeResponse has cyclomatic complexity 24 (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.
smartSearchTasks (cyclomatic 24) dashboard/hzl-service.js:2195— smartSearchTasks has cyclomatic complexity 24 (threshold 15). Of this number, 15 points are the body's own statements and 9 belong to 6 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.
canvasImportFromJson (cyclomatic 24) dashboard/hzl-service.js:4803— canvasImportFromJson has cyclomatic complexity 24 (threshold 15). Most of this is not in the body itself: 4 of the 24 points are its own statements and the rest belongs to one function literal inside it that branches (line 4810). 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.
hzl-service.setTaskParent (cyclomatic 23) dashboard/hzl-service.js:2104— hzl-service.setTaskParent has cyclomatic complexity 23 (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.
hzl-service.claimTask (cyclomatic 23) dashboard/hzl-service.js:2318— hzl-service.claimTask 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.
hzl-service.renderStatusEventMessage (cyclomatic 23) dashboard/hzl-service.js:3116— hzl-service.renderStatusEventMessage 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.
ProjectBundleImporter._verify (cyclomatic 23) dashboard/project-bundle-import.js:775— ProjectBundleImporter._verify 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.
specify-sessions.createSession (cyclomatic 23) dashboard/specify-sessions.js:47— specify-sessions.createSession 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.
server.handleSpecifyStep (cyclomatic 23) REDACTED:4048— server.handleSpecifyStep 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.
ActiveAgentsBar.ActiveAgentPill (cyclomatic 23) dashboard/src/components/ActiveAgentsBar.jsx:155— ActiveAgentsBar.ActiveAgentPill has cyclomatic complexity 23 (threshold 15). Of this number, 19 points are the body's own statements and 4 belong to 2 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.
canvasGeometry.computePortPositions (cyclomatic 23) dashboard/src/utils/canvasGeometry.mjs:329— canvasGeometry.computePortPositions has cyclomatic complexity 23 (threshold 15). Of this number, 17 points are the body's own statements and 6 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.
TaskDisciplineControl.TaskDisciplineControl (cyclomatic 23) dashboard/src/components/TaskDisciplineControl.jsx:28— TaskDisciplineControl.TaskDisciplineControl has cyclomatic complexity 23 (threshold 15). Most of this is not in the body itself: 6 of the 23 points are its own statements and the rest belongs to 6 function items inside it that branch (changeDiscipline, a function literal at line 93, a function literal at line 37, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
ClaimStateLine.ClaimStateLine (cyclomatic 23) dashboard/src/components/ClaimStateLine.jsx:63— ClaimStateLine.ClaimStateLine has cyclomatic complexity 23 (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.
work-state.normalizeWorkStateDetails (cyclomatic 22) dashboard/work-state.js:92— work-state.normalizeWorkStateDetails 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.
hzl-service.workflowStart (cyclomatic 22) dashboard/hzl-service.js:903— hzl-service.workflowStart 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 4 function literals inside it that branch (lines 911, 910, 930, …). 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.
hzl-service.canvasSaveConnection (cyclomatic 22) dashboard/hzl-service.js:4713— hzl-service.canvasSaveConnection has cyclomatic complexity 22 (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.
project-bundle-export.toPortableHistoryFromEvents (cyclomatic 22) dashboard/project-bundle-export.js:434— project-bundle-export.toPortableHistoryFromEvents has cyclomatic complexity 22 (threshold 15). 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, 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.
dashboardApi.fetchDashboardSnapshot (cyclomatic 22) dashboard/src/utils/dashboardApi.js:318— dashboardApi.fetchDashboardSnapshot has cyclomatic complexity 22 (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.
TrashPanel.TrashPanel (cyclomatic 22) dashboard/src/components/TrashPanel.jsx:22— TrashPanel.TrashPanel has cyclomatic complexity 22 (threshold 15). Most of this is not in the body itself: 8 of the 22 points are its own statements and the rest belongs to 4 function items inside it that branch (handleEmpty, formatWhen, a function literal at line 26, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
clawhub-scan-summary.phaseForIssue (cyclomatic 22) scripts/clawhub-scan-summary.mjs:41— clawhub-scan-summary.phaseForIssue has cyclomatic complexity 22 (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.
setup.readExistingServiceConfig (cyclomatic 22) scripts/setup.mjs:448— setup.readExistingServiceConfig has cyclomatic complexity 22 (threshold 15). Of this number, 20 points are the body's own statements and 2 belong to one function literal inside it that branches. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
addComment (cyclomatic 22) dashboard/hzl-service.js:2836— addComment 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.
governance.verifyHumanConfirmation (cyclomatic 21) dashboard/governance.js:123— governance.verifyHumanConfirmation has cyclomatic complexity 21 (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.
hzl-service._indicatorForEntry (cyclomatic 21) dashboard/hzl-service.js:3324— hzl-service._indicatorForEntry has cyclomatic complexity 21 (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.
specify-policy._validateQuestion (cyclomatic 21) dashboard/specify-policy.js:53— specify-policy._validateQuestion 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.
server.app.post("/api/specify/sessions") (cyclomatic 21) REDACTED:3952— server.app.post("/api/specify/sessions") 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.
workState.normalizeStuckIndicatorActionDescriptor (cyclomatic 21) dashboard/src/utils/workState.js:159— workState.normalizeStuckIndicatorActionDescriptor has cyclomatic complexity 21 (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.
ProjectActionsMenu.ProjectActionsMenu (cyclomatic 21) dashboard/src/components/ProjectActionsMenu.jsx:27— ProjectActionsMenu.ProjectActionsMenu has cyclomatic complexity 21 (threshold 15). Of this number, 11 points are the body's own statements and 10 belong to 7 function items inside it that branch. To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
ProjectBundleModals.ImportPreviewSummary (cyclomatic 21) dashboard/src/components/ProjectBundleModals.jsx:446— ProjectBundleModals.ImportPreviewSummary has cyclomatic complexity 21 (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.
canvasMarkdown.parseMarkdownHtml::parseNode (cyclomatic 21) dashboard/src/utils/canvasMarkdown.mjs:105— canvasMarkdown.parseMarkdownHtml::parseNode 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.
widgets2.ContextIndexWidget (cyclomatic 21) REDACTED:578— widgets2.ContextIndexWidget has cyclomatic complexity 21 (threshold 15). Most of this is not in the body itself: 9 of the 21 points are its own statements and the rest belongs to 7 function literals inside it that branch (lines 614, 589, 584, …). 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.
setup.parseLaunchdEnvironment (cyclomatic 21) scripts/setup.mjs:209— setup.parseLaunchdEnvironment 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.
(anonymous) (cyclomatic 21) dashboard/tools/ov-audit.mjs:51— (anonymous) 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.
flowboard-metadata.updateProjectMeta (cyclomatic 20) dashboard/flowboard-metadata.js:269— flowboard-metadata.updateProjectMeta 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.
policy-ledger.appendPolicyRecord (cyclomatic 20) dashboard/policy-ledger.js:38— policy-ledger.appendPolicyRecord 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.
hzl-service.buildCreationAudit (cyclomatic 20) dashboard/hzl-service.js:1203— hzl-service.buildCreationAudit 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.
project-bundle-validator.validateFiles (cyclomatic 20) dashboard/project-bundle-validator.js:511— project-bundle-validator.validateFiles has cyclomatic complexity 20 (threshold 15). Most of this is not in the body itself: 3 of the 20 points are its own statements and the rest belongs to one function literal inside it that branches (line 516). 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.
project-lifecycle._validateUpdateInput (cyclomatic 20) dashboard/project-lifecycle.js:305— project-lifecycle._validateUpdateInput 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.
specify-policy._validateProposal (cyclomatic 20) dashboard/specify-policy.js:93— specify-policy._validateProposal 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.
telegram-auth.validateTelegramInitData (cyclomatic 20) dashboard/telegram-auth.js:167— telegram-auth.validateTelegramInitData 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.
server.normalizeTaskBreakdown (cyclomatic 20) REDACTED:703— server.normalizeTaskBreakdown has cyclomatic complexity 20 (threshold 15). Of this number, 10 points are the body's own statements and 10 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.
TasksView.SubtaskCard (cyclomatic 20) dashboard/src/pages/TasksView.jsx:171— TasksView.SubtaskCard has cyclomatic complexity 20 (threshold 15). Of this number, 12 points are the body's own statements and 8 belong to 2 function items inside it that branch. To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
setSpecifyConfirmation (cyclomatic 20) dashboard/hzl-service.js:4312— setSpecifyConfirmation 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.
flowboard-metadata.listProjects (cyclomatic 19) dashboard/flowboard-metadata.js:218— flowboard-metadata.listProjects has cyclomatic complexity 19 (threshold 15). Most of this is not in the body itself: 3 of the 19 points are its own statements and the rest belongs to 2 function literals inside it that branch (lines 242, 241). 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.
task-creation-policy.hasOneTopLevelAction (cyclomatic 19) dashboard/task-creation-policy.js:41— task-creation-policy.hasOneTopLevelAction has cyclomatic complexity 19 (threshold 15). Of this number, 14 points are the body's own statements and 5 belong to 2 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.
project-bundle-export.bundleValidationDiagnostics (cyclomatic 19) dashboard/project-bundle-export.js:338— project-bundle-export.bundleValidationDiagnostics has cyclomatic complexity 19 (threshold 15). Most of this is not in the body itself: 2 of the 19 points are its own statements and the rest belongs to one function literal inside it that branches (line 340). 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.
project-lifecycle.healProject (cyclomatic 19) dashboard/project-lifecycle.js:546— project-lifecycle.healProject has cyclomatic complexity 19 (threshold 15). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
server.app.delete("/api/projects/:name/tasks/:id") (cyclomatic 19) REDACTED:3154— server.app.delete("/api/projects/:name/tasks/:id") 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.
SnippetUpgrade.UpgradeModal::handleApply (cyclomatic 19) dashboard/src/components/SnippetUpgrade.jsx:275— SnippetUpgrade.UpgradeModal::handleApply has cyclomatic complexity 19 (threshold 15). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators. This shape REPEATS in the file: one other method here (SnippetUpgrade.UpgradeModal) has the same decision points, in the same order, at the same nesting depths — so this is one pattern written twice rather than two separate problems. Splitting this body alone leaves the other exactly as it is. Where these are variations on one operation, the change that clears both is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
SnippetUpgrade.AppUpdateSection (cyclomatic 19) dashboard/src/components/SnippetUpgrade.jsx:637— SnippetUpgrade.AppUpdateSection 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.
widgets3.GhPullsWidget (cyclomatic 19) REDACTED:111— widgets3.GhPullsWidget has cyclomatic complexity 19 (threshold 15). Of this number, 15 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.
systemd-config.splitSystemdWords (cyclomatic 19) scripts/systemd-config.mjs:39— systemd-config.splitSystemdWords has cyclomatic complexity 19 (threshold 15). Of this number, 16 points are the body's own statements and 3 belong to one function item inside it that branches. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
canvasSaveConnection (cyclomatic 19) REDACTED:941— canvasSaveConnection has cyclomatic complexity 19 (threshold 15). Of this number, 16 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.
(anonymous) (cyclomatic 19) REDACTED:3154— (anonymous) 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.
normalizeProject (cyclomatic 19) dashboard/project-bundle-export.js:398— normalizeProject 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, 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.
hzl-service.createTaskWithPolicy (cyclomatic 18) dashboard/hzl-service.js:1107— hzl-service.createTaskWithPolicy has cyclomatic complexity 18 (threshold 15). Of this number, 17 points are the body's own statements and 1 belongs to one function item 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.
hzl-service.recalcParentStatus (cyclomatic 18) dashboard/hzl-service.js:1981— hzl-service.recalcParentStatus has cyclomatic complexity 18 (threshold 15). Of this number, 13 points are the body's own statements and 5 belong to 3 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.
hzl-service.getComplianceStatus (cyclomatic 18) dashboard/hzl-service.js:3827— hzl-service.getComplianceStatus 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.
project-bundle-validator.validateSpecs (cyclomatic 18) dashboard/project-bundle-validator.js:408— project-bundle-validator.validateSpecs has cyclomatic complexity 18 (threshold 15). Most of this is not in the body itself: 8 of the 18 points are its own statements and the rest belongs to one function literal inside it that branches (line 411). 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.
specify-worker-openclaw.createOpenClawCliAdapter.call (cyclomatic 18) dashboard/specify-worker-openclaw.js:167— specify-worker-openclaw.createOpenClawCliAdapter.call 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.
DeleteProjectModal.DeleteProjectModal (cyclomatic 18) dashboard/src/components/DeleteProjectModal.jsx:9— DeleteProjectModal.DeleteProjectModal has cyclomatic complexity 18 (threshold 15). Of this number, 10 points are the body's own statements and 8 belong to 3 function items inside it that branch. To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
canvasMarkdown.renderNoteMarkdown (cyclomatic 18) dashboard/src/utils/canvasMarkdown.mjs:18— canvasMarkdown.renderNoteMarkdown 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, 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.
createOpenClawCliAdapter.call (cyclomatic 18) dashboard/specify-worker-openclaw.js:167— createOpenClawCliAdapter.call 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.
hzl-service._normalizeExceptionReview (cyclomatic 17) dashboard/hzl-service.js:153— hzl-service._normalizeExceptionReview 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.
hzl-service.workflowHandoff (cyclomatic 17) dashboard/hzl-service.js:951— hzl-service.workflowHandoff has cyclomatic complexity 17 (threshold 15). Of this number, 14 points are the body's own statements and 3 belong to one function literal inside it that branches. To reduce it, 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.
hzl-service.moveTaskToProject (cyclomatic 17) dashboard/hzl-service.js:2030— hzl-service.moveTaskToProject 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.
hzl-service.getOpenQuestions (cyclomatic 17) dashboard/hzl-service.js:3048— hzl-service.getOpenQuestions 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.
snippets-doctor.applyActions (cyclomatic 17) dashboard/snippets-doctor.js:733— snippets-doctor.applyActions 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.
project-bundle-export.exportProjectReviewBundle (cyclomatic 17) dashboard/project-bundle-export.js:482— project-bundle-export.exportProjectReviewBundle 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.
ProjectBundleImporter._ensureProject (cyclomatic 17) dashboard/project-bundle-import.js:553— ProjectBundleImporter._ensureProject 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.
specify-worker-bridge._step (cyclomatic 17) dashboard/specify-worker-bridge.js:183— specify-worker-bridge._step has cyclomatic complexity 17 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
Sidebar.ProjectItem (cyclomatic 17) dashboard/src/components/Sidebar.jsx:91— Sidebar.ProjectItem has cyclomatic complexity 17 (threshold 15). Of this number, 10 points are the body's own statements and 7 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.
TasksView.AddTaskForm::handleSubmit (cyclomatic 17) dashboard/src/pages/TasksView.jsx:950— TasksView.AddTaskForm::handleSubmit 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.
setup.ensureOwnerOnlyRegularFile (cyclomatic 17) scripts/setup.mjs:643— setup.ensureOwnerOnlyRegularFile 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.
(anonymous) (cyclomatic 17) REDACTED:3461— (anonymous) 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.
agent-identity.classifyAgentId (cyclomatic 16) dashboard/agent-identity.js:62— agent-identity.classifyAgentId 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.
project-bundle-schema.normalizeRelativePath (cyclomatic 16) dashboard/project-bundle-schema.js:156— project-bundle-schema.normalizeRelativePath 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.
ProjectBundleImporter._publishStagedFiles (cyclomatic 16) dashboard/project-bundle-import.js:502— ProjectBundleImporter._publishStagedFiles 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.
project-lifecycle.createProject (cyclomatic 16) dashboard/project-lifecycle.js:142— project-lifecycle.createProject has cyclomatic complexity 16 (threshold 15). 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.
project-lifecycle.deleteProject (cyclomatic 16) dashboard/project-lifecycle.js:418— project-lifecycle.deleteProject has cyclomatic complexity 16 (threshold 15). 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.
server.app.get("/api/dashboard/snapshot/v1") (cyclomatic 16) REDACTED:2332— server.app.get("/api/dashboard/snapshot/v1") has cyclomatic complexity 16 (threshold 15). Of this number, 12 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.
server.app.get("/api/search") (cyclomatic 16) REDACTED:4894— server.app.get("/api/search") has cyclomatic complexity 16 (threshold 15). Of this number, 14 points are the body's own statements and 2 belong to 2 function literals inside it that branch. To reduce it, 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.
leaseHealth.getLeaseHealth (cyclomatic 16) dashboard/src/utils/leaseHealth.js:56— leaseHealth.getLeaseHealth 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.
widgets2.NotesWidget::locateFromEvent (cyclomatic 16) REDACTED:763— widgets2.NotesWidget::locateFromEvent 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.
setup.systemdUnitSearchPaths (cyclomatic 16) scripts/setup.mjs:276— setup.systemdUnitSearchPaths 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.
packGrid (cyclomatic 16) dashboard/overview.js:313— packGrid has cyclomatic complexity 16 (threshold 15). Most of this is not in the body itself: 2 of the 16 points are its own statements and the rest belongs to one function literal inside it that branches (line 319). 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.
directRefreshTasks (cyclomatic 16) dashboard/src/state/appStateBridge.mjs:59— directRefreshTasks has cyclomatic complexity 16 (threshold 15). Most of this is not in the body itself: 4 of the 16 points are its own statements and the rest belongs to 4 function items inside it that branch (a function literal at line 83, a function literal at line 67, a function literal at line 71, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
CanvasView.CanvasView (cognitive 377) REDACTED:80— CanvasView.CanvasView has cognitive complexity 377 (threshold 15). Drivers by points: if/else 185 (253 pts), boolean chains 71, ternaries 14 (26 pts), loops 15 (21 pts), error handling 4 (6 pts) (nesting depth added 88). Of this number, 27 points are the body's own statements and 350 belong to 62 function items inside it that branch. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
DetailPanel.DetailPanel (cognitive 267) dashboard/src/components/DetailPanel.jsx:182— DetailPanel.DetailPanel has cognitive complexity 267 (threshold 15). Drivers by points: boolean chains 122, if/else 78 (90 pts), ternaries 24 (34 pts), error handling 21 (nesting depth added 22). Of this number, 62 points are the body's own statements and 205 belong to 54 function items inside it that branch. To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
TasksView.TasksView (cognitive 183) dashboard/src/pages/TasksView.jsx:1170— TasksView.TasksView has cognitive complexity 183 (threshold 15). Drivers by points: if/else 82 (110 pts), boolean chains 48, ternaries 8 (11 pts), loops 7 (10 pts), error handling 4 (nesting depth added 34). Most of this is not in the body itself: 10 of the 183 points are its own statements and the rest belongs to 32 function literals inside it that branch (lines 1435, 1670, 1581, …). 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.
FilesView.FilesView (cognitive 171) dashboard/src/pages/FilesView.jsx:466— FilesView.FilesView has cognitive complexity 171 (threshold 15). Drivers by points: if/else 87 (98 pts), boolean chains 43, ternaries 19 (25 pts), error handling 5 (nesting depth added 17). Most of this is not in the body itself: 13 of the 171 points are its own statements and the rest belongs to 37 function literals inside it that branch (lines 719, 613, 871, …). 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.
Sidebar.Sidebar (cognitive 163) dashboard/src/components/Sidebar.jsx:201— Sidebar.Sidebar has cognitive complexity 163 (threshold 15). Drivers by points: if/else 90 (107 pts), boolean chains 33, ternaries 11 (12 pts), loops 7, error handling 4 (nesting depth added 18). Most of this is not in the body itself: 8 of the 163 points are its own statements and the rest belongs to 42 function items inside it that branch (a function literal at line 265, handleItemKeyDown, onGripPointerDown::onUp, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
DashboardContext.DashboardProvider (cognitive 154) dashboard/src/context/DashboardContext.jsx:75— DashboardContext.DashboardProvider has cognitive complexity 154 (threshold 15). Drivers by points: if/else 65 (86 pts), boolean chains 47, ternaries 9 (16 pts), error handling 3, loops 1 (2 pts) (nesting depth added 29). Most of this is not in the body itself: 1 of the 154 points is its own statement and the rest belongs to 33 function literals inside it that branch (lines 376, 495, 215, …). 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.
routePath (cognitive 147) dashboard/src/utils/canvasGeometry.mjs:48— routePath has cognitive complexity 147 (threshold 15). Drivers by points: if/else 35 (83 pts), ternaries 12 (50 pts), boolean chains 14 (nesting depth added 86). Of this number, 144 points are the body's own statements and 3 belong to one function item inside it that branches. 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.
(anonymous) (cognitive 131) REDACTED:2875— (anonymous) has cognitive complexity 131 (threshold 15). Drivers by points: if/else 40 (71 pts), boolean chains 31, error handling 7 (12 pts), ternaries 4 (10 pts), loops 3 (6 pts), other 1 (nesting depth added 45). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
updateTask (cognitive 127) dashboard/hzl-service.js:1431— updateTask has cognitive complexity 127 (threshold 15). Drivers by points: if/else 46 (73 pts), boolean chains 26, error handling 4 (15 pts), loops 3 (8 pts), ternaries 1 (4 pts), other 1 (nesting depth added 46). Of this number, 121 points are the body's own statements and 6 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.
server.app.put("/api/projects/:name/tasks/:id") (cognitive 125) REDACTED:2875— server.app.put("/api/projects/:name/tasks/:id") has cognitive complexity 125 (threshold 15). Drivers by points: if/else 40 (71 pts), boolean chains 29, error handling 7 (12 pts), ternaries 3 (7 pts), loops 3 (6 pts) (nesting depth added 43). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
(anonymous) (cognitive 118) REDACTED:2702— (anonymous) has cognitive complexity 118 (threshold 15). Drivers by points: if/else 26 (48 pts), boolean chains 30, ternaries 14 (20 pts), error handling 7 (14 pts), loops 2 (5 pts), other 1 (nesting depth added 38). Of this number, 107 points are the body's own statements and 11 belong to 5 function items inside it that branch. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
SpecifyStepper.SpecifyStepper (cognitive 96) dashboard/src/components/SpecifyStepper.jsx:40— SpecifyStepper.SpecifyStepper has cognitive complexity 96 (threshold 15). Drivers by points: boolean chains 50, if/else 21 (22 pts), ternaries 10 (20 pts), error handling 4 (nesting depth added 11). Of this number, 56 points are the body's own statements and 40 belong to 11 function items inside it that branch. To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
OverviewView.OverviewView (cognitive 89) dashboard/src/pages/OverviewView.jsx:64— OverviewView.OverviewView has cognitive complexity 89 (threshold 15). Drivers by points: if/else 22 (34 pts), boolean chains 30, ternaries 15 (20 pts), loops 3 (4 pts), error handling 1 (nesting depth added 18). Of this number, 22 points are the body's own statements and 67 belong to 32 function items inside it that branch. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
systemd-config.parseSystemdEnvironmentFile (cognitive 85) scripts/systemd-config.mjs:349— systemd-config.parseSystemdEnvironmentFile has cognitive complexity 85 (threshold 15). Drivers by points: if/else 41 (75 pts), boolean chains 5, match/switch 1 (2 pts), ternaries 2, loops 1 (nesting depth added 35). Of this number, 78 points are the body's own statements and 7 belong to 2 function items inside it that branch. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
ProjectBundleModals.ImportProjectModal (cognitive 83) dashboard/src/components/ProjectBundleModals.jsx:494— ProjectBundleModals.ImportProjectModal has cognitive complexity 83 (threshold 15). Drivers by points: boolean chains 38, if/else 19 (20 pts), ternaries 11 (20 pts), error handling 5 (nesting depth added 10). Of this number, 37 points are the body's own statements and 46 belong to 12 function items inside it that branch. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
SnippetUpgrade.UpgradeModal (cognitive 80) dashboard/src/components/SnippetUpgrade.jsx:152— SnippetUpgrade.UpgradeModal has cognitive complexity 80 (threshold 15). Drivers by points: boolean chains 74, if/else 19 (22 pts), ternaries 10 (17 pts), error handling 3 (6 pts) (nesting depth added 13). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators. This shape REPEATS in the file: one other method here (SnippetUpgrade.UpgradeModal::handleApply) has the same decision points, in the same order, at the same nesting depths — so this is one pattern written twice rather than two separate problems. Splitting this body alone leaves the other exactly as it is. Where these are variations on one operation, the change that clears both is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
widgets2.MilestonesWidget (cognitive 75) REDACTED:262— widgets2.MilestonesWidget has cognitive complexity 75 (threshold 15). Drivers by points: boolean chains 29, ternaries 14 (21 pts), if/else 12 (20 pts), loops 3 (4 pts), error handling 1 (nesting depth added 16). Of this number, 49 points are the body's own statements and 26 belong to 10 function items inside it that branch. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
widgets2.LinksWidget (cognitive 69) REDACTED:864— widgets2.LinksWidget has cognitive complexity 69 (threshold 15). Drivers by points: if/else 15 (26 pts), boolean chains 24, ternaries 10 (19 pts) (nesting depth added 20). Most of this is not in the body itself: 11 of the 69 points are its own statements and the rest belongs to 15 function items inside it that branch (a function literal at line 947, removeLink, saveEdit, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
canonicalizeBundle (cognitive 69) dashboard/project-bundle-schema.js:229— canonicalizeBundle has cognitive complexity 69 (threshold 15). Drivers by points: if/else 16 (31 pts), boolean chains 11, error handling 3 (11 pts), loops 5 (9 pts), ternaries 2 (5 pts), other 2 (nesting depth added 30). Of this number, 63 points are the body's own statements and 6 belong to 4 function items inside it that branch. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
TasksView.TaskCard (cognitive 68) dashboard/src/pages/TasksView.jsx:304— TasksView.TaskCard has cognitive complexity 68 (threshold 15). Drivers by points: if/else 20 (26 pts), boolean chains 25, ternaries 8 (9 pts), error handling 4 (6 pts), loops 1 (2 pts) (nesting depth added 10). Of this number, 27 points are the body's own statements and 41 belong to 12 function items inside it that branch. To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition.
startServer (cognitive 67) REDACTED:5089— startServer has cognitive complexity 67 (threshold 15). Drivers by points: if/else 14 (21 pts), ternaries 9 (17 pts), error handling 10 (16 pts), boolean chains 11, loops 1 (2 pts) (nesting depth added 22). Of this number, 32 points are the body's own statements and 35 belong to 11 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.
ActiveAgentsBar.ActiveAgentsBar (cognitive 65) dashboard/src/components/ActiveAgentsBar.jsx:285— ActiveAgentsBar.ActiveAgentsBar has cognitive complexity 65 (threshold 15). Drivers by points: if/else 31 (33 pts), boolean chains 26, ternaries 6 (nesting depth added 2). Most of this is not in the body itself: 11 of the 65 points are its own statements and the rest belongs to 30 function literals inside it that branch (lines 511, 434, 346, …). 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.
snippets-doctor.runCli (cognitive 64) dashboard/snippets-doctor.js:821— snippets-doctor.runCli has cognitive complexity 64 (threshold 15). Drivers by points: if/else 22 (50 pts), boolean chains 8, loops 2 (3 pts), error handling 1 (2 pts), ternaries 1 (nesting depth added 30). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
systemd-config.unescapeSystemdString (cognitive 62) scripts/systemd-config.mjs:88— systemd-config.unescapeSystemdString has cognitive complexity 62 (threshold 15). Drivers by points: if/else 13 (50 pts), boolean chains 7, match/switch 1 (3 pts), error handling 1, loops 1 (nesting depth added 39). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
widgets2.NotesWidget (cognitive 59) REDACTED:681— widgets2.NotesWidget has cognitive complexity 59 (threshold 15). Drivers by points: if/else 23 (29 pts), ternaries 12 (16 pts), boolean chains 11, loops 2, error handling 1 (nesting depth added 10). Most of this is not in the body itself: 11 of the 59 points are its own statements and the rest belongs to 12 function items inside it that branch (locateFromEvent, a function literal at line 745, openFromPreview, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
FilesView.FilePreview (cognitive 59) dashboard/src/pages/FilesView.jsx:148— FilesView.FilePreview has cognitive complexity 59 (threshold 15). Drivers by points: boolean chains 28, if/else 17 (21 pts), ternaries 5 (8 pts), error handling 2 (nesting depth added 7). Of this number, 23 points are the body's own statements and 36 belong to 6 function items inside it that branch. To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition.
widgets2.FileViewerWidget (cognitive 58) REDACTED:1293— widgets2.FileViewerWidget has cognitive complexity 58 (threshold 15). Drivers by points: if/else 12 (22 pts), ternaries 9 (21 pts), boolean chains 11, loops 2 (4 pts) (nesting depth added 24). Of this number, 22 points are the body's own statements and 36 belong to 11 function items inside it that branch. To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
hzl-service.deleteTask (cognitive 57) dashboard/hzl-service.js:1747— hzl-service.deleteTask has cognitive complexity 57 (threshold 15). Drivers by points: if/else 13 (29 pts), error handling 4 (14 pts), boolean chains 8, loops 2 (6 pts) (nesting depth added 30). 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.
widgets2.RepoStatusWidget (cognitive 57) REDACTED:1160— widgets2.RepoStatusWidget has cognitive complexity 57 (threshold 15). Drivers by points: ternaries 14 (29 pts), if/else 12 (18 pts), boolean chains 10 (nesting depth added 21). Of this number, 25 points are the body's own statements and 32 belong to 11 function items inside it that branch. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
validateOverview (cognitive 55) dashboard/overview.js:525— validateOverview has cognitive complexity 55 (threshold 15). Drivers by points: if/else 23 (31 pts), boolean chains 19, ternaries 3, loops 1 (2 pts) (nesting depth added 9). Most of this is not in the body itself: 10 of the 55 points are its own statements and the rest belongs to one function literal inside it that branches (line 538). 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.
hzl-service.createTaskRaw (cognitive 53) dashboard/hzl-service.js:1248— hzl-service.createTaskRaw has cognitive complexity 53 (threshold 15). Drivers by points: ternaries 20 (23 pts), if/else 13 (17 pts), boolean chains 11, error handling 1 (2 pts) (nesting depth added 8). 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.
hzl-service.getProjectHistory (cognitive 53) dashboard/hzl-service.js:2693— hzl-service.getProjectHistory has cognitive complexity 53 (threshold 15). Drivers by points: ternaries 9 (29 pts), if/else 5 (11 pts), boolean chains 10, loops 2 (3 pts) (nesting depth added 27). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
project-bundle-validator.validateTasks (cognitive 53) dashboard/project-bundle-validator.js:313— project-bundle-validator.validateTasks has cognitive complexity 53 (threshold 15). Drivers by points: if/else 24 (40 pts), loops 5 (7 pts), boolean chains 6 (nesting depth added 18). Of this number, 30 points are the body's own statements and 23 belong to 3 function items inside it that branch. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
WorkStatePopover.WorkStatePopover (cognitive 52) dashboard/src/components/WorkStatePopover.jsx:126— WorkStatePopover.WorkStatePopover has cognitive complexity 52 (threshold 15). Drivers by points: boolean chains 27, if/else 15 (16 pts), ternaries 8, error handling 1 (nesting depth added 1). Most of this is not in the body itself: 15 of the 52 points are its own statements and the rest belongs to 11 function items inside it that branch (commit, loadDraftForState, handleQuestionSubmit, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
apiFetch (cognitive 52) dashboard/src/utils/apiFetch.js:37— apiFetch has cognitive complexity 52 (threshold 15). Drivers by points: if/else 22 (35 pts), boolean chains 12, error handling 3 (4 pts), ternaries 1 (nesting depth added 14). Of this number, 43 points are the body's own statements and 9 belong to 6 function items inside it that branch. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
systemd-config.parseSystemdEnvironment (cognitive 51) scripts/systemd-config.mjs:246— systemd-config.parseSystemdEnvironment has cognitive complexity 51 (threshold 15). Drivers by points: if/else 17 (40 pts), loops 3 (6 pts), ternaries 1 (3 pts), boolean chains 2 (nesting depth added 28). Of this number, 42 points are the body's own statements and 9 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.
getProjectActivity (cognitive 51) dashboard/hzl-service.js:2931— getProjectActivity has cognitive complexity 51 (threshold 15). Drivers by points: if/else 12 (25 pts), ternaries 5 (15 pts), boolean chains 6, loops 4 (5 pts) (nesting depth added 24). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
(anonymous) (cognitive 49) dashboard/tools/ov-audit.mjs:51— (anonymous) has cognitive complexity 49 (threshold 15). Drivers by points: if/else 11 (33 pts), loops 4 (12 pts), boolean chains 4 (nesting depth added 30). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
evaluateCreationPolicy (cognitive 48) dashboard/task-creation-policy.js:107— evaluateCreationPolicy has cognitive complexity 48 (threshold 15). Drivers by points: if/else 23 (35 pts), boolean chains 11, ternaries 2 (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.
getStuckTasks (cognitive 48) dashboard/hzl-service.js:3513— getStuckTasks has cognitive complexity 48 (threshold 15). Drivers by points: if/else 11 (25 pts), boolean chains 13, ternaries 5 (8 pts), loops 1, other 1 (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.
rules-api.buildOperationalTaskStateMarkdown (cognitive 46) dashboard/rules-api.js:217— rules-api.buildOperationalTaskStateMarkdown has cognitive complexity 46 (threshold 15). Drivers by points: ternaries 6 (17 pts), if/else 15 (16 pts), loops 3 (7 pts), boolean chains 6 (nesting depth added 16). Of this number, 45 points are the body's own statements and 1 belongs to one function literal inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
server.persistSpecifyProposal (cognitive 44) REDACTED:726— server.persistSpecifyProposal has cognitive complexity 44 (threshold 15). Drivers by points: boolean chains 15, if/else 8 (10 pts), ternaries 5 (8 pts), error handling 3 (7 pts), loops 2 (4 pts) (nesting depth added 11). Of this number, 26 points are the body's own statements and 18 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.
ProjectBundleModals.ExportProjectModal (cognitive 44) dashboard/src/components/ProjectBundleModals.jsx:201— ProjectBundleModals.ExportProjectModal has cognitive complexity 44 (threshold 15). Drivers by points: boolean chains 23, if/else 8 (9 pts), ternaries 7 (9 pts), error handling 3 (nesting depth added 3). Of this number, 17 points are the body's own statements and 27 belong to 7 function items inside it that branch. To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
ProjectBundleImporter.importBundle (cognitive 43) dashboard/project-bundle-import.js:849— ProjectBundleImporter.importBundle has cognitive complexity 43 (threshold 15). Drivers by points: if/else 15 (19 pts), boolean chains 12, error handling 4 (9 pts), ternaries 2 (3 pts) (nesting depth added 10). 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.
rebuildCache (cognitive 43) dashboard/hzl-service.js:618— rebuildCache has cognitive complexity 43 (threshold 15). Drivers by points: if/else 10 (22 pts), loops 6 (8 pts), error handling 4 (7 pts), boolean chains 5, ternaries 1 (nesting depth added 17). Of this number, 40 points are the body's own statements and 3 belong to one function literal inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
project-bundle-validator.validateManifest (cognitive 42) dashboard/project-bundle-validator.js:196— project-bundle-validator.validateManifest has cognitive complexity 42 (threshold 15). Drivers by points: if/else 26 (32 pts), boolean chains 4, loops 3 (4 pts), error handling 1 (2 pts) (nesting depth added 8). Of this number, 40 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, 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.
decisionFields (cognitive 42) dashboard/specify-policy.js:149— decisionFields has cognitive complexity 42 (threshold 15). Drivers by points: if/else 16 (28 pts), boolean chains 9, loops 3 (5 pts) (nesting depth added 14). Most of this is not in the body itself: 11 of the 42 points are its own statements and the rest belongs to 3 function items inside it that branch (a function literal at line 171, addNamedFields, addField). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
migrateProject (cognitive 42) dashboard/migrate-tasks.js:159— migrateProject has cognitive complexity 42 (threshold 15). Drivers by points: if/else 9 (17 pts), ternaries 5 (13 pts), boolean chains 7, loops 2 (3 pts), error handling 1 (2 pts) (nesting depth added 18). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
widgets2.StallDetectionWidget (cognitive 41) REDACTED:1025— widgets2.StallDetectionWidget has cognitive complexity 41 (threshold 15). Drivers by points: ternaries 16 (23 pts), boolean chains 12, if/else 6 (nesting depth added 7). Of this number, 27 points are the body's own statements and 14 belong to 8 function items inside it that branch. To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition.
applyOps (cognitive 41) dashboard/overview.js:395— applyOps has cognitive complexity 41 (threshold 15). Drivers by points: ternaries 15 (22 pts), boolean chains 10, if/else 4 (8 pts), match/switch 1 (nesting depth added 11). Most of this is not in the body itself: 3 of the 41 points are its own statements and the rest belongs to 5 function items inside it that branch (a function literal at line 417, a function literal at line 402, sizeToWidth, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
fetchInsight (cognitive 41) dashboard/github.js:120— fetchInsight has cognitive complexity 41 (threshold 15). Drivers by points: if/else 10 (15 pts), boolean chains 14, error handling 3 (6 pts), ternaries 3 (6 pts) (nesting depth added 11). Of this number, 33 points are the body's own statements and 8 belong to 9 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.
ConnectionLayer.ConnectionLayer (cognitive 40) dashboard/src/components/canvas/ConnectionLayer.jsx:16— ConnectionLayer.ConnectionLayer has cognitive complexity 40 (threshold 15). Drivers by points: if/else 9 (20 pts), boolean chains 10, ternaries 4 (6 pts), loops 3 (4 pts) (nesting depth added 14). Of this number, 34 points are the body's own statements and 6 belong to 2 function items inside it that branch. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
renderNoteMarkdown (cognitive 40) dashboard/src/utils/canvasMarkdown.mjs:18— renderNoteMarkdown has cognitive complexity 40 (threshold 15). Drivers by points: if/else 15 (31 pts), ternaries 3 (8 pts), loops 1 (nesting depth added 21). Of this number, 34 points are the body's own statements and 6 belong to 2 function literals inside it that branch. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
ProjectBundleImporter._publishStagedFiles (cognitive 39) dashboard/project-bundle-import.js:502— ProjectBundleImporter._publishStagedFiles has cognitive complexity 39 (threshold 15). Drivers by points: if/else 13 (30 pts), error handling 2 (5 pts), boolean chains 3, loops 1 (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.
ProjectBundleImporter._restoreHistory (cognitive 39) dashboard/project-bundle-import.js:707— ProjectBundleImporter._restoreHistory has cognitive complexity 39 (threshold 15). Drivers by points: if/else 7 (16 pts), boolean chains 15, ternaries 3 (7 pts), loops 1 (nesting depth added 13). Of this number, 33 points are the body's own statements and 6 belong to 3 function items inside it that branch. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
CreateProjectModal.CreateProjectModal (cognitive 39) dashboard/src/components/CreateProjectModal.jsx:26— CreateProjectModal.CreateProjectModal has cognitive complexity 39 (threshold 15). Drivers by points: if/else 12 (13 pts), ternaries 9 (13 pts), boolean chains 11, error handling 2 (nesting depth added 5). Of this number, 22 points are the body's own statements and 17 belong to 9 function items inside it that branch. To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition.
buildFileTree (cognitive 39) REDACTED:3224— buildFileTree has cognitive complexity 39 (threshold 15). Drivers by points: if/else 14 (23 pts), ternaries 3 (6 pts), loops 5, boolean chains 2, other 2, error handling 1 (nesting depth added 12). Most of this is not in the body itself: 15 of the 39 points are its own statements and the rest belongs to 4 function items inside it that branch (walk, a function literal at line 3290, sortEntries, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
hzl-service.getNotifiableStuckTasks (cognitive 38) dashboard/hzl-service.js:3676— hzl-service.getNotifiableStuckTasks has cognitive complexity 38 (threshold 15). Drivers by points: if/else 11 (20 pts), boolean chains 10, loops 8 (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
specify-policy._validateProposal (cognitive 38) dashboard/specify-policy.js:93— specify-policy._validateProposal has cognitive complexity 38 (threshold 15). Drivers by points: if/else 11 (25 pts), ternaries 2 (6 pts), boolean chains 5, loops 1 (2 pts) (nesting depth added 19). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
widgets3.GhCiWidget (cognitive 38) REDACTED:167— widgets3.GhCiWidget has cognitive complexity 38 (threshold 15). Drivers by points: ternaries 11 (27 pts), boolean chains 9, if/else 2 (nesting depth added 16). Of this number, 17 points are the body's own statements and 21 belong to 3 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.
(anonymous) (cognitive 38) REDACTED:4149— (anonymous) has cognitive complexity 38 (threshold 15). Drivers by points: if/else 16 (22 pts), boolean chains 15, error handling 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.
ProjectBundleImporter._canonicalAdmission (cognitive 37) dashboard/project-bundle-import.js:367— ProjectBundleImporter._canonicalAdmission has cognitive complexity 37 (threshold 15). Drivers by points: boolean chains 15, ternaries 7 (11 pts), if/else 10, error handling 1 (nesting depth added 4). 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: 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.
widgets3.AgentQuestionsWidget (cognitive 37) REDACTED:352— widgets3.AgentQuestionsWidget has cognitive complexity 37 (threshold 15). Drivers by points: if/else 8 (14 pts), ternaries 7 (14 pts), boolean chains 9 (nesting depth added 13). Most of this is not in the body itself: 5 of the 37 points are its own statements and the rest belongs to 7 function items inside it that branch (sendAnswer, a function literal at line 411, a function literal at line 363, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
setup.readExistingServiceConfig (cognitive 37) scripts/setup.mjs:448— setup.readExistingServiceConfig has cognitive complexity 37 (threshold 15). Drivers by points: if/else 13 (21 pts), loops 4 (11 pts), boolean chains 2, error handling 1 (2 pts), ternaries 1 (nesting depth added 16). 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.
rankTasks (cognitive 37) dashboard/smart-search.js:140— rankTasks has cognitive complexity 37 (threshold 15). Drivers by points: if/else 13 (24 pts), boolean chains 6, loops 2 (4 pts), other 2, ternaries 1 (nesting depth added 13). Of this number, 31 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.
_importTasks (cognitive 37) dashboard/project-bundle-import.js:618— _importTasks has cognitive complexity 37 (threshold 15). Drivers by points: if/else 9 (20 pts), boolean chains 11, loops 2 (3 pts), other 3 (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.
smart-search.passesFilters (cognitive 36) dashboard/smart-search.js:113— smart-search.passesFilters has cognitive complexity 36 (threshold 15). Drivers by points: if/else 13 (23 pts), boolean chains 12, loops 1 (nesting depth added 10). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
hzl-service.buildHandoffMarkdown (cognitive 36) dashboard/hzl-service.js:4037— hzl-service.buildHandoffMarkdown has cognitive complexity 36 (threshold 15). Drivers by points: if/else 16 (19 pts), boolean chains 9, ternaries 3 (6 pts), error handling 2 (nesting depth added 6). Of this number, 34 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.
snippets-doctor.collectStatus (cognitive 36) dashboard/snippets-doctor.js:623— snippets-doctor.collectStatus has cognitive complexity 36 (threshold 15). Drivers by points: if/else 8 (15 pts), boolean chains 7, error handling 3 (7 pts), loops 5 (7 pts) (nesting depth added 13). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
apiFetch.apiJson (cognitive 35) dashboard/src/utils/apiFetch.js:285— apiFetch.apiJson has cognitive complexity 35 (threshold 15). Drivers by points: ternaries 8 (16 pts), boolean chains 12, if/else 4 (5 pts), error handling 2 (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
CanvasMiniMap.CanvasMiniMap (cognitive 35) REDACTED:37— CanvasMiniMap.CanvasMiniMap has cognitive complexity 35 (threshold 15). Drivers by points: boolean chains 13, if/else 11 (12 pts), ternaries 8 (10 pts) (nesting depth added 3). Of this number, 16 points are the body's own statements and 19 belong to 10 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.
canvasTextFormat.applyFormattingToTextarea (cognitive 35) dashboard/src/utils/canvasTextFormat.mjs:7— canvasTextFormat.applyFormattingToTextarea has cognitive complexity 35 (threshold 15). Drivers by points: if/else 15 (16 pts), ternaries 5 (10 pts), boolean chains 8, match/switch 1 (nesting depth added 6). Most of this is not in the body itself: 6 of the 35 points are its own statements and the rest belongs to 8 function items inside it that branch (isWrapped, isSurrounded, wrapInline, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
(anonymous) (cognitive 35) REDACTED:2254— (anonymous) has cognitive complexity 35 (threshold 15). Drivers by points: ternaries 10 (17 pts), boolean chains 12, if/else 3 (4 pts), error handling 2 (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.
canvasGeometry.computePortPositions (cognitive 34) dashboard/src/utils/canvasGeometry.mjs:329— canvasGeometry.computePortPositions has cognitive complexity 34 (threshold 15). Drivers by points: if/else 11 (21 pts), ternaries 3 (6 pts), boolean chains 4, loops 3 (nesting depth added 13). Of this number, 21 points are the body's own statements and 13 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.
hzl-service._toFbTask (cognitive 33) dashboard/hzl-service.js:198— hzl-service._toFbTask has cognitive complexity 33 (threshold 15). Drivers by points: boolean chains 22, ternaries 6 (10 pts), if/else 1 (nesting depth added 4). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
project-lifecycle._validateUpdateInput (cognitive 33) dashboard/project-lifecycle.js:305— project-lifecycle._validateUpdateInput has cognitive complexity 33 (threshold 15). Drivers by points: if/else 18 (30 pts), boolean chains 3 (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.
server.app.post("/api/projects/import") (cognitive 33) REDACTED:2254— server.app.post("/api/projects/import") has cognitive complexity 33 (threshold 15). Drivers by points: ternaries 9 (15 pts), boolean chains 12, if/else 3 (4 pts), error handling 2 (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
hzl-service.getComplianceStatus (cognitive 32) dashboard/hzl-service.js:3827— hzl-service.getComplianceStatus has cognitive complexity 32 (threshold 15). Drivers by points: if/else 10 (25 pts), boolean chains 6, loops 1 (nesting depth added 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
(anonymous) (cognitive 32) REDACTED:4289— (anonymous) has cognitive complexity 32 (threshold 15). Drivers by points: boolean chains 9, if/else 6 (9 pts), ternaries 7 (9 pts), error handling 2 (5 pts) (nesting depth added 8). Of this number, 30 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.
snippets-doctor.applyActions (cognitive 31) dashboard/snippets-doctor.js:733— snippets-doctor.applyActions has cognitive complexity 31 (threshold 15). Drivers by points: if/else 10 (21 pts), error handling 3 (6 pts), ternaries 1 (2 pts), boolean chains 1, loops 1 (nesting depth added 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
project-bundle-export.toPortableHistoryFromEvents (cognitive 31) dashboard/project-bundle-export.js:434— project-bundle-export.toPortableHistoryFromEvents has cognitive complexity 31 (threshold 15). Drivers by points: ternaries 5 (14 pts), boolean chains 12, if/else 2 (3 pts), loops 2 (nesting depth added 10). Of this number, 26 points are the body's own statements and 5 belong to one function literal inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
_validateQuestion (cognitive 31) dashboard/specify-policy.js:53— _validateQuestion has cognitive complexity 31 (threshold 15). Drivers by points: if/else 10 (21 pts), boolean chains 7, loops 1 (3 pts) (nesting depth added 13). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
specify-sessions.createSession (cognitive 30) dashboard/specify-sessions.js:47— specify-sessions.createSession has cognitive complexity 30 (threshold 15). Drivers by points: if/else 6 (12 pts), boolean chains 10, ternaries 4 (5 pts), 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.
updateProjectMeta (cognitive 30) dashboard/flowboard-metadata.js:269— updateProjectMeta has cognitive complexity 30 (threshold 15). Drivers by points: if/else 15 (20 pts), ternaries 3 (6 pts), boolean chains 4 (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.
canvasReducer (cognitive 30) dashboard/src/state/canvasStore.mjs:28— canvasReducer has cognitive complexity 30 (threshold 15). Drivers by points: boolean chains 12, ternaries 4 (8 pts), if/else 4 (7 pts), other 2, match/switch 1 (nesting depth added 7). Most of this is not in the body itself: 12 of the 30 points are its own statements and the rest belongs to 8 function literals inside it that branch (lines 113, 127, 83, …). 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.
dashboardApi.validateTask (cognitive 29) dashboard/src/utils/dashboardApi.js:131— dashboardApi.validateTask has cognitive complexity 29 (threshold 15). Drivers by points: boolean chains 20, loops 2 (4 pts), ternaries 1 (3 pts), if/else 2 (nesting depth added 4). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
canvasTextFormat.insertNumberedPrefix (cognitive 29) dashboard/src/utils/canvasTextFormat.mjs:179— canvasTextFormat.insertNumberedPrefix has cognitive complexity 29 (threshold 15). Drivers by points: ternaries 9 (24 pts), if/else 4 (5 pts) (nesting depth added 16). Of this number, 20 points are the body's own statements and 9 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.
hzl-service.renderStatusEventMessage (cognitive 28) dashboard/hzl-service.js:3116— hzl-service.renderStatusEventMessage has cognitive complexity 28 (threshold 15). Drivers by points: ternaries 5 (12 pts), if/else 5 (10 pts), boolean chains 5, match/switch 1 (nesting depth added 12). 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.
project-bundle-validator.validateOverview (cognitive 28) dashboard/project-bundle-validator.js:483— project-bundle-validator.validateOverview has cognitive complexity 28 (threshold 15). Drivers by points: if/else 16 (17 pts), boolean chains 10, loops 1 (nesting depth added 1). Most of this is not in the body itself: 4 of the 28 points are its own statements and the rest belongs to one function literal inside it that branches (line 489). 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.
ProjectBundleImporter._verify (cognitive 28) dashboard/project-bundle-import.js:775— ProjectBundleImporter._verify has cognitive complexity 28 (threshold 15). Drivers by points: if/else 9 (15 pts), boolean chains 10, loops 3 (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
stuck-notify.buildStuckNotifications (cognitive 28) REDACTED:48— stuck-notify.buildStuckNotifications has cognitive complexity 28 (threshold 15). Drivers by points: ternaries 8 (11 pts), boolean chains 7, if/else 6, loops 4 (nesting depth added 3). Of this number, 16 points are the body's own statements and 12 belong to 3 function items inside it that branch. To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition.
Modal.Modal (cognitive 28) dashboard/src/components/Modal.jsx:28— Modal.Modal has cognitive complexity 28 (threshold 15). Drivers by points: boolean chains 15, if/else 10 (12 pts), ternaries 1 (nesting depth added 2). Most of this is not in the body itself: 9 of the 28 points are its own statements and the rest belongs to 5 function items inside it that branch (a function literal at line 42, a function literal at line 73, handleOverlayPointerDown, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
SearchPalette.SearchPalette (cognitive 28) dashboard/src/components/SearchPalette.jsx:19— SearchPalette.SearchPalette has cognitive complexity 28 (threshold 15). Drivers by points: boolean chains 16, if/else 12. Most of this is not in the body itself: 13 of the 28 points are its own statements and the rest belongs to 7 function items inside it that branch (a function literal at line 39, handleKeyDown, a function literal at line 69, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
canvasMarkdown.parseMarkdownHtml::parseNode (cognitive 28) dashboard/src/utils/canvasMarkdown.mjs:105— canvasMarkdown.parseMarkdownHtml::parseNode has cognitive complexity 28 (threshold 15). Drivers by points: if/else 12 (17 pts), boolean chains 4, ternaries 2 (4 pts), 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.
systemd-config.splitSystemdWords (cognitive 28) scripts/systemd-config.mjs:39— systemd-config.splitSystemdWords has cognitive complexity 28 (threshold 15). Drivers by points: if/else 14 (24 pts), boolean chains 3, loops 1 (nesting depth added 10). Of this number, 27 points are the body's own statements and 1 belongs to one function item inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
fetchRepoStatus (cognitive 28) dashboard/github.js:51— fetchRepoStatus has cognitive complexity 28 (threshold 15). Drivers by points: boolean chains 14, if/else 7 (10 pts), error handling 3 (4 pts) (nesting depth added 4). Of this number, 23 points are the body's own statements and 5 belong to 7 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.
hzl-service.setTaskParent (cognitive 27) dashboard/hzl-service.js:2104— hzl-service.setTaskParent has cognitive complexity 27 (threshold 15). Drivers by points: if/else 9 (12 pts), boolean chains 8, error handling 2 (4 pts), ternaries 2, loops 1 (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.
rate-limiter.parseIpAddress (cognitive 27) dashboard/rate-limiter.js:154— rate-limiter.parseIpAddress has cognitive complexity 27 (threshold 15). Drivers by points: if/else 13 (15 pts), boolean chains 9, ternaries 3 (nesting depth added 2). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition.
server.handleSpecifyStep (cognitive 27) REDACTED:4048— server.handleSpecifyStep has cognitive complexity 27 (threshold 15). Drivers by points: if/else 11 (14 pts), boolean chains 7, ternaries 3 (5 pts), error handling 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.
ProjectBundleModals.WarningList (cognitive 27) dashboard/src/components/ProjectBundleModals.jsx:102— ProjectBundleModals.WarningList has cognitive complexity 27 (threshold 15). Drivers by points: boolean chains 14, ternaries 9 (12 pts), if/else 1 (nesting depth added 3). Most of this is not in the body itself: 3 of the 27 points are its own statements and the rest belongs to one function literal inside it that branches (line 110). 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.
(anonymous) (cognitive 27) REDACTED:3818— (anonymous) has cognitive complexity 27 (threshold 15). Drivers by points: boolean chains 12, if/else 6 (7 pts), ternaries 5, error handling 2 (3 pts) (nesting depth added 2). Of this number, 26 points are the body's own statements and 1 belongs to 3 function literals inside it that branch. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
canvasImportFromJson (cognitive 27) dashboard/hzl-service.js:4803— canvasImportFromJson has cognitive complexity 27 (threshold 15). Drivers by points: if/else 6 (11 pts), boolean chains 10, loops 2, other 2, ternaries 1 (2 pts) (nesting depth added 6). Most of this is not in the body itself: 2 of the 27 points are its own statements and the rest belongs to one function literal inside it that branches (line 4810). 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.
hzl-service.evaluateStuckIndicators (cognitive 26) dashboard/hzl-service.js:3413— hzl-service.evaluateStuckIndicators has cognitive complexity 26 (threshold 15). Drivers by points: if/else 5 (12 pts), boolean chains 5, error handling 1 (4 pts), ternaries 2 (4 pts), loops 1 (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.
NoteCard.NoteCard (cognitive 26) dashboard/src/components/canvas/NoteCard.jsx:49— NoteCard.NoteCard has cognitive complexity 26 (threshold 15). Drivers by points: ternaries 10, if/else 7 (9 pts), boolean chains 7 (nesting depth added 2). Most of this is not in the body itself: 12 of the 26 points are its own statements and the rest belongs to 7 function literals inside it that branch (lines 176, 64, 74, …). 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.
widgets3.GhPullsWidget (cognitive 26) REDACTED:111— widgets3.GhPullsWidget has cognitive complexity 26 (threshold 15). Drivers by points: ternaries 7 (17 pts), boolean chains 8, if/else 1 (nesting depth added 10). Of this number, 21 points are the body's own statements and 5 belong to one function literal inside it that branches. 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.
validateCanvas (cognitive 26) dashboard/project-bundle-validator.js:442— validateCanvas has cognitive complexity 26 (threshold 15). Drivers by points: if/else 14 (16 pts), boolean chains 7, ternaries 1 (2 pts), loops 1 (nesting depth added 3). Most of this is not in the body itself: 4 of the 26 points are its own statements and the rest belongs to 2 function literals inside it that branch (lines 462, 448). 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.
createBundle (cognitive 26) dashboard/project-bundle-schema.js:433— createBundle has cognitive complexity 26 (threshold 15). Drivers by points: boolean chains 13, if/else 4 (7 pts), ternaries 4 (5 pts), loops 1 (nesting depth added 4). Of this number, 21 points are the body's own statements and 5 belong to 2 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.
bundle-freshness.newestMtime (cognitive 25) dashboard/bundle-freshness.js:35— bundle-freshness.newestMtime has cognitive complexity 25 (threshold 15). Drivers by points: if/else 8 (18 pts), boolean chains 3, error handling 2 (3 pts), loops 1 (nesting depth added 11). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
hzl-service.canvasSaveConnection (cognitive 25) dashboard/hzl-service.js:4713— hzl-service.canvasSaveConnection has cognitive complexity 25 (threshold 15). Drivers by points: boolean chains 15, if/else 7 (10 pts) (nesting depth added 3). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
project-bundle-validator.validateFiles (cognitive 25) dashboard/project-bundle-validator.js:511— project-bundle-validator.validateFiles has cognitive complexity 25 (threshold 15). Drivers by points: if/else 13 (18 pts), boolean chains 5, error handling 1 (2 pts) (nesting depth added 6). Most of this is not in the body itself: 2 of the 25 points are its own statements and the rest belongs to one function literal inside it that branches (line 516). 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.
TrashPanel.TrashPanel (cognitive 25) dashboard/src/components/TrashPanel.jsx:22— TrashPanel.TrashPanel has cognitive complexity 25 (threshold 15). Drivers by points: if/else 11 (12 pts), ternaries 5 (8 pts), boolean chains 4, error handling 1 (nesting depth added 4). Most of this is not in the body itself: 9 of the 25 points are its own statements and the rest belongs to 4 function items inside it that branch (handleEmpty, formatWhen, a function literal at line 26, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
widgets.TaskStatsWidget (cognitive 25) REDACTED:217— widgets.TaskStatsWidget has cognitive complexity 25 (threshold 15). Drivers by points: boolean chains 12, if/else 6 (7 pts), ternaries 5, loops 1 (nesting depth added 1). Most of this is not in the body itself: 10 of the 25 points are its own statements and the rest belongs to 8 function items inside it that branch (a function literal at line 242, a function literal at line 229, jumpTo, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
widgets3.GhIssuesWidget (cognitive 25) REDACTED:289— widgets3.GhIssuesWidget has cognitive complexity 25 (threshold 15). Drivers by points: ternaries 7 (19 pts), boolean chains 5, if/else 1 (nesting depth added 12). Of this number, 15 points are the body's own statements and 10 belong to 4 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.
setup.parseLaunchdEnvironment (cognitive 25) scripts/setup.mjs:209— setup.parseLaunchdEnvironment has cognitive complexity 25 (threshold 15). Drivers by points: if/else 8 (12 pts), boolean chains 5, error handling 2 (4 pts), ternaries 2 (3 pts), 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.
(anonymous) (cognitive 25) REDACTED:3154— (anonymous) has cognitive complexity 25 (threshold 15). Drivers by points: if/else 8 (13 pts), boolean chains 4, error handling 2 (4 pts), loops 2, ternaries 2 (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity· run (cognitive 25) · ×1
run (cognitive 25) dashboard/migrations.js:183— run has cognitive complexity 25 (threshold 15). Drivers by points: if/else 12 (19 pts), error handling 2 (4 pts), loops 2 (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
smartSearchTasks (cognitive 25) dashboard/hzl-service.js:2195— smartSearchTasks has cognitive complexity 25 (threshold 15). Drivers by points: boolean chains 11, if/else 5 (7 pts), error handling 2 (4 pts), ternaries 2, loops 1 (nesting depth added 4). Of this number, 17 points are the body's own statements and 8 belong to 6 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.
canvas-placement.autoPlaceNote (cognitive 24) dashboard/canvas-placement.js:43— canvas-placement.autoPlaceNote has cognitive complexity 24 (threshold 15). Drivers by points: if/else 5 (11 pts), loops 4 (8 pts), boolean chains 3, ternaries 2 (nesting depth added 10). Of this number, 23 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.
install-trigger.main (cognitive 24) dashboard/install-trigger.mjs:152— install-trigger.main has cognitive complexity 24 (threshold 15). Drivers by points: if/else 11 (17 pts), error handling 2 (3 pts), boolean chains 2, ternaries 1 (2 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.
project-bundle-validator.validateHistory (cognitive 24) dashboard/project-bundle-validator.js:543— project-bundle-validator.validateHistory has cognitive complexity 24 (threshold 15). Drivers by points: if/else 15 (16 pts), boolean chains 7, loops 1 (nesting depth added 1). Most of this is not in the body itself: 8 of the 24 points are its own statements and the rest belongs to 3 function items inside it that branch (a function literal at line 553, a function literal at line 574, validateHistoryId). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
widgets2.ContextIndexWidget (cognitive 24) REDACTED:578— widgets2.ContextIndexWidget has cognitive complexity 24 (threshold 15). Drivers by points: ternaries 7 (11 pts), boolean chains 10, if/else 3 (nesting depth added 4). Most of this is not in the body itself: 9 of the 24 points are its own statements and the rest belongs to 7 function literals inside it that branch (lines 614, 589, 584, …). 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.
_normalizeResponse (cognitive 24) dashboard/specify-worker-bridge.js:110— _normalizeResponse has cognitive complexity 24 (threshold 15). Drivers by points: boolean chains 15, if/else 5 (6 pts), ternaries 1 (2 pts), other 1 (nesting depth added 2). 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.
project-bundle-validator.validateSpecs (cognitive 23) dashboard/project-bundle-validator.js:408— project-bundle-validator.validateSpecs has cognitive complexity 23 (threshold 15). Drivers by points: if/else 10 (14 pts), boolean chains 4, error handling 2 (4 pts), loops 1 (nesting depth added 6). Most of this is not in the body itself: 10 of the 23 points are its own statements and the rest belongs to one function literal inside it that branches (line 411). 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.
project-bundle-export.readLinkedSpecs (cognitive 23) dashboard/project-bundle-export.js:361— project-bundle-export.readLinkedSpecs has cognitive complexity 23 (threshold 15). Drivers by points: if/else 7 (14 pts), error handling 3 (6 pts), boolean chains 2, loops 1 (nesting depth added 10). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
specify-worker-openclaw.extractJsonObject (cognitive 23) dashboard/specify-worker-openclaw.js:106— specify-worker-openclaw.extractJsonObject has cognitive complexity 23 (threshold 15). Drivers by points: if/else 9 (17 pts), error handling 1 (4 pts), boolean chains 1, loops 1 (nesting depth added 11). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
server.telegramAuthMiddleware (cognitive 23) REDACTED:389— server.telegramAuthMiddleware has cognitive complexity 23 (threshold 15). Drivers by points: if/else 9 (15 pts), boolean chains 8 (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.
server.app.get("/api/projects/:name/tasks") (cognitive 23) REDACTED:2598— server.app.get("/api/projects/:name/tasks") has cognitive complexity 23 (threshold 15). Drivers by points: boolean chains 12, if/else 7, ternaries 2 (3 pts), error handling 1 (nesting depth added 1). Of this number, 18 points are the body's own statements and 5 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.
normalizeWorkStateDetails (cognitive 23) dashboard/work-state.js:92— normalizeWorkStateDetails has cognitive complexity 23 (threshold 15). Drivers by points: if/else 9 (12 pts), boolean chains 8, loops 2, ternaries 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.
(anonymous) (cognitive 23) REDACTED:3952— (anonymous) has cognitive complexity 23 (threshold 15). Drivers by points: boolean chains 9, ternaries 6, if/else 4, other 3, error handling 1. 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.
addComment (cognitive 23) dashboard/hzl-service.js:2836— addComment has cognitive complexity 23 (threshold 15). Drivers by points: ternaries 5 (8 pts), boolean chains 7, if/else 6 (7 pts), other 1 (nesting depth added 4). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
ProjectBundleImporter._stageBundle (cognitive 22) dashboard/project-bundle-import.js:456— ProjectBundleImporter._stageBundle has cognitive complexity 22 (threshold 15). Drivers by points: if/else 8 (13 pts), boolean chains 3, error handling 2 (3 pts), ternaries 1 (2 pts), 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.
project-lifecycle.deleteProject (cognitive 22) dashboard/project-lifecycle.js:418— project-lifecycle.deleteProject has cognitive complexity 22 (threshold 15). Drivers by points: error handling 5 (9 pts), if/else 5 (7 pts), boolean chains 3, ternaries 1 (2 pts), 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.
MoveTaskModal.MoveTaskModal (cognitive 22) dashboard/src/components/MoveTaskModal.jsx:15— MoveTaskModal.MoveTaskModal has cognitive complexity 22 (threshold 15). Drivers by points: boolean chains 12, if/else 7, ternaries 1 (2 pts), error handling 1 (nesting depth added 1). Most of this is not in the body itself: 10 of the 22 points are its own statements and the rest belongs to 6 function items inside it that branch (call, handleReparent, a function literal at line 25, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
ClaimStateLine.ClaimStateLine (cognitive 22) dashboard/src/components/ClaimStateLine.jsx:63— ClaimStateLine.ClaimStateLine has cognitive complexity 22 (threshold 15). Drivers by points: boolean chains 11, if/else 9 (11 pts) (nesting depth added 2). 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.
setup.readSystemdEnvironmentFiles (cognitive 22) scripts/setup.mjs:389— setup.readSystemdEnvironmentFiles has cognitive complexity 22 (threshold 15). Drivers by points: if/else 5 (12 pts), error handling 2 (4 pts), loops 2 (3 pts), boolean chains 2, ternaries 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.
canvasSaveConnection (cognitive 22) REDACTED:941— canvasSaveConnection has cognitive complexity 22 (threshold 15). Drivers by points: if/else 9 (12 pts), boolean chains 10 (nesting depth added 3). Of this number, 19 points are the body's own statements and 3 belong to 2 function literals inside it that branch. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
buildDashboardSnapshot (cognitive 22) dashboard/dashboard-snapshot.js:45— buildDashboardSnapshot has cognitive complexity 22 (threshold 15). Drivers by points: boolean chains 11, ternaries 10, if/else 1. Of this number, 21 points are the body's own statements and 1 belongs to 5 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.
hzl-service.getOpenQuestions (cognitive 21) dashboard/hzl-service.js:3048— hzl-service.getOpenQuestions has cognitive complexity 21 (threshold 15). Drivers by points: if/else 6 (11 pts), boolean chains 6, loops 2, ternaries 1 (2 pts) (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
hzl-service.getCheckpointHealth (cognitive 21) dashboard/hzl-service.js:3765— hzl-service.getCheckpointHealth has cognitive complexity 21 (threshold 15). Drivers by points: if/else 10 (16 pts), boolean chains 5 (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.
dashboardApi.fetchDashboardSnapshot (cognitive 21) dashboard/src/utils/dashboardApi.js:318— dashboardApi.fetchDashboardSnapshot has cognitive complexity 21 (threshold 15). Drivers by points: boolean chains 10, if/else 6 (7 pts), ternaries 2, error handling 1, loops 1 (nesting depth added 1). 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.
CanvasToolbar.CanvasToolbar (cognitive 21) dashboard/src/components/canvas/CanvasToolbar.jsx:23— CanvasToolbar.CanvasToolbar has cognitive complexity 21 (threshold 15). Drivers by points: boolean chains 9, if/else 8 (9 pts), ternaries 2, loops 1 (nesting depth added 1). Most of this is not in the body itself: 7 of the 21 points are its own statements and the rest belongs to 9 function literals inside it that branch (lines 48, 33, 37, …). 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.
TasksView.AddTaskForm::handleSubmit (cognitive 21) dashboard/src/pages/TasksView.jsx:950— TasksView.AddTaskForm::handleSubmit has cognitive complexity 21 (threshold 15). Drivers by points: if/else 8 (14 pts), boolean chains 6, error handling 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.
policy-ledger.appendPolicyRecord (cognitive 20) dashboard/policy-ledger.js:38— policy-ledger.appendPolicyRecord has cognitive complexity 20 (threshold 15). Drivers by points: boolean chains 9, ternaries 5, error handling 2 (3 pts), if/else 3 (nesting depth added 1). 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.
hzl-service.workflowStart (cognitive 20) dashboard/hzl-service.js:903— hzl-service.workflowStart has cognitive complexity 20 (threshold 15). Drivers by points: boolean chains 7, if/else 6, ternaries 2 (4 pts), error handling 1 (2 pts), loops 1 (nesting depth added 3). Of this number, 11 points are the body's own statements and 9 belong to 4 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.
hzl-service.moveTaskToProject (cognitive 20) dashboard/hzl-service.js:2030— hzl-service.moveTaskToProject has cognitive complexity 20 (threshold 15). Drivers by points: if/else 6 (9 pts), boolean chains 5, error handling 3 (4 pts), loops 2 (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.
migrate-tasks.main (cognitive 20) dashboard/migrate-tasks.js:250— migrate-tasks.main has cognitive complexity 20 (threshold 15). Drivers by points: if/else 6 (7 pts), ternaries 3 (5 pts), error handling 2 (4 pts), boolean chains 2, loops 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.
project-bundle-export.walkContextFiles::walk (cognitive 20) dashboard/project-bundle-export.js:224— project-bundle-export.walkContextFiles::walk has cognitive complexity 20 (threshold 15). Drivers by points: if/else 8 (16 pts), boolean chains 2, error handling 1, loops 1 (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
ProjectBundleImporter._ensureProject (cognitive 20) dashboard/project-bundle-import.js:553— ProjectBundleImporter._ensureProject has cognitive complexity 20 (threshold 15). Drivers by points: if/else 7 (8 pts), boolean chains 6, ternaries 2 (5 pts), error handling 1 (nesting depth added 4). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
project-lifecycle.healProject (cognitive 20) dashboard/project-lifecycle.js:546— project-lifecycle.healProject has cognitive complexity 20 (threshold 15). Drivers by points: boolean chains 9, error handling 2 (4 pts), if/else 4, ternaries 2 (3 pts) (nesting depth added 3). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
specify-worker-bridge._step (cognitive 20) dashboard/specify-worker-bridge.js:183— specify-worker-bridge._step has cognitive complexity 20 (threshold 15). Drivers by points: if/else 10 (16 pts), boolean chains 3, error handling 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.
server.app.post("/api/specify/sessions") (cognitive 20) REDACTED:3952— server.app.post("/api/specify/sessions") has cognitive complexity 20 (threshold 15). Drivers by points: boolean chains 8, ternaries 5 (7 pts), if/else 4, error handling 1 (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.
TaskDisciplineControl.TaskDisciplineControl (cognitive 20) dashboard/src/components/TaskDisciplineControl.jsx:28— TaskDisciplineControl.TaskDisciplineControl has cognitive complexity 20 (threshold 15). Drivers by points: boolean chains 8, if/else 8, ternaries 3, error handling 1. Most of this is not in the body itself: 5 of the 20 points are its own statements and the rest belongs to 6 function items inside it that branch (changeDiscipline, a function literal at line 93, a function literal at line 37, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
(anonymous) (cognitive 20) REDACTED:2598— (anonymous) has cognitive complexity 20 (threshold 15). Drivers by points: boolean chains 9, if/else 7, ternaries 2 (3 pts), error handling 1 (nesting depth added 1). Of this number, 18 points are the body's own statements and 2 belong to 9 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.
directRefreshTasks (cognitive 20) dashboard/src/state/appStateBridge.mjs:59— directRefreshTasks has cognitive complexity 20 (threshold 15). Drivers by points: if/else 9 (13 pts), boolean chains 4, error handling 2 (3 pts) (nesting depth added 5). Most of this is not in the body itself: 3 of the 20 points are its own statements and the rest belongs to 4 function items inside it that branch (a function literal at line 67, a function literal at line 83, a function literal at line 71, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
hzl-service.buildCreationAudit (cognitive 19) dashboard/hzl-service.js:1203— hzl-service.buildCreationAudit has cognitive complexity 19 (threshold 15). Drivers by points: boolean chains 8, if/else 8, ternaries 3. 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.
hzl-service.claimTask (cognitive 19) dashboard/hzl-service.js:2318— hzl-service.claimTask has cognitive complexity 19 (threshold 15). Drivers by points: if/else 9 (10 pts), boolean chains 9 (nesting depth added 1). 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.
project-bundle-import-preview.parsePathTokens (cognitive 19) dashboard/project-bundle-import-preview.js:132— project-bundle-import-preview.parsePathTokens has cognitive complexity 19 (threshold 15). Drivers by points: if/else 7 (14 pts), boolean chains 3, loops 1, ternaries 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.
specify-worker-openclaw.createOpenClawCliAdapter.call (cognitive 19) dashboard/specify-worker-openclaw.js:167— specify-worker-openclaw.createOpenClawCliAdapter.call has cognitive complexity 19 (threshold 15). Drivers by points: boolean chains 7, if/else 5 (6 pts), ternaries 3 (5 pts), error handling 1 (nesting depth added 3). 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.
ActiveAgentsBar.ActiveAgentPill (cognitive 19) dashboard/src/components/ActiveAgentsBar.jsx:155— ActiveAgentsBar.ActiveAgentPill has cognitive complexity 19 (threshold 15). Drivers by points: boolean chains 9, ternaries 6, if/else 4. Of this number, 15 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.
canvasGeometry.manhattanPath (cognitive 19) dashboard/src/utils/canvasGeometry.mjs:203— canvasGeometry.manhattanPath has cognitive complexity 19 (threshold 15). Drivers by points: if/else 8 (13 pts), boolean chains 4, ternaries 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.
canvasGeometry.buildConnectedPorts (cognitive 19) dashboard/src/utils/canvasGeometry.mjs:404— canvasGeometry.buildConnectedPorts has cognitive complexity 19 (threshold 15). Drivers by points: if/else 7 (16 pts), boolean chains 2, loops 1 (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
TasksView.SubtaskCard (cognitive 19) dashboard/src/pages/TasksView.jsx:171— TasksView.SubtaskCard has cognitive complexity 19 (threshold 15). Drivers by points: boolean chains 9, if/else 6 (8 pts), error handling 1, ternaries 1 (nesting depth added 2). Most of this is not in the body itself: 9 of the 19 points are its own statements and the rest belongs to 2 function items inside it that branch (handleCreateSpec, handleClick). Those helpers are already separate functions, so extracting the branching again is not available. To reduce it, move them out of the body to the enclosing scope, where each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
validateTelegramInitData (cognitive 19) dashboard/telegram-auth.js:167— validateTelegramInitData has cognitive complexity 19 (threshold 15). Drivers by points: if/else 11, boolean chains 6, error handling 2. Of this number, 17 points are the body's own statements and 2 belong to 3 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.
createOpenClawCliAdapter.call (cognitive 19) dashboard/specify-worker-openclaw.js:167— createOpenClawCliAdapter.call has cognitive complexity 19 (threshold 15). Drivers by points: boolean chains 7, if/else 5 (6 pts), ternaries 3 (5 pts), error handling 1 (nesting depth added 3). 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.
parseQuery (cognitive 19) dashboard/smart-search.js:22— parseQuery has cognitive complexity 19 (threshold 15). Drivers by points: if/else 8 (12 pts), boolean chains 3, ternaries 1 (3 pts), loops 1 (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
flowboard-metadata.listProjects (cognitive 18) dashboard/flowboard-metadata.js:218— flowboard-metadata.listProjects has cognitive complexity 18 (threshold 15). Drivers by points: ternaries 11, boolean chains 7. Most of this is not in the body itself: 2 of the 18 points are its own statements and the rest belongs to 2 function literals inside it that branch (lines 242, 241). 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.
hzl-service.getTaskSummary (cognitive 18) dashboard/hzl-service.js:1820— hzl-service.getTaskSummary has cognitive complexity 18 (threshold 15). Drivers by points: if/else 11 (15 pts), loops 2, boolean chains 1 (nesting depth added 4). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
project-bundle-schema.normalizeRelativePath (cognitive 18) dashboard/project-bundle-schema.js:156— project-bundle-schema.normalizeRelativePath has cognitive complexity 18 (threshold 15). Drivers by points: if/else 10 (14 pts), boolean chains 3, loops 1 (nesting depth added 4). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
project-bundle-export.bundleValidationDiagnostics (cognitive 18) dashboard/project-bundle-export.js:338— project-bundle-export.bundleValidationDiagnostics has cognitive complexity 18 (threshold 15). Drivers by points: ternaries 12, boolean chains 5, if/else 1. Most of this is not in the body itself: 1 of the 18 points is its own statement and the rest belongs to one function literal inside it that branches (line 340). 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.
server.app.use("/api/") (cognitive 18) REDACTED:498— server.app.use("/api/") has cognitive complexity 18 (threshold 15). Drivers by points: if/else 4 (9 pts), boolean chains 3, error handling 1 (3 pts), ternaries 1 (3 pts) (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
DeleteProjectModal.DeleteProjectModal (cognitive 18) dashboard/src/components/DeleteProjectModal.jsx:9— DeleteProjectModal.DeleteProjectModal has cognitive complexity 18 (threshold 15). Drivers by points: boolean chains 6, if/else 5 (6 pts), ternaries 4 (5 pts), error handling 1 (nesting depth added 2). Of this number, 10 points are the body's own statements and 8 belong to 3 function items inside it that branch. To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition.
ProjectBundleModals.ImportPreviewSummary (cognitive 18) dashboard/src/components/ProjectBundleModals.jsx:446— ProjectBundleModals.ImportPreviewSummary has cognitive complexity 18 (threshold 15). Drivers by points: boolean chains 16, ternaries 2. 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.
DashboardConnectionState.DashboardConnectionState (cognitive 18) dashboard/src/components/DashboardConnectionState.jsx:47— DashboardConnectionState.DashboardConnectionState has cognitive complexity 18 (threshold 15). Drivers by points: boolean chains 8, ternaries 4 (8 pts), if/else 2 (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.
hasOneTopLevelAction (cognitive 18) dashboard/task-creation-policy.js:41— hasOneTopLevelAction has cognitive complexity 18 (threshold 15). Drivers by points: boolean chains 9, if/else 8 (9 pts) (nesting depth added 1). Of this number, 13 points are the body's own statements and 5 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.
(anonymous) (cognitive 18) REDACTED:498— (anonymous) has cognitive complexity 18 (threshold 15). Drivers by points: if/else 4 (9 pts), boolean chains 3, error handling 1 (3 pts), ternaries 1 (3 pts) (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
buildSourcePreview (cognitive 18) dashboard/project-bundle-import-preview.js:192— buildSourcePreview has cognitive complexity 18 (threshold 15). Drivers by points: if/else 5 (9 pts), loops 3 (4 pts), boolean chains 3, ternaries 1 (2 pts) (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
setSpecifyConfirmation (cognitive 18) dashboard/hzl-service.js:4312— setSpecifyConfirmation has cognitive complexity 18 (threshold 15). Drivers by points: boolean chains 7, if/else 3 (5 pts), other 4, loops 1, ternaries 1 (nesting depth added 2). 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.
normalizeStuckIndicatorActionDescriptor (cognitive 18) dashboard/src/utils/workState.js:159— normalizeStuckIndicatorActionDescriptor has cognitive complexity 18 (threshold 15). Drivers by points: boolean chains 10, if/else 5, ternaries 3. To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
rollbackOptimisticFields (cognitive 18) dashboard/src/state/taskState.mjs:114— rollbackOptimisticFields has cognitive complexity 18 (threshold 15). Drivers by points: if/else 7 (11 pts), boolean chains 4, ternaries 1 (2 pts), loops 1 (nesting depth added 5). Of this number, 17 points are the body's own statements and 1 belongs to one function literal inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
agent-identity.classifyAgentId (cognitive 17) dashboard/agent-identity.js:62— agent-identity.classifyAgentId has cognitive complexity 17 (threshold 15). Drivers by points: if/else 7, ternaries 4 (7 pts), boolean chains 3 (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.
hzl-service.createTaskWithPolicy (cognitive 17) dashboard/hzl-service.js:1107— hzl-service.createTaskWithPolicy has cognitive complexity 17 (threshold 15). Drivers by points: boolean chains 6, error handling 2 (4 pts), if/else 3 (4 pts), ternaries 3 (nesting depth added 3). Of this number, 16 points are the body's own statements and 1 belongs to one function item inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
hzl-service.getProjectStats (cognitive 17) dashboard/hzl-service.js:1865— hzl-service.getProjectStats has cognitive complexity 17 (threshold 15). Drivers by points: if/else 6 (12 pts), boolean chains 2, error handling 1, loops 1, ternaries 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.
hzl-service.getProjectActivityDaily (cognitive 17) dashboard/hzl-service.js:3003— hzl-service.getProjectActivityDaily has cognitive complexity 17 (threshold 15). Drivers by points: if/else 4 (7 pts), boolean chains 5, loops 3, ternaries 1 (2 pts) (nesting depth added 4). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
hzl-service.getHandoffContext (cognitive 17) dashboard/hzl-service.js:3904— hzl-service.getHandoffContext has cognitive complexity 17 (threshold 15). Drivers by points: error handling 4 (7 pts), if/else 6 (7 pts), ternaries 2, boolean chains 1 (nesting depth added 4). 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.
project-bundle-export.exportProjectReviewBundle (cognitive 17) dashboard/project-bundle-export.js:482— project-bundle-export.exportProjectReviewBundle has cognitive complexity 17 (threshold 15). Drivers by points: if/else 6 (7 pts), boolean chains 6, ternaries 3, loops 1 (nesting depth added 1). 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.
server.getTaskReminder (cognitive 17) REDACTED:1733— server.getTaskReminder has cognitive complexity 17 (threshold 15). Drivers by points: ternaries 4 (10 pts), if/else 4 (6 pts), boolean chains 1 (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
server.resolveProjectFile (cognitive 17) REDACTED:3334— server.resolveProjectFile has cognitive complexity 17 (threshold 15). Drivers by points: if/else 6 (8 pts), error handling 5 (7 pts), boolean chains 2 (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.
leaseHealth.getLeaseHealth (cognitive 17) dashboard/src/utils/leaseHealth.js:56— leaseHealth.getLeaseHealth has cognitive complexity 17 (threshold 15). Drivers by points: if/else 8 (11 pts), boolean chains 6 (nesting depth added 3). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
SnippetUpgrade.resolveChip (cognitive 17) dashboard/src/components/SnippetUpgrade.jsx:105— SnippetUpgrade.resolveChip has cognitive complexity 17 (threshold 15). Drivers by points: if/else 6 (7 pts), boolean chains 5, ternaries 2 (5 pts) (nesting depth added 4). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
SnippetUpgrade.UpgradeModal::handleApply (cognitive 17) dashboard/src/components/SnippetUpgrade.jsx:275— SnippetUpgrade.UpgradeModal::handleApply has cognitive complexity 17 (threshold 15). Drivers by points: boolean chains 9, error handling 2 (4 pts), if/else 4 (nesting depth added 2). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators. This shape REPEATS in the file: one other method here (SnippetUpgrade.UpgradeModal) has the same decision points, in the same order, at the same nesting depths — so this is one pattern written twice rather than two separate problems. Splitting this body alone leaves the other exactly as it is. Where these are variations on one operation, the change that clears both is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
SnippetUpgrade.AppUpdateSection (cognitive 17) dashboard/src/components/SnippetUpgrade.jsx:637— SnippetUpgrade.AppUpdateSection has cognitive complexity 17 (threshold 15). Drivers by points: boolean chains 8, if/else 8, ternaries 1. 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.
widgets2.TokenAffordance (cognitive 17) REDACTED:68— widgets2.TokenAffordance has cognitive complexity 17 (threshold 15). Drivers by points: if/else 7 (9 pts), boolean chains 4, ternaries 3 (4 pts) (nesting depth added 3). Most of this is not in the body itself: 6 of the 17 points are its own statements and the rest belongs to 4 function items inside it that branch (save, a function literal at line 109, a function literal at line 76, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
widgets2.TimelineWidget (cognitive 17) REDACTED:540— widgets2.TimelineWidget has cognitive complexity 17 (threshold 15). Drivers by points: boolean chains 7, ternaries 4 (6 pts), if/else 2 (3 pts), loops 1 (nesting depth added 3). Of this number, 11 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.
buildTelegramAuthConfig (cognitive 17) dashboard/telegram-auth.js:79— buildTelegramAuthConfig has cognitive complexity 17 (threshold 15). Drivers by points: if/else 8, boolean chains 5, ternaries 3 (4 pts) (nesting depth added 1). Of this number, 10 points are the body's own statements and 7 belong to 3 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.
recalcParentStatus (cognitive 17) dashboard/hzl-service.js:1981— recalcParentStatus has cognitive complexity 17 (threshold 15). Drivers by points: if/else 7 (8 pts), boolean chains 6, ternaries 1 (3 pts) (nesting depth added 3). Of this number, 14 points are the body's own statements and 3 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.
pollUntilUpdated (cognitive 17) dashboard/src/utils/appUpdate.mjs:78— pollUntilUpdated has cognitive complexity 17 (threshold 15). Drivers by points: if/else 3 (9 pts), error handling 2 (6 pts), boolean chains 1, loops 1 (nesting depth added 10). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
hzl-service._indicatorForEntry (cognitive 16) dashboard/hzl-service.js:3324— hzl-service._indicatorForEntry has cognitive complexity 16 (threshold 15). Drivers by points: boolean chains 9, ternaries 6 (7 pts) (nesting depth added 1). 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.
snippets-doctor.findSnippetRegion (cognitive 16) dashboard/snippets-doctor.js:506— snippets-doctor.findSnippetRegion has cognitive complexity 16 (threshold 15). Drivers by points: if/else 7 (10 pts), boolean chains 4, loops 2 (nesting depth added 3). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
project-bundle-import-preview.scanPathCollisions (cognitive 16) dashboard/project-bundle-import-preview.js:283— project-bundle-import-preview.scanPathCollisions has cognitive complexity 16 (threshold 15). Drivers by points: if/else 4 (7 pts), ternaries 2 (6 pts), error handling 1 (2 pts), loops 1 (nesting depth added 8). Most of this is not in the body itself: 3 of the 16 points are its own statements and the rest belongs to one function literal inside it that branches (line 287). 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.
project-bundle-import.taskGraphOrder (cognitive 16) dashboard/project-bundle-import.js:156— project-bundle-import.taskGraphOrder has cognitive complexity 16 (threshold 15). Drivers by points: if/else 3 (7 pts), loops 4 (6 pts), ternaries 1 (2 pts), boolean chains 1 (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
version-check.compareSemver (cognitive 16) dashboard/version-check.js:30— version-check.compareSemver has cognitive complexity 16 (threshold 15). Drivers by points: if/else 7 (8 pts), ternaries 3 (6 pts), boolean chains 1, loops 1 (nesting depth added 4). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
server.authenticateOrChallenge (cognitive 16) REDACTED:345— server.authenticateOrChallenge has cognitive complexity 16 (threshold 15). Drivers by points: if/else 6 (10 pts), boolean chains 4, error handling 1 (2 pts) (nesting depth added 5). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
server.cleanCanvasData (cognitive 16) REDACTED:1002— server.cleanCanvasData has cognitive complexity 16 (threshold 15). Drivers by points: if/else 4 (8 pts), boolean chains 6, loops 2 (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.
server.app.delete("/api/agents/:id") (cognitive 16) REDACTED:1342— server.app.delete("/api/agents/:id") has cognitive complexity 16 (threshold 15). Drivers by points: boolean chains 4, error handling 2 (4 pts), if/else 4, loops 1 (2 pts), ternaries 2 (nesting depth added 3). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
server.app.post("/api/projects") (cognitive 16) REDACTED:1758— server.app.post("/api/projects") has cognitive complexity 16 (threshold 15). Drivers by points: if/else 8 (12 pts), error handling 2, boolean chains 1, ternaries 1 (nesting depth added 4). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
activeAgents.buildActiveAgentRows (cognitive 16) dashboard/src/utils/activeAgents.js:73— activeAgents.buildActiveAgentRows has cognitive complexity 16 (threshold 15). Drivers by points: if/else 3 (5 pts), ternaries 3 (5 pts), boolean chains 4, loops 2 (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.
Sidebar.ProjectItem (cognitive 16) dashboard/src/components/Sidebar.jsx:91— Sidebar.ProjectItem has cognitive complexity 16 (threshold 15). Drivers by points: boolean chains 9, if/else 4 (5 pts), ternaries 2 (nesting depth added 1). Of this number, 8 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.
canvasMutations.sendPromote (cognitive 16) dashboard/src/state/canvasMutations.mjs:236— canvasMutations.sendPromote has cognitive complexity 16 (threshold 15). Drivers by points: if/else 6 (9 pts), boolean chains 6, error handling 1 (nesting depth added 3). Of this number, 13 points are the body's own statements and 3 belong to 3 function literals inside it that branch. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
parentActivity.getActiveSubtaskClaims (cognitive 16) dashboard/src/parentActivity.mjs:25— parentActivity.getActiveSubtaskClaims has cognitive complexity 16 (threshold 15). Drivers by points: if/else 5 (9 pts), boolean chains 6, loops 1 (nesting depth added 4). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
TasksView.AddSubtaskForm (cognitive 16) dashboard/src/pages/TasksView.jsx:706— TasksView.AddSubtaskForm has cognitive complexity 16 (threshold 15). Drivers by points: if/else 8 (10 pts), boolean chains 5, error handling 1 (nesting depth added 2). Most of this is not in the body itself: 1 of the 16 points is its own statement and the rest belongs to 2 function items inside it that branch (handleSubmit, handleKeyDown). Those helpers are already separate functions, so extracting the branching again is not available. To reduce it, move them out of the body to the enclosing scope, where each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
FilesView.tokenizeJson (cognitive 16) dashboard/src/pages/FilesView.jsx:406— FilesView.tokenizeJson has cognitive complexity 16 (threshold 15). Drivers by points: if/else 8 (12 pts), ternaries 1 (3 pts), loops 1 (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
canvasTextFormat.insertLinePrefix (cognitive 16) dashboard/src/utils/canvasTextFormat.mjs:131— canvasTextFormat.insertLinePrefix has cognitive complexity 16 (threshold 15). Drivers by points: ternaries 5 (10 pts), if/else 5 (6 pts) (nesting depth added 6). Of this number, 13 points are the body's own statements and 3 belong to one function literal inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
systemd-config.expandSupportedSystemdSpecifiers (cognitive 16) scripts/systemd-config.mjs:198— systemd-config.expandSupportedSystemdSpecifiers has cognitive complexity 16 (threshold 15). Drivers by points: if/else 5 (7 pts), ternaries 3 (6 pts), boolean chains 2, loops 1 (nesting depth added 5). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
systemd-config.applySystemdEvents (cognitive 16) scripts/systemd-config.mjs:318— systemd-config.applySystemdEvents has cognitive complexity 16 (threshold 15). Drivers by points: if/else 6 (12 pts), loops 2 (4 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.
setup.parseOverrideEnvKeys (cognitive 16) scripts/setup.mjs:157— setup.parseOverrideEnvKeys has cognitive complexity 16 (threshold 15). Drivers by points: if/else 7 (13 pts), loops 2, 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.
setup.applySystemdEventsWithSources (cognitive 16) scripts/setup.mjs:361— setup.applySystemdEventsWithSources has cognitive complexity 16 (threshold 15). Drivers by points: if/else 6 (12 pts), loops 2 (4 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.
setup.ensureOwnerOnlyRegularFile (cognitive 16) scripts/setup.mjs:643— setup.ensureOwnerOnlyRegularFile has cognitive complexity 16 (threshold 15). Drivers by points: if/else 9 (10 pts), boolean chains 4, error handling 2 (nesting depth added 1). 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.
validateFileInventory (cognitive 16) dashboard/project-bundle-validator.js:615— validateFileInventory has cognitive complexity 16 (threshold 15). Drivers by points: if/else 4 (6 pts), error handling 2 (4 pts), boolean chains 3, loops 3 (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.
D2 · Cognitive Complexity· run (cognitive 16) · ×1
run (cognitive 16) dashboard/migrations.js:101— run has cognitive complexity 16 (threshold 15). Drivers by points: if/else 8 (10 pts), error handling 2 (3 pts), boolean chains 2, ternaries 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.
No structured logging — No logging call was found in the 338 JavaScript/TypeScript production file(s) this check read across 2 module(s). Each was searched for its ecosystem's logging libraries (JavaScript/TypeScript: pino, winston, bunyan, log4js, loglevel, consola, the NestJS Logger) and for a call on a receiver named `log`/`logger` (or ending in `Logger`/`_logger`) with a level verb. It cannot see logging through a repo-local wrapper named otherwise, or in source it did not read — this is 'no logging found by this walk', not a verdict that nothing here logs. If it is right, production issues will be hard to diagnose.
Duplication concentrated across 5 sibling directories (13 clone groups) dashboard/src/components/Sidebar.jsx:491— 13 duplicated blocks under dashboard/src/ have copies in at least two of the sibling directories components, context, pages, state, utils — 8 of them are reported below, and 5 are counted here but not reported individually: those copies match on shape but no longer clear R10's bar for an individually reported row — either they kept neither their own names nor their values, or what was copied is too small to stand on its own (it reports near-exact duplication only, and only of substantial extent). What this row states is the concentration, which the detector measured over all 13 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 13 local ones: the siblings replicate behaviour none of them owns, which is the shape of a missing shared module — a common library every sibling imports — rather than 13 separate extractions. Check first whether the siblings are deliberately standalone deliverables (scaffold templates, demo apps that must stay copy-pasteable); where they are, the duplication is the design and the per-block rows are the ones to act on.
R10 · Code Duplication· Duplicated block with local edits (119 matched lines × 2 locations) · ×1
Duplicated block with local edits (119 matched lines × 2 locations) REDACTED:15— REDACTED:15 · REDACTED:18 — the two spans are one implementation copied and then locally edited — 924 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one.
R10 · Code Duplication· Duplicated block with local edits (107 matched lines × 2 locations) · ×1
Duplicated block with local edits (107 matched lines × 2 locations) dashboard/test-canvas-dblclick.js:31— dashboard/test-canvas-dblclick.js:31 · dashboard/test-canvas-links.js:38 — the two spans are one implementation copied and then locally edited — 982 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one.
R10 · Code Duplication· Duplicated block with local edits (103 matched lines × 2 locations) · ×1
Duplicated block with local edits (103 matched lines × 2 locations) dashboard/test-canvas-dblclick.js:221— dashboard/test-canvas-dblclick.js:221 · dashboard/test-canvas-links.js:221 — the two spans are one implementation copied and then locally edited — 904 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one.
R10 · Code Duplication· Duplicated block with local edits (98 matched lines × 2 locations) · ×1
Duplicated block with local edits (98 matched lines × 2 locations) dashboard/test-canvas-db-drift.js:32— dashboard/test-canvas-db-drift.js:32 · dashboard/test-canvas-db-import.js:23 — the two spans are one implementation copied and then locally edited — 925 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 (92 lines × 2 locations) dashboard/test-specify-e2e-complex.js:10— dashboard/test-specify-e2e-complex.js:10 · dashboard/test-specify-e2e-simple.js:10 — the 2 copies sit in sibling files in one directory, so check first whether one of them (or an existing module there) already owns this behaviour and the others should call it; otherwise extract it into one module in that directory and have each site call it.
R10 · Code Duplication· Duplicated block with local edits (89 matched lines × 2 locations) · ×1
Duplicated block with local edits (89 matched lines × 2 locations) dashboard/test-specify-api-confirm.js:41— dashboard/test-specify-api-confirm.js:41 · dashboard/test-specify-failure-scenarios.js:39 — the two spans are one implementation copied and then locally edited — 652 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one.
R10 · Code Duplication· Duplicated block with local edits (82 matched lines × 2 locations) · ×1
Duplicated block with local edits (82 matched lines × 2 locations) scripts/capture-v5-gif.mjs:15— scripts/capture-v5-gif.mjs:15 · scripts/capture-v5-screenshots.mjs:7 — the two spans are one implementation copied and then locally edited — 903 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one.
R10 · Code Duplication· Duplicated block with local edits (70 matched lines × 2 locations) · ×1
Duplicated block with local edits (70 matched lines × 2 locations) dashboard/test-canvas-promote-integration.js:104— dashboard/test-canvas-promote-integration.js:104 · dashboard/test-canvas-promote-stepper-visible.js:59 — the two spans are one implementation copied and then locally edited — 567 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one.
R10 · Code Duplication· Duplicated block with local edits (61 matched lines × 2 locations) · ×1
Duplicated block with local edits (61 matched lines × 2 locations) dashboard/test-setup-linux-systemd.mjs:493— dashboard/test-setup-linux-systemd.mjs:493 · dashboard/test-setup-linux-systemd.mjs:574 — the two spans are one implementation copied and then locally edited — 470 tokens are still identical, in the same order in both spans, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one.
Duplicated block (55 lines × 2 locations) dashboard/test-search-api.js:10— dashboard/test-search-api.js:10 · dashboard/test-task-move-reparent.js:10 — the 2 copies sit in sibling files in one directory, so check first whether one of them (or an existing module there) already owns this behaviour and the others should call it; otherwise extract it into one module in that directory and have each site call it.
R10 · Code Duplication· Duplicated block with local edits (49 matched lines × 2 locations) · ×1
Duplicated block with local edits (49 matched lines × 2 locations) dashboard/test-handoff-package.js:74— dashboard/test-handoff-package.js:74 · dashboard/test-handoff-package.js:184 — the two spans are one implementation copied and then locally edited — 263 tokens are still identical, in the same order in both spans, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one.
Duplicated block (46 lines × 2 locations) dashboard/test-canvas-promote-integration.js:12— dashboard/test-canvas-promote-integration.js:12 · dashboard/test-canvas-promote-stepper-visible.js:12 — the 2 copies sit in sibling files in one directory, so check first whether one of them (or an existing module there) already owns this behaviour and the others should call it; otherwise extract it into one module in that directory and have each site call it.
Duplicated block (45 lines × 2 locations) dashboard/test-canvas-create-task-smoke.js:16— dashboard/test-canvas-create-task-smoke.js:16 · dashboard/test-canvas-db-endpoints.js:23 — the 2 copies sit in sibling files in one directory, so check first whether one of them (or an existing module there) already owns this behaviour and the others should call it; otherwise extract it into one module in that directory and have each site call it.
Duplicated block (43 lines × 3 locations) dashboard/test-agent-delete-guard.js:19— dashboard/test-agent-delete-guard.js:19 · dashboard/test-destructive-confirmation.js:17 · dashboard/test-task-archive-errors.js:16 — the 3 copies sit in sibling files in one directory, so check first whether one of them (or an existing module there) already owns this behaviour and the others should call it; otherwise extract it into one module in that directory and have each site call it. There is one copy in each of 3 separate files rather than several in one place, so check first whether these are sibling modules that each declare their own version of one shape — one per entity, per provider, per language. Where they are, no single extracted module collapses them: each module still has to be written, and what recurs is the TEMPLATE. The moves that do collapse a template are to generate these modules from the set they enumerate, or to replace the repeated construction with one factory each site calls with its own values — and where the set is the point, each module pinning one distinct thing, the repetition IS the enumeration and there is nothing to delete.
R10 · Code Duplication· Duplicated block with local edits (42 matched lines × 2 locations) · ×1
Duplicated block with local edits (42 matched lines × 2 locations) dashboard/github.js:52— dashboard/github.js:52 · dashboard/github.js:121 — the two spans are one implementation copied and then locally edited — 366 tokens are still identical, in the same order in both spans, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one.
Duplicated block (41 lines × 2 locations) REDACTED:4089— REDACTED:4089 · REDACTED:4238 — 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 (40 matched lines × 2 locations) · ×1
Duplicated block with local edits (40 matched lines × 2 locations) REDACTED:23— REDACTED:23 · REDACTED:24 — the two spans are one implementation copied and then locally edited — 283 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 (38 lines × 3 locations) dashboard/test-canvas-browser-smoke.js:81— dashboard/test-canvas-browser-smoke.js:81 · dashboard/test-canvas-dblclick.js:289 · dashboard/test-canvas-links.js:338 — the 3 copies are spread across 3 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
R10 · Code Duplication· Duplicated block with local edits (37 matched lines × 2 locations) · ×1
Duplicated block with local edits (37 matched lines × 2 locations) dashboard/test-dashboard-api.mjs:39— dashboard/test-dashboard-api.mjs:39 · dashboard/test-dashboard-race-regressions-e2e.js:30 — the two spans are one implementation copied and then locally edited — 149 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one.
R10 · Code Duplication· Duplicated block with local edits (36 matched lines × 2 locations) · ×1
Duplicated block with local edits (36 matched lines × 2 locations) REDACTED:1171— REDACTED:1171 · REDACTED:29 — the two spans are one implementation copied and then locally edited — 348 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one.
R10 · Code Duplication· Duplicated block with local edits (35 matched lines × 2 locations) · ×1
Duplicated block with local edits (35 matched lines × 2 locations) dashboard/test-snippets-doctor.js:203— dashboard/test-snippets-doctor.js:203 · dashboard/test-snippets-doctor.js:828 — the two spans are one implementation copied and then locally edited — 268 tokens are still identical, in the same order in both spans, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one.
Duplicated block (31 lines × 3 locations) dashboard/test-specify-e2e-chat-origin.js:27— dashboard/test-specify-e2e-chat-origin.js:27 · dashboard/test-specify-e2e-complex.js:32 · dashboard/test-specify-e2e-simple.js:32 — the 3 copies sit in sibling files in one directory, so check first whether one of them (or an existing module there) already owns this behaviour and the others should call it; otherwise extract it into one module in that directory and have each site call it. There is one copy in each of 3 separate files rather than several in one place, so check first whether these are sibling modules that each declare their own version of one shape — one per entity, per provider, per language. Where they are, no single extracted module collapses them: each module still has to be written, and what recurs is the TEMPLATE. The moves that do collapse a template are to generate these modules from the set they enumerate, or to replace the repeated construction with one factory each site calls with its own values — and where the set is the point, each module pinning one distinct thing, the repetition IS the enumeration and there is nothing to delete.
R10 · Code Duplication· Duplicated block with local edits (29 matched lines × 2 locations) · ×1
Duplicated block with local edits (29 matched lines × 2 locations) dashboard/test-work-state-e2e.js:109— dashboard/test-work-state-e2e.js:109 · dashboard/test-work-state-poll-race-e2e.js:114 — the two spans are one implementation copied and then locally edited — 242 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 (28 lines × 2 locations) REDACTED:2120— REDACTED:2120 · REDACTED:2227 — 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 (28 matched lines × 2 locations) · ×1
Duplicated block with local edits (28 matched lines × 2 locations) dashboard/test-file-endpoints-security.js:27— dashboard/test-file-endpoints-security.js:27 · dashboard/test-project-delete-guard.js:32 — the two spans are one implementation copied and then locally edited — 303 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 (26 lines × 3 locations) dashboard/test-specify-clarify-regression.js:92— dashboard/test-specify-clarify-regression.js:92 · dashboard/test-specify-e2e-complex.js:80 · dashboard/test-specify-e2e-simple.js:80 — 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.
Boundary violation [package:relative-cross-package] dashboard/test-project-context-retry.mjs:7— dashboard/test-project-context-retry.mjs:7 reaches into another package with a relative path (../hooks/project-context/handler.js) — import the package by name instead.
Complex function (anonymous) (cyclomatic 93, cognitive 131) REDACTED:2875— (anonymous) has cyclomatic complexity 93 and cognitive complexity 131; 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 UpgradeModal (cyclomatic 93, cognitive 85) dashboard/src/components/SnippetUpgrade.jsx:152— UpgradeModal has cyclomatic complexity 93 and cognitive complexity 85; 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 updateTask (cyclomatic 82, cognitive 121) dashboard/hzl-service.js:1431— updateTask has cyclomatic complexity 82 and cognitive complexity 121; 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 76, cognitive 107) REDACTED:2702— (anonymous) has cyclomatic complexity 76 and cognitive complexity 107; 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 DetailPanel (cyclomatic 75, cognitive 62) dashboard/src/components/DetailPanel.jsx:182— DetailPanel has cyclomatic complexity 75 and cognitive complexity 62; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
R2 · Cyclomatic Complexity· Complex function run (cyclomatic 69, cognitive 55) · ×1
Complex function run (cyclomatic 69, cognitive 55) dashboard/test-canvas-db-import.js:92— run has cyclomatic complexity 69 and cognitive complexity 55; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
R2 · Cyclomatic Complexity· Complex function run (cyclomatic 64, cognitive 50) · ×1
Complex function run (cyclomatic 64, cognitive 50) dashboard/test-overview-api.js:30— run has cyclomatic complexity 64 and cognitive complexity 50; 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 SpecifyStepper (cyclomatic 63, cognitive 59) dashboard/src/components/SpecifyStepper.jsx:40— SpecifyStepper has cyclomatic complexity 63 and cognitive complexity 59; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
R2 · Cyclomatic Complexity· Complex function run (cyclomatic 60, cognitive 48) · ×1
Complex function run (cyclomatic 60, cognitive 48) dashboard/test-canvas-db-store.js:62— run has cyclomatic complexity 60 and cognitive complexity 48; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
R2 · Cyclomatic Complexity· Complex function run (cyclomatic 58, cognitive 61) · ×1
Complex function run (cyclomatic 58, cognitive 61) dashboard/test-dashboard-shell.js:46— run has cyclomatic complexity 58 and cognitive complexity 61; 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 routePath (cyclomatic 49, cognitive 144) dashboard/src/utils/canvasGeometry.mjs:48— routePath has cyclomatic complexity 49 and cognitive complexity 144; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
R2 · Cyclomatic Complexity· Complex function main (cyclomatic 47, cognitive 48) · ×1
Complex function main (cyclomatic 47, cognitive 48) dashboard/test-work-state-api.js:12— main has cyclomatic complexity 47 and cognitive complexity 48; 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 parseSystemdEnvironmentFile (cyclomatic 46, cognitive 78) scripts/systemd-config.mjs:349— parseSystemdEnvironmentFile has cyclomatic complexity 46 and cognitive complexity 78; 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 createTaskRaw (cyclomatic 45, cognitive 50) dashboard/hzl-service.js:1248— createTaskRaw has cyclomatic complexity 45 and cognitive complexity 50; 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 44, cognitive 39) dashboard/test-dashboard-race-regressions-e2e.js:149— (anonymous) has cyclomatic complexity 44 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 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 exerciseEndpoints (cyclomatic 42, cognitive 32) dashboard/test-canvas-db-endpoints.js:90— exerciseEndpoints has cyclomatic complexity 42 and cognitive complexity 32; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function runTests (cyclomatic 40, cognitive 39) dashboard/test-specify-clarify-regression.js:95— runTests has cyclomatic complexity 40 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 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 evaluateCreationPolicy (cyclomatic 38, cognitive 48) dashboard/task-creation-policy.js:107— evaluateCreationPolicy has cyclomatic complexity 38 and cognitive complexity 48; 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 MilestonesWidget (cyclomatic 38, cognitive 45) REDACTED:262— MilestonesWidget has cyclomatic complexity 38 and cognitive complexity 45; 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 _canonicalAdmission (cyclomatic 38, cognitive 36) dashboard/project-bundle-import.js:367— _canonicalAdmission has cyclomatic complexity 38 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 sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
REDACTED: 4965 lines of code REDACTED:1— REDACTED has 4965 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
dashboard/hzl-service.js: 4518 lines of code dashboard/hzl-service.js:1— dashboard/hzl-service.js has 4518 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files· dashboard/src/pages/TasksView.jsx · ×1
dashboard/src/pages/TasksView.jsx: 1874 lines of code dashboard/src/pages/TasksView.jsx:1— dashboard/src/pages/TasksView.jsx has 1874 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files· dashboard/src/components/DetailPanel.jsx · ×1
dashboard/src/components/DetailPanel.jsx: 1628 lines of code dashboard/src/components/DetailPanel.jsx:1— dashboard/src/components/DetailPanel.jsx has 1628 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
REDACTED: 1329 lines of code REDACTED:1— REDACTED has 1329 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
REDACTED: 1310 lines of code REDACTED:1— REDACTED has 1310 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files· dashboard/src/pages/FilesView.jsx · ×1
dashboard/src/pages/FilesView.jsx: 1137 lines of code dashboard/src/pages/FilesView.jsx:1— dashboard/src/pages/FilesView.jsx has 1137 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files· dashboard/src/components/Sidebar.jsx · ×1
dashboard/src/components/Sidebar.jsx: 977 lines of code dashboard/src/components/Sidebar.jsx:1— dashboard/src/components/Sidebar.jsx has 977 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files· dashboard/test-setup-linux-systemd.mjs · ×1
dashboard/test-setup-linux-systemd.mjs: 954 lines of code dashboard/test-setup-linux-systemd.mjs:1— dashboard/test-setup-linux-systemd.mjs has 954 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files· dashboard/project-bundle-import.js · ×1
dashboard/project-bundle-import.js: 943 lines of code dashboard/project-bundle-import.js:1— dashboard/project-bundle-import.js has 943 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files· dashboard/src/components/SnippetUpgrade.jsx · ×1
dashboard/src/components/SnippetUpgrade.jsx: 909 lines of code dashboard/src/components/SnippetUpgrade.jsx:1— dashboard/src/components/SnippetUpgrade.jsx has 909 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files· dashboard/snippets-doctor.js · ×1
dashboard/snippets-doctor.js: 887 lines of code dashboard/snippets-doctor.js:1— dashboard/snippets-doctor.js has 887 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files· dashboard/test-snippets-doctor.js · ×1
dashboard/test-snippets-doctor.js: 846 lines of code dashboard/test-snippets-doctor.js:1— dashboard/test-snippets-doctor.js has 846 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files· dashboard/test-t168-t177-integration.js · ×1
dashboard/test-t168-t177-integration.js: 773 lines of code dashboard/test-t168-t177-integration.js:1— dashboard/test-t168-t177-integration.js has 773 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
REDACTED: 767 lines of code REDACTED:1— REDACTED has 767 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files· dashboard/src/components/ProjectBundleModals.jsx · ×1
dashboard/src/components/ProjectBundleModals.jsx: 756 lines of code dashboard/src/components/ProjectBundleModals.jsx:1— dashboard/src/components/ProjectBundleModals.jsx has 756 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files· dashboard/src/context/DashboardContext.jsx · ×1
dashboard/src/context/DashboardContext.jsx: 690 lines of code dashboard/src/context/DashboardContext.jsx:1— dashboard/src/context/DashboardContext.jsx has 690 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files· dashboard/project-bundle-validator.js · ×1
dashboard/project-bundle-validator.js: 628 lines of code dashboard/project-bundle-validator.js:1— dashboard/project-bundle-validator.js has 628 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files· dashboard/test-dashboard-shell.js · ×1
dashboard/test-dashboard-shell.js: 628 lines of code dashboard/test-dashboard-shell.js:1— dashboard/test-dashboard-shell.js has 628 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files· dashboard/flowboard-metadata.js · ×1
dashboard/flowboard-metadata.js: 620 lines of code dashboard/flowboard-metadata.js:1— dashboard/flowboard-metadata.js has 620 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
dashboard/overview.js: 603 lines of code dashboard/overview.js:1— dashboard/overview.js has 603 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files· dashboard/project-lifecycle.js · ×1
dashboard/project-lifecycle.js: 602 lines of code dashboard/project-lifecycle.js:1— dashboard/project-lifecycle.js has 602 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files· dashboard/src/utils/canvasGeometry.mjs · ×1
dashboard/src/utils/canvasGeometry.mjs: 586 lines of code dashboard/src/utils/canvasGeometry.mjs:1— dashboard/src/utils/canvasGeometry.mjs has 586 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files· dashboard/src/components/ActiveAgentsBar.jsx · ×1
dashboard/src/components/ActiveAgentsBar.jsx: 583 lines of code dashboard/src/components/ActiveAgentsBar.jsx:1— dashboard/src/components/ActiveAgentsBar.jsx has 583 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files· dashboard/project-bundle-export.js · ×1
dashboard/project-bundle-export.js: 545 lines of code dashboard/project-bundle-export.js:1— dashboard/project-bundle-export.js has 545 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files· dashboard/src/pages/OverviewView.jsx · ×1
dashboard/src/pages/OverviewView.jsx: 521 lines of code dashboard/src/pages/OverviewView.jsx:1— dashboard/src/pages/OverviewView.jsx has 521 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files· dashboard/src/components/SpecifyStepper.jsx · ×1
dashboard/src/components/SpecifyStepper.jsx: 512 lines of code dashboard/src/components/SpecifyStepper.jsx:1— dashboard/src/components/SpecifyStepper.jsx has 512 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files· dashboard/test-hzl-integration.js · ×1
dashboard/test-hzl-integration.js: 506 lines of code dashboard/test-hzl-integration.js:1— dashboard/test-hzl-integration.js has 506 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files· dashboard/project-bundle-schema.js · ×1
dashboard/project-bundle-schema.js: 494 lines of code dashboard/project-bundle-schema.js:1— dashboard/project-bundle-schema.js has 494 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files· dashboard/test-work-state-e2e.js · ×1
dashboard/test-work-state-e2e.js: 494 lines of code dashboard/test-work-state-e2e.js:1— dashboard/test-work-state-e2e.js has 494 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files· dashboard/test-snippets-integration.js · ×1
dashboard/test-snippets-integration.js: 479 lines of code dashboard/test-snippets-integration.js:1— dashboard/test-snippets-integration.js has 479 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files· dashboard/test-setup-macos-launchd.mjs · ×1
dashboard/test-setup-macos-launchd.mjs: 475 lines of code dashboard/test-setup-macos-launchd.mjs:1— dashboard/test-setup-macos-launchd.mjs has 475 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files· dashboard/project-bundle-import-preview.js · ×1
dashboard/project-bundle-import-preview.js: 461 lines of code dashboard/project-bundle-import-preview.js:1— dashboard/project-bundle-import-preview.js has 461 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files· dashboard/test-dashboard-api.mjs · ×1
dashboard/test-dashboard-api.mjs: 460 lines of code dashboard/test-dashboard-api.mjs:1— dashboard/test-dashboard-api.mjs has 460 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files· dashboard/test-work-state-backend.js · ×1
dashboard/test-work-state-backend.js: 443 lines of code dashboard/test-work-state-backend.js:1— dashboard/test-work-state-backend.js has 443 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
REDACTED: 433 lines of code REDACTED:1— REDACTED has 433 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
REDACTED: 421 lines of code REDACTED:1— REDACTED has 421 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
dashboard/migrations.js: 420 lines of code dashboard/migrations.js:1— dashboard/migrations.js has 420 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
No lint or typecheck script — test ✓ · lint ✗ · typecheck ✗ — read from this repository's package.json scripts and corroborated against its CI workflows. A script counts when its name or command matches the step: `test` for the suite, `lint` or `prettier` for linting, `typecheck`/`type-check`/`tsc` for type checking. ✗ therefore means no script or CI step under those names was found, NOT that the step is absent from your pipeline — a task invoked by a runner this check does not read, or named something else entirely, is not seen and is worth confirming before acting on a cross. A ✓ means the wiring is DECLARED — a script or CI step under those names exists. It is not a statement that the step passes, or that it runs at all: nothing here installs a dependency or executes a suite.
Dead file (~71 LoC) dashboard/tools/ov-resize-probe.mjs— no import path from any entry point (234 application, 19 tooling, 10 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 (~14 LoC) openclaw/flowboard-plugin.js— no import path from any entry point (234 application, 19 tooling, 10 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
Third-party script without Subresource Integrity dashboard/index.html:24— `https://telegram.org/js/telegram-web-app.js` is executed by this page with no Subresource Integrity. Whoever can answer that request — the CDN, anyone who compromises it, anyone on the network path — runs arbitrary script in this page's origin, with its session. The URL also names no version, so it resolves to whatever that origin serves at fetch time — the executed bytes can change with nobody touching this repository.
README/code drift README.md:198— README.md changes into `FlowBoard/dashboard`, but no such folder exists. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
README/code drift README.md:423— README.md names `CONVENTIONS.md`, but no file or folder `CONVENTIONS.md` exists. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
README/code drift docs/concepts/README.md:38— docs/concepts/README.md names `SESSIONS.md`, but no file or folder `SESSIONS.md` exists. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
README/code drift docs/concepts/README.md:109— docs/concepts/README.md names `context/specify-prompt.md`, but no file or folder `context/specify-prompt.md` exists. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
README/code drift docs/concepts/idea-canvas.md:107— docs/concepts/idea-canvas.md names `context/specify-prompt.md`, but no file or folder `context/specify-prompt.md` exists. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
README/code drift docs/concepts/multi-agent-model.md:46— docs/concepts/multi-agent-model.md names `ACTIVE-PROJECT.md`, but no file or folder `ACTIVE-PROJECT.md` exists. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
README/code drift docs/concepts/project-file-structure.md:5— docs/concepts/project-file-structure.md names `SESSIONS.md`, but no file or folder `SESSIONS.md` exists. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
README/code drift docs/concepts/project-file-structure.md:17— docs/concepts/project-file-structure.md names `ACTIVE-PROJECT.md`, but no file or folder `ACTIVE-PROJECT.md` exists. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
README/code drift docs/concepts/snippet-doctor.md:5— docs/concepts/snippet-doctor.md names `BOOT.md`, but no file or folder `BOOT.md` exists. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
README/code drift docs/concepts/specify-workflow.md:21— docs/concepts/specify-workflow.md names `context/specify-prompt.md`, but no file or folder `context/specify-prompt.md` exists. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
README/code drift docs/concepts/specify-workflow.md:157— docs/concepts/specify-workflow.md names `context/specify-spec-template.md`, but no file or folder `context/specify-spec-template.md` exists. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
README/code drift docs/project-mode/agent-bridge.md:66— docs/project-mode/agent-bridge.md names `SESSIONS.md`, but no file or folder `SESSIONS.md` exists. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
README/code drift docs/project-mode/compliance.md:65— docs/project-mode/compliance.md names `BOOTSTRAP.md`, but no file or folder `BOOTSTRAP.md` exists. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
README/code drift docs/project-mode/error-handling.md:13— docs/project-mode/error-handling.md names `ACTIVE-PROJECT.md`, but no file or folder `ACTIVE-PROJECT.md` exists. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
README/code drift docs/project-mode/error-handling.md:13— docs/project-mode/error-handling.md names `_index.md`, but no file or folder `_index.md` exists. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
README/code drift docs/project-mode/hzl.md:70— docs/project-mode/hzl.md names `SESSIONS.md`, but no file or folder `SESSIONS.md` exists. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
README/code drift docs/project-mode/hzl.md:73— docs/project-mode/hzl.md names `.pre-db.bak`, but no file or folder `.pre-db.bak` exists. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
README/code drift docs/project-mode/hzl.md:79— docs/project-mode/hzl.md names `_index.md`, but no file or folder `_index.md` exists. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
README/code drift docs/project-mode/hzl.md:79— docs/project-mode/hzl.md names `ACTIVE-PROJECT.md`, but no file or folder `ACTIVE-PROJECT.md` exists. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
README/code drift docs/project-mode/key-principles.md:20— docs/project-mode/key-principles.md names `ACTIVE-PROJECT.md`, but no file or folder `ACTIVE-PROJECT.md` exists. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
README/code drift docs/project-mode/key-principles.md:20— docs/project-mode/key-principles.md names `_index.md`, but no file or folder `_index.md` exists. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
README/code drift docs/project-mode/key-principles.md:20— docs/project-mode/key-principles.md names `SESSION-STATE.md`, but no file or folder `SESSION-STATE.md` exists. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
README/code drift docs/project-mode/key-principles.md:46— docs/project-mode/key-principles.md names `SESSIONS.md`, but no file or folder `SESSIONS.md` exists. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
README/code drift docs/project-mode/project-files.md:12— docs/project-mode/project-files.md names `SESSIONS.md`, but no file or folder `SESSIONS.md` exists. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
README/code drift docs/project-mode/project-files.md:14— docs/project-mode/project-files.md names `.pre-db.bak`, but no file or folder `.pre-db.bak` exists. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
Duplicated predicate dashboard/test-work-state-e2e.js:231— `!!rect && rect.width > 0 && rect.right <= window.innerWidth + 1` appears character-identically in 2 files — dashboard/test-work-state-e2e.js, dashboard/test-work-state-poll-race-e2e.js. 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 dashboard/src/utils/dashboardApi.js:16— `!!value && typeof value === 'object' && !Array.isArray(value)` appears character-identically in 2 files — dashboard/src/utils/dashboardApi.js, dashboard/src/utils/workState.js. 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 dashboard/hzl-service.js:4805— `!data || !Array.isArray(data.notes) || !Array.isArray(data.connections)` appears character-identically in 2 files — dashboard/hzl-service.js, REDACTED. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate dashboard/hzl-service.js:4689— `!noteIds || !Array.isArray(noteIds) || noteIds.length === 0` appears character-identically in 2 files — dashboard/hzl-service.js, REDACTED. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate dashboard/hzl-service.js:4840— `!noteIds.has(c.from) || !noteIds.has(c.to)` appears character-identically in 2 files — dashboard/hzl-service.js, REDACTED. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate scripts/clawpack-gate.mjs:46— `!npmPrefix.error && npmPrefix.status === 0 && npmPrefix.stdout.trim()` appears character-identically in 2 files — scripts/clawpack-gate.mjs, scripts/release-install-canary.mjs. 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 dashboard/src/components/ProjectBundleModals.jsx:596— `!parsed || typeof parsed !== 'object' || Array.isArray(parsed)` appears character-identically in 2 files — dashboard/src/components/ProjectBundleModals.jsx, scripts/setup.mjs. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate scripts/clawpack-gate.mjs:38— `!pathProbe.error && pathProbe.status === 0` appears character-identically in 2 files — scripts/clawpack-gate.mjs, scripts/release-install-canary.mjs. 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 dashboard/governance.js:99— `!proposal || typeof proposal !== 'object'` appears character-identically in 2 files — dashboard/governance.js, dashboard/specify-policy.js. 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 dashboard/hzl-service.js:1874— `(t.status === 'done' || t.status === 'archived') && t.completed` appears character-identically in 2 files — dashboard/hzl-service.js, REDACTED. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate dashboard/test-canvas-db-drift.js:167— `Array.isArray(res.body?.pending) && Array.isArray(res.body?.migrated) && typeof res.body?.total === 'number'` appears character-identically in 2 files — dashboard/test-canvas-db-drift.js, dashboard/test-canvas-db-import.js. 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 dashboard/src/components/canvas/ConnectionLayer.jsx:95— `COLOR_STROKE[fromNote?.color] || 'var(--border-strong)'` appears character-identically in 2 files — dashboard/src/components/canvas/ConnectionLayer.jsx, dashboard/src/utils/canvasGeometry.mjs. 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 dashboard/hzl-service.js:1445— `Object.prototype.hasOwnProperty.call(updates, 'workState') || Object.prototype.hasOwnProperty.call(updates, 'workStateDetails')` appears character-identically in 2 files — dashboard/hzl-service.js, REDACTED. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate dashboard/test-content-hygiene-api.js:65— `created.status === 200 && created.body?.ok` appears character-identically in 2 files — dashboard/test-content-hygiene-api.js, dashboard/test-task-description.js. 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 dashboard/test-canvas-db-endpoints.js:81— `db.prepare('SELECT migrated_at FROM canvas_meta WHERE project = ?').get(project) || null` appears character-identically in 2 files — dashboard/test-canvas-db-endpoints.js, dashboard/test-canvas-db-import.js. 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 dashboard/src/components/Modal.jsx:137— `document.getElementById('modalRoot') || document.body` appears character-identically in 3 files — dashboard/src/components/Modal.jsx, dashboard/src/components/SearchPalette.jsx, dashboard/src/components/SnippetUpgrade.jsx. 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 dashboard/test-files-back-overview-e2e.js:54— `document.querySelector('.file-tree-footer')?.textContent || ''` appears character-identically in 2 files — dashboard/test-files-back-overview-e2e.js, dashboard/test-files-race-regressions-e2e.js. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate REDACTED:591— `e.name === 'context' && e.type === 'directory'` appears character-identically in 2 files — REDACTED, scripts/v5-demo-fixture.mjs. 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 dashboard/src/components/MarkdownEditor.jsx:136— `el.scrollHeight > el.clientHeight || el.scrollWidth > el.clientWidth` appears character-identically in 2 files — dashboard/src/components/MarkdownEditor.jsx, REDACTED. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate dashboard/snippets-doctor.js:442— `entry.name === 'workspace' || entry.name.startsWith('workspace-')` appears character-identically in 2 files — dashboard/snippets-doctor.js, dashboard/test-snippets-realdata.js. 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 dashboard/test-compliance-detection.js:201— `found && found.issues.includes('routed-unclaimed')` appears character-identically in 2 files — dashboard/test-compliance-detection.js, REDACTED. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate dashboard/test-compliance-detection.js:78— `found && found.reason === 'routed-unclaimed'` appears character-identically in 2 files — dashboard/test-compliance-detection.js, REDACTED. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate dashboard/governance.js:86— `principal?.kind === 'human' && principal.verified === true` appears character-identically in 2 files — dashboard/governance.js, dashboard/task-creation-policy.js. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate scripts/capture-v5-gif.mjs:17— `process.env.FLOWBOARD_API || 'http://127.0.0.1:18790'` appears character-identically in 3 files — scripts/capture-v5-gif.mjs, scripts/capture-v5-screenshots.mjs, scripts/v5-demo-fixture.mjs. 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 dashboard/test-t168-t177-integration.js:26— `process.env.FLOWBOARD_API || 'http://localhost:18790'` appears character-identically in 2 files — dashboard/test-t168-t177-integration.js, dashboard/test-v5-integration.js. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Silent fallback default in catch dashboard/flowboard-metadata.js:371— `_parseImportProgress` swallows every exception into `return {}` — a data error becomes a silent behavior change with no trail. Log the failure or let it raise. If that constant is the correct answer rather than a stand-in for a value that could not be read, say so in a comment on the handler or in the docstring, and the row stops firing.
Silent fallback default in catch dashboard/github.js:15— `resolveToken` swallows every exception into `return ''` — a data error becomes a silent behavior change with no trail. Log the failure or let it raise. If that constant is the correct answer rather than a stand-in for a value that could not be read, say so in a comment on the handler or in the docstring, and the row stops firing.
Silent fallback default in catch dashboard/hzl-service.js:3105— `safeJson` swallows every exception into `return {}` — a data error becomes a silent behavior change with no trail. Log the failure or let it raise. If that constant is the correct answer rather than a stand-in for a value that could not be read, say so in a comment on the handler or in the docstring, and the row stops firing.
Silent fallback default in catch dashboard/install-trigger.mjs:71— `readOrEmpty` swallows every exception into `return ''` — a data error becomes a silent behavior change with no trail. Log the failure or let it raise. If that constant is the correct answer rather than a stand-in for a value that could not be read, say so in a comment on the handler or in the docstring, and the row stops firing.
Silent fallback default in catch dashboard/snippets-doctor.js:282— `collectBootstrapDocAdvisories` swallows every exception into `return []` — a data error becomes a silent behavior change with no trail. Log the failure or let it raise. If that constant is the correct answer rather than a stand-in for a value that could not be read, say so in a comment on the handler or in the docstring, and the row stops firing.
Silent fallback default in catch dashboard/snippets-doctor.js:330— `readGatewayProcesses` swallows every exception into `return []` — a data error becomes a silent behavior change with no trail. Log the failure or let it raise. If that constant is the correct answer rather than a stand-in for a value that could not be read, say so in a comment on the handler or in the docstring, and the row stops firing.
Silent fallback default in catch REDACTED:1024— `scanPendingCanvasMigrations` swallows every exception into `return []` — a data error becomes a silent behavior change with no trail. Log the failure or let it raise. If that constant is the correct answer rather than a stand-in for a value that could not be read, say so in a comment on the handler or in the docstring, and the row stops firing.
Silent fallback default in catch REDACTED:1592— `parseIndexMd` swallows every exception into `return []` — a data error becomes a silent behavior change with no trail. Log the failure or let it raise. If that constant is the correct answer rather than a stand-in for a value that could not be read, say so in a comment on the handler or in the docstring, and the row stops firing.
Silent fallback default in catch REDACTED:1699— `projectExists` swallows every exception into `return false` — a data error becomes a silent behavior change with no trail. Log the failure or let it raise. If that constant is the correct answer rather than a stand-in for a value that could not be read, say so in a comment on the handler or in the docstring, and the row stops firing.
Silent fallback default in catch REDACTED:1872— `app.get("/api/projects/:name/task-discipline")` swallows every exception into `return {}` — a data error becomes a silent behavior change with no trail. Log the failure or let it raise. If that constant is the correct answer rather than a stand-in for a value that could not be read, say so in a comment on the handler or in the docstring, and the row stops firing.
Silent fallback default in catch REDACTED:4689— `app.get("/api/projects/:name/github")` swallows every exception into `return {}` — a data error becomes a silent behavior change with no trail. Log the failure or let it raise. If that constant is the correct answer rather than a stand-in for a value that could not be read, say so in a comment on the handler or in the docstring, and the row stops firing.
Silent fallback default in catch dashboard/src/components/Sidebar.jsx:45— `loadUserFolders` swallows every exception into `return []` — a data error becomes a silent behavior change with no trail. Log the failure or let it raise. If that constant is the correct answer rather than a stand-in for a value that could not be read, say so in a comment on the handler or in the docstring, and the row stops firing.
Silent fallback default in catch dashboard/src/components/Sidebar.jsx:56— `loadFolderOrder` swallows every exception into `return []` — a data error becomes a silent behavior change with no trail. Log the failure or let it raise. If that constant is the correct answer rather than a stand-in for a value that could not be read, say so in a comment on the handler or in the docstring, and the row stops firing.
Silent fallback default in catch dashboard/src/pages/FilesView.jsx:68— `readLastOpenedFiles` swallows every exception into `return {}` — a data error becomes a silent behavior change with no trail. Log the failure or let it raise. If that constant is the correct answer rather than a stand-in for a value that could not be read, say so in a comment on the handler or in the docstring, and the row stops firing.
Silent fallback default in catch dashboard/test-support/browser-harness.js:102— `descendantsOf` swallows every exception into `return []` — a data error becomes a silent behavior change with no trail. Log the failure or let it raise. If that constant is the correct answer rather than a stand-in for a value that could not be read, say so in a comment on the handler or in the docstring, and the row stops firing.
Silent fallback default in catch dashboard/test-setup-linux-systemd.mjs:43— `readLines` swallows every exception into `return []` — a data error becomes a silent behavior change with no trail. Log the failure or let it raise. If that constant is the correct answer rather than a stand-in for a value that could not be read, say so in a comment on the handler or in the docstring, and the row stops firing.
Silent fallback default in catch dashboard/test-setup-macos-launchd.mjs:46— `readLines` swallows every exception into `return []` — a data error becomes a silent behavior change with no trail. Log the failure or let it raise. If that constant is the correct answer rather than a stand-in for a value that could not be read, say so in a comment on the handler or in the docstring, and the row stops firing.
Unused export 'default' dashboard/src/components/Card.jsx:11— Nothing ultimately consumes this binding: its only referrer is the re-export in dashboard/src/components/index.js, whose re-exported name has no consumer either. Removing it is therefore not a one-file change — drop the re-export line in dashboard/src/components/index.js in the same commit, or the barrel will import a name that no longer exists.
Unused export 'default' dashboard/src/components/DataList.jsx:8— Nothing ultimately consumes this binding: its only referrer is the re-export in dashboard/src/components/index.js, whose re-exported name has no consumer either. Removing it is therefore not a one-file change — drop the re-export line in dashboard/src/components/index.js in the same commit, or the barrel will import a name that no longer exists.
Unused export 'default' dashboard/src/components/Panel.jsx:14— Nothing ultimately consumes this binding: its only referrer is the re-export in dashboard/src/components/index.js, whose re-exported name has no consumer either. Removing it is therefore not a one-file change — drop the re-export line in dashboard/src/components/index.js in the same commit, or the barrel will import a name that no longer exists.
Unused export 'default' dashboard/src/components/SearchBar.jsx:57— Nothing ultimately consumes this binding: its only referrer is the re-export in dashboard/src/components/index.js, whose re-exported name has no consumer either. Removing it is therefore not a one-file change — drop the re-export line in dashboard/src/components/index.js in the same commit, or the barrel will import a name that no longer exists.
Unused export 'default' dashboard/src/components/Tag.jsx:20— Nothing ultimately consumes this binding: its only referrer is the re-export in dashboard/src/components/index.js, whose re-exported name has no consumer either. Removing it is therefore not a one-file change — drop the re-export line in dashboard/src/components/index.js in the same commit, or the barrel will import a name that no longer exists.
Unused export 'default' dashboard/src/context/NavigationContext.jsx:62— Nothing imports this binding — it is safe to review for removal.
ADR not followed: ADR-0031: Canonical work state and transient stuck indicator docs/adr/0031-canonical-work-state-and-transient-indicator.md:53— docs/adr/0031-canonical-work-state-and-transient-indicator.md:53 rules out `status` in action, but production code uses it: dashboard/src/hooks/useTaskActions.jsx:25, dashboard/src/hooks/useTaskActions.jsx:26, dashboard/src/hooks/useTaskActions.jsx:33, dashboard/src/hooks/useTaskActions.jsx:34
ADR not followed: ADR-0031: Canonical work state and transient stuck indicator docs/adr/0031-canonical-work-state-and-transient-indicator.md:53— docs/adr/0031-canonical-work-state-and-transient-indicator.md:53 rules out `workState` in action, but production code uses it: dashboard/src/hooks/useTaskActions.jsx:41, dashboard/src/hooks/useTaskActions.jsx:42
ADR not followed: ADR-0026: Frontend architecture invariants (post-React-migration) docs/adr/0026-frontend-architecture-invariants.md:45— docs/adr/0026-frontend-architecture-invariants.md:45 rules out `window._viewProject`, but production code uses it: dashboard/test-work-state-poll-race-e2e.js:193, dashboard/test-work-state-e2e.js:221, dashboard/test-task-stats-trend-e2e.js:25, dashboard/test-t447-5-governance-e2e.js:32, dashboard/test-overview-fixes-e2e.js:41 (+8 more)
ADR not followed: ADR-0026: Frontend architecture invariants (post-React-migration) docs/adr/0026-frontend-architecture-invariants.md:61— docs/adr/0026-frontend-architecture-invariants.md:61 rules out `window`, but production code uses it: dashboard/test-work-state.mjs:274, dashboard/test-work-state.mjs:284, dashboard/test-work-state.mjs:314, dashboard/test-work-state.mjs:331, dashboard/test-work-state.mjs:333 (+397 more)
ADR not followed: ADR-0019: Frontend runtime foundation owns task UI state convergence docs/adr/0019-frontend-runtime-foundation.md:56— docs/adr/0019-frontend-runtime-foundation.md:56 rules out `window.appState.tasks` in bridge, but production code uses it: dashboard/test-app-state-bridge.mjs:91
C2 · Access Controls· No named authorization policies · ×1
No named authorization policies — Authorization IS enforced here (by route guards, auth middleware or checks that refuse a caller) — this is NOT a claim that endpoints are unprotected. What's missing is a NAMED rule set: who may do what is encoded inline where it is checked, so the rules can't be listed, reviewed or tested apart from the code that applies them. Recommendation, not a defect.
Documentation: written for insiders docs/design-guidelines.md— The Color Palette section lists concrete values like `--text-strong` but does not explain what each token means or how it maps to the UI elements (e.g. which color is accent, which is muted). Add a short 'What each color/token looks like on screen' table for readers who cannot decode the palette.
D26 · Project Cohesion· Projects may be oversized for their cohesion · ×1
Projects may be oversized for their cohesion — 1 of 2 project(s) overshoot their size bounds, lowering Project Cohesion to 0.0/10. The most over is `dashboard` (77380 LoC, 338 module-visible types across 15 directories). Review these for cohesion — draw the boundary inside the module first (group each responsibility into its own package or directory and keep the cross-boundary members non-public), since splitting a published package moves types between packages and breaks consumers.
No tests found — No test suite could be collected — no discoverable tests to count. If this repository does test, wiring the suite to a framework a runner can collect (Vitest, Jest, Mocha, or the runtime's built-in runner (`node --test`, `bun test`, `deno test`)) is what makes it countable here; a pipeline step that invokes a runner is not evidence on its own, because a runner over an empty suite passes. Tests written as plain executables or shell/PowerShell harnesses are not collectible this way and are not scored here.
GD1 · Unfinished & placeholder code· Placeholder literal left in code · ×1
Placeholder literal left in code scripts/privacy-scan.mjs:18— A placeholder string ("changeme") is still in shipped code — typical of generated boilerplate that was never filled in.
No SAST — No static application security testing detected. For this repository's stack, add CodeQL's javascript-typescript pack, `semgrep --config=p/javascript`, or eslint-plugin-security as a CI step. What was searched, so you can tell an absence from a miss: the 2483 CI workflow file(s) in this repository, and the scanner and linter configuration checked in beside them. A scan that runs outside CI, one configured in your forge's web UI rather than in a committed file, or a tool whose name is none of those this check carries, is not seen — if that is your case the row is wrong, and saying so is more useful than adding a second scanner.
R7 · Dead Code· Unused export 'AgentChipStack' · ×1
Unused export 'AgentChipStack' dashboard/src/components/AgentChip.jsx:136— Nothing ultimately consumes this binding: its only referrer is the re-export in dashboard/src/components/index.js, whose re-exported name has no consumer either. Removing it is therefore not a one-file change — drop the re-export line in dashboard/src/components/index.js in the same commit, or the barrel will import a name that no longer exists.
R7 · Dead Code· Unused export 'tasksForStructureReview' · ×1
Unused export 'tasksForStructureReview' dashboard/src/utils/exceptionReview.mjs:21— Nothing imports this binding — it is safe to review for removal.
R7 · Dead Code· Unused export 'DEFAULT_STALE_THRESHOLD_MS' · ×1
Unused export 'DEFAULT_STALE_THRESHOLD_MS' dashboard/src/utils/leaseHealth.js:9— Nothing imports this binding — it is safe to review for removal.
R7 · Dead Code· Unused export 'worstLeaseHealth' · ×1
Unused export 'worstLeaseHealth' dashboard/src/utils/leaseHealth.js:96— Nothing imports this binding — it is safe to review for removal.
R7 · Dead Code· Unused module-local declaration 'isObject' · ×1
Unused module-local declaration 'isObject' dashboard/project-bundle-import.js:73— This top-level declaration is not exported and its name occurs nowhere else in its module — not called, read, typed against, re-exported or named by a string. Nothing outside the module can reach a non-exported binding, so this is the whole search: remove it, or use it.
R7 · Dead Code· Unused module-local declaration 'cloneJson' · ×1
Unused module-local declaration 'cloneJson' dashboard/project-bundle-import.js:77— This top-level declaration is not exported and its name occurs nowhere else in its module — not called, read, typed against, re-exported or named by a string. Nothing outside the module can reach a non-exported binding, so this is the whole search: remove it, or use it.
R7 · Dead Code· Unused module-local declaration 'parseIndexMd' · ×1
Unused module-local declaration 'parseIndexMd' REDACTED:1575— This top-level declaration is not exported and its name occurs nowhere else in its module — not called, read, typed against, re-exported or named by a string. Nothing outside the module can reach a non-exported binding, so this is the whole search: remove it, or use it.
R7 · Dead Code· Unused module-local declaration 'nextTaskId' · ×1
Unused module-local declaration 'nextTaskId' REDACTED:1619— This top-level declaration is not exported and its name occurs nowhere else in its module — not called, read, typed against, re-exported or named by a string. Nothing outside the module can reach a non-exported binding, so this is the whole search: remove it, or use it.
R7 · Dead Code· Unused module-local declaration 'nextSubtaskId' · ×1
Unused module-local declaration 'nextSubtaskId' REDACTED:1628— This top-level declaration is not exported and its name occurs nowhere else in its module — not called, read, typed against, re-exported or named by a string. Nothing outside the module can reach a non-exported binding, so this is the whole search: remove it, or use it.
R7 · Dead Code· Unused module-local declaration 'STATUS_OPTIONS' · ×1
Unused module-local declaration 'STATUS_OPTIONS' dashboard/src/components/DetailPanel.jsx:69— This top-level declaration is not exported and its name occurs nowhere else in its module — not called, read, typed against, re-exported or named by a string. Nothing outside the module can reach a non-exported binding, so this is the whole search: remove it, or use it.
R7 · Dead Code· Unused module-local declaration 'ACTIVITY_ICON' · ×1
Unused module-local declaration 'ACTIVITY_ICON' dashboard/src/components/DetailPanel.jsx:134— This top-level declaration is not exported and its name occurs nowhere else in its module — not called, read, typed against, re-exported or named by a string. Nothing outside the module can reach a non-exported binding, so this is the whole search: remove it, or use it.
R7 · Dead Code· Unused module-local declaration 'isVerifiedHuman' · ×1
Unused module-local declaration 'isVerifiedHuman' dashboard/task-creation-policy.js:20— This top-level declaration is not exported and its name occurs nowhere else in its module — not called, read, typed against, re-exported or named by a string. Nothing outside the module can reach a non-exported binding, so this is the whole search: remove it, or use it.
R7 · Dead Code· Unused module-local declaration 'validBundle' · ×1
Unused module-local declaration 'validBundle' dashboard/test-project-bundle-schema.js:96— This top-level declaration is not exported and its name occurs nowhere else in its module — not called, read, typed against, re-exported or named by a string. Nothing outside the module can reach a non-exported binding, so this is the whole search: remove it, or use it.
No app-layer HTTPS enforcement detected REDACTED:5347— `app.listen(…)` serves plain HTTP on a network address, and nothing in its package enforces HTTPS: no TLS served (`https.createServer`, Fastify `https`, Nest `httpsOptions`), no redirect of plain requests to `https://`, no `Strict-Transport-Security` (helmet sends it by default), and no TLS-terminating proxy configuration committed beside it — so a browser may talk to it in clear text. (−2.0 on this card.)
X2 · Cancellation propagation· Not all async functions that make a request accept an AbortSignal · ×1
Not all async functions that make a request accept an AbortSignal — Only 3/6 async functions that make a cancellable request (fetch, axios, ky, ofetch) accept an AbortSignal or pass one on, so a request keeps running after whatever wanted it has given up — a page navigated away from, an unmounted component, a timed-out job. Take a `signal` (or an options object that carries one) and hand it to the request; where nothing could ever cancel the call, omitting it is a deliberate choice — judge against how the function is used.
Outdated (npm): @codemirror/lang-markdown — @codemirror/lang-markdown is pinned at 6.5.0; registry.npmjs.org publishes 6.5.2 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
Outdated (npm): @codemirror/language — @codemirror/language is pinned at 6.12.3; registry.npmjs.org publishes 6.13.1 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
Outdated (npm): @codemirror/state — @codemirror/state is pinned at 6.7.5; registry.npmjs.org publishes 6.7.6 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
Outdated (npm): @codemirror/view — @codemirror/view is pinned at 6.43.0; registry.npmjs.org publishes 6.43.15 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
Outdated (npm): @uiw/react-codemirror — @uiw/react-codemirror is pinned at 4.25.10; registry.npmjs.org publishes 4.25.12 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
Outdated (npm): express — express is pinned at 5.2.1; registry.npmjs.org publishes 5.3.0 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
Outdated (npm): express-rate-limit — express-rate-limit is pinned at 8.5.2; registry.npmjs.org publishes 8.7.1 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
Outdated (npm): lucide-react — lucide-react is pinned at 1.47.0; registry.npmjs.org publishes 1.61.0 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
Outdated (npm): react — react is pinned at 19.2.4; registry.npmjs.org publishes 19.3.1 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
Outdated (npm): react-dom — react-dom is pinned at 19.2.4; registry.npmjs.org publishes 19.3.1 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
Outdated (npm): react-grid-layout — react-grid-layout is pinned at 2.2.3; registry.npmjs.org publishes 2.3.0 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
Appendix B — Reproduction & audit trail
Every external tool invocation behind a deep-scan dimension — the tool, its captured version, the exact command, how many findings it yielded, and a link to the retained raw output. To reproduce any finding: check out the same commit and run the command shown (repo-relative — never an absolute scratch path). The complete raw scanner output is retained verbatim under artifacts/raw/ (indexed in artifacts/raw/index.json); per-invocation exit codes and wall-clock durations are in sidecar.json — kept out of this table so the rendered report stays byte-identical across runs of the same commit.
trivy: not applicable — No Infrastructure-as-Code or container manifests found (Dockerfile, Docker Compose, Terraform, Kubernetes/Helm, CloudFormation, ARM, Bicep, Ansible); nothing to scan.
semgrep: not applicable — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that.
runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here.
runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here.
runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here.
Run 01a162f1-f0d7-740c-8a59-8519d3d126db · every finding is also locatable in findings.md, and the complete scoring record (with exit codes + durations) in sidecar.json.
Issues: 70 · Warnings: 960 · Recommendations: 114 · Info: 11 — Appendix A · all findings · full markdown report.
Generated by Watchdog — deterministic code-health analysis. 22-10-2026 @ 09:29 UTC.
Downloadable artifacts
Machine-readable and reproducible from this commit + frozen rubric — drop them straight into a contract appendix, a CRA dossier, or a downstream SCA / VEX tool.