Public report of amruthpillai/reactive-resume, published 26 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, 26 October 2026, 16:20 UTC · Survey ID cd_56c8ace4b905479ba4b75f3dadeac749
amruthpillai/reactive-resume
Measured 26 October 2026, 16:10 UTC, at code version 28fbcb3
Regression: 1 dimension fell since the last survey
A regression is a drop of 0.5 points or more in the score, or of 2.5 or more out of 10 in a dimension, since the last survey.
CAI scoreWeak
CriticalWeakAdequateStrongExemplary
Down 12 since the last survey
The score is built from these lenses. Each lens grades one area of the code, such as how easy it is to change or how well it is protected. The weakest lens counts most, so one weak area pulls the score down instead of being averaged away.
A large codebase: 168,984 lines of product code in 30 projects, tests not counted · Estimated rebuild effort: about 1.4 person-years · Weakest lens: Architecture, 39
Findings by how serious they are
99 critical1276 serious68 minor
7 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
26 October 2026, 16:10 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.
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 ▸
93of 93 dimensions measured by tools.
1421of 1443 findings point to an exact file and line, so you can open each one in the code. The other 22 concern the repository as a whole, such as missing documentation.
93dimensions across 7 lenses, read from 168,984 lines of product code in 30 projects.
amruthpillai/reactive-resume falls short of our standard for production, held back most by its Architecture lens, the way the code is structured into parts. It scores 44 out of 100 and is rated Weak, and 88 of its 99 critical findings are security problems.
Architecture, at 39, is the weakest lens and counts most in the score. The best first step for the work it takes is replacing the two exposed passwords or keys and switching the old ones off, worth about 3 points. Respecting the front end's boundaries would lift Architecture itself, worth about 4 points. Raising Architecture to 70 would lift the score to about 49.
Sixty-three pipeline tools are referenced by a changeable name, so the build pipeline can be tampered with. Nine secrets can leak from the build pipeline, and five settings leave the servers or containers unsafe. Pinning each tool to an exact version, limiting each secret to its own step and correcting the unsafe settings would close these risks. Updating the vulnerable packages would fix the four packages with a known security hole, and the two passwords or keys in the code and the two passwords or keys in the code's history need replacing, with the old ones switched off. The five controls that only work with a mouse need to work with the keyboard, or to become a real button.
The product code is 168,984 lines, about €200,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 Architecture rose from 39 to 70, the lowest score rated Strong, the score would rise from 44 to about 49.
Code composition: what the lines of code are
Product code 81%Tests 19%
New since the last survey: 765 findings
These 765 critical or serious findings weren't in the previous survey, on 12 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: 1063 findings
These 1063 critical or serious findings were in the previous survey, on 12 October 2026, and are gone from this one. The first 100 are listed here.
€67,000 to €340,000, for 1,112 to 3,527 hours of work, about 1.4 person-years for 1 to 3 engineers
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 44. Better code takes more work to write, so the factor is ×1.0 at a score of 70, lower below it and higher above it.
Size
Large: 168,984 lines of product code
What it is not
Not a quotation: nobody has offered to build it for that. Not a valuation: it says nothing about what the business is worth. Not a certified figure: no professional has signed it as one.
How the estimate is made: 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 REDACTED Scanning — start with REDACTED, REDACTED.
Resolve the 1 Projects may be oversized for their cohesion finding(s) in Project Cohesion.
Raises the score by about 2 points · Low effort · Project Cohesion
3
Fix the listed violations: import through public entries (package exports / slice index), never reach into another layer or package's internals.
Raises the score by about 4 points · Medium effort · Import Boundaries
Diagnosis: what the measurements show together
Each conclusion below combines several dimensions into one point that no single dimension shows, and lists the measurements it rests on.
Where the investment is most exposed · Value at risk
This code would cost about €200,000 to build again, about 1.4 person-years of work. Its weakest lens is Architecture, at 39 (Weak). Architecture is about whether the structure holds up as the product grows, and when the structure is weak, a change in one place ripples into many others. Because the weakest lens counts most in the score, work on Architecture also moves the score most.
Based on: the rebuild estimate · the Architecture grade · how much each lens counts
What to do: Start with the Architecture actions in Top priorities.
If you do one thing first · First action
Resolve the 2 Leaked secret finding(s) in REDACTED Scanning. Of all the actions in this report, it raises the score most for the work it takes: about 3 points for low effort, because it clears the 2 REDACTED 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 5.1 out of 10. Code at that level is slower to change than clean code, and Watchdog estimates the extra work at 7% to 17% on every change. The history of the code shows how much it changes: about 2,306,875 lines over the last 90 days, which is about 9,355,660 lines a year. At that pace, the extra work comes to an estimated 1719.1 to 10314.6 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, never less than 2% to 5% and never more than 40% to 60% in all; 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.
Architecture — module dependency graph
Project dependencies, layered top-to-bottom; arrows show direction. Any dashed red edge points upward or sideways, which only happens where the projects form a dependency cycle. A graph without cycles has none.
Architecture: which parts of the code depend on which
The code is divided into modules, groups of code that each handle one part of the product, and a module depends on another when it uses code from it. The table lists the modules both down the side and across the top, in an order where each module should only use modules listed above it. A number in a cell means the module on that row uses the module in that column, and it counts the pairs of building blocks (types) that connect them. The one thing to look for is a mark above the diagonal line. It means two or more modules use each other in a loop (a dependency cycle), so none of them can be changed, tested or released on its own.
400 modules, with 114 dependencies between them. Every module uses only modules listed above it, so there are no loops.
The table shows the 40 modules with the most connections; 360 more are left out to keep it readable.
Which modules use which. The module on each row uses the module in each column, and the number counts the pairs of types that connect them. A cell above the diagonal is part of a loop.
apps.mobile.src.features.applications uses apps.mobile.src.features.applications.next-step, so a change to apps.mobile.src.features.applications.next-step can break apps.mobile.src.features.applications, while a change to apps.mobile.src.features.applications can't break apps.mobile.src.features.applications.next-step.
Position
Below the diagonal: apps.mobile.src.features.applications uses a module listed above it, which is the healthy direction.
apps.mobile.src.features.check uses packages.resume.src.ats.types, so a change to packages.resume.src.ats.types can break apps.mobile.src.features.check, while a change to apps.mobile.src.features.check can't break packages.resume.src.ats.types.
Position
Below the diagonal: apps.mobile.src.features.check uses a module listed above it, which is the healthy direction.
apps.mobile.src.features.design uses apps.mobile.src.features.design.layout, so a change to apps.mobile.src.features.design.layout can break apps.mobile.src.features.design, while a change to apps.mobile.src.features.design can't break apps.mobile.src.features.design.layout.
Position
Below the diagonal: apps.mobile.src.features.design uses a module listed above it, which is the healthy direction.
apps.mobile.src.features.letters uses apps.mobile.src.features.letters.length, so a change to apps.mobile.src.features.letters.length can break apps.mobile.src.features.letters, while a change to apps.mobile.src.features.letters can't break apps.mobile.src.features.letters.length.
Position
Below the diagonal: apps.mobile.src.features.letters uses a module listed above it, which is the healthy direction.
apps.mobile.src.features.workspace uses apps.mobile.src.features.workspace.logic, so a change to apps.mobile.src.features.workspace.logic can break apps.mobile.src.features.workspace, while a change to apps.mobile.src.features.workspace can't break apps.mobile.src.features.workspace.logic.
Position
Below the diagonal: apps.mobile.src.features.workspace uses a module listed above it, which is the healthy direction.
apps.mobile.src.features.write uses apps.mobile.src.features.design.design-pane, so a change to apps.mobile.src.features.design.design-pane can break apps.mobile.src.features.write, while a change to apps.mobile.src.features.write can't break apps.mobile.src.features.design.design-pane.
Position
Below the diagonal: apps.mobile.src.features.write uses a module listed above it, which is the healthy direction.
apps.mobile.src.features.write uses apps.mobile.src.features.write.model, so a change to apps.mobile.src.features.write.model can break apps.mobile.src.features.write, while a change to apps.mobile.src.features.write can't break apps.mobile.src.features.write.model.
Position
Below the diagonal: apps.mobile.src.features.write uses a module listed above it, which is the healthy direction.
apps.web.src.features.assistant uses apps.web.src.features.homepage.remember, so a change to apps.web.src.features.homepage.remember can break apps.web.src.features.assistant, while a change to apps.web.src.features.assistant can't break apps.web.src.features.homepage.remember.
Position
Below the diagonal: apps.web.src.features.assistant uses a module listed above it, which is the healthy direction.
apps.web.src.features.assistant uses packages.api.src.features.agent.messages-persistence, so a change to packages.api.src.features.agent.messages-persistence can break apps.web.src.features.assistant, while a change to apps.web.src.features.assistant can't break packages.api.src.features.agent.messages-persistence.
Position
Below the diagonal: apps.web.src.features.assistant uses a module listed above it, which is the healthy direction.
apps.web.src.features.ats-checker uses packages.resume.src.ats-pdf.types, so a change to packages.resume.src.ats-pdf.types can break apps.web.src.features.ats-checker, while a change to apps.web.src.features.ats-checker can't break packages.resume.src.ats-pdf.types.
Position
Below the diagonal: apps.web.src.features.ats-checker uses a module listed above it, which is the healthy direction.
apps.web.src.features.documents uses apps.web.src.features.resume.import.read-file, so a change to apps.web.src.features.resume.import.read-file can break apps.web.src.features.documents, while a change to apps.web.src.features.documents can't break apps.web.src.features.resume.import.read-file.
Position
Below the diagonal: apps.web.src.features.documents uses a module listed above it, which is the healthy direction.
apps.web.src.features.letters uses apps.mobile.src.features.letters.length, so a change to apps.mobile.src.features.letters.length can break apps.web.src.features.letters, while a change to apps.web.src.features.letters can't break apps.mobile.src.features.letters.length.
Position
Below the diagonal: apps.web.src.features.letters uses a module listed above it, which is the healthy direction.
apps.web.src.features.letters uses apps.mobile.src.features.share.files, so a change to apps.mobile.src.features.share.files can break apps.web.src.features.letters, while a change to apps.web.src.features.letters can't break apps.mobile.src.features.share.files.
Position
Below the diagonal: apps.web.src.features.letters uses a module listed above it, which is the healthy direction.
apps.web.src.features.resume.editor uses apps.web.src.features.resume.editor.store, so a change to apps.web.src.features.resume.editor.store can break apps.web.src.features.resume.editor, while a change to apps.web.src.features.resume.editor can't break apps.web.src.features.resume.editor.store.
Position
Below the diagonal: apps.web.src.features.resume.editor uses a module listed above it, which is the healthy direction.
apps.web.src.features.resume.editor.check uses packages.resume.src.ats.types, so a change to packages.resume.src.ats.types can break apps.web.src.features.resume.editor.check, while a change to apps.web.src.features.resume.editor.check can't break packages.resume.src.ats.types.
Position
Below the diagonal: apps.web.src.features.resume.editor.check uses a module listed above it, which is the healthy direction.
apps.web.src.features.resume.editor.write uses apps.mobile.src.features.design.design-pane, so a change to apps.mobile.src.features.design.design-pane can break apps.web.src.features.resume.editor.write, while a change to apps.web.src.features.resume.editor.write can't break apps.mobile.src.features.design.design-pane.
Position
Below the diagonal: apps.web.src.features.resume.editor.write uses a module listed above it, which is the healthy direction.
apps.web.src.features.resume.editor.write uses apps.mobile.src.features.write.model, so a change to apps.mobile.src.features.write.model can break apps.web.src.features.resume.editor.write, while a change to apps.web.src.features.resume.editor.write can't break apps.mobile.src.features.write.model.
Position
Below the diagonal: apps.web.src.features.resume.editor.write uses a module listed above it, which is the healthy direction.
apps.web.src.features.resume.editor.write uses apps.web.src.features.resume.editor.store, so a change to apps.web.src.features.resume.editor.store can break apps.web.src.features.resume.editor.write, while a change to apps.web.src.features.resume.editor.write can't break apps.web.src.features.resume.editor.store.
Position
Below the diagonal: apps.web.src.features.resume.editor.write uses a module listed above it, which is the healthy direction.
apps.web.src.features.resume.export uses apps.mobile.src.features.share.files, so a change to apps.mobile.src.features.share.files can break apps.web.src.features.resume.export, while a change to apps.web.src.features.resume.export can't break apps.mobile.src.features.share.files.
Position
Below the diagonal: apps.web.src.features.resume.export uses a module listed above it, which is the healthy direction.
apps.web.src.features.resume.public uses apps.mobile.src.features.design.design-pane, so a change to apps.mobile.src.features.design.design-pane can break apps.web.src.features.resume.public, while a change to apps.web.src.features.resume.public can't break apps.mobile.src.features.design.design-pane.
Position
Below the diagonal: apps.web.src.features.resume.public uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in apps.web.src.routes.builder.$resumeId.-sidebar.right.sections.layout uses a type in apps.mobile.src.features.design.layout.
apps.web.src.routes.builder.$resumeId.-sidebar.right.sections.layout uses apps.mobile.src.features.design.layout, so a change to apps.mobile.src.features.design.layout can break apps.web.src.routes.builder.$resumeId.-sidebar.right.sections.layout, while a change to apps.web.src.routes.builder.$resumeId.-sidebar.right.sections.layout can't break apps.mobile.src.features.design.layout.
Position
Below the diagonal: apps.web.src.routes.builder.$resumeId.-sidebar.right.sections.layout uses a module listed above it, which is the healthy direction.
packages.api.src.features.agent uses packages.api.src.features.agent.messages-persistence, so a change to packages.api.src.features.agent.messages-persistence can break packages.api.src.features.agent, while a change to packages.api.src.features.agent can't break packages.api.src.features.agent.messages-persistence.
Position
Below the diagonal: packages.api.src.features.agent uses a module listed above it, which is the healthy direction.
packages.api.src.features.resume uses packages.db.src.client, so a change to packages.db.src.client can break packages.api.src.features.resume, while a change to packages.api.src.features.resume can't break packages.db.src.client.
Position
Below the diagonal: packages.api.src.features.resume uses a module listed above it, which is the healthy direction.
At a glance — Code Health · 47% · Weak · gated by D1, D2, R7, X5 ·
Findings mapped to OWASP categories; the specific CVEs/secrets are in the Security dimension cards below and findings.md (redacted only on the public version of this report).
OWASP category
Findings
Severity
A05:2025 — Injection
87
High / Critical
A02:2025 — Security Misconfiguration
11
High / Critical
A03:2025 — Software Supply Chain Failures
10
High / Critical
A07:2025 — Authentication Failures
5
High / Critical
Roadmap
First, eliminate all boundary violations by ensuring imports strictly use public exports and never access internal package details. Next, maintain slice independence by routing cross-slice dependencies through explicit contracts rather than direct references. Simultaneously, address the two leaked secrets in the e2e and smoke configurations and resolve the oversized project cohesion issue. Finally, clarify the codebase structure by explicitly naming layers or verifying repository conventions, as the current composition analysis reflects naming gaps rather than design flaws.
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 REDACTED Scanning — start with REDACTED, REDACTED.
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.
Add a SAST step to CI running what this repository's stack ships: CodeQL's javascript-typescript pack, `semgrep --config=p/typescript`, 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 — 99
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 — 1276
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 — 68
Recorded, with no effect on how the codebase functions.
Present so the survey is complete, not because it needs doing.
Could not be resolved — 7
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. 93 of 93 evaluated dimensions are computed purely by tools and static analysis (confidence 1.0); none rely on LLM judgement. 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 — 93 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, 1421 of 1443 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.
D14 License Compliance — 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. This repository declares package.json, but the licence verdict published here was taken over its gem dependencies. Nothing was read about its npm dependencies' licensing in either direction, and a clean score on this card must not be read as covering them.
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 (248 contributor(s) across 6276 commit(s) sampled, automation and bot accounts excluded). One of them holds 87% of the history; the other 247 hold 0.1% 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.
D19 Documentation Quality — measured, with a gap in what it reached — Watchdog measured this, but not all of it. What it did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. Each ecosystem's manifests (what makes a folder runnable or a published package) need their own proof before D19 judges its units. Until then those folders' READMEs are judged only as documents (boilerplate, structure), never counted as complete.
D21 Naming 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. D21's deterministic naming rules are gated on C# first (docs/plans/deterministic-engine.md, P5): each other language is switched on only after its own concept suite and A/B gate pass. Until then its declarations carry no naming verdict this run — this says nothing about whether its names are consistent.
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 publishes a package — a Claude Code plugin, declared by plugins/reactive-resume/.claude-plugin/plugin.json — so it DOES have an intentionally-exposed surface: the commands, skills, agents and hooks the plugin contributes to its host, which consumers reach by name. D22 collects code-API surfaces (type and member signatures) only, and has no collector for a plugin's contribution surface, so the consistency of that surface was not judged. That is OUR side and it is a COLLECTOR gap, not an environment fault — no change to the scan image can close it.
D24 Comment Value — 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's reader does not cover the language this repository's product is written in, so it had nothing of the product to read. That is a gap in this analyzer's language reach — not a finding about this repository.
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.
D32 Data Compliance (PII/GDPR) — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. `apps/mobile/app/_layout.tsx`, `apps/mobile/src/features/applications/stages.ts`, `REDACTED`, `apps/mobile/src/features/search/search-screen.tsx`, `apps/mobile/src/features/settings/locale-names.ts`, … (+104 more) produced a parse error, so every rule in this engine's `gdpr.yml` was absent there. That absence is NOT a clean result: these rules detect personal data crossing a boundary into a log sink, a URL or browser storage, and a file that was never parsed cannot report any of the three. The rest of the tree analysed normally and its rows above stand; only these files are unaccounted for. You can widen what we reach: fix the syntax error (or exclude the file deliberately) and re-scan to cover it.
AX7 Slice cohesion — 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. 401 further occurrence(s) are not listed individually; the score already reflects all 441.
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 DockerCompose (REDACTED). compose up failed (exit 18 — an image could not be pulled) — redis Pulling seaweedfs Pulling seaweedfs_create_bucket Pulling postgres Pulling seaweedfs_create_bucket Error Get "https://registry-1.docker.io/v2/": Forbidden seaweedfs Error context canceled redis Error context canceled postgres Error context canceled Error response from daemon: Get "https://registry-1.docker.io/v2/": Forbidden; the earlier `compose pull` step reported: reactive_resume Skipped - No image to be pulled seaweedfs_create_bucket Pulling postgres Pulling seaweedfs Pulling redis Pulling seaweedfs_create_bucket Error Get "https://registry-1.docker.io/v2/": Forbidden seaweedfs Error context canceled redis Error context canceled postgres Error context canceled Error response from daemon: Get "https://registry-1.docker.io/v2/": Forbidden; the runtime sandbox reaches registries only through the in-fence pull-through mirror, so an image the mirror does not carry cannot be fetched — this is a limit of our sandbox, not of your stack; runtime evidence skipped.
M4 Documentation accuracy — 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. M4 checks only the claim kinds adjudicated at or above 95 % precision: links and versions (PREREGISTRATION version 9). Paths, command arguments, installs, environment variables, settings, projects, packages, routes, cd targets, infrastructure products and removed modules are read but not checked, and none of them is reported or counted.
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. 464 further occurrence(s) are not listed individually; the score already reflects all 504.
R11 Import Boundaries — 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. 153 further occurrence(s) are not listed individually; the score already reflects all 193.
R3 Large Files — 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. 55 further occurrence(s) are not listed individually; the score already reflects all 95.
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. 363 further occurrence(s) are not listed individually; the score already reflects all 403.
R7 Dead Code — measured, with a gap in what it reached — Watchdog measured this, but not all of it. What it did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. 218 further occurrence(s) are not listed individually; the score already reflects all 258.
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. 40 further occurrence(s) are not listed individually; the score already reflects all 80.
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 log through no library that carries a message's values as fields (pino, winston, bunyan, tslog, LogTape, roarr; Python's logging, structlog; PHP's PSR-3 loggers), so its log calls cannot be judged, 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.
D5 Coupling: Coupling is measured between projects/assemblies — runtime coupling through DI, reflection, messaging or shared databases is invisible to a static reference graph.
D6 Cohesion (LCOM4): LCOM4 cohesion is syntactic — it infers connectivity from which methods touch which fields/methods by name, not from real runtime behaviour or intent.
D8 Code Coverage: Coverage is measured by building and running the test suite inside 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.
D10 Test Quality: Assertion density is structural — it cannot tell a meaningful behavioural assertion from a trivial one, only that an assertion is present.
D11 Test Reliability: Flakiness is inferred from history/markers — Watchdog runs the suite once (for coverage), not the repeated runs under varied conditions that reveal nondeterminism, so a flaky test never recorded as failing is invisible here.
D12 Dependency Hygiene: Dependency health reads manifests and lockfiles — a vulnerability in a vendored/copied dependency, or risk from how a dependency is actually used, is outside this view.
D13 REDACTED Scanning: REDACTED detection is signature- and entropy-based on the current tree — a secret that does not match a known pattern, or one already rotated, will not be flagged (a clean scan is "nothing matched", not "no secrets exist").
D14 License Compliance: License compatibility is checked against declared package metadata and a policy — mislabelled or missing license metadata, and obligations that depend on how you distribute, are not resolved here.
D15 Churn × Complexity Hotspots: Churn hotspots come from git history — a freshly imported or squashed repository has no churn signal, and recent rewrites can mask a historically risky file.
D17 Explicit Debt: Acknowledged-debt signals (TODO/FIXME, suppressions, dead code) are textual — undocumented debt that nobody marked, and debt that lives in design rather than annotations, is invisible. Committed machine-written code (scaffolded migrations, designer/codegen output, generated stubs) is excluded — it is never the team's dead code to delete.
D19 Documentation Quality: Documentation quality publishes two things only: a runnable or packaged unit with no example, and a multi-project root README that maps none of its parts. It does not judge clarity, and its other checks (overview, licence, boilerplate, structure, empty sections, XML-doc coverage) are withheld after adjudication: their candidates are counted in the card's gaps, not shown as rows. A false statement in a document is M4's; units are .NET projects only.
D20 ADR Quality: ADR quality 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.
D23 Boundary Type-Coupling: Boundary leakage is detected from type references across detected contexts — leaks that flow through primitives, serialization or shared infrastructure may not surface as a typed reference.
D26 Project Cohesion: Project focus is sized from members/namespaces per project — a project that is broad by deliberate design reads the same as one that has sprawled.
D28 Secrets (history): Secret-history scanning sweeps the git log for known patterns — a secret that predates the available history, or never matched a signature, is not found (clean means "nothing matched in the history we can see").
D29 Static Analysis (SAST): SAST findings are pattern-based (semgrep) — it finds classes of bug it has rules for; logic flaws, auth/authorization gaps and issues needing runtime context are out of reach (and clean means "no rule matched").
D30 Dependency Vulnerabilities: CVE matching depends on accurate package/version metadata and on the advisory databases — a vulnerability with no published advisory, or in code not declared as a dependency, is not seen. Coverage needs a RESOLVED graph: an unpinned requirements.txt, or a pom without a resolved build, yields partial coverage rather than a clean verdict. An ecosystem the analyzer cannot scan is reported as unmeasured, never as clean.
D31 IaC & Container Security: IaC scanning checks Dockerfiles/Terraform/Kubernetes against best-practice rules — it cannot see the live cloud account, runtime configuration, or drift between the committed config and what is actually deployed.
D34 Knowledge Freshness: Freshness is decayed commit RECENCY, not comprehension — code read often but rarely committed reads as orphaned, and stable code that genuinely needs no changes is penalised the same as forgotten code; bot/squash commits distort it like the bus factor.
D35 Change Coupling: Change coupling is co-change in COMMITS — files split across separate commits, or coupled only through a shared config/build step, read as uncoupled, and a sweeping commit (rename/format) is excluded so it doesn't couple everything. It shows that files change together, not WHY: a high coupling can be a healthy cohesive pair as readily as a hidden leak.
D43 Malicious Dependencies: Only packages some vulnerability database has already NAMED as malicious are seen — a compromise published in the last hours, or never reported at all, is invisible here, and this dimension reading 10 is not evidence that a dependency is trustworthy. There is no typosquat or dependency-confusion analysis: a package nobody has reported is simply absent from the feeds. Coverage is the dependency scan's: an ecosystem that could not be scanned is disclosed as unmeasured, never as clean.
D44 Platform End-of-Life: The support table is FROZEN, so it goes out of date by losing RECALL: a release that ended support after the table was written is missed until the table is refreshed, and this dimension reading 10 is not evidence that a platform is current. Only platforms the repository DECLARES in a place this pass reads are seen — a runtime named only in a REDACTED (D31's subject), in a CI workflow (D29's), or in a file this pass does not parse (go.mod, a Gemfile ruby directive) is invisible here, which is why a repository declaring none of them abstains rather than scoring. Only frameworks with a PUBLISHED support policy are tracked: React, Flask and Express publish none, so their age cannot be judged and their absence from a report is not a statement that they are supported.
AC1 Text alternatives: Alt-text is detected structurally — the scan sees that an alternative EXISTS, not whether it meaningfully describes the image, and decorative-vs-missing is judged by attribute shape; runtime-injected images and a non-role=img decorative svg are out of scope. This is accessibility readiness, never a WCAG conformance claim.
AC2 Forms & labels: Label association is read from static markup — a label wired up at runtime (JS-set aria-labelledby, framework-injected ids) reads as missing, a present label says nothing about whether its text is correct. A known UI-library field component (e.g. a JSX <TextField>) is now checked conservatively — flagged only when it carries NO label/aria-label/aria-labelledby/id/name — but wrapper/context-labelled libraries (Chakra/Radix FormControl+FormLabel) aren't statically visible (possible false positive) and non-JSX lowercased components are still skipped. A click handler on a plain element is now asked for a name too (it is a control the author declared), but the subtree test that answers it is deliberately generous: any DYNAMIC text expression in the subtree counts as a name, so an icon chosen by a ternary ({cond ? <IconA/> : <IconB/>}) reads as named, and a glyph component from a library the icon-import list does not know still names its parent. A clean result is "no unlabelled control found", not a labelling proof.
AC3 Page structure: Page structure is read from the static markup tree — landmarks, headings and lang injected at runtime aren't seen, heading ORDER is checked structurally (not against the rendered visual hierarchy), and lang/title/main fire only on full documents, never partials, and the data-table check sees header-cell presence (a <th> exists), not whether each header correctly associates with its cells. Static readiness, not conformance.
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.
C4 Data Retention: This control is scored from in-repo evidence only — its real-world effectiveness, exercised only at runtime, is outside a static scan.
C5 Data-Subject Rights: This control is scored from in-repo evidence only — absence of evidence here means the scan found no in-repo trace, not that the control does not exist.
M4 Documentation accuracy: Onboarding quality is an LLM read of the docs/setup present — it cannot run the onboarding or measure how long a real new joiner takes; the verdict is sampled and advisory.
P4 Deployment & Rollback: Approval/branch-protection rules live in repository settings the scan cannot see — only their in-repo evidence (config files, workflows) is checked, so a control enforced purely in the host's settings reads as "not evidenced".
P5 DR & Backup: Backup/restore and disaster-recovery readiness is judged from in-repo evidence — a config that exists is not a tested restore, so the absence of positive evidence is reported as "not evidenced", never scored as present.
P6 Release Hygiene: Rollback/observability controls are inferred from repo artefacts (pipelines, dashboards-as-code) — controls configured in external tooling, with no in-repo trace, cannot be credited.
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.
252 method(s) exceeded the cyclomatic complexity threshold of 15; the worst was add-sheet.AddApplicationSheet at 122. A further 9 method(s) were over the threshold but excluded as flat dispatchers (a long switch/match over independent cases: many branches, almost no nesting), the largest being messages.getPdfFindingMessage at 78 — they are counted neither in the figure above nor in this dimension's score. 7 files carry no cyclomatic complexity row at all for this reason — every one of their over-threshold methods was excluded, so the exclusion is disclosed nowhere in the file itself: apps/mobile/src/features/ats-checker/messages.ts (messages.getPdfFindingMessage at 78), apps/web/src/features/auth/pages/error.tsx (error.getErrorMessage at 22), apps/web/src/features/resume/editor/write/model.ts (model.describeEntry at 18), packages/env/src/deployment.ts (deployment.deploymentEnvironment at 18), apps/mobile/src/features/write/entry-fields.tsx (entry-fields.EntryFields::render at 17), and 2 more not listed here. They are named here because the per-file figures other dimensions report are taken BEFORE this exclusion, so such a file can show a high maximum complexity elsewhere in this report and nothing here, with nothing to reconcile the two.
+ 246 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Bring the 11 bodies over 60 down to 60 or less in Cyclomatic Complexity — start with add-sheet.AddApplicationSheet (cyclomatic 122), practise.Session (cyclomatic 85), cascade.resolveStylesheet (cyclomatic 85). — 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 11 together lifts Cyclomatic Complexity from 3.2 to about 4.8/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.
+ 288 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Bring the 18 bodies over 60 down to 60 or less in Cognitive Complexity — start with cascade.resolveStylesheet (cognitive 204), practise.Session (cognitive 163), practise.Session (cognitive 141). — 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 18 together lifts Cognitive Complexity from 2.0 to about 4.3/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 Classes5.4 / 10Adequate✓ 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 167 FunctionTooLong finding(s) in God Classes — start with apply.tsx (6), today.tsx (4), index.tsx (4). — One of this dimension's main actionable groups (167 warning-level).
Resolve the 40 FileTooLong finding(s) in God Classes — start with service.ts (4), sections.tsx (2), practise.tsx (2). — One of this dimension's main actionable groups (40 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.
Do you agree with this assessment?
D5 · Coupling8.2 / 10Strong✓ Tool-verified
What it measures: Whether volatile projects sit underneath others that depend on them (so their churn ripples upward), and whether project dependencies form cycles. A widely-depended-on but stable shared/kernel project is healthy, not penalised.
Method: Dependency cycles via elementary-DFS over real .csproj references, plus Martin instability (afferent/efferent) per project. Exhaustive over the reference graph, deterministic.
Coverage: Exhaustive · type-level: afferent/efferent coupling + cycles computed over every production type — the population is all types, not a name convention.
27 production modules (Gradle+Cargo+npm+CMake), 0 dependency cycle(s), 0 unstable depended-on module(s). Read from the build's own module declarations; edges a convention plugin adds from buildSrc or build-logic are not visible there; 6 module(s) off the main sequence, with abstractness counted on 26 of the 27 (the rest declare no modelled class or interface, export only macros, declare types in source no model reads, or have no source directory of their own).
Off the main sequence: @reactive-resume/forme-native · ×6
What to do
Resolve the 6 Off the main sequence finding(s) in Coupling. — One of this dimension's main actionable groups (6 warning-level).
Enforce Coupling in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
Detailed fixes: d5_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether a class's methods are focused on a single responsibility.
Method: LCOM4 cohesion per production class with at least two methods: connected components of methods sharing state or calls, computed syntactically. Deterministic, not a proxy.
Coverage: Exhaustive · type-level: LCOM4 cohesion computed over every production class — the population is all types, not a name convention.
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.
Line coverage 79.6%. Measured from the JavaScript/TypeScript suite (node:test via `pnpm install --frozen-lockfile --ignore-scripts` in apps/mobile/).
✓ On the Gold path — maintain.
Detailed fixes: d8_recommendation.md.
Do you agree with this assessment?
D9 · Test Distribution9.8 / 10Exemplary✓ Tool-verified
What it measures: Whether the test suite has a healthy mix of unit / integration / end-to-end tests.
Method: Test projects classified (Unit/Integration/BDD/E2E) from compiled metadata; test methods counted exhaustively across projects with placement-agnostic disk fallback. Deterministic.
1540 test methods: 1513 unit, 0 integration, 0 BDD, 27 e2e. The JavaScript/TypeScript suite contributes 1540 `it`/`test` case(s) across 359 test file(s) declaring at least one; its tier split is read from package names and paths only.
✓ On the Gold path — maintain.
Detailed fixes: d9_recommendation.md.
Do you agree with this assessment?
D10 · Test Quality10.0 / 10Stronggated by 3 serious findings✓ Tool-verified
What it measures: Whether the tests truly assert behaviour rather than just running the code.
Method: Per-test assertions, skips, and mock references analyzed via Roslyn; structured skip-reason tags (BUG:/ENV:) separate documented deferrals from debt. Deterministic.
Mock-dominated test: creates and duplicates with an automatically generated address · ×12packages/mcp/src/tools.test.ts:110
What to do
Resolve the 12 Mock-dominated test finding(s) in Test Quality — start with service.test.ts (8), tools.test.ts, router.test.ts. — One of this dimension's main actionable groups (12 recommendation-level).
Resolve the 3 Skipped test finding(s) in Test Quality — start with assistant.spec.ts, career.spec.ts, guest.spec.ts. — One of this dimension's main actionable groups (3 warning-level).
Enforce Test Quality in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
Detailed fixes: d10_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D11 · Test Reliability10.0 / 10Exemplary✓ Tool-verified
What it measures: Whether the tests pass reliably, with no flakiness.
Method: Suite re-run N times within tiered wall-clock budgets (unit to e2e); tests failing non-deterministically across runs flagged; guarded tests retried when #if guards detected.
What it measures: Whether dependencies are current, secure, and not bloated.
Method: Manifest scan via dotnet list package across all projects; worst-signal-per-package deduction (saturating for vulnerabilities, capped-linear for deprecation/outdated) per KLoC. Exhaustive, deterministic.
0 outdated direct gem(s), 0 pinning defect(s). 2 declaration(s) graded against rubygems.org, 1 of them against a version resolved in a committed Gemfile.lock. 1 declaration(s) carry a requirement that EXCLUDES the current release; that is a deliberate constraint (a supported-version ceiling or a held-back CI pin) and is counted, not charged. Whether any of these gems is DEPRECATED or YANKED is not graded — rubygems.org publishes no deprecation marker, and a yank removes a version rather than flagging it. Whether any is UNMAINTAINED is not graded either: no registry publishes a maintenance status, and release age does not stand in for one. Whether any is UNUSED is a source question, not a registry one. Known CVEs in this dependency graph are D30's question, read from the manifest there.
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 REDACTED Scanning — start with REDACTED, REDACTED. — One of this dimension's main actionable groups (2 issue-level).
Enforce REDACTED Scanning in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
Detailed fixes: d13_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether the licenses of third-party packages are compatible with your policy.
Method: Third-party package licenses resolved from declared package metadata and checked against the configured policy (allow/deny/copyleft). Deterministic; clean = no incompatible license found at metadata depth.
0 of 132 shipped gem(s) use a banned license. Licences were resolved from rubygems.org over the 132 gem(s) a consumer installs — this repository's runtime declarations closed transitively over its committed Gemfile.lock. Development-group and `add_development_dependency` gems are excluded: they are not distributed with this repository. 2 of them publish no licence on rubygems.org; that is missing data, not a violation, and none of them is charged. ★ COVERAGE OF THIS VERDICT: it grades this repository's gem dependencies and nothing else. The repository also declares package.json, and the licences of those dependencies were NOT read by this pass — a gap in this engine's coverage, not a statement about them. So this result says the graded closure carries no banned licence; it does NOT say this repository's licensing is clear.
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: packages/auth/src/config.ts (18×45=810); apps/mobile/src/features/documents/library.tsx (7×75=525); apps/server/src/openapi/generator.ts (12×35=420) Repeated repair below the complexity floor: packages/fonts/src/index.ts (6 of 10 changes were fixes); packages/api/src/features/storage/service.ts (6 of 8 changes were fixes); packages/db/src/schema/auth.ts (5 of 8 changes were fixes)
Resolve the 95 Hotspot finding(s) in Churn × Complexity Hotspots — start with service.ts (3), index.tsx (2), config.ts. — One of this dimension's main actionable groups (95 warning-level).
Resolve the 12 Repeated repair finding(s) in Churn × Complexity Hotspots — start with index.ts (2), service.ts, auth.ts. — One of this dimension's main actionable groups (12 warning-level).
Detailed fixes: d15_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Acknowledged debt left in the code — TODOs, dead code, suppressed warnings.
Method: Roslyn syntactic debt markers (suppressions/TODO/FIXME/HACK/empty-catch/commented-code/Obsolete) plus SymbolFinder dead-code analysis; weighted-debt-per-KLoC density deducted 2.0x per unit. Deterministic, exhaustive.
0 deducted task-comment markers across 167995 LoC (0.0/KLoC) → score 10.0. Task comments only: this repository's language is read without a compiler, so D17's suppression, dead-code and commented-out-code arms did not run and this score counts fewer marker kinds than a .NET repository's would.
What it measures: Whether the project's documentation is clear, complete, and useful.
Method: Every README, docs/ document and root guide parsed by its markup and measured in Unicode letters. Published: a runnable or packaged .NET project whose README (or a document it links, or a root guide) shows no example, and a root README naming none of three or more projects. Overview, licence, boilerplate, wall-of-text, empty-section and XML-doc rows are measured and withheld (counted in gaps) after adjudication. Deterministic, exhaustive, advisory.
1 of 1 documentation facets pass in full. 139 document(s) read across 1 unit(s).
✓ On the Gold path — maintain.
Detailed fixes: d19_recommendation.md.
Do you agree with this assessment?
D20 · ADR Quality0.0 / 10Critical✓ Tool-verified
What it measures: Whether architecture decisions are recorded well (context, decision, consequences).
Method: 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 domain types (IDs, enums, value objects) leak across bounded-context boundaries.
Method: Cross-context domain-type leakage via Roslyn structural classification (strongly-typed IDs / value objects) over every public surface. Exhaustive, deterministic, type-level aggregate-boundary check.
Coverage: Bounded contexts derived from NAMESPACE prefix (or graph-inferred where available); cross-boundary domain-type leakage then checked exhaustively over every public member of every type.
35 domain type(s) cross context boundaries across 22 contexts.
Cross-context type DbOrTx (db → api) · ×8packages/api/src/features/documents/ownership.ts:10
Cross-context type AuthProvider (auth → web) · ×5apps/web/src/features/settings/account/auth-hooks.ts:14
Cross-context type AtsCategory (resume → mobile) · ×2apps/mobile/src/features/check/issues.ts:29
Cross-context type PageMapTarget (pdf → mobile) · ×2apps/mobile/src/features/check/model.ts:52
Cross-context type PdfCategory (resume → web) · ×2apps/web/src/features/ats-checker/messages.ts:344
+ 13 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Resolve the 8 Cross-context type DbOrTx (db → api) finding(s) in Boundary Type-Coupling — start with version-history.ts (2), slugs.ts (2), ownership.ts. — One of this dimension's main actionable groups (8 warning-level).
Resolve the 5 Cross-context type AuthProvider (auth → web) finding(s) in Boundary Type-Coupling — start with auth-hooks.ts (5). — One of this dimension's main actionable groups (5 warning-level).
Resolve the 2 Cross-context type AtsCategory (resume → mobile) finding(s) in Boundary Type-Coupling — start with issues.ts (2). — One of this dimension's main actionable groups (2 warning-level).
Enforce Boundary Type-Coupling in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Verified — provenance only; does not change the score.
Detailed fixes: d23_recommendation.md · top locations in Appendix A, every location in findings.md.
4 of 30 build units (Bundler, Cargo, Gradle, 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: REDACTED scan via TWO gitleaks detect passes in an isolated checkout — the full git history, then a second --no-git pass over the working tree as it stands — merged and de-duplicated by (rule, file, line); each match flagged 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.
2 finding(s): 0 critical, 2 high, 0 medium, 0 low. Remediation for historically-committed secrets is credential rotation — they remain in history regardless of later deletion.
REDACTED
REDACTED
REDACTED
What to do
Resolve the 1 REDACTED finding(s) in Secrets (history) — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
Resolve the 1 High secret finding(s) in Secrets (history) — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
Resolve the 1 Rotate the exposed credentials finding(s) in Secrets (history). — One of this dimension's main actionable groups (1 recommendation-level).
Detailed fixes: d28_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Real static-analysis (SAST) findings — likely security bugs in the code, any language.
Method: Polyglot static analysis via semgrep across the repo using the pinned, image-baked p/security-audit + p/owasp-top-ten rulesets (no scan-time registry fetch); severity rules (ERROR/WARNING/INFO) map to a full-band severity-weighted score. Exhaustive, deterministic; degrades on parse failure.
Coverage: semgrep pattern rules over all files — exhaustive for the rule set, blind to classes of bug without a rule (clean = no rule matched).
87 finding(s): 0 critical, 75 high, 12 medium, 0 low. 63 unpinned-GitHub-Actions row(s) are reported here but scored by D36 (supply-chain provenance), which measures that posture as `pinned_actions` — one pinning decision is charged once, not once per lens. semgrep hit a parse error in 114 file(s) — `apps/mobile/app/_layout.tsx` (line 50), `apps/mobile/src/features/applications/stages.ts` (line 43), `REDACTED` (lines 43–45), `apps/mobile/src/features/search/search-screen.tsx` (line 259), `apps/mobile/src/features/settings/locale-names.ts` (line 61), … (+109 more) — so no absence of findings in the named regions is evidence of anything; rows reported elsewhere in those files are real. Fix the syntax error (or exclude the file deliberately) and re-scan to cover them. Separately, one or more rules could not re-parse an embedded snippet in 1 file(s) (e.g. a workflow `run:` block read as shell). Those files WERE scanned and their other rows are unaffected; only those rules' view of those snippets is missing.
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
+ 6 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Resolve the 9 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (8), REDACTED. — One of this dimension's main actionable groups (9 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).
No action in Static Analysis (SAST) — all 63 REDACTED finding(s) are reported here at file:line but scored by D36 (supply-chain provenance), so none is charged to this dimension. — One of this dimension's main actionable groups (63 issue-level, 0 of them charged here).
Detailed fixes: d29_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether any dependency has a known published vulnerability (CVE), direct or transitive, in ANY ecosystem the repository declares — Dart pub, Elixir and Erlang via Hex, Go modules, Java and Kotlin via Maven/Gradle, JavaScript/npm, .NET/NuGet, PHP/Composer, Python/PyPI, RubyGems, Rust/Cargo and Swift.
Method: Dependency-CVE scan across every ecosystem the repository declares, scored ONCE. Three sources are unioned and deduplicated by advisory identity (rule id + alias closure, CVE<->GHSA) scoped to package+version, keeping the worst severity: `osv-scanner --recursive` over osv.dev for Dart pub, Elixir/Hex (and Erlang, whose `rebar.lock` syft first converts to a CycloneDX SBOM the scanner reads, with rows attributed back to the lock), Go, Java and Kotlin via Maven/Gradle (and Scala, whose sbt build's pinned direct declarations are written into a CycloneDX SBOM the scanner reads, with rows attributed back to the build file), npm, PHP/Composer, Python/PyPI, RubyGems, Rust/Cargo and Swift; `trivy fs --scanners vuln` for npm lockfiles; and `dotnet list package --vulnerable --include-transitive` for NuGet (with per-advisory collapse of the project x target-framework fan-out), plus a DECLARED-dependency arm that resolves a published gem's gemspec against rubygems.org where no Gemfile.lock is committed. `SeverityScore(c,h,m,l, normalizer 8.0)`. NotApplicable only when NO ecosystem is readable; if any applicable ecosystem could not be scanned the findings are REPORTED and the score is withheld. Supersedes the npm and OSV arms, retired 2026-09-05.
Resolve the 4 High CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (4). — One of this dimension's main actionable groups (4 issue-level).
Resolve the 2 Medium advisory (unmaintained) finding(s) in Dependency Vulnerabilities — start with REDACTED (2). — One of this dimension's main actionable groups (2 warning-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.
Resolve the 5 High IaC finding(s) in IaC & Container Security — start with REDACTED (4), REDACTED. — One of this dimension's main actionable groups (5 issue-level).
Resolve the 4 Low IaC finding(s) in IaC & Container Security — start with REDACTED (4). — One of this dimension's main actionable groups (4 recommendation-level).
Resolve the 2 Medium IaC finding(s) in IaC & Container Security — start with REDACTED (2). — One of this dimension's main actionable groups (2 warning-level).
Detailed fixes: d31_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether anyone still has living knowledge of each file, or it has been orphaned — last understood long ago by someone now gone quiet. The sibling of the bus factor: D16 asks who owns it, D34 asks whether anyone still knows it.
Method: File orphaning as total living-knowledge decay below one focused-commit's worth within a year, computed per-file from the D16 decay model. Exhaustive, deterministic over fixed history.
Every significant source file has living knowledge — recently and meaningfully worked. Counted over 684 of the 1190 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.
What it measures: Whether the build pipeline provides supply-chain integrity — generated provenance/attestation, signed artifacts (cosign/sigstore), an SBOM, and pinned build actions. Presence of the configuration, not a runtime guarantee.
Method: Supply-chain provenance/signing read deterministically from CI/build config (.github/workflows, .gitlab-ci.yml, azure-pipelines, Jenkinsfile, .circleci) + the release surface: four signals — generated provenance/attestation (SLSA/in-toto/actions-attest), artifact signing (cosign/sigstore/gitsign), an SBOM (syft/sbom-action/*.spdx.json/*.cdx.json), and SHA-pinned build actions — scored 10·present/denom. NotApplicable without a build pipeline. Detects configuration presence, not runtime enforcement.
What it measures: Whether the repository publishes a coordinated-vulnerability-disclosure policy (SECURITY.md or security.txt) with a reporting contact, so finders know how to report a vulnerability. Presence of a policy file with a contact, not whether the policy is adequate or honoured.
Method: Vulnerability-disclosure policy read deterministically from the repo: a SECURITY.md (root/.github/docs) or .well-known/security.txt / security.txt, regex-checked for a reporting contact (email / URL / mailto). Present + contact → 10; present without a contact → 4; NotApplicable when no policy file exists (it may live off-repo). Detects the policy file's presence + contact, not its adequacy.
What it measures: Whether any dependency the repository declares is published as MALICIOUS rather than merely vulnerable — a package that is an attacker's work, in any ecosystem osv-scanner reads. Scored apart from D30 because the answer is binary: there is no safe version to upgrade to, and the fix is to remove the package and rotate every credential it could have read.
Method: The same dependency scan D30 reads, partitioned on the scanner's own classification rather than rescanned: a row is MALICIOUS when its id is in the `MAL-` space (the ossf/malicious-packages feed) OR its `database_specific.cwe_ids` carries `CWE-506` ("Embedded Malicious Code"). Both channels are structural; the summary text is deliberately NOT read, because a malicious-package record whose summary says only "Critical severity vulnerability" is a real shape ([GHSA redacted]) and a text matcher misses it. Scored BINARY: any surviving row is 0, whatever its severity and however many CVEs sit beside it — a hostile dependency is not a quantity. Applicability and degradation are D30's: NotApplicable only when no ecosystem is readable, and an unscannable ecosystem degrades rather than reading clean. SCORED, not informational.
What it measures: Whether anyone still ships security patches for the platform this repository RUNS ON — the runtime it pins and the framework majors its own constraints hold it to. Separate from D12 because the question differs: a current Django on an end-of-life Python is perfectly up to date and completely unsupported, and the fix is a migration rather than a version bump. What the repository says it merely SUPPORTS is never charged.
Method: End-of-life PLATFORM read from the repository's own declarations and graded against a FROZEN, dated table of vendor support dates — no network, no feed, no API, so this dimension answers identically inside a closed scan fence. Two subjects: a RUNTIME the project pins (a single or all-end-of-life TargetFramework, a .nvmrc or .python-version, a requires-python CAP) and a FRAMEWORK major a dependency constraint cannot move off (a caret, tilde or exact version; `vue@^2.7.16` pins Vue 2). A FLOOR is deliberately never charged — `requires-python = ">=3.8"` states what a package SUPPORTS, not what it runs on — and a multi-target project is charged only when EVERY target is out of support. Runtime 4.0/product capped 8.0, framework 1.5 capped 4.5. The table is safe to freeze because a statement about support that ended in the past cannot become false: it loses recall as it ages, never precision, and a test asserts every entry predates the freeze date. Disjoint from D31 (a container image's OS layer) and D29 (the toolchain a CI workflow installs). Abstains when the repository declares no platform this pass reads — never scores it clean.
0 end-of-life runtime(s) and 0 end-of-life framework(s), read from 2 platform declaration(s) and 2 dependency declaration(s). This dimension reads what the repository says about ITSELF — a pinned target framework, a version file, a capped requires-python, a Rust toolchain pin, a framework major a constraint cannot move off. A FLOOR is deliberately never charged: `requires-python = ">=3.8"` states what the package SUPPORTS, not what it runs on, and a well-maintained library declares exactly that while running its own CI on a current release. The end-of-life facts are FROZEN and dated, so this dimension needs no network and answers identically inside a closed scan fence; as the table ages it loses recall and never precision, because a statement about support that ended in the past cannot become false. The OS layer of a container image is D31's question and the toolchain a CI workflow installs is D29's; this row is neither.
✓ On the Gold path — maintain.
Detailed fixes: d44_recommendation.md.
Do you agree with this assessment?
Frontend & cross-cutting dimensions
R = React/JS · M = Maturity · P = Readiness.
AC1 · Text alternatives10.0 / 10Exemplary○ Nothing flagged
Other · Accessibility — Whether non-text content carries a text alternative — img/area/input[type=image] have alt, a meaningful svg has a title or aria-label, video has a captions track, and object/embed/canvas have a name or fallback content. Static markup readiness, not a WCAG conformance claim.
Method: Static markup-model scan: every img/area/input[type=image] checked for alt, svg[role=img] for a title/aria-label, video for a captions <track>. Components skipped, spreads suppressed. Deterministic, hard fact per element.
Coverage: Population: image/media elements — img, area, input[type=image], svg, video, object, embed, canvas — across the PARSED MARKUP files only (.html/.htm/.cshtml/.razor/.vue/.svelte/.jsx/.tsx); components, hidden subtrees and dynamic-attribute elements are skipped. Markup built in script — tagged-template (html`…`) UIs and hyperscript DOM factories — is NOT read by any producer, so it contributes no element to this population; where such a frontend is present the card discloses it as an analyzer gap rather than scoring around it.
Do you agree with this assessment?
AC2 · Forms & labels6.7 / 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.
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. (×6) — apps/mobile/src/components/collection-header.tsx:66, apps/mobile/src/features/assistant/chat-view.tsx:784, apps/mobile/src/features/assistant/messages.tsx:372, …
This UI-library field component has no label / aria-label / aria-labelledby / id — and neither does anything it renders (a name prop is the form-submission key, not a label) — so it likely renders an unlabelled control. Name it 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. (×2) — apps/mobile/src/features/design/advanced.tsx:496, apps/mobile/src/features/design/controls.tsx:201
A fieldset groups related controls but has no <legend> to name the group. Add a <legend> as its first child — or, if the group already has a visible caption beside it (or the fieldset is there only to disable its subtree and carries no group box), point aria-labelledby at that caption's id instead, which names the group without rendering a second one. (×5) — apps/web/src/features/resume/editor/write/basics-card.tsx:81, apps/web/src/features/resume/editor/write/entry-card.tsx:175, apps/web/src/features/resume/editor/write/entry-card.tsx:239, …
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. — apps/web/src/routes/builder/letter/-components/letter-page.tsx:205
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.
Do you agree with this assessment?
AC3 · Page structure7.7 / 10Strong✓ Tool-verified
Other · Accessibility — Whether pages declare a language (well-formed BCP-47) and a non-empty title, expose exactly one main landmark and a sane heading order with non-empty headings, keep zoom enabled, title their iframes, give data tables header cells, and avoid meta-refresh. Static markup readiness, not a WCAG conformance claim.
Method: Static markup-model scan: html lang, document <title>, a main landmark and heading order on full documents only, plus zoom-disabling viewports, untitled iframes and meta-refresh anywhere. Deterministic, per structural checkpoint.
Coverage: Population: the PARSED MARKUP documents (.html/.htm/.cshtml/.razor/.vue/.svelte/.jsx/.tsx). The page-level checks — lang, title, single main landmark — fire ONCE PER FULL DOCUMENT (an <html> root) and never on a partial or component fragment, so a repo of fragments is assessed only on the per-element checks (heading order, table headers, iframe titles, meta-refresh, zoom). Markup built in script — tagged-template (html`…`) UIs and hyperscript DOM factories — is not read at all.
No <main> (or role="main") means no "skip to content" target and a weaker landmark map. Wrap the primary content in <main>. — apps/web/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".
A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabIndex={0} + a key handler. (×5) — apps/web/src/features/applications/components/list-view.tsx:276, apps/web/src/features/applications/components/list-view.tsx:292, apps/web/src/features/resume/editor/check/check-panel.tsx:198, …
This <section> carries tabIndex={0}, so it is in the tab order and a keyboard user will land on it — but its only behaviour is bound to pointerdown, pointer gestures a keyboard cannot produce, and there is no key handler. The tab stop leads nowhere. Bind the same behaviour to a key handler, or provide an equivalent control elsewhere. Give it a role as well, so assistive tech can announce what it is. — apps/web/src/routes/builder/$resumeId/-components/page-canvas.tsx:87
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.
`.initial-loader__spinner` moves (`animation: app-spin 0.7s 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. — apps/web/index.html:85
<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). (×9) — apps/web/src/features/assistant/conversation.tsx:636, apps/web/src/features/career/coach.tsx:636, apps/web/src/features/career/knowledge/facts.tsx:127, …
<section> 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) — apps/web/src/routes/builder/$resumeId/-components/page-canvas.tsx:87, apps/web/src/routes/builder/letter/-components/letter-page.tsx:110
<span> moves — its `animate-[toast-fuse_linear_forwards]` 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:. — packages/ui/src/components/toast.tsx:28
`html:active-view-transition-type(page)::view-transition-new(root)` moves (`animation: var(--d2) var(--ease) both vt-page-in`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce. — apps/web/src/index.css:92
`html:active-view-transition-type(forward)::view-transition-new(root)` moves (`animation: var(--d2) var(--ease) both vt-push-in`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce. — apps/web/src/index.css:124
`html:active-view-transition-type(back)::view-transition-new(root)` moves (`animation: var(--d2) var(--ease) both vt-pop-in`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce. — apps/web/src/index.css:128
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 477 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 vitest-axe 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 the codebase has a recognisable, scale-appropriate structure (a named architectural style, or modular enough for its size) rather than being an ad-hoc ball of mud.
Method: Roslyn plus csproj analysis: architecture style detection (DDD, clean, vertical-slice, CQRS) and structure fitness for repo size. Deterministic.
Other · Architecture — Whether interfaces stay focused rather than fat — the Interface-Segregation principle (SOLID 'I').
Method: Roslyn scan: public interface declared-member counts (accessors fold into their property/event); fat-interface threshold (over 15 declared members) flagged per type. Each finding also reports the distinct-OPERATION count — members counted by name, so an overload group counts once — which decides whether it states the caller-side ISP harm or the implementer-side burden of an overload set. TypeScript: exported interfaces that declare behaviour, counted over their REQUIRED operations (method signatures and function-typed properties with no `?`, once per signature) — data-shape interfaces and ambient .d.ts declarations are outside the population; JavaScript declares no interfaces and is not applicable. Deterministic, type-level.
Other · Architecture — Whether feature slices stay independent (no direct cross-slice references) — the discipline that makes vertical-slice architecture pay off.
Method: Roslyn scan (vertical-slice gated): feature slices resolved from namespaces (.Features.*, .Slices.*) or project names; cross-slice type references detected. Deterministic, traceable.
`ApplicationDetail` (slice 'application-detail') depends on `useApplication` from slice 'applications'. — apps/mobile/src/features/application-detail/detail-screen.tsx:31
`ApplicationDetail` (slice 'application-detail') depends on `useApplicationMutations` from slice 'applications'. — apps/mobile/src/features/application-detail/detail-screen.tsx:32
`ApplicationDetail` (slice 'application-detail') depends on `syncReminders` from slice 'reminders'. — apps/mobile/src/features/application-detail/detail-screen.tsx:41
`ApplicationDetail` (slice 'application-detail') depends on `applicationError` from slice 'applications'. — apps/mobile/src/features/application-detail/detail-screen.tsx:59
`ApplicationDetail` (slice 'application-detail') depends on `getClosedReasonLabel` from slice 'applications'. — apps/mobile/src/features/application-detail/detail-screen.tsx:94
`useDetailMutations` (slice 'application-detail') depends on `useInvalidateApplications` from slice 'applications'. — apps/mobile/src/features/application-detail/hooks.ts:29
`interviewReminder` (slice 'application-detail') depends on `Application` from slice 'applications'. — apps/mobile/src/features/application-detail/hooks.ts:56
`interviewReminder` (slice 'application-detail') depends on `ReminderTarget` from slice 'reminders'. — apps/mobile/src/features/application-detail/hooks.ts:56
`useUserTime` (slice 'application-detail') depends on `useProfile` from slice 'settings'. — apps/mobile/src/features/application-detail/hooks.ts:114
`useUserTime` (slice 'application-detail') depends on `isTimeZone` from slice 'reminders'. — apps/mobile/src/features/application-detail/hooks.ts:116
`useUserTime` (slice 'application-detail') depends on `deviceTimeZone` from slice 'reminders'. — apps/mobile/src/features/application-detail/hooks.ts:116
`emptyDraft` (slice 'application-detail') depends on `zonedParts` from slice 'reminders'. — apps/mobile/src/features/application-detail/interview-sheet.tsx:77
`draftFrom` (slice 'application-detail') depends on `isTimeZone` from slice 'reminders'. — apps/mobile/src/features/application-detail/interview-sheet.tsx:88
`InterviewSheetProps` (slice 'application-detail') depends on `Application` from slice 'applications'. — apps/mobile/src/features/application-detail/interview-sheet.tsx:107
`InterviewForm` (slice 'application-detail') depends on `useInvalidateApplications` from slice 'applications'. — apps/mobile/src/features/application-detail/interview-sheet.tsx:127
`InterviewForm` (slice 'application-detail') depends on `useReminders` from slice 'reminders'. — apps/mobile/src/features/application-detail/interview-sheet.tsx:128
`InterviewForm` (slice 'application-detail') depends on `DEFAULT_LEAD` from slice 'reminders'. — apps/mobile/src/features/application-detail/interview-sheet.tsx:139
`InterviewForm` (slice 'application-detail') depends on `applicationDetailQueryKey` from slice 'applications'. — apps/mobile/src/features/application-detail/interview-sheet.tsx:231
`InterviewForm` (slice 'application-detail') depends on `holdReminder` from slice 'reminders'. — apps/mobile/src/features/application-detail/interview-sheet.tsx:237
`InterviewForm` (slice 'application-detail') depends on `releaseReminder` from slice 'reminders'. — apps/mobile/src/features/application-detail/interview-sheet.tsx:246
`InterviewForm` (slice 'application-detail') depends on `REMINDER_LEADS` from slice 'reminders'. — apps/mobile/src/features/application-detail/interview-sheet.tsx:479
`SectionProps` (slice 'application-detail') depends on `Application` from slice 'applications'. — apps/mobile/src/features/application-detail/sections.tsx:52
`StageStepper` (slice 'application-detail') depends on `useApplicationMutations` from slice 'applications'. — apps/mobile/src/features/application-detail/sections.tsx:75
`StageStepper` (slice 'application-detail') depends on `PIPELINE` from slice 'applications'. — apps/mobile/src/features/application-detail/sections.tsx:82
`StageStepper` (slice 'application-detail') depends on `getStageLabel` from slice 'applications'. — apps/mobile/src/features/application-detail/sections.tsx:91
`StageStepper` (slice 'application-detail') depends on `applicationError` from slice 'applications'. — apps/mobile/src/features/application-detail/sections.tsx:92
`StageStepper` (slice 'application-detail') depends on `getStageColor` from slice 'applications'. — apps/mobile/src/features/application-detail/sections.tsx:110
`NextStepCard` (slice 'application-detail') depends on `getNextStep` from slice 'applications'. — apps/mobile/src/features/application-detail/sections.tsx:156
`NextStepCard` (slice 'application-detail') depends on `describeNextStep` from slice 'applications'. — apps/mobile/src/features/application-detail/sections.tsx:157
`NextStepCard` (slice 'application-detail') depends on `shareIcs` from slice 'reminders'. — apps/mobile/src/features/application-detail/sections.tsx:183
`NextStepCard` (slice 'application-detail') depends on `interviewEvent` from slice 'reminders'. — apps/mobile/src/features/application-detail/sections.tsx:184
`NextStepCard` (slice 'application-detail') depends on `followUpEvent` from slice 'reminders'. — apps/mobile/src/features/application-detail/sections.tsx:184
`NextStepCard` (slice 'application-detail') depends on `icsFileName` from slice 'reminders'. — apps/mobile/src/features/application-detail/sections.tsx:185
`NextStepCard` (slice 'application-detail') depends on `zonedParts` from slice 'reminders'. — apps/mobile/src/features/application-detail/sections.tsx:185
`ApplicationSheetProps` (slice 'application-detail') depends on `Application` from slice 'applications'. — apps/mobile/src/features/application-detail/sheets.tsx:38
`CloseSheet` (slice 'application-detail') depends on `useApplicationMutations` from slice 'applications'. — apps/mobile/src/features/application-detail/sheets.tsx:46
`CloseSheet` (slice 'application-detail') depends on `applicationError` from slice 'applications'. — apps/mobile/src/features/application-detail/sheets.tsx:66
`CloseSheet` (slice 'application-detail') depends on `CLOSED_REASONS` from slice 'applications'. — apps/mobile/src/features/application-detail/sheets.tsx:75
`CloseSheet` (slice 'application-detail') depends on `getClosedReasonLabel` from slice 'applications'. — apps/mobile/src/features/application-detail/sheets.tsx:78
`FollowUpForm` (slice 'application-detail') depends on `useReminders` from slice 'reminders'. — apps/mobile/src/features/application-detail/sheets.tsx:199
What to do
Keep slices independent: share cross-slice needs via an explicit contract/shared-kernel, not direct references between slices.
Do you agree with this assessment?
C1 · Data Protection3.5 / 10Weak✓ Tool-verified
Other · Security — Whether sensitive data is encrypted at rest and in transit and keys are vaulted.
Method: Roslyn plus filesystem scan: encryption presence (EF ColumnEncryption, key-vault references, HTTPS enforcement) and key-derivation KDF detection. Deterministic.
What to do
Strengthen data-at-rest protection: vault your keys (AWS KMS / Secrets Manager, Azure Key Vault, GCP KMS / REDACTED Manager, HashiCorp Vault) and encrypt the most sensitive columns (typeorm-encrypted, prisma-field-encryption, mongoose-field-encryption or MongoDB CSFLE) — partial coverage still leaves gaps.
Enforce HTTPS (serve through https.createServer / NestJS httpsOptions, or redirect plain HTTP with express-sslify behind your TLS terminator) so data in transit is always encrypted.
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.
Do you agree with this assessment?
C4 · Data Retention10.0 / 10Exemplary✓ Tool-verified
Other · Security — Whether data has a defined lifetime — retention periods, TTLs, cleanup jobs (storage limitation).
Method: Roslyn scan: retention/TTL configuration presence in schema; CascadeDelete detected but not scored as retention control. Deterministic, gated by PII presence.
Other · Security — Whether GDPR data-subject requests are supported in code — erasure, export/portability, consent.
Method: Roslyn scan: GDPR data-subject-rights corroboration (erasure/export/consent vocabulary co-occurring with subject-id store crossing or explicit GDPR pattern). Deterministic, gated by PII.
Corroborated rights: erasure ✓ · export ✗ · consent ✗. Each tick means this scan found code in the repository implementing that right — a deletion/anonymisation path for erasure, a data-export or portability path for export, and consent state recorded alongside the personal data it authorises. A ✗ therefore means no such code was recognised HERE, not that the right is unsupported: a capability provided by a platform, a manual runbook, or code spelled in a way this scan does not match is not visible to it. Confirm before treating a cross as a gap; where it is one, the right has to be fulfilled manually.
What to do
Implement data export/portability for a data subject (a machine-readable export of their personal data).
Track GDPR consent (lawful basis) alongside the personal data it authorises.
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.
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.
`onRequestClose` is wired to an arrow whose body is empty — the markup attaches a listener that does nothing. Implement the handler, or remove the attribute that wires it. — apps/mobile/src/draft/conflict-sheet.tsx:39
Both arms of this conditional expression are the same, so no input can make the condition matter. Implement the distinction that was intended, or drop the condition. — apps/web/src/features/resume/editor/chrome.tsx:131
A bare `eslint-disable` or `@ts-nocheck` with no rule list switches every lint rule or the whole type checker off for the rest of the file — hidden debt. Disable the specific rule on the specific line, with a justification, instead. (×2) — apps/web/src/routeTree.gen.ts:1, apps/web/src/routeTree.gen.ts:3
A test is skipped/ignored — coverage that looks present but never runs. Re-enable it or delete it so the green run means something. (×3) — tests/e2e/specs/assistant.spec.ts:7, tests/e2e/specs/career.spec.ts:50, tests/e2e/specs/guest.spec.ts:5
What to do
Clear the softer debt: re-enable or delete skipped tests, decide whether each empty function is a deliberate no-op (and say so in a comment), and replace blanket `eslint-disable` / `@ts-nocheck` with targeted, justified suppressions.
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 an 'Architecture' / 'How it works' section to the root README — the high-level shape.
Add a README to the 27 of 29 project(s) that lack one — worth up to 1.9 pts.
Maturity · Maturity — Whether key decisions (ADRs) and the high-level shape (C4/diagrams) are written down.
Method: Filesystem scan: ADR folder/naming conventions or content, plus Mermaid/PlantUML/C4/architecture.md discovery. Exhaustive, deterministic.
No Architecture Decision Records found — no conventional ADR directory, no numbered `NNNN-title` documents in any markup this check reads, and nothing ADR-shaped by content. Design rationale recorded elsewhere (a design-notes tree, a mailing list, pull-request discussion) is not visible to this check and is not re-findable per decision, so a future maintainer cannot ask why one choice was made and get an answer.
What to do
Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them.
Maturity · Maturity — Whether the 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.
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 · Observability6.0 / 10Adequate✓ Tool-verified
Readiness · Readiness — Whether the code is diagnosable in production — structured logging, tracing/metrics, health checks.
Only 1/3 runnable modules use logging (modules with no entry point or server are excluded — they are libraries a runnable module hosts). Silent: `apps/mobile`, `tooling`.
What to do
Extend structured logging to the remaining runnable modules so everything you run is diagnosable in production.
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/typescript`, or eslint-plugin-security as a CI step. What was searched, so you can tell an absence from a miss: the 51954 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/typescript`, or eslint-plugin-security — so a security regression fails the build instead of landing.
Enable Dependabot/Renovate or a dependency-review gate.
Add gitleaks/trufflehog in CI to block PRs that introduce committed secrets.
Readiness · Readiness — Whether releases are automated and safely reversible (probes, rolling updates, approval gates) — from manifests/pipeline files, not the live environment.
Method: Filesystem scan: deployment manifests/IaC (K8s YAML, Helm, Terraform) for rolling updates, probes, approval gates, migration hooks. Exhaustive, deterministic.
Do you agree with this assessment?
P5 · DR & Backup4.0 / 10Weak✓ Tool-verified
Readiness · Readiness — Whether disaster recovery is planned and codified — backups, geo-recovery, RTO/RPO, persistence guarantees — from IaC + container manifests + docs, never the live cloud.
Method: Filesystem scan: disaster recovery, backup, geo-recovery, RTO/RPO, persistence guarantees from IaC, manifests, and docs. Exhaustive, deterministic, never a live environment.
What to do
Document RTO/RPO and a tested restore procedure (a backup config alone isn't disaster recovery).
Enable purge protection / soft-delete (and prevent_destroy on critical resources) so data stores can't be lost to an accidental or malicious delete.
Readiness · Readiness — Whether database schema changes go through versioned migrations rather than being auto-created from the model at startup.
Method: Roslyn scan: EF Core DbContext for a versioned migrations directory versus bare EnsureCreated usage; off .NET, a file scan of dependency manifests, migration histories (Flyway, Liquibase, Alembic, Django, Rails, Prisma, TypeORM, Knex/Sequelize, golang-migrate, goose, Laravel, Doctrine, Diesel/sqlx) and schema auto-create in production source or config. Exhaustive, deterministic.
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.
`unzipSync` in `detectImportKind` 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. — apps/web/src/features/resume/import/read-file.ts:78
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 Safety9.8 / 10Exemplary✓ Tool-verified
React / JS · Code Health — How much of the frontend is typed TypeScript vs untyped JavaScript.
Method: Frontend file inventory: the share of typed TypeScript vs untyped JavaScript across the source tree. Deterministic, exhaustive over frontend files.
What to do
Migrate the remaining .js/.jsx files to TypeScript.
React / JS · Code Health — Near-exact copy-pasted blocks of substantial extent across the frontend (the D4 clone algorithm over JS/TS tokens, D-386): a block is reported only where its copies still agree on most of their own identifiers and literals, or were renamed as they were pasted but kept most of their constants, and where the copies carry enough code to stand on their own or the copied extent reaches 30 lines — so a re-implementation sharing neither names nor values, and a small pasted declaration, are both found and deliberately not reported, and a clean R10 is not a claim that nothing was copied.
Method: Near-exact copy-pasted blocks of substantial extent across the frontend (the D4 clone algorithm run over JS/TS tokens). Masking finds the candidates; a block is reported when its copies still agree on most of their own identifiers and literals, or when a renamed copy still agrees on most of its constants, AND the copies carry enough code to stand on their own — or when the copied extent reaches 30 lines. So a re-implementation sharing neither names nor values, and a small pasted declaration, are deliberately not counted. Deterministic.
151 duplicated blocks under apps/ have copies in at least two of the sibling directories mobile, web — 114 of them are reported below, and 37 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 151 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 151 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 151 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. — apps/mobile/src/features/check/issues.ts:2
48 duplicated blocks under packages/pdf/src/templates/ have copies in at least two of the sibling directories azurill, bronzor, chikorita, ditgar, ditto, gengar (+13 more sibling(s) not listed) — 37 of them are reported below, and 11 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 48 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 48 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 48 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. — packages/pdf/src/templates/ditgar/DitgarPage.tsx:1
42 duplicated blocks under apps/web/src/features/ have copies in at least two of the sibling directories applications, assistant, ats-checker, career, command-palette, documents (+3 more sibling(s) not listed) — 17 of them are reported below, and 25 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 42 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 42 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 42 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. — apps/web/src/features/assistant/assistant-panel.tsx:150
39 duplicated blocks under apps/mobile/src/features/ have copies in at least two of the sibling directories ai, application-detail, applications, applications-board, assistant, ats-checker (+13 more sibling(s) not listed) — 22 of them are reported below, and 17 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 39 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 39 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 39 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. — apps/mobile/src/features/letters/rich-text-field.tsx:16
34 duplicated blocks under apps/web/src/ have copies in at least two of the sibling directories components, dialogs, features, routes — 19 of them are reported below, and 15 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 34 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 34 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 34 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. — apps/web/src/features/letters/use-letter-mode.ts:31
26 duplicated blocks under packages/api/src/features/ have copies in at least two of the sibling directories agent, ai-providers, applications, auth, career, cover-letters (+3 more sibling(s) not listed) — 8 of them are reported below, and 18 are counted here but not reported individually: those copies match on shape but no longer clear R10's bar for an individually reported row — either they kept neither their own names nor their values, or what was copied is too small to stand on its own (it reports near-exact duplication only, and only of substantial extent). What this row states is the concentration, which the detector measured over all 26 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 26 local ones: the siblings replicate behaviour none of them owns, which is the shape of a missing shared module — a common library every sibling imports — rather than 26 separate extractions. Check first whether the siblings are deliberately standalone deliverables (scaffold templates, demo apps that must stay copy-pasteable); where they are, the duplication is the design and the per-block rows are the ones to act on. — packages/api/src/features/cover-letters/versions.ts:25
22 duplicated blocks under packages/ have copies in at least two of the sibling directories ai, api, auth, docx, env, forme-native (+6 more sibling(s) not listed) — 15 of them are reported below, and 7 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 22 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 22 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 22 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. — packages/docx/src/html-to-docx.ts:54
17 duplicated blocks under the repository root have copies in at least two of the sibling directories apps, packages, tooling — 9 of them are reported below, and 8 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 17 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 17 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 17 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. — apps/web/src/features/applications/csv.ts:17
10 duplicated blocks under apps/mobile/src/ have copies in at least two of the sibling directories draft, features, i18n, preview, shell, ui — 3 of them are reported below, and 7 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 10 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 10 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 10 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. — apps/mobile/src/features/letters/page.tsx:58
8 duplicated blocks under apps/mobile/ have copies in at least two of the sibling directories app, src — 4 of them are reported below, and 4 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 8 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 8 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 8 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. — apps/mobile/app/_layout.tsx:102
5 duplicated blocks under apps/web/src/routes/builder/ have copies in at least two of the sibling directories $resumeId, letter — 4 of them are reported below, and 1 is 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 5 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 5 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 5 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. — apps/web/src/routes/builder/$resumeId/-components/editor-shell.tsx:30
apps/mobile/src/features/check/issues.ts:2 · apps/web/src/features/resume/editor/check/issues.ts:1 — these 2 files are line-for-line copies of one another — 244 lines are identical, in the same order, in every one of them — so this is one fact about the file set, not a block to extract. An edit made to one file and not the others changes behaviour silently, which is the failure a wholesale copy guarantees. Pick one file as the single source and derive the others from it (re-export it, spread it into the local overrides each variant genuinely needs, or generate the copies at build time) — the few lines that differ between the files are exactly the part each variant should still own. Check first whether the copies are deliberately standalone deliverables (a translation file seeded from its sibling and waiting to be translated); where they are, the duplication is the design, and the honest move is to mark the seeded file as untranslated rather than to let it pass as done. — apps/mobile/src/features/check/issues.ts:2
packages/pdf/src/templates/ditgar/DitgarPage.tsx:1 · packages/pdf/src/templates/gengar/GengarPage.tsx:1 — these 2 files are line-for-line copies of one another — 206 lines are identical, in the same order, in every one of them — so this is one fact about the file set, not a block to extract. An edit made to one file and not the others changes behaviour silently, which is the failure a wholesale copy guarantees. Pick one file as the single source and derive the others from it (re-export it, spread it into the local overrides each variant genuinely needs, or generate the copies at build time) — the few lines that differ between the files are exactly the part each variant should still own. Check first whether the copies are deliberately standalone deliverables (a translation file seeded from its sibling and waiting to be translated); where they are, the duplication is the design, and the honest move is to mark the seeded file as untranslated rather than to let it pass as done. — packages/pdf/src/templates/ditgar/DitgarPage.tsx:1
apps/mobile/src/features/workspace/tabs/debrief.tsx:37 · apps/web/src/features/career/workspace/debrief.tsx:52 — the two spans are one implementation copied and then locally edited — 1260 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. — apps/mobile/src/features/workspace/tabs/debrief.tsx:37
apps/mobile/src/features/workspace/tabs/saved.tsx:25 · apps/web/src/features/career/workspace/saved.tsx:22 — the two spans are one implementation copied and then locally edited — 1278 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. — apps/mobile/src/features/workspace/tabs/saved.tsx:25
apps/mobile/src/features/workspace/tabs/messages.tsx:40 · apps/web/src/features/career/workspace/messages.tsx:36 — the two spans are one implementation copied and then locally edited — 1091 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. — apps/mobile/src/features/workspace/tabs/messages.tsx:40
apps/mobile/src/features/letters/rich-text-field.tsx:16 · apps/mobile/src/features/write/rich-text-field.tsx:23 — the two spans are one implementation copied and then locally edited — 936 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. — apps/mobile/src/features/letters/rich-text-field.tsx:16
apps/mobile/src/features/ai/catalog.ts:53 · apps/web/src/features/settings/ai/catalog.ts:71 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — apps/mobile/src/features/ai/catalog.ts:53
apps/mobile/src/features/workspace/tabs/fit.tsx:82 · apps/web/src/features/career/workspace/fit.tsx:124 — the two spans are one implementation copied and then locally edited — 849 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. — apps/mobile/src/features/workspace/tabs/fit.tsx:82
packages/pdf/src/templates/lapras/LaprasPage.tsx:17 · packages/pdf/src/templates/onyx/OnyxPage.tsx:17 — the two spans are one implementation copied and then locally edited — 816 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. — packages/pdf/src/templates/lapras/LaprasPage.tsx:17
apps/web/src/features/assistant/assistant-panel.tsx:150 · apps/web/src/features/career/coach.tsx:320 — the two spans are one implementation copied and then locally edited — 550 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. — apps/web/src/features/assistant/assistant-panel.tsx:150
packages/docx/src/html-to-docx.ts:54 · packages/odt/src/html-to-odt.ts:12 — the two spans are one implementation copied and then locally edited — 704 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. — packages/docx/src/html-to-docx.ts:54
apps/web/src/dialogs/auth/disable-two-factor.tsx:27 · apps/web/src/dialogs/auth/enable-two-factor.tsx:33 — the two spans are one implementation copied and then locally edited — 476 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. — apps/web/src/dialogs/auth/disable-two-factor.tsx:27
apps/mobile/src/features/workspace/hooks.ts:60 · apps/web/src/features/career/hooks.ts:73 — the two spans are one implementation copied and then locally edited — 671 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. — apps/mobile/src/features/workspace/hooks.ts:60
apps/web/src/features/assistant/conversation.tsx:272 · apps/web/src/features/career/coach-chat.tsx:217 — the two spans are one implementation copied and then locally edited — 414 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. — apps/web/src/features/assistant/conversation.tsx:272
apps/mobile/src/features/applications/next-step.ts:1 · apps/web/src/features/applications/next-step.ts:1 — these 2 files are line-for-line copies of one another — 83 lines are identical, in the same order, in every one of them — so this is one fact about the file set, not a block to extract. An edit made to one file and not the others changes behaviour silently, which is the failure a wholesale copy guarantees. Pick one file as the single source and derive the others from it (re-export it, spread it into the local overrides each variant genuinely needs, or generate the copies at build time) — the few lines that differ between the files are exactly the part each variant should still own. Check first whether the copies are deliberately standalone deliverables (a translation file seeded from its sibling and waiting to be translated); where they are, the duplication is the design, and the honest move is to mark the seeded file as untranslated rather than to let it pass as done. — apps/mobile/src/features/applications/next-step.ts:1
packages/ui/src/components/dialog.tsx:7 · packages/ui/src/components/sheet.tsx:7 — the two spans are one implementation copied and then locally edited — 461 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. — packages/ui/src/components/dialog.tsx:7
apps/mobile/src/features/history/history.tsx:64 · apps/mobile/src/features/letters/share.tsx:285 — the two spans are one implementation copied and then locally edited — 685 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. — apps/mobile/src/features/history/history.tsx:64
apps/web/src/features/auth/pages/forgot-password.tsx:49 · apps/web/src/features/auth/pages/register.tsx:96 — the two spans are one implementation copied and then locally edited — 434 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. — apps/web/src/features/auth/pages/forgot-password.tsx:49
apps/mobile/src/features/history/history.tsx:181 · apps/mobile/src/features/letters/share.tsx:390 — the two spans are one implementation copied and then locally edited — 494 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. — apps/mobile/src/features/history/history.tsx:181
apps/mobile/src/features/workspace/logic.ts:268 · apps/web/src/features/career/workspace/recorder.ts:202 — the 2 copies are spread across 2 directories, so the shared home is a decision rather than an obvious spot: check first whether one of them already owns this behaviour, and otherwise put the extracted module somewhere all of the sites already reach rather than making one of them depend on another. — apps/mobile/src/features/workspace/logic.ts:268
apps/mobile/src/features/applications-board/insights.ts:21 · apps/web/src/features/applications/insights.ts:100 — the two spans are one implementation copied and then locally edited — 620 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. — apps/mobile/src/features/applications-board/insights.ts:21
apps/mobile/src/features/letters/page.tsx:58 · apps/mobile/src/preview/page.tsx:127 — the two spans are one implementation copied and then locally edited — 399 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. — apps/mobile/src/features/letters/page.tsx:58
apps/web/src/features/assistant/conversation.tsx:695 · apps/web/src/features/career/coach-thread.tsx:359 — the two spans are one implementation copied and then locally edited — 330 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. — apps/web/src/features/assistant/conversation.tsx:695
packages/pdf/src/templates/porygon/PorygonPage.tsx:33 · packages/pdf/src/templates/scizor/ScizorPage.tsx:33 — the 2 copies are spread across 2 directories, so the shared home is a decision rather than an obvious spot: check first whether one of them already owns this behaviour, and otherwise put the extracted module somewhere all of the sites already reach rather than making one of them depend on another. — packages/pdf/src/templates/porygon/PorygonPage.tsx:33
apps/mobile/src/features/assistant/coach-screen.tsx:73 · apps/mobile/src/features/workspace/coach-sheet.tsx:41 — the two spans are one implementation copied and then locally edited — 306 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. — apps/mobile/src/features/assistant/coach-screen.tsx:73
apps/mobile/src/features/write/model.ts:39 · apps/web/src/features/resume/editor/write/model.ts:19 — the 2 copies are spread across 2 directories, so the shared home is a decision rather than an obvious spot: check first whether one of them already owns this behaviour, and otherwise put the extracted module somewhere all of the sites already reach rather than making one of them depend on another. — apps/mobile/src/features/write/model.ts:39
packages/db/src/schema/auth.ts:61 · packages/db/src/schema/auth.ts:383 — the two spans are one implementation copied and then locally edited — 411 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. — packages/db/src/schema/auth.ts:61
apps/mobile/src/features/application-detail/interview-sheet.tsx:90 · apps/web/src/features/applications/components/interview-dialog.tsx:111 — the two spans are one implementation copied and then locally edited — 372 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. — apps/mobile/src/features/application-detail/interview-sheet.tsx:90
apps/mobile/src/features/write/model.ts:104 · apps/web/src/features/resume/editor/write/model.ts:88 — the 2 copies are spread across 2 files, and the SHAPE of this repetition could not be determined. It is not a run of declarations, a listing, a declaration header, a type body or a slice through a construct — and it was not measured as a run of executable statements either, so this row cannot tell you whether a function can stand where these lines are. Read the two spans before acting, because the move is opposite in the two cases. Where they are statements, the ordinary answer holds: give the shared part one home and call it from each site. Where they turn out to be declarations, a literal's entries, or the cases of an enumeration, there is no call site to call anything from, and collapsing them would delete what each copy pins — a shared base type, a generated set, or one exported constant each site refers to is the move instead, and sometimes the honest answer is that there is nothing to extract at all. Reported because the copies drift apart the first time only one of them is edited, which is true whichever of those they are. — apps/mobile/src/features/write/model.ts:104
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.
apps/mobile/scripts/parity/device.ts:8 reaches into another package with a relative path (../../modules/pdf-pages) — import the package by name instead. — apps/mobile/scripts/parity/device.ts:8
apps/mobile/scripts/parity/host.mts:19 reaches into another package with a relative path (../../../web/public/photos/sample-picture.jpg) — import the package by name instead. — apps/mobile/scripts/parity/host.mts:19
apps/mobile/scripts/parity/review.ts:4 reaches into another package with a relative path (../../modules/pdf-pages) — import the package by name instead. — apps/mobile/scripts/parity/review.ts:4
apps/mobile/src/features/ats-checker/original-page.tsx:1 reaches into another package with a relative path (../../../modules/pdf-pages) — import the package by name instead. — apps/mobile/src/features/ats-checker/original-page.tsx:1
apps/mobile/src/features/ats-checker/original-page.tsx:7 reaches into another package with a relative path (../../../modules/pdf-pages) — import the package by name instead. — apps/mobile/src/features/ats-checker/original-page.tsx:7
apps/mobile/src/preview/pipeline.ts:1 reaches into another package with a relative path (../../modules/pdf-pages) — import the package by name instead. — apps/mobile/src/preview/pipeline.ts:1
apps/mobile/src/preview/pipeline.ts:5 reaches into another package with a relative path (../../modules/pdf-pages) — import the package by name instead. — apps/mobile/src/preview/pipeline.ts:5
apps/mobile/src/shell/key-commands.ts:1 reaches into another package with a relative path (../../modules/key-commands) — import the package by name instead. — apps/mobile/src/shell/key-commands.ts:1
apps/mobile/src/shell/key-commands.ts:4 reaches into another package with a relative path (../../modules/key-commands) — import the package by name instead. — apps/mobile/src/shell/key-commands.ts:4
apps/mobile/src/ui/icon.tsx:4 imports phosphor-react-native/src/icons/ArrowClockwise, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead. — apps/mobile/src/ui/icon.tsx:4
apps/mobile/src/ui/icon.tsx:5 imports phosphor-react-native/src/icons/ArrowCounterClockwise, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead. — apps/mobile/src/ui/icon.tsx:5
apps/mobile/src/ui/icon.tsx:6 imports phosphor-react-native/src/icons/ArrowDown, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead. — apps/mobile/src/ui/icon.tsx:6
apps/mobile/src/ui/icon.tsx:7 imports phosphor-react-native/src/icons/ArrowLeft, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead. — apps/mobile/src/ui/icon.tsx:7
apps/mobile/src/ui/icon.tsx:8 imports phosphor-react-native/src/icons/ArrowRight, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead. — apps/mobile/src/ui/icon.tsx:8
apps/mobile/src/ui/icon.tsx:9 imports phosphor-react-native/src/icons/ArrowsClockwise, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead. — apps/mobile/src/ui/icon.tsx:9
apps/mobile/src/ui/icon.tsx:10 imports phosphor-react-native/src/icons/ArrowsDownUp, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead. — apps/mobile/src/ui/icon.tsx:10
apps/mobile/src/ui/icon.tsx:11 imports phosphor-react-native/src/icons/ArrowsInLineVertical, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead. — apps/mobile/src/ui/icon.tsx:11
apps/mobile/src/ui/icon.tsx:12 imports phosphor-react-native/src/icons/ArrowsInSimple, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead. — apps/mobile/src/ui/icon.tsx:12
apps/mobile/src/ui/icon.tsx:13 imports phosphor-react-native/src/icons/ArrowsLeftRight, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead. — apps/mobile/src/ui/icon.tsx:13
apps/mobile/src/ui/icon.tsx:14 imports phosphor-react-native/src/icons/ArrowsOutSimple, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead. — apps/mobile/src/ui/icon.tsx:14
apps/mobile/src/ui/icon.tsx:15 imports phosphor-react-native/src/icons/ArrowSquareOut, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead. — apps/mobile/src/ui/icon.tsx:15
apps/mobile/src/ui/icon.tsx:16 imports phosphor-react-native/src/icons/ArrowUp, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead. — apps/mobile/src/ui/icon.tsx:16
apps/mobile/src/ui/icon.tsx:17 imports phosphor-react-native/src/icons/ArrowUpRight, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead. — apps/mobile/src/ui/icon.tsx:17
apps/mobile/src/ui/icon.tsx:18 imports phosphor-react-native/src/icons/ArrowUUpLeft, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead. — apps/mobile/src/ui/icon.tsx:18
apps/mobile/src/ui/icon.tsx:19 imports phosphor-react-native/src/icons/ArrowUUpRight, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead. — apps/mobile/src/ui/icon.tsx:19
apps/mobile/src/ui/icon.tsx:20 imports phosphor-react-native/src/icons/Bell, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead. — apps/mobile/src/ui/icon.tsx:20
apps/mobile/src/ui/icon.tsx:21 imports phosphor-react-native/src/icons/BookmarkSimple, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead. — apps/mobile/src/ui/icon.tsx:21
apps/mobile/src/ui/icon.tsx:22 imports phosphor-react-native/src/icons/BookOpen, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead. — apps/mobile/src/ui/icon.tsx:22
apps/mobile/src/ui/icon.tsx:23 imports phosphor-react-native/src/icons/BookOpenText, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead. — apps/mobile/src/ui/icon.tsx:23
apps/mobile/src/ui/icon.tsx:24 imports phosphor-react-native/src/icons/Books, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead. — apps/mobile/src/ui/icon.tsx:24
apps/mobile/src/ui/icon.tsx:25 imports phosphor-react-native/src/icons/BracketsCurly, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead. — apps/mobile/src/ui/icon.tsx:25
apps/mobile/src/ui/icon.tsx:26 imports phosphor-react-native/src/icons/Brain, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead. — apps/mobile/src/ui/icon.tsx:26
apps/mobile/src/ui/icon.tsx:27 imports phosphor-react-native/src/icons/Briefcase, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead. — apps/mobile/src/ui/icon.tsx:27
apps/mobile/src/ui/icon.tsx:28 imports phosphor-react-native/src/icons/Bug, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead. — apps/mobile/src/ui/icon.tsx:28
apps/mobile/src/ui/icon.tsx:29 imports phosphor-react-native/src/icons/CalendarBlank, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead. — apps/mobile/src/ui/icon.tsx:29
apps/mobile/src/ui/icon.tsx:30 imports phosphor-react-native/src/icons/CalendarDot, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead. — apps/mobile/src/ui/icon.tsx:30
apps/mobile/src/ui/icon.tsx:31 imports phosphor-react-native/src/icons/CalendarDots, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead. — apps/mobile/src/ui/icon.tsx:31
apps/mobile/src/ui/icon.tsx:32 imports phosphor-react-native/src/icons/CalendarPlus, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead. — apps/mobile/src/ui/icon.tsx:32
apps/mobile/src/ui/icon.tsx:33 imports phosphor-react-native/src/icons/Camera, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead. — apps/mobile/src/ui/icon.tsx:33
apps/mobile/src/ui/icon.tsx:34 imports phosphor-react-native/src/icons/CameraPlus, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead. — apps/mobile/src/ui/icon.tsx:34
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.
resolveStylesheet has cyclomatic complexity 90 and cognitive complexity 216; 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. — packages/resume/src/stylesheet/cascade.ts:554
ScheduleSheet has cyclomatic complexity 72 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. — apps/web/src/features/career/schedule-sheet.tsx:129
AddApplicationSheet has cyclomatic complexity 72 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 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. — apps/mobile/src/features/applications/add-sheet.tsx:48
parseDeepLink has cyclomatic complexity 65 and cognitive complexity 84; 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. — apps/mobile/src/linking/parse.ts:39
toFormeStyle has cyclomatic complexity 64 and cognitive complexity 127; 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. — packages/pdf/src/forme/style.ts:373
convertNode has cyclomatic complexity 63 and cognitive complexity 97; 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. — packages/pdf/src/forme/to-forme.tsx:466
DocumentsLibrary has cyclomatic complexity 58 and cognitive complexity 54; 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. — apps/mobile/src/features/documents/library.tsx:159
parseReactiveResumeV4JSON has cyclomatic complexity 53 and cognitive complexity 56; 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. — packages/import/src/reactive-resume-v4-json.tsx:241
NewDocument has cyclomatic complexity 51 and cognitive complexity 44; 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. — apps/mobile/src/features/documents/new-document.tsx:24
send has cyclomatic complexity 50 and cognitive complexity 57; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — packages/api/src/features/agent/service.ts:1117
ApplicationsList has cyclomatic complexity 49 and cognitive complexity 43; 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. — apps/mobile/src/features/applications/list-screen.tsx:55
Session has cyclomatic complexity 48 and cognitive complexity 42; 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. — apps/web/src/features/career/workspace/practise.tsx:218
WebAccessSection has cyclomatic complexity 48 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. — apps/web/src/features/settings/ai/web-access.tsx:30
processBlockElement has cyclomatic complexity 47 and cognitive complexity 96; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — packages/docx/src/html-to-docx.ts:149
CoachPage has cyclomatic complexity 46 and cognitive complexity 46; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — apps/web/src/features/career/coach.tsx:104
ProviderForm has cyclomatic complexity 43 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. — apps/mobile/src/features/ai/provider-editor.tsx:75
Session has cyclomatic complexity 43 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. — apps/mobile/src/features/workspace/tabs/practise.tsx:185
ContextColumn has cyclomatic complexity 43 and cognitive complexity 37; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive 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. — apps/web/src/features/career/workspace/shell.tsx:465
ToolPartView has cyclomatic complexity 42 and cognitive complexity 54; 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. — apps/mobile/src/features/assistant/messages.tsx:201
What to do
Break down the listed branch-heavy functions; aim P95 cyclomatic ≤ 5.
Do you agree with this assessment?
R3 · Large Files6.6 / 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.
packages/api/src/features/agent/service.ts has 1582 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — packages/api/src/features/agent/service.ts:1
packages/pdf/src/templates/shared/sections.tsx has 1399 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — packages/pdf/src/templates/shared/sections.tsx:1
apps/web/src/routeTree.gen.ts has 1126 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — apps/web/src/routeTree.gen.ts:1
packages/api/src/features/career/service.ts has 1117 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — packages/api/src/features/career/service.ts:1
apps/web/src/features/career/workspace/practise.tsx has 1030 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — apps/web/src/features/career/workspace/practise.tsx:1
packages/pdf/src/forme/to-forme.tsx has 978 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — packages/pdf/src/forme/to-forme.tsx:1
packages/pdf/src/semantic/tree.ts has 918 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — packages/pdf/src/semantic/tree.ts:1
apps/web/src/features/assistant/conversation.tsx has 843 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — apps/web/src/features/assistant/conversation.tsx:1
apps/mobile/src/features/assistant/chat-view.tsx has 839 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — apps/mobile/src/features/assistant/chat-view.tsx:1
packages/resume/src/stylesheet/cascade.ts has 838 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — packages/resume/src/stylesheet/cascade.ts:1
packages/api/src/features/applications/service.ts has 810 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — packages/api/src/features/applications/service.ts:1
apps/mobile/src/features/application-detail/sections.tsx has 805 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — apps/mobile/src/features/application-detail/sections.tsx:1
apps/web/src/features/career/today.tsx has 787 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — apps/web/src/features/career/today.tsx:1
apps/web/src/features/resume/editor/write/picture-settings.tsx has 762 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — apps/web/src/features/resume/editor/write/picture-settings.tsx:1
packages/schema/src/resume/data.ts has 755 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — packages/schema/src/resume/data.ts:1
packages/mcp/src/tool-meta.ts has 747 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — packages/mcp/src/tool-meta.ts:1
apps/mobile/src/features/workspace/tabs/practise.tsx has 739 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — apps/mobile/src/features/workspace/tabs/practise.tsx:1
apps/mobile/src/features/letters/write.tsx has 726 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — apps/mobile/src/features/letters/write.tsx:1
packages/api/src/features/resume/service.ts has 719 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — packages/api/src/features/resume/service.ts:1
apps/web/src/features/resume/builder/draft.ts has 704 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — apps/web/src/features/resume/builder/draft.ts:1
apps/web/src/features/homepage/prepare.tsx has 687 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — apps/web/src/features/homepage/prepare.tsx:1
apps/web/src/features/settings/ai/providers.tsx has 680 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — apps/web/src/features/settings/ai/providers.tsx:1
apps/web/src/features/career/coach-chat.tsx has 676 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — apps/web/src/features/career/coach-chat.tsx:1
apps/web/src/features/career/coach.tsx has 674 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — apps/web/src/features/career/coach.tsx:1
apps/mobile/src/ui/overlays.tsx has 669 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — apps/mobile/src/ui/overlays.tsx:1
apps/web/src/routes/builder/letter/-components/write-panel.tsx has 664 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — apps/web/src/routes/builder/letter/-components/write-panel.tsx:1
packages/auth/src/config.ts has 662 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — packages/auth/src/config.ts:1
apps/web/src/features/applications/components/application-detail-sheet.tsx has 647 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — apps/web/src/features/applications/components/application-detail-sheet.tsx:1
apps/web/src/features/career/workspace/shell.tsx has 637 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — apps/web/src/features/career/workspace/shell.tsx:1
packages/resume/src/stylesheet/values.ts has 637 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — packages/resume/src/stylesheet/values.ts:1
packages/api/src/features/career/jobs.ts has 635 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — packages/api/src/features/career/jobs.ts:1
apps/web/src/features/career/workspace/prepare.tsx has 629 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — apps/web/src/features/career/workspace/prepare.tsx:1
apps/web/src/features/career/workspace/apply.tsx has 626 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — apps/web/src/features/career/workspace/apply.tsx:1
apps/mobile/src/features/write/outline.tsx has 623 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — apps/mobile/src/features/write/outline.tsx:1
apps/web/src/features/documents/new-document-dialog.tsx has 611 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — apps/web/src/features/documents/new-document-dialog.tsx:1
apps/mobile/src/features/applications-board/board-screen.tsx has 610 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — apps/mobile/src/features/applications-board/board-screen.tsx:1
apps/mobile/src/features/documents/library.tsx has 605 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — apps/mobile/src/features/documents/library.tsx:1
apps/web/src/features/career/schedule-sheet.tsx has 601 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — apps/web/src/features/career/schedule-sheet.tsx:1
apps/mobile/app/dev/ui.tsx has 594 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — apps/mobile/app/dev/ui.tsx:1
apps/web/src/features/documents/documents-page.tsx has 592 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — apps/web/src/features/documents/documents-page.tsx: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 Coverage6.4 / 10Adequate✓ 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.
apps/server/src/static/agent-skills.test.ts:8 imports '../../../../plugins/reactive-resume/skills', which names no file in this repository — and no rule in its .gitignore chain could cover one, so no build writes it either. The import throws as the runner collects this file, so none of its test cases run and nothing it was written to verify is verified. Restore the missing module or delete the test. It is excluded from the reachability measured above, because a file that cannot load reaches nothing. — apps/server/src/static/agent-skills.test.ts:8
packages/api/src/features/career/jobs.integration.test.ts:97 imports '../../../../../migrations/', which names no file in this repository — and no rule in its .gitignore chain could cover one, so no build writes it either. The import throws as the runner collects this file, so none of its test cases run and nothing it was written to verify is verified. Restore the missing module or delete the test. It is excluded from the reachability measured above, because a file that cannot load reaches nothing. — packages/api/src/features/career/jobs.integration.test.ts:97
packages/api/src/features/career/service.integration.test.ts:95 imports '../../../../../migrations/', which names no file in this repository — and no rule in its .gitignore chain could cover one, so no build writes it either. The import throws as the runner collects this file, so none of its test cases run and nothing it was written to verify is verified. Restore the missing module or delete the test. It is excluded from the reachability measured above, because a file that cannot load reaches nothing. — packages/api/src/features/career/service.integration.test.ts:95
packages/db/src/migrations.integration.test.ts:14 imports '../../../migrations', which names no file in this repository — and no rule in its .gitignore chain could cover one, so no build writes it either. The import throws as the runner collects this file, so none of its test cases run and nothing it was written to verify is verified. Restore the missing module or delete the test. It is excluded from the reachability measured above, because a file that cannot load reaches nothing. — packages/db/src/migrations.integration.test.ts:14
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. (×36) — apps/mobile/src/features/assistant/chat-view.tsx:1, apps/web/src/features/career/today.tsx:1, apps/web/src/features/resume/editor/write/picture-settings.tsx:1, …
What to do
Add tests that import the unreached modules (directly or through their public entry).
Do you agree with this assessment?
R6 · Tooling10.0 / 10Exemplary✓ Tool-verified
React / JS · Readiness — Whether the project wires up test, lint and typecheck — detected from each package.json script's COMMAND (eslint / tsc / vitest / jest / playwright), not just its name, and corroborated against CI-workflow invocations so a tool run only in CI still counts.
Method: package.json scanned for test/lint/typecheck script wiring. Deterministic presence check.
This repository declares test tooling, and the ✓ above records that declaration — but apps/server/src/static/agent-skills.test.ts and 3 other test file(s) in this workspace cannot be loaded at all: it imports a module that names no file in this repository, so the runner throws while collecting it and none of its cases execute. The wiring is present and the suite it points at does not run as written, which is why the tooling tick must not be read as a statement that the tests pass. Fix the unloadable file(s) — each one is reported with its failing import under Test Coverage — then the declared script exercises what it claims to. — apps/server/src/static/agent-skills.test.ts:8
Do you agree with this assessment?
R7 · Dead Code2.2 / 10Critical✓ 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 277 application, 56 tooling and 375 test entry point(s) detected in this repo. Gate removals on `pnpm run build` — an undetected custom entry would make these reachable.
no import path from any entry point (277 application, 56 tooling, 375 test roots considered), but 3 in-repo import(s) from 3 other file(s) do name it (apps/mobile/src/features/assistant/assistant-screen.tsx, apps/mobile/src/features/assistant/coach-screen.tsx, apps/mobile/src/features/workspace/coach-sheet.tsx) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it — apps/mobile/src/features/assistant/chat-view.tsx
no import path from any entry point (277 application, 56 tooling, 375 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (apps/mobile/src/features/application-detail/detail-screen.tsx) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it — apps/mobile/src/features/application-detail/sections.tsx
no import path from any entry point (277 application, 56 tooling, 375 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (apps/mobile/app/applications/[id]/[tab].tsx) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it (×4) — apps/mobile/src/features/workspace/tabs/practise.tsx, apps/mobile/src/features/workspace/tabs/apply.tsx, apps/mobile/src/features/workspace/tabs/prepare.tsx, …
no import path from any entry point (277 application, 56 tooling, 375 test roots considered), but 2 in-repo import(s) from 2 other file(s) do name it (apps/mobile/app/letter/[id]/write.tsx, apps/mobile/src/features/letters/design.tsx) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it — apps/mobile/src/features/letters/write.tsx
no import path from any entry point (277 application, 56 tooling, 375 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (apps/mobile/app/builder/[id]/write.tsx) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it — apps/mobile/src/features/write/outline.tsx
no import path from any entry point (277 application, 56 tooling, 375 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (apps/mobile/app/(tabs)/applications/board.tsx) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it — apps/mobile/src/features/applications-board/board-screen.tsx
no import path from any entry point (277 application, 56 tooling, 375 test roots considered), but 2 in-repo import(s) from 1 other file(s) do name it (apps/mobile/src/features/assistant/chat-view.tsx) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it — apps/mobile/src/features/assistant/messages.tsx
no import path from any entry point (277 application, 56 tooling, 375 test roots considered), but 2 in-repo import(s) from 2 other file(s) do name it (apps/mobile/app/(tabs)/documents/index.tsx, apps/mobile/app/(tabs)/documents/trash.tsx) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it — apps/mobile/src/features/documents/library.tsx
no import path from any entry point (277 application, 56 tooling, 375 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (apps/mobile/app/ats-checker.tsx) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it — apps/mobile/src/features/ats-checker/checker.tsx
no import path from any entry point (277 application, 56 tooling, 375 test roots considered), but 2 in-repo import(s) from 1 other file(s) do name it (apps/mobile/src/features/design/design-pane.tsx) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it — apps/mobile/src/features/design/advanced.tsx
no import path from any entry point (277 application, 56 tooling, 375 test roots considered), but 2 in-repo import(s) from 2 other file(s) do name it (apps/mobile/src/features/applications-board/views.tsx, apps/mobile/src/features/applications/list-screen.tsx) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it — apps/mobile/src/features/applications/add-sheet.tsx
no import path from any entry point (277 application, 56 tooling, 375 test roots considered), but 4 in-repo import(s) from 4 other file(s) do name it (apps/mobile/src/features/application-detail/detail-screen.tsx, apps/mobile/src/features/application-detail/sections.tsx, apps/mobile/src/features/applications-board/board-screen.tsx and 1 more) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it — apps/mobile/src/features/application-detail/sheets.tsx
no import path from any entry point (277 application, 56 tooling, 375 test roots considered), but 12 in-repo import(s) from 7 other file(s) do name it (apps/mobile/src/features/write/entry-fields.tsx, apps/mobile/src/features/write/entry-screen.tsx, apps/mobile/src/features/write/entry-sheet.tsx and 4 more) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it — apps/mobile/src/features/write/model.ts
no import path from any entry point (277 application, 56 tooling, 375 test roots considered), but 2 in-repo import(s) from 2 other file(s) do name it (apps/mobile/app/(tabs)/_layout.tsx, apps/mobile/src/shell/builder-chrome.tsx) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it — apps/mobile/src/shell/app-tabs.tsx
no import path from any entry point (277 application, 56 tooling, 375 test roots considered), but 3 in-repo import(s) from 3 other file(s) do name it (apps/mobile/src/features/application-detail/detail-screen.tsx, apps/mobile/src/features/applications-board/calendar-screen.tsx, apps/mobile/src/features/workspace/shell.tsx) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it — apps/mobile/src/features/application-detail/interview-sheet.tsx
no import path from any entry point (277 application, 56 tooling, 375 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (apps/mobile/app/letter/[id]/_layout.tsx) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it — apps/mobile/src/features/letters/share.tsx
no import path from any entry point (277 application, 56 tooling, 375 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (apps/mobile/app/(tabs)/applications/index.tsx) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it — apps/mobile/src/features/applications/list-screen.tsx
no import path from any entry point (277 application, 56 tooling, 375 test roots considered), but 2 in-repo import(s) from 2 other file(s) do name it (apps/mobile/src/features/write/basics-screen.tsx, apps/mobile/src/features/write/entry-screen.tsx) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it — apps/mobile/src/features/write/entry-fields.tsx
no import path from any entry point (277 application, 56 tooling, 375 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (apps/mobile/app/new.tsx) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it — apps/mobile/src/features/documents/new-document.tsx
no import path from any entry point (277 application, 56 tooling, 375 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (apps/mobile/app/(tabs)/applications/insights.tsx) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it — apps/mobile/src/features/applications-board/insights-screen.tsx
no import path from any entry point (277 application, 56 tooling, 375 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (apps/mobile/app/(tabs)/applications/calendar.tsx) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it — apps/mobile/src/features/applications-board/calendar-screen.tsx
no import path from any entry point (277 application, 56 tooling, 375 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (apps/mobile/app/search.tsx) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it — apps/mobile/src/features/search/search-screen.tsx
no import path from any entry point (277 application, 56 tooling, 375 test roots considered), but 2 in-repo import(s) from 2 other file(s) do name it (apps/mobile/app/builder/[id]/assistant.tsx, apps/mobile/app/letter/[id]/assistant.tsx) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it — apps/mobile/src/features/assistant/assistant-screen.tsx
no import path from any entry point (277 application, 56 tooling, 375 test roots considered), but 2 in-repo import(s) from 2 other file(s) do name it (apps/mobile/src/features/ats-checker/checker.tsx, apps/mobile/src/features/check/parser.tsx) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it — apps/mobile/src/features/ats-checker/messages.ts
no import path from any entry point (277 application, 56 tooling, 375 test roots considered), but 2 in-repo import(s) from 2 other file(s) do name it (apps/mobile/app/(tabs)/settings/preferences.tsx, apps/mobile/src/features/application-detail/interview-sheet.tsx) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it — apps/mobile/src/lib/timezones.ts
no import path from any entry point (277 application, 56 tooling, 375 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (apps/mobile/src/features/share/screen.tsx) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it — apps/mobile/src/features/share/link.tsx
no import path from any entry point (277 application, 56 tooling, 375 test roots considered), but 3 in-repo import(s) from 3 other file(s) do name it (apps/mobile/src/features/design/advanced.tsx, apps/mobile/src/features/design/design-pane.tsx, apps/mobile/src/features/design/layout-screen.tsx) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it — apps/mobile/src/features/design/style-groups.tsx
no import path from any entry point (277 application, 56 tooling, 375 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (apps/mobile/app/(tabs)/career/coach.tsx) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it — apps/mobile/src/features/assistant/coach-screen.tsx
no import path from any entry point (277 application, 56 tooling, 375 test roots considered), but 16 in-repo import(s) from 8 other file(s) do name it (apps/mobile/src/features/workspace/shell.tsx, apps/mobile/src/features/workspace/tabs/apply.tsx, apps/mobile/src/features/workspace/tabs/debrief.tsx and 5 more) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it — apps/mobile/src/features/workspace/hooks.ts
no import path from any entry point (277 application, 56 tooling, 375 test roots considered), but 5 in-repo import(s) from 3 other file(s) do name it (apps/mobile/app/builder/[id]/_layout.tsx, apps/mobile/app/letter/[id]/_layout.tsx, apps/mobile/src/features/document-menu/index.tsx) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it — apps/mobile/src/shell/builder-chrome.tsx
no import path from any entry point (277 application, 56 tooling, 375 test roots considered), but 2 in-repo import(s) from 2 other file(s) do name it (apps/mobile/src/features/write/entry-fields.tsx, apps/mobile/src/features/write/entry-screen.tsx) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it — apps/mobile/src/features/write/rich-text-field.tsx
no import path from any entry point (277 application, 56 tooling, 375 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (apps/mobile/app/(tabs)/career/today.tsx) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it — apps/mobile/src/features/career/today.tsx
no import path from any entry point (277 application, 56 tooling, 375 test roots considered), but 9 in-repo import(s) from 6 other file(s) do name it (apps/mobile/src/features/check/actions.ts, apps/mobile/src/features/check/model.ts, apps/mobile/src/features/check/page.tsx and 3 more) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it — apps/mobile/src/features/check/issues.ts
no import path from any entry point (277 application, 56 tooling, 375 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (apps/mobile/src/features/design/design-pane.tsx) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it — apps/mobile/src/features/design/layout-screen.tsx
no import path from any entry point (277 application, 56 tooling, 375 test roots considered), but 9 in-repo import(s) from 8 other file(s) do name it (apps/mobile/src/features/workspace/coach-sheet.tsx, apps/mobile/src/features/workspace/tabs/apply.tsx, apps/mobile/src/features/workspace/tabs/debrief.tsx and 5 more) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it — apps/mobile/src/features/workspace/parts.tsx
no import path from any entry point (277 application, 56 tooling, 375 test roots considered), but 8 in-repo import(s) from 7 other file(s) do name it (apps/mobile/src/features/workspace/shell.tsx, apps/mobile/src/features/workspace/tabs/apply.tsx, apps/mobile/src/features/workspace/tabs/debrief.tsx and 4 more) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it — apps/mobile/src/features/workspace/logic.ts
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. (×2) — tooling/cloudflare/build.mjs:43, REDACTED:122
Declared in the root package.json but never imported anywhere in that package or its workspace members — no static import reaches it. Usually that is dead weight and attack surface, but two shapes are indistinguishable from source and are NOT dead: an optional or native peer that another dependency loads dynamically at runtime, and a package a build, docs or test step installs and invokes separately. Confirm which of the three this is before removing it.
Declared in packages/email/package.json but never imported anywhere in that package or its workspace members — no static import reaches it. Usually that is dead weight and attack surface, but two shapes are indistinguishable from source and are NOT dead: an optional or native peer that another dependency loads dynamically at runtime, and a package a build, docs or test step installs and invokes separately. Confirm which of the three this is before removing it.
Only test files import it (first: packages/api/src/features/documents/exports.test.ts:3) — move it to devDependencies. — packages/api/package.json:67
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. This repository commits the configuration that serves its own HTTP surface, so that configuration was read in full for the security response headers it sets. 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.
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.
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 document2.7 / 10Weak✓ Tool-verified
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.
`detectJsonImportKind` is exported and takes `parsed: unknown` from its caller, and it calls itself at line 36 (`detectJsonImportKind`) with a piece of `parsed` — and nowhere in `detectJsonImportKind` is there a depth parameter, a descent counter, or any other cap. The walk therefore spends one stack frame per LEVEL of the value it is handed, so the nesting of the caller's document — not this code — decides how deep the stack goes. JavaScript sets no limit of its own on that nesting: `JSON.parse` accepts any depth, so a 100,000-byte body — inside Express's default 100kb limit — parses to 50,000 levels, and a walk like this one throws `RangeError: Maximum call stack size exceeded` long before it reaches the bottom. Wherever that throw lands, the work fails: a request errors, and a walk running outside any `try` — an event handler, a timer, a promise nobody awaits — takes the Node process down with every other request in flight. Thread a depth argument through `detectJsonImportKind` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack. — apps/web/src/features/resume/import/read-file.ts:36
`jsonImportFormat` is exported and takes `value: unknown` from its caller, and it calls itself at line 24 (`jsonImportFormat`) with a piece of `value` — and nowhere in `jsonImportFormat` is there a depth parameter, a descent counter, or any other cap. The walk therefore spends one stack frame per LEVEL of the value it is handed, so the nesting of the caller's document — not this code — decides how deep the stack goes. JavaScript sets no limit of its own on that nesting: `JSON.parse` accepts any depth, so a 100,000-byte body — inside Express's default 100kb limit — parses to 50,000 levels, and a walk like this one throws `RangeError: Maximum call stack size exceeded` long before it reaches the bottom. Wherever that throw lands, the work fails: a request errors, and a walk running outside any `try` — an event handler, a timer, a promise nobody awaits — takes the Node process down with every other request in flight. Thread a depth argument through `jsonImportFormat` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack. — apps/mobile/src/features/documents/import-file.ts:24
What to do
Each finding names the externally-callable member that accepts the document and the self-call that descends, and states that no depth parameter or counter exists anywhere in the walk. Confirm from the two, then thread a depth argument through the walk and reject documents past a fixed maximum, or rewrite it with an explicit stack.
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 14/18 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.
`fetchText` 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 })`. — tooling/locales/generate-region-zones.mjs:13
`fetchPublicResumePdf` 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 })`. — apps/web/src/features/resume/public/public-pdf.ts:15
`fetchSample` 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 })`. — apps/web/src/features/ats-checker/checker.tsx:149
`uiFontFace` 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 })`. — apps/web/src/features/applications/components/insights-view.tsx:217
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 an argument guard throws the exception its own condition describes — a guard that rejects a value for being EMPTY and reports it as `NullPointerException` (Java, Kotlin, Scala), `ArgumentError.notNull` (Dart) or `ArgumentNullException` (F#'s `nullArg`) tells the caller a parameter was null when it provably was not.
Method: Roslyn syntax: `throw new ArgumentNullException(nameof(p))` statements controlled by an `if`, whose condition is read for a test that is true of a NON-null `p` — an emptiness test that dereferences it (`p.Count == 0`, `!p.Any()`) or a BCL predicate documented true of the empty value (`string.IsNullOrEmpty(p)`). Deterministic, provable per finding. Advisory.
Other · Code Health — Whether a `when` guard is free of side effects — a guard that increments a counter or assigns while deciding whether its arm matches applies that change during PATTERN MATCHING, on an arm that may not be selected, and skips it entirely when a short-circuit to its left answers first.
Method: Roslyn syntax: `when` guards on case labels and switch-expression arms, read for a mutation (`++`/`--`/assignment) sitting in a position the guard's own `&&`/`||`/`??`/`?:`/`?.` can skip. Deterministic, provable per finding. Advisory.
Other · Code Health — Whether a method that TAKES a lock or semaphore and gives it back from a flag-guarded `finally` returns the value that flag implies — reporting success while the guard hands the primitive back admits a second caller the exclusion was there to keep out, and reporting failure while the guard keeps it leaves nothing to ever give it back.
Method: Roslyn syntax: `try` statements whose `finally` releases a synchronisation primitive under a bare local-bool guard, where the method also TOOK that same primitive before the `try`, checked for a `return` of a bool literal whose value disagrees with the flag state the method's own straight-line assignments put it in. Deterministic, provable per finding. Advisory.
Other · Code Health — Whether the work a diagnostic log line costs is paid only when that line is wanted — C# evaluates a call's arguments BEFORE the call, so a trace/debug message joined or projected out of a collection is built in full on every pass, and then discarded by a sink the shipped configuration leaves switched off.
Method: Roslyn syntax: log calls at a diagnostic level (a `Log`-prefixed method naming Trace/Debug/Verbose, or a bare `Debug`/`Trace`/`Verbose` on a receiver named for a logger), whose argument list is read for a call whose cost scales with a sequence — a LINQ operator, a materialisation, `string.Join`, a serializer — with no enclosing level check or conditional-compilation region. 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 unescaped5.4 / 10Adequate✓ Tool-verified
Other · Security — Whether text read out of the document being converted is escaped before it is written into generated markup — a value the document's author chose, interpolated into an attribute the surrounding literal delimits, can close that attribute and open another.
Method: Roslyn semantic model over the whole compilation: a string-typed `Value`/`InnerText`/`InnerXml`/`Text` member declared inside `DocumentFormat.OpenXml` or `System.Xml` is a taint SOURCE, propagated through assignments, returns, arguments, tuple elements and string composition to its transitive closure, then read at interpolated-string holes that sit in a markup position the surrounding literal itself delimits. Escaper/encoder calls and enclosing validator conditions cut the flow. Flow- and container-insensitive by construction. A second arm needs no provenance at all and reports a type that CONTRADICTS ITSELF — the same expression escaped at one delimited markup hole and interpolated raw at another hole in the same markup position of the same type, which the type's own escaping proves is a defect without knowing where the value came from. On a repository with no .NET source it reads JavaScript/TypeScript off the token stream with the same rule: a DOM read of raw document text (`getAttribute`, `textContent`, `innerText`, `nodeValue`) is the source, propagated through local bindings and string composition, and judged at template-literal and concatenation holes in the same two delimited markup positions; escapers and validating conditions cut it, and documentation-site, test, vendored and minified scripts are not read. Deterministic, provable per finding. Advisory.
`escapeXml(href)` is text this program did not author, and it is written into the start of a URL attribute, where it chooses the scheme through markup this function returns with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. HTML encoding does not help here — a `javascript:` URL contains nothing it changes; allow only http(s) or a relative path. — apps/server/src/static/seo.ts:54
`escapeAttribute(href)` is text this program did not author, and it is written into the start of a URL attribute, where it chooses the scheme through markup built here with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. HTML encoding does not help here — a `javascript:` URL contains nothing it changes; allow only http(s) or a relative path. — apps/server/src/static/web.ts:237
`url` is text this program did not author, and it is written into the start of a URL attribute, where it chooses the scheme through markup this function returns with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. HTML encoding does not help here — a `javascript:` URL contains nothing it changes; allow only http(s) or a relative path. — apps/server/src/static/web.ts:243
`escapeAttribute(canonicalUrl)` is text this program did not author, and it is written into the start of a URL attribute, where it chooses the scheme through markup built here with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. HTML encoding does not help here — a `javascript:` URL contains nothing it changes; allow only http(s) or a relative path. — apps/server/src/static/web.ts:454
`serializeJsonLd(structuredData)` is text this program did not author, and it is written into the text of an element through `dangerouslySetInnerHTML` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup. — apps/web/src/features/homepage/faq.tsx:210
`html` is text this program did not author, and it is written into the text of an element through `dangerouslySetInnerHTML` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup. — REDACTED:68
`escapeXml(node.href)` is text this program did not author, and it is written into the start of a URL attribute, where it chooses the scheme through markup this function returns with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. HTML encoding does not help here — a `javascript:` URL contains nothing it changes; allow only http(s) or a relative path. — REDACTED:82
`whitespace` is text this program did not author, and it is written into the text of an element through `insertAdjacentHTML` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup. (×2) — REDACTED:88, REDACTED:97
`child.innerHTML` is text this program did not author, and it is written into the text of an element through `innerHTML` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup. — REDACTED:112
What to do
Each finding names the expression, the attribute it lands in and the line. Confirm the value's origin from the read this analyzer traced, then escape it at the sink or validate it against the shape the attribute accepts before interpolating.
Other · Code Health — Whether a value the caller is invited to supply is the value the type actually uses — a constructor parameter stored in a private field that nothing ever reads while the default it was given is spelled out a second time at the site that should have read it, a keyed lookup that falls back to a different setting than the one its key names while the same type falls back to the matching one for that same key, or a culture-sensitive parse given no format provider by a type that feeds its own settable culture to the same kind of parse elsewhere, or a number an entry point writes to standard output under the host's culture while the same entry point formats with the invariant culture elsewhere. Either way, every caller who supplies a value silently gets something else.
Method: Roslyn syntax: private instance fields of a non-partial type assigned in a constructor from one of its own parameters with a `??` fallback, checked for whether anything in the type body reads the field and whether that same fallback expression is spelled out again outside the constructor; and `??` fallbacks onto a member access from a lookup call carrying exactly one string literal, grouped by that key across the type and checked for a fallback member whose folded name disagrees with the key while a sibling site for the same key agrees with it. On a repository with no .NET source the first two arms read JavaScript/TypeScript off the engine’s own token stream (tests included, bundles and vendored paths not): a `#x`, `private` or `private` parameter-property instance field filled in the constructor from a parameter (or one member of one) through `??`/`||` or a parameter default, never read anywhere in the file by name, whose constructed default is spelled again in the class body; and `lookup("key") ?? s.member` grouped by key per class, or per module outside every class. The culture arm has no JavaScript counterpart: its parses take no locale. Deterministic, provable per finding. Advisory.
Other · Code Health — Whether a value handed from a callback to the body that waits on it crosses on something built to be crossed — a `Queue<T>`/`List<T>`/`Dictionary<K,V>` written inside an event handler and read back outside it is mutated by two flows at once, and the semaphore or completion source beside it orders how MANY items exist while leaving the collection's own head, tail and backing array unprotected.
Method: Roslyn syntax: method, accessor, local-function and lambda bodies that declare BOTH a non-thread-safe generic collection (`Queue`/`Stack`/`List`/`Dictionary`/`HashSet`/`Sorted*`/`LinkedList`) and a synchronisation primitive (`SemaphoreSlim`/`TaskCompletionSource`/`ManualResetEvent(Slim)`/`AutoResetEvent`/`CountdownEvent`) as locals, then read for a `+=`-registered lambda that raises that primitive while the body outside every lambda waits on it — and, in that scope, a mutating call on the collection inside the lambda paired with a mention of it outside. Any `lock` in the scope abstains it. On a repository with no .NET source the same handoff is read in Java off the engine’s own token stream (test source sets, vendored and demonstration paths not): an `ArrayList`/`LinkedList`/`ArrayDeque`/`PriorityQueue`/`Hash*`/`LinkedHash*`/`Tree*` local and a `CountDownLatch`/`Semaphore`/`CompletableFuture` local, a lambda or anonymous class that raises the primitive and mutates the collection, and a wait outside it; any `synchronized` or `lock()` abstains the body. Because each of those primitives orders what the callback wrote before raising it, only a touch that provably overlaps the callback is convicted: one after the registration and before the next wait, or one in a loop registered-before, waiting on every pass and not declaring the collection. Deterministic, provable per finding. Advisory.
Do you agree with this assessment?
X27 · Collection changed while being enumerated10.0 / 10Exemplary○ Nothing flagged
Other · Code Health — Whether a `for` loop leaves the `RefCell` it is walking alone — safe Rust rejects a body that changes the collection its loop borrows at compile time, except through interior mutability: a `RefCell` borrowed in the loop's header stays borrowed until the loop ends, so a `borrow_mut()` of it inside the body panics with `already borrowed: BorrowMutError` and the remaining elements are never seen. Whether a `for (x in c)` or `c.forEach { … }` leaves the collection it is walking alone — a `mutableListOf`/`ArrayList`, `mutableMapOf`/`HashMap` or `mutableSetOf`/`HashSet` is a `java.util` collection on the JVM and is walked by its own fail-fast iterator, so a body that adds to or removes from the very collection the loop is walking makes the next step throw `ConcurrentModificationException` and the remaining elements are never seen.
Method: Roslyn syntax + semantics: `foreach` statements whose body calls a structural mutator (`Add`/`Remove`/`Clear`/`Insert`/…) on the very expression the loop is enumerating. Two arms. ARM A — the source is a concrete fragile BCL collection, or a live `Keys`/`Values` view over one, and the mutator resolves to that same collection's own member; concurrent and immutable collections and arrays are outside the population by construction, since their enumerators survive a structural change. ARM B — the source is an argument-less accessor CALL on a receiver whose body is in source: the accessor must return a stored field VERBATIM and a sibling member must structurally change that same field, both read off the implementations rather than from the members' names. A mutation the loop provably exits immediately after (`break`/`return`/`throw`/`goto`), or one written inside a nested loop or a lambda, is counted and never reported. Deterministic, provable per finding. Advisory.
Do you agree with this assessment?
X28 · Index access outside its own emptiness guard10.0 / 10Exemplary○ Nothing flagged
Other · Code Health — Whether a condition that tests a value for emptiness indexes that same value only where the test holds — an `||` written one parenthesis too far to the left leaves an index access outside the guard beside it, so the empty case the guard exists to anticipate reaches the index and throws.
Method: Roslyn syntax only, no semantic model: the OUTERMOST `&&`/`||` of every boolean condition, read for a symbol the condition tests for emptiness (`string.IsNullOrEmpty`/`IsNullOrWhiteSpace`, a `Length`/`Count` comparison against a literal, `Any()`, a `Length`/`Count` pattern, or a comparison against `""`) and ALSO indexes. Each `symbol[...]` access is placed by a boolean-reachability walk from the access up to the outermost connective: an access is COVERED when some enclosing step has it in the right operand and the left operand, under the truth value that step forces, proves the symbol non-empty — a recursion over `&&`/`||` whose true- and false-directions are asymmetric. A finding needs BOTH an uncovered access and a covered one on the same symbol in the same condition, which is the agreeing twin that separates a misplaced parenthesis from an unrelated length test. Bare index accesses with no emptiness test in the condition are neither counted nor reported; a non-identifier receiver and a lambda nested inside the condition are outside the population. Deterministic, provable per finding. Advisory.
Do you agree with this assessment?
X29 · Per-element action decided by a fixed element10.0 / 10Exemplary○ Nothing flagged
Other · Code Health — Whether a decision taken once per element is taken ABOUT that element — a test inside a counted loop that reads a fixed subscript of the very collection its guarded statement indexes by the loop variable applies element zero's answer to all of them, so the elements that differ from it are all handled wrongly, and in the same direction.
Method: Roslyn syntax only, no semantic model: every `for` statement declaring exactly ONE loop variable, and every `if` inside its body that is not under a nested loop or a lambda. A site enters the population when the `if`’s condition never mentions the loop variable while the statement it guards indexes some collection by that variable ALONE (`c[i]`; `c[i + 1]` and `c[i, j]` are outside it). A finding additionally needs the AGREEING TWIN at the same-collection grain: the condition must read THAT SAME collection at a subscript that does not move — written into the condition, or reached through a local declared BEFORE the loop, so an alias bound inside the body is not followed. Both collection expressions must be simple identifiers. On a repository with no .NET source the same rule reads JavaScript/TypeScript off the engine’s own token stream (tests included, bundles and vendored paths not): a `for (let|var|const x = …; …; …)` with one declarator and a braced body, an alias followed only when it is declared before the loop in a block that encloses it and never assigned inside the loop. Deterministic, provable per finding. Advisory.
Other · Code Health — Whether exceptions are handled rather than silently swallowed or rethrown with lost stack traces.
Method: Roslyn syntax scan: every catch clause counted; empty catches and bare rethrows flagged. Population is all catch clauses, not estimated. Deterministic, hard fact.
`catch` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter. (×3) — packages/schema/src/resume/period.ts:112, packages/api/src/features/applications/posting.ts:130, apps/web/src/features/auth/redirect.ts:16
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. (×26) — packages/pdf/src/forme/font-subset.ts:93, packages/api/src/features/statistics/service.ts:40, packages/api/src/features/statistics/service.ts:65, …
`.catch(() => {})` handles the rejection by doing nothing — the failure is discarded with no log and no rethrow, and the chain carries on as if the work succeeded. Log it through whatever this codebase already uses to report problems, hand it to a caller that can (`next(error)`, a returned rejection), or don't catch it. (×11) — packages/api/src/features/web-access/builtin.ts:121, packages/api/src/features/resume/events.ts:74, packages/api/src/features/resume/events.ts:144, …
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.
Other · Code Health — Whether strict null checking is enabled and not undermined by heavy `!` assertion — TypeScript's `strictNullChecks` (which `strict` turns on) is what makes `string` exclude `null` and `undefined`, and the postfix `!` is the operator that silences it.
Method: Roslyn compiler-options scan: NullableContextOptions per project; null-forgiving (!) suppression density per 1k syntax nodes. Deterministic, adoption plus suppression penalty.
2/9 of this repository's type-checking configuration(s) turn on strict null checking (`"strict": true`, or `"strictNullChecks": true`). A configuration that states neither is counted as OFF, because off is tsc's own default; a solution-style one whose `"files"` is empty and whose `"references"` point at other projects is in neither number, because it checks no source itself. Where it is off, `string` admits `null` and `undefined`: passing a value that is null compiles silently and throws on the first property access.
What to do
The findings name the configuration each number was taken from and, for the assertions, the files that hold them. Turn null checking on where it is off — `"strict": true` in the base tsconfig that the others extend switches `strictNullChecks` on with the rest of the family — and then resolve the assertions rather than adding to them. A `!` on a value the checker could show to be null is a promise the author cannot check from where they are standing, and each one is a `TypeError: Cannot read properties of null` waiting for the path that makes it true; where the value genuinely cannot be null, say something the checker can see instead (narrow it with a test, make the property required, drop the `?`).
Do you agree with this assessment?
WCAG coverage — what static analysis assessed
Statically assessed 15 of 55 WCAG 2.2 Level A/AA success criteria (27%; ≈30% of the 50 WCAG 2.1 AA criteria for EN 301 549). The other 40 require runtime or manual evaluation. Partial signal only (a clean result is necessary, not sufficient; static analysis fully verifies none). This is accessibility readiness, not a conformance claim — a WCAG conformance claim requires manual evaluation (WCAG-EM 1.0).
The score is the rank-weighted fold of these lenses (worst-heaviest), each including its meta-dimensions; a lens with a Critical contributor is capped at Fair (its band reads "gated by …") and is never the strongest area however high its average.
Unscored — 2 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.
X10 Duplicated predicate — 25 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
X7 Silent fallback defaults — 10 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.
C3 Audit Trail — Repo shows no audit-logging mechanism (an audit-log table or model, an ORM write hook that records changes — a TypeORM/MikroORM subscriber, a Sequelize or Mongoose hook, Prisma middleware — or a change-history plugin such as mongoose-history or sequelize-paper-trail) for sensitive changes — absence of evidence is not evidence of a working control. Record an audit trail in code (or document where it lives) so this dimension can be scored.
Not included — 37 check(s) not relevant to this codebase
These checks had nothing to measure here (no tests, no git history, the codebase is small, or the architecture style doesn't apply), so they're omitted above rather than scored low.
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; this repository's Kotlin 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; this repository's TypeScript 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; Rust with no dependency-injection crate has no container to hand one lifetime's instance to another — every value is owned by the code that builds it, and the borrow checker rejects a longer-lived value keeping a borrow of a shorter-lived one; this repository's Swift 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 — No container singleton was found, so there is no shared instance for concurrent requests to race on. No class in this Kotlin code is a Spring, JSR-330 or CDI singleton bean. No Swift request handler (a Vapor, Hummingbird, Kitura, Swifter or Perfect route handler, as a method or a registered closure) is declared, so no state is shared between request threads. Rust's compiler refuses unsynchronised shared mutation — a value shared across threads must be Sync — so the race this check looks for cannot be written. 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).
AX4 Dependency direction — not applicable to a vertical-slice architecture (the inward-dependency rule is for layered/clean styles)
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 — compose up failed (exit 18 — an image could not be pulled) — redis Pulling seaweedfs Pulling seaweedfs_create_bucket Pulling postgres Pulling seaweedfs_create_bucket Error Get "https://registry-1.docker.io/v2/": Forbidden seaweedfs Error context canceled redis Error context canceled postgres Error context canceled Error response from daemon: Get "https://registry-1.docker.io/v2/": Forbidden; the earlier `compose pull` step reported: reactive_resume Skipped - No image to be pulled seaweedfs_create_bucket Pulling postgres Pulling seaweedfs Pulling redis Pulling seaweedfs_create_bucket Error Get "https://registry-1.docker.io/v2/": Forbidden seaweedfs Error context canceled redis Error context canceled postgres Error context canceled Error response from daemon: Get "https://registry-1.docker.io/v2/": Forbidden; the runtime sandbox reaches registries only through the in-fence pull-through mirror, so an image the mirror does not carry cannot be fetched — this is a limit of our sandbox, not of your stack; runtime evidence skipped This is a statement about this run, not a statement about your application: nothing here says the surface is inaccessible, only that it was never rendered.
D16 Bus Factor — single-maintainer repository — bus factor is not applicable
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.
D21 Naming Consistency — Naming consistency is measured on C# only; JavaScript, Kotlin, Rust, Swift, TypeScript not measured.
D22 Internal API Consistency — The exposed public-API surface could not be collected — no C#/VB projects loaded.
D24 Comment Value — D24 reads C# and Visual Basic comments only — this repository's production source is .kt, .mts, .rs, .swift, .ts, .tsx, which was left unread. Not scored: this is a gap in the analyzer, not a verdict about this repository.
D25 ADR Conformance — no ADRs to check
D27 Navigability — D27 counts a call into the standard library or a dependency as unresolved for this repository's language (.mts,.ts,.tsx), 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.
D32 Data Compliance (PII/GDPR) — 109 file(s) were not parsed by semgrep — the PII/GDPR ruleset never ran over them
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 — This repository's production source (.mts, .ts, .tsx) is not read by D4's token comparison, which compares .NET source: duplication in it is measured by R10 Code Duplication, the frontend lens's card running the same clone algorithm over the JS/TS token stream. Not scored here — read the R10 card for this repository's duplication.
D40 Network Egress Confinement — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here.
D41 Kernel & Syscall Confinement — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here.
D42 Runtime Threat Enforcement — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here.
D7 Architectural Integrity — no checkable ADRs, and no project-reference graph for the cycle pass to read — so this dimension makes no claim about dependency cycles in either direction (where this repository's language has an import-cycle lens, cycles are reported there). Architectural integrity not assessed
DM1 Domain Modelling — not scored — this repository shows only 1 of the 3 signals this lens looks for (1 value object(s))
ED2 Event/command shape — not scored — deciding whether a command has more than one competing handler requires resolving the call graph, and this analysis resolves a call's owner only where the receiver's type is written down in the source. Reported as guidance rather than measured
ED2 Event/command shape — not scored — deciding whether a command has more than one competing handler requires resolving the call graph, and a call made through an inferred or generic receiver has no resolvable owner in the source. Reported as guidance rather than measured
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'.
P7 Outbound HTTP resilience — not applicable — no HTTP server, API framework or worker entry point was found in the JVM, JavaScript/TypeScript, Rust, Swift source, so there is no service whose uptime a failing dependency could take down
P9 Domain vs controller coverage — coverage data present for 5 file(s), but no domain-layer files were identified: no covered file's path contains any of the markers this check keys on (/domain/, /aggregates/, /valueobjects/, /domainmodel/, .domain/, /entities/), which are matched case-insensitively anywhere in the path. With no domain partition there is nothing to compare the web/controller layer against — if this repository keeps its business rules under a folder named none of those, that naming is what the check cannot see, not the domain logic.
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: allocation awareness is rated where code engineers for it — at least 400 production lines that ship benchmarks or already use allocation-aware idioms (8 or more). This repository's Kotlin and Swift code has 453 production line(s), 3 such use(s) and no benchmarks, so there is no allocation work to rate. The card is reward-only: its absence costs nothing.
R5 Dependency Freshness — uses a pnpm lockfile — dependency freshness not measured here; JS/npm CVEs are scored in D30 (Dependency Vulnerabilities), which answers every ecosystem
SC1 Supply-chain hygiene — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
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
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.
AC4 · Keyboard semantics· Click handler on a non-interactive <tr> · ×2
Click handler on a non-interactive <tr> apps/web/src/features/applications/components/list-view.tsx:276— 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 <tr> apps/web/src/features/applications/components/list-view.tsx:292— 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· Click handler on a non-interactive <div> · ×2
Click handler on a non-interactive <div> apps/web/src/features/resume/editor/page-overlay.tsx:63— 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> apps/web/src/routes/builder/letter/-components/letter-page.tsx:205— A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabIndex={0} + a key handler.
Import cycle (2 files) packages/db/src/schema/applications.ts:13— packages/db/src/schema/applications.ts → packages/db/src/schema/cover-letter.ts → packages/db/src/schema/applications.ts (one verified cycle inside a mutually-dependent group of 3 files)
AC2 · Forms & labels· Custom control with no accessible name on <div> · ×1
Custom control with no accessible name on <div> apps/web/src/routes/builder/letter/-components/letter-page.tsx:205— 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 <li> · ×1
Click handler on a non-interactive <li> apps/web/src/features/resume/editor/check/check-panel.tsx:198— A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabIndex={0} + a key handler.
Focusable <section> isn't keyboard-operable apps/web/src/routes/builder/$resumeId/-components/page-canvas.tsx:87— This <section> carries tabIndex={0}, so it is in the tab order and a keyboard user will land on it — but its only behaviour is bound to pointerdown, pointer gestures a keyboard cannot produce, and there is no key handler. The tab stop leads nowhere. Bind the same behaviour to a key handler, or provide an equivalent control elsewhere. Give it a role as well, so assistive tech can announce what it is.
Unlisted import '@formepdf/core' tooling/cloudflare/build.mjs:43— Imported but not declared in any reachable package.json — installs work only by hoisting accident.
FunctionTooLong: add-sheet.AddApplicationSheet apps/mobile/src/features/applications/add-sheet.tsx:48— FunctionTooLong — AddApplicationSheet runs 441 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 341 over it, 4.41× 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: practise.Session apps/web/src/features/career/workspace/practise.tsx:218— FunctionTooLong — Session runs 412 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 312 over it, 4.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.
FunctionTooLong: add-application-dialog.AddApplicationForm apps/web/src/features/applications/components/add-application-dialog.tsx:68— FunctionTooLong — AddApplicationForm runs 400 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 300 over it, 4.00× 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: new-document.NewDocument apps/mobile/src/features/documents/new-document.tsx:24— FunctionTooLong — NewDocument runs 387 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 287 over it, 3.87× 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: store.createDraftStore apps/mobile/src/draft/store.ts:50— FunctionTooLong — createDraftStore runs 384 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 284 over it, 3.84× 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: list-screen.ApplicationsList apps/mobile/src/features/applications/list-screen.tsx:55— FunctionTooLong — ApplicationsList runs 380 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 280 over it, 3.80× 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: schedule-sheet.ScheduleSheet apps/web/src/features/career/schedule-sheet.tsx:129— FunctionTooLong — ScheduleSheet runs 361 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 261 over it, 3.61× 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: web-access.WebAccessSection apps/web/src/features/settings/ai/web-access.tsx:30— FunctionTooLong — WebAccessSection runs 358 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 258 over it, 3.58× 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: library.DocumentsLibrary apps/mobile/src/features/documents/library.tsx:159— FunctionTooLong — DocumentsLibrary runs 354 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 254 over it, 3.54× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: practise.Session apps/mobile/src/features/workspace/tabs/practise.tsx:185— FunctionTooLong — Session runs 346 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 246 over it, 3.46× 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: search-screen.SearchScreen apps/mobile/src/features/search/search-screen.tsx:41— FunctionTooLong — SearchScreen runs 330 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 230 over it, 3.30× 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: interview-sheet.InterviewForm apps/mobile/src/features/application-detail/interview-sheet.tsx:121— FunctionTooLong — InterviewForm runs 329 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 229 over it, 3.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: interview-dialog.InterviewDialog apps/web/src/features/applications/components/interview-dialog.tsx:145— FunctionTooLong — InterviewDialog runs 316 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 216 over it, 3.16× 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: today.TodayScreen apps/mobile/src/features/career/today.tsx:33— FunctionTooLong — TodayScreen runs 314 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 214 over it, 3.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: messages.getPdfFindingMessage apps/mobile/src/features/ats-checker/messages.ts:21— FunctionTooLong — getPdfFindingMessage runs 310 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 210 over it, 3.10× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: calendar-screen.ApplicationCalendar apps/mobile/src/features/applications-board/calendar-screen.tsx:51— FunctionTooLong — ApplicationCalendar runs 296 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 196 over it, 2.96× 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: chat-view.Conversation apps/mobile/src/features/assistant/chat-view.tsx:241— FunctionTooLong — Conversation runs 290 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 190 over it, 2.90× 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: coach.CoachPage apps/web/src/features/career/coach.tsx:104— FunctionTooLong — CoachPage runs 283 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 183 over it, 2.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: config.getAuthConfig packages/auth/src/config.ts:257— FunctionTooLong — getAuthConfig runs 283 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 183 over it, 2.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: cascade.resolveStylesheet packages/resume/src/stylesheet/cascade.ts:554— FunctionTooLong — resolveStylesheet runs 261 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 161 over it, 2.61× 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: link.LinkTab apps/mobile/src/features/share/link.tsx:32— FunctionTooLong — LinkTab runs 260 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 160 over it, 2.60× 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: section-sheet.SectionSheet apps/mobile/src/features/write/section-sheet.tsx:24— FunctionTooLong — SectionSheet runs 259 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 159 over it, 2.59× 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: rich-text.RichText packages/pdf/src/templates/shared/rich-text.tsx:76— FunctionTooLong — RichText runs 256 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 156 over it, 2.56× 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: reactive-resume-v4-json.parseReactiveResumeV4JSON packages/import/src/reactive-resume-v4-json.tsx:241— FunctionTooLong — parseReactiveResumeV4JSON runs 251 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 151 over it, 2.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: board-screen.Board apps/mobile/src/features/applications-board/board-screen.tsx:85— FunctionTooLong — Board runs 250 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 150 over it, 2.50× 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.
Hotspot: packages/auth/src/config.ts packages/auth/src/config.ts:257— packages/auth/src/config.ts changed 18 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 45 in config.getAuthConfig at line 257. 11 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-07-28..2026-10-26, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-28 12:07:53 +01:00' --until='2026-10-26 12:07:53 +01:00' --full-history --no-merges -- packages/auth/src/config.ts`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: apps/mobile/src/features/documents/library.tsx apps/mobile/src/features/documents/library.tsx:159— apps/mobile/src/features/documents/library.tsx changed 7 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 75 in library.DocumentsLibrary at line 159. 1 of those changes was a fix/bug commit, and the other 6 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-07-28..2026-10-26, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-28 12:07:53 +01:00' --until='2026-10-26 12:07:53 +01:00' --full-history --no-merges -- apps/mobile/src/features/documents/library.tsx`: 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: apps/server/src/openapi/generator.ts apps/server/src/openapi/generator.ts:226— apps/server/src/openapi/generator.ts changed 12 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 35 in generator.addCurlSamples at line 226. 6 of those changes were fix/bug commits, and the other 6 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-07-28..2026-10-26, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-28 12:07:53 +01:00' --until='2026-10-26 12:07:53 +01:00' --full-history --no-merges -- apps/server/src/openapi/generator.ts`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: packages/pdf/src/forme/to-forme.tsx packages/pdf/src/forme/to-forme.tsx:466— packages/pdf/src/forme/to-forme.tsx changed 6 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 67 in to-forme.convertNode at line 466. 5 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-07-28..2026-10-26, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-28 12:07:53 +01:00' --until='2026-10-26 12:07:53 +01:00' --full-history --no-merges -- packages/pdf/src/forme/to-forme.tsx`: 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: apps/web/src/routes/dashboard/applications/index.tsx apps/web/src/routes/dashboard/applications/index.tsx:70— apps/web/src/routes/dashboard/applications/index.tsx changed 9 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 37 in index.RouteComponent at line 70. 1 of those changes was a fix/bug commit, and the other 8 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-07-28..2026-10-26, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-28 12:07:53 +01:00' --until='2026-10-26 12:07:53 +01:00' --full-history --no-merges -- apps/web/src/routes/dashboard/applications/index.tsx`: 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: apps/web/src/features/resume/preview/preview.browser.tsx apps/web/src/features/resume/preview/preview.browser.tsx:111— apps/web/src/features/resume/preview/preview.browser.tsx changed 9 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 33 in preview.browser.ResumePreviewClient at line 111. 2 of those changes were fix/bug commits, and the other 7 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-07-28..2026-10-26, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-28 12:07:53 +01:00' --until='2026-10-26 12:07:53 +01:00' --full-history --no-merges -- apps/web/src/features/resume/preview/preview.browser.tsx`: 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: packages/pdf/src/templates/shared/sections.tsx packages/pdf/src/templates/shared/sections.tsx:1027— packages/pdf/src/templates/shared/sections.tsx changed 16 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 18 in sections.EducationSection at line 1027. 8 of those changes were fix/bug commits, and the other 8 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-07-28..2026-10-26, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-28 12:07:53 +01:00' --until='2026-10-26 12:07:53 +01:00' --full-history --no-merges -- packages/pdf/src/templates/shared/sections.tsx`: 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: apps/mobile/src/features/applications/list-screen.tsx apps/mobile/src/features/applications/list-screen.tsx:55— apps/mobile/src/features/applications/list-screen.tsx changed 4 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 71 in list-screen.ApplicationsList at line 55. 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-07-28..2026-10-26, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-28 12:07:53 +01:00' --until='2026-10-26 12:07:53 +01:00' --full-history --no-merges -- apps/mobile/src/features/applications/list-screen.tsx`: 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: apps/web/src/components/input/chip-input.tsx apps/web/src/components/input/chip-input.tsx:157— apps/web/src/components/input/chip-input.tsx changed 6 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 47 in chip-input.ChipInput at line 157. 2 of those changes were fix/bug commits, and the other 4 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-07-28..2026-10-26, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-28 12:07:53 +01:00' --until='2026-10-26 12:07:53 +01:00' --full-history --no-merges -- apps/web/src/components/input/chip-input.tsx`: 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: packages/pdf/src/templates/shared/rich-text.tsx packages/pdf/src/templates/shared/rich-text.tsx:76— packages/pdf/src/templates/shared/rich-text.tsx changed 8 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 35 in rich-text.RichText at line 76. 3 of those changes were fix/bug commits, and the other 5 changed it for other reasons — this file is under both repair and feature pressure. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-07-28..2026-10-26, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-28 12:07:53 +01:00' --until='2026-10-26 12:07:53 +01:00' --full-history --no-merges -- packages/pdf/src/templates/shared/rich-text.tsx`: 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: apps/mobile/src/features/applications-board/board-screen.tsx apps/mobile/src/features/applications-board/board-screen.tsx:85— apps/mobile/src/features/applications-board/board-screen.tsx changed 5 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 55 in board-screen.Board at line 85. 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-07-28..2026-10-26, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-28 12:07:53 +01:00' --until='2026-10-26 12:07:53 +01:00' --full-history --no-merges -- apps/mobile/src/features/applications-board/board-screen.tsx`: 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: packages/mcp/src/parity.ts packages/mcp/src/parity.ts:344— packages/mcp/src/parity.ts changed 12 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 22 in parity.registerParityTools at line 344. 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-07-28..2026-10-26, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-28 12:07:53 +01:00' --until='2026-10-26 12:07:53 +01:00' --full-history --no-merges -- packages/mcp/src/parity.ts`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: apps/web/src/features/resume/stylesheet/editor.tsx apps/web/src/features/resume/stylesheet/editor.tsx:122— apps/web/src/features/resume/stylesheet/editor.tsx changed 7 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 31 in editor.StylesheetCodeEditor at line 122. 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-07-28..2026-10-26, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-28 12:07:53 +01:00' --until='2026-10-26 12:07:53 +01:00' --full-history --no-merges -- apps/web/src/features/resume/stylesheet/editor.tsx`: 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: apps/web/src/features/homepage/scroll.ts apps/web/src/features/homepage/scroll.ts:153— apps/web/src/features/homepage/scroll.ts changed 4 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 54 in scroll.useScrollScenes at line 153. 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-07-28..2026-10-26, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-28 12:07:53 +01:00' --until='2026-10-26 12:07:53 +01:00' --full-history --no-merges -- apps/web/src/features/homepage/scroll.ts`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: packages/api/src/features/agent/service.ts packages/api/src/features/agent/service.ts:732— packages/api/src/features/agent/service.ts changed 10 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 21 in service.createAgent at line 732. 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-07-28..2026-10-26, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-28 12:07:53 +01:00' --until='2026-10-26 12:07:53 +01:00' --full-history --no-merges -- packages/api/src/features/agent/service.ts`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: packages/import/src/reactive-resume-v4-json.tsx packages/import/src/reactive-resume-v4-json.tsx:241— packages/import/src/reactive-resume-v4-json.tsx changed 6 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 32 in reactive-resume-v4-json.parseReactiveResumeV4JSON at line 241. 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-07-28..2026-10-26, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-28 12:07:53 +01:00' --until='2026-10-26 12:07:53 +01:00' --full-history --no-merges -- packages/import/src/reactive-resume-v4-json.tsx`: 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: packages/mcp/src/tools.ts packages/mcp/src/tools.ts:80— packages/mcp/src/tools.ts changed 8 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 24 in tools.registerTools at line 80. 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-07-28..2026-10-26, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-28 12:07:53 +01:00' --until='2026-10-26 12:07:53 +01:00' --full-history --no-merges -- packages/mcp/src/tools.ts`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: packages/pdf/src/hooks/use-register-fonts.ts packages/pdf/src/hooks/use-register-fonts.ts:218— packages/pdf/src/hooks/use-register-fonts.ts changed 10 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 19 in use-register-fonts.resolvePdfFonts at line 218. 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-07-28..2026-10-26, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-28 12:07:53 +01:00' --until='2026-10-26 12:07:53 +01:00' --full-history --no-merges -- packages/pdf/src/hooks/use-register-fonts.ts`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: apps/web/src/features/resume/public/public-resume.tsx apps/web/src/features/resume/public/public-resume.tsx:46— apps/web/src/features/resume/public/public-resume.tsx changed 9 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 21 in public-resume.PublicResumePage at line 46. 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-07-28..2026-10-26, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-28 12:07:53 +01:00' --until='2026-10-26 12:07:53 +01:00' --full-history --no-merges -- apps/web/src/features/resume/public/public-resume.tsx`: 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: packages/docx/src/html-to-docx.ts packages/docx/src/html-to-docx.ts:149— packages/docx/src/html-to-docx.ts changed 4 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 47 in html-to-docx.processBlockElement at line 149. 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-07-28..2026-10-26, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-28 12:07:53 +01:00' --until='2026-10-26 12:07:53 +01:00' --full-history --no-merges -- packages/docx/src/html-to-docx.ts`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: apps/web/src/routes/builder/$resumeId/-sidebar/right/sections/layout/pages.tsx apps/web/src/routes/builder/$resumeId/-sidebar/right/sections/layout/pages.tsx:88— apps/web/src/routes/builder/$resumeId/-sidebar/right/sections/layout/pages.tsx changed 6 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 31 in pages.LayoutPages at line 88. 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-07-28..2026-10-26, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-28 12:07:53 +01:00' --until='2026-10-26 12:07:53 +01:00' --full-history --no-merges -- apps/web/src/routes/builder/$resumeId/-sidebar/right/sections/layout/pages.tsx`: 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: apps/web/src/dialogs/auth/enable-two-factor.tsx apps/web/src/dialogs/auth/enable-two-factor.tsx:54— apps/web/src/dialogs/auth/enable-two-factor.tsx changed 10 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 18 in enable-two-factor.EnableTwoFactorDialog at line 54. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-07-28..2026-10-26, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-28 12:07:53 +01:00' --until='2026-10-26 12:07:53 +01:00' --full-history --no-merges -- apps/web/src/dialogs/auth/enable-two-factor.tsx`: 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: apps/mobile/src/features/assistant/chat-view.tsx apps/mobile/src/features/assistant/chat-view.tsx:241— apps/mobile/src/features/assistant/chat-view.tsx changed 3 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 58 in chat-view.Conversation at line 241. 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-07-28..2026-10-26, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-28 12:07:53 +01:00' --until='2026-10-26 12:07:53 +01:00' --full-history --no-merges -- apps/mobile/src/features/assistant/chat-view.tsx`: 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: apps/web/src/features/resume/builder/draft.ts apps/web/src/features/resume/builder/draft.ts:262— apps/web/src/features/resume/builder/draft.ts changed 9 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 19 in draft.flushResumeSave at line 262. 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-07-28..2026-10-26, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-28 12:07:53 +01:00' --until='2026-10-26 12:07:53 +01:00' --full-history --no-merges -- apps/web/src/features/resume/builder/draft.ts`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: packages/api/src/features/ai/service.ts packages/api/src/features/ai/service.ts:209— packages/api/src/features/ai/service.ts changed 10 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 17 in service.describeTestConnectionFailure at line 209. 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-07-28..2026-10-26, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-28 12:07:53 +01:00' --until='2026-10-26 12:07:53 +01:00' --full-history --no-merges -- packages/api/src/features/ai/service.ts`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
FileTooLong: agent/service.ts packages/api/src/features/agent/service.ts— FileTooLong — 1222 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 722 over it, 2.44× 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: shared/sections.tsx packages/pdf/src/templates/shared/sections.tsx— FileTooLong — 1157 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 657 over it, 2.31× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: career/service.ts packages/api/src/features/career/service.ts— FileTooLong — 923 significant lines (blank, comment-only and punctuation-only lines excluded), about 76% of them inside a single declaration: careerService (293-1131). The bar is 500 significant lines; this is 423 over it, 1.85× 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: workspace/practise.tsx apps/web/src/features/career/workspace/practise.tsx— FileTooLong — 907 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 407 over it, 1.81× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: semantic/tree.ts packages/pdf/src/semantic/tree.ts— FileTooLong — 776 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 276 over it, 1.55× 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: forme/to-forme.tsx packages/pdf/src/forme/to-forme.tsx— FileTooLong — 760 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 260 over it, 1.52× 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: assistant/conversation.tsx apps/web/src/features/assistant/conversation.tsx— FileTooLong — 714 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 214 over it, 1.43× 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: application-detail/sections.tsx apps/mobile/src/features/application-detail/sections.tsx— FileTooLong — 701 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 201 over it, 1.40× 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: assistant/chat-view.tsx apps/mobile/src/features/assistant/chat-view.tsx— FileTooLong — 688 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 188 over it, 1.38× 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: stylesheet/cascade.ts packages/resume/src/stylesheet/cascade.ts— FileTooLong — 682 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 182 over it, 1.36× 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: career/today.tsx apps/web/src/features/career/today.tsx— FileTooLong — 676 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 176 over it, 1.35× 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: write/picture-settings.tsx apps/web/src/features/resume/editor/write/picture-settings.tsx— FileTooLong — 659 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 159 over it, 1.32× 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: resume/data.ts packages/schema/src/resume/data.ts— FileTooLong — 658 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 158 over it, 1.32× 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: tabs/practise.tsx apps/mobile/src/features/workspace/tabs/practise.tsx— FileTooLong — 655 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 155 over it, 1.31× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: applications/service.ts packages/api/src/features/applications/service.ts— FileTooLong — 653 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 153 over it, 1.31× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: src/tool-meta.ts packages/mcp/src/tool-meta.ts— FileTooLong — 644 significant lines (blank, comment-only and punctuation-only lines excluded), about 79% of them inside a single declaration: TOOL_META (157-753). The bar is 500 significant lines; this is 144 over it, 1.29× 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: letters/write.tsx apps/mobile/src/features/letters/write.tsx— FileTooLong — 640 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 140 over it, 1.28× 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: ai/providers.tsx apps/web/src/features/settings/ai/providers.tsx— FileTooLong — 592 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 92 over it, 1.18× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: homepage/prepare.tsx apps/web/src/features/homepage/prepare.tsx— FileTooLong — 582 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 82 over it, 1.16× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: career/coach.tsx apps/web/src/features/career/coach.tsx— FileTooLong — 580 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 80 over it, 1.16× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: resume/service.ts packages/api/src/features/resume/service.ts— FileTooLong — 578 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 78 over it, 1.16× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: -components/write-panel.tsx apps/web/src/routes/builder/letter/-components/write-panel.tsx— FileTooLong — 575 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 75 over it, 1.15× 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/application-detail-sheet.tsx apps/web/src/features/applications/components/application-detail-sheet.tsx— FileTooLong — 574 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 74 over it, 1.15× 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: career/coach-chat.tsx apps/web/src/features/career/coach-chat.tsx— FileTooLong — 572 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 72 over it, 1.14× 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: workspace/shell.tsx apps/web/src/features/career/workspace/shell.tsx— FileTooLong — 565 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 65 over it, 1.13× 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.
Boundary violation [package:relative-cross-package] apps/mobile/scripts/parity/device.ts:8— apps/mobile/scripts/parity/device.ts:8 reaches into another package with a relative path (../../modules/pdf-pages) — import the package by name instead.
Boundary violation [package:relative-cross-package] apps/mobile/scripts/parity/host.mts:19— apps/mobile/scripts/parity/host.mts:19 reaches into another package with a relative path (../../../web/public/photos/sample-picture.jpg) — import the package by name instead.
Boundary violation [package:relative-cross-package] apps/mobile/scripts/parity/review.ts:4— apps/mobile/scripts/parity/review.ts:4 reaches into another package with a relative path (../../modules/pdf-pages) — import the package by name instead.
Boundary violation [package:relative-cross-package] apps/mobile/src/features/ats-checker/original-page.tsx:1— apps/mobile/src/features/ats-checker/original-page.tsx:1 reaches into another package with a relative path (../../../modules/pdf-pages) — import the package by name instead.
Boundary violation [package:relative-cross-package] apps/mobile/src/features/ats-checker/original-page.tsx:7— apps/mobile/src/features/ats-checker/original-page.tsx:7 reaches into another package with a relative path (../../../modules/pdf-pages) — import the package by name instead.
Boundary violation [package:relative-cross-package] apps/mobile/src/preview/pipeline.ts:1— apps/mobile/src/preview/pipeline.ts:1 reaches into another package with a relative path (../../modules/pdf-pages) — import the package by name instead.
Boundary violation [package:relative-cross-package] apps/mobile/src/preview/pipeline.ts:5— apps/mobile/src/preview/pipeline.ts:5 reaches into another package with a relative path (../../modules/pdf-pages) — import the package by name instead.
Boundary violation [package:relative-cross-package] apps/mobile/src/shell/key-commands.ts:1— apps/mobile/src/shell/key-commands.ts:1 reaches into another package with a relative path (../../modules/key-commands) — import the package by name instead.
Boundary violation [package:relative-cross-package] apps/mobile/src/shell/key-commands.ts:4— apps/mobile/src/shell/key-commands.ts:4 reaches into another package with a relative path (../../modules/key-commands) — import the package by name instead.
Boundary violation [package:third-party-deep-import] apps/mobile/src/ui/icon.tsx:4— apps/mobile/src/ui/icon.tsx:4 imports phosphor-react-native/src/icons/ArrowClockwise, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead.
Boundary violation [package:third-party-deep-import] apps/mobile/src/ui/icon.tsx:5— apps/mobile/src/ui/icon.tsx:5 imports phosphor-react-native/src/icons/ArrowCounterClockwise, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead.
Boundary violation [package:third-party-deep-import] apps/mobile/src/ui/icon.tsx:6— apps/mobile/src/ui/icon.tsx:6 imports phosphor-react-native/src/icons/ArrowDown, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead.
Boundary violation [package:third-party-deep-import] apps/mobile/src/ui/icon.tsx:7— apps/mobile/src/ui/icon.tsx:7 imports phosphor-react-native/src/icons/ArrowLeft, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead.
Boundary violation [package:third-party-deep-import] apps/mobile/src/ui/icon.tsx:8— apps/mobile/src/ui/icon.tsx:8 imports phosphor-react-native/src/icons/ArrowRight, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead.
Boundary violation [package:third-party-deep-import] apps/mobile/src/ui/icon.tsx:9— apps/mobile/src/ui/icon.tsx:9 imports phosphor-react-native/src/icons/ArrowsClockwise, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead.
Boundary violation [package:third-party-deep-import] apps/mobile/src/ui/icon.tsx:10— apps/mobile/src/ui/icon.tsx:10 imports phosphor-react-native/src/icons/ArrowsDownUp, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead.
Boundary violation [package:third-party-deep-import] apps/mobile/src/ui/icon.tsx:11— apps/mobile/src/ui/icon.tsx:11 imports phosphor-react-native/src/icons/ArrowsInLineVertical, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead.
Boundary violation [package:third-party-deep-import] apps/mobile/src/ui/icon.tsx:12— apps/mobile/src/ui/icon.tsx:12 imports phosphor-react-native/src/icons/ArrowsInSimple, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead.
Boundary violation [package:third-party-deep-import] apps/mobile/src/ui/icon.tsx:13— apps/mobile/src/ui/icon.tsx:13 imports phosphor-react-native/src/icons/ArrowsLeftRight, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead.
Boundary violation [package:third-party-deep-import] apps/mobile/src/ui/icon.tsx:14— apps/mobile/src/ui/icon.tsx:14 imports phosphor-react-native/src/icons/ArrowsOutSimple, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead.
Boundary violation [package:third-party-deep-import] apps/mobile/src/ui/icon.tsx:15— apps/mobile/src/ui/icon.tsx:15 imports phosphor-react-native/src/icons/ArrowSquareOut, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead.
Boundary violation [package:third-party-deep-import] apps/mobile/src/ui/icon.tsx:16— apps/mobile/src/ui/icon.tsx:16 imports phosphor-react-native/src/icons/ArrowUp, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead.
Boundary violation [package:third-party-deep-import] apps/mobile/src/ui/icon.tsx:17— apps/mobile/src/ui/icon.tsx:17 imports phosphor-react-native/src/icons/ArrowUpRight, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead.
Boundary violation [package:third-party-deep-import] apps/mobile/src/ui/icon.tsx:18— apps/mobile/src/ui/icon.tsx:18 imports phosphor-react-native/src/icons/ArrowUUpLeft, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead.
Boundary violation [package:third-party-deep-import] apps/mobile/src/ui/icon.tsx:19— apps/mobile/src/ui/icon.tsx:19 imports phosphor-react-native/src/icons/ArrowUUpRight, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead.
Swallowed exception (empty catch) packages/pdf/src/forme/font-subset.ts:93— 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) packages/api/src/features/web-access/builtin.ts:121— `.catch(() => {})` handles the rejection by doing nothing — the failure is discarded with no log and no rethrow, and the chain carries on as if the work succeeded. Log it through whatever this codebase already uses to report problems, hand it to a caller that can (`next(error)`, a returned rejection), or don't catch it.
Swallowed exception (empty catch) packages/api/src/features/statistics/service.ts:40— 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) packages/api/src/features/statistics/service.ts:65— 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) packages/api/src/features/resume/events.ts:59— 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) packages/api/src/features/resume/events.ts:74— `.catch(() => {})` handles the rejection by doing nothing — the failure is discarded with no log and no rethrow, and the chain carries on as if the work succeeded. Log it through whatever this codebase already uses to report problems, hand it to a caller that can (`next(error)`, a returned rejection), or don't catch it.
Swallowed exception (empty catch) packages/api/src/features/resume/events.ts:144— `.catch(() => {})` handles the rejection by doing nothing — the failure is discarded with no log and no rethrow, and the chain carries on as if the work succeeded. Log it through whatever this codebase already uses to report problems, hand it to a caller that can (`next(error)`, a returned rejection), or don't catch it.
Swallowed exception (empty catch) packages/api/src/features/resume/events.ts:180— `.catch(() => {})` handles the rejection by doing nothing — the failure is discarded with no log and no rethrow, and the chain carries on as if the work succeeded. Log it through whatever this codebase already uses to report problems, hand it to a caller that can (`next(error)`, a returned rejection), or don't catch it.
Swallowed exception (empty catch) packages/api/src/features/resume/pdf-analysis.ts:15— `.catch(() => {})` handles the rejection by doing nothing — the failure is discarded with no log and no rethrow, and the chain carries on as if the work succeeded. Log it through whatever this codebase already uses to report problems, hand it to a caller that can (`next(error)`, a returned rejection), or don't catch it.
Swallowed exception (empty catch) packages/api/src/features/resume/pdf-analysis.ts:33— `.catch(() => {})` handles the rejection by doing nothing — the failure is discarded with no log and no rethrow, and the chain carries on as if the work succeeded. Log it through whatever this codebase already uses to report problems, hand it to a caller that can (`next(error)`, a returned rejection), or don't catch it.
Swallowed exception (empty catch) packages/api/src/features/applications/service.ts:395— `.catch(() => {})` handles the rejection by doing nothing — the failure is discarded with no log and no rethrow, and the chain carries on as if the work succeeded. Log it through whatever this codebase already uses to report problems, hand it to a caller that can (`next(error)`, a returned rejection), or don't catch it.
Swallowed exception (empty catch) packages/api/src/features/applications/service.ts:586— `.catch(() => {})` handles the rejection by doing nothing — the failure is discarded with no log and no rethrow, and the chain carries on as if the work succeeded. Log it through whatever this codebase already uses to report problems, hand it to a caller that can (`next(error)`, a returned rejection), or don't catch it.
Swallowed exception (empty catch) apps/web/src/routes/dashboard/applications/index.tsx:333— 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) apps/web/src/routes/builder/letter/-components/letter-shell.tsx:201— 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) apps/web/src/libs/webmcp.ts:121— 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) apps/web/src/features/theme/provider.tsx:66— An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Swallowed exception (empty catch) apps/web/src/features/resume/public/public-resume.tsx:63— 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) apps/web/src/features/resume/import/read-file.ts:84— An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Swallowed exception (empty catch) apps/web/src/features/resume/editor/check/parser-view.tsx:21— `.catch(() => {})` handles the rejection by doing nothing — the failure is discarded with no log and no rethrow, and the chain carries on as if the work succeeded. Log it through whatever this codebase already uses to report problems, hand it to a caller that can (`next(error)`, a returned rejection), or don't catch it.
Swallowed exception (empty catch) apps/web/src/features/resume/builder/draft.ts:149— 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) apps/web/src/features/resume/builder/draft.ts:157— 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) apps/web/src/features/resume/builder/draft.ts:710— `.catch(() => {})` handles the rejection by doing nothing — the failure is discarded with no log and no rethrow, and the chain carries on as if the work succeeded. Log it through whatever this codebase already uses to report problems, hand it to a caller that can (`next(error)`, a returned rejection), or don't catch it.
Swallowed exception (empty catch) apps/web/src/features/documents/thumbnail-store.ts:44— 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) apps/web/src/features/documents/thumbnail-store.ts:53— 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) apps/web/src/features/documents/documents-page.tsx:335— 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.
+ 12 more in this group — see findings.md.
R4 · Test Coverage· No test reaches this file · ×36
No test reaches this file apps/mobile/src/features/assistant/chat-view.tsx: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 apps/web/src/features/career/today.tsx: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 apps/web/src/features/resume/editor/write/picture-settings.tsx: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 apps/mobile/src/features/workspace/tabs/practise.tsx: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 apps/mobile/src/features/letters/write.tsx: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 apps/web/src/features/homepage/prepare.tsx: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 apps/web/src/features/settings/ai/providers.tsx: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 apps/web/src/features/career/coach.tsx: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 apps/web/src/routes/builder/letter/-components/write-panel.tsx: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 apps/web/src/features/applications/components/application-detail-sheet.tsx: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 apps/web/src/routes/builder/$resumeId/-sidebar/right/sections/layout/pages.tsx: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 apps/mobile/src/features/write/outline.tsx: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 apps/web/src/features/career/schedule-sheet.tsx: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 apps/mobile/src/features/applications-board/board-screen.tsx: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 apps/mobile/src/features/assistant/messages.tsx: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 apps/mobile/src/features/ats-checker/checker.tsx: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 apps/web/src/features/resume/stylesheet/editor.tsx: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 apps/mobile/src/features/workspace/tabs/apply.tsx: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 apps/web/src/features/resume/editor/check/job-match.tsx: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 apps/mobile/src/features/design/advanced.tsx: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 apps/web/src/features/ats-checker/checker.tsx: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 apps/mobile/src/features/write/model.ts:1— No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
No test reaches this file apps/mobile/src/features/application-detail/interview-sheet.tsx: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 apps/mobile/src/features/letters/share.tsx: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 apps/mobile/src/features/write/entry-fields.tsx: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.
Repeated repair: packages/fonts/src/index.ts packages/fonts/src/index.ts:204— packages/fonts/src/index.ts changed 10 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 8 (its worst body is index.resolveBoldFontWeight at line 204), 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(pdf): load CJK resume previews on slow connections (#3633)”; “fix(pdf): use correct font fallback for Unicode arrows (#3617)”; “fix(pdf): render text symbols like ★ instead of failing every PDF (#3583)”; “fix: audit code for reduction”. 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-07-28..2026-10-26, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-28 12:07:53 +01:00' --until='2026-10-26 12:07:53 +01:00' --full-history --no-merges -- packages/fonts/src/index.ts`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Repeated repair: packages/api/src/features/storage/service.ts packages/api/src/features/storage/service.ts:161— packages/api/src/features/storage/service.ts 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 11 (its worst body is LocalStorageService.list at line 161), 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: security hardening across auth, API, AI, imports and deployment (#3662)”; “fix(auth): migrate guest uploads and rewrite asset URLs on account linking (#3653)”; “fix(auth): preserve uploads across account link failures”; “fix(storage): prevent prefix deletion when source files cannot be read”. 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-07-28..2026-10-26, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-28 12:07:53 +01:00' --until='2026-10-26 12:07:53 +01:00' --full-history --no-merges -- packages/api/src/features/storage/service.ts`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Repeated repair: packages/db/src/schema/auth.ts packages/db/src/schema/auth.ts:7— packages/db/src/schema/auth.ts changed 8 times in last 90 days and 5 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 1 (its worst body is auth.lower at line 7), 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: float application bulk actions and enable auth joins (#3675)”; “fix: security hardening across auth, API, AI, imports and deployment (#3662)”; “fix: keep CJK previews and line-break exports rendering, speed up social sign-in (#3605)”; “fix(auth): align account schema with Better Auth 1.7.3 (#3488)”. 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-07-28..2026-10-26, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-28 12:07:53 +01:00' --until='2026-10-26 12:07:53 +01:00' --full-history --no-merges -- packages/db/src/schema/auth.ts`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Repeated repair: packages/api/src/features/resume/public-pdf.ts packages/api/src/features/resume/public-pdf.ts:50— packages/api/src/features/resume/public-pdf.ts changed 7 times in last 90 days and 4 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 12 (its worst body is public-pdf.createPublicResumePdf at line 50), 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(api): exempt resume owner from public PDF password challenge (#3668)”; “fix: security hardening across auth, API, AI, imports and deployment (#3662)”; “fix(api): resolve renamed resume slugs in public PDF, social meta, and download stats (#3658)”; “fix: audit code for reduction”. 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-07-28..2026-10-26, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-28 12:07:53 +01:00' --until='2026-10-26 12:07:53 +01:00' --full-history --no-merges -- packages/api/src/features/resume/public-pdf.ts`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Repeated repair: packages/api/src/middleware/rate-limit/index.ts packages/api/src/middleware/rate-limit/index.ts:24— packages/api/src/middleware/rate-limit/index.ts changed 7 times in last 90 days and 4 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 8 (its worst body is index.getInputKeyPart at line 24), 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(api): multiplex resume update subscriptions and rate limit per user (#3661)”; “fix: security hardening across auth, API, AI, imports and deployment (#3662)”; “fix: audit code for reduction”; “fix(sharing): record public PDF download statistics (#3414)”. 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-07-28..2026-10-26, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-28 12:07:53 +01:00' --until='2026-10-26 12:07:53 +01:00' --full-history --no-merges -- packages/api/src/middleware/rate-limit/index.ts`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Repeated repair: packages/pdf/src/templates/ditgar/DitgarPage.tsx packages/pdf/src/templates/ditgar/DitgarPage.tsx:69— packages/pdf/src/templates/ditgar/DitgarPage.tsx 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 8 (its worst body is DitgarPage.DitgarPage at line 69), 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: audit code for reduction”; “fix(pdf): align Ditgar item headers with body text (#3445)”; “fix: preserve margins on PDF overflow pages (#3422)”; “fix(stylesheet): apply item-header to every header row on every template (#3357)”. 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-07-28..2026-10-26, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-28 12:07:53 +01:00' --until='2026-10-26 12:07:53 +01:00' --full-history --no-merges -- packages/pdf/src/templates/ditgar/DitgarPage.tsx`: 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: apps/web/src/routes/builder/$resumeId/-sidebar/right/sections/page.tsx apps/web/src/routes/builder/$resumeId/-sidebar/right/sections/page.tsx:28— apps/web/src/routes/builder/$resumeId/-sidebar/right/sections/page.tsx changed 5 times in last 90 days and 3 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 3 (its worst body is page.PageSectionForm at line 28), UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “fix(builder): keep numeric drafts finite and within bounds (#3594)”; “fix(pdf): size free-form pages by their content (#3597)”; “fix: clamp page margin values to [0, 100] to prevent crash on paste (#3277)”. 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-07-28..2026-10-26, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-28 12:07:53 +01:00' --until='2026-10-26 12:07:53 +01:00' --full-history --no-merges -- apps/web/src/routes/builder/$resumeId/-sidebar/right/sections/page.tsx`: 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: packages/api/src/features/resume/social-meta.ts packages/api/src/features/resume/social-meta.ts:30— packages/api/src/features/resume/social-meta.ts changed 5 times in last 90 days and 3 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 2 (its worst body is social-meta.getPublicResumeSocialMeta 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: security hardening across auth, API, AI, imports and deployment (#3662)”; “fix(api): resolve renamed resume slugs in public PDF, social meta, and download stats (#3658)”; “fix: audit code for reduction”. 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-07-28..2026-10-26, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-28 12:07:53 +01:00' --until='2026-10-26 12:07:53 +01:00' --full-history --no-merges -- packages/api/src/features/resume/social-meta.ts`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Repeated repair: packages/utils/src/locale.ts packages/utils/src/locale.ts:126— packages/utils/src/locale.ts changed 5 times in last 90 days and 3 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 9 (its worst body is locale.getLocaleScript at line 126), 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(pdf): use correct font fallback for Unicode arrows (#3617)”; “fix(pdf): render text symbols like ★ instead of failing every PDF (#3583)”; “fix(pdf): render emoji via a Noto Emoji script fallback (#3351)”. 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-07-28..2026-10-26, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-28 12:07:53 +01:00' --until='2026-10-26 12:07:53 +01:00' --full-history --no-merges -- packages/utils/src/locale.ts`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Repeated repair: packages/pdf/src/templates/leafish/LeafishPage.tsx packages/pdf/src/templates/leafish/LeafishPage.tsx:60— packages/pdf/src/templates/leafish/LeafishPage.tsx changed 5 times in last 90 days and 3 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 4 (its worst body is LeafishPage.LeafishPage at line 60), 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: repair v6 PDF and builder regressions (#3600)”; “fix: audit code for reduction”; “fix: preserve margins on PDF overflow pages (#3422)”. 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-07-28..2026-10-26, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-28 12:07:53 +01:00' --until='2026-10-26 12:07:53 +01:00' --full-history --no-merges -- packages/pdf/src/templates/leafish/LeafishPage.tsx`: 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: packages/pdf/src/templates/shared/base-template-styles.ts packages/pdf/src/templates/shared/base-template-styles.ts:25— packages/pdf/src/templates/shared/base-template-styles.ts changed 5 times in last 90 days and 3 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 1 (its worst body is base-template-styles.createBaseTemplateStyles at line 25), 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: repair v6 PDF and builder regressions (#3600)”; “fix(pdf): resolve bold text weight from the family's bold face (#3335)”; “fix(pdf): constrain bullet list content width within horizontal margin (#3367)”. 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-07-28..2026-10-26, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-28 12:07:53 +01:00' --until='2026-10-26 12:07:53 +01:00' --full-history --no-merges -- packages/pdf/src/templates/shared/base-template-styles.ts`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Repeated repair: apps/web/src/routes/builder/letter/$coverLetterId.tsx apps/web/src/routes/builder/letter/$coverLetterId.tsx:54— apps/web/src/routes/builder/letter/$coverLetterId.tsx 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 9 (its worst body is $coverLetterId.RouteComponent at line 54), 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: security hardening across auth, API, AI, imports and deployment (#3662)”; “fix(auth): support loopback origins, secure email logs, and SPA redirects”; “fix(cover-letter): localize and customize greeting and signature”. 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-07-28..2026-10-26, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-28 12:07:53 +01:00' --until='2026-10-26 12:07:53 +01:00' --full-history --no-merges -- apps/web/src/routes/builder/letter/$coverLetterId.tsx`: 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.
Focus outline removed inline apps/web/src/features/assistant/conversation.tsx:636— <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 apps/web/src/features/career/coach.tsx:636— <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 apps/web/src/features/career/knowledge/facts.tsx:127— <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 apps/web/src/features/career/knowledge/facts.tsx:267— <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 apps/web/src/features/career/knowledge/preferences.tsx:219— <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 apps/web/src/features/career/knowledge/preferences.tsx:304— <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 apps/web/src/features/career/knowledge/preferences.tsx:360— <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 apps/web/src/features/documents/document-card.tsx:87— <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 apps/web/src/features/resume/share/download-tab.tsx:143— <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 apps/web/src/routes/builder/$resumeId/-components/page-canvas.tsx:87— <section> 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 apps/web/src/routes/builder/letter/-components/letter-page.tsx:110— <section> 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).
X24 · Document value interpolated into markup unescaped· Untrusted text written into markup unescaped · ×10
Untrusted text written into markup unescaped apps/server/src/static/seo.ts:54— `escapeXml(href)` is text this program did not author, and it is written into the start of a URL attribute, where it chooses the scheme through markup this function returns with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. HTML encoding does not help here — a `javascript:` URL contains nothing it changes; allow only http(s) or a relative path.
Untrusted text written into markup unescaped apps/server/src/static/web.ts:237— `escapeAttribute(href)` is text this program did not author, and it is written into the start of a URL attribute, where it chooses the scheme through markup built here with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. HTML encoding does not help here — a `javascript:` URL contains nothing it changes; allow only http(s) or a relative path.
Untrusted text written into markup unescaped apps/server/src/static/web.ts:243— `url` is text this program did not author, and it is written into the start of a URL attribute, where it chooses the scheme through markup this function returns with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. HTML encoding does not help here — a `javascript:` URL contains nothing it changes; allow only http(s) or a relative path.
Untrusted text written into markup unescaped apps/server/src/static/web.ts:454— `escapeAttribute(canonicalUrl)` is text this program did not author, and it is written into the start of a URL attribute, where it chooses the scheme through markup built here with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. HTML encoding does not help here — a `javascript:` URL contains nothing it changes; allow only http(s) or a relative path.
Untrusted text written into markup unescaped apps/web/src/features/homepage/faq.tsx:210— `serializeJsonLd(structuredData)` is text this program did not author, and it is written into the text of an element through `dangerouslySetInnerHTML` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup.
Untrusted text written into markup unescaped REDACTED:68— `html` is text this program did not author, and it is written into the text of an element through `dangerouslySetInnerHTML` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup.
Untrusted text written into markup unescaped REDACTED:82— `escapeXml(node.href)` is text this program did not author, and it is written into the start of a URL attribute, where it chooses the scheme through markup this function returns with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. HTML encoding does not help here — a `javascript:` URL contains nothing it changes; allow only http(s) or a relative path.
Untrusted text written into markup unescaped REDACTED:88— `whitespace` is text this program did not author, and it is written into the text of an element through `insertAdjacentHTML` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup.
Untrusted text written into markup unescaped REDACTED:97— `whitespace` is text this program did not author, and it is written into the text of an element through `insertAdjacentHTML` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup.
Untrusted text written into markup unescaped REDACTED:112— `child.innerHTML` is text this program did not author, and it is written into the text of an element through `innerHTML` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup.
Cross-context type DbOrTx (db → api) packages/api/src/features/documents/ownership.ts:10— DbOrTx (context db) is exposed in api's public surface via ownership.lockUser — couples the contexts.
Cross-context type DbOrTx (db → api) packages/api/src/features/documents/version-history.ts:80— DbOrTx (context db) is exposed in api's public surface via version-history.createVersionHistory.write — couples the contexts.
Cross-context type DbOrTx (db → api) packages/api/src/features/cover-letters/versions.ts:33— DbOrTx (context db) is exposed in api's public surface via versions.writeLetterVersion — couples the contexts.
Cross-context type DbOrTx (db → api) packages/api/src/features/cover-letters/embedded.ts:19— DbOrTx (context db) is exposed in api's public surface via embedded.adoptEmbeddedLetters — couples the contexts.
Cross-context type DbOrTx (db → api) packages/api/src/features/resume/slugs.ts:26— DbOrTx (context db) is exposed in api's public surface via slugs.findFreeSlug — couples the contexts.
Cross-context type DbOrTx (db → api) packages/api/src/features/resume/slugs.ts:64— DbOrTx (context db) is exposed in api's public surface via slugs.recordSlugChange — couples the contexts.
Cross-context type DbOrTx (db → api) packages/api/src/features/resume/version-history.ts:21— DbOrTx (context db) is exposed in api's public surface via version-history.writeVersion — couples the contexts.
Cross-context type DbOrTx (db → api) packages/api/src/features/applications/service.ts:137— DbOrTx (context db) is exposed in api's public surface via service.recordSentResume — couples the contexts.
AC2 · Forms & labels· <TextInput> field component without a label · ×6
<TextInput> field component without a label apps/mobile/src/components/collection-header.tsx:66— 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.
<TextInput> field component without a label apps/mobile/src/features/assistant/chat-view.tsx:784— 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.
<TextInput> field component without a label apps/mobile/src/features/assistant/messages.tsx:372— 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.
<TextInput> field component without a label apps/mobile/src/features/design/advanced.tsx:496— This UI-library field component has no label / aria-label / aria-labelledby / id — and neither does anything it renders (a name prop is the form-submission key, not a label) — so it likely renders an unlabelled control. Name it 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.
<TextInput> field component without a label apps/mobile/src/features/design/controls.tsx:201— This UI-library field component has no label / aria-label / aria-labelledby / id — and neither does anything it renders (a name prop is the form-submission key, not a label) — so it likely renders an unlabelled control. Name it 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.
<TextInput> field component without a label apps/mobile/src/features/search/search-screen.tsx:359— 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.
Off the main sequence: @reactive-resume/forme-native — @reactive-resume/forme-native: abstractness 0.00, instability 0.00, distance 1.00 — zone of pain — concrete and depended on by 1 project(s), so it's rigid to change.
Off the main sequence: @reactive-resume/utils — @reactive-resume/utils: abstractness 0.00, instability 0.00, distance 1.00 — zone of pain — concrete and depended on by 16 project(s), so it's rigid to change.
Off the main sequence: @reactive-resume/schema — @reactive-resume/schema: abstractness 0.00, instability 0.07, distance 0.93 — zone of pain — concrete and depended on by 13 project(s), so it's rigid to change.
Off the main sequence: @reactive-resume/resume — @reactive-resume/resume: abstractness 0.00, instability 0.20, distance 0.80 — zone of pain — concrete and depended on by 8 project(s), so it's rigid to change.
Off the main sequence: @reactive-resume/env — @reactive-resume/env: abstractness 0.00, instability 0.25, distance 0.75 — zone of pain — concrete and depended on by 6 project(s), so it's rigid to change.
Off the main sequence: @reactive-resume/fonts — @reactive-resume/fonts: abstractness 0.00, instability 0.25, distance 0.75 — zone of pain — concrete and depended on by 3 project(s), so it's rigid to change.
AC2 · Forms & labels· <fieldset> without a <legend> · ×5
<fieldset> without a <legend> apps/web/src/features/resume/editor/write/basics-card.tsx:81— A fieldset groups related controls but has no <legend> to name the group. Add a <legend> as its first child — or, if the group already has a visible caption beside it (or the fieldset is there only to disable its subtree and carries no group box), point aria-labelledby at that caption's id instead, which names the group without rendering a second one.
<fieldset> without a <legend> apps/web/src/features/resume/editor/write/entry-card.tsx:175— A fieldset groups related controls but has no <legend> to name the group. Add a <legend> as its first child — or, if the group already has a visible caption beside it (or the fieldset is there only to disable its subtree and carries no group box), point aria-labelledby at that caption's id instead, which names the group without rendering a second one.
<fieldset> without a <legend> apps/web/src/features/resume/editor/write/entry-card.tsx:239— A fieldset groups related controls but has no <legend> to name the group. Add a <legend> as its first child — or, if the group already has a visible caption beside it (or the fieldset is there only to disable its subtree and carries no group box), point aria-labelledby at that caption's id instead, which names the group without rendering a second one.
<fieldset> without a <legend> apps/web/src/routes/builder/$resumeId/-components/design-panel.tsx:93— A fieldset groups related controls but has no <legend> to name the group. Add a <legend> as its first child — or, if the group already has a visible caption beside it (or the fieldset is there only to disable its subtree and carries no group box), point aria-labelledby at that caption's id instead, which names the group without rendering a second one.
<fieldset> without a <legend> apps/web/src/routes/builder/$resumeId/-components/design-panel.tsx:152— A fieldset groups related controls but has no <legend> to name the group. Add a <legend> as its first child — or, if the group already has a visible caption beside it (or the fieldset is there only to disable its subtree and carries no group box), point aria-labelledby at that caption's id instead, which names the group without rendering a second one.
AC6 · Visual & motion safety· Animation without a prefers-reduced-motion guard · ×5
Animation without a prefers-reduced-motion guard apps/web/index.html:85— `.initial-loader__spinner` moves (`animation: app-spin 0.7s 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 packages/ui/src/components/toast.tsx:28— <span> moves — its `animate-[toast-fuse_linear_forwards]` 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 apps/web/src/index.css:92— `html:active-view-transition-type(page)::view-transition-new(root)` moves (`animation: var(--d2) var(--ease) both vt-page-in`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce.
Animation without a prefers-reduced-motion guard apps/web/src/index.css:124— `html:active-view-transition-type(forward)::view-transition-new(root)` moves (`animation: var(--d2) var(--ease) both vt-push-in`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce.
Animation without a prefers-reduced-motion guard apps/web/src/index.css:128— `html:active-view-transition-type(back)::view-transition-new(root)` moves (`animation: var(--d2) var(--ease) both vt-pop-in`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce.
Cross-context type AuthProvider (auth → web) apps/web/src/features/settings/account/auth-hooks.ts:14— AuthProvider (context auth) is exposed in web's public surface via auth-hooks.getProviderName — couples the contexts.
Cross-context type AuthProvider (auth → web) apps/web/src/features/settings/account/auth-hooks.ts:72— AuthProvider (context auth) is exposed in web's public surface via auth-hooks.useAuthAccounts.getAccountByProviderId — couples the contexts.
Cross-context type AuthProvider (auth → web) apps/web/src/features/settings/account/auth-hooks.ts:77— AuthProvider (context auth) is exposed in web's public surface via auth-hooks.useAuthAccounts.hasAccount — couples the contexts.
Cross-context type AuthProvider (auth → web) apps/web/src/features/settings/account/auth-hooks.ts:93— AuthProvider (context auth) is exposed in web's public surface via auth-hooks.useAuthProviderActions.link — couples the contexts.
Cross-context type AuthProvider (auth → web) apps/web/src/features/settings/account/auth-hooks.ts:128— AuthProvider (context auth) is exposed in web's public surface via auth-hooks.useAuthProviderActions.unlink — couples the contexts.
R4 · Test Coverage· This test file cannot be loaded · ×4
This test file cannot be loaded apps/server/src/static/agent-skills.test.ts:8— apps/server/src/static/agent-skills.test.ts:8 imports '../../../../plugins/reactive-resume/skills', which names no file in this repository — and no rule in its .gitignore chain could cover one, so no build writes it either. The import throws as the runner collects this file, so none of its test cases run and nothing it was written to verify is verified. Restore the missing module or delete the test. It is excluded from the reachability measured above, because a file that cannot load reaches nothing.
This test file cannot be loaded packages/api/src/features/career/jobs.integration.test.ts:97— packages/api/src/features/career/jobs.integration.test.ts:97 imports '../../../../../migrations/', which names no file in this repository — and no rule in its .gitignore chain could cover one, so no build writes it either. The import throws as the runner collects this file, so none of its test cases run and nothing it was written to verify is verified. Restore the missing module or delete the test. It is excluded from the reachability measured above, because a file that cannot load reaches nothing.
This test file cannot be loaded packages/api/src/features/career/service.integration.test.ts:95— packages/api/src/features/career/service.integration.test.ts:95 imports '../../../../../migrations/', which names no file in this repository — and no rule in its .gitignore chain could cover one, so no build writes it either. The import throws as the runner collects this file, so none of its test cases run and nothing it was written to verify is verified. Restore the missing module or delete the test. It is excluded from the reachability measured above, because a file that cannot load reaches nothing.
This test file cannot be loaded packages/db/src/migrations.integration.test.ts:14— packages/db/src/migrations.integration.test.ts:14 imports '../../../migrations', which names no file in this repository — and no rule in its .gitignore chain could cover one, so no build writes it either. The import throws as the runner collects this file, so none of its test cases run and nothing it was written to verify is verified. Restore the missing module or delete the test. It is excluded from the reachability measured above, because a file that cannot load reaches nothing.
X2 · Cancellation propagation· Async function without AbortSignal · ×4
Async function without AbortSignal: fetchText tooling/locales/generate-region-zones.mjs:13— `fetchText` 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: fetchPublicResumePdf apps/web/src/features/resume/public/public-pdf.ts:15— `fetchPublicResumePdf` 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: fetchSample apps/web/src/features/ats-checker/checker.tsx:149— `fetchSample` 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: uiFontFace apps/web/src/features/applications/components/insights-view.tsx:217— `uiFontFace` 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 })`.
Swallowed exception (caught, then discarded) packages/schema/src/resume/period.ts:112— `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) packages/api/src/features/applications/posting.ts:130— `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) apps/web/src/features/auth/redirect.ts:16— `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.
issues.describeFinding (cyclomatic 30) apps/mobile/src/features/check/issues.ts:112— issues.describeFinding has cyclomatic complexity 30 (threshold 15). Of this number, 24 points are the body's own statements and 6 belong to 3 function literals inside it that branch. To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Where every arm is uniform — the same kind of value, with no behaviour of its own — a table keyed by the case is the shorter form; wherever the arms carry different data or different behaviour, keep them as cases, because collapsing those trades an explicit, reviewable set of cases for nothing.
issues.describeFinding (cyclomatic 30) apps/web/src/features/resume/editor/check/issues.ts:117— issues.describeFinding has cyclomatic complexity 30 (threshold 15). Of this number, 24 points are the body's own statements and 6 belong to 3 function literals inside it that branch. To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Where every arm is uniform — the same kind of value, with no behaviour of its own — a table keyed by the case is the shorter form; wherever the arms carry different data or different behaviour, keep them as cases, because collapsing those trades an explicit, reviewable set of cases for nothing.
values.compileProgram::compileRule (cognitive 48) packages/resume/src/stylesheet/values.ts:554— values.compileProgram::compileRule has cognitive complexity 48 (threshold 15). Drivers by points: if/else 12 (25 pts), ternaries 7 (15 pts), boolean chains 5, loops 2 (3 pts) (nesting depth added 22). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body. This shape REPEATS in the file: one other method here (values.compileProgram::visit) 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.
values.compileProgram::visit (cognitive 20) packages/resume/src/stylesheet/values.ts:641— values.compileProgram::visit has cognitive complexity 20 (threshold 15). Drivers by points: if/else 7 (14 pts), ternaries 1 (3 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. This shape REPEATS in the file: one other method here (values.compileProgram::compileRule) 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.
issues.describeFinding (cognitive 17) apps/mobile/src/features/check/issues.ts:112— issues.describeFinding has cognitive complexity 17 (threshold 15). Drivers by points: if/else 4 (9 pts), loops 2 (4 pts), ternaries 1 (2 pts), boolean chains 1, match/switch 1 (nesting depth added 8). Most of this is not in the body itself: 3 of the 17 points are its own statements and the rest belongs to 3 function literals inside it that branch (lines 306, 280, 220). 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.
issues.describeFinding (cognitive 17) apps/web/src/features/resume/editor/check/issues.ts:117— issues.describeFinding has cognitive complexity 17 (threshold 15). Drivers by points: if/else 4 (9 pts), loops 2 (4 pts), ternaries 1 (2 pts), boolean chains 1, match/switch 1 (nesting depth added 8). Most of this is not in the body itself: 3 of the 17 points are its own statements and the rest belongs to 3 function literals inside it that branch (lines 311, 285, 225). 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.
messages.ProposalCard::describe (cognitive 16) apps/mobile/src/features/workspace/tabs/messages.tsx:202— messages.ProposalCard::describe has cognitive complexity 16 (threshold 15). Drivers by points: ternaries 4 (9 pts), if/else 3 (6 pts), match/switch 1 (nesting depth added 8). 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. This shape REPEATS in the file: one other method here (messages.ProposalCard) 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.
messages.ProposalCard::describe (cognitive 16) apps/web/src/features/career/workspace/messages.tsx:217— messages.ProposalCard::describe has cognitive complexity 16 (threshold 15). Drivers by points: ternaries 4 (9 pts), if/else 3 (6 pts), match/switch 1 (nesting depth added 8). 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.
Cross-context type AtsCategory (resume → mobile) apps/mobile/src/features/check/issues.ts:29— AtsCategory (context resume) is exposed in mobile's public surface via issues.getCategoryName — couples the contexts.
Cross-context type AtsCategory (resume → mobile) apps/mobile/src/features/check/issues.ts:38— AtsCategory (context resume) is exposed in mobile's public surface via issues.getCategoryDescription — couples the contexts.
Cross-context type PageMapTarget (pdf → mobile) apps/mobile/src/features/check/model.ts:52— PageMapTarget (context pdf) is exposed in mobile's public surface via model.sameTarget — couples the contexts.
Cross-context type PageMapTarget (pdf → mobile) apps/mobile/src/features/check/model.ts:67— PageMapTarget (context pdf) is exposed in mobile's public surface via model.termTargets — couples the contexts.
Cross-context type PdfCategory (resume → web) apps/web/src/features/ats-checker/messages.ts:344— PdfCategory (context resume) is exposed in web's public surface via messages.getPdfCategoryLabel — couples the contexts.
Cross-context type PdfCategory (resume → web) apps/web/src/features/ats-checker/messages.ts:355— PdfCategory (context resume) is exposed in web's public surface via messages.getPdfCategoryDescription — couples the contexts.
Cross-context type AtsCategory (resume → web) apps/web/src/features/resume/editor/check/issues.ts:32— AtsCategory (context resume) is exposed in web's public surface via issues.getCategoryName — couples the contexts.
Cross-context type AtsCategory (resume → web) apps/web/src/features/resume/editor/check/issues.ts:41— AtsCategory (context resume) is exposed in web's public surface via issues.getCategoryDescription — couples the contexts.
Cross-context type ResumeExportTarget (resume → web) apps/web/src/features/resume/export/use-resume-export.ts:54— ResumeExportTarget (context resume) is exposed in web's public surface via use-resume-export.getDefaultFileName — couples the contexts.
Cross-context type ResumeExportTarget (resume → web) apps/web/src/features/resume/export/use-resume-export.ts:67— ResumeExportTarget (context resume) is exposed in web's public surface via use-resume-export.createExportFile — couples the contexts.
Cross-context type Script (utils → pdf) packages/pdf/src/hooks/use-register-fonts.ts:187— Script (context utils) is exposed in pdf's public surface via use-register-fonts.resumeContentScripts — couples the contexts.
Cross-context type Script (utils → pdf) packages/pdf/src/hooks/use-register-fonts.ts:218— Script (context utils) is exposed in pdf's public surface via use-register-fonts.resolvePdfFonts — couples the contexts.
R10 · Code Duplication· Duplicated block with local edits (128 matched lines × 2 locations) · ×2
Duplicated block with local edits (128 matched lines × 2 locations) apps/mobile/src/features/workspace/tabs/fit.tsx:82— apps/mobile/src/features/workspace/tabs/fit.tsx:82 · apps/web/src/features/career/workspace/fit.tsx:124 — the two spans are one implementation copied and then locally edited — 849 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 (128 matched lines × 2 locations) packages/pdf/src/templates/lapras/LaprasPage.tsx:17— packages/pdf/src/templates/lapras/LaprasPage.tsx:17 · packages/pdf/src/templates/onyx/OnyxPage.tsx:17 — the two spans are one implementation copied and then locally edited — 816 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 (84 matched lines × 2 locations) · ×2
Duplicated block with local edits (84 matched lines × 2 locations) apps/mobile/src/features/workspace/hooks.ts:60— apps/mobile/src/features/workspace/hooks.ts:60 · apps/web/src/features/career/hooks.ts:73 — the two spans are one implementation copied and then locally edited — 671 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 (84 matched lines × 2 locations) apps/web/src/features/assistant/conversation.tsx:272— apps/web/src/features/assistant/conversation.tsx:272 · apps/web/src/features/career/coach-chat.tsx:217 — the two spans are one implementation copied and then locally edited — 414 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 (59 matched lines × 2 locations) · ×2
Duplicated block with local edits (59 matched lines × 2 locations) apps/mobile/src/features/applications-board/insights.ts:21— apps/mobile/src/features/applications-board/insights.ts:21 · apps/web/src/features/applications/insights.ts:100 — the two spans are one implementation copied and then locally edited — 620 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 (59 matched lines × 2 locations) apps/mobile/src/features/letters/page.tsx:58— apps/mobile/src/features/letters/page.tsx:58 · apps/mobile/src/preview/page.tsx:127 — the two spans are one implementation copied and then locally edited — 399 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 (51 matched lines × 2 locations) · ×2
Duplicated block with local edits (51 matched lines × 2 locations) apps/mobile/src/features/assistant/coach-screen.tsx:73— apps/mobile/src/features/assistant/coach-screen.tsx:73 · apps/mobile/src/features/workspace/coach-sheet.tsx:41 — the two spans are one implementation copied and then locally edited — 306 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 (51 matched lines × 2 locations) packages/db/src/schema/auth.ts:61— packages/db/src/schema/auth.ts:61 · packages/db/src/schema/auth.ts:383 — the two spans are one implementation copied and then locally edited — 411 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.
Dead file (~470 LoC) apps/mobile/src/features/documents/new-document.tsx— no import path from any entry point (277 application, 56 tooling, 375 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (apps/mobile/app/new.tsx) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it
Dead file (~470 LoC) apps/mobile/src/features/workspace/tabs/prepare.tsx— no import path from any entry point (277 application, 56 tooling, 375 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (apps/mobile/app/applications/[id]/[tab].tsx) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it
X17 · Uncapped recursion over a caller-supplied document· Recursive walk over a caller-supplied document has no depth cap · ×2
Recursive walk over a caller-supplied document has no depth cap apps/web/src/features/resume/import/read-file.ts:36— `detectJsonImportKind` is exported and takes `parsed: unknown` from its caller, and it calls itself at line 36 (`detectJsonImportKind`) with a piece of `parsed` — and nowhere in `detectJsonImportKind` is there a depth parameter, a descent counter, or any other cap. The walk therefore spends one stack frame per LEVEL of the value it is handed, so the nesting of the caller's document — not this code — decides how deep the stack goes. JavaScript sets no limit of its own on that nesting: `JSON.parse` accepts any depth, so a 100,000-byte body — inside Express's default 100kb limit — parses to 50,000 levels, and a walk like this one throws `RangeError: Maximum call stack size exceeded` long before it reaches the bottom. Wherever that throw lands, the work fails: a request errors, and a walk running outside any `try` — an event handler, a timer, a promise nobody awaits — takes the Node process down with every other request in flight. Thread a depth argument through `detectJsonImportKind` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack.
Recursive walk over a caller-supplied document has no depth cap apps/mobile/src/features/documents/import-file.ts:24— `jsonImportFormat` is exported and takes `value: unknown` from its caller, and it calls itself at line 24 (`jsonImportFormat`) with a piece of `value` — and nowhere in `jsonImportFormat` is there a depth parameter, a descent counter, or any other cap. The walk therefore spends one stack frame per LEVEL of the value it is handed, so the nesting of the caller's document — not this code — decides how deep the stack goes. JavaScript sets no limit of its own on that nesting: `JSON.parse` accepts any depth, so a 100,000-byte body — inside Express's default 100kb limit — parses to 50,000 levels, and a walk like this one throws `RangeError: Maximum call stack size exceeded` long before it reaches the bottom. Wherever that throw lands, the work fails: a request errors, and a walk running outside any `try` — an event handler, a timer, a promise nobody awaits — takes the Node process down with every other request in flight. Thread a depth argument through `jsonImportFormat` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack.
AC2 · Forms & labels· <Textarea> field component without a label · ×1
<Textarea> field component without a label apps/web/src/features/applications/components/application-form-sheet.tsx:160— 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.
AC2 · Forms & labels· <Combobox> field component without a label · ×1
<Combobox> field component without a label apps/web/src/features/settings/integrations/components/ai-provider-picker.tsx:33— 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.
AC3 · Page structure· Page without a main landmark · ×1
Page without a main landmark apps/web/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 477 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.
add-sheet.AddApplicationSheet (cyclomatic 122) apps/mobile/src/features/applications/add-sheet.tsx:48— add-sheet.AddApplicationSheet has cyclomatic complexity 122 (threshold 15). Of this number, 71 points are the body's own statements and 51 belong to 20 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.
practise.Session (cyclomatic 85) apps/web/src/features/career/workspace/practise.tsx:218— practise.Session has cyclomatic complexity 85 (threshold 15). Of this number, 44 points are the body's own statements and 41 belong to 16 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.
cascade.resolveStylesheet (cyclomatic 85) packages/resume/src/stylesheet/cascade.ts:554— cascade.resolveStylesheet has cyclomatic complexity 85 (threshold 15). Of this number, 81 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.
new-document.NewDocument (cyclomatic 78) apps/mobile/src/features/documents/new-document.tsx:24— new-document.NewDocument has cyclomatic complexity 78 (threshold 15). Of this number, 37 points are the body's own statements and 41 belong to 10 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.
library.DocumentsLibrary (cyclomatic 75) apps/mobile/src/features/documents/library.tsx:159— library.DocumentsLibrary has cyclomatic complexity 75 (threshold 15). Of this number, 55 points are the body's own statements and 20 belong to 17 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.
practise.Session (cyclomatic 72) apps/mobile/src/features/workspace/tabs/practise.tsx:185— practise.Session has cyclomatic complexity 72 (threshold 15). Of this number, 37 points are the body's own statements and 35 belong to 13 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.
list-screen.ApplicationsList (cyclomatic 71) apps/mobile/src/features/applications/list-screen.tsx:55— list-screen.ApplicationsList has cyclomatic complexity 71 (threshold 15). Of this number, 48 points are the body's own statements and 23 belong to 8 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.
parse.parseDeepLink (cyclomatic 68) apps/mobile/src/linking/parse.ts:39— parse.parseDeepLink has cyclomatic complexity 68 (threshold 15). Of this number, 65 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.
to-forme.convertNode (cyclomatic 67) packages/pdf/src/forme/to-forme.tsx:466— to-forme.convertNode has cyclomatic complexity 67 (threshold 15). Of this number, 58 points are the body's own statements and 9 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.
coach.CoachPage (cyclomatic 65) apps/web/src/features/career/coach.tsx:104— coach.CoachPage has cyclomatic complexity 65 (threshold 15). Of this number, 40 points are the body's own statements and 25 belong to 14 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.
style.toFormeStyle (cyclomatic 65) packages/pdf/src/forme/style.ts:373— style.toFormeStyle has cyclomatic complexity 65 (threshold 15). Of this number, 63 points are the body's own statements and 2 belong to 2 function literals inside it that branch. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
provider-editor.ProviderForm (cyclomatic 60) apps/mobile/src/features/ai/provider-editor.tsx:75— provider-editor.ProviderForm has cyclomatic complexity 60 (threshold 15). Of this number, 36 points are the body's own statements and 24 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.
chat-view.Conversation (cyclomatic 58) apps/mobile/src/features/assistant/chat-view.tsx:241— chat-view.Conversation has cyclomatic complexity 58 (threshold 15). Of this number, 24 points are the body's own statements and 34 belong to 20 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.
schedule-sheet.ScheduleSheet (cyclomatic 56) apps/web/src/features/career/schedule-sheet.tsx:129— schedule-sheet.ScheduleSheet has cyclomatic complexity 56 (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. This shape REPEATS in the file: one other method here (schedule-sheet.ScheduleSheet::onSave) 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.
board-screen.Board (cyclomatic 55) apps/mobile/src/features/applications-board/board-screen.tsx:85— board-screen.Board has cyclomatic complexity 55 (threshold 15). Of this number, 20 points are the body's own statements and 35 belong to 17 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.
today.TodayScreen (cyclomatic 55) apps/mobile/src/features/career/today.tsx:33— today.TodayScreen has cyclomatic complexity 55 (threshold 15). Of this number, 31 points are the body's own statements and 24 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.
shell.Workspace (cyclomatic 55) apps/web/src/features/career/workspace/shell.tsx:110— shell.Workspace has cyclomatic complexity 55 (threshold 15). Of this number, 31 points are the body's own statements and 24 belong 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.
scroll.useScrollScenes (cyclomatic 54) apps/web/src/features/homepage/scroll.ts:153— scroll.useScrollScenes has cyclomatic complexity 54 (threshold 15). Most of this is not in the body itself: 1 of the 54 points is its own statement and the rest belongs to 6 function literals inside it that branch (lines 214, 169, 316, …). 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.
link.LinkTab (cyclomatic 53) apps/mobile/src/features/share/link.tsx:32— link.LinkTab has cyclomatic complexity 53 (threshold 15). Of this number, 33 points are the body's own statements and 20 belong to 8 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.
web-access.WebAccessSection (cyclomatic 53) apps/web/src/features/settings/ai/web-access.tsx:30— web-access.WebAccessSection has cyclomatic complexity 53 (threshold 15). Of this number, 50 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.
interview-sheet.InterviewForm (cyclomatic 51) apps/mobile/src/features/application-detail/interview-sheet.tsx:121— interview-sheet.InterviewForm has cyclomatic complexity 51 (threshold 15). Of this number, 28 points are the body's own statements and 23 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.
interview-dialog.InterviewDialog (cyclomatic 50) apps/web/src/features/applications/components/interview-dialog.tsx:145— interview-dialog.InterviewDialog has cyclomatic complexity 50 (threshold 15). Of this number, 33 points are the body's own statements and 17 belong to 10 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.
html.parseRichText (cyclomatic 47) REDACTED:63— html.parseRichText has cyclomatic complexity 47 (threshold 15). Of this number, 37 points are the body's own statements and 10 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.
chip-input.ChipInput (cyclomatic 47) apps/web/src/components/input/chip-input.tsx:157— chip-input.ChipInput has cyclomatic complexity 47 (threshold 15). Most of this is not in the body itself: 9 of the 47 points are its own statements and the rest belongs to 10 function items inside it that branch (handleDragEnd, handleKeyDown, removeChip, …). 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.
html-to-docx.processBlockElement (cyclomatic 47) packages/docx/src/html-to-docx.ts:149— html-to-docx.processBlockElement has cyclomatic complexity 47 (threshold 15). Of this number, 44 points are the body's own statements and 3 belong to 2 function items inside it that branch. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
layout.ListRow (cyclomatic 46) apps/mobile/src/ui/layout.tsx:55— layout.ListRow has cyclomatic complexity 46 (threshold 15). Of this number, 35 points are the body's own statements and 11 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.
search-screen.SearchScreen (cyclomatic 46) apps/mobile/src/features/search/search-screen.tsx:41— search-screen.SearchScreen has cyclomatic complexity 46 (threshold 15). Of this number, 23 points are the body's own statements and 23 belong to 13 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.
shell.ContextColumn (cyclomatic 46) apps/web/src/features/career/workspace/shell.tsx:465— shell.ContextColumn has cyclomatic complexity 46 (threshold 15). Of this number, 41 points are the body's own statements and 5 belong to 4 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.
config.getAuthConfig (cyclomatic 45) packages/auth/src/config.ts:257— config.getAuthConfig has cyclomatic complexity 45 (threshold 15). Most of this is not in the body itself: 11 of the 45 points are its own statements and the rest belongs to 6 function literals inside it that branch (lines 330, 484, 307, …). 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.
web-access.WebAccessSettings (cyclomatic 44) apps/mobile/src/features/ai/web-access.tsx:37— web-access.WebAccessSettings has cyclomatic complexity 44 (threshold 15). Of this number, 39 points are the body's own statements and 5 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.
document-sheets.DocumentSheets (cyclomatic 44) apps/mobile/src/features/documents/document-sheets.tsx:26— document-sheets.DocumentSheets has cyclomatic complexity 44 (threshold 15). Of this number, 35 points are the body's own statements and 9 belong to 9 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.
page.ResumePage (cyclomatic 44) apps/mobile/src/preview/page.tsx:25— page.ResumePage has cyclomatic complexity 44 (threshold 15). Most of this is not in the body itself: 15 of the 44 points are its own statements and the rest belongs to 12 function items inside it that branch (fit, selectAt, a function literal at line 168, …). 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.
rich-text-editor-field.RichTextEditor (cyclomatic 44) apps/web/src/features/resume/editor/write/rich-text-editor-field.tsx:190— rich-text-editor-field.RichTextEditor has cyclomatic complexity 44 (threshold 15). Of this number, 25 points are the body's own statements and 19 belong to 10 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.
ai-consent.authorizeAiRequest (cyclomatic 43) apps/mobile/src/api/ai-consent.ts:11— ai-consent.authorizeAiRequest has cyclomatic complexity 43 (threshold 15). Of this number, 30 points are the body's own statements and 13 belong to 5 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.
messages.ToolPartView (cyclomatic 42) apps/mobile/src/features/assistant/messages.tsx:201— messages.ToolPartView has cyclomatic complexity 42 (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.
values.valueSyntaxError (cyclomatic 42) packages/resume/src/stylesheet/values.ts:376— values.valueSyntaxError has cyclomatic complexity 42 (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.
index.DocumentMenu (cyclomatic 41) apps/mobile/src/features/document-menu/index.tsx:26— index.DocumentMenu has cyclomatic complexity 41 (threshold 15). Of this number, 34 points are the body's own statements and 7 belong to 5 function items inside it that branch. To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
history.HistoryPanel (cyclomatic 41) apps/mobile/src/features/history/history.tsx:52— history.HistoryPanel has cyclomatic complexity 41 (threshold 15). Of this number, 24 points are the body's own statements and 17 belong to 8 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.
section-sheet.SectionSheet (cyclomatic 41) apps/mobile/src/features/write/section-sheet.tsx:24— section-sheet.SectionSheet has cyclomatic complexity 41 (threshold 15). Of this number, 29 points are the body's own statements and 12 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.
add-application-dialog.AddApplicationForm (cyclomatic 41) apps/web/src/features/applications/components/add-application-dialog.tsx:68— add-application-dialog.AddApplicationForm has cyclomatic complexity 41 (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 (add-application-dialog.AddApplicationForm::add) 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.
generate.generateCareer (cyclomatic 40) packages/api/src/features/career/generate.ts:100— generate.generateCareer has cyclomatic complexity 40 (threshold 15). Of this number, 35 points are the body's own statements and 5 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.
offers.OfferCard (cyclomatic 39) apps/mobile/src/features/career/offers.tsx:101— offers.OfferCard has cyclomatic complexity 39 (threshold 15). Of this number, 34 points are the body's own statements and 5 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.
page-canvas.PageCanvas (cyclomatic 39) apps/web/src/routes/builder/$resumeId/-components/page-canvas.tsx:33— page-canvas.PageCanvas has cyclomatic complexity 39 (threshold 15). Of this number, 30 points are the body's own statements and 9 belong to 4 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.
assistant-screen.DocumentAssistantScreen (cyclomatic 38) apps/mobile/src/features/assistant/assistant-screen.tsx:95— assistant-screen.DocumentAssistantScreen has cyclomatic complexity 38 (threshold 15). Of this number, 29 points are the body's own statements and 9 belong to 7 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.
conversation.Composer (cyclomatic 38) apps/web/src/features/assistant/conversation.tsx:674— conversation.Composer has cyclomatic complexity 38 (threshold 15). Of this number, 24 points are the body's own statements and 14 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.
design-pane.DesignPane (cyclomatic 37) apps/mobile/src/features/design/design-pane.tsx:41— design-pane.DesignPane has cyclomatic complexity 37 (threshold 15). Of this number, 22 points are the body's own statements and 15 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.
import-file.importDocument (cyclomatic 37) apps/mobile/src/features/documents/import-file.ts:40— import-file.importDocument has cyclomatic complexity 37 (threshold 15). Of this number, 35 points are the body's own statements and 2 belong to one function item inside it that branches. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
outline.Outline (cyclomatic 37) apps/mobile/src/features/write/outline.tsx:50— outline.Outline has cyclomatic complexity 37 (threshold 15). Of this number, 16 points are the body's own statements and 21 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.
index.RouteComponent (cyclomatic 37) apps/web/src/routes/dashboard/applications/index.tsx:70— index.RouteComponent has cyclomatic complexity 37 (threshold 15). Of this number, 31 points are the body's own statements and 6 belong 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.
chat-view.Composer (cyclomatic 36) apps/mobile/src/features/assistant/chat-view.tsx:645— chat-view.Composer has cyclomatic complexity 36 (threshold 15). Of this number, 17 points are the body's own statements and 19 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.
today.Schedules (cyclomatic 36) apps/web/src/features/career/today.tsx:658— today.Schedules has cyclomatic complexity 36 (threshold 15). Most of this is not in the body itself: 5 of the 36 points are its own statements and the rest belongs to 10 function items inside it that branch (status, toggle, describe, …). 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.
messages.ProposalCard (cyclomatic 36) apps/web/src/features/career/workspace/messages.tsx:192— messages.ProposalCard has cyclomatic complexity 36 (threshold 15). Of this number, 17 points are the body's own statements and 19 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.
layout-screen.LayoutScreen (cyclomatic 35) apps/mobile/src/features/design/layout-screen.tsx:44— layout-screen.LayoutScreen has cyclomatic complexity 35 (threshold 15). Most of this is not in the body itself: 3 of the 35 points are its own statements and the rest belongs to 11 function items inside it that branch (column, begin, move, …). 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.
rich-text.RichText (cyclomatic 35) packages/pdf/src/templates/shared/rich-text.tsx:76— rich-text.RichText 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 7 function items inside it that branch (a function literal at line 235, renderText, renderView, …). 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.
values.expandShorthand (cyclomatic 35) packages/resume/src/stylesheet/values.ts:241— values.expandShorthand has cyclomatic complexity 35 (threshold 15). Of this number, 34 points are the body's own statements and 1 belongs to one function item inside it that branches. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
share.LetterHistory (cyclomatic 34) apps/mobile/src/features/letters/share.tsx:275— share.LetterHistory has cyclomatic complexity 34 (threshold 15). Of this number, 18 points are the body's own statements and 16 belong to 7 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.
assistant-panel.AssistantPanel (cyclomatic 33) apps/web/src/features/assistant/assistant-panel.tsx:53— assistant-panel.AssistantPanel has cyclomatic complexity 33 (threshold 15). Of this number, 16 points are the body's own statements and 17 belong to 7 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.
preview.browser.ResumePreviewClient (cyclomatic 33) apps/web/src/features/resume/preview/preview.browser.tsx:111— preview.browser.ResumePreviewClient has cyclomatic complexity 33 (threshold 15). Most of this is not in the body itself: 7 of the 33 points are its own statements and the rest belongs to 9 function literals inside it that branch (lines 152, 140, 268, …). 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.
jobs.execute (cyclomatic 33) packages/api/src/features/career/jobs.ts:343— jobs.execute has cyclomatic complexity 33 (threshold 15). Most of this is not in the body itself: 9 of the 33 points are its own statements and the rest belongs to one function literal inside it that branches (line 385). 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.
json-resume.convertJSONResume (cyclomatic 33) packages/import/src/json-resume.tsx:155— json-resume.convertJSONResume has cyclomatic complexity 33 (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.
calendar-screen.ApplicationCalendar (cyclomatic 32) apps/mobile/src/features/applications-board/calendar-screen.tsx:51— calendar-screen.ApplicationCalendar has cyclomatic complexity 32 (threshold 15). Most of this is not in the body itself: 10 of the 32 points are its own statements and the rest belongs to 6 function items inside it that branch (a function literal at line 219, dayHeading, a function literal at line 81, …). 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.
preferences.Preferences (cyclomatic 32) apps/mobile/src/features/career/preferences.tsx:18— preferences.Preferences has cyclomatic complexity 32 (threshold 15). Of this number, 23 points are the body's own statements and 9 belong to 5 function literals inside it that branch. To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
parser.Parser (cyclomatic 32) apps/mobile/src/features/check/parser.tsx:23— parser.Parser has cyclomatic complexity 32 (threshold 15). Most of this is not in the body itself: 15 of the 32 points are its own statements and the rest belongs to 3 function literals inside it that branch (lines 54, 41, 78). 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.
apply.AnswerCard (cyclomatic 32) apps/mobile/src/features/workspace/tabs/apply.tsx:206— apply.AnswerCard has cyclomatic complexity 32 (threshold 15). Of this number, 25 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.
messages.ProposalCard (cyclomatic 32) apps/mobile/src/features/workspace/tabs/messages.tsx:182— messages.ProposalCard has cyclomatic complexity 32 (threshold 15). Of this number, 16 points are the body's own statements and 16 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.
conversation.ToolPartView (cyclomatic 32) apps/web/src/features/assistant/conversation.tsx:419— conversation.ToolPartView has cyclomatic complexity 32 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
reactive-resume-v4-json.parseReactiveResumeV4JSON (cyclomatic 32) packages/import/src/reactive-resume-v4-json.tsx:241— reactive-resume-v4-json.parseReactiveResumeV4JSON has cyclomatic complexity 32 (threshold 15). Of this number, 16 points are the body's own statements and 16 belong to 14 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.
tree.buildItem (cyclomatic 32) packages/pdf/src/semantic/tree.ts:257— tree.buildItem has cyclomatic complexity 32 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
documents-page.DocumentsPage (cyclomatic 31) apps/web/src/features/documents/documents-page.tsx:54— documents-page.DocumentsPage has cyclomatic complexity 31 (threshold 15). Of this number, 21 points are the body's own statements and 10 belong to 7 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.
editor.StylesheetCodeEditor (cyclomatic 31) apps/web/src/features/resume/stylesheet/editor.tsx:122— editor.StylesheetCodeEditor has cyclomatic complexity 31 (threshold 15). Most of this is not in the body itself: 3 of the 31 points are its own statements and the rest belongs to 10 function items inside it that branch (updateColor, a function literal at line 199, a function literal at line 307, …). 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.
pages.LayoutPages (cyclomatic 31) apps/web/src/routes/builder/$resumeId/-sidebar/right/sections/layout/pages.tsx:88— pages.LayoutPages has cyclomatic complexity 31 (threshold 15). Most of this is not in the body itself: 4 of the 31 points are its own statements and the rest belongs to 7 function literals inside it that branch (lines 126, 105, 198, …). 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.
compare-resume.hasDuplicateJsonMembers (cyclomatic 31) tooling/recovery/compare-resume.ts:61— compare-resume.hasDuplicateJsonMembers has cyclomatic complexity 31 (threshold 15). Most of this is not in the body itself: 3 of the 31 points are its own statements and the rest belongs to 5 function items inside it that branch (scanObject, scanString, scanValue, …). 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.
store.createDraftStore.open (cyclomatic 30) apps/mobile/src/draft/store.ts:173— store.createDraftStore.open 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.
writing.Writing (cyclomatic 30) apps/mobile/src/features/check/writing.tsx:37— writing.Writing has cyclomatic complexity 30 (threshold 15). Most of this is not in the body itself: 12 of the 30 points are its own statements and the rest belongs to 6 function items inside it that branch (run, accept, a function literal at line 179, …). 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.
library.DocumentItem (cyclomatic 30) apps/mobile/src/features/documents/library.tsx:62— library.DocumentItem has cyclomatic complexity 30 (threshold 15). Of this number, 29 points are the body's own statements and 1 belongs to one function item inside it that branches. To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
share.LetterDownload (cyclomatic 30) apps/mobile/src/features/letters/share.tsx:88— share.LetterDownload has cyclomatic complexity 30 (threshold 15). Most of this is not in the body itself: 14 of the 30 points are its own statements and the rest belongs to 2 function items inside it that branch (download, a function literal at line 202). 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.
entry-card.EntryCard (cyclomatic 30) apps/web/src/features/resume/editor/write/entry-card.tsx:65— entry-card.EntryCard has cyclomatic complexity 30 (threshold 15). Of this number, 22 points are the body's own statements and 8 belong to 4 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.
operators.summarizePageOperators (cyclomatic 30) packages/resume/src/ats-pdf/analyze/operators.ts:111— operators.summarizePageOperators has cyclomatic complexity 30 (threshold 15). Of this number, 29 points are the body's own statements and 1 belongs to one function item inside it that branches. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
overlays.Sheet (cyclomatic 29) apps/mobile/src/ui/overlays.tsx:92— overlays.Sheet has cyclomatic complexity 29 (threshold 15). Most of this is not in the body itself: 14 of the 29 points are its own statements and the rest belongs to 6 function items inside it that branch (a function literal at line 127, onDismiss, a function literal at line 135, …). 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.
sections.NextStepCard (cyclomatic 29) apps/mobile/src/features/application-detail/sections.tsx:149— sections.NextStepCard has cyclomatic complexity 29 (threshold 15). Of this number, 27 points are the body's own statements and 2 belong to one function item inside it that branches. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
schedule-sheet.ScheduleForm (cyclomatic 29) apps/mobile/src/features/career/schedule-sheet.tsx:80— schedule-sheet.ScheduleForm has cyclomatic complexity 29 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top. This shape REPEATS in the file: one other method here (schedule-sheet.ScheduleForm::save) 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.
screen.CheckScreen (cyclomatic 29) apps/mobile/src/features/check/screen.tsx:25— screen.CheckScreen has cyclomatic complexity 29 (threshold 15). Of this number, 19 points are the body's own statements and 10 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.
builder-chrome.Frame (cyclomatic 29) apps/mobile/src/shell/builder-chrome.tsx:112— builder-chrome.Frame has cyclomatic complexity 29 (threshold 15). Of this number, 19 points are the body's own statements and 10 belong to 5 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.
picture-screen.PictureScreen (cyclomatic 28) apps/mobile/src/features/write/picture-screen.tsx:41— picture-screen.PictureScreen 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 6 function items inside it that branch (a function literal at line 61, remove, set, …). 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.
sent-documents.SentDocuments (cyclomatic 28) apps/web/src/features/applications/components/detail/sent-documents.tsx:53— sent-documents.SentDocuments has cyclomatic complexity 28 (threshold 15). Of this number, 22 points are the body's own statements and 6 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.
application-form-sheet.ApplicationFormSheet (cyclomatic 28) apps/web/src/features/applications/components/application-form-sheet.tsx:203— application-form-sheet.ApplicationFormSheet has cyclomatic complexity 28 (threshold 15). Of this number, 17 points are the body's own statements and 11 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.
apply.AnswerCard (cyclomatic 28) apps/web/src/features/career/workspace/apply.tsx:230— apply.AnswerCard has cyclomatic complexity 28 (threshold 15). Of this number, 23 points are the body's own statements and 5 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.
page-layer.CheckPageLayer (cyclomatic 28) apps/web/src/features/resume/editor/check/page-layer.tsx:86— page-layer.CheckPageLayer has cyclomatic complexity 28 (threshold 15). Most of this is not in the body itself: 13 of the 28 points are its own statements and the rest belongs to 6 function items inside it that branch (a function literal at line 121, a function literal at line 111, a function literal at line 156, …). 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.
tree.partMatchesOwner (cyclomatic 28) packages/pdf/src/semantic/tree.ts:668— tree.partMatchesOwner has cyclomatic complexity 28 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
store.createDraftStore.flush (cyclomatic 27) apps/mobile/src/draft/store.ts:308— store.createDraftStore.flush has cyclomatic complexity 27 (threshold 15). Most of this is not in the body itself: 13 of the 27 points are its own statements and the rest belongs to one function literal inside it that branches (line 322). 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.
public-resume.PublicResume (cyclomatic 27) apps/mobile/src/features/public/public-resume.tsx:29— public-resume.PublicResume has cyclomatic complexity 27 (threshold 15). Of this number, 19 points are the body's own statements and 8 belong to 5 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.
shell.WorkspaceScreen (cyclomatic 27) apps/mobile/src/features/workspace/shell.tsx:68— shell.WorkspaceScreen 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, 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.
conversation.Conversation (cyclomatic 27) apps/web/src/features/assistant/conversation.tsx:66— conversation.Conversation has cyclomatic complexity 27 (threshold 15). Most of this is not in the body itself: 11 of the 27 points are its own statements and the rest belongs to 9 function items inside it that branch (a function literal at line 161, send, a function literal at line 101, …). 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.
offers.ComparisonTable (cyclomatic 27) apps/web/src/features/career/offers.tsx:185— offers.ComparisonTable has cyclomatic complexity 27 (threshold 15). Most of this is not in the body itself: 7 of the 27 points are its own statements and the rest belongs to 6 function literals inside it that branch (lines 242, 207, 198, …). 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.
fit.FitTab (cyclomatic 27) apps/web/src/features/career/workspace/fit.tsx:55— fit.FitTab has cyclomatic complexity 27 (threshold 15). Of this number, 20 points are the body's own statements and 7 belong to 5 function items inside it that branch. To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
values.compileProgram::compileRule (cyclomatic 27) packages/resume/src/stylesheet/values.ts:554— values.compileProgram::compileRule 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.
generator.generateOpenApiSpec (cyclomatic 26) apps/server/src/openapi/generator.ts:89— generator.generateOpenApiSpec has cyclomatic complexity 26 (threshold 15). Of this number, 21 points are the body's own statements and 5 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.
rich-text-markup.hasUnsupportedTableMarkup (cyclomatic 26) apps/web/src/components/input/rich-text-markup.ts:360— rich-text-markup.hasUnsupportedTableMarkup 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.
csv.mapCsvToApplications (cyclomatic 26) apps/web/src/features/applications/csv.ts:210— csv.mapCsvToApplications has cyclomatic complexity 26 (threshold 15). Of this number, 13 points are the body's own statements and 13 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.
list-view.ApplicationList (cyclomatic 26) apps/web/src/features/applications/components/list-view.tsx:62— list-view.ApplicationList has cyclomatic complexity 26 (threshold 15). Most of this is not in the body itself: 5 of the 26 points are its own statements and the rest belongs to 9 function items inside it that branch (a function literal at line 162, header, a function literal at line 72, …). 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.
editor.StylesheetEditorShell (cyclomatic 26) apps/web/src/features/resume/stylesheet/editor.tsx:378— editor.StylesheetEditorShell has cyclomatic complexity 26 (threshold 15). Most of this is not in the body itself: 9 of the 26 points are its own statements and the rest belongs to 8 function items inside it that branch (highlightRuleAt, a function literal at line 416, a function literal at line 414, …). 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.
markdown.parseBlocks (cyclomatic 25) apps/mobile/src/features/assistant/markdown.tsx:14— markdown.parseBlocks has cyclomatic complexity 25 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
coach-screen.CoachScreen (cyclomatic 25) apps/mobile/src/features/assistant/coach-screen.tsx:68— coach-screen.CoachScreen has cyclomatic complexity 25 (threshold 15). Of this number, 22 points are the body's own statements and 3 belong to 3 function literals inside it that branch. To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
combobox.Combobox (cyclomatic 25) apps/web/src/components/ui/combobox.tsx:72— combobox.Combobox has cyclomatic complexity 25 (threshold 15). Most of this is not in the body itself: 11 of the 25 points are its own statements and the rest belongs to 5 function items inside it that branch (handleExternalChange, findOption, filter, …). 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.
coach-thread.Composer (cyclomatic 25) apps/web/src/features/career/coach-thread.tsx:330— coach-thread.Composer has cyclomatic complexity 25 (threshold 15). Most of this is not in the body itself: 10 of the 25 points are its own statements and the rest belongs to 5 function items inside it that branch (submit, a function literal at line 396, upload, …). 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.
offers.OffersPage (cyclomatic 25) apps/web/src/features/career/offers.tsx:56— offers.OffersPage has cyclomatic complexity 25 (threshold 15). Most of this is not in the body itself: 9 of the 25 points are its own statements and the rest belongs to 3 function literals inside it that branch (lines 66, 69, 149). 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.
offers.useCells (cyclomatic 25) apps/web/src/features/career/offers.tsx:393— offers.useCells has cyclomatic complexity 25 (threshold 15). Most of this is not in the body itself: 1 of the 25 points is its own statement and the rest belongs to 3 function literals inside it that branch (lines 397, 408, 426). 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.
section-row.SectionMenu (cyclomatic 25) apps/web/src/features/resume/editor/write/section-row.tsx:179— section-row.SectionMenu has cyclomatic complexity 25 (threshold 15). Of this number, 13 points are the body's own statements and 12 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.
error-message.getReadableErrorMessage (cyclomatic 25) apps/web/src/libs/error-message.ts:5— error-message.getReadableErrorMessage has cyclomatic complexity 25 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
legacy-converter.activeSlotChunks (cyclomatic 25) packages/pdf/src/semantic/legacy-converter.ts:169— legacy-converter.activeSlotChunks has cyclomatic complexity 25 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
extract.findGutter (cyclomatic 25) packages/resume/src/ats-pdf/extract.ts:224— extract.findGutter has cyclomatic complexity 25 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
selector.compileSimple (cyclomatic 25) packages/resume/src/stylesheet/selector.ts:175— selector.compileSimple has cyclomatic complexity 25 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
cascade.structuralValue (cyclomatic 25) packages/resume/src/stylesheet/cascade.ts:494— cascade.structuralValue has cyclomatic complexity 25 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
document.useLetterAssistantDocument (cyclomatic 24) apps/mobile/src/features/assistant/document.ts:75— document.useLetterAssistantDocument has cyclomatic complexity 24 (threshold 15). Most of this is not in the body itself: 1 of the 24 points is its own statement and the rest belongs to 8 function literals inside it that branch (lines 109, 136, 93, …). 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.
read-file.detectImportKind (cyclomatic 24) apps/web/src/features/resume/import/read-file.ts:58— read-file.detectImportKind 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.
resume-reflow.EntryView (cyclomatic 24) apps/web/src/features/resume/public/resume-reflow.tsx:46— resume-reflow.EntryView has cyclomatic complexity 24 (threshold 15). Of this number, 21 points are the body's own statements and 3 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.
letter-page.LetterPage (cyclomatic 24) apps/web/src/routes/builder/letter/-components/letter-page.tsx:47— letter-page.LetterPage has cyclomatic complexity 24 (threshold 15). Of this number, 15 points are the body's own statements and 9 belong to 4 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.
messages-persistence.applyStepToUiMessage (cyclomatic 24) packages/api/src/features/agent/messages-persistence.ts:110— messages-persistence.applyStepToUiMessage has cyclomatic complexity 24 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
tools.registerTools (cyclomatic 24) packages/mcp/src/tools.ts:80— tools.registerTools has cyclomatic complexity 24 (threshold 15). Most of this is not in the body itself: 2 of the 24 points are its own statements and the rest belongs to 10 function literals inside it that branch (lines 173, 151, 274, …). 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.
picture-shadow.getPictureShadow (cyclomatic 24) packages/pdf/src/templates/shared/picture-shadow.ts:43— picture-shadow.getPictureShadow has cyclomatic complexity 24 (threshold 15). Of this number, 21 points are the body's own statements and 3 belong to one function item inside it that branches. To reduce it, 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.
images.node.readServerImage (cyclomatic 24) packages/pdf/src/forme/images.node.ts:13— images.node.readServerImage has cyclomatic complexity 24 (threshold 15). Of this number, 13 points are the body's own statements and 11 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.
date-field.WallClockField (cyclomatic 23) apps/mobile/src/features/application-detail/date-field.tsx:37— date-field.WallClockField has cyclomatic complexity 23 (threshold 15). Of this number, 15 points are the body's own statements and 8 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.
facts.Facts (cyclomatic 23) apps/mobile/src/features/career/facts.tsx:58— facts.Facts has cyclomatic complexity 23 (threshold 15). Of this number, 15 points are the body's own statements and 8 belong to 3 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.
thumbnail.Thumbnail (cyclomatic 23) apps/mobile/src/features/documents/thumbnail.tsx:20— thumbnail.Thumbnail has cyclomatic complexity 23 (threshold 15). Of this number, 20 points are the body's own statements and 3 belong to 3 function literals inside it that branch. To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
download.DownloadTab (cyclomatic 23) apps/mobile/src/features/share/download.tsx:22— download.DownloadTab 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. This shape REPEATS in the file: one other method here (download.DownloadTab::download) 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.
activity.Activity (cyclomatic 23) apps/web/src/features/applications/components/detail/activity.tsx:51— activity.Activity has cyclomatic complexity 23 (threshold 15). Most of this is not in the body itself: 9 of the 23 points are its own statements and the rest belongs to 9 function items inside it that branch (a function literal at line 129, describe, submit, …). 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.
today.NewRoles (cyclomatic 23) apps/web/src/features/career/today.tsx:300— today.NewRoles has cyclomatic complexity 23 (threshold 15). Most of this is not in the body itself: 11 of the 23 points are its own statements and the rest belongs to 6 function items inside it that branch (emptyLine, a function literal at line 440, a function literal at line 352, …). 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.
store.useLetterEditorStore (cyclomatic 23) apps/web/src/features/letters/store.ts:78— store.useLetterEditorStore has cyclomatic complexity 23 (threshold 15). Most of this is not in the body itself: 1 of the 23 points is its own statement and the rest belongs to 8 function literals inside it that branch (lines 106, 154, 93, …). 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.
pdf-viewer.PdfViewer (cyclomatic 23) apps/web/src/features/resume/public/pdf-viewer.tsx:74— pdf-viewer.PdfViewer has cyclomatic complexity 23 (threshold 15). Most of this is not in the body itself: 5 of the 23 points are its own statements and the rest belongs to 10 function literals inside it that branch (lines 118, 92, 177, …). 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.
providers.EditProviderForm (cyclomatic 23) apps/web/src/features/settings/ai/providers.tsx:576— providers.EditProviderForm has cyclomatic complexity 23 (threshold 15). Of this number, 17 points are the body's own statements and 6 belong to 3 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.
context.collapseOldestToolPairs (cyclomatic 23) packages/api/src/features/agent/context.ts:117— context.collapseOldestToolPairs has cyclomatic complexity 23 (threshold 15). Of this number, 16 points are the body's own statements and 7 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.
messages-merge.mergeClientToolResponses (cyclomatic 23) packages/api/src/features/agent/messages-merge.ts:50— messages-merge.mergeClientToolResponses has cyclomatic complexity 23 (threshold 15). Most of this is not in the body itself: 8 of the 23 points are its own statements and the rest belongs to one function literal inside it that branches (line 81). 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.
builder.buildDocument (cyclomatic 23) packages/docx/src/builder.ts:282— builder.buildDocument 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.
fetch-prebuilt.main (cyclomatic 23) packages/forme-native/scripts/fetch-prebuilt.mjs:8— fetch-prebuilt.main has cyclomatic complexity 23 (threshold 15). Of this number, 22 points are the body's own statements and 1 belongs to one function literal inside it that branches. To reduce it, split the body: 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.
level.parseLevel (cyclomatic 23) packages/import/src/level.ts:6— level.parseLevel 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.
linkedin.parseLinkedInExport (cyclomatic 23) packages/import/src/linkedin.ts:166— linkedin.parseLinkedInExport has cyclomatic complexity 23 (threshold 15). Of this number, 22 points are the body's own statements and 1 belongs to one function literal inside it that branches. To reduce it, split the body: 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.
level-display.LevelDisplay (cyclomatic 23) packages/pdf/src/templates/shared/level-display.tsx:26— level-display.LevelDisplay has cyclomatic complexity 23 (threshold 15). 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 69). 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.
preferences.PreferencesScreen (cyclomatic 22) apps/mobile/app/(tabs)/settings/preferences.tsx:34— preferences.PreferencesScreen has cyclomatic complexity 22 (threshold 15). Of this number, 18 points are the body's own statements and 4 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.
button.Button (cyclomatic 22) apps/mobile/src/ui/button.tsx:39— button.Button has cyclomatic complexity 22 (threshold 15). Most of this is not in the body itself: 9 of the 22 points are its own statements and the rest belongs to one function literal inside it that branches (line 85). 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.
host.server (cyclomatic 22) apps/mobile/scripts/parity/host.mts:55— host.server 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.
provider-list.ProviderRow (cyclomatic 22) apps/mobile/src/features/ai/provider-list.tsx:74— provider-list.ProviderRow has cyclomatic complexity 22 (threshold 15). Of this number, 17 points are the body's own statements and 5 belong to one function item inside it that branches. To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
page.CheckPage (cyclomatic 22) apps/mobile/src/features/check/page.tsx:29— page.CheckPage has cyclomatic complexity 22 (threshold 15). Of this number, 16 points are the body's own statements and 6 belong to 3 function literals inside it that branch. To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
application-detail-sheet.Detail (cyclomatic 22) apps/web/src/features/applications/components/application-detail-sheet.tsx:94— application-detail-sheet.Detail has cyclomatic complexity 22 (threshold 15). Of this number, 13 points are the body's own statements and 9 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.
import-applications-sheet.ImportApplicationsSheet (cyclomatic 22) apps/web/src/features/applications/components/import-applications-sheet.tsx:58— import-applications-sheet.ImportApplicationsSheet has cyclomatic complexity 22 (threshold 15). Of this number, 14 points are the body's own statements and 8 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.
consent.OAuthConsentPage (cyclomatic 22) apps/web/src/features/auth/pages/consent.tsx:42— consent.OAuthConsentPage has cyclomatic complexity 22 (threshold 15). Of this number, 16 points are the body's own statements and 6 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.
stories.StoriesPage (cyclomatic 22) apps/web/src/features/career/knowledge/stories.tsx:52— stories.StoriesPage has cyclomatic complexity 22 (threshold 15). Of this number, 21 points are the body's own statements and 1 belongs to one function item inside it that branches. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
stories.StoryEditor (cyclomatic 22) apps/web/src/features/career/knowledge/stories.tsx:404— stories.StoryEditor 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 6 function items inside it that branch (a function literal at line 512, a function literal at line 540, submit, …). 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.
debrief.DebriefForm (cyclomatic 22) apps/web/src/features/career/workspace/debrief.tsx:101— debrief.DebriefForm has cyclomatic complexity 22 (threshold 15). Of this number, 12 points are the body's own statements and 10 belong to 5 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.
parity.registerParityTools (cyclomatic 22) packages/mcp/src/parity.ts:344— parity.registerParityTools has cyclomatic complexity 22 (threshold 15). Most of this is not in the body itself: 5 of the 22 points are its own statements and the rest belongs to one function literal inside it that branches (line 364). 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.
css-escape.escapeCssIdentifier (cyclomatic 22) packages/resume/src/stylesheet/css-escape.ts:1— css-escape.escapeCssIdentifier 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.
checker.AtsChecker (cyclomatic 21) apps/mobile/src/features/ats-checker/checker.tsx:41— checker.AtsChecker has cyclomatic complexity 21 (threshold 15). Most of this is not in the body itself: 5 of the 21 points are its own statements and the rest belongs to 6 function items inside it that branch (a function literal at line 124, check, importAndOpen, …). 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.
calendar-view.ApplicationCalendar (cyclomatic 21) apps/web/src/features/applications/components/calendar-view.tsx:38— calendar-view.ApplicationCalendar 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 6 function items inside it that branch (a function literal at line 138, dayHeading, a function literal at line 61, …). 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.
coach-chat.ChatView (cyclomatic 21) apps/web/src/features/career/coach-chat.tsx:67— coach-chat.ChatView has cyclomatic complexity 21 (threshold 15). Of this number, 14 points are the body's own statements and 7 belong to 5 function items inside it that branch. To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
document-card.DocumentCard (cyclomatic 21) apps/web/src/features/documents/document-card.tsx:136— document-card.DocumentCard 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.
prepare.Prepare (cyclomatic 21) apps/web/src/features/homepage/prepare.tsx:502— prepare.Prepare has cyclomatic complexity 21 (threshold 15). Most of this is not in the body itself: 7 of the 21 points are its own statements and the rest belongs to 5 function literals inside it that branch (lines 625, 538, 582, …). 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.
public-resume.PublicResumePage (cyclomatic 21) apps/web/src/features/resume/public/public-resume.tsx:46— public-resume.PublicResumePage has cyclomatic complexity 21 (threshold 15). Of this number, 18 points are the body's own statements and 3 belong to one function item inside it that branches. To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
service.createAgent (cyclomatic 21) packages/api/src/features/agent/service.ts:732— service.createAgent has cyclomatic complexity 21 (threshold 15). Of this number, 12 points are the body's own statements and 9 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.
html-to-odt.processBlock (cyclomatic 21) packages/odt/src/html-to-odt.ts:162— html-to-odt.processBlock has cyclomatic complexity 21 (threshold 15). Of this number, 19 points are the body's own statements and 2 belong to one function literal inside it that branches. To reduce it, 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.
rich-text-keys.getRichTextSemanticKind (cyclomatic 21) packages/pdf/src/semantic/rich-text-keys.ts:19— rich-text-keys.getRichTextSemanticKind 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.
text.renderChildren (cyclomatic 21) packages/pdf/src/text.tsx:152— text.renderChildren has cyclomatic complexity 21 (threshold 15). Most of this is not in the body itself: 5 of the 21 points are its own statements and the rest belongs to 2 function literals inside it that branch (lines 158, 175). 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.
selector.matchesSimple (cyclomatic 21) packages/resume/src/stylesheet/selector.ts:345— selector.matchesSimple has cyclomatic complexity 21 (threshold 15). To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Where every arm is uniform — the same kind of value, with no behaviour of its own — a table keyed by the case is the shorter form; wherever the arms carry different data or different behaviour, keep them as cases, because collapsing those trades an explicit, reviewable set of cases for nothing.
url-security.node.fetchPublic (cyclomatic 21) packages/utils/src/url-security.node.ts:154— url-security.node.fetchPublic has cyclomatic complexity 21 (threshold 15). Most of this is not in the body itself: 10 of the 21 points are its own statements and the rest belongs to 2 function literals inside it that branch (lines 174, 210). 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.
PdfPagesModule.definition (cyclomatic 21) apps/mobile/modules/pdf-pages/ios/PdfPagesModule.swift:10— PdfPagesModule.definition has cyclomatic complexity 21 (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.
job-match.JobMatch (cyclomatic 20) apps/mobile/src/features/check/job-match.tsx:25— job-match.JobMatch 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. This shape REPEATS in the file: one other method here (job-match.JobMatch::link) 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.
use-review-prompt.useReviewPrompt (cyclomatic 20) apps/mobile/src/features/reviews/use-review-prompt.ts:14— use-review-prompt.useReviewPrompt has cyclomatic complexity 20 (threshold 15). Most of this is not in the body itself: 2 of the 20 points are its own statements and the rest belongs to 4 function literals inside it that branch (lines 34, 53, 21, …). 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.
model.resolveDrop (cyclomatic 20) apps/mobile/src/features/write/model.ts:425— model.resolveDrop has cyclomatic complexity 20 (threshold 15). Of this number, 17 points are the body's own statements and 3 belong to 2 function items inside it that branch. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
today.NeedsYou (cyclomatic 20) apps/web/src/features/career/today.tsx:132— today.NeedsYou has cyclomatic complexity 20 (threshold 15). Most of this is not in the body itself: 9 of the 20 points are its own statements and the rest belongs to 5 function items inside it that branch (meta, a function literal at line 214, act, …). 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.
move-item.moveItem (cyclomatic 20) packages/resume/src/move-item.ts:17— move-item.moveItem has cyclomatic complexity 20 (threshold 15). Of this number, 16 points are the body's own statements and 4 belong to 3 function literals inside it that branch. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
layout.Banner (cyclomatic 19) apps/mobile/src/ui/layout.tsx:364— layout.Banner 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, 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.
checker.Result (cyclomatic 19) apps/mobile/src/features/ats-checker/checker.tsx:332— checker.Result has cyclomatic complexity 19 (threshold 15). Of this number, 15 points are the body's own statements and 4 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.
outline.SectionRow (cyclomatic 19) apps/mobile/src/features/write/outline.tsx:313— outline.SectionRow 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, 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.
rich-input-whitespace.markPastedHtml::normalize (cyclomatic 19) apps/web/src/components/input/rich-input-whitespace.ts:56— rich-input-whitespace.markPastedHtml::normalize 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.
add-application-dialog.AddApplicationForm::add (cyclomatic 19) apps/web/src/features/applications/components/add-application-dialog.tsx:142— add-application-dialog.AddApplicationForm::add 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. This shape REPEATS in the file: one other method here (add-application-dialog.AddApplicationForm) 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.
coach-chat.Proposal (cyclomatic 19) apps/web/src/features/career/coach-chat.tsx:609— coach-chat.Proposal has cyclomatic complexity 19 (threshold 15). Of this number, 11 points are the body's own statements and 8 belong to 5 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.
schedule-sheet.ScheduleSheet::onSave (cyclomatic 19) apps/web/src/features/career/schedule-sheet.tsx:206— schedule-sheet.ScheduleSheet::onSave 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. This shape REPEATS in the file: one other method here (schedule-sheet.ScheduleSheet) 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.
new-document-dialog.useResumeImport.importFile (cyclomatic 19) apps/web/src/features/documents/new-document-dialog.tsx:73— new-document-dialog.useResumeImport.importFile has cyclomatic complexity 19 (threshold 15). Of this number, 17 points are the body's own statements and 2 belong to one function literal inside it that branches. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
draft.flushResumeSave (cyclomatic 19) apps/web/src/features/resume/builder/draft.ts:262— draft.flushResumeSave 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.
section-row.SectionRow (cyclomatic 19) apps/web/src/features/resume/editor/write/section-row.tsx:61— section-row.SectionRow has cyclomatic complexity 19 (threshold 15). Of this number, 14 points are the body's own statements and 5 belong to 2 function items inside it that branch. To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
sanitize.coerceValueAgainstTemplate (cyclomatic 19) packages/ai/src/resume/sanitize.ts:110— sanitize.coerceValueAgainstTemplate 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.
html-to-odt.mergeStyle (cyclomatic 19) packages/odt/src/html-to-odt.ts:29— html-to-odt.mergeStyle has cyclomatic complexity 19 (threshold 15). To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Where every arm is uniform — the same kind of value, with no behaviour of its own — a table keyed by the case is the shorter form; wherever the arms carry different data or different behaviour, keep them as cases, because collapsing those trades an explicit, reviewable set of cases for nothing.
use-register-fonts.resolvePdfFonts (cyclomatic 19) packages/pdf/src/hooks/use-register-fonts.ts:218— use-register-fonts.resolvePdfFonts has cyclomatic complexity 19 (threshold 15). Of this number, 10 points are the body's own statements and 9 belong to 2 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.
tree.buildSemanticTree (cyclomatic 19) packages/pdf/src/semantic/tree.ts:915— tree.buildSemanticTree has cyclomatic complexity 19 (threshold 15). Most of this is not in the body itself: 9 of the 19 points are its own statements and the rest belongs to one function literal inside it that branches (line 935). 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.
catalog.loadModelSuggestions (cyclomatic 18) apps/mobile/src/features/ai/catalog.ts:193— catalog.loadModelSuggestions has cyclomatic complexity 18 (threshold 15). Most of this is not in the body itself: 3 of the 18 points are its own statements and the rest belongs to 3 function literals inside it that branch (lines 206, 202, 228). 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.
schedule-sheet.ScheduleForm::save (cyclomatic 18) apps/mobile/src/features/career/schedule-sheet.tsx:137— schedule-sheet.ScheduleForm::save has cyclomatic complexity 18 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages. This shape REPEATS in the file: one other method here (schedule-sheet.ScheduleForm) 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.
profile.ProfileField (cyclomatic 18) apps/mobile/src/features/settings/profile.tsx:15— profile.ProfileField has cyclomatic complexity 18 (threshold 15). Of this number, 14 points are the body's own statements and 4 belong to 2 function items inside it that branch. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
profile.ProfileEditor (cyclomatic 18) apps/mobile/src/features/settings/profile.tsx:72— profile.ProfileEditor has cyclomatic complexity 18 (threshold 15). Most of this is not in the body itself: 3 of the 18 points are its own statements and the rest belongs to one function literal inside it that branches (line 80). 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.
download.DownloadTab::download (cyclomatic 18) apps/mobile/src/features/share/download.tsx:57— download.DownloadTab::download 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. This shape REPEATS in the file: one other method here (download.DownloadTab) 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.
state.createAutosave.send (cyclomatic 18) apps/mobile/src/features/workspace/state.ts:112— state.createAutosave.send 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 118). 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.
shell.TabBadges (cyclomatic 18) apps/mobile/src/features/workspace/shell.tsx:258— shell.TabBadges has cyclomatic complexity 18 (threshold 15). Most of this is not in the body itself: 5 of the 18 points are its own statements and the rest belongs to 2 function items inside it that branch (badge, a function literal at line 284). 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.
debrief.DebriefForm (cyclomatic 18) apps/mobile/src/features/workspace/tabs/debrief.tsx:94— debrief.DebriefForm has cyclomatic complexity 18 (threshold 15). Of this number, 13 points are the body's own statements and 5 belong to 5 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.
open.redirectSystemPath (cyclomatic 18) apps/mobile/src/linking/open.ts:33— open.redirectSystemPath has cyclomatic complexity 18 (threshold 15). Most of this is not in the body itself: 4 of the 18 points are its own statements and the rest belongs to one function literal inside it that branches (line 44). The decisions are inside the literal, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literal's work into a named function or method at the enclosing scope and have the literal call it, then reduce whichever part then reads as the largest.
app-tabs.SidebarItem (cyclomatic 18) apps/mobile/src/shell/app-tabs.tsx:295— app-tabs.SidebarItem has cyclomatic complexity 18 (threshold 15). Of this number, 11 points are the body's own statements and 7 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.
display.LevelDisplay (cyclomatic 18) apps/web/src/components/level/display.tsx:17— display.LevelDisplay has cyclomatic complexity 18 (threshold 15). Most of this is not in the body itself: 7 of the 18 points are its own statements and the rest belongs to one function literal inside it that branches (line 45). 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.
enable-two-factor.EnableTwoFactorDialog (cyclomatic 18) apps/web/src/dialogs/auth/enable-two-factor.tsx:54— enable-two-factor.EnableTwoFactorDialog has cyclomatic complexity 18 (threshold 15). Most of this is not in the body itself: 1 of the 18 points is its own statement and the rest belongs to 10 function items inside it that branch (a function literal at line 138, a function literal at line 228, a function literal at line 67, …). 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.
verify-2fa.TwoFactorVerificationPage (cyclomatic 18) apps/web/src/features/auth/pages/verify-2fa.tsx:36— verify-2fa.TwoFactorVerificationPage 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 2 function literals inside it that branch (lines 45, 110). 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.
link-tab.AddressField (cyclomatic 18) apps/web/src/features/resume/share/link-tab.tsx:182— link-tab.AddressField has cyclomatic complexity 18 (threshold 15). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
draft.draftLetterBody (cyclomatic 18) packages/api/src/features/cover-letters/draft.ts:47— draft.draftLetterBody has cyclomatic complexity 18 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
config.verifyOAuthToken (cyclomatic 18) packages/auth/src/config.ts:47— config.verifyOAuthToken has cyclomatic complexity 18 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
builder.buildHeader (cyclomatic 18) packages/docx/src/builder.ts:135— builder.buildHeader 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, 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.
contracts.wireJsonSchema (cyclomatic 18) packages/mcp/src/contracts.ts:79— contracts.wireJsonSchema has cyclomatic complexity 18 (threshold 15). Most of this is not in the body itself: 1 of the 18 points is its own statement and the rest belongs to 2 function literals inside it that branch (lines 92, 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.
to-forme.fitImage (cyclomatic 18) packages/pdf/src/forme/to-forme.tsx:726— to-forme.fitImage 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.
base-styles.buildPdfBaseStyles::visit (cyclomatic 18) packages/pdf/src/semantic/base-styles.ts:50— base-styles.buildPdfBaseStyles::visit 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.
sections.EducationSection (cyclomatic 18) packages/pdf/src/templates/shared/sections.tsx:1027— sections.EducationSection has cyclomatic complexity 18 (threshold 15). Most of this is not in the body itself: 2 of the 18 points are its own statements and the rest belongs to 3 function literals inside it that branch (lines 1073, 1040, 1046). 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.
render.renderResumeElement (cyclomatic 18) packages/pdf/src/forme/render.ts:216— render.renderResumeElement has cyclomatic complexity 18 (threshold 15). Most of this is not in the body itself: 7 of the 18 points are its own statements and the rest belongs to 4 function items inside it that branch (layOut, layOutOnce::render, a function literal at line 264, …). 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.
compare-resume.parseRequest (cyclomatic 18) tooling/recovery/compare-resume.ts:206— compare-resume.parseRequest has cyclomatic complexity 18 (threshold 15). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
session.authorize (cyclomatic 17) apps/mobile/src/auth/session.ts:310— session.authorize 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.
overlays.DialogAction (cyclomatic 17) apps/mobile/src/ui/overlays.tsx:329— overlays.DialogAction has cyclomatic complexity 17 (threshold 15). Most of this is not in the body itself: 8 of the 17 points are its own statements and the rest belongs to 5 function items inside it that branch (a function literal at line 359, startHold, a function literal at line 339, …). 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.
document.useResumeAssistantDocument (cyclomatic 17) apps/mobile/src/features/assistant/document.ts:34— document.useResumeAssistantDocument has cyclomatic complexity 17 (threshold 15). Most of this is not in the body itself: 1 of the 17 points is its own statement and the rest belongs to 5 function literals inside it that branch (lines 58, 41, 54, …). 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.
job-match.JobMatch::link (cyclomatic 17) apps/mobile/src/features/check/job-match.tsx:41— job-match.JobMatch::link has cyclomatic complexity 17 (threshold 15). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators. This shape REPEATS in the file: one other method here (job-match.JobMatch) 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.
logic.parseNumber (cyclomatic 17) apps/mobile/src/features/workspace/logic.ts:300— logic.parseNumber 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.
apply.Apply (cyclomatic 17) apps/mobile/src/features/workspace/tabs/apply.tsx:46— apply.Apply has cyclomatic complexity 17 (threshold 15). Of this number, 13 points are the body's own statements and 4 belong to 4 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.
practise.Practise (cyclomatic 17) apps/mobile/src/features/workspace/tabs/practise.tsx:60— practise.Practise has cyclomatic complexity 17 (threshold 15). Of this number, 16 points are the body's own statements and 1 belongs to one function literal inside it that branches. To reduce it, 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.
rich-text-field.RichTextToolbar (cyclomatic 17) apps/mobile/src/features/write/rich-text-field.tsx:227— rich-text-field.RichTextToolbar has cyclomatic complexity 17 (threshold 15). Most of this is not in the body itself: 5 of the 17 points are its own statements and the rest belongs to 3 function items inside it that branch (a function literal at line 356, setHeading, setHeading::toggle). 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.
basics-screen.CustomFields (cyclomatic 17) apps/mobile/src/features/write/basics-screen.tsx:145— basics-screen.CustomFields has cyclomatic complexity 17 (threshold 15). Most of this is not in the body itself: 5 of the 17 points are its own statements and the rest belongs to 5 function literals inside it that branch (lines 169, 153, 259, …). 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.
workspace-chrome.Frame (cyclomatic 17) apps/mobile/src/shell/workspace-chrome.tsx:56— workspace-chrome.Frame has cyclomatic complexity 17 (threshold 15). Most of this is not in the body itself: 7 of the 17 points are its own statements and the rest belongs to 6 function items inside it that branch (revealActive, a function literal at line 153, a function literal at line 141, …). 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.
generator.addCurlSamples::example (cyclomatic 17) apps/server/src/openapi/generator.ts:236— generator.addCurlSamples::example 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. This shape REPEATS in the file: one other method here (generator.addCurlSamples) 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.
uploads.handleUpload (cyclomatic 17) apps/server/src/static/uploads.ts:12— uploads.handleUpload 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.
next-step-card.NextStepCard (cyclomatic 17) apps/web/src/features/applications/components/detail/next-step-card.tsx:44— next-step-card.NextStepCard has cyclomatic complexity 17 (threshold 15). Of this number, 9 points are the body's own statements and 8 belong 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.
coach-chat.MessageView (cyclomatic 17) apps/web/src/features/career/coach-chat.tsx:262— coach-chat.MessageView has cyclomatic complexity 17 (threshold 15). Of this number, 15 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.
recorder.parse (cyclomatic 17) apps/web/src/features/career/workspace/recorder.ts:234— recorder.parse 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.
apply.ApplyTab (cyclomatic 17) apps/web/src/features/career/workspace/apply.tsx:53— apply.ApplyTab has cyclomatic complexity 17 (threshold 15). Of this number, 14 points are the body's own statements and 3 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.
new-document-dialog.CopyForJob (cyclomatic 17) apps/web/src/features/documents/new-document-dialog.tsx:508— new-document-dialog.CopyForJob has cyclomatic complexity 17 (threshold 15). Of this number, 9 points are the body's own statements and 8 belong to 3 function items inside it that branch. To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
parser-view.ParsedText (cyclomatic 17) apps/web/src/features/resume/editor/check/parser-view.tsx:97— parser-view.ParsedText has cyclomatic complexity 17 (threshold 15). 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 literals inside it that branch (lines 152, 168, 135, …). 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.
dates-field.DatesField (cyclomatic 17) apps/web/src/features/resume/editor/write/dates-field.tsx:96— dates-field.DatesField has cyclomatic complexity 17 (threshold 15). Of this number, 15 points are the body's own statements and 2 belong to 2 function literals inside it that branch. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
read-file.detectJsonImportKind (cyclomatic 17) apps/web/src/features/resume/import/read-file.ts:31— read-file.detectJsonImportKind 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.
service.describeTestConnectionFailure (cyclomatic 17) packages/api/src/features/ai/service.ts:209— service.describeTestConnectionFailure 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.
service.sourceText (cyclomatic 17) packages/api/src/features/career/service.ts:62— service.sourceText has cyclomatic complexity 17 (threshold 15). Of this number, 16 points are the body's own statements and 1 belongs to one function literal inside it that branches. To reduce it, 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.
plain-text.groupEntries (cyclomatic 17) packages/import/src/plain-text.ts:262— plain-text.groupEntries has cyclomatic complexity 17 (threshold 15). Of this number, 14 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.
images.readImageHeader (cyclomatic 17) packages/pdf/src/forme/images.ts:54— images.readImageHeader 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.
style-rules.toStyle (cyclomatic 17) packages/pdf/src/templates/shared/style-rules.ts:46— style-rules.toStyle 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.
cascade.expandVariables (cyclomatic 17) packages/resume/src/stylesheet/cascade.ts:245— cascade.expandVariables 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.
period.parseEndpoint (cyclomatic 17) packages/schema/src/resume/period.ts:155— period.parseEndpoint 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.
fields.Chip (cyclomatic 16) apps/mobile/src/ui/fields.tsx:429— fields.Chip has cyclomatic complexity 16 (threshold 15). Of this number, 10 points are the body's own statements and 6 belong to one function literal inside it that branches. To reduce it, split the body: 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.
offers.OffersScreen (cyclomatic 16) apps/mobile/src/features/career/offers.tsx:17— offers.OffersScreen has cyclomatic complexity 16 (threshold 15). Of this number, 9 points are the body's own statements and 7 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.
import-file.jsonImportFormat (cyclomatic 16) apps/mobile/src/features/documents/import-file.ts:21— import-file.jsonImportFormat 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.
write.DraftBox (cyclomatic 16) apps/mobile/src/features/letters/write.tsx:579— write.DraftBox 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.
apply.Checklist (cyclomatic 16) apps/mobile/src/features/workspace/tabs/apply.tsx:433— apply.Checklist has cyclomatic complexity 16 (threshold 15). Most of this is not in the body itself: 3 of the 16 points are its own statements and the rest belongs to 4 function items inside it that branch (markApplied, a function literal at line 521, share, …). 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.
fit.Fit (cyclomatic 16) apps/mobile/src/features/workspace/tabs/fit.tsx:26— fit.Fit has cyclomatic complexity 16 (threshold 15). Of this number, 11 points are the body's own statements and 5 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.
improve.ImprovePanel (cyclomatic 16) apps/mobile/src/features/write/improve.tsx:28— improve.ImprovePanel has cyclomatic complexity 16 (threshold 15). Of this number, 14 points are the body's own statements and 2 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.
rich-text-field.RichTextField (cyclomatic 16) apps/mobile/src/features/write/rich-text-field.tsx:69— rich-text-field.RichTextField has cyclomatic complexity 16 (threshold 15). Of this number, 8 points are the body's own statements and 8 belong to 6 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.
top-bar.TopBar (cyclomatic 16) apps/mobile/src/shell/top-bar.tsx:30— top-bar.TopBar has cyclomatic complexity 16 (threshold 15). Of this number, 15 points are the body's own statements and 1 belongs to one function literal inside it that branches. To reduce it, 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.
generator.addCurlSamples (cyclomatic 16) apps/server/src/openapi/generator.ts:226— generator.addCurlSamples 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. This shape REPEATS in the file: one other method here (generator.addCurlSamples::example) 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.
checker.Result (cyclomatic 16) apps/web/src/features/ats-checker/checker.tsx:376— checker.Result 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, 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.
preferences.PreferencesForm (cyclomatic 16) apps/web/src/features/career/knowledge/preferences.tsx:55— preferences.PreferencesForm has cyclomatic complexity 16 (threshold 15). Of this number, 12 points are the body's own statements and 4 belong to 3 function literals inside it that branch. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
facts.FactRow (cyclomatic 16) apps/web/src/features/career/knowledge/facts.tsx:339— facts.FactRow 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, 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.
write-panel.DraftBox (cyclomatic 16) apps/web/src/routes/builder/letter/-components/write-panel.tsx:517— write-panel.DraftBox has cyclomatic complexity 16 (threshold 15). Of this number, 15 points are the body's own statements and 1 belongs to one function item inside it that branches. To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
tools.buildCareerTools (cyclomatic 16) packages/api/src/features/career/tools.ts:85— tools.buildCareerTools has cyclomatic complexity 16 (threshold 15). Of this number, 13 points are the body's own statements and 3 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.
parity.decodeInput (cyclomatic 16) packages/mcp/src/parity.ts:295— parity.decodeInput has cyclomatic complexity 16 (threshold 15). Of this number, 15 points are the body's own statements and 1 belongs to one function literal inside it that branches. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
harvest.harvestPdfDocument (cyclomatic 16) packages/resume/src/ats-pdf/harvest.ts:253— harvest.harvestPdfDocument has cyclomatic complexity 16 (threshold 15). Of this number, 15 points are the body's own statements and 1 belongs to one function item inside it that branches. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
generate-reference.renderSchemaReference::visit (cyclomatic 16) tooling/semantic-css/generate-reference.ts:97— generate-reference.renderSchemaReference::visit 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.
cascade.resolveStylesheet (cognitive 204) packages/resume/src/stylesheet/cascade.ts:554— cascade.resolveStylesheet has cognitive complexity 204 (threshold 15). Drivers by points: if/else 59 (154 pts), ternaries 9 (22 pts), loops 10 (15 pts), boolean chains 13 (nesting depth added 113). 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.
practise.Session (cognitive 163) apps/mobile/src/features/workspace/tabs/practise.tsx:185— practise.Session has cognitive complexity 163 (threshold 15). Drivers by points: ternaries 29 (120 pts), if/else 22 (24 pts), boolean chains 18, error handling 1 (nesting depth added 93). Of this number, 118 points are the body's own statements and 45 belong to 13 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.
practise.Session (cognitive 141) apps/web/src/features/career/workspace/practise.tsx:218— practise.Session has cognitive complexity 141 (threshold 15). Drivers by points: ternaries 22 (77 pts), if/else 22 (35 pts), boolean chains 26, error handling 3 (nesting depth added 68). Of this number, 91 points are the body's own statements and 50 belong to 16 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.
style.toFormeStyle (cognitive 126) packages/pdf/src/forme/style.ts:373— style.toFormeStyle has cognitive complexity 126 (threshold 15). Drivers by points: if/else 45 (101 pts), boolean chains 17, ternaries 3 (7 pts), loops 1 (nesting depth added 60). Of this number, 125 points are the body's own statements and 1 belongs 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.
assistant-screen.DocumentAssistantScreen (cognitive 109) apps/mobile/src/features/assistant/assistant-screen.tsx:95— assistant-screen.DocumentAssistantScreen has cognitive complexity 109 (threshold 15). Drivers by points: ternaries 24 (91 pts), if/else 3 (10 pts), boolean chains 8 (nesting depth added 74). Of this number, 76 points are the body's own statements and 33 belong to 7 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.
library.DocumentsLibrary (cognitive 100) apps/mobile/src/features/documents/library.tsx:159— library.DocumentsLibrary has cognitive complexity 100 (threshold 15). Drivers by points: ternaries 30 (70 pts), boolean chains 23, if/else 7 (nesting depth added 40). Of this number, 83 points are the body's own statements and 17 belong to 17 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.
add-sheet.AddApplicationSheet (cognitive 98) apps/mobile/src/features/applications/add-sheet.tsx:48— add-sheet.AddApplicationSheet has cognitive complexity 98 (threshold 15). Drivers by points: boolean chains 46, ternaries 17 (31 pts), if/else 13 (20 pts), error handling 1 (nesting depth added 21). Of this number, 49 points are the body's own statements and 49 belong to 20 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.
html-to-docx.processBlockElement (cognitive 97) packages/docx/src/html-to-docx.ts:149— html-to-docx.processBlockElement has cognitive complexity 97 (threshold 15). Drivers by points: if/else 23 (51 pts), ternaries 10 (31 pts), loops 3 (8 pts), boolean chains 7 (nesting depth added 54). Of this number, 94 points are the body's own statements and 3 belong to 2 function items inside it that branch. To reduce it, 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.
section-sheet.SectionSheet (cognitive 92) apps/mobile/src/features/write/section-sheet.tsx:24— section-sheet.SectionSheet has cognitive complexity 92 (threshold 15). Drivers by points: ternaries 22 (67 pts), if/else 8 (16 pts), boolean chains 9 (nesting depth added 53). Of this number, 69 points are the body's own statements and 23 belong to 10 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.
to-forme.convertNode (cognitive 91) packages/pdf/src/forme/to-forme.tsx:466— to-forme.convertNode has cognitive complexity 91 (threshold 15). Drivers by points: if/else 22 (45 pts), ternaries 10 (21 pts), boolean chains 18, loops 2 (6 pts), match/switch 1 (nesting depth added 38). Of this number, 82 points are the body's own statements and 9 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.
list-screen.ApplicationsList (cognitive 85) apps/mobile/src/features/applications/list-screen.tsx:55— list-screen.ApplicationsList has cognitive complexity 85 (threshold 15). Drivers by points: ternaries 29 (53 pts), boolean chains 26, if/else 5, error handling 1 (nesting depth added 24). Of this number, 54 points are the body's own statements and 31 belong to 8 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.
parse.parseDeepLink (cognitive 85) apps/mobile/src/linking/parse.ts:39— parse.parseDeepLink has cognitive complexity 85 (threshold 15). Drivers by points: if/else 28 (50 pts), boolean chains 20, error handling 3 (6 pts), ternaries 2 (5 pts), loops 2 (4 pts) (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.
html.parseRichText (cognitive 81) REDACTED:63— html.parseRichText has cognitive complexity 81 (threshold 15). Drivers by points: if/else 29 (52 pts), ternaries 5 (18 pts), boolean chains 9, loops 2 (nesting depth added 36). Of this number, 71 points are the body's own statements and 10 belong to 4 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.
new-document.NewDocument (cognitive 80) apps/mobile/src/features/documents/new-document.tsx:24— new-document.NewDocument has cognitive complexity 80 (threshold 15). Drivers by points: boolean chains 32, if/else 23 (28 pts), ternaries 10 (16 pts), error handling 3 (4 pts) (nesting depth added 12). Of this number, 28 points are the body's own statements and 52 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.
coach.CoachPage (cognitive 75) apps/web/src/features/career/coach.tsx:104— coach.CoachPage has cognitive complexity 75 (threshold 15). Drivers by points: ternaries 22 (38 pts), boolean chains 27, if/else 8, error handling 2 (nesting depth added 16). Of this number, 53 points are the body's own statements and 22 belong to 14 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.
today.TodayScreen (cognitive 72) apps/mobile/src/features/career/today.tsx:33— today.TodayScreen has cognitive complexity 72 (threshold 15). Drivers by points: ternaries 32 (55 pts), boolean chains 15, if/else 2 (nesting depth added 23). Of this number, 43 points are the body's own statements and 29 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.
values.expandShorthand (cognitive 70) packages/resume/src/stylesheet/values.ts:241— values.expandShorthand has cognitive complexity 70 (threshold 15). Drivers by points: if/else 23 (56 pts), boolean chains 7, ternaries 2 (7 pts) (nesting depth added 38). Of this number, 69 points are the body's own statements and 1 belongs 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.
chat-view.Conversation (cognitive 66) apps/mobile/src/features/assistant/chat-view.tsx:241— chat-view.Conversation has cognitive complexity 66 (threshold 15). Drivers by points: ternaries 18 (22 pts), boolean chains 20, if/else 15 (20 pts), loops 2 (3 pts), error handling 1 (nesting depth added 10). Of this number, 25 points are the body's own statements and 41 belong to 20 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.
board-screen.Board (cognitive 59) apps/mobile/src/features/applications-board/board-screen.tsx:85— board-screen.Board has cognitive complexity 59 (threshold 15). Drivers by points: if/else 23, ternaries 17 (22 pts), boolean chains 13, loops 1 (nesting depth added 5). Of this number, 22 points are the body's own statements and 37 belong to 17 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.
interview-sheet.InterviewForm (cognitive 57) apps/mobile/src/features/application-detail/interview-sheet.tsx:121— interview-sheet.InterviewForm has cognitive complexity 57 (threshold 15). Drivers by points: ternaries 20 (28 pts), boolean chains 15, if/else 11 (12 pts), error handling 2 (nesting depth added 9). Of this number, 32 points are the body's own statements and 25 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, 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.
offers.OfferCard (cognitive 57) apps/mobile/src/features/career/offers.tsx:101— offers.OfferCard has cognitive complexity 57 (threshold 15). Drivers by points: ternaries 29 (48 pts), boolean chains 8, if/else 1 (nesting depth added 19). Of this number, 51 points are the body's own statements and 6 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.
messages.ToolPartView (cognitive 56) apps/mobile/src/features/assistant/messages.tsx:201— messages.ToolPartView has cognitive complexity 56 (threshold 15). Drivers by points: ternaries 17 (38 pts), if/else 5 (10 pts), boolean chains 7, match/switch 1 (nesting depth added 26). 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.
assistant-panel.AssistantPanel (cognitive 56) apps/web/src/features/assistant/assistant-panel.tsx:53— assistant-panel.AssistantPanel has cognitive complexity 56 (threshold 15). Drivers by points: ternaries 13 (40 pts), if/else 8, boolean chains 6, error handling 2 (nesting depth added 27). Of this number, 42 points are the body's own statements and 14 belong to 7 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.
search-screen.SearchScreen (cognitive 54) apps/mobile/src/features/search/search-screen.tsx:41— search-screen.SearchScreen has cognitive complexity 54 (threshold 15). Drivers by points: ternaries 16 (23 pts), if/else 15 (18 pts), boolean chains 11, loops 1 (2 pts) (nesting depth added 11). Of this number, 29 points are the body's own statements and 25 belong to 13 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.
operators.summarizePageOperators (cognitive 54) packages/resume/src/ats-pdf/analyze/operators.ts:111— operators.summarizePageOperators has cognitive complexity 54 (threshold 15). Drivers by points: if/else 18 (38 pts), ternaries 4 (10 pts), boolean chains 5, loops 1 (nesting depth added 26). Of this number, 53 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.
web-access.WebAccessSettings (cognitive 53) apps/mobile/src/features/ai/web-access.tsx:37— web-access.WebAccessSettings has cognitive complexity 53 (threshold 15). Drivers by points: ternaries 13 (29 pts), boolean chains 17, if/else 5 (6 pts), error handling 1 (nesting depth added 17). Of this number, 45 points are the body's own statements and 8 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.
scroll.useScrollScenes (cognitive 53) apps/web/src/features/homepage/scroll.ts:153— scroll.useScrollScenes has cognitive complexity 53 (threshold 15). Drivers by points: if/else 17 (21 pts), boolean chains 15, ternaries 11 (15 pts), loops 2 (nesting depth added 8). None of this is in the body itself: all 53 points belong to 6 function literals inside it that branch (lines 214, 169, 316, …). 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.
layout.ListRow (cognitive 51) apps/mobile/src/ui/layout.tsx:55— layout.ListRow has cognitive complexity 51 (threshold 15). Drivers by points: ternaries 31 (40 pts), boolean chains 11 (nesting depth added 9). Of this number, 37 points are the body's own statements and 14 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.
chip-input.ChipInput (cognitive 51) apps/web/src/components/input/chip-input.tsx:157— chip-input.ChipInput has cognitive complexity 51 (threshold 15). Drivers by points: if/else 22 (27 pts), boolean chains 14, ternaries 8 (10 pts) (nesting depth added 7). Most of this is not in the body itself: 6 of the 51 points are its own statements and the rest belongs to 10 function items inside it that branch (handleKeyDown, handleDragEnd, handleInputChange, …). 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.
values.valueSyntaxError (cognitive 51) packages/resume/src/stylesheet/values.ts:376— values.valueSyntaxError has cognitive complexity 51 (threshold 15). Drivers by points: if/else 18 (24 pts), ternaries 9 (18 pts), boolean chains 9 (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.
documents-page.DocumentsPage (cognitive 50) apps/web/src/features/documents/documents-page.tsx:54— documents-page.DocumentsPage has cognitive complexity 50 (threshold 15). Drivers by points: ternaries 9 (33 pts), boolean chains 12, if/else 5 (nesting depth added 24). Of this number, 31 points are the body's own statements and 19 belong to 7 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.
config.getAuthConfig (cognitive 50) packages/auth/src/config.ts:257— config.getAuthConfig has cognitive complexity 50 (threshold 15). Drivers by points: if/else 19 (27 pts), boolean chains 16, ternaries 5, error handling 1, loops 1 (nesting depth added 8). Most of this is not in the body itself: 10 of the 50 points are its own statements and the rest belongs to 6 function literals inside it that branch (lines 330, 484, 307, …). 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.
schedule-sheet.ScheduleSheet (cognitive 49) apps/web/src/features/career/schedule-sheet.tsx:129— schedule-sheet.ScheduleSheet has cognitive complexity 49 (threshold 15). Drivers by points: ternaries 28 (37 pts), boolean chains 35, if/else 5 (nesting depth added 9). 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. This shape REPEATS in the file: one other method here (schedule-sheet.ScheduleSheet::onSave) 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.
screen.CheckScreen (cognitive 48) apps/mobile/src/features/check/screen.tsx:25— screen.CheckScreen has cognitive complexity 48 (threshold 15). Drivers by points: ternaries 14 (32 pts), boolean chains 8, if/else 4 (8 pts) (nesting depth added 22). Of this number, 23 points are the body's own statements and 25 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.
link.LinkTab (cognitive 48) apps/mobile/src/features/share/link.tsx:32— link.LinkTab has cognitive complexity 48 (threshold 15). Drivers by points: ternaries 13 (21 pts), boolean chains 15, if/else 10 (11 pts), error handling 1 (nesting depth added 9). Of this number, 31 points are the body's own statements and 17 belong to 8 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.
page.ResumePage (cognitive 48) apps/mobile/src/preview/page.tsx:25— page.ResumePage has cognitive complexity 48 (threshold 15). Drivers by points: ternaries 17 (20 pts), boolean chains 13, if/else 11 (13 pts), error handling 1, loops 1 (nesting depth added 5). Of this number, 17 points are the body's own statements and 31 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, 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.
markdown.parseBlocks (cognitive 47) apps/mobile/src/features/assistant/markdown.tsx:14— markdown.parseBlocks has cognitive complexity 47 (threshold 15). Drivers by points: if/else 10 (23 pts), ternaries 4 (10 pts), loops 4 (9 pts), boolean chains 5 (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.
csv.mapCsvToApplications (cognitive 47) apps/web/src/features/applications/csv.ts:210— csv.mapCsvToApplications has cognitive complexity 47 (threshold 15). Drivers by points: if/else 21 (36 pts), ternaries 2 (5 pts), error handling 1 (3 pts), boolean chains 2, loops 1 (nesting depth added 20). Of this number, 16 points are the body's own statements and 31 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.
generate.generateCareer (cognitive 47) packages/api/src/features/career/generate.ts:100— generate.generateCareer has cognitive complexity 47 (threshold 15). Drivers by points: ternaries 17 (21 pts), if/else 10 (13 pts), boolean chains 7, loops 4 (6 pts) (nesting depth added 9). Of this number, 41 points are the body's own statements and 6 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.
parity.registerParityTools (cognitive 47) packages/mcp/src/parity.ts:344— parity.registerParityTools has cognitive complexity 47 (threshold 15). Drivers by points: if/else 10 (22 pts), ternaries 5 (14 pts), loops 4 (9 pts), boolean chains 2 (nesting depth added 26). Most of this is not in the body itself: 6 of the 47 points are its own statements and the rest belongs to one function literal inside it that branches (line 364). 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.
interview-dialog.InterviewDialog (cognitive 45) apps/web/src/features/applications/components/interview-dialog.tsx:145— interview-dialog.InterviewDialog has cognitive complexity 45 (threshold 15). Drivers by points: ternaries 16 (19 pts), boolean chains 18, if/else 6 (7 pts), error handling 1 (nesting depth added 4). Of this number, 29 points are the body's own statements and 16 belong to 10 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.
import-file.importDocument (cognitive 44) apps/mobile/src/features/documents/import-file.ts:40— import-file.importDocument has cognitive complexity 44 (threshold 15). Drivers by points: if/else 17 (22 pts), boolean chains 10, ternaries 5 (10 pts), error handling 1 (2 pts) (nesting depth added 11). Of this number, 42 points are the body's own statements and 2 belong to one function item inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
history.HistoryPanel (cognitive 44) apps/mobile/src/features/history/history.tsx:52— history.HistoryPanel has cognitive complexity 44 (threshold 15). Drivers by points: boolean chains 18, ternaries 10 (17 pts), if/else 8 (9 pts) (nesting depth added 8). Of this number, 23 points are the body's own statements and 21 belong to 8 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.
outline.Outline (cognitive 44) apps/mobile/src/features/write/outline.tsx:50— outline.Outline has cognitive complexity 44 (threshold 15). Drivers by points: ternaries 20 (26 pts), if/else 13 (14 pts), boolean chains 4 (nesting depth added 7). Of this number, 16 points are the body's own statements and 28 belong to 11 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.
messages-merge.mergeClientToolResponses (cognitive 44) packages/api/src/features/agent/messages-merge.ts:50— messages-merge.mergeClientToolResponses has cognitive complexity 44 (threshold 15). Drivers by points: if/else 14 (32 pts), ternaries 2 (7 pts), boolean chains 4, loops 1 (nesting depth added 23). Most of this is not in the body itself: 9 of the 44 points are its own statements and the rest belongs to one function literal inside it that branches (line 81). 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.
schedule-sheet.ScheduleForm (cognitive 43) apps/mobile/src/features/career/schedule-sheet.tsx:80— schedule-sheet.ScheduleForm has cognitive complexity 43 (threshold 15). Drivers by points: ternaries 29 (51 pts), boolean chains 12, if/else 6 (8 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. This shape REPEATS in the file: one other method here (schedule-sheet.ScheduleForm::save) 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.
improve.ImprovePanel (cognitive 43) apps/mobile/src/features/write/improve.tsx:28— improve.ImprovePanel has cognitive complexity 43 (threshold 15). Drivers by points: ternaries 13 (41 pts), boolean chains 2 (nesting depth added 28). Of this number, 41 points are the body's own statements and 2 belong to 2 function items inside it that branch. To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
generator.addCurlSamples (cognitive 43) apps/server/src/openapi/generator.ts:226— generator.addCurlSamples has cognitive complexity 43 (threshold 15). Drivers by points: ternaries 9 (27 pts), if/else 14 (21 pts), loops 4 (8 pts), boolean chains 7 (nesting depth added 29). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body. This shape REPEATS in the file: one other method here (generator.addCurlSamples::example) 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.
rich-text-markup.hasUnsupportedTableMarkup (cognitive 43) apps/web/src/components/input/rich-text-markup.ts:360— rich-text-markup.hasUnsupportedTableMarkup has cognitive complexity 43 (threshold 15). Drivers by points: if/else 15 (34 pts), loops 3 (5 pts), boolean chains 4 (nesting depth added 21). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
calendar-screen.ApplicationCalendar (cognitive 42) apps/mobile/src/features/applications-board/calendar-screen.tsx:51— calendar-screen.ApplicationCalendar has cognitive complexity 42 (threshold 15). Drivers by points: ternaries 26 (37 pts), if/else 3, boolean chains 2 (nesting depth added 11). Most of this is not in the body itself: 10 of the 42 points are its own statements and the rest belongs to 6 function items inside it that branch (a function literal at line 219, dayHeading, a function literal at line 81, …). 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.
share.LetterHistory (cognitive 42) apps/mobile/src/features/letters/share.tsx:275— share.LetterHistory has cognitive complexity 42 (threshold 15). Drivers by points: ternaries 12 (20 pts), if/else 11 (13 pts), boolean chains 9 (nesting depth added 10). Of this number, 19 points are the body's own statements and 23 belong to 7 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.
generator.generateOpenApiSpec (cognitive 42) apps/server/src/openapi/generator.ts:89— generator.generateOpenApiSpec has cognitive complexity 42 (threshold 15). Drivers by points: if/else 9 (26 pts), boolean chains 10, loops 3 (6 pts) (nesting depth added 20). Of this number, 37 points are the body's own statements and 5 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.
today.Schedules (cognitive 42) apps/web/src/features/career/today.tsx:658— today.Schedules has cognitive complexity 42 (threshold 15). Drivers by points: ternaries 15 (27 pts), boolean chains 8, if/else 7 (nesting depth added 12). Most of this is not in the body itself: 7 of the 42 points are its own statements and the rest belongs to 10 function items inside it that branch (status, describe, toggle, …). 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.
index.RouteComponent (cognitive 42) apps/web/src/routes/dashboard/applications/index.tsx:70— index.RouteComponent has cognitive complexity 42 (threshold 15). Drivers by points: boolean chains 24, ternaries 6 (16 pts), if/else 2 (nesting depth added 10). Of this number, 36 points are the body's own statements and 6 belong 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.
layout-screen.LayoutScreen (cognitive 41) apps/mobile/src/features/design/layout-screen.tsx:44— layout-screen.LayoutScreen has cognitive complexity 41 (threshold 15). Drivers by points: ternaries 16 (20 pts), boolean chains 9, if/else 7 (9 pts), loops 2 (3 pts) (nesting depth added 7). Most of this is not in the body itself: 2 of the 41 points are its own statements and the rest belongs to 11 function items inside it that branch (begin, column, move, …). 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.
jobs.execute (cognitive 41) packages/api/src/features/career/jobs.ts:343— jobs.execute has cognitive complexity 41 (threshold 15). Drivers by points: if/else 11 (16 pts), ternaries 7 (15 pts), boolean chains 9, loops 1 (nesting depth added 13). Most of this is not in the body itself: 12 of the 41 points are its own statements and the rest belongs to one function literal inside it that branches (line 385). 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.
compare-resume.hasDuplicateJsonMembers (cognitive 41) tooling/recovery/compare-resume.ts:61— compare-resume.hasDuplicateJsonMembers has cognitive complexity 41 (threshold 15). Drivers by points: if/else 22 (35 pts), loops 5, boolean chains 1 (nesting depth added 13). Most of this is not in the body itself: 2 of the 41 points are its own statements and the rest belongs to 5 function items inside it that branch (scanObject, scanString, scanArray, …). 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.
store.createDraftStore.open (cognitive 40) apps/mobile/src/draft/store.ts:173— store.createDraftStore.open has cognitive complexity 40 (threshold 15). Drivers by points: if/else 19 (22 pts), ternaries 4 (9 pts), boolean chains 6, error handling 2 (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.
conversation.Composer (cognitive 40) apps/web/src/features/assistant/conversation.tsx:674— conversation.Composer has cognitive complexity 40 (threshold 15). Drivers by points: ternaries 13 (20 pts), boolean chains 13, if/else 6, error handling 1 (nesting depth added 7). Of this number, 29 points are the body's own statements and 11 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.
provider-editor.ProviderForm (cognitive 39) apps/mobile/src/features/ai/provider-editor.tsx:75— provider-editor.ProviderForm has cognitive complexity 39 (threshold 15). Drivers by points: boolean chains 25, ternaries 16 (24 pts), if/else 13 (14 pts), error handling 3 (nesting depth added 9). 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. This shape REPEATS in the file: one other method here (provider-editor.ProviderForm::save) 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.
shell.WorkspaceScreen (cognitive 39) apps/mobile/src/features/workspace/shell.tsx:68— shell.WorkspaceScreen has cognitive complexity 39 (threshold 15). Drivers by points: ternaries 11 (26 pts), boolean chains 8, if/else 3 (5 pts) (nesting depth added 17). Of this number, 36 points are the body's own statements and 3 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.
model.resolveDrop (cognitive 39) apps/mobile/src/features/write/model.ts:425— model.resolveDrop has cognitive complexity 39 (threshold 15). Drivers by points: if/else 10 (26 pts), boolean chains 6, loops 2 (5 pts), ternaries 1 (2 pts) (nesting depth added 20). Of this number, 36 points are the body's own statements and 3 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.
web-access.WebAccessSection (cognitive 39) apps/web/src/features/settings/ai/web-access.tsx:30— web-access.WebAccessSection has cognitive complexity 39 (threshold 15). Drivers by points: ternaries 10 (21 pts), boolean chains 18 (nesting depth added 11). 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.
overlays.Sheet (cognitive 38) apps/mobile/src/ui/overlays.tsx:92— overlays.Sheet has cognitive complexity 38 (threshold 15). Drivers by points: ternaries 12 (18 pts), if/else 10 (14 pts), boolean chains 6 (nesting depth added 10). Of this number, 19 points are the body's own statements and 19 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.
apply.AnswerCard (cognitive 38) apps/mobile/src/features/workspace/tabs/apply.tsx:206— apply.AnswerCard has cognitive complexity 38 (threshold 15). Drivers by points: ternaries 18 (25 pts), boolean chains 10, if/else 2 (3 pts) (nesting depth added 8). Of this number, 24 points are the body's own statements and 14 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.
messages-persistence.applyStepToUiMessage (cognitive 38) packages/api/src/features/agent/messages-persistence.ts:110— messages-persistence.applyStepToUiMessage has cognitive complexity 38 (threshold 15). Drivers by points: if/else 8 (16 pts), ternaries 4 (14 pts), boolean chains 7, loops 1 (nesting depth added 18). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
ai-consent.authorizeAiRequest (cognitive 37) apps/mobile/src/api/ai-consent.ts:11— ai-consent.authorizeAiRequest has cognitive complexity 37 (threshold 15). Drivers by points: ternaries 12 (18 pts), boolean chains 13, if/else 6 (nesting depth added 6). Of this number, 26 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.
job-match.JobMatch (cognitive 37) apps/mobile/src/features/check/job-match.tsx:25— job-match.JobMatch has cognitive complexity 37 (threshold 15). Drivers by points: boolean chains 14, ternaries 9 (14 pts), if/else 7 (8 pts), error handling 1 (nesting depth added 6). Of this number, 22 points are the body's own statements and 15 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.
preview.browser.ResumePreviewClient (cognitive 37) apps/web/src/features/resume/preview/preview.browser.tsx:111— preview.browser.ResumePreviewClient has cognitive complexity 37 (threshold 15). Drivers by points: ternaries 13 (18 pts), if/else 10 (12 pts), boolean chains 6, error handling 1 (nesting depth added 7). Most of this is not in the body itself: 4 of the 37 points are its own statements and the rest belongs to 9 function literals inside it that branch (lines 152, 140, 268, …). 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.
page-canvas.PageCanvas (cognitive 37) apps/web/src/routes/builder/$resumeId/-components/page-canvas.tsx:33— page-canvas.PageCanvas has cognitive complexity 37 (threshold 15). Drivers by points: boolean chains 16, ternaries 12 (16 pts), if/else 5 (nesting depth added 4). Of this number, 27 points are the body's own statements and 10 belong to 4 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.
builder.buildDocument (cognitive 37) packages/docx/src/builder.ts:282— builder.buildDocument has cognitive complexity 37 (threshold 15). Drivers by points: if/else 6 (13 pts), loops 4 (10 pts), ternaries 7 (8 pts), boolean chains 6 (nesting depth added 14). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
proposals.collectPassages (cognitive 37) packages/resume/src/proposals.ts:253— proposals.collectPassages has cognitive complexity 37 (threshold 15). Drivers by points: if/else 6 (17 pts), ternaries 3 (11 pts), loops 3 (7 pts), boolean chains 2 (nesting depth added 23). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
design-pane.DesignPane (cognitive 36) apps/mobile/src/features/design/design-pane.tsx:41— design-pane.DesignPane has cognitive complexity 36 (threshold 15). Drivers by points: ternaries 20 (39 pts), if/else 12 (18 pts), boolean chains 4 (nesting depth added 25). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body. This shape REPEATS in the file: one other method here (design-pane.DesignPane::body) 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.
rich-input-whitespace.markPastedHtml::normalize (cognitive 36) apps/web/src/components/input/rich-input-whitespace.ts:56— rich-input-whitespace.markPastedHtml::normalize has cognitive complexity 36 (threshold 15). Drivers by points: if/else 9 (23 pts), loops 3 (9 pts), boolean chains 4 (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.
today.NewRoles (cognitive 36) apps/web/src/features/career/today.tsx:300— today.NewRoles has cognitive complexity 36 (threshold 15). Drivers by points: ternaries 12 (26 pts), boolean chains 8, if/else 2 (nesting depth added 14). Of this number, 16 points are the body's own statements and 20 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.
pages.LayoutPages (cognitive 36) apps/web/src/routes/builder/$resumeId/-sidebar/right/sections/layout/pages.tsx:88— pages.LayoutPages has cognitive complexity 36 (threshold 15). Drivers by points: if/else 20 (26 pts), boolean chains 6, ternaries 3, loops 1 (nesting depth added 6). Most of this is not in the body itself: 3 of the 36 points are its own statements and the rest belongs to 7 function literals inside it that branch (lines 126, 105, 198, …). 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.
sections.NextStepCard (cognitive 35) apps/mobile/src/features/application-detail/sections.tsx:149— sections.NextStepCard has cognitive complexity 35 (threshold 15). Drivers by points: ternaries 20 (27 pts), boolean chains 7, if/else 1 (nesting depth added 7). Of this number, 33 points are the body's own statements and 2 belong to one function item inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
shell.Workspace (cognitive 35) apps/web/src/features/career/workspace/shell.tsx:110— shell.Workspace has cognitive complexity 35 (threshold 15). Drivers by points: boolean chains 21, ternaries 9 (10 pts), if/else 4 (nesting depth added 1). Of this number, 24 points are the body's own statements and 11 belong 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.
rich-text-editor-field.RichTextEditor (cognitive 35) apps/web/src/features/resume/editor/write/rich-text-editor-field.tsx:190— rich-text-editor-field.RichTextEditor has cognitive complexity 35 (threshold 15). Drivers by points: boolean chains 22, ternaries 8, if/else 5. Of this number, 17 points are the body's own statements and 18 belong to 10 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.
error-message.getReadableErrorMessage (cognitive 35) apps/web/src/libs/error-message.ts:5— error-message.getReadableErrorMessage has cognitive complexity 35 (threshold 15). Drivers by points: if/else 11 (24 pts), boolean chains 8, loops 1 (3 pts) (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.
reactive-resume-v4-json.parseReactiveResumeV4JSON (cognitive 35) packages/import/src/reactive-resume-v4-json.tsx:241— reactive-resume-v4-json.parseReactiveResumeV4JSON has cognitive complexity 35 (threshold 15). Drivers by points: boolean chains 17, ternaries 8 (9 pts), if/else 5 (8 pts), error handling 1 (nesting depth added 4). Of this number, 19 points are the body's own statements and 16 belong to 14 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.
tree.buildItem (cognitive 35) packages/pdf/src/semantic/tree.ts:257— tree.buildItem has cognitive complexity 35 (threshold 15). Drivers by points: ternaries 7 (12 pts), if/else 8 (11 pts), boolean chains 9, loops 2 (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.
rich-text.RichText (cognitive 35) packages/pdf/src/templates/shared/rich-text.tsx:76— rich-text.RichText has cognitive complexity 35 (threshold 15). Drivers by points: ternaries 18 (21 pts), if/else 8 (9 pts), boolean chains 5 (nesting depth added 4). Most of this is not in the body itself: 9 of the 35 points are its own statements and the rest belongs to 7 function items inside it that branch (a function literal at line 235, renderText, renderView, …). 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.
date-field.WallClockField (cognitive 34) apps/mobile/src/features/application-detail/date-field.tsx:37— date-field.WallClockField has cognitive complexity 34 (threshold 15). Drivers by points: ternaries 12 (21 pts), if/else 4 (8 pts), boolean chains 5 (nesting depth added 13). Of this number, 22 points are the body's own statements and 12 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.
facts.Facts (cognitive 34) apps/mobile/src/features/career/facts.tsx:58— facts.Facts has cognitive complexity 34 (threshold 15). Drivers by points: ternaries 10 (25 pts), boolean chains 7, error handling 1, if/else 1 (nesting depth added 15). Of this number, 28 points are the body's own statements and 6 belong to 3 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.
preferences.Preferences (cognitive 34) apps/mobile/src/features/career/preferences.tsx:18— preferences.Preferences has cognitive complexity 34 (threshold 15). Drivers by points: ternaries 20 (25 pts), boolean chains 6, if/else 3 (nesting depth added 5). Of this number, 27 points are the body's own statements and 7 belong to 5 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.
add-application-dialog.AddApplicationForm (cognitive 34) apps/web/src/features/applications/components/add-application-dialog.tsx:68— add-application-dialog.AddApplicationForm has cognitive complexity 34 (threshold 15). Drivers by points: boolean chains 38, ternaries 17 (19 pts), if/else 6, error handling 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. This shape REPEATS in the file: one other method here (add-application-dialog.AddApplicationForm::add) 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.
conversation.ToolPartView (cognitive 34) apps/web/src/features/assistant/conversation.tsx:419— conversation.ToolPartView has cognitive complexity 34 (threshold 15). Drivers by points: ternaries 7 (18 pts), if/else 4 (8 pts), boolean chains 7, match/switch 1 (nesting depth added 15). The drivers above price the dispatch low by construction — a dispatch is charged once however many cases it lists, while each branch inside an arm is charged in full — so most of this count is what the case bodies hold, and the arms are where it can be reduced. To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident.
context.collapseOldestToolPairs (cognitive 34) packages/api/src/features/agent/context.ts:117— context.collapseOldestToolPairs has cognitive complexity 34 (threshold 15). Drivers by points: if/else 9 (19 pts), boolean chains 7, loops 4 (5 pts), ternaries 2 (3 pts) (nesting depth added 12). Of this number, 23 points are the body's own statements and 11 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.
index.DocumentMenu (cognitive 33) apps/mobile/src/features/document-menu/index.tsx:26— index.DocumentMenu has cognitive complexity 33 (threshold 15). Drivers by points: boolean chains 24, ternaries 5 (6 pts), if/else 3 (nesting depth added 1). Of this number, 28 points are the body's own statements and 5 belong to 5 function items inside it that branch. To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
extract.findGutter (cognitive 33) packages/resume/src/ats-pdf/extract.ts:224— extract.findGutter has cognitive complexity 33 (threshold 15). Drivers by points: if/else 13 (21 pts), loops 5 (7 pts), boolean chains 4, 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.
harvest.harvestPdfDocument (cognitive 33) packages/resume/src/ats-pdf/harvest.ts:253— harvest.harvestPdfDocument has cognitive complexity 33 (threshold 15). Drivers by points: if/else 8 (22 pts), loops 3 (6 pts), ternaries 2 (3 pts), boolean chains 2 (nesting depth added 18). Of this number, 32 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.
selector.compileSimple (cognitive 33) packages/resume/src/stylesheet/selector.ts:175— selector.compileSimple has cognitive complexity 33 (threshold 15). Drivers by points: if/else 12 (27 pts), boolean chains 5, match/switch 1 (nesting depth added 15). The drivers above price the dispatch low by construction — a dispatch is charged once however many cases it lists, while each branch inside an arm is charged in full — so most of this count is what the case bodies hold, and the arms are where it can be reduced. To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident.
cascade.structuralValue (cognitive 33) packages/resume/src/stylesheet/cascade.ts:494— cascade.structuralValue has cognitive complexity 33 (threshold 15). Drivers by points: if/else 21 (28 pts), boolean chains 5 (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.
writing.Writing (cognitive 32) apps/mobile/src/features/check/writing.tsx:37— writing.Writing has cognitive complexity 32 (threshold 15). Drivers by points: ternaries 5 (15 pts), boolean chains 8, if/else 7 (8 pts), error handling 1 (nesting depth added 11). Of this number, 20 points are the body's own statements and 12 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.
share.LetterDownload (cognitive 32) apps/mobile/src/features/letters/share.tsx:88— share.LetterDownload has cognitive complexity 32 (threshold 15). Drivers by points: ternaries 11 (14 pts), boolean chains 11, if/else 5, error handling 1, loops 1 (nesting depth added 3). Most of this is not in the body itself: 15 of the 32 points are its own statements and the rest belongs to 2 function items inside it that branch (download, a function literal at line 202). 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.
shell.ContextColumn (cognitive 32) apps/web/src/features/career/workspace/shell.tsx:465— shell.ContextColumn has cognitive complexity 32 (threshold 15). Drivers by points: boolean chains 23, ternaries 8, if/else 1. Of this number, 28 points are the body's own statements and 4 belong to 4 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.
json-resume.convertJSONResume (cognitive 32) packages/import/src/json-resume.tsx:155— json-resume.convertJSONResume has cognitive complexity 32 (threshold 15). Drivers by points: boolean chains 32. 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.
html-to-odt.processBlock (cognitive 32) packages/odt/src/html-to-odt.ts:162— html-to-odt.processBlock has cognitive complexity 32 (threshold 15). Drivers by points: if/else 12 (21 pts), ternaries 3 (5 pts), loops 2 (4 pts), boolean chains 2 (nesting depth added 13). Of this number, 28 points are the body's own statements and 4 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.
checker.Result (cognitive 31) apps/mobile/src/features/ats-checker/checker.tsx:332— checker.Result has cognitive complexity 31 (threshold 15). Drivers by points: ternaries 17 (30 pts), boolean chains 1 (nesting depth added 13). Of this number, 26 points are the body's own statements and 5 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.
combobox.Combobox (cognitive 30) apps/web/src/components/ui/combobox.tsx:72— combobox.Combobox has cognitive complexity 30 (threshold 15). Drivers by points: ternaries 11 (17 pts), if/else 6 (7 pts), boolean chains 6 (nesting depth added 7). Most of this is not in the body itself: 9 of the 30 points are its own statements and the rest belongs to 5 function items inside it that branch (handleExternalChange, findOption, filter, …). 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.
list-view.ApplicationList (cognitive 30) apps/web/src/features/applications/components/list-view.tsx:62— list-view.ApplicationList has cognitive complexity 30 (threshold 15). Drivers by points: ternaries 9 (15 pts), boolean chains 10, if/else 5 (nesting depth added 6). Most of this is not in the body itself: 4 of the 30 points are its own statements and the rest belongs to 9 function items inside it that branch (a function literal at line 162, a function literal at line 115, header, …). 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.
legacy-converter.activeSlotChunks (cognitive 30) packages/pdf/src/semantic/legacy-converter.ts:169— legacy-converter.activeSlotChunks has cognitive complexity 30 (threshold 15). Drivers by points: if/else 11 (16 pts), boolean chains 13, ternaries 1 (nesting depth added 5). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
insights-view.uiFontFace (cognitive 29) apps/web/src/features/applications/components/insights-view.tsx:217— insights-view.uiFontFace has cognitive complexity 29 (threshold 15). Drivers by points: if/else 7 (19 pts), error handling 2 (5 pts), loops 2 (3 pts), boolean chains 2 (nesting depth added 16). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
stories.StoriesPage (cognitive 29) apps/web/src/features/career/knowledge/stories.tsx:52— stories.StoriesPage has cognitive complexity 29 (threshold 15). Drivers by points: ternaries 8 (17 pts), boolean chains 10, if/else 2 (nesting depth added 9). Of this number, 28 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.
offers.useCells (cognitive 29) apps/web/src/features/career/offers.tsx:393— offers.useCells has cognitive complexity 29 (threshold 15). Drivers by points: ternaries 16 (23 pts), boolean chains 3, if/else 3 (nesting depth added 7). None of this is in the body itself: all 29 points belong to 3 function literals inside it that branch (lines 397, 408, 426). 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.
page-layer.CheckPageLayer (cognitive 29) apps/web/src/features/resume/editor/check/page-layer.tsx:86— page-layer.CheckPageLayer has cognitive complexity 29 (threshold 15). Drivers by points: ternaries 9 (13 pts), boolean chains 9, if/else 5 (7 pts) (nesting depth added 6). Most of this is not in the body itself: 8 of the 29 points are its own statements and the rest belongs to 6 function items inside it that branch (a function literal at line 121, a function literal at line 111, a function literal at line 156, …). 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.
checker.AtsChecker (cognitive 28) apps/mobile/src/features/ats-checker/checker.tsx:41— checker.AtsChecker has cognitive complexity 28 (threshold 15). Drivers by points: ternaries 7 (13 pts), if/else 8 (10 pts), error handling 3, boolean chains 2 (nesting depth added 8). Most of this is not in the body itself: 7 of the 28 points are its own statements and the rest belongs to 6 function items inside it that branch (check, importAndOpen, a function literal at line 124, …). 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.
parser.Parser (cognitive 28) apps/mobile/src/features/check/parser.tsx:23— parser.Parser has cognitive complexity 28 (threshold 15). Drivers by points: boolean chains 12, if/else 8 (9 pts), ternaries 3 (5 pts), error handling 2 (nesting depth added 3). Most of this is not in the body itself: 12 of the 28 points are its own statements and the rest belongs to 3 function literals inside it that branch (lines 54, 41, 78). 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.
document-sheets.DocumentSheets (cognitive 28) apps/mobile/src/features/documents/document-sheets.tsx:26— document-sheets.DocumentSheets has cognitive complexity 28 (threshold 15). Drivers by points: boolean chains 26, if/else 2. Of this number, 24 points are the body's own statements and 4 belong to 9 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.
public-resume.PublicResume (cognitive 28) apps/mobile/src/features/public/public-resume.tsx:29— public-resume.PublicResume has cognitive complexity 28 (threshold 15). Drivers by points: ternaries 7 (11 pts), boolean chains 8, if/else 7, error handling 2 (nesting depth added 4). Of this number, 20 points are the body's own statements and 8 belong to 5 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.
application-form-sheet.ApplicationFormSheet (cognitive 28) apps/web/src/features/applications/components/application-form-sheet.tsx:203— application-form-sheet.ApplicationFormSheet has cognitive complexity 28 (threshold 15). Drivers by points: boolean chains 15, if/else 7, ternaries 5 (6 pts) (nesting depth added 1). Of this number, 16 points are the body's own statements and 12 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.
conversation.Conversation (cognitive 28) apps/web/src/features/assistant/conversation.tsx:66— conversation.Conversation has cognitive complexity 28 (threshold 15). Drivers by points: if/else 8 (12 pts), boolean chains 10, loops 2 (3 pts), ternaries 3 (nesting depth added 5). Most of this is not in the body itself: 6 of the 28 points are its own statements and the rest belongs to 9 function items inside it that branch (a function literal at line 161, send, a function literal at line 101, …). 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.
coach-screen.CoachScreen (cognitive 27) apps/mobile/src/features/assistant/coach-screen.tsx:68— coach-screen.CoachScreen has cognitive complexity 27 (threshold 15). Drivers by points: ternaries 15 (18 pts), boolean chains 8, if/else 1 (nesting depth added 3). Of this number, 24 points are the body's own statements and 3 belong to 3 function literals inside it that branch. To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition.
logic.parseNumber (cognitive 27) apps/mobile/src/features/workspace/logic.ts:300— logic.parseNumber has cognitive complexity 27 (threshold 15). Drivers by points: if/else 9 (19 pts), boolean chains 7, 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.
today.NeedsYou (cognitive 27) apps/web/src/features/career/today.tsx:132— today.NeedsYou has cognitive complexity 27 (threshold 15). Drivers by points: ternaries 11 (19 pts), boolean chains 6, if/else 2 (nesting depth added 8). Most of this is not in the body itself: 13 of the 27 points are its own statements and the rest belongs to 5 function items inside it that branch (meta, a function literal at line 214, act, …). 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.
recorder.parse (cognitive 27) apps/web/src/features/career/workspace/recorder.ts:234— recorder.parse has cognitive complexity 27 (threshold 15). Drivers by points: if/else 9 (19 pts), boolean chains 7, 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.
entry-card.EntryCard (cognitive 27) apps/web/src/features/resume/editor/write/entry-card.tsx:65— entry-card.EntryCard has cognitive complexity 27 (threshold 15). Drivers by points: boolean chains 19, if/else 4, ternaries 4. Of this number, 19 points are the body's own statements and 8 belong to 4 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.
fetch-prebuilt.main (cognitive 27) packages/forme-native/scripts/fetch-prebuilt.mjs:8— fetch-prebuilt.main has cognitive complexity 27 (threshold 15). Drivers by points: if/else 13 (17 pts), boolean chains 7, loops 2, ternaries 1 (nesting depth added 4). 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: 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.
tree.partMatchesOwner (cognitive 27) packages/pdf/src/semantic/tree.ts:668— tree.partMatchesOwner has cognitive complexity 27 (threshold 15). Drivers by points: if/else 13 (16 pts), boolean chains 10, 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.
library.DocumentItem (cognitive 26) apps/mobile/src/features/documents/library.tsx:62— library.DocumentItem has cognitive complexity 26 (threshold 15). Drivers by points: ternaries 14 (15 pts), boolean chains 10, if/else 1 (nesting depth added 1). Of this number, 25 points are the body's own statements and 1 belongs to one function item inside it that branches. To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
picture-screen.PictureScreen (cognitive 26) apps/mobile/src/features/write/picture-screen.tsx:41— picture-screen.PictureScreen has cognitive complexity 26 (threshold 15). Drivers by points: if/else 11, ternaries 9 (10 pts), boolean chains 4, error handling 1 (nesting depth added 1). Most of this is not in the body itself: 8 of the 26 points are its own statements and the rest belongs to 6 function items inside it that branch (a function literal at line 61, remove, set, …). 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.
builder-chrome.Frame (cognitive 26) apps/mobile/src/shell/builder-chrome.tsx:112— builder-chrome.Frame has cognitive complexity 26 (threshold 15). Drivers by points: ternaries 12, boolean chains 7, if/else 6 (7 pts) (nesting depth added 1). Of this number, 15 points are the body's own statements and 11 belong to 5 function items 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.
sent-documents.SentDocuments (cognitive 26) apps/web/src/features/applications/components/detail/sent-documents.tsx:53— sent-documents.SentDocuments has cognitive complexity 26 (threshold 15). Drivers by points: boolean chains 14, ternaries 7 (11 pts), error handling 1 (nesting depth added 4). Of this number, 18 points are the body's own statements and 8 belong to 5 function items inside it that branch. To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
consent.OAuthConsentPage (cognitive 26) apps/web/src/features/auth/pages/consent.tsx:42— consent.OAuthConsentPage has cognitive complexity 26 (threshold 15). Drivers by points: boolean chains 13, ternaries 4 (10 pts), if/else 3 (nesting depth added 6). Of this number, 21 points are the body's own statements and 5 belong to 2 function items inside it that branch. To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
letter-page.LetterPage (cognitive 26) apps/web/src/routes/builder/letter/-components/letter-page.tsx:47— letter-page.LetterPage has cognitive complexity 26 (threshold 15). Drivers by points: ternaries 10 (13 pts), boolean chains 10, if/else 3 (nesting depth added 3). Of this number, 14 points are the body's own statements and 12 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.
legacy-styles-migration.migrateLegacyStyles (cognitive 26) packages/api/src/features/resume/legacy-styles-migration.ts:77— legacy-styles-migration.migrateLegacyStyles has cognitive complexity 26 (threshold 15). Drivers by points: if/else 4 (13 pts), loops 3 (6 pts), error handling 1 (4 pts), ternaries 1 (3 pts) (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.
level-display.LevelDisplay (cognitive 26) packages/pdf/src/templates/shared/level-display.tsx:26— level-display.LevelDisplay has cognitive complexity 26 (threshold 15). Drivers by points: ternaries 9 (13 pts), if/else 11, boolean chains 2 (nesting depth added 4). Most of this is not in the body itself: 9 of the 26 points are its own statements and the rest belongs to one function literal inside it that branches (line 69). 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.
move-item.moveItem (cognitive 26) packages/resume/src/move-item.ts:17— move-item.moveItem has cognitive complexity 26 (threshold 15). Drivers by points: if/else 9 (13 pts), boolean chains 7, ternaries 3 (6 pts) (nesting depth added 7). Of this number, 24 points are the body's own statements and 2 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.
cascade.expandedWinnersFor (cognitive 26) packages/resume/src/stylesheet/cascade.ts:344— cascade.expandedWinnersFor has cognitive complexity 26 (threshold 15). Drivers by points: if/else 7 (18 pts), loops 4 (7 pts), boolean chains 1 (nesting depth added 14). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
generate-reference.renderSchemaReference::visit (cognitive 26) tooling/semantic-css/generate-reference.ts:97— generate-reference.renderSchemaReference::visit has cognitive complexity 26 (threshold 15). Drivers by points: ternaries 6 (14 pts), if/else 4 (6 pts), loops 3 (4 pts), boolean chains 2 (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.
preferences.PreferencesScreen (cognitive 25) apps/mobile/app/(tabs)/settings/preferences.tsx:34— preferences.PreferencesScreen has cognitive complexity 25 (threshold 15). Drivers by points: ternaries 12 (17 pts), boolean chains 4, error handling 2, if/else 2 (nesting depth added 5). Of this number, 21 points are the body's own statements and 4 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.
open.redirectSystemPath (cognitive 25) apps/mobile/src/linking/open.ts:33— open.redirectSystemPath has cognitive complexity 25 (threshold 15). Drivers by points: if/else 10 (15 pts), ternaries 3 (5 pts), error handling 2 (3 pts), boolean chains 1, loops 1 (nesting depth added 8). Most of this is not in the body itself: 3 of the 25 points are its own statements and the rest belongs to one function literal inside it that branches (line 44). The decisions are inside the literal, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literal's work into a named function or method at the enclosing scope and have the literal call it, then reduce whichever part then reads as the largest.
apply.AnswerCard (cognitive 25) apps/web/src/features/career/workspace/apply.tsx:230— apply.AnswerCard has cognitive complexity 25 (threshold 15). Drivers by points: boolean chains 11, ternaries 8 (9 pts), if/else 3 (5 pts) (nesting depth added 3). Of this number, 18 points are the body's own statements and 7 belong to 4 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.
sanitize.coerceValueAgainstTemplate (cognitive 25) packages/ai/src/resume/sanitize.ts:110— sanitize.coerceValueAgainstTemplate has cognitive complexity 25 (threshold 15). Drivers by points: if/else 12 (18 pts), boolean chains 4, 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.
service.createAgent (cognitive 25) packages/api/src/features/agent/service.ts:732— service.createAgent has cognitive complexity 25 (threshold 15). Drivers by points: if/else 7 (8 pts), ternaries 6 (8 pts), loops 3 (5 pts), boolean chains 3, error handling 1 (nesting depth added 5). Of this number, 16 points are the body's own statements and 9 belong to 7 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.
values.cssFunctionDepth (cognitive 25) packages/resume/src/stylesheet/values.ts:91— values.cssFunctionDepth has cognitive complexity 25 (threshold 15). Drivers by points: if/else 9 (21 pts), boolean chains 3, 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.
button.Button (cognitive 24) apps/mobile/src/ui/button.tsx:39— button.Button has cognitive complexity 24 (threshold 15). Drivers by points: ternaries 15 (18 pts), boolean chains 6 (nesting depth added 3). Most of this is not in the body itself: 9 of the 24 points are its own statements and the rest belongs to one function literal inside it that branches (line 85). 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.
host.server (cognitive 24) apps/mobile/scripts/parity/host.mts:55— host.server has cognitive complexity 24 (threshold 15). Drivers by points: boolean chains 10, if/else 7, ternaries 2 (4 pts), loops 1 (2 pts), error handling 1 (nesting depth added 3). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition.
csv.parseCsv (cognitive 24) apps/web/src/features/applications/csv.ts:13— csv.parseCsv has cognitive complexity 24 (threshold 15). Drivers by points: if/else 11 (20 pts), boolean chains 3, loops 1 (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
new-document-dialog.useResumeImport.importFile (cognitive 24) apps/web/src/features/documents/new-document-dialog.tsx:73— new-document-dialog.useResumeImport.importFile has cognitive complexity 24 (threshold 15). Drivers by points: if/else 10 (14 pts), boolean chains 4, error handling 2 (3 pts), ternaries 2 (3 pts) (nesting depth added 6). Of this number, 22 points are the body's own statements and 2 belong to one function literal inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
editor.StylesheetCodeEditor (cognitive 24) apps/web/src/features/resume/stylesheet/editor.tsx:122— editor.StylesheetCodeEditor has cognitive complexity 24 (threshold 15). Drivers by points: if/else 11, boolean chains 10, ternaries 2 (3 pts) (nesting depth added 1). Most of this is not in the body itself: 2 of the 24 points are its own statements and the rest belongs to 10 function items inside it that branch (a function literal at line 199, updateColor, a function literal at line 232, …). 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.
service.sourceText (cognitive 24) packages/api/src/features/career/service.ts:62— service.sourceText has cognitive complexity 24 (threshold 15). Drivers by points: if/else 11 (16 pts), ternaries 2 (5 pts), boolean chains 3 (nesting depth added 8). 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, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
linkedin.parseCsv (cognitive 24) packages/import/src/linkedin.ts:99— linkedin.parseCsv has cognitive complexity 24 (threshold 15). Drivers by points: if/else 11 (20 pts), boolean chains 3, loops 1 (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
use-register-fonts.resolvePdfFonts (cognitive 24) packages/pdf/src/hooks/use-register-fonts.ts:218— use-register-fonts.resolvePdfFonts has cognitive complexity 24 (threshold 15). Drivers by points: if/else 7 (9 pts), loops 4 (7 pts), ternaries 5 (6 pts), boolean chains 2 (nesting depth added 6). Most of this is not in the body itself: 10 of the 24 points are its own statements and the rest belongs to 2 function items inside it that branch (registerFallbacks, registerFont). 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.
profile.ProfileEditor (cognitive 23) apps/mobile/src/features/settings/profile.tsx:72— profile.ProfileEditor has cognitive complexity 23 (threshold 15). Drivers by points: if/else 9 (16 pts), ternaries 3 (4 pts), boolean chains 3 (nesting depth added 8). Most of this is not in the body itself: 2 of the 23 points are its own statements and the rest belongs to one function literal inside it that branches (line 80). 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.
offers.OffersPage (cognitive 23) apps/web/src/features/career/offers.tsx:56— offers.OffersPage has cognitive complexity 23 (threshold 15). Drivers by points: boolean chains 11, if/else 6, ternaries 5 (6 pts) (nesting depth added 1). Most of this is not in the body itself: 8 of the 23 points are its own statements and the rest belongs to 3 function literals inside it that branch (lines 66, 69, 149). 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.
offers.ComparisonTable (cognitive 23) apps/web/src/features/career/offers.tsx:185— offers.ComparisonTable has cognitive complexity 23 (threshold 15). Drivers by points: boolean chains 15, ternaries 7 (8 pts) (nesting depth added 1). 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 literals inside it that branch (lines 242, 207, 198, …). 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.
prepare.Prepare (cognitive 23) apps/web/src/features/homepage/prepare.tsx:502— prepare.Prepare has cognitive complexity 23 (threshold 15). Drivers by points: ternaries 12 (16 pts), boolean chains 6, if/else 1 (nesting depth added 4). Most of this is not in the body itself: 6 of the 23 points are its own statements and the rest belongs to 5 function literals inside it that branch (lines 625, 582, 538, …). 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.
editor.StylesheetEditorShell (cognitive 23) apps/web/src/features/resume/stylesheet/editor.tsx:378— editor.StylesheetEditorShell has cognitive complexity 23 (threshold 15). Drivers by points: boolean chains 10, if/else 8, ternaries 5. Most of this is not in the body itself: 7 of the 23 points are its own statements and the rest belongs to 8 function items inside it that branch (highlightRuleAt, a function literal at line 414, a function literal at line 416, …). 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.
section-renderers.renderCustomSection (cognitive 23) packages/docx/src/section-renderers.ts:311— section-renderers.renderCustomSection has cognitive complexity 23 (threshold 15). Drivers by points: if/else 8 (14 pts), loops 2 (4 pts), boolean chains 3, ternaries 1 (2 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.
html-to-odt.collectInline (cognitive 23) packages/odt/src/html-to-odt.ts:72— html-to-odt.collectInline has cognitive complexity 23 (threshold 15). Drivers by points: if/else 9 (21 pts), boolean chains 1, loops 1 (nesting depth added 12). 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, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
cascade.expandVariables (cognitive 23) packages/resume/src/stylesheet/cascade.ts:245— cascade.expandVariables has cognitive complexity 23 (threshold 15). Drivers by points: if/else 12 (19 pts), boolean chains 3, loops 1 (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
provider-list.ProviderRow (cognitive 22) apps/mobile/src/features/ai/provider-list.tsx:74— provider-list.ProviderRow has cognitive complexity 22 (threshold 15). Drivers by points: boolean chains 8, ternaries 5 (7 pts), if/else 5 (6 pts), error handling 1 (nesting depth added 3). Of this number, 14 points are the body's own statements and 8 belong to one function item inside it that branches. To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, 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.
download.DownloadTab::download (cognitive 22) apps/mobile/src/features/share/download.tsx:57— download.DownloadTab::download has cognitive complexity 22 (threshold 15). Drivers by points: if/else 8 (11 pts), ternaries 3 (6 pts), boolean chains 4, 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. This shape REPEATS in the file: one other method here (download.DownloadTab) 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.
download.DownloadTab (cognitive 22) apps/mobile/src/features/share/download.tsx:22— download.DownloadTab has cognitive complexity 22 (threshold 15). Drivers by points: boolean chains 24, if/else 8 (11 pts), ternaries 6 (10 pts), error handling 1 (nesting depth added 7). 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 (download.DownloadTab::download) 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.
messages.ProposalCard (cognitive 22) apps/mobile/src/features/workspace/tabs/messages.tsx:182— messages.ProposalCard has cognitive complexity 22 (threshold 15). Drivers by points: ternaries 16 (29 pts), if/else 4 (7 pts), boolean chains 6, match/switch 1 (nesting depth added 16). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body. This shape REPEATS in the file: one other method here (messages.ProposalCard::describe) 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.
rich-text-field.RichTextToolbar (cognitive 22) apps/mobile/src/features/write/rich-text-field.tsx:227— rich-text-field.RichTextToolbar has cognitive complexity 22 (threshold 15). Drivers by points: if/else 10 (12 pts), ternaries 4 (7 pts), boolean chains 3 (nesting depth added 5). Most of this is not in the body itself: 7 of the 22 points are its own statements and the rest belongs to 3 function items inside it that branch (setHeading, a function literal at line 356, setHeading::toggle). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
app-tabs.SidebarItem (cognitive 22) apps/mobile/src/shell/app-tabs.tsx:295— app-tabs.SidebarItem has cognitive complexity 22 (threshold 15). Drivers by points: ternaries 16 (21 pts), if/else 1 (nesting depth added 5). Of this number, 14 points are the body's own statements and 8 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.
activity.Activity (cognitive 22) apps/web/src/features/applications/components/detail/activity.tsx:51— activity.Activity has cognitive complexity 22 (threshold 15). Drivers by points: boolean chains 10, ternaries 6 (8 pts), if/else 4 (nesting depth added 2). Most of this is not in the body itself: 8 of the 22 points are its own statements and the rest belongs to 9 function items inside it that branch (a function literal at line 129, describe, submit, …). 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.
pdf-viewer.PdfViewer (cognitive 22) apps/web/src/features/resume/public/pdf-viewer.tsx:74— pdf-viewer.PdfViewer has cognitive complexity 22 (threshold 15). Drivers by points: if/else 14 (15 pts), ternaries 4 (5 pts), boolean chains 2 (nesting depth added 2). Most of this is not in the body itself: 5 of the 22 points are its own statements and the rest belongs to 10 function literals inside it that branch (lines 177, 92, 118, …). 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.
resume-reflow.EntryView (cognitive 22) apps/web/src/features/resume/public/resume-reflow.tsx:46— resume-reflow.EntryView has cognitive complexity 22 (threshold 15). Drivers by points: boolean chains 16, ternaries 6. 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, 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.
public-resume.PublicResumePage (cognitive 22) apps/web/src/features/resume/public/public-resume.tsx:46— public-resume.PublicResumePage has cognitive complexity 22 (threshold 15). Drivers by points: boolean chains 9, ternaries 7 (9 pts), error handling 1 (2 pts), if/else 2 (nesting depth added 3). Of this number, 18 points are the body's own statements and 4 belong to one function item inside it that branches. To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition.
service.describeTestConnectionFailure (cognitive 22) packages/api/src/features/ai/service.ts:209— service.describeTestConnectionFailure has cognitive complexity 22 (threshold 15). Drivers by points: if/else 10 (14 pts), boolean chains 4, ternaries 2 (4 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.
linkedin.parseLinkedInExport (cognitive 22) packages/import/src/linkedin.ts:166— linkedin.parseLinkedInExport has cognitive complexity 22 (threshold 15). Drivers by points: if/else 9 (11 pts), boolean chains 9, error handling 2 (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.
plain-text.groupEntries (cognitive 22) packages/import/src/plain-text.ts:262— plain-text.groupEntries has cognitive complexity 22 (threshold 15). Drivers by points: if/else 9 (17 pts), boolean chains 3, loops 1, ternaries 1 (nesting depth added 8). Of this number, 19 points are the body's own statements and 3 belong to one function item inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
overlays.DialogAction (cognitive 21) apps/mobile/src/ui/overlays.tsx:329— overlays.DialogAction has cognitive complexity 21 (threshold 15). Drivers by points: ternaries 11 (16 pts), if/else 3, boolean chains 2 (nesting depth added 5). Most of this is not in the body itself: 8 of the 21 points are its own statements and the rest belongs to 5 function items inside it that branch (a function literal at line 359, startHold, a function literal at line 339, …). 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.
sections.WhatYouSent (cognitive 21) apps/mobile/src/features/application-detail/sections.tsx:280— sections.WhatYouSent has cognitive complexity 21 (threshold 15). Drivers by points: ternaries 11 (18 pts), boolean chains 3 (nesting depth added 7). Of this number, 16 points are the body's own statements and 5 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.
offers.OffersScreen (cognitive 21) apps/mobile/src/features/career/offers.tsx:17— offers.OffersScreen has cognitive complexity 21 (threshold 15). Drivers by points: ternaries 9 (17 pts), boolean chains 4 (nesting depth added 8). Most of this is not in the body itself: 8 of the 21 points are its own statements and the rest belongs to 4 function literals inside it that branch (lines 66, 73, 77, …). 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.
profile.ProfileField (cognitive 21) apps/mobile/src/features/settings/profile.tsx:15— profile.ProfileField has cognitive complexity 21 (threshold 15). Drivers by points: ternaries 10 (15 pts), boolean chains 4, if/else 2 (nesting depth added 5). Of this number, 18 points are the body's own statements and 3 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.
rich-text-markup.hasRectangularTableGrid (cognitive 21) apps/web/src/components/input/rich-text-markup.ts:310— rich-text-markup.hasRectangularTableGrid has cognitive complexity 21 (threshold 15). Drivers by points: if/else 4 (11 pts), loops 4 (9 pts), boolean chains 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.
calendar-view.ApplicationCalendar (cognitive 21) apps/web/src/features/applications/components/calendar-view.tsx:38— calendar-view.ApplicationCalendar has cognitive complexity 21 (threshold 15). Drivers by points: boolean chains 12, ternaries 5, if/else 3 (4 pts) (nesting depth added 1). Most of this is not in the body itself: 8 of the 21 points are its own statements and the rest belongs to 6 function items inside it that branch (a function literal at line 138, dayHeading, a function literal at line 61, …). 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.
coach-thread.Composer (cognitive 21) apps/web/src/features/career/coach-thread.tsx:330— coach-thread.Composer has cognitive complexity 21 (threshold 15). Drivers by points: boolean chains 8, if/else 6, ternaries 6, error handling 1. Most of this is not in the body itself: 9 of the 21 points are its own statements and the rest belongs to 5 function items inside it that branch (a function literal at line 396, submit, upload, …). 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.
section-row.SectionMenu (cognitive 21) apps/web/src/features/resume/editor/write/section-row.tsx:179— section-row.SectionMenu has cognitive complexity 21 (threshold 15). Drivers by points: boolean chains 9, if/else 7, ternaries 4, loops 1. Of this number, 12 points are the body's own statements and 9 belong to 9 function items 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.
agent-tool-contracts.agentWebSources (cognitive 21) packages/ai/src/tools/agent-tool-contracts.ts:68— agent-tool-contracts.agentWebSources has cognitive complexity 21 (threshold 15). Drivers by points: if/else 7 (14 pts), loops 2 (5 pts), boolean chains 2 (nesting depth added 10). Of this number, 18 points are the body's own statements and 3 belong to one function item inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
contracts.wireJsonSchema (cognitive 21) packages/mcp/src/contracts.ts:79— contracts.wireJsonSchema has cognitive complexity 21 (threshold 15). Drivers by points: if/else 8, loops 3 (6 pts), ternaries 2 (4 pts), boolean chains 3 (nesting depth added 5). None of this is in the body itself: all 21 points belong to 2 function literals inside it that branch (lines 92, 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.
tools.registerTools (cognitive 21) packages/mcp/src/tools.ts:80— tools.registerTools has cognitive complexity 21 (threshold 15). Drivers by points: ternaries 13, if/else 5, boolean chains 2, loops 1. Most of this is not in the body itself: 1 of the 21 points is its own statement and the rest belongs to 10 function literals inside it that branch (lines 151, 173, 274, …). 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.
images.readImageHeader (cognitive 21) packages/pdf/src/forme/images.ts:54— images.readImageHeader has cognitive complexity 21 (threshold 15). Drivers by points: if/else 8 (15 pts), boolean chains 4, loops 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.
rich-text-keys.getRichTextSemanticKind (cognitive 21) packages/pdf/src/semantic/rich-text-keys.ts:19— rich-text-keys.getRichTextSemanticKind has cognitive complexity 21 (threshold 15). Drivers by points: if/else 15, boolean chains 4, ternaries 1 (2 pts) (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.
patch.applyResumePatches (cognitive 21) packages/resume/src/patch.ts:116— patch.applyResumePatches has cognitive complexity 21 (threshold 15). Drivers by points: if/else 6 (15 pts), error handling 2 (3 pts), ternaries 1 (2 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.
values.splitValue (cognitive 21) packages/resume/src/stylesheet/values.ts:175— values.splitValue has cognitive complexity 21 (threshold 15). Drivers by points: if/else 8 (17 pts), boolean chains 3, loops 1 (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
period.buildMonthLookup (cognitive 21) packages/schema/src/resume/period.ts:103— period.buildMonthLookup has cognitive complexity 21 (threshold 15). Drivers by points: loops 4 (7 pts), if/else 2 (6 pts), ternaries 1 (4 pts), error handling 1 (3 pts), boolean chains 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.
PdfPagesModule.definition (cognitive 21) apps/mobile/modules/pdf-pages/ios/PdfPagesModule.swift:10— PdfPagesModule.definition has cognitive complexity 21 (threshold 15). Drivers by points: boolean chains 9, if/else 8 (9 pts), loops 3 (nesting depth added 1). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
layout.Banner (cognitive 20) apps/mobile/src/ui/layout.tsx:364— layout.Banner has cognitive complexity 20 (threshold 15). Drivers by points: ternaries 18 (20 pts) (nesting depth added 2). 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: 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.
thumbnail.Thumbnail (cognitive 20) apps/mobile/src/features/documents/thumbnail.tsx:20— thumbnail.Thumbnail has cognitive complexity 20 (threshold 15). Drivers by points: ternaries 10 (13 pts), boolean chains 6, if/else 1 (nesting depth added 3). Of this number, 17 points are the body's own statements and 3 belong to 3 function literals inside it that branch. To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition.
practise.Practise (cognitive 20) apps/mobile/src/features/workspace/tabs/practise.tsx:60— practise.Practise has cognitive complexity 20 (threshold 15). Drivers by points: ternaries 9 (13 pts), boolean chains 4, if/else 3 (nesting depth added 4). Of this number, 19 points are the body's own statements and 1 belongs to one function literal inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
resume-pdf.handleResumePdfDownload (cognitive 20) apps/server/src/http/resume-pdf.ts:18— resume-pdf.handleResumePdfDownload has cognitive complexity 20 (threshold 15). Drivers by points: ternaries 4 (9 pts), if/else 5 (7 pts), boolean chains 3, error handling 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.
coach-chat.Proposal (cognitive 20) apps/web/src/features/career/coach-chat.tsx:609— coach-chat.Proposal has cognitive complexity 20 (threshold 15). Drivers by points: ternaries 8 (11 pts), boolean chains 3, if/else 3, error handling 2, loops 1 (nesting depth added 3). Of this number, 12 points are the body's own statements and 8 belong to 5 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.
stories.StoryEditor (cognitive 20) apps/web/src/features/career/knowledge/stories.tsx:404— stories.StoryEditor has cognitive complexity 20 (threshold 15). Drivers by points: ternaries 10 (11 pts), boolean chains 7, if/else 2 (nesting depth added 1). Most of this is not in the body itself: 8 of the 20 points are its own statements and the rest belongs to 6 function items inside it that branch (a function literal at line 540, a function literal at line 512, submit, …). 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.
offers.requirementsFor (cognitive 20) apps/web/src/features/career/offers.tsx:485— offers.requirementsFor has cognitive complexity 20 (threshold 15). Drivers by points: ternaries 6 (15 pts), if/else 3, boolean chains 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.
document-card.DocumentCard (cognitive 20) apps/web/src/features/documents/document-card.tsx:136— document-card.DocumentCard has cognitive complexity 20 (threshold 15). Drivers by points: boolean chains 15, ternaries 5. 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.
draft.flushResumeSave (cognitive 20) apps/web/src/features/resume/builder/draft.ts:262— draft.flushResumeSave has cognitive complexity 20 (threshold 15). Drivers by points: if/else 8 (10 pts), boolean chains 7, ternaries 1 (2 pts), error handling 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.
read-file.detectImportKind (cognitive 20) apps/web/src/features/resume/import/read-file.ts:58— read-file.detectImportKind has cognitive complexity 20 (threshold 15). Drivers by points: if/else 7 (9 pts), boolean chains 7, error handling 2 (4 pts) (nesting depth added 4). 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: 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.
color-tokens.collectCompiledColorTokens (cognitive 20) apps/web/src/features/resume/stylesheet/color-tokens.ts:31— color-tokens.collectCompiledColorTokens has cognitive complexity 20 (threshold 15). Drivers by points: if/else 4 (12 pts), loops 3 (6 pts), boolean chains 2 (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.
providers.ProviderFieldsForm (cognitive 20) apps/web/src/features/settings/ai/providers.tsx:309— providers.ProviderFieldsForm has cognitive complexity 20 (threshold 15). Drivers by points: ternaries 8 (15 pts), boolean chains 5 (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.
providers.EditProviderForm (cognitive 20) apps/web/src/features/settings/ai/providers.tsx:576— providers.EditProviderForm has cognitive complexity 20 (threshold 15). Drivers by points: boolean chains 10, if/else 5, ternaries 4, error handling 1. Of this number, 13 points are the body's own statements and 7 belong to 3 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.
LocalStorageService.list (cognitive 20) packages/api/src/features/storage/service.ts:161— LocalStorageService.list has cognitive complexity 20 (threshold 15). Drivers by points: if/else 4 (12 pts), error handling 2 (5 pts), boolean chains 2, ternaries 1 (nesting depth added 11). Of this number, 19 points are the body's own statements and 1 belongs to one function literal inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
html-to-docx.collectInlineChildren (cognitive 20) packages/docx/src/html-to-docx.ts:109— html-to-docx.collectInlineChildren has cognitive complexity 20 (threshold 15). Drivers by points: if/else 7 (15 pts), ternaries 1 (3 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.
to-forme.fitImage (cognitive 20) packages/pdf/src/forme/to-forme.tsx:726— to-forme.fitImage has cognitive complexity 20 (threshold 15). Drivers by points: ternaries 8 (13 pts), boolean chains 4, if/else 3 (nesting depth added 5). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
render.renderResumeElement (cognitive 20) packages/pdf/src/forme/render.ts:216— render.renderResumeElement has cognitive complexity 20 (threshold 15). Drivers by points: if/else 9 (11 pts), loops 3 (4 pts), ternaries 2 (3 pts), boolean chains 2 (nesting depth added 4). Most of this is not in the body itself: 7 of the 20 points are its own statements and the rest belongs to 4 function items inside it that branch (layOut, layOutOnce::render, a function literal at line 264, …). 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.
markdown.renderCustomSection (cognitive 20) packages/resume/src/markdown.ts:274— markdown.renderCustomSection has cognitive complexity 20 (threshold 15). Drivers by points: if/else 7 (13 pts), loops 2 (4 pts), boolean chains 3 (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
css-escape.escapeCssIdentifier (cognitive 20) packages/resume/src/stylesheet/css-escape.ts:1— css-escape.escapeCssIdentifier has cognitive complexity 20 (threshold 15). Drivers by points: boolean chains 10, if/else 6 (9 pts), loops 1 (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.
period.parseEndpoint (cognitive 20) packages/schema/src/resume/period.ts:155— period.parseEndpoint has cognitive complexity 20 (threshold 15). Drivers by points: if/else 8 (9 pts), ternaries 3 (7 pts), boolean chains 4 (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.
url-security.node.fetchPublic (cognitive 20) packages/utils/src/url-security.node.ts:154— url-security.node.fetchPublic has cognitive complexity 20 (threshold 15). Drivers by points: if/else 6, ternaries 5 (6 pts), boolean chains 4, loops 2 (3 pts), error handling 1 (nesting depth added 2). Most of this is not in the body itself: 8 of the 20 points are its own statements and the rest belongs to 2 function literals inside it that branch (lines 174, 210). 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.
resources.readPreviewImage (cognitive 19) apps/mobile/src/preview/resources.ts:86— resources.readPreviewImage has cognitive complexity 19 (threshold 15). Drivers by points: if/else 9 (14 pts), loops 2, ternaries 1 (2 pts), boolean chains 1 (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
chat.webSources (cognitive 19) apps/mobile/src/features/assistant/chat.ts:54— chat.webSources has cognitive complexity 19 (threshold 15). Drivers by points: if/else 5 (9 pts), boolean chains 5, loops 2 (4 pts), ternaries 1 (nesting depth added 6). Of this number, 14 points are the body's own statements and 5 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.
import-applications-sheet.ImportApplicationsSheet (cognitive 19) apps/web/src/features/applications/components/import-applications-sheet.tsx:58— import-applications-sheet.ImportApplicationsSheet has cognitive complexity 19 (threshold 15). Drivers by points: boolean chains 10, ternaries 5, if/else 4. Of this number, 11 points are the body's own statements and 8 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.
checker.AtsChecker (cognitive 19) apps/web/src/features/ats-checker/checker.tsx:61— checker.AtsChecker has cognitive complexity 19 (threshold 15). Drivers by points: ternaries 4 (8 pts), if/else 6 (7 pts), boolean chains 2, error handling 2 (nesting depth added 5). Most of this is not in the body itself: 6 of the 19 points are its own statements and the rest belongs to 5 function items inside it that branch (check, importAndOpen, a function literal at line 113, …). 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.
preferences.PreferencesForm (cognitive 19) apps/web/src/features/career/knowledge/preferences.tsx:55— preferences.PreferencesForm has cognitive complexity 19 (threshold 15). Drivers by points: ternaries 9 (13 pts), boolean chains 6 (nesting depth added 4). Of this number, 15 points are the body's own statements and 4 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.
debrief.DebriefForm (cognitive 19) apps/web/src/features/career/workspace/debrief.tsx:101— debrief.DebriefForm has cognitive complexity 19 (threshold 15). Drivers by points: boolean chains 6, if/else 5 (6 pts), error handling 3 (4 pts), ternaries 3 (nesting depth added 2). Most of this is not in the body itself: 7 of the 19 points are its own statements and the rest belongs to 5 function items inside it that branch (a function literal at line 109, change, a function literal at line 142, …). 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.
fit.FitTab (cognitive 19) apps/web/src/features/career/workspace/fit.tsx:55— fit.FitTab has cognitive complexity 19 (threshold 15). Drivers by points: boolean chains 12, ternaries 5, if/else 2. Of this number, 14 points are the body's own statements and 5 belong to 5 function items inside it that branch. To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
parser-view.ParsedText (cognitive 19) apps/web/src/features/resume/editor/check/parser-view.tsx:97— parser-view.ParsedText has cognitive complexity 19 (threshold 15). Drivers by points: ternaries 6 (8 pts), boolean chains 7, if/else 4 (nesting depth added 2). Most of this is not in the body itself: 6 of the 19 points are its own statements and the rest belongs to 4 function literals inside it that branch (lines 152, 135, 168, …). 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.
draft.draftLetterBody (cognitive 19) packages/api/src/features/cover-letters/draft.ts:47— draft.draftLetterBody has cognitive complexity 19 (threshold 15). Drivers by points: ternaries 7 (8 pts), if/else 5 (7 pts), boolean chains 2, error handling 1, loops 1 (nesting depth added 3). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition.
builder.buildHeader (cognitive 19) packages/docx/src/builder.ts:135— builder.buildHeader has cognitive complexity 19 (threshold 15). Drivers by points: if/else 9 (10 pts), boolean chains 6, ternaries 1 (2 pts), loops 1 (nesting depth added 2). Of this number, 18 points are the body's own statements and 1 belongs to one function item inside it that branches. To reduce it, split the body: 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.
picture-shadow.convolve (cognitive 19) packages/pdf/src/templates/shared/picture-shadow.ts:23— picture-shadow.convolve has cognitive complexity 19 (threshold 15). Drivers by points: ternaries 2 (8 pts), loops 3 (6 pts), if/else 1 (4 pts), boolean chains 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.
images.node.readServerImage (cognitive 19) packages/pdf/src/forme/images.node.ts:13— images.node.readServerImage has cognitive complexity 19 (threshold 15). Drivers by points: if/else 8 (9 pts), boolean chains 6, error handling 1 (2 pts), ternaries 2 (nesting depth added 2). Most of this is not in the body itself: 8 of the 19 points are its own statements and the rest belongs to 3 function literals inside it that branch (lines 38, 36, 56). 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.
overlays.ConfirmDialog (cognitive 18) apps/mobile/src/ui/overlays.tsx:409— overlays.ConfirmDialog has cognitive complexity 18 (threshold 15). Drivers by points: ternaries 11 (15 pts), boolean chains 2, if/else 1 (nesting depth added 4). 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, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
write.DraftBox (cognitive 18) apps/mobile/src/features/letters/write.tsx:579— write.DraftBox has cognitive complexity 18 (threshold 15). Drivers by points: ternaries 8 (11 pts), boolean chains 4, if/else 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.
date-field.DatesField (cognitive 18) apps/mobile/src/features/write/date-field.tsx:150— date-field.DatesField has cognitive complexity 18 (threshold 15). Drivers by points: ternaries 10 (17 pts), boolean chains 1 (nesting depth added 7). Of this number, 15 points are the body's own statements and 3 belong to 2 function literals inside it that branch. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
outline.SectionRow (cognitive 18) apps/mobile/src/features/write/outline.tsx:313— outline.SectionRow has cognitive complexity 18 (threshold 15). Drivers by points: ternaries 11, boolean chains 4, if/else 3. Of this number, 15 points are the body's own statements and 3 belong to 2 function literals inside it that branch. To reduce it, split the body: 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.
handler.handleMcp (cognitive 18) apps/server/src/mcp/handler.ts:24— handler.handleMcp has cognitive complexity 18 (threshold 15). Drivers by points: if/else 6 (8 pts), ternaries 2 (5 pts), boolean chains 2, error handling 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.
application-detail-sheet.Detail (cognitive 18) apps/web/src/features/applications/components/application-detail-sheet.tsx:94— application-detail-sheet.Detail has cognitive complexity 18 (threshold 15). Drivers by points: boolean chains 9, ternaries 5, if/else 4. Of this number, 9 points are the body's own statements and 9 belong to 4 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.
section-row.SectionRow (cognitive 18) apps/web/src/features/resume/editor/write/section-row.tsx:61— section-row.SectionRow has cognitive complexity 18 (threshold 15). Drivers by points: boolean chains 12, ternaries 4, if/else 2. Of this number, 13 points are the body's own statements and 5 belong to 2 function items inside it that branch. To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
page-canvas.ResumePageCaption (cognitive 18) apps/web/src/routes/builder/$resumeId/-components/page-canvas.tsx:159— page-canvas.ResumePageCaption has cognitive complexity 18 (threshold 15). Drivers by points: ternaries 4 (14 pts), boolean chains 2, if/else 2 (nesting depth added 10). To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
service.readPage (cognitive 18) packages/api/src/features/web-access/service.ts:157— service.readPage has cognitive complexity 18 (threshold 15). Drivers by points: ternaries 5 (9 pts), if/else 3 (6 pts), error handling 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.
level.parseLevel (cognitive 18) packages/import/src/level.ts:6— level.parseLevel has cognitive complexity 18 (threshold 15). Drivers by points: if/else 13, boolean chains 5. 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.
sections.renderSection (cognitive 18) packages/odt/src/sections.ts:120— sections.renderSection has cognitive complexity 18 (threshold 15). Drivers by points: if/else 6 (8 pts), ternaries 3 (6 pts), boolean chains 4 (nesting depth added 5). Of this number, 13 points are the body's own statements and 5 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.
style.flattenAlpha (cognitive 18) packages/pdf/src/forme/style.ts:211— style.flattenAlpha has cognitive complexity 18 (threshold 15). Drivers by points: if/else 8 (12 pts), ternaries 3, boolean chains 2, loops 1 (nesting depth added 4). Of this number, 13 points are the body's own statements and 5 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.
text.renderChildren (cognitive 18) packages/pdf/src/text.tsx:152— text.renderChildren has cognitive complexity 18 (threshold 15). Drivers by points: boolean chains 9, if/else 5 (7 pts), ternaries 2 (nesting depth added 2). Most of this is not in the body itself: 3 of the 18 points are its own statements and the rest belongs to 2 function literals inside it that branch (lines 158, 175). 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.
picture-shadow.getPictureShadow (cognitive 18) packages/pdf/src/templates/shared/picture-shadow.ts:43— picture-shadow.getPictureShadow has cognitive complexity 18 (threshold 15). Drivers by points: if/else 8, boolean chains 5, loops 4 (5 pts) (nesting depth added 1). Of this number, 15 points are the body's own statements and 3 belong to one function item inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
style-rules.toStyle (cognitive 18) packages/pdf/src/templates/shared/style-rules.ts:46— style-rules.toStyle has cognitive complexity 18 (threshold 15). Drivers by points: if/else 14 (16 pts), loops 2 (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.CustomServer (cognitive 17) apps/mobile/app/(auth)/server.tsx:26— server.CustomServer has cognitive complexity 17 (threshold 15). Drivers by points: ternaries 7 (9 pts), if/else 5 (6 pts), boolean chains 1, error handling 1 (nesting depth added 3). Most of this is not in the body itself: 7 of the 17 points are its own statements and the rest belongs to 3 function items inside it that branch (run, a function literal at line 65, a function literal at line 123). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
store.createDraftStore.resolveConflict (cognitive 17) apps/mobile/src/draft/store.ts:364— store.createDraftStore.resolveConflict has cognitive complexity 17 (threshold 15). Drivers by points: if/else 9 (13 pts), boolean chains 3, 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.
store.createDraftStore.replayQueue (cognitive 17) apps/mobile/src/draft/store.ts:444— store.createDraftStore.replayQueue has cognitive complexity 17 (threshold 15). Drivers by points: if/else 6 (10 pts), boolean chains 4, error handling 1 (2 pts), loops 1 (nesting depth added 5). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
fields.SelectSheet (cognitive 17) apps/mobile/src/ui/fields.tsx:203— fields.SelectSheet has cognitive complexity 17 (threshold 15). Drivers by points: ternaries 10 (15 pts), boolean chains 2 (nesting depth added 5). Of this number, 12 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.
device.checkParity (cognitive 17) apps/mobile/scripts/parity/device.ts:90— device.checkParity has cognitive complexity 17 (threshold 15). Drivers by points: if/else 3 (6 pts), boolean chains 3, error handling 1 (3 pts), loops 2 (3 pts), ternaries 1 (2 pts) (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
development.DevelopmentTools (cognitive 17) apps/mobile/scripts/parity/development.tsx:48— development.DevelopmentTools has cognitive complexity 17 (threshold 15). Drivers by points: ternaries 8 (10 pts), if/else 5, boolean chains 2 (nesting depth added 2). Most of this is not in the body itself: 8 of the 17 points are its own statements and the rest belongs to 3 function items inside it that branch (editDraft, a function literal at line 77, a function literal at line 74). 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.
provider-editor.ProviderForm::save (cognitive 17) apps/mobile/src/features/ai/provider-editor.tsx:135— provider-editor.ProviderForm::save has cognitive complexity 17 (threshold 15). Drivers by points: if/else 9 (10 pts), boolean chains 6, error handling 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. This shape REPEATS in the file: one other method here (provider-editor.ProviderForm) 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.
document.useLetterAssistantDocument (cognitive 17) apps/mobile/src/features/assistant/document.ts:75— document.useLetterAssistantDocument has cognitive complexity 17 (threshold 15). Drivers by points: boolean chains 7, if/else 7, ternaries 2, loops 1. None of this is in the body itself: all 17 points belong to 8 function literals inside it that branch (lines 93, 109, 136, …). 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.
messages.QuestionCard (cognitive 17) apps/mobile/src/features/assistant/messages.tsx:336— messages.QuestionCard has cognitive complexity 17 (threshold 15). Drivers by points: ternaries 7 (13 pts), boolean chains 3, if/else 1 (nesting depth added 6). Of this number, 16 points are the body's own statements and 1 belongs to one function literal inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
chat-view.Composer::attach (cognitive 17) apps/mobile/src/features/assistant/chat-view.tsx:665— chat-view.Composer::attach has cognitive complexity 17 (threshold 15). Drivers by points: if/else 9 (10 pts), loops 3 (4 pts), error handling 2 (3 pts) (nesting depth added 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. This shape REPEATS in the file: one other method here (chat-view.Composer) 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.
chat-view.Composer (cognitive 17) apps/mobile/src/features/assistant/chat-view.tsx:645— chat-view.Composer has cognitive complexity 17 (threshold 15). Drivers by points: ternaries 11 (14 pts), if/else 11 (12 pts), boolean chains 6, loops 3 (4 pts), error handling 2 (3 pts) (nesting depth added 6). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level. This shape REPEATS in the file: one other method here (chat-view.Composer::attach) 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.
schedule-sheet.ScheduleForm::save (cognitive 17) apps/mobile/src/features/career/schedule-sheet.tsx:137— schedule-sheet.ScheduleForm::save has cognitive complexity 17 (threshold 15). Drivers by points: ternaries 8 (9 pts), if/else 5, boolean chains 3 (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. This shape REPEATS in the file: one other method here (schedule-sheet.ScheduleForm) 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.
design-pane.DesignPane::body (cognitive 17) apps/mobile/src/features/design/design-pane.tsx:91— design-pane.DesignPane::body has cognitive complexity 17 (threshold 15). Drivers by points: if/else 9 (13 pts), ternaries 2 (4 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. This shape REPEATS in the file: one other method here (design-pane.DesignPane) 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.
state.createAutosave.send (cognitive 17) apps/mobile/src/features/workspace/state.ts:112— state.createAutosave.send has cognitive complexity 17 (threshold 15). Drivers by points: boolean chains 8, if/else 7 (8 pts), ternaries 1 (nesting depth added 1). Most of this is not in the body itself: 6 of the 17 points are its own statements and the rest belongs to one function literal inside it that branches (line 118). 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.
apply.Apply (cognitive 17) apps/mobile/src/features/workspace/tabs/apply.tsx:46— apply.Apply has cognitive complexity 17 (threshold 15). Drivers by points: ternaries 10 (12 pts), boolean chains 3, if/else 2 (nesting depth added 2). Of this number, 13 points are the body's own statements and 4 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.
fit.Fit (cognitive 17) apps/mobile/src/features/workspace/tabs/fit.tsx:26— fit.Fit has cognitive complexity 17 (threshold 15). Drivers by points: ternaries 10 (12 pts), boolean chains 3, if/else 2 (nesting depth added 2). Of this number, 12 points are the body's own statements and 5 belong to 4 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.
generator.addCurlSamples::example (cognitive 17) apps/server/src/openapi/generator.ts:236— generator.addCurlSamples::example has cognitive complexity 17 (threshold 15). Drivers by points: if/else 9, boolean chains 4, ternaries 3 (4 pts) (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. This shape REPEATS in the file: one other method here (generator.addCurlSamples) 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.
uploads.handleUpload (cognitive 17) apps/server/src/static/uploads.ts:12— uploads.handleUpload has cognitive complexity 17 (threshold 15). Drivers by points: if/else 9 (10 pts), boolean chains 5, ternaries 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.
display.LevelDisplay (cognitive 17) apps/web/src/components/level/display.tsx:17— display.LevelDisplay has cognitive complexity 17 (threshold 15). Drivers by points: boolean chains 11, if/else 4, ternaries 2. Most of this is not in the body itself: 6 of the 17 points are its own statements and the rest belongs to one function literal inside it that branches (line 45). 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.
enable-two-factor.EnableTwoFactorDialog (cognitive 17) apps/web/src/dialogs/auth/enable-two-factor.tsx:54— enable-two-factor.EnableTwoFactorDialog has cognitive complexity 17 (threshold 15). Drivers by points: if/else 10, boolean chains 6, ternaries 1. None of this is in the body itself: all 17 points belong to 10 function items inside it that branch (a function literal at line 138, a function literal at line 67, handleCopySecret, …). 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.
add-application-dialog.AddApplicationForm::add (cognitive 17) apps/web/src/features/applications/components/add-application-dialog.tsx:142— add-application-dialog.AddApplicationForm::add has cognitive complexity 17 (threshold 15). Drivers by points: ternaries 8 (9 pts), boolean chains 4, if/else 3, error handling 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. This shape REPEATS in the file: one other method here (add-application-dialog.AddApplicationForm) 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.
schedule-sheet.ScheduleSheet::onSave (cognitive 17) apps/web/src/features/career/schedule-sheet.tsx:206— schedule-sheet.ScheduleSheet::onSave has cognitive complexity 17 (threshold 15). Drivers by points: ternaries 8 (9 pts), boolean chains 6, if/else 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. This shape REPEATS in the file: one other method here (schedule-sheet.ScheduleSheet) 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.
practise.PractiseTab (cognitive 17) apps/web/src/features/career/workspace/practise.tsx:69— practise.PractiseTab has cognitive complexity 17 (threshold 15). Drivers by points: ternaries 7 (10 pts), boolean chains 4, if/else 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.
store.useLetterEditorStore (cognitive 17) apps/web/src/features/letters/store.ts:78— store.useLetterEditorStore has cognitive complexity 17 (threshold 15). Drivers by points: if/else 7, boolean chains 6, ternaries 3 (4 pts) (nesting depth added 1). None of this is in the body itself: all 17 points belong to 8 function literals inside it that branch (lines 106, 93, 154, …). 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.
improve.ImprovePanel (cognitive 17) apps/web/src/features/resume/editor/write/improve.tsx:38— improve.ImprovePanel has cognitive complexity 17 (threshold 15). Drivers by points: ternaries 4 (7 pts), if/else 3 (6 pts), boolean chains 4 (nesting depth added 6). Of this number, 10 points are the body's own statements and 7 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.
api-keys.ApiKeysSection (cognitive 17) apps/web/src/features/settings/ai/api-keys.tsx:43— api-keys.ApiKeysSection has cognitive complexity 17 (threshold 15). Drivers by points: ternaries 5 (10 pts), boolean chains 5, if/else 2 (nesting depth added 5). Most of this is not in the body itself: 3 of the 17 points are its own statements and the rest belongs to 4 function items inside it that branch (a function literal at line 131, revoke, a function literal at line 52, …). 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.
providers.ProvidersSection (cognitive 17) apps/web/src/features/settings/ai/providers.tsx:52— providers.ProvidersSection has cognitive complexity 17 (threshold 15). Drivers by points: ternaries 5 (13 pts), boolean chains 4 (nesting depth added 8). Of this number, 10 points are the body's own statements and 7 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.
service.linkLetterApplication (cognitive 17) packages/api/src/features/cover-letters/service.ts:117— service.linkLetterApplication has cognitive complexity 17 (threshold 15). Drivers by points: if/else 5 (7 pts), ternaries 2 (5 pts), boolean chains 4, 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.
service.recordSentResume (cognitive 17) packages/api/src/features/applications/service.ts:137— service.recordSentResume has cognitive complexity 17 (threshold 15). Drivers by points: if/else 8 (13 pts), boolean chains 4 (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.
parity.decodeInput (cognitive 17) packages/mcp/src/parity.ts:295— parity.decodeInput has cognitive complexity 17 (threshold 15). Drivers by points: if/else 7 (9 pts), boolean chains 4, loops 1 (2 pts), ternaries 1 (2 pts) (nesting depth added 4). Of this number, 15 points are the body's own statements and 2 belong to one function literal inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
rich-text-html.projectNormalizedRichTextHtml (cognitive 17) REDACTED:263— rich-text-html.projectNormalizedRichTextHtml has cognitive complexity 17 (threshold 15). Drivers by points: if/else 6 (8 pts), ternaries 4 (5 pts), boolean chains 2, loops 2 (nesting depth added 3). Most of this is not in the body itself: 3 of the 17 points are its own statements and the rest belongs to 4 function items inside it that branch (visit, a function literal at line 305, a function literal at line 290, …). 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.
tree.buildSemanticTree (cognitive 17) packages/pdf/src/semantic/tree.ts:915— tree.buildSemanticTree has cognitive complexity 17 (threshold 15). Drivers by points: if/else 5 (7 pts), boolean chains 5, ternaries 4 (5 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 one function literal inside it that branches (line 935). 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.
contact.findLinkMismatches (cognitive 17) packages/resume/src/ats-pdf/analyze/contact.ts:75— contact.findLinkMismatches has cognitive complexity 17 (threshold 15). Drivers by points: if/else 5 (10 pts), boolean chains 4, ternaries 1 (2 pts), loops 1 (nesting depth added 6). Of this number, 16 points are the body's own statements and 1 belongs to one function literal inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
harvest.toLinkAnnotations (cognitive 17) packages/resume/src/ats-pdf/harvest.ts:121— harvest.toLinkAnnotations has cognitive complexity 17 (threshold 15). Drivers by points: ternaries 5 (10 pts), if/else 3 (5 pts), boolean chains 1, loops 1 (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
rules.urlRules (cognitive 17) packages/resume/src/ats/rules.ts:82— rules.urlRules has cognitive complexity 17 (threshold 15). Drivers by points: if/else 4 (7 pts), boolean chains 4, loops 2 (3 pts), ternaries 1 (3 pts) (nesting depth added 6). Of this number, 15 points are the body's own statements and 2 belong to one function literal inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
rules.structureRules (cognitive 17) packages/resume/src/ats/rules.ts:181— rules.structureRules has cognitive complexity 17 (threshold 15). Drivers by points: if/else 4 (8 pts), boolean chains 5, loops 3 (4 pts) (nesting depth added 5). Of this number, 16 points are the body's own statements and 1 belongs to one function literal inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
fields.Chip (cognitive 16) apps/mobile/src/ui/fields.tsx:429— fields.Chip has cognitive complexity 16 (threshold 15). Drivers by points: ternaries 12 (14 pts), boolean chains 2 (nesting depth added 2). Of this number, 10 points are the body's own statements and 6 belong to one function literal inside it that branches. To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition.
fit.tightenResume (cognitive 16) apps/mobile/src/preview/fit.ts:7— fit.tightenResume has cognitive complexity 16 (threshold 15). Drivers by points: if/else 8 (10 pts), boolean chains 4, ternaries 1 (2 pts) (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.
error.aiSettingsError (cognitive 16) apps/mobile/src/features/ai/error.ts:4— error.aiSettingsError has cognitive complexity 16 (threshold 15). Drivers by points: if/else 7 (13 pts), boolean chains 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.
sections.InlineFact (cognitive 16) apps/mobile/src/features/application-detail/sections.tsx:378— sections.InlineFact has cognitive complexity 16 (threshold 15). Drivers by points: ternaries 4 (7 pts), boolean chains 4, if/else 4, error handling 1 (nesting depth added 3). Most of this is not in the body itself: 5 of the 16 points are its own statements and the rest belongs to one function item inside it that branches (commit). 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.
error.applicationError (cognitive 16) apps/mobile/src/features/applications/error.ts:4— error.applicationError has cognitive complexity 16 (threshold 15). Drivers by points: if/else 8 (15 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.
write.EmptyBody (cognitive 16) apps/mobile/src/features/letters/write.tsx:514— write.EmptyBody has cognitive complexity 16 (threshold 15). Drivers by points: ternaries 7 (11 pts), boolean chains 5 (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.
use-review-prompt.useReviewPrompt (cognitive 16) apps/mobile/src/features/reviews/use-review-prompt.ts:14— use-review-prompt.useReviewPrompt has cognitive complexity 16 (threshold 15). Drivers by points: if/else 7, boolean chains 5, error handling 2, ternaries 2. Most of this is not in the body itself: 1 of the 16 points is its own statement and the rest belongs to 4 function literals inside it that branch (lines 34, 53, 21, …). 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.
shell.TabBadges (cognitive 16) apps/mobile/src/features/workspace/shell.tsx:258— shell.TabBadges has cognitive complexity 16 (threshold 15). Drivers by points: ternaries 6 (8 pts), boolean chains 5, if/else 3 (nesting depth added 2). Most of this is not in the body itself: 3 of the 16 points are its own statements and the rest belongs to 2 function items inside it that branch (badge, a function literal at line 284). 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.
debrief.DebriefForm (cognitive 16) apps/mobile/src/features/workspace/tabs/debrief.tsx:94— debrief.DebriefForm has cognitive complexity 16 (threshold 15). Drivers by points: ternaries 7 (9 pts), boolean chains 4, if/else 3 (nesting depth added 2). Of this number, 10 points are the body's own statements and 6 belong to 5 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.
rich-text-field.RichTextField (cognitive 16) apps/mobile/src/features/write/rich-text-field.tsx:69— rich-text-field.RichTextField has cognitive complexity 16 (threshold 15). Drivers by points: if/else 7 (8 pts), ternaries 5, boolean chains 3 (nesting depth added 1). Most of this is not in the body itself: 7 of the 16 points are its own statements and the rest belongs to 6 function items inside it that branch (publish, a function literal at line 86, a function literal at line 95, …). 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.
workspace-chrome.Frame (cognitive 16) apps/mobile/src/shell/workspace-chrome.tsx:56— workspace-chrome.Frame has cognitive complexity 16 (threshold 15). Drivers by points: ternaries 8, boolean chains 5, if/else 3. Most of this is not in the body itself: 6 of the 16 points are its own statements and the rest belongs to 6 function items inside it that branch (revealActive, a function literal at line 153, a function literal at line 141, …). 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.
Coordination.fetch (cognitive 16) apps/server/src/cloudflare/coordination.ts:22— Coordination.fetch has cognitive complexity 16 (threshold 15). Drivers by points: if/else 6, boolean chains 3, error handling 1 (3 pts), loops 1 (2 pts), ternaries 2 (nesting depth added 3). Of this number, 9 points are the body's own statements and 7 belong to one function literal inside it that branches. To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
get-next-weights.getNextWeights (cognitive 16) apps/web/src/components/typography/get-next-weights.ts:5— get-next-weights.getNextWeights has cognitive complexity 16 (threshold 15). Drivers by points: if/else 6 (7 pts), ternaries 3 (5 pts), boolean chains 3, 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.
register.RegisterPage (cognitive 16) apps/web/src/features/auth/pages/register.tsx:49— register.RegisterPage has cognitive complexity 16 (threshold 15). Drivers by points: if/else 6 (8 pts), boolean chains 7, ternaries 1 (nesting depth added 2). Most of this is not in the body itself: 6 of the 16 points are its own statements and the rest belongs to one function literal inside it that branches (line 57). 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.
verify-2fa.TwoFactorVerificationPage (cognitive 16) apps/web/src/features/auth/pages/verify-2fa.tsx:36— verify-2fa.TwoFactorVerificationPage has cognitive complexity 16 (threshold 15). Drivers by points: ternaries 11, boolean chains 3, if/else 2. Most of this is not in the body itself: 7 of the 16 points are its own statements and the rest belongs to 2 function literals inside it that branch (lines 45, 110). 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.
facts.FactRow (cognitive 16) apps/web/src/features/career/knowledge/facts.tsx:339— facts.FactRow has cognitive complexity 16 (threshold 15). Drivers by points: ternaries 10 (11 pts), boolean chains 3, if/else 1 (2 pts) (nesting depth added 2). Of this number, 13 points are the body's own statements and 3 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.
dates-field.DatesField (cognitive 16) apps/web/src/features/resume/editor/write/dates-field.tsx:96— dates-field.DatesField has cognitive complexity 16 (threshold 15). Drivers by points: ternaries 7 (12 pts), boolean chains 4 (nesting depth added 5). Of this number, 15 points are the body's own statements and 1 belongs 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.
service.searchWeb (cognitive 16) packages/api/src/features/web-access/service.ts:118— service.searchWeb has cognitive complexity 16 (threshold 15). Drivers by points: ternaries 4 (8 pts), if/else 5 (7 pts), error handling 1 (nesting depth added 6). Of this number, 13 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.
posting.jobPostingsIn (cognitive 16) packages/api/src/features/applications/posting.ts:120— posting.jobPostingsIn has cognitive complexity 16 (threshold 15). Drivers by points: if/else 2 (5 pts), ternaries 2 (4 pts), loops 2 (3 pts), boolean chains 2, error handling 1 (2 pts) (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
jobs.sendPendingEmail (cognitive 16) packages/api/src/features/career/jobs.ts:491— jobs.sendPendingEmail has cognitive complexity 16 (threshold 15). Drivers by points: if/else 4 (9 pts), boolean chains 3, error handling 1 (3 pts), loops 1 (nesting depth added 7). Of this number, 14 points are the body's own statements and 2 belong to one function literal inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
plain-text.segment (cognitive 16) packages/import/src/plain-text.ts:467— plain-text.segment has cognitive complexity 16 (threshold 15). Drivers by points: if/else 5 (9 pts), boolean chains 6, loops 1 (nesting depth added 4). Of this number, 15 points are the body's own statements and 1 belongs to one function literal inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
render.unplacedBlocks (cognitive 16) packages/pdf/src/forme/render.ts:99— render.unplacedBlocks has cognitive complexity 16 (threshold 15). Drivers by points: if/else 5 (7 pts), boolean chains 5, loops 3 (4 pts) (nesting depth added 3). 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 item inside it that branches (visit). 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.
tokenize.tokenize (cognitive 16) packages/resume/src/ats-pdf/jd/tokenize.ts:38— tokenize.tokenize has cognitive complexity 16 (threshold 15). Drivers by points: if/else 6 (12 pts), boolean chains 2, loops 1, ternaries 1 (nesting depth added 6). Of this number, 13 points are the body's own statements and 3 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.
Cross-context type PdfCategory (resume → mobile) apps/mobile/src/features/ats-checker/messages.ts:420— PdfCategory (context resume) is exposed in mobile's public surface via messages.getPdfCategoryLabel — couples the contexts.
Cross-context type MoveTarget (resume → mobile) apps/mobile/src/features/write/model.ts:508— MoveTarget (context resume) is exposed in mobile's public surface via model.moveItem — couples the contexts.
Cross-context type CalendarEvent (mobile → web) apps/web/src/features/applications/ics.ts:33— CalendarEvent (context mobile) is exposed in web's public surface via ics.buildIcs — couples the contexts.
Cross-context type Breakpoint (ui → web) apps/web/src/features/assistant/dock.tsx:19— Breakpoint (context ui) is exposed in web's public surface via dock.assistantPlaceFor — couples the contexts.
Cross-context type PdfSeverity (resume → web) apps/web/src/features/ats-checker/messages.ts:366— PdfSeverity (context resume) is exposed in web's public surface via messages.getPdfSeverityLabel — couples the contexts.
Cross-context type PageMapTarget (pdf → web) apps/web/src/features/resume/editor/store.ts:32— PageMapTarget (context pdf) is exposed in web's public surface via EditorSelection.EditorSelection — couples the contexts.
Cross-context type Script (utils → fonts) packages/fonts/src/index.ts:240— Script (context utils) is exposed in fonts's public surface via index.getPdfFallbackFontFamilies — couples the contexts.
Cross-context type SemanticNodeKind (resume → pdf) packages/pdf/src/semantic/rich-text-keys.ts:19— SemanticNodeKind (context resume) is exposed in pdf's public surface via rich-text-keys.getRichTextSemanticKind — couples the contexts.
Cross-context type Block (mobile → resume) packages/resume/src/proposals.ts:167— Block (context mobile) is exposed in resume's public surface via proposals.splitBlocks — couples the contexts.
Cross-context type JsonSchema (server → tooling) tooling/semantic-css/generate-reference.ts:91— JsonSchema (context server) is exposed in tooling's public surface via generate-reference.renderSchemaReference — couples the contexts.
IC1 · Incompleteness & stubs· Markup wires an event to an empty handler · ×1
Markup wires an event to an empty handler apps/mobile/src/draft/conflict-sheet.tsx:39— `onRequestClose` is wired to an arrow whose body is empty — the markup attaches a listener that does nothing. Implement the handler, or remove the attribute that wires it.
IC1 · Incompleteness & stubs· Both branches are identical · ×1
Both branches are identical — the condition decides nothing apps/web/src/features/resume/editor/chrome.tsx:131— Both arms of this conditional expression are the same, so no input can make the condition matter. Implement the distinction that was intended, or drop the condition.
Sync-over-async blocking apps/web/src/features/resume/import/read-file.ts:78— `unzipSync` in `detectImportKind` 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.
Duplication concentrated across 2 sibling directories (151 clone groups) apps/mobile/src/features/check/issues.ts:2— 151 duplicated blocks under apps/ have copies in at least two of the sibling directories mobile, web — 114 of them are reported below, and 37 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 151 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 151 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 151 separate extractions. Check first whether the siblings are deliberately standalone deliverables (scaffold templates, demo apps that must stay copy-pasteable); where they are, the duplication is the design and the per-block rows are the ones to act on.
Duplication concentrated across 19 sibling directories (48 clone groups) packages/pdf/src/templates/ditgar/DitgarPage.tsx:1— 48 duplicated blocks under packages/pdf/src/templates/ have copies in at least two of the sibling directories azurill, bronzor, chikorita, ditgar, ditto, gengar (+13 more sibling(s) not listed) — 37 of them are reported below, and 11 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 48 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 48 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 48 separate extractions. Check first whether the siblings are deliberately standalone deliverables (scaffold templates, demo apps that must stay copy-pasteable); where they are, the duplication is the design and the per-block rows are the ones to act on.
Duplication concentrated across 9 sibling directories (42 clone groups) apps/web/src/features/assistant/assistant-panel.tsx:150— 42 duplicated blocks under apps/web/src/features/ have copies in at least two of the sibling directories applications, assistant, ats-checker, career, command-palette, documents (+3 more sibling(s) not listed) — 17 of them are reported below, and 25 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 42 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 42 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 42 separate extractions. Check first whether the siblings are deliberately standalone deliverables (scaffold templates, demo apps that must stay copy-pasteable); where they are, the duplication is the design and the per-block rows are the ones to act on.
Duplication concentrated across 19 sibling directories (39 clone groups) apps/mobile/src/features/letters/rich-text-field.tsx:16— 39 duplicated blocks under apps/mobile/src/features/ have copies in at least two of the sibling directories ai, application-detail, applications, applications-board, assistant, ats-checker (+13 more sibling(s) not listed) — 22 of them are reported below, and 17 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 39 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 39 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 39 separate extractions. Check first whether the siblings are deliberately standalone deliverables (scaffold templates, demo apps that must stay copy-pasteable); where they are, the duplication is the design and the per-block rows are the ones to act on.
Duplication concentrated across 4 sibling directories (34 clone groups) apps/web/src/features/letters/use-letter-mode.ts:31— 34 duplicated blocks under apps/web/src/ have copies in at least two of the sibling directories components, dialogs, features, routes — 19 of them are reported below, and 15 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 34 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 34 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 34 separate extractions. Check first whether the siblings are deliberately standalone deliverables (scaffold templates, demo apps that must stay copy-pasteable); where they are, the duplication is the design and the per-block rows are the ones to act on.
Duplication concentrated across 9 sibling directories (26 clone groups) packages/api/src/features/cover-letters/versions.ts:25— 26 duplicated blocks under packages/api/src/features/ have copies in at least two of the sibling directories agent, ai-providers, applications, auth, career, cover-letters (+3 more sibling(s) not listed) — 8 of them are reported below, and 18 are counted here but not reported individually: those copies match on shape but no longer clear R10's bar for an individually reported row — either they kept neither their own names nor their values, or what was copied is too small to stand on its own (it reports near-exact duplication only, and only of substantial extent). What this row states is the concentration, which the detector measured over all 26 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 26 local ones: the siblings replicate behaviour none of them owns, which is the shape of a missing shared module — a common library every sibling imports — rather than 26 separate extractions. Check first whether the siblings are deliberately standalone deliverables (scaffold templates, demo apps that must stay copy-pasteable); where they are, the duplication is the design and the per-block rows are the ones to act on.
Duplication concentrated across 12 sibling directories (22 clone groups) packages/docx/src/html-to-docx.ts:54— 22 duplicated blocks under packages/ have copies in at least two of the sibling directories ai, api, auth, docx, env, forme-native (+6 more sibling(s) not listed) — 15 of them are reported below, and 7 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 22 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 22 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 22 separate extractions. Check first whether the siblings are deliberately standalone deliverables (scaffold templates, demo apps that must stay copy-pasteable); where they are, the duplication is the design and the per-block rows are the ones to act on.
Duplication concentrated across 3 sibling directories (17 clone groups) apps/web/src/features/applications/csv.ts:17— 17 duplicated blocks under the repository root have copies in at least two of the sibling directories apps, packages, tooling — 9 of them are reported below, and 8 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 17 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 17 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 17 separate extractions. Check first whether the siblings are deliberately standalone deliverables (scaffold templates, demo apps that must stay copy-pasteable); where they are, the duplication is the design and the per-block rows are the ones to act on.
Duplication concentrated across 6 sibling directories (10 clone groups) apps/mobile/src/features/letters/page.tsx:58— 10 duplicated blocks under apps/mobile/src/ have copies in at least two of the sibling directories draft, features, i18n, preview, shell, ui — 3 of them are reported below, and 7 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 10 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 10 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 10 separate extractions. Check first whether the siblings are deliberately standalone deliverables (scaffold templates, demo apps that must stay copy-pasteable); where they are, the duplication is the design and the per-block rows are the ones to act on.
Duplication concentrated across 2 sibling directories (8 clone groups) apps/mobile/app/_layout.tsx:102— 8 duplicated blocks under apps/mobile/ have copies in at least two of the sibling directories app, src — 4 of them are reported below, and 4 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 8 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 8 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 8 separate extractions. Check first whether the siblings are deliberately standalone deliverables (scaffold templates, demo apps that must stay copy-pasteable); where they are, the duplication is the design and the per-block rows are the ones to act on.
Duplication concentrated across 2 sibling directories (5 clone groups) apps/web/src/routes/builder/$resumeId/-components/editor-shell.tsx:30— 5 duplicated blocks under apps/web/src/routes/builder/ have copies in at least two of the sibling directories $resumeId, letter — 4 of them are reported below, and 1 is 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 5 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 5 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 5 separate extractions. Check first whether the siblings are deliberately standalone deliverables (scaffold templates, demo apps that must stay copy-pasteable); where they are, the duplication is the design and the per-block rows are the ones to act on.
Wholesale file copy (244 identical lines × 2 files) apps/mobile/src/features/check/issues.ts:2— apps/mobile/src/features/check/issues.ts:2 · apps/web/src/features/resume/editor/check/issues.ts:1 — these 2 files are line-for-line copies of one another — 244 lines are identical, in the same order, in every one of them — so this is one fact about the file set, not a block to extract. An edit made to one file and not the others changes behaviour silently, which is the failure a wholesale copy guarantees. Pick one file as the single source and derive the others from it (re-export it, spread it into the local overrides each variant genuinely needs, or generate the copies at build time) — the few lines that differ between the files are exactly the part each variant should still own. Check first whether the copies are deliberately standalone deliverables (a translation file seeded from its sibling and waiting to be translated); where they are, the duplication is the design, and the honest move is to mark the seeded file as untranslated rather than to let it pass as done.
Wholesale file copy (206 identical lines × 2 files) packages/pdf/src/templates/ditgar/DitgarPage.tsx:1— packages/pdf/src/templates/ditgar/DitgarPage.tsx:1 · packages/pdf/src/templates/gengar/GengarPage.tsx:1 — these 2 files are line-for-line copies of one another — 206 lines are identical, in the same order, in every one of them — so this is one fact about the file set, not a block to extract. An edit made to one file and not the others changes behaviour silently, which is the failure a wholesale copy guarantees. Pick one file as the single source and derive the others from it (re-export it, spread it into the local overrides each variant genuinely needs, or generate the copies at build time) — the few lines that differ between the files are exactly the part each variant should still own. Check first whether the copies are deliberately standalone deliverables (a translation file seeded from its sibling and waiting to be translated); where they are, the duplication is the design, and the honest move is to mark the seeded file as untranslated rather than to let it pass as done.
R10 · Code Duplication· Duplicated block with local edits (178 matched lines × 2 locations) · ×1
Duplicated block with local edits (178 matched lines × 2 locations) apps/mobile/src/features/workspace/tabs/debrief.tsx:37— apps/mobile/src/features/workspace/tabs/debrief.tsx:37 · apps/web/src/features/career/workspace/debrief.tsx:52 — the two spans are one implementation copied and then locally edited — 1260 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 (147 matched lines × 2 locations) · ×1
Duplicated block with local edits (147 matched lines × 2 locations) apps/mobile/src/features/workspace/tabs/saved.tsx:25— apps/mobile/src/features/workspace/tabs/saved.tsx:25 · apps/web/src/features/career/workspace/saved.tsx:22 — the two spans are one implementation copied and then locally edited — 1278 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 (146 matched lines × 2 locations) · ×1
Duplicated block with local edits (146 matched lines × 2 locations) apps/mobile/src/features/workspace/tabs/messages.tsx:40— apps/mobile/src/features/workspace/tabs/messages.tsx:40 · apps/web/src/features/career/workspace/messages.tsx:36 — the two spans are one implementation copied and then locally edited — 1091 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 (136 matched lines × 2 locations) · ×1
Duplicated block with local edits (136 matched lines × 2 locations) apps/mobile/src/features/letters/rich-text-field.tsx:16— apps/mobile/src/features/letters/rich-text-field.tsx:16 · apps/mobile/src/features/write/rich-text-field.tsx:23 — the two spans are one implementation copied and then locally edited — 936 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 (129 lines × 2 locations) apps/mobile/src/features/ai/catalog.ts:53— apps/mobile/src/features/ai/catalog.ts:53 · apps/web/src/features/settings/ai/catalog.ts:71 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
R10 · Code Duplication· Duplicated block with local edits (108 matched lines × 2 locations) · ×1
Duplicated block with local edits (108 matched lines × 2 locations) apps/web/src/features/assistant/assistant-panel.tsx:150— apps/web/src/features/assistant/assistant-panel.tsx:150 · apps/web/src/features/career/coach.tsx:320 — the two spans are one implementation copied and then locally edited — 550 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 (104 matched lines × 2 locations) · ×1
Duplicated block with local edits (104 matched lines × 2 locations) packages/docx/src/html-to-docx.ts:54— packages/docx/src/html-to-docx.ts:54 · packages/odt/src/html-to-odt.ts:12 — the two spans are one implementation copied and then locally edited — 704 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 (85 matched lines × 2 locations) · ×1
Duplicated block with local edits (85 matched lines × 2 locations) apps/web/src/dialogs/auth/disable-two-factor.tsx:27— apps/web/src/dialogs/auth/disable-two-factor.tsx:27 · apps/web/src/dialogs/auth/enable-two-factor.tsx:33 — the two spans are one implementation copied and then locally edited — 476 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.
Wholesale file copy (83 identical lines × 2 files) apps/mobile/src/features/applications/next-step.ts:1— apps/mobile/src/features/applications/next-step.ts:1 · apps/web/src/features/applications/next-step.ts:1 — these 2 files are line-for-line copies of one another — 83 lines are identical, in the same order, in every one of them — so this is one fact about the file set, not a block to extract. An edit made to one file and not the others changes behaviour silently, which is the failure a wholesale copy guarantees. Pick one file as the single source and derive the others from it (re-export it, spread it into the local overrides each variant genuinely needs, or generate the copies at build time) — the few lines that differ between the files are exactly the part each variant should still own. Check first whether the copies are deliberately standalone deliverables (a translation file seeded from its sibling and waiting to be translated); where they are, the duplication is the design, and the honest move is to mark the seeded file as untranslated rather than to let it pass as done.
R10 · Code Duplication· Duplicated block with local edits (81 matched lines × 2 locations) · ×1
Duplicated block with local edits (81 matched lines × 2 locations) packages/ui/src/components/dialog.tsx:7— packages/ui/src/components/dialog.tsx:7 · packages/ui/src/components/sheet.tsx:7 — the two spans are one implementation copied and then locally edited — 461 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 (80 matched lines × 2 locations) · ×1
Duplicated block with local edits (80 matched lines × 2 locations) apps/mobile/src/features/history/history.tsx:64— apps/mobile/src/features/history/history.tsx:64 · apps/mobile/src/features/letters/share.tsx:285 — the two spans are one implementation copied and then locally edited — 685 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 (78 matched lines × 2 locations) · ×1
Duplicated block with local edits (78 matched lines × 2 locations) apps/web/src/features/auth/pages/forgot-password.tsx:49— apps/web/src/features/auth/pages/forgot-password.tsx:49 · apps/web/src/features/auth/pages/register.tsx:96 — the two spans are one implementation copied and then locally edited — 434 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 (72 matched lines × 2 locations) · ×1
Duplicated block with local edits (72 matched lines × 2 locations) apps/mobile/src/features/history/history.tsx:181— apps/mobile/src/features/history/history.tsx:181 · apps/mobile/src/features/letters/share.tsx:390 — the two spans are one implementation copied and then locally edited — 494 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 (65 lines × 2 locations) apps/mobile/src/features/workspace/logic.ts:268— apps/mobile/src/features/workspace/logic.ts:268 · apps/web/src/features/career/workspace/recorder.ts:202 — the 2 copies are spread across 2 directories, so the shared home is a decision rather than an obvious spot: check first whether one of them already owns this behaviour, and otherwise put the extracted module somewhere all of the sites already reach rather than making one of them depend on another.
R10 · Code Duplication· Duplicated block with local edits (55 matched lines × 2 locations) · ×1
Duplicated block with local edits (55 matched lines × 2 locations) apps/web/src/features/assistant/conversation.tsx:695— apps/web/src/features/assistant/conversation.tsx:695 · apps/web/src/features/career/coach-thread.tsx:359 — the two spans are one implementation copied and then locally edited — 330 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 (53 lines × 2 locations) packages/pdf/src/templates/porygon/PorygonPage.tsx:33— packages/pdf/src/templates/porygon/PorygonPage.tsx:33 · packages/pdf/src/templates/scizor/ScizorPage.tsx:33 — the 2 copies are spread across 2 directories, so the shared home is a decision rather than an obvious spot: check first whether one of them already owns this behaviour, and otherwise put the extracted module somewhere all of the sites already reach rather than making one of them depend on another.
Duplicated block (51 lines × 2 locations) apps/mobile/src/features/write/model.ts:39— apps/mobile/src/features/write/model.ts:39 · apps/web/src/features/resume/editor/write/model.ts:19 — the 2 copies are spread across 2 directories, so the shared home is a decision rather than an obvious spot: check first whether one of them already owns this behaviour, and otherwise put the extracted module somewhere all of the sites already reach rather than making one of them depend on another.
R10 · Code Duplication· Duplicated block with local edits (49 matched lines × 2 locations) · ×1
Duplicated block with local edits (49 matched lines × 2 locations) apps/mobile/src/features/application-detail/interview-sheet.tsx:90— apps/mobile/src/features/application-detail/interview-sheet.tsx:90 · apps/web/src/features/applications/components/interview-dialog.tsx:111 — the two spans are one implementation copied and then locally edited — 372 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 (49 lines × 2 locations) apps/mobile/src/features/write/model.ts:104— apps/mobile/src/features/write/model.ts:104 · apps/web/src/features/resume/editor/write/model.ts:88 — the 2 copies are spread across 2 files, and the SHAPE of this repetition could not be determined. It is not a run of declarations, a listing, a declaration header, a type body or a slice through a construct — and it was not measured as a run of executable statements either, so this row cannot tell you whether a function can stand where these lines are. Read the two spans before acting, because the move is opposite in the two cases. Where they are statements, the ordinary answer holds: give the shared part one home and call it from each site. Where they turn out to be declarations, a literal's entries, or the cases of an enumeration, there is no call site to call anything from, and collapsing them would delete what each copy pins — a shared base type, a generated set, or one exported constant each site refers to is the move instead, and sometimes the honest answer is that there is nothing to extract at all. Reported because the copies drift apart the first time only one of them is edited, which is true whichever of those they are.
Complex function resolveStylesheet (cyclomatic 90, cognitive 216) packages/resume/src/stylesheet/cascade.ts:554— resolveStylesheet has cyclomatic complexity 90 and cognitive complexity 216; 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 ScheduleSheet (cyclomatic 72, cognitive 62) apps/web/src/features/career/schedule-sheet.tsx:129— ScheduleSheet has cyclomatic complexity 72 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.
Complex function AddApplicationSheet (cyclomatic 72, cognitive 45) apps/mobile/src/features/applications/add-sheet.tsx:48— AddApplicationSheet has cyclomatic complexity 72 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 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 parseDeepLink (cyclomatic 65, cognitive 84) apps/mobile/src/linking/parse.ts:39— parseDeepLink has cyclomatic complexity 65 and cognitive complexity 84; 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 toFormeStyle (cyclomatic 64, cognitive 127) packages/pdf/src/forme/style.ts:373— toFormeStyle has cyclomatic complexity 64 and cognitive complexity 127; 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 convertNode (cyclomatic 63, cognitive 97) packages/pdf/src/forme/to-forme.tsx:466— convertNode has cyclomatic complexity 63 and cognitive complexity 97; 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 DocumentsLibrary (cyclomatic 58, cognitive 54) apps/mobile/src/features/documents/library.tsx:159— DocumentsLibrary has cyclomatic complexity 58 and cognitive complexity 54; 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 parseReactiveResumeV4JSON (cyclomatic 53, cognitive 56) packages/import/src/reactive-resume-v4-json.tsx:241— parseReactiveResumeV4JSON has cyclomatic complexity 53 and cognitive complexity 56; 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 NewDocument (cyclomatic 51, cognitive 44) apps/mobile/src/features/documents/new-document.tsx:24— NewDocument has cyclomatic complexity 51 and cognitive complexity 44; 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 send (cyclomatic 50, cognitive 57) packages/api/src/features/agent/service.ts:1117— send has cyclomatic complexity 50 and cognitive complexity 57; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function ApplicationsList (cyclomatic 49, cognitive 43) apps/mobile/src/features/applications/list-screen.tsx:55— ApplicationsList has cyclomatic complexity 49 and cognitive complexity 43; 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 Session (cyclomatic 48, cognitive 42) apps/web/src/features/career/workspace/practise.tsx:218— Session has cyclomatic complexity 48 and cognitive complexity 42; 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 WebAccessSection (cyclomatic 48, cognitive 36) apps/web/src/features/settings/ai/web-access.tsx:30— WebAccessSection has cyclomatic complexity 48 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.
Complex function processBlockElement (cyclomatic 47, cognitive 96) packages/docx/src/html-to-docx.ts:149— processBlockElement has cyclomatic complexity 47 and cognitive complexity 96; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function CoachPage (cyclomatic 46, cognitive 46) apps/web/src/features/career/coach.tsx:104— CoachPage has cyclomatic complexity 46 and cognitive complexity 46; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function ProviderForm (cyclomatic 43, cognitive 39) apps/mobile/src/features/ai/provider-editor.tsx:75— ProviderForm has cyclomatic complexity 43 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 Session (cyclomatic 43, cognitive 39) apps/mobile/src/features/workspace/tabs/practise.tsx:185— Session has cyclomatic complexity 43 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 ContextColumn (cyclomatic 43, cognitive 37) apps/web/src/features/career/workspace/shell.tsx:465— ContextColumn has cyclomatic complexity 43 and cognitive complexity 37; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive 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 ToolPartView (cyclomatic 42, cognitive 54) apps/mobile/src/features/assistant/messages.tsx:201— ToolPartView has cyclomatic complexity 42 and cognitive complexity 54; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
R3 · Large Files· packages/api/src/features/agent/service.ts · ×1
packages/api/src/features/agent/service.ts: 1582 lines of code packages/api/src/features/agent/service.ts:1— packages/api/src/features/agent/service.ts has 1582 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· packages/pdf/src/templates/shared/sections.tsx · ×1
packages/pdf/src/templates/shared/sections.tsx: 1399 lines of code packages/pdf/src/templates/shared/sections.tsx:1— packages/pdf/src/templates/shared/sections.tsx has 1399 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· apps/web/src/routeTree.gen.ts · ×1
apps/web/src/routeTree.gen.ts: 1126 lines of code apps/web/src/routeTree.gen.ts:1— apps/web/src/routeTree.gen.ts has 1126 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· packages/api/src/features/career/service.ts · ×1
packages/api/src/features/career/service.ts: 1117 lines of code packages/api/src/features/career/service.ts:1— packages/api/src/features/career/service.ts has 1117 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· apps/web/src/features/career/workspace/practise.tsx · ×1
apps/web/src/features/career/workspace/practise.tsx: 1030 lines of code apps/web/src/features/career/workspace/practise.tsx:1— apps/web/src/features/career/workspace/practise.tsx has 1030 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· packages/pdf/src/forme/to-forme.tsx · ×1
packages/pdf/src/forme/to-forme.tsx: 978 lines of code packages/pdf/src/forme/to-forme.tsx:1— packages/pdf/src/forme/to-forme.tsx has 978 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· packages/pdf/src/semantic/tree.ts · ×1
packages/pdf/src/semantic/tree.ts: 918 lines of code packages/pdf/src/semantic/tree.ts:1— packages/pdf/src/semantic/tree.ts has 918 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· apps/web/src/features/assistant/conversation.tsx · ×1
apps/web/src/features/assistant/conversation.tsx: 843 lines of code apps/web/src/features/assistant/conversation.tsx:1— apps/web/src/features/assistant/conversation.tsx has 843 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· apps/mobile/src/features/assistant/chat-view.tsx · ×1
apps/mobile/src/features/assistant/chat-view.tsx: 839 lines of code apps/mobile/src/features/assistant/chat-view.tsx:1— apps/mobile/src/features/assistant/chat-view.tsx has 839 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· packages/resume/src/stylesheet/cascade.ts · ×1
packages/resume/src/stylesheet/cascade.ts: 838 lines of code packages/resume/src/stylesheet/cascade.ts:1— packages/resume/src/stylesheet/cascade.ts has 838 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· packages/api/src/features/applications/service.ts · ×1
packages/api/src/features/applications/service.ts: 810 lines of code packages/api/src/features/applications/service.ts:1— packages/api/src/features/applications/service.ts has 810 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· apps/mobile/src/features/application-detail/sections.tsx · ×1
apps/mobile/src/features/application-detail/sections.tsx: 805 lines of code apps/mobile/src/features/application-detail/sections.tsx:1— apps/mobile/src/features/application-detail/sections.tsx has 805 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· apps/web/src/features/career/today.tsx · ×1
apps/web/src/features/career/today.tsx: 787 lines of code apps/web/src/features/career/today.tsx:1— apps/web/src/features/career/today.tsx has 787 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· apps/web/src/features/resume/editor/write/picture-settings.tsx · ×1
apps/web/src/features/resume/editor/write/picture-settings.tsx: 762 lines of code apps/web/src/features/resume/editor/write/picture-settings.tsx:1— apps/web/src/features/resume/editor/write/picture-settings.tsx has 762 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· packages/schema/src/resume/data.ts · ×1
packages/schema/src/resume/data.ts: 755 lines of code packages/schema/src/resume/data.ts:1— packages/schema/src/resume/data.ts has 755 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· packages/mcp/src/tool-meta.ts · ×1
packages/mcp/src/tool-meta.ts: 747 lines of code packages/mcp/src/tool-meta.ts:1— packages/mcp/src/tool-meta.ts has 747 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· apps/mobile/src/features/workspace/tabs/practise.tsx · ×1
apps/mobile/src/features/workspace/tabs/practise.tsx: 739 lines of code apps/mobile/src/features/workspace/tabs/practise.tsx:1— apps/mobile/src/features/workspace/tabs/practise.tsx has 739 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· apps/mobile/src/features/letters/write.tsx · ×1
apps/mobile/src/features/letters/write.tsx: 726 lines of code apps/mobile/src/features/letters/write.tsx:1— apps/mobile/src/features/letters/write.tsx has 726 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· packages/api/src/features/resume/service.ts · ×1
packages/api/src/features/resume/service.ts: 719 lines of code packages/api/src/features/resume/service.ts:1— packages/api/src/features/resume/service.ts has 719 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· apps/web/src/features/resume/builder/draft.ts · ×1
apps/web/src/features/resume/builder/draft.ts: 704 lines of code apps/web/src/features/resume/builder/draft.ts:1— apps/web/src/features/resume/builder/draft.ts has 704 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· apps/web/src/features/homepage/prepare.tsx · ×1
apps/web/src/features/homepage/prepare.tsx: 687 lines of code apps/web/src/features/homepage/prepare.tsx:1— apps/web/src/features/homepage/prepare.tsx has 687 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· apps/web/src/features/settings/ai/providers.tsx · ×1
apps/web/src/features/settings/ai/providers.tsx: 680 lines of code apps/web/src/features/settings/ai/providers.tsx:1— apps/web/src/features/settings/ai/providers.tsx has 680 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· apps/web/src/features/career/coach-chat.tsx · ×1
apps/web/src/features/career/coach-chat.tsx: 676 lines of code apps/web/src/features/career/coach-chat.tsx:1— apps/web/src/features/career/coach-chat.tsx has 676 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· apps/web/src/features/career/coach.tsx · ×1
apps/web/src/features/career/coach.tsx: 674 lines of code apps/web/src/features/career/coach.tsx:1— apps/web/src/features/career/coach.tsx has 674 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· apps/mobile/src/ui/overlays.tsx · ×1
apps/mobile/src/ui/overlays.tsx: 669 lines of code apps/mobile/src/ui/overlays.tsx:1— apps/mobile/src/ui/overlays.tsx has 669 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· apps/web/src/routes/builder/letter/-components/write-panel.tsx · ×1
apps/web/src/routes/builder/letter/-components/write-panel.tsx: 664 lines of code apps/web/src/routes/builder/letter/-components/write-panel.tsx:1— apps/web/src/routes/builder/letter/-components/write-panel.tsx has 664 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· packages/auth/src/config.ts · ×1
packages/auth/src/config.ts: 662 lines of code packages/auth/src/config.ts:1— packages/auth/src/config.ts has 662 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· apps/web/src/features/applications/components/application-detail-sheet.tsx · ×1
apps/web/src/features/applications/components/application-detail-sheet.tsx: 647 lines of code apps/web/src/features/applications/components/application-detail-sheet.tsx:1— apps/web/src/features/applications/components/application-detail-sheet.tsx has 647 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· apps/web/src/features/career/workspace/shell.tsx · ×1
apps/web/src/features/career/workspace/shell.tsx: 637 lines of code apps/web/src/features/career/workspace/shell.tsx:1— apps/web/src/features/career/workspace/shell.tsx has 637 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· packages/resume/src/stylesheet/values.ts · ×1
packages/resume/src/stylesheet/values.ts: 637 lines of code packages/resume/src/stylesheet/values.ts:1— packages/resume/src/stylesheet/values.ts has 637 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· packages/api/src/features/career/jobs.ts · ×1
packages/api/src/features/career/jobs.ts: 635 lines of code packages/api/src/features/career/jobs.ts:1— packages/api/src/features/career/jobs.ts has 635 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· apps/web/src/features/career/workspace/prepare.tsx · ×1
apps/web/src/features/career/workspace/prepare.tsx: 629 lines of code apps/web/src/features/career/workspace/prepare.tsx:1— apps/web/src/features/career/workspace/prepare.tsx has 629 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· apps/web/src/features/career/workspace/apply.tsx · ×1
apps/web/src/features/career/workspace/apply.tsx: 626 lines of code apps/web/src/features/career/workspace/apply.tsx:1— apps/web/src/features/career/workspace/apply.tsx has 626 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· apps/mobile/src/features/write/outline.tsx · ×1
apps/mobile/src/features/write/outline.tsx: 623 lines of code apps/mobile/src/features/write/outline.tsx:1— apps/mobile/src/features/write/outline.tsx has 623 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files· apps/web/src/features/documents/new-document-dialog.tsx · ×1
apps/web/src/features/documents/new-document-dialog.tsx: 611 lines of code apps/web/src/features/documents/new-document-dialog.tsx:1— apps/web/src/features/documents/new-document-dialog.tsx has 611 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· apps/mobile/src/features/applications-board/board-screen.tsx · ×1
apps/mobile/src/features/applications-board/board-screen.tsx: 610 lines of code apps/mobile/src/features/applications-board/board-screen.tsx:1— apps/mobile/src/features/applications-board/board-screen.tsx has 610 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· apps/mobile/src/features/documents/library.tsx · ×1
apps/mobile/src/features/documents/library.tsx: 605 lines of code apps/mobile/src/features/documents/library.tsx:1— apps/mobile/src/features/documents/library.tsx has 605 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· apps/web/src/features/career/schedule-sheet.tsx · ×1
apps/web/src/features/career/schedule-sheet.tsx: 601 lines of code apps/web/src/features/career/schedule-sheet.tsx:1— apps/web/src/features/career/schedule-sheet.tsx has 601 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
apps/mobile/app/dev/ui.tsx: 594 lines of code apps/mobile/app/dev/ui.tsx:1— apps/mobile/app/dev/ui.tsx has 594 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· apps/web/src/features/documents/documents-page.tsx · ×1
apps/web/src/features/documents/documents-page.tsx: 592 lines of code apps/web/src/features/documents/documents-page.tsx:1— apps/web/src/features/documents/documents-page.tsx has 592 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R6 · Tooling· The declared test suite includes a file that cannot be loaded · ×1
The declared test suite includes a file that cannot be loaded apps/server/src/static/agent-skills.test.ts:8— This repository declares test tooling, and the ✓ above records that declaration — but apps/server/src/static/agent-skills.test.ts and 3 other test file(s) in this workspace cannot be loaded at all: it imports a module that names no file in this repository, so the runner throws while collecting it and none of its cases execute. The wiring is present and the suite it points at does not run as written, which is why the tooling tick must not be read as a statement that the tests pass. Fix the unloadable file(s) — each one is reported with its failing import under Test Coverage — then the declared script exercises what it claims to.
Dead file (~896 LoC) apps/mobile/src/features/assistant/chat-view.tsx— no import path from any entry point (277 application, 56 tooling, 375 test roots considered), but 3 in-repo import(s) from 3 other file(s) do name it (apps/mobile/src/features/assistant/assistant-screen.tsx, apps/mobile/src/features/assistant/coach-screen.tsx, apps/mobile/src/features/workspace/coach-sheet.tsx) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it
Dead file (~842 LoC) apps/mobile/src/features/application-detail/sections.tsx— no import path from any entry point (277 application, 56 tooling, 375 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (apps/mobile/src/features/application-detail/detail-screen.tsx) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it
Dead file (~773 LoC) apps/mobile/src/features/workspace/tabs/practise.tsx— no import path from any entry point (277 application, 56 tooling, 375 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (apps/mobile/app/applications/[id]/[tab].tsx) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it
Dead file (~764 LoC) apps/mobile/src/features/letters/write.tsx— no import path from any entry point (277 application, 56 tooling, 375 test roots considered), but 2 in-repo import(s) from 2 other file(s) do name it (apps/mobile/app/letter/[id]/write.tsx, apps/mobile/src/features/letters/design.tsx) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it
Dead file (~651 LoC) apps/mobile/src/features/write/outline.tsx— no import path from any entry point (277 application, 56 tooling, 375 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (apps/mobile/app/builder/[id]/write.tsx) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it
Dead file (~632 LoC) apps/mobile/src/features/applications-board/board-screen.tsx— no import path from any entry point (277 application, 56 tooling, 375 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (apps/mobile/app/(tabs)/applications/board.tsx) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it
Dead file (~619 LoC) apps/mobile/src/features/assistant/messages.tsx— no import path from any entry point (277 application, 56 tooling, 375 test roots considered), but 2 in-repo import(s) from 1 other file(s) do name it (apps/mobile/src/features/assistant/chat-view.tsx) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it
Dead file (~611 LoC) apps/mobile/src/features/documents/library.tsx— no import path from any entry point (277 application, 56 tooling, 375 test roots considered), but 2 in-repo import(s) from 2 other file(s) do name it (apps/mobile/app/(tabs)/documents/index.tsx, apps/mobile/app/(tabs)/documents/trash.tsx) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it
Dead file (~584 LoC) apps/mobile/src/features/ats-checker/checker.tsx— no import path from any entry point (277 application, 56 tooling, 375 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (apps/mobile/app/ats-checker.tsx) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it
Dead file (~575 LoC) apps/mobile/src/features/workspace/tabs/apply.tsx— no import path from any entry point (277 application, 56 tooling, 375 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (apps/mobile/app/applications/[id]/[tab].tsx) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it
Dead file (~553 LoC) apps/mobile/src/features/design/advanced.tsx— no import path from any entry point (277 application, 56 tooling, 375 test roots considered), but 2 in-repo import(s) from 1 other file(s) do name it (apps/mobile/src/features/design/design-pane.tsx) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it
Dead file (~535 LoC) apps/mobile/src/features/applications/add-sheet.tsx— no import path from any entry point (277 application, 56 tooling, 375 test roots considered), but 2 in-repo import(s) from 2 other file(s) do name it (apps/mobile/src/features/applications-board/views.tsx, apps/mobile/src/features/applications/list-screen.tsx) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it
Dead file (~515 LoC) apps/mobile/src/features/application-detail/sheets.tsx— no import path from any entry point (277 application, 56 tooling, 375 test roots considered), but 4 in-repo import(s) from 4 other file(s) do name it (apps/mobile/src/features/application-detail/detail-screen.tsx, apps/mobile/src/features/application-detail/sections.tsx, apps/mobile/src/features/applications-board/board-screen.tsx and 1 more) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it
Dead file (~514 LoC) apps/mobile/src/features/write/model.ts— no import path from any entry point (277 application, 56 tooling, 375 test roots considered), but 12 in-repo import(s) from 7 other file(s) do name it (apps/mobile/src/features/write/entry-fields.tsx, apps/mobile/src/features/write/entry-screen.tsx, apps/mobile/src/features/write/entry-sheet.tsx and 4 more) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it
Dead file (~506 LoC) apps/mobile/src/shell/app-tabs.tsx— no import path from any entry point (277 application, 56 tooling, 375 test roots considered), but 2 in-repo import(s) from 2 other file(s) do name it (apps/mobile/app/(tabs)/_layout.tsx, apps/mobile/src/shell/builder-chrome.tsx) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it
Dead file (~500 LoC) apps/mobile/src/features/application-detail/interview-sheet.tsx— no import path from any entry point (277 application, 56 tooling, 375 test roots considered), but 3 in-repo import(s) from 3 other file(s) do name it (apps/mobile/src/features/application-detail/detail-screen.tsx, apps/mobile/src/features/applications-board/calendar-screen.tsx, apps/mobile/src/features/workspace/shell.tsx) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it
Dead file (~493 LoC) apps/mobile/src/features/letters/share.tsx— no import path from any entry point (277 application, 56 tooling, 375 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (apps/mobile/app/letter/[id]/_layout.tsx) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it
Dead file (~482 LoC) apps/mobile/src/features/applications/list-screen.tsx— no import path from any entry point (277 application, 56 tooling, 375 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (apps/mobile/app/(tabs)/applications/index.tsx) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it
Dead file (~476 LoC) apps/mobile/src/features/write/entry-fields.tsx— no import path from any entry point (277 application, 56 tooling, 375 test roots considered), but 2 in-repo import(s) from 2 other file(s) do name it (apps/mobile/src/features/write/basics-screen.tsx, apps/mobile/src/features/write/entry-screen.tsx) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it
Dead file (~468 LoC) apps/mobile/src/features/applications-board/insights-screen.tsx— no import path from any entry point (277 application, 56 tooling, 375 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (apps/mobile/app/(tabs)/applications/insights.tsx) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it
Dead file (~459 LoC) apps/mobile/src/features/applications-board/calendar-screen.tsx— no import path from any entry point (277 application, 56 tooling, 375 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (apps/mobile/app/(tabs)/applications/calendar.tsx) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it
Dead file (~446 LoC) apps/mobile/src/features/search/search-screen.tsx— no import path from any entry point (277 application, 56 tooling, 375 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (apps/mobile/app/search.tsx) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it
Dead file (~444 LoC) apps/mobile/src/features/assistant/assistant-screen.tsx— no import path from any entry point (277 application, 56 tooling, 375 test roots considered), but 2 in-repo import(s) from 2 other file(s) do name it (apps/mobile/app/builder/[id]/assistant.tsx, apps/mobile/app/letter/[id]/assistant.tsx) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it
Dead file (~435 LoC) apps/mobile/src/features/ats-checker/messages.ts— no import path from any entry point (277 application, 56 tooling, 375 test roots considered), but 2 in-repo import(s) from 2 other file(s) do name it (apps/mobile/src/features/ats-checker/checker.tsx, apps/mobile/src/features/check/parser.tsx) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it
Dead file (~422 LoC) apps/mobile/src/lib/timezones.ts— no import path from any entry point (277 application, 56 tooling, 375 test roots considered), but 2 in-repo import(s) from 2 other file(s) do name it (apps/mobile/app/(tabs)/settings/preferences.tsx, apps/mobile/src/features/application-detail/interview-sheet.tsx) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it
Dead file (~410 LoC) apps/mobile/src/features/share/link.tsx— no import path from any entry point (277 application, 56 tooling, 375 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (apps/mobile/src/features/share/screen.tsx) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it
Dead file (~400 LoC) apps/mobile/src/features/design/style-groups.tsx— no import path from any entry point (277 application, 56 tooling, 375 test roots considered), but 3 in-repo import(s) from 3 other file(s) do name it (apps/mobile/src/features/design/advanced.tsx, apps/mobile/src/features/design/design-pane.tsx, apps/mobile/src/features/design/layout-screen.tsx) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it
Dead file (~398 LoC) apps/mobile/src/features/assistant/coach-screen.tsx— no import path from any entry point (277 application, 56 tooling, 375 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (apps/mobile/app/(tabs)/career/coach.tsx) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it
Dead file (~396 LoC) apps/mobile/src/features/workspace/hooks.ts— no import path from any entry point (277 application, 56 tooling, 375 test roots considered), but 16 in-repo import(s) from 8 other file(s) do name it (apps/mobile/src/features/workspace/shell.tsx, apps/mobile/src/features/workspace/tabs/apply.tsx, apps/mobile/src/features/workspace/tabs/debrief.tsx and 5 more) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it
Dead file (~390 LoC) apps/mobile/src/shell/builder-chrome.tsx— no import path from any entry point (277 application, 56 tooling, 375 test roots considered), but 5 in-repo import(s) from 3 other file(s) do name it (apps/mobile/app/builder/[id]/_layout.tsx, apps/mobile/app/letter/[id]/_layout.tsx, apps/mobile/src/features/document-menu/index.tsx) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it
Dead file (~385 LoC) apps/mobile/src/features/write/rich-text-field.tsx— no import path from any entry point (277 application, 56 tooling, 375 test roots considered), but 2 in-repo import(s) from 2 other file(s) do name it (apps/mobile/src/features/write/entry-fields.tsx, apps/mobile/src/features/write/entry-screen.tsx) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it
Dead file (~379 LoC) apps/mobile/src/features/career/today.tsx— no import path from any entry point (277 application, 56 tooling, 375 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (apps/mobile/app/(tabs)/career/today.tsx) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it
Dead file (~374 LoC) apps/mobile/src/features/check/issues.ts— no import path from any entry point (277 application, 56 tooling, 375 test roots considered), but 9 in-repo import(s) from 6 other file(s) do name it (apps/mobile/src/features/check/actions.ts, apps/mobile/src/features/check/model.ts, apps/mobile/src/features/check/page.tsx and 3 more) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it
Dead file (~370 LoC) apps/mobile/src/features/workspace/tabs/debrief.tsx— no import path from any entry point (277 application, 56 tooling, 375 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (apps/mobile/app/applications/[id]/[tab].tsx) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it
Dead file (~365 LoC) apps/mobile/src/features/design/layout-screen.tsx— no import path from any entry point (277 application, 56 tooling, 375 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (apps/mobile/src/features/design/design-pane.tsx) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it
Dead file (~357 LoC) apps/mobile/src/features/workspace/parts.tsx— no import path from any entry point (277 application, 56 tooling, 375 test roots considered), but 9 in-repo import(s) from 8 other file(s) do name it (apps/mobile/src/features/workspace/coach-sheet.tsx, apps/mobile/src/features/workspace/tabs/apply.tsx, apps/mobile/src/features/workspace/tabs/debrief.tsx and 5 more) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it
Dead file (~340 LoC) apps/mobile/src/features/workspace/logic.ts— no import path from any entry point (277 application, 56 tooling, 375 test roots considered), but 8 in-repo import(s) from 7 other file(s) do name it (apps/mobile/src/features/workspace/shell.tsx, apps/mobile/src/features/workspace/tabs/apply.tsx, apps/mobile/src/features/workspace/tabs/debrief.tsx and 4 more) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it
Unused dependency 'lefthook' — Declared in the root package.json but never imported anywhere in that package or its workspace members — no static import reaches it. Usually that is dead weight and attack surface, but two shapes are indistinguishable from source and are NOT dead: an optional or native peer that another dependency loads dynamically at runtime, and a package a build, docs or test step installs and invokes separately. Confirm which of the three this is before removing it.
Unused dependency '@react-email/ui' — Declared in packages/email/package.json but never imported anywhere in that package or its workspace members — no static import reaches it. Usually that is dead weight and attack surface, but two shapes are indistinguishable from source and are NOT dead: an optional or native peer that another dependency loads dynamically at runtime, and a package a build, docs or test step installs and invokes separately. Confirm which of the three this is before removing it.
Duplicated predicate apps/mobile/src/features/career/amount.ts:15— `!/^\d+$/.test(ungrouped) || (fraction !== undefined && !/^\d{1,2}$/.test(fraction))` appears character-identically in 2 files — apps/mobile/src/features/career/amount.ts, apps/web/src/features/career/knowledge/amount.ts. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate apps/mobile/src/features/write/entry-fields.tsx:49— `!["http:", "https:"].includes(parsed.protocol) || !parsed.hostname.includes(".")` appears character-identically in 2 files — apps/mobile/src/features/write/entry-fields.tsx, apps/web/src/features/resume/editor/write/fields.tsx. 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 apps/web/src/features/resume/editor/write/entry-card.tsx:102— `!event.altKey || (event.key !== "ArrowUp" && event.key !== "ArrowDown")` appears character-identically in 2 files — apps/web/src/features/resume/editor/write/entry-card.tsx, apps/web/src/features/resume/editor/write/section-row.tsx. 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 apps/mobile/src/features/assistant/chat.ts:43— `!host.includes(".") || /^[\d.]+$/.test(host) || host.includes(":") || /(?:^|\.)(?:localhost|local|internal|lan)$/.test(host) || host.endsWit…` appears character-identically in 2 files — apps/mobile/src/features/assistant/chat.ts, packages/ai/src/tools/agent-tool-contracts.ts. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate apps/web/src/features/resume/editor/page-overlay.tsx:36— `!pageMap || !page || page.width <= 0 || page.height <= 0` appears character-identically in 2 files — apps/web/src/features/resume/editor/page-overlay.tsx, apps/web/src/routes/builder/letter/-components/letter-page.tsx. 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 apps/mobile/src/features/write/model.ts:269— `!placed.has(id) && isSectionInUse(data, id, recentlyAdded)` appears character-identically in 2 files — apps/mobile/src/features/write/model.ts, apps/web/src/features/resume/editor/write/model.ts. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate apps/mobile/src/features/workspace/tabs/fit.tsx:166— `!readOnly && (status === "missing" || status === "partial")` appears character-identically in 2 files — apps/mobile/src/features/workspace/tabs/fit.tsx, apps/web/src/features/career/workspace/fit.tsx. 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 apps/mobile/src/features/public/reflow.ts:98— `!repeatedPosition || field !== "position"` appears character-identically in 2 files — apps/mobile/src/features/public/reflow.ts, apps/web/src/features/resume/public/resume-reflow.tsx. 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 apps/mobile/src/features/workspace/tabs/apply.tsx:522— `!submitted && !readOnly && index === items.length - 1` appears character-identically in 2 files — apps/mobile/src/features/workspace/tabs/apply.tsx, apps/web/src/features/career/workspace/apply.tsx. 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 apps/mobile/src/features/settings/profile.tsx:106— `!uploaded || typeof uploaded !== "object" || !("url" in uploaded) || typeof uploaded.url !== "string"` appears character-identically in 2 files — apps/mobile/src/features/settings/profile.tsx, apps/mobile/src/features/write/picture-screen.tsx. 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 apps/mobile/src/features/assistant/chat-view.tsx:655— `!value || props.streaming || props.disabled || uploading` appears character-identically in 2 files — apps/mobile/src/features/assistant/chat-view.tsx, apps/web/src/features/career/coach-thread.tsx. 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 apps/mobile/src/features/documents/import-file.ts:26— `"basics" in data && !("sections" in data) && !("metadata" in data)` appears character-identically in 2 files — apps/mobile/src/features/documents/import-file.ts, apps/web/src/features/resume/import/read-file.ts. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate apps/mobile/src/features/documents/import-file.ts:27— `"sections" in data || "metadata" in data` appears character-identically in 2 files — apps/mobile/src/features/documents/import-file.ts, apps/web/src/features/resume/import/read-file.ts. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate apps/mobile/src/features/workspace/logic.ts:317— `(last !== "small" && last !== "ten") || current >= 100` appears character-identically in 2 files — apps/mobile/src/features/workspace/logic.ts, apps/web/src/features/career/workspace/recorder.ts. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate apps/mobile/app/(tabs)/settings/preferences.tsx:51— `Intl.DateTimeFormat().resolvedOptions().timeZone || "UTC"` appears character-identically in 4 files — apps/mobile/app/(tabs)/settings/preferences.tsx, apps/mobile/src/api/client.ts, apps/mobile/src/features/application-detail/interview-sheet.tsx, apps/mobile/src/features/reminders/schedule.ts. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate apps/mobile/src/features/career/amount.ts:23— `Number.isFinite(value) && value <= Number.MAX_SAFE_INTEGER` appears character-identically in 2 files — apps/mobile/src/features/career/amount.ts, apps/web/src/features/career/knowledge/amount.ts. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate apps/mobile/src/features/career/offer-compare.ts:6— `a.currency === b.currency && a.period === b.period` appears character-identically in 2 files — apps/mobile/src/features/career/offer-compare.ts, apps/web/src/features/career/offer-compare.ts. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate apps/mobile/src/features/assistant/proposals.ts:131— `after.startsWith(before) && after.length > before.length` appears character-identically in 2 files — apps/mobile/src/features/assistant/proposals.ts, apps/web/src/features/resume/editor/proposals/proposals.ts. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate apps/mobile/src/features/workspace/tabs/practise.tsx:340— `answer.trim().length >= 10 && (mode === "typed" || spoken !== null) && !busy && !showFeedback` appears character-identically in 2 files — apps/mobile/src/features/workspace/tabs/practise.tsx, apps/web/src/features/career/workspace/practise.tsx. 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 apps/mobile/src/features/applications-board/insights.ts:71— `application.resumeId && isTailored(application) === tailored` appears character-identically in 2 files — apps/mobile/src/features/applications-board/insights.ts, apps/web/src/features/applications/insights.ts. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate apps/mobile/src/features/application-detail/detail-screen.tsx:79— `application.sourceUrl || application.jobDescription` appears character-identically in 2 files — apps/mobile/src/features/application-detail/detail-screen.tsx, apps/web/src/features/applications/components/application-detail-sheet.tsx. 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 apps/mobile/src/features/applications/next-step.ts:61— `application.status === "applied" && days >= FOLLOW_UP_AFTER_DAYS` appears character-identically in 2 files — apps/mobile/src/features/applications/next-step.ts, apps/web/src/features/applications/next-step.ts. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate apps/mobile/src/features/workspace/shell.tsx:108— `archived && (!version || version.data.kind !== archiveKinds[tab])` appears character-identically in 2 files — apps/mobile/src/features/workspace/shell.tsx, apps/web/src/features/career/workspace/shell.tsx. 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 apps/mobile/src/features/career/today.tsx:65— `b.matches.length - a.matches.length || new Date(b.firstSeenAt).getTime() - new Date(a.firstSeenAt).getTime()` appears character-identically in 2 files — apps/mobile/src/features/career/today.tsx, apps/web/src/features/career/today.tsx. 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 apps/mobile/src/features/public/reflow.ts:137— `basics.website.label || basics.website.url.replace(/^https?:\/\//, "")` appears character-identically in 2 files — apps/mobile/src/features/public/reflow.ts, apps/web/src/features/resume/public/resume-reflow.tsx. 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.
Mock-dominated test: creates and duplicates with an automatically generated address packages/mcp/src/tools.test.ts:110— This test sets up 3 test doubles (for example `a double assigned in a shared setup`) against 1 real object(s) of its own, and its only verification is 2 check(s) that the doubles were called. It pins how the code is wired, not what it does: it passes with a wrong result and fails when a call is harmlessly reordered or merged. Assert the outcome instead (the value returned, the state left behind), build collaborators and value objects for real or with a small hand-written fake, and keep doubles for the boundaries the test cannot own — the network, the clock, the file system.
Mock-dominated test: probes search in the user's first region packages/api/src/features/web-access/router.test.ts:30— This test sets up 3 test doubles (for example `vi.mock/jest.mock of an imported module`) against 1 real object(s) of its own, and its only verification is 1 check(s) that the doubles were called. It pins how the code is wired, not what it does: it passes with a wrong result and fails when a call is harmlessly reordered or merged. Assert the outcome instead (the value returned, the state left behind), build collaborators and value objects for real or with a small hand-written fake, and keep doubles for the boundaries the test cannot own — the network, the clock, the file system.
Mock-dominated test: prepares a copy at %s while preserving its base and submitted documents packages/api/src/features/documents/service.test.ts:90— This test sets up 4 test doubles (for example `a double assigned in a shared setup`) against 0 real object(s) of its own, and its only verification is 5 check(s) that the doubles were called. It pins how the code is wired, not what it does: it passes with a wrong result and fails when a call is harmlessly reordered or merged. Assert the outcome instead (the value returned, the state left behind), build collaborators and value objects for real or with a small hand-written fake, and keep doubles for the boundaries the test cannot own — the network, the clock, the file system.
Mock-dominated test: links manual preparation while preserving submission history: %j packages/api/src/features/documents/service.test.ts:111— This test sets up 3 test doubles (for example `vi.fn`) against 0 real object(s) of its own, and its only verification is 3 check(s) that the doubles were called. It pins how the code is wired, not what it does: it passes with a wrong result and fails when a call is harmlessly reordered or merged. Assert the outcome instead (the value returned, the state left behind), build collaborators and value objects for real or with a small hand-written fake, and keep doubles for the boundaries the test cannot own — the network, the clock, the file system.
Mock-dominated test: saves the sent version and score when the %s is linked at Applied packages/api/src/features/applications/service.test.ts:212— This test sets up 5 test doubles (for example `vi.fn`) against 0 real object(s) of its own, and its only verification is 2 check(s) that the doubles were called. It pins how the code is wired, not what it does: it passes with a wrong result and fails when a call is harmlessly reordered or merged. Assert the outcome instead (the value returned, the state left behind), build collaborators and value objects for real or with a small hand-written fake, and keep doubles for the boundaries the test cannot own — the network, the clock, the file system.
Mock-dominated test: saves it once, and not before the application is sent packages/api/src/features/applications/service.test.ts:238— This test sets up 4 test doubles (for example `vi.fn`) against 0 real object(s) of its own, and its only verification is 1 check(s) that the doubles were called. It pins how the code is wired, not what it does: it passes with a wrong result and fails when a call is harmlessly reordered or merged. Assert the outcome instead (the value returned, the state left behind), build collaborators and value objects for real or with a small hand-written fake, and keep doubles for the boundaries the test cannot own — the network, the clock, the file system.
Mock-dominated test: does not delete the replaced upload when another application still references it packages/api/src/features/applications/service.test.ts:395— This test sets up 3 test doubles (for example `vi.fn`) against 1 real object(s) of its own, and its only verification is 1 check(s) that the doubles were called. It pins how the code is wired, not what it does: it passes with a wrong result and fails when a call is harmlessly reordered or merged. Assert the outcome instead (the value returned, the state left behind), build collaborators and value objects for real or with a small hand-written fake, and keep doubles for the boundaries the test cannot own — the network, the clock, the file system.
Mock-dominated test: leaves the document and the posting out when their context chips are removed packages/api/src/features/agent/service.test.ts:334— This test sets up 8 test doubles (for example `vi.fn`) against 2 real object(s) of its own, and its only verification is 15 check(s) that the doubles were called. It pins how the code is wired, not what it does: it passes with a wrong result and fails when a call is harmlessly reordered or merged. Assert the outcome instead (the value returned, the state left behind), build collaborators and value objects for real or with a small hand-written fake, and keep doubles for the boundaries the test cannot own — the network, the clock, the file system.
Mock-dominated test: signals a remote run without releasing its database claim packages/api/src/features/agent/service.test.ts:1341— This test sets up 3 test doubles (for example `a double assigned in a shared setup`) against 0 real object(s) of its own, and its only verification is 3 check(s) that the doubles were called. It pins how the code is wired, not what it does: it passes with a wrong result and fails when a call is harmlessly reordered or merged. Assert the outcome instead (the value returned, the state left behind), build collaborators and value objects for real or with a small hand-written fake, and keep doubles for the boundaries the test cannot own — the network, the clock, the file system.
Mock-dominated test: proceeds with cleanup when the thread is owned by the user packages/api/src/features/agent/service.test.ts:1365— This test sets up 10 test doubles (for example `vi.fn`) against 0 real object(s) of its own, and its only verification is 8 check(s) that the doubles were called. It pins how the code is wired, not what it does: it passes with a wrong result and fails when a call is harmlessly reordered or merged. Assert the outcome instead (the value returned, the state left behind), build collaborators and value objects for real or with a small hand-written fake, and keep doubles for the boundaries the test cannot own — the network, the clock, the file system.
Mock-dominated test: $name apps/web/src/features/resume/builder/draft.test.ts:688— This test sets up 5 test doubles (for example `vi.fn`) against 0 real object(s) of its own, and its only verification is 3 check(s) that the doubles were called. It pins how the code is wired, not what it does: it passes with a wrong result and fails when a call is harmlessly reordered or merged. Assert the outcome instead (the value returned, the state left behind), build collaborators and value objects for real or with a small hand-written fake, and keep doubles for the boundaries the test cannot own — the network, the clock, the file system.
Mock-dominated test: stops question playback and releases its audio when leaving Practise apps/web/src/features/career/workspace/workspace.test.tsx:421— This test sets up 7 test doubles (for example `vi.fn`) against 0 real object(s) of its own, and its only verification is 4 check(s) that the doubles were called. It pins how the code is wired, not what it does: it passes with a wrong result and fails when a call is harmlessly reordered or merged. Assert the outcome instead (the value returned, the state left behind), build collaborators and value objects for real or with a small hand-written fake, and keep doubles for the boundaries the test cannot own — the network, the clock, the file system.
Silent fallback default in catch apps/mobile/src/features/applications-board/calendar.ts:107— `weekStartsOn` swallows every exception into `return 1` — 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 apps/mobile/src/features/workspace/voice.ts:37— `readStored` 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 apps/mobile/src/features/write/picture-screen.tsx:35— `resolvePictureUrl` 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 apps/server/src/http/app.ts:55— `getTrustedClient` swallows every exception into `return "unknown"` — 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 apps/web/src/features/career/coach.tsx:85— `readOfferIds` 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 apps/web/src/features/career/offers.tsx:37— `readPair` 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 apps/web/src/features/career/workspace/debrief.tsx:255— `ReviewCard` 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 apps/web/src/features/career/workspace/practise.tsx:834— `useVoiceSettings` 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 apps/web/src/routes/dashboard/applications/index.tsx:306— `readDismissed` 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 packages/api/src/features/web-access/transport.ts:65— `normalizeSearch` 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.
Disabled test tests/e2e/specs/assistant.spec.ts:7— A test is skipped/ignored — coverage that looks present but never runs. Re-enable it or delete it so the green run means something.
Disabled test tests/e2e/specs/career.spec.ts:50— A test is skipped/ignored — coverage that looks present but never runs. Re-enable it or delete it so the green run means something.
Disabled test tests/e2e/specs/guest.spec.ts:5— A test is skipped/ignored — coverage that looks present but never runs. Re-enable it or delete it so the green run means something.
Blanket warning suppression apps/web/src/routeTree.gen.ts:1— A bare `eslint-disable` or `@ts-nocheck` with no rule list switches every lint rule or the whole type checker off for the rest of the file — hidden debt. Disable the specific rule on the specific line, with a justification, instead.
Blanket warning suppression apps/web/src/routeTree.gen.ts:3— A bare `eslint-disable` or `@ts-nocheck` with no rule list switches every lint rule or the whole type checker off for the rest of the file — hidden debt. Disable the specific rule on the specific line, with a justification, instead.
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.
C5 · Data-Subject Rights· Partial data-subject-rights support · ×1
Partial data-subject-rights support — Corroborated rights: erasure ✓ · export ✗ · consent ✗. Each tick means this scan found code in the repository implementing that right — a deletion/anonymisation path for erasure, a data-export or portability path for export, and consent state recorded alongside the personal data it authorises. A ✗ therefore means no such code was recognised HERE, not that the right is unsupported: a capability provided by a platform, a manual runbook, or code spelled in a way this scan does not match is not visible to it. Confirm before treating a cross as a gap; where it is one, the right has to be fulfilled manually.
No ADRs found — No ADRs found. The recognised ADR directories in this tree were read — `apps/web/src/features/resume/editor/proposals` — and none of their files is a decision record (a README, index or template page does not count). What was searched, so you can tell an empty log from a search that missed one: every directory under the tree (build output, dependencies and VCS metadata excepted), for a document that is either any non-index page inside a recognised ADR directory, whatever its name and however deeply nested (`docs/adr/use-postgres.md`, `docs/adr/2024/0001-x.md`); or a file anywhere whose name is ADR-shaped (`0001-use-postgres.md`, `adr-012-caching.md`); or, when neither turned anything up, a document carrying the decision-record signature (an "Architecture Decision Record" heading, or Status / Context / Decision / Consequences as section headings). A decision log that clears none of these — unnumbered files outside any recognised directory, without those headings — is not seen by this check and this row is then wrong. If that is your case, say so rather than renaming anything; otherwise, consider recording architectural decisions in `docs/adr/`.
D26 · Project Cohesion· Projects may be oversized for their cohesion · ×1
Projects may be oversized for their cohesion — 4 of 30 project(s) overshoot their size bounds, lowering Project Cohesion to 7.3/10. The most over is `apps/web` (58599 LoC, 376 module-visible types across 73 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.
D28 · Secrets (history)· Rotate the exposed credentials · ×1
No ADRs — No Architecture Decision Records found — no conventional ADR directory, no numbered `NNNN-title` documents in any markup this check reads, and nothing ADR-shaped by content. Design rationale recorded elsewhere (a design-notes tree, a mailing list, pull-request discussion) is not visible to this check and is not re-findable per decision, so a future maintainer cannot ask why one choice was made and get an answer.
Logging is not universal — Only 1/3 runnable modules use logging (modules with no entry point or server are excluded — they are libraries a runnable module hosts). Silent: `apps/mobile`, `tooling`.
No SAST — No static application security testing detected. For this repository's stack, add CodeQL's javascript-typescript pack, `semgrep --config=p/typescript`, or eslint-plugin-security as a CI step. What was searched, so you can tell an absence from a miss: the 51954 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.
R8 · Dependency Hygiene· Test-only dependency 'fflate' in production deps · ×1
Test-only dependency 'fflate' in production deps packages/api/package.json:67— Only test files import it (first: packages/api/src/features/documents/exports.test.ts:3) — move it to devDependencies.
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 14/18 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.
X5 · Nullable reference types· Strict null checking is not enabled everywhere the repository type-checks · ×1
Strict null checking is not enabled everywhere the repository type-checks — 2/9 of this repository's type-checking configuration(s) turn on strict null checking (`"strict": true`, or `"strictNullChecks": true`). A configuration that states neither is counted as OFF, because off is tsc's own default; a solution-style one whose `"files"` is empty and whose `"references"` point at other projects is in neither number, because it checks no source itself. Where it is off, `string` admits `null` and `undefined`: passing a value that is null compiles silently and throws on the first property access.
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.
semgrep: not applicable — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that. semgrep could not parse 109 file(s) — `apps/mobile/app/_layout.tsx`, `apps/mobile/src/features/applications/stages.ts`, `REDACTED`, `apps/mobile/src/features/search/search-screen.tsx`, `apps/mobile/src/features/settings/locale-names.ts`, … (+104 more) — so the PII/GDPR sweep did not cover the unparsed regions of them; rows reported elsewhere in those files are real.
runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here.
runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here.
runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here.
Run 01a178fa-6e9f-7371-b516-1ada9a8a9faa · every finding is also locatable in findings.md, and the complete scoring record (with exit codes + durations) in sidecar.json.
Issues: 99 · Warnings: 1276 · Recommendations: 68 — Appendix A · all findings · full markdown report.
Generated by Watchdog — deterministic code-health analysis. 26-10-2026 @ 16:10 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.