Public report of cameroncooke/AXe, published 15 November 2026. It has the same score, grades and number of
findings as the full report. The details of security findings (where they are in the code, which known
vulnerabilities and which passwords or keys were found) are left out, so nobody can use them against the project.
Public
Executive reportMeasured under the Code Assurance Index, an open standard for code quality, using its published scoring rules (rubric version 2026.11.4). Assert signed this survey and filed it in the standard's public register, where anyone can look it up by its survey ID. Check this survey →
Signed and filed in the standard's public register, 15 November 2026, 01:08 UTC · Survey ID cd_930eda5c8876400985ecba88067ea156
cameroncooke/AXe
Measured 15 November 2026, 01:07 UTC, at code version 61c4a27
CAI scoreAdequate
CriticalWeakAdequateStrongExemplary
Down 6 since the last survey
The score is built from these lenses. Each lens grades one area of the code, such as how easy it is to change or how well it is protected. The weakest lens counts most, so one weak area pulls the score down instead of being averaged away.
A medium codebase: 77,552 lines of product code in 6 projects, tests not counted · Estimated rebuild effort: about 0.8 person-years · Weakest lens: Code Health, 50
Findings by how serious they are
22 critical703 serious39 minor
21 dimensions are left out of the score. For each one, we either couldn't measure it in this code, or found no evidence of the safeguard we look for, such as a tested backup restore. They count neither for nor against the score, and Limitations lists each one with its reason.
This survey was produced by
Canine Code Analyzer
Producer
Canine Development
Analyzer
Canine Code Analyzer engine 1.0.0
Measured
15 November 2026, 01:07 UTC
A measurement, not a certificate. The Code Assurance Index records a number
together with the evidence it was worked out from, so anyone can recalculate it, but it doesn't certify or guarantee
the code. The standard was written by Canine Development, which also builds the Canine Code Analyzer. It is open to any tool that
implements it, and today the Canine Code Analyzer is the only one that does.
The score is deterministic, which means the same code always gets the same score. We work it out with tools that follow published rules, and an AI model never decides it, so anyone who applies the same rules to the same code gets the same number. How it is done is explained under Methodology ▸
56of 56 dimensions measured by tools.
751of 764 findings point to an exact file and line, so you can open each one in the code. The other 13 concern the repository as a whole, such as missing documentation.
56dimensions across 7 lenses, read from 77,552 lines of product code in 6 projects.
cameroncooke/AXe falls short of our standard for production, held back most by its Code Health lens, the quality of the code itself. It scores 55 out of 100 and is rated Adequate, and all 22 of its critical findings are security problems.
Code Health, at 50, is the weakest lens, level with Security and Compliance, and counts most in the score. The best first step is simplifying the most tangled functions, worth about 3 points. Fixing the three pipeline steps that put outside input straight into a shell command comes next, worth about 2 points. Raising Code Health to 70 would lift the score to about 59.
Fifteen pipeline tools are referenced by a changeable name, so the build pipeline can be tampered with. Three pipeline steps put outside input straight into a shell command, so an attacker can run commands in the build pipeline, and three secrets can leak from the build pipeline. Pinning each tool to an exact version, passing outside input through environment variables and limiting each secret to its own step would close these risks. The password or key in the code's history needs replacing, with the old one switched off.
The product code is 77,552 lines, about €120,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 Code Health rose from 50 to 70, the lowest score rated Strong, the score would rise from 55 to about 59.
Code composition: what the lines of code are
Product code 65%Tests 35%
New since the last survey: 676 findings
These 676 critical or serious findings weren't in the previous survey, on 29 October 2026. The first 100 are listed here, and the findings file in the download package lists them all.
We compare every finding with the previous survey's. A finding that has only moved to another line in the same file counts as the same finding, so only new findings appear here. Advisory notes from the AI model are left out, because the model words them afresh in every survey.
Fixed since the last survey: 38 findings
These 38 critical or serious findings were in the previous survey, on 29 October 2026, and are gone from this one.
€40,000 to €200,000, for 667 to 2,116 hours of work, about 0.8 person-years for 1 to 2 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.8 at a score of 55. Better code takes more work to write, so the factor is ×1.0 at a score of 70, lower below it and higher above it.
Size
Medium: 77,552 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: We price the hours a team would need to write this code again, at €60 to €95 an hour. Declarations and boilerplate are priced at a fast rate and logic at a slower one, and the logic is then multiplied by the difficulty of the problem and by the quality factor. The estimate can be about 30% off either way, and it moves most with the hourly rate and the difficulty. 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 6 finding(s) in Cyclomatic Complexity.
Add a SAST step to CI running what this repository's stack ships: CodeQL's Swift pack (Swift/Xcode) — or `semgrep --config=auto`, which runs on any language — so a security regression fails the build instead of landing.
Each conclusion below combines several dimensions into one point that no single dimension shows, and lists the measurements it rests on.
Where the investment is most exposed · Value at risk
This code would cost about €120,000 to build again, about 0.8 person-years of work. Its weakest lens is Code Health, at 50 (Weak). Code Health is about how easy the code is to read and change safely, and code that is hard to read is slow and risky to change, so every future change costs more than it should. Because the weakest lens counts most in the score, work on Code Health also moves the score most.
Based on: the rebuild estimate · the Code Health grade · how much each lens counts
What to do: Start with the Code Health actions in Top priorities.
If you do one thing first · First action
Resolve the 6 finding(s) in Cyclomatic Complexity. Of all the actions in this report, it raises the score most for the work it takes: about 3 points for medium effort, because it clears the 6 Cyclomatic Complexity 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.6 out of 10. Code at that level is slower to change than clean code, and we estimate the extra work at 6% to 13% on every change. The history of the code shows how much it changes: about 183,435 lines over the last 90 days, which is about 743,931 lines a year. At that pace, the extra work comes to an estimated 110.6 to 663.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 our 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 · Code Duplication · 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.
16 modules, with 5 dependencies between them. One loop runs through 3 of the modules, marked above the diagonal.
Which modules use which. The module on each row uses the module in each column, and the number counts the pairs of types that connect them. A cell above the diagonal is part of a loop.
32 pairs of types, where a type in AXeCore uses a type in repository. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
Findings mapped to OWASP categories; the specific CVEs/secrets are in the Security dimension cards below and findings.md (redacted only on the public version of this report).
OWASP category
Findings
Severity
A05:2025 — Injection
21
High / Critical
A03:2025 — Software Supply Chain Failures
6
Medium
A07:2025 — Authentication Failures
2
High / Critical
Roadmap
Top priorities: Resolve the 6 finding(s) in Cyclomatic Complexity; Add a SAST step to CI running what this repository's stack ships: CodeQL's Swift pack (Swift/Xcode) — or `semgrep --config=auto`, which runs on any language — so a security regression fails the build instead of landing; Bring the 54 bodies over 30 down to 30 or less in Cognitive Complexity — start with AgentModeRequest.validate (cognitive 322), SliderPickupReadPhase.run (cognitive 225), SelectedAXOperation.perform (cognitive 172).
Ranked by impact ÷ effort. "Helps" is the estimated gain on the 0–100 health score.
Do this
Helps
Effort
Dimension
Resolve the 6 finding(s) in Cyclomatic Complexity.
Add a SAST step to CI running what this repository's stack ships: CodeQL's Swift pack (Swift/Xcode) — or `semgrep --config=auto`, which runs on any language — so a security regression fails the build instead of landing.
Bring the 54 bodies over 30 down to 30 or less in Cognitive Complexity — start with AgentModeRequest.validate (cognitive 322), SliderPickupReadPhase.run (cognitive 225), SelectedAXOperation.perform (cognitive 172).
Bring the 12 bodies over 60 down to 60 or less in Cyclomatic Complexity — start with AgentModeRequest.validate (cyclomatic 300), SliderPickupReadPhase.run (cyclomatic 143), SelectedAXRequest.validate (cyclomatic 118).
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 — 22
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 — 703
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 — 39
Recorded, with no effect on how the codebase functions.
Present so the survey is complete, not because it needs doing.
Could not be resolved — 21
Something this survey could not settle
from the outside, and which could be critical or serious. Either a control was required and no
positive evidence of it exists in the repository — a backup job that nothing shows was ever restored from proves
nothing about restores — or our own analysis could not run over that part of the tree. This is not a clean
result. These are excluded from the score rather than awarded a pass, so the number on the cover neither
rewards nor penalises them: if you act on this survey without resolving them, you carry that risk yourself. Each
one is named under Limitations.
Methodology & how to trust this report
This survey is a deep, periodic assessment — run each sprint, monthly, or quarterly, taking the time to go wider and deeper than a quick check and surfacing in one coherent report what you'd otherwise piece together from a dozen separate tools. It scores deterministically: the same commit yields the same score, every run. All 56 evaluated dimensions are computed by tools and static analysis; no language model sets or judges any of them. Overall confidence is 0.9, the weighted average across measured dimensions.
Every figure here is one of two kinds, and we label which: ✓ Measured — a deterministic fact (LoC, complexity, coverage); ~ Modeled — an estimate from a stated model (cost, effort, value-at-risk), always a range with its assumptions, never a precise fact. We never present a modelled estimate as if it were measured. Perfect or absent scores carry their provenance too (ADR-0011): ✓ Tool-verified means the property itself was measured across the surface; ○ Nothing flagged means the probes came back clean — a claim bounded by what a repository can show; ⊘ Not evidenced means a working control (a tested restore, an automated rollback) showed no positive evidence — absence of evidence is not evidence of a control, so it's excluded from the score rather than awarded a spurious 10.
What we checked — 56 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, 751 of 764 do; the remainder are repo-wide signals — a dimension-level measurement, not a single line. (Every path in this report is repo-relative by construction: paths are normalized at the producer and the report is rejected if any rooted path leaks through.)
Is there a tool behind the number? Every score below names the method that produced it: Roslyn, git or a scanner, not a narrative.
Does re-running give the same result? Run it again on the same commit and the score — and this report, byte for byte — is identical. A report whose numbers move between runs is describing the run, not the code.
This report answers yes to all three. That's the bar to hold any assessment to.
Tools & methods
The actual versions used this run (captured at analysis time) — re-run on the same commit for the identical score.
Method
Backs
Version
Evaluator
Roslyn static analysis
Complexity, cohesion, coupling, dead code, API surface, layering
What ran differently this time — a tool absent, degraded, or that fell back to an estimate. Named openly, not folded silently into the scores. A degraded run also records its exact cause in diagnostics.md.
D8 Code Coverage — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Coverage NOT MEASURED: the Swift half could not be measured — the Swift suite in . produced no coverage export. Coverage is excluded from the score rather than counted as a near-zero. This is OUR limitation, not a defect in the repo.
D10 Test Quality — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. The 1,509 test(s) behind this row are the ones the code-model census could read, and this repository also carries at least 22 test source file(s) (.py, .rb) that it cannot: it reads the test types the .swift frontend declared, so a suite in any other language is invisible to it. Skipped tests, zero-assertion tests and the other quality signals on this row are UNMEASURED in that suite — their absence from the counts above is a gap in this analyzer's language coverage, not a finding that those tests are sound.
D11 Test Reliability — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Test source is present (.py, .swift, .rb) and this repository declares a SwiftPM test suite (AXe), but it was not re-run: no test result was produced. Not scored — this is a gap in the analyzer's language coverage, not a finding about this repository.
D14 License Compliance — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. This repository declares a Python pyproject.toml/requirements.txt (pip/uv/Poetry), but the licence verdict published here was taken over its SwiftPM package dependencies. Nothing was read about its Python dependencies' licensing in either direction, and a clean score on this card must not be read as covering them.
D14 License Compliance — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. This repository declares package.json, but the licence verdict published here was taken over its SwiftPM package 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 (11 contributor(s) across 632 commit(s) sampled, automation and bot accounts excluded). One of them holds 95% of the history; the other 10 hold 0.5% 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.
D21 Naming Consistency — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. D21's naming rules read C# through Roslyn and every other language through its sidecar model; these languages are left out (PHP's reading is its own change, a Roslyn-loaded VB or F# project has no population builder yet). Their declarations carry no naming verdict this run — this says nothing about whether their names are consistent.
D21 Naming Consistency — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. PREREGISTRATION version 20's fallback (adjudication D21-sample3-v3): this rule kind was adjudicated below the 95 % precision gate, so its candidates are counted here and not published, and the score covers only the acronym-spelling and awaitable-suffix rules. The kind returns as rows only after it shows a measured precision; this says nothing about whether these names are consistent.
D21 Naming Consistency — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. PREREGISTRATION version 20's fallback (adjudication D21-sample3-v3): this rule kind was adjudicated below the 95 % precision gate, so its candidates are counted here and not published, and the score covers only the acronym-spelling and awaitable-suffix rules. The kind returns as rows only after it shows a measured precision; this says nothing about whether these names are consistent.
D22 Internal API Consistency — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. D22's deterministic call-shape rules are gated on C# first (docs/plans/deterministic-engine.md, P5): each other language is switched on only after its own concept suite and A/B gate pass. This says nothing about whether that surface is consistent.
D24 Comment Value — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Each source language's comment syntax, and the code a comment annotates in it, needs its own proof before D24 judges it. Until then those comments are left unread, not counted as clean.
D32 Data Compliance (PII/GDPR) — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. `AxePlaygroundApp/AxePlayground/ContentView.swift`, `AxePlaygroundApp/AxePlayground/Views/TouchControlView.swift`, `Packages/IDBKit/FBControlCore/Async/AsyncFBFutureBridge.swift`, `Packages/IDBKit/FBControlCore/Configuration/FBiOSTargetConfiguration.swift`, `Packages/IDBKit/FBSimulatorControl/Commands/FBAXOpaqueFrameTapAdmission.swift`, … (+33 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.
D44 Platform End-of-Life — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This dimension reads a project's own statement about the platform it runs on: a TargetFramework in a .NET project file, a .nvmrc or .python-version, a capped requires-python, a Rust toolchain file or Cargo.toml rust-version, a .go-version, .java-version, .ruby-version, .tool-versions or .sdkmanrc, a go.mod go directive, a Maven or Gradle Java level or toolchain, a Gemfile's ruby directive, a mix.exs elixir requirement, a rebar.config minimum_otp_vsn, a pubspec.yaml SDK constraint, a build.sbt scalaVersion, or a framework major pinned by a dependency constraint. This repository carries none of them, so nothing about its platform was established. That is a gap in this analyzer's coverage, NOT a finding that the platform is supported — a language whose runtime is declared elsewhere (Package.swift, a Dockerfile) is simply not read here yet.
AX1 Captive dependencies — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads Microsoft.Extensions.DependencyInjection registrations in C# and Spring beans in Java/Kotlin only, and this repository defines its own container in Packages/IDBKit/FBControlCore/Commands/FBTargetCommandCache.swift, whose lifetimes are not modelled yet, 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.
AXB1 Runtime evidence locked — no reproducible boot — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Subject: 4 markup document(s) — HTML, Razor, JSX, Vue, Svelte or server templates. The Runtime Evidence tier boots an app only via docker-compose, an Aspire AppHost, a Dockerfile, an npm dev script, a web service's own toolchain entry point (cargo, go, dotnet, Python, Spring Boot), or an Android app's own Gradle wrapper (run on an emulator); an Apple or Flutter app needs a host it lacks. None applied, so no live runtime a11y/egress/header evidence was collected. You can widen what we reach: add a docker-compose.yml (or an Aspire AppHost) that brings the app up with its dependencies. We then boot it in an isolated sandbox and gathers real runtime evidence — you change nothing in your pipeline (no CI step, no SDK).
C1 Data Protection — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These personal data controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks personal data controls.
C2 Access Controls — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These authorization controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks authorization controls.
C3 Audit Trail — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These audit controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks audit controls.
C4 Data Retention — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These retention controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks retention controls.
C5 Data-Subject Rights — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These data-subject rights controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks data-subject rights controls.
GD1 Unfinished & placeholder code — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, F#, JavaScript/TypeScript, Dart, Ruby and Scala source only, and this repository's Swift, c, objectivec is most of its product and is not read yet, 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.
IC1 Incompleteness & stubs — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, JavaScript/TypeScript, Java, Dart, Ruby and Scala source only, and this repository's Swift, c, objectivec is most of its product and is not read yet, 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.
M4 Documentation accuracy — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. M4 checks only the claim kinds adjudicated at or above 95 % precision: links and versions (PREREGISTRATION version 9), and artefact counts an order of magnitude off. Paths, command arguments, installs, environment variables, settings, projects, packages, routes, cd targets, infrastructure products and removed modules are read but not checked, and none of them is reported or counted.
P5 DR & Backup — not measured this run — This is a true statement about the repository that carries nothing for its owner to act on, so it is reported here rather than as a defect in their code. No backup/snapshot/replication config, RTO/RPO or restore-procedure documentation was found — and no production persistence was detected either (no data-access packages, no data-store services, no database resources), so there is nothing in this repository whose loss a DR control would recover. If this system's data lives in a platform or ops repo we can't see, that's where the DR evidence belongs.
S1 Web-Security Posture — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These web-security controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks web-security controls.
X12 Unreachable branch — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check's reader does not cover most of the languages this repository's product is written in. What it read is kept, but it is too small a share to grade the product by. That is a gap in this analyzer's language reach — not a finding about this repository.
X16 Unfloored truncation loop — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check's reader does not cover most of the languages this repository's product is written in. What it read is kept, but it is too small a share to grade the product by. That is a gap in this analyzer's language reach — not a finding about this repository.
X2 Cancellation propagation — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Go, PHP, Dart, Kotlin, Ruby, Scala, Java, Python and Rust source only, and no C# was loaded, and no named async function in this repository's JavaScript/TypeScript, nor any Go, PHP or Dart function or Kotlin suspend function, makes a request that can be cancelled (fetch, axios, ky, ofetch, got, undici, node:http; net/http, net.Dial; amphp; Dio; Ktor, OkHttp), so there is nothing to judge, 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.
X27 Collection changed while being enumerated — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and Java, Rust, Erlang, F#, Python, Dart, Ruby, Scala and Kotlin source only, and no C# was loaded, no Java, Rust, Erlang, F#, Python, Dart, Ruby, Scala or Kotlin was found, and this repository's Objective-C, Swift (Foundation mutable collections) is not read yet, 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.
X4 Structured logging — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Java, Kotlin, Python, PHP, Dart, Ruby, Scala and Rust source only, and no C# was loaded, and this repository's JavaScript/TypeScript, Python and PHP make no call through a named logger, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
Repo exclusion declarations (.gitattributes linguist-generated/vendored, .editorconfig generated_code): none declared — every source file was scored.
Limitations & what we did not check
We assess the repository exactly as committed, and only the repository. By design we do not reach outside the source tree: the live cloud account, the running CI/CD pipeline, the host's branch-protection and approval rules, the production configuration, or a restore actually exercised against a backup are all out of scope. That boundary is a feature, not a gap — a repo-relative, deterministic scan re-runs identically on any commit and every finding opens at a real file and line, where a live audit can neither be reproduced nor traced. The visible consequence is that controls which leave no in-repo evidence are reported as "not evidenced" and excluded from the score rather than awarded a number a static scan cannot justify.
Per-dimension blind spots
For each dimension that was measured, what a static, repo-only scan structurally cannot see — the honest edge of the measurement, not a failure of it.
D1 Cyclomatic Complexity: Cyclomatic complexity counts branches statically — it cannot tell an essential decision tree from accidental tangle, nor see complexity that lives in data or configuration (large switch-case token tables, DSL lexers/parsers, data-as-code rule tables) rather than control flow: a tokenizer's many single-character cases read as high complexity though each branch is trivial.
D2 Cognitive Complexity: Cognitive-complexity heuristics approximate how hard code is to follow; genuine domain difficulty and well-named intent that eases reading are not captured.
D3 God Classes: "God class" is sized by members and responsibilities visible in the type — a deliberately broad facade over a coherent subsystem can read the same as an accidental grab-bag. For front-end JS the file-length check is cohesion-aware (a single-responsibility module — one class/IIFE — earns a 3× threshold), but cohesion is approximated from top-level declarations, not true dependency structure.
D4 Code Duplication: Duplication is token-similarity — an in-process token-stream comparison over sliding windows, with type-aware normalization — so it finds copy-paste, not semantic duplication expressed differently. Committed machine-written code (scaffolded migrations, designer/codegen output, protobuf/OpenAPI stubs, model snapshots) is EXCLUDED — its repetition is the tool's, not the team's — so the score reflects hand-written duplication only.
D5 Coupling: Coupling is measured between projects/assemblies — runtime coupling through DI, reflection, messaging or shared databases is invisible to a static reference graph.
D6 Cohesion (LCOM4): LCOM4 cohesion is syntactic — it infers connectivity from which methods touch which fields/methods by name, not from real runtime behaviour or intent.
D10 Test Quality: Assertion density is structural — it cannot tell a meaningful behavioural assertion from a trivial one, only that an assertion is present.
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 checks the structure of the decision records present: it cannot know about decisions made and never recorded, and it does not judge how well a record argues its case. Records in a language the section lexicon does not cover are not evaluated.
D21 Naming Consistency: Naming consistency compares each name with the convention its structural peers follow in this repository: it cannot tell whether a consistently used name is a good one, and languages other than C# and TypeScript are not measured.
D26 Project Cohesion: Project focus is sized from members/namespaces per project — a project that is broad by deliberate design reads the same as one that has sprawled.
D27 Navigability: Indirection/navigability is structural — it measures hops to follow a call, not whether that indirection buys real flexibility or just ceremony.
D28 Secrets (history): Secret-history scanning sweeps the git log for known patterns — a secret that predates the available history, or never matched a signature, is not found (clean means "nothing matched in the history we can see").
D29 Static Analysis (SAST): SAST findings are pattern-based (semgrep) — it finds classes of bug it has rules for; logic flaws, auth/authorization gaps and issues needing runtime context are out of reach (and clean means "no rule matched").
D30 Dependency Vulnerabilities: CVE matching depends on accurate package/version metadata and on the advisory databases — a vulnerability with no published advisory, or in code not declared as a dependency, is not seen. Coverage needs a RESOLVED graph: an unpinned requirements.txt, or a pom without a resolved build, yields partial coverage rather than a clean verdict. An ecosystem the analyzer cannot scan is reported as unmeasured, never as clean.
D34 Knowledge Freshness: Freshness is decayed commit RECENCY, not comprehension — code read often but rarely committed reads as orphaned, and stable code that genuinely needs no changes is penalised the same as forgotten code; bot/squash commits distort it like the bus factor.
D35 Change Coupling: Change coupling is co-change in COMMITS — files split across separate commits, or coupled only through a shared config/build step, read as uncoupled, and a sweeping commit (rename/format) is excluded so it doesn't couple everything. It shows that files change together, not WHY: a high coupling can be a healthy cohesive pair as readily as a hidden leak.
D43 Malicious Dependencies: Only packages some vulnerability database has already NAMED as malicious are seen — a compromise published in the last hours, or never reported at all, is invisible here, and this dimension reading 10 is not evidence that a dependency is trustworthy. There is no typosquat or dependency-confusion analysis: a package nobody has reported is simply absent from the feeds. Coverage is the dependency scan's: an ecosystem that could not be scanned is disclosed as unmeasured, never as clean.
AC6 Visual & motion safety: Contrast and motion safety are PARTIAL by construction — literal colours (hex/rgb/hsl/named) in inline styles, in-repo <style> blocks, in-repo .css files, var() tokens, Tailwind neutral utilities and CSS-in-JS top-level declarations are read (same-rule/same-element colour+background pairs only); computed/runtime/theme colour, external-CDN stylesheets, CSS-in-JS dynamic (${…}) and nested-selector colours, cross-element pairs and image contrast stay out of reach, so a clean result is bounded by what the static CSS itself shows.
AX10 Code composition: Role is inferred from namespace/folder convention, not semantics — a domain concept living in a folder named "Services" reads as application, and the split is lines-of-code, not business value. The business-logic-share score is a SOFT, FLOORED signal: it contributes to the Architecture lens but is floored at the Critical gate, so an infrastructure-heavy design (a gateway, an ETL, a driver) is legitimately low without being nuked to zero.
AX9 CQS / query purity: Handlers are found by interface/name convention — a query handler using neither is not seen. Mutation is a resolved write/publish invocation (SaveChanges/repository/bus), so a write hidden behind a hand-rolled wrapper, reflection, or a string-keyed service locator resolves to a non-persistence type and isn't flagged; it detects that a query writes state, not whether the write is a legitimate read-side cache update. Clean means "no resolved write/publish in a query body", not a proof of CQS purity.
M4 Documentation accuracy: Documentation accuracy checks links, versions and artefact counts against the tree: other claims (paths, commands, settings, routes) are read but not checked, and it cannot run the onboarding or measure how long a real new joiner takes.
P4 Deployment & Rollback: Approval/branch-protection rules live in repository settings the scan cannot see — only their in-repo evidence (config files, workflows) is checked, so a control enforced purely in the host's settings reads as "not evidenced".
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.
138 method(s) exceeded the cyclomatic complexity threshold of 15; the worst was AgentModeRequest.validate at 300. A further 5 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 KeyEvent.keyCodeForString at 99 — they are counted neither in the figure above nor in this dimension's score. 3 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: Sources/AXe/Types/KeyCode.swift (KeyEvent.keyCodeForString at 99), AxePlaygroundApp/AxePlayground/ContentView.swift (ContentView.destinationView at 29), AxePlaygroundApp/AxePlayground/Views/KeyPressView.swift (KeyCaptureUIView.getKeyInfo at 29). 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.
+ 133 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Bring the 12 bodies over 60 down to 60 or less in Cyclomatic Complexity — start with AgentModeRequest.validate (cyclomatic 300), SliderPickupReadPhase.run (cyclomatic 143), SelectedAXRequest.validate (cyclomatic 118). — 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 12 together lifts Cyclomatic Complexity from 2.0 to about 4.2/10, projected with the scoring formula itself and assuming each lands exactly at 60; a cleaner split scores higher.
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.
+ 170 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Bring the 54 bodies over 30 down to 30 or less in Cognitive Complexity — start with AgentModeRequest.validate (cognitive 322), SliderPickupReadPhase.run (cognitive 225), SelectedAXOperation.perform (cognitive 172). — 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 54 together lifts Cognitive Complexity from 2.0 to about 5.6/10, projected with the scoring formula itself and assuming each lands exactly at 30; a cleaner split scores higher.
Detailed fixes: d2_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D3 · God Classes8.9 / 10Strong✓ Tool-verified
What it measures: Over-large classes that try to do too much ("god classes").
Method: God-class detection by line and method-count thresholds per logical type (partial classes unified), filtered for generated code and registration/contract false positives. Deterministic.
Resolve the 14 MethodTooLong finding(s) in God Classes — start with SelectedAXOperation.swift, SliderPickupReadPhase.swift, SimulatorAgentRunner.swift. — One of this dimension's main actionable groups (14 warning-level).
Resolve the 5 FileTooLong finding(s) in God Classes — start with scenes.tsx, RuntimeSnapshot.swift, AgentPolicy.swift. — One of this dimension's main actionable groups (5 warning-level).
Resolve the 5 ClassTooLong finding(s) in God Classes — start with AgentModeController.swift, SelectedSliderValueOperation.swift, SelectedHIDOwner.swift. — One of this dimension's main actionable groups (5 warning-level).
Detailed fixes: d3_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: How much of the production code is copy-pasted: the share of production lines inside a reported copy (every copy of a duplicated block or of an edited member, each line once), 10 at none and 0 at a quarter of the lines.
Method: Code duplication via token-stream sliding windows with type-aware normalization (locals masked, type names preserved), scored on the share of production lines inside a reported copy (each line once; 10 at none, 0 at a quarter). Deterministic.
57 duplicated block group(s) detected. 2.7 % of the production lines (2,106 of 77,552) are in a reported copy. A further 58 rows report members as variants of one another; the share counts each copied line once, however many rows cite it. 12 of the 115 are in trees this repository does not ship — vendored, example/demo, project-template, fixture and benchmark code — and are ranked below the shipped groups rather than excluded from them: the duplication there is real and is still counted in this dimension's score. The dimensions that publish a production-file census leave those trees out of theirs, so this count is deliberately drawn over the wider population.
Edited copy of a member (6 corresponding lines) · ×6Sources/AXe/Utilities/AgentModeSnapshot.swift:248
Edited copy of a member (7 corresponding lines) · ×5Sources/AXe/Utilities/SliderValue/SliderPickupReadPhase.swift:26
Edited copy of a member (3 corresponding lines) · ×5Sources/AXe/Utilities/DeviceStateOutput.swift:121
+ 50 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Resolve the 10 Duplicated block (5 lines × 2) finding(s) in Code Duplication — start with AccessibilityFetcher.swift, AgentModeController.swift, SelectedVideoRecording.swift. — One of this dimension's main actionable groups (10 warning-level).
Resolve the 7 Duplicated block (6 lines × 2) finding(s) in Code Duplication — start with PhysicalDeviceMedia.swift (2), Slider.swift, PhaseTiming.swift. — One of this dimension's main actionable groups (7 warning-level).
Resolve the 6 Edited copy of a member (6 corresponding lines) finding(s) in Code Duplication — start with AgentModeSnapshot.swift, AgentModeController+Batch.swift, DuoControlsTouchObserver.swift. — One of this dimension's main actionable groups (6 warning-level).
Detailed fixes: d4_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D5 · Coupling8.7 / 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.
6 production modules (npm+SwiftPM+XcodeGen), 0 dependency cycle(s), 0 unstable depended-on module(s). Read from the build's own module declarations; an XcodeGen target's dependency on a local Swift package or on a target of another project is not visible there; 1 module(s) off the main sequence, with abstractness counted on 4 of the 6 (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: AXeCore
What to do
Resolve the 1 Off the main sequence finding(s) in Coupling. — One of this dimension's main actionable groups (1 warning-level).
Detailed fixes: d5_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether a class's methods are focused on a single responsibility.
Method: LCOM4 cohesion per production class with at least two methods: connected components of methods sharing state or calls, computed syntactically. Deterministic, not a proxy.
Coverage: Exhaustive · type-level: LCOM4 cohesion computed over every production class — the population is all types, not a name convention.
Resolve the 2 Low cohesion finding(s) in Cohesion (LCOM4) — start with DuoControlsTargets.swift, KeyPressView.swift. — One of this dimension's main actionable groups (2 warning-level).
Detailed fixes: d6_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D10 · Test Quality8.5 / 10Strong✓ 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.
11 skipped (11 with a documented reason), 150 zero-assertion, no mocking-framework packages referenced (hand-written doubles or no mocking) across 1509 tests. Measured on the .swift suite only — at least 22 test source file(s) (.py, .rb) went unread, so its test quality is unmeasured and is not in these counts.
No assertions: inertAdditionsKeepTheLayout · ×150Tests/AgentBatchReferencePlanTests.swift:187
Resolve the 150 No assertions finding(s) in Test Quality — start with PlaygroundDuoCoreTests.swift (20), PlaygroundAgentSelectorTests.swift (9), PlaygroundOrdinaryInputTests.swift (9). — One of this dimension's main actionable groups (150 warning-level).
Detailed fixes: d10_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether dependencies are current, not deprecated, and not bloated. Known vulnerabilities are D30's.
Method: Manifest scan via dotnet list package across all projects; worst-signal-per-package deduction (capped-linear for deprecation, prerelease and outdated) per KLoC. Known-vulnerable packages are D30's and are not charged here (rubric-2026.11.2). Exhaustive.
1 outdated direct SwiftPM dependencies, 0 pinning defect(s). SwiftPM has no package registry: a dependency is a repository URL and its releases are that repository's semver tags, so currency is answered by listing tags rather than by querying an index. Only a newer tag on the SAME MAJOR is reported — a `from:` requirement admits everything below the next major and nothing above it, so a major crossing needs a Package.swift edit rather than an update, and naming the update as its remedy would be wrong. Whether any dependency is DEPRECATED or ABANDONED is not graded and cannot be: a repository publishes no such marker, and there is no registry that could carry one. Known CVEs in this dependency graph are D30's question.
Outdated: swift-argument-parser
✓ On the Gold path — maintain.
Detailed fixes: d12_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether any secrets (keys, tokens, passwords) have leaked into the code.
Method: In-process native secret scanner (entropy plus signature patterns) across all tracked files; no external tool. A clean result is a measured 10, not no-data zero. Deterministic.
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 1 SwiftPM package(s) use a banned license. SwiftPM has no package registry, so each package's licence is the one its repository declares: 1 of them read from the licence file the repository carries at the revision Package.resolved pins, and 0 — unpinned, or whose licence file could not be read or named — from api.deps.dev, which reports the licence the repository declares today. Graded: every package a committed Package.resolved pins, direct and transitive, and every declared dependency none pins. ★ COVERAGE OF THIS VERDICT: it grades this repository's SwiftPM package dependencies and nothing else. The repository also declares a Python pyproject.toml/requirements.txt (pip/uv/Poetry) and package.json, and the licences of those dependency graphs 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: Sources/AXe/Utilities/AgentModeProtocol.swift (21×300=6300); Sources/AXe/Utilities/SelectedHIDProtocol.swift (31×101=3131); Sources/AXe/Utilities/SelectedHIDOwner.swift (30×70=2100) Repeated repair below the complexity floor: Sources/AXe/Utilities/ScrollUntil.swift (4 of 4 changes were fixes); Sources/AXe/Utilities/DeviceStateOutput.swift (4 of 4 changes were fixes); benchmarks/preparation.py (3 of 4 changes were fixes)
Resolve the 52 Hotspot finding(s) in Churn × Complexity Hotspots — start with AgentModeProtocol.swift, SelectedHIDProtocol.swift, SelectedHIDOwner.swift. — One of this dimension's main actionable groups (52 warning-level).
Resolve the 4 Repeated repair finding(s) in Churn × Complexity Hotspots — start with ScrollUntil.swift, DeviceStateOutput.swift, preparation.py. — One of this dimension's main actionable groups (4 warning-level).
Detailed fixes: d15_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Acknowledged debt left in the code — TODOs, dead code, suppressed warnings.
Method: Roslyn syntactic debt markers (suppressions/TODO/FIXME/HACK/empty-catch/commented-code/Obsolete) plus SymbolFinder dead-code analysis; weighted-debt-per-KLoC density deducted 2.0x per unit. Deterministic, exhaustive.
0 deducted task-comment markers across 77552 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. 11 document(s) read across 2 unit(s).
✓ On the Gold path — maintain.
Detailed fixes: d19_recommendation.md.
Do you agree with this assessment?
D20 · ADR Quality0.0 / 10Critical✓ Tool-verified
What it measures: Whether architecture decisions are recorded well (context, decision, consequences).
Method: Every ADR read by its section structure: nine located rules (a missing Decision, Context or Consequences section, a stale status, two records deciding the same question, a dangling supersede link, a number-only title, a single option, no named cost, no status where the log uses one, no enforcement field where the log adopted one), each a fixed deduction from 10; the score is the mean over evaluated records. Deterministic, no model. Advisory.
Resolve the 1 No ADRs found finding(s) in ADR Quality — start with Package.swift. — One of this dimension's main actionable groups (1 recommendation-level).
Detailed fixes: d20_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether names — types, methods, variables — are clear and consistent.
Method: Seven vocabulary-free rules (N1-N7) mine each naming convention from the repository and flag a name that breaks a convention its structural peers in the same unit follow; production C# and TypeScript, each its own population. Deterministic, no model, no sample. Advisory.
9 naming inconsistencies among 433 declarations measured against a convention their peers follow.
`axTranslationPid` spells `Pid` where 183 names in the project spell it `PID` · ×2Packages/IDBKit/FBSimulatorControl/Commands/FBAXPlatformElement.swift:51
`frontmostPid` spells `Pid` where 183 names in the project spell it `PID` · ×2Packages/IDBKit/FBSimulatorControl/Commands/FBAXTranslationRequest.swift:183
`displayId` spells `Id` where 247 names in the project spell it `ID`Packages/IDBKit/FBSimulatorControl/HID/FBSimulatorNativeContextReader.swift:320
`uniqueId` spells `Id` where 247 names in the project spell it `ID`Packages/IDBKit/FBSimulatorControl/HID/FBSimulatorNativeContextReader.swift:321
`AXUniqueId` spells `Id` where 247 names in the project spell it `ID`Sources/AXe/Utilities/AccessibilityElement.swift:38
+ 2 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Resolve the 2 `axTranslationPid` spells `Pid` where 183 names in the project spell it… finding(s) in Naming Consistency — start with FBAXPlatformElement.swift (2). — One of this dimension's main actionable groups (2 recommendation-level).
Resolve the 2 `frontmostPid` spells `Pid` where 183 names in the project spell it… finding(s) in Naming Consistency — start with FBAXTranslationRequest.swift (2). — One of this dimension's main actionable groups (2 recommendation-level).
Resolve the 1 `displayId` spells `Id` where 247 names in the project spell it `ID` finding(s) in Naming Consistency — start with FBSimulatorNativeContextReader.swift. — One of this dimension's main actionable groups (1 recommendation-level).
Detailed fixes: d21_recommendation.md · top locations in Appendix A, every location in findings.md.
1 of 4 build units (SwiftPM, XcodeGen, 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: How far you must trace to follow a call — low indirection and co-located slices read easier.
Method: Call indirection (interface hops, cross-namespace calls, slice-locality scaled) over a sampled set of method invocations, size-aware baseline. Sampled; confidence discounted by symbol-resolution gaps. C# also names each pass-through layer (a class whose every public method only forwards its own parameters to one collaborator) as a located finding; the score is not affected.
Coverage: Slice locality from the first namespace segments, SAMPLED (≤400 methods) — not exhaustive.
2 % of calls cross a namespace and 1 % go through an interface, but 100 % of collaborators are co-located — so a call's collaborators sit together and tracing stays easy. Baseline: small — navigation cost is tolerated.
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.
1 finding(s): 0 critical, 1 high, 0 medium, 0 low. Remediation for historically-committed secrets is credential rotation — they remain in history regardless of later deletion.
REDACTED
REDACTED
What to do
Resolve the 1 REDACTED 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).
21 finding(s): 0 critical, 21 high, 0 medium, 0 low. 15 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 11 file(s) — `Packages/IDBKit/FBControlCore/Processes/FBProcessFetcher.h` (line 12, line 14, line 23, …), `Packages/IDBKit/FBControlCore/Utility/FBControlCoreFrameworkLoader.h` (line 10, line 11, line 21, …), `Packages/IDBKit/PrivateHeaders/CoreSimDeviceIO/SimDisplayIOSurfaceRenderable-Protocol.h` (line 31, line 42, line 47, …), `Packages/IDBKit/PrivateHeaders/CoreSimulator/SimDevice.h`, `Packages/IDBKit/PrivateHeaders/CoreSimulatorUtilities/NSArray-SimArgv.h` (line 17, line 19, lines 19–20, …), … (+6 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
What to do
Resolve the 3 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (3). — One of this dimension's main actionable groups (3 issue-level).
Resolve the 2 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED, REDACTED. — One of this dimension's main actionable groups (2 issue-level).
No action in Static Analysis (SAST) — all 15 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 (15 issue-level, 0 of them charged here).
Detailed fixes: d29_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether any dependency has a known published vulnerability (CVE), direct or transitive, in ANY ecosystem the repository declares — Dart pub, Elixir and Erlang via Hex, Go modules, Java and Kotlin via Maven/Gradle, JavaScript/npm, .NET/NuGet, PHP/Composer, Python/PyPI, RubyGems, Rust/Cargo and Swift.
Method: Dependency-CVE scan across every ecosystem the repository declares, scored ONCE. Three sources are unioned and deduplicated by advisory identity (rule id + alias closure, CVE<->GHSA) scoped to package+version, keeping the worst severity: `osv-scanner --recursive` over osv.dev for Dart pub, Elixir/Hex (and Erlang, whose `rebar.lock` syft first converts to a CycloneDX SBOM the scanner reads, with rows attributed back to the lock), Go, Java and Kotlin via Maven/Gradle (and Scala, whose sbt build's pinned direct declarations are written into a CycloneDX SBOM the scanner reads, with rows attributed back to the build file), npm, PHP/Composer, Python/PyPI, RubyGems, Rust/Cargo and Swift; `trivy fs --scanners vuln` for npm lockfiles; and `dotnet list package --vulnerable --include-transitive` for NuGet (with per-advisory collapse of the project x target-framework fan-out), plus a DECLARED-dependency arm that resolves a published gem's gemspec against rubygems.org where no Gemfile.lock is committed. `SeverityScore(c,h,m,l, normalizer 8.0)`. NotApplicable only when NO ecosystem is readable; if any applicable ecosystem could not be scanned the findings are REPORTED and the score is withheld. Supersedes the npm and OSV arms, retired 2026-09-05. Advisory since rubric-2026.11.2 (CAI decision 0006): every row is a match against a vulnerability database that changes daily, so the reading is shown and never moves a scored dimension, lens or the headline.
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 281 of the 333 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.
What it measures: Whether files that change together actually belong together — pairs that repeatedly co-change in git history despite having no explicit code dependency, surfacing the hidden/logical coupling (and boundaries in the wrong place) a static scan can't see.
Method: Pairwise co-occurrence over the per-commit file sets in git history (production source only — tests and generated dropped): Degree-of-Coupling = shared ÷ min individual revisions, reported above noise floors (each file ≥10 revisions, ≥5 shared commits, ≥50% strength); sweeping commits excluded. Deterministic over fixed history.
Coverage: Population: PRODUCTION source files only — test and generated files are dropped before pairing, so a class co-changing with its own test (trivially ~100%) can't drown the real production↔production coupling. Pairs ranked by Degree-of-Coupling. A non-source file is never a coupling PARTICIPANT either: documentation, schemas, config and data files are dropped with the rest, so a code↔docs pair — a command and the reference page that restates it — is not reported however strongly the two co-change; nor is coupling that runs THROUGH a build step or config file.
Resolve the 1 Change-coupling hub finding(s) in Change Coupling — start with Drag.swift. — One of this dimension's main actionable groups (1 warning-level).
Resolve the 1 Change coupling finding(s) in Change Coupling — start with Swipe.swift. — One of this dimension's main actionable groups (1 warning-level).
Detailed fixes: d35_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether the build pipeline provides supply-chain integrity — generated provenance/attestation, signed artifacts (cosign/sigstore), an SBOM, and pinned build actions. Presence of the configuration, not a runtime guarantee.
Method: Supply-chain provenance/signing read deterministically from CI/build config (.github/workflows, .gitlab-ci.yml, azure-pipelines, Jenkinsfile, .circleci) + the release surface: four signals — generated provenance/attestation (SLSA/in-toto/actions-attest), artifact signing (cosign/sigstore/gitsign), an SBOM (syft/sbom-action/*.spdx.json/*.cdx.json), and SHA-pinned build actions — scored 10·present/denom. NotApplicable without a build pipeline. Detects configuration presence, not runtime enforcement.
+ 1 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 warning-level).
Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing — start with REDACTED. — One of this dimension's main actionable groups (1 warning-level).
Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 warning-level).
Detailed fixes: d36_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether any dependency the repository declares is published as MALICIOUS rather than merely vulnerable — a package that is an attacker's work, in any ecosystem osv-scanner reads. Reported apart from D30 because the answer is binary: there is no safe version to upgrade to, and the fix is to remove the package and rotate every credential it could have read.
Method: The same dependency scan D30 reads, partitioned on the scanner's own classification rather than rescanned: a row is MALICIOUS when its id is in the `MAL-` space (the ossf/malicious-packages feed) OR its `database_specific.cwe_ids` carries `CWE-506` ("Embedded Malicious Code"). Both channels are structural; the summary text is deliberately NOT read, because a malicious-package record whose summary says only "Critical severity vulnerability" is a real shape ([GHSA redacted]) and a text matcher misses it. Scored BINARY: any surviving row is 0, whatever its severity and however many CVEs sit beside it — a hostile dependency is not a quantity. Applicability and degradation are D30's: NotApplicable only when no ecosystem is readable, and an unscannable ecosystem degrades rather than reading clean. Advisory since rubric-2026.11.2 (CAI decision 0006): the malicious-package feed is a database that changes daily, so the reading is shown and never moves a scored dimension, lens or the headline.
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.
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.
Other · Architecture — Whether the project-reference graph is acyclic (cycles block independent build/deploy and signal eroding boundaries).
Method: Project reference cycles via elementary-DFS over real .csproj references, using the engine shared with D5/D7; cyclic versus acyclic. Exhaustive, deterministic.
Other · Architecture — Whether dependencies point inward (Domain ← Application ← Infrastructure/Web) — the clean-architecture dependency rule, checked across the project graph.
Method: Layer violations by name-segment inference (Domain/Core to Application to Infrastructure/Web) over the project-reference graph. Exhaustive over all projects, deterministic.
Do you agree with this assessment?
AX8 · Test isolation10.0 / 10Exemplary✓ Tool-verified
Other · Architecture — Whether production projects stay free of references to test projects — tests may depend on production, never the reverse.
Method: Csproj graph: each production project checked for references to test projects (identified by test-framework presence, not name). Zero violations is clean. Deterministic.
Other · Architecture — Whether read (query) handlers stay side-effect-free — a query that writes persistent state or raises events breaks CQS and makes reads unsafe to retry, cache, or route to a read replica.
Method: Roslyn scan: CQRS handlers classified query-vs-command by interface (IQueryHandler/ICommandHandler/IRequestHandler<TQuery,TResult>) and name convention (*Query/Get*/Find* vs *Command); each query handler's body checked for persistent-state writes (SaveChanges/repository Add-Update) or event publishes by resolved invocation. Deterministic, type-level, exhaustive over the detected handlers.
Coverage: Population: CQRS handlers identified by IQueryHandler/ICommandHandler/IRequestHandler interface + *Query/Get*/Find*/*Command NAME convention; query purity then checked exhaustively within that set — a query handler using neither convention is invisible, and mutation is a resolved persistence/publish CALL, not full dataflow.
Maturity · Maturity — Whether the repository and its projects have a README, and whether it is substantive.
Method: Filesystem scan: README presence, word count, and headings for depth; git history for staleness. Exhaustive across root and project dirs, deterministic.
Maturity · Maturity — Whether key decisions (ADRs) and the high-level shape (C4/diagrams) are written down.
Method: Filesystem scan: ADR folder/naming conventions or content, plus Mermaid/PlantUML/C4/architecture.md discovery. Exhaustive, deterministic.
No Architecture Decision Records found — no conventional ADR directory, no numbered `NNNN-title` documents in any markup this check reads, and nothing ADR-shaped by content. Design rationale recorded elsewhere (a design-notes tree, a mailing list, pull-request discussion) is not visible to this check and is not re-findable per decision, so a future maintainer cannot ask why one choice was made and get an answer.
What to do
Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them.
Maturity · Maturity — Whether the repository is organised deliberately: production code and tests are set apart in a way its ecosystem or the repository itself declares.
Method: Filesystem scan: src/test folder separation and namespace-prefix consistency (majority RootNamespace agreement). Exhaustive across projects, deterministic.
Maturity · Maturity — Whether the project's current-state documentation describes the code that exists.
Method: Every current-state document's checkable claims looked up in the tree (links, versions, and artefact counts an order of magnitude off), plus two README checks: an advertised infrastructure product with no footprint, and a module the CHANGELOG records as removed. Deterministic, no model. Advisory.
Readiness · Readiness — Whether an automated pipeline builds and tests every change.
Method: Filesystem scan: CI workflow files (.github/workflows, .gitlab-ci.yml, etc.) for build and test stages. Exhaustive, deterministic.
Do you agree with this assessment?
P10 · Library API & versioning10.0 / 10Exemplary○ Nothing flagged
Readiness · Readiness — For a library: a deliberate (small) public API surface and explicit semantic versioning so consumers can depend on it safely.
Method: Roslyn scan: public API surface area and semantic-versioning markers (SemVer attributes, changelog entries) for libraries; off .NET, a library is the ecosystem's publication act (an npm package that is not private and names an entry point, a PyPI distribution with a build system, a Rust library crate, a Maven/Gradle module that publishes, a Go module with no package main, a gemspec, a Composer library, a SwiftPM library product, a pub.dev or Hex package), its surface is the share of types the language's code model records as public (Rust, Swift, Java, Kotlin, Go, Dart; not measured where the model records no type visibility or, as in TypeScript, only module-level export), and its version is read from the manifest, a semver CHANGELOG, release tooling or semver git tags. Exhaustive, deterministic.
Do you agree with this assessment?
P2 · Observability7.0 / 10Strong✓ Tool-verified
Readiness · Readiness — Whether the code is diagnosable in production — structured logging, tracing/metrics, health checks.
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 Swift pack (Swift/Xcode) (or `semgrep --config=auto`, which runs on any language) as a CI step. What was searched, so you can tell an absence from a miss: the 7 CI workflow file(s) in this repository, and the scanner and linter configuration checked in beside them. A scan that runs outside CI, one configured in your forge's web UI rather than in a committed file, or a tool whose name is none of those this check carries, is not seen — if that is your case the row is wrong, and saying so is more useful than adding a second scanner. — REDACTED:4
`promo-video/package.json` declares packages, and nothing in the repository keeps them current: no Dependabot or Renovate configuration that schedules updates, and no dependency-review gate on pull requests. A pinned dependency stays at the version it was added at until someone notices — including after an advisory is published against it. Add a `.github/dependabot.yml` with one `package-ecosystem` entry per ecosystem the tree uses (or an enabled `renovate.json`), and gate pull requests with `actions/dependency-review-action`. — promo-video/package.json:10
What to do
Add a SAST step to CI running what this repository's stack ships: CodeQL's Swift pack (Swift/Xcode) — or `semgrep --config=auto`, which runs on any language — so a security regression fails the build instead of landing.
Enable Dependabot/Renovate or a dependency-review gate.
Add gitleaks/trufflehog in CI to block PRs that introduce committed secrets.
Readiness · 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.
Readiness · Performance — Whether the code protects its performance with benchmarks — a benchmark suite, allocation/memory measurement, and (ideally) a CI gate. Presence is credited as a bonus, never a deduction.
Method: Repo + source scan: BenchmarkDotNet referenced (csproj/source), [Benchmark]/[MemoryDiagnoser] attribute counts, and a benchmark step in CI; off .NET, the same ladder over Go testing.B, Rust criterion/#[bench]/divan, JMH/kotlinx-benchmark, pytest-benchmark/asv/pyperf, tinybench/mitata/vitest bench/benchmark.js and Swift package-benchmark — scored as a bonus ladder (absence is neutral, never a deduction). Deterministic, presence detection.
Readiness · Performance — Whether asynchronous code stays responsive — it avoids sync-over-async blocking (a .NET .Wait()/.GetAwaiter().GetResult(), a time.sleep or blocking HTTP call inside a Python coroutine, a *Sync call inside an async JavaScript function, block_on inside a Rust async fn, runBlocking inside a Kotlin suspend function, block() inside a Reactor publisher) that stalls a thread or event loop and risks deadlock, and, where the code is a reusable library on .NET, awaits with ConfigureAwait(false) so it never captures and stalls its caller's context.
Method: Production-source scan: sync-over-async blocking counted everywhere — .Wait()/.GetAwaiter().GetResult() in .NET; off .NET, read from each language's code model, a blocking call inside an async function (Python, TS/JS, Rust, Kotlin, Swift, Dart) or inside a Java method returning a Reactor Mono/Flux or a Scala method returning a Future or effect — and, for a .NET library with ≥5 awaits, the share of awaits using ConfigureAwait(false). Deterministic, syntax/text detection.
`sleep` is async and calls sleep — a blocking call inside async code stalls the cooperative pool's thread — one per core — and every task scheduled on it for as long as it runs. — Sources/AXe/Utilities/Batch/PhysicalDeviceBatch.swift:46
`send` is async and calls .wait() — a blocking call inside async code stalls the cooperative pool's thread — one per core — and every task scheduled on it for as long as it runs. — scripts/fixtures/DuoExternalStateChange.swift:187
What to do
Swift: await instead of blocking — `try await Task.sleep(for:)` for Thread.sleep/sleep, a checked continuation instead of a DispatchSemaphore or DispatchGroup wait, the async Process and URLSession APIs; never park a thread waiting on a Task — the cooperative pool cannot guarantee it progress.
Do you agree with this assessment?
R1 · Type Safety6.2 / 10Adequate✓ 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.
5 typed · 3 plain JS — the untyped files are promo-video/make-music.mjs, scripts/generate-github-release-notes.mjs, scripts/release-context.mjs.
React / JS · Code Health — The share of the scored frontend lines inside a near-exact copy-pasted block of substantial extent (the D4 clone algorithm over JS/TS tokens, D-386; each line once, 10 at none and 0 at a quarter of the lines, as D4): 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. Scored on the share of the scored frontend lines inside a reported copy, on the same curve as D4. Deterministic.
scripts/generate-github-release-notes.mjs:75 · scripts/release-context.mjs:19 — the two spans are one implementation copied and then locally edited — 90 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — scripts/generate-github-release-notes.mjs:75
promo-video/src/scenes.tsx:318 · promo-video/src/scenes.tsx:533 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. — promo-video/src/scenes.tsx:318
What to do
Act on each finding's own remediation rather than one rule: the move depends on what recurs. Where the copies are executable blocks, give the shared part one home and call it from each site; where they are declarations, a listing, a specialisation already delegating to its base, or one shape repeated per entity, there is no call site and the move is a shared type, a generated set or a factory — sometimes there is nothing to extract.
React / JS · Code Health — Per-function cyclomatic/cognitive complexity from the token-level function scanner (D-386) — real branching, not a regex heuristic.
Method: Per-function cyclomatic/cognitive complexity from a token-level function scanner (real branching, not a regex heuristic), computed over every frontend function. Deterministic.
(anonymous) has cyclomatic complexity 24 and cognitive complexity 19; 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. — promo-video/src/scenes.tsx:623
parseArgs has cyclomatic complexity 21 and cognitive complexity 45; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — scripts/generate-github-release-notes.mjs:28
extractChangelogSection has cyclomatic complexity 16 and cognitive complexity 26; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — scripts/generate-github-release-notes.mjs:135
parseArgs has cyclomatic complexity 16 and cognitive complexity 18; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — scripts/release-context.mjs:5
(anonymous) has cyclomatic complexity 14 and cognitive complexity 14; 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. — promo-video/src/lib.tsx:217
buildContext has cyclomatic complexity 12 and cognitive complexity 18; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — scripts/release-context.mjs:114
Do you agree with this assessment?
R3 · Large Files5.0 / 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.
promo-video/src/scenes.tsx has 703 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — promo-video/src/scenes.tsx:1
What to do
Split each oversized file along the responsibilities already in it, into smaller focused modules in the same package.
React / JS · Readiness — How outdated the npm dependencies are (a maturity signal). JS/npm CVEs are scored separately in D30 (JS/npm Dependency Vulnerabilities).
Method: npm dependency staleness from manifest/registry metadata (a maturity signal; JS/npm CVEs are scored separately in D30, which answers dependency vulnerabilities for every ecosystem). Deterministic.
Do you agree with this assessment?
R6 · Tooling6.7 / 10Adequate✓ Tool-verified
React / JS · Readiness — Whether the project wires up test, lint and typecheck — detected from each package.json script's COMMAND (eslint / tsc / vitest / jest / playwright), not just its name, and corroborated against CI-workflow invocations so a tool run only in CI still counts.
Method: package.json scanned for test/lint/typecheck script wiring. Deterministic presence check.
test ✓ · lint ✗ · typecheck ✓ — read from this repository's package.json scripts and corroborated against its CI workflows. A script counts when its name or command matches the step: `test` for the suite, `lint` or `prettier` for linting, `typecheck`/`type-check`/`tsc` for type checking. ✗ therefore means no script or CI step under those names was found, NOT that the step is absent from your pipeline — a task invoked by a runner this check does not read, or named something else entirely, is not seen and is worth confirming before acting on a cross. A ✓ means the wiring is DECLARED — a script or CI step under those names exists. It is not a statement that the step passes, or that it runs at all: nothing here installs a dependency or executes a suite.
What to do
Add eslint as package.json scripts and run them in CI.
Do you agree with this assessment?
R7 · Dead Code9.9 / 10Exemplary✓ Tool-verified
React / JS · Code Health — Files unreachable from every application/tooling/test entry point, and exports nothing imports (module-graph reachability, D-386).
Method: Dead code: files unreachable from every application/tooling/test entry point plus exports nothing imports, via module-graph reachability. Deterministic, exhaustive over the import graph.
Nothing imports this binding — it is safe to review for removal. — promo-video/src/lib.tsx:40
React / JS · Readiness — npm dependency truthfulness (D-386): unused dependencies, imports not declared anywhere, and type-/test-only packages shipped as production deps.
Method: npm dependency truthfulness: unused dependencies, imports declared nowhere, and type-/test-only packages shipped as production deps — from the manifest + import graph. Deterministic.
Declared in promo-video/package.json but never imported anywhere in that package or its workspace members — no static import reaches it. Usually that is dead weight and attack surface, but two shapes are indistinguishable from source and are NOT dead: an optional or native peer that another dependency loads dynamically at runtime, and a package a build, docs or test step installs and invokes separately. Confirm which of the three this is before removing it.
What to do
Remove unused dependencies, declare unlisted imports explicitly, and demote type-/test-only packages to devDependencies.
React / JS · Architecture — Import cycles in the module graph (D-386) — files that can only be understood and changed together.
Method: Import cycles in the module graph, detected exhaustively over JS/TS imports (the same cycle detection as the .NET coupling dimension). Deterministic.
Other · Security — 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.
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?
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.
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. (×20) — Sources/AXe/Utilities/AgentModeNativeOperation.swift:87, Sources/AXe/Utilities/AgentModeSnapshot.swift:74, Sources/AXe/Utilities/AgentModeSnapshot.swift:425, …
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.
Do you agree with this assessment?
WCAG coverage — what static analysis assessed
Statically assessed 2 of 55 WCAG 2.2 Level A/AA success criteria (4%; ≈4% of the 50 WCAG 2.1 AA criteria for EN 301 549). The other 53 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 — 7 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
X7 Silent fallback defaults — 1 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
Not evidenced — 4 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 — Not assessed: these audit controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) 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. Absence of an idiom this check recognises is NOT evidence that this repository lacks audit controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
C4 Data Retention — Not assessed: these retention controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) 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. Absence of an idiom this check recognises is NOT evidence that this repository lacks retention controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
C5 Data-Subject Rights — Not assessed: these data-subject rights controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) 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. Absence of an idiom this check recognises is NOT evidence that this repository lacks data-subject rights controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
P5 DR & Backup — not evidenced — repo shows no backup/RTO/RPO controls; absence of evidence is not evidence of a working control
Not included — 66 check(s) not relevant to this codebase
These checks had nothing to measure here (no tests, no git history, the codebase is small, or the architecture style doesn't apply), so they're omitted above rather than scored low.
AC1 Text alternatives — No image/media element found in the parsed markup — AC1 not applicable here.
AC2 Forms & labels — No form control/button found in the parsed markup — AC2 not applicable here.
AC3 Page structure — No structural check found in the parsed markup — AC3 not applicable here.
AC4 Keyboard semantics — No interactive element found in the parsed markup — AC4 not applicable here.
AC5 ARIA correctness — No ARIA usage found in the parsed markup — AC5 not applicable here.
AX1 Captive dependencies — 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
AX2 Stateful singletons — No container singleton was found, so there is no shared instance for concurrent requests to race on. No function in this Python code is served by a threaded web framework (a Flask, Bottle or FastAPI route, a Django or Pyramid view), so no module is shared between request threads. 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. TypeScript/JavaScript runs each process's requests on one event loop, so no two requests write a shared object at the same instant (interleaving across an await is a different defect).
AX5 Architecture & structure — not assessed — architecture style/structure is computed from a project graph (projects, types, module namespaces) that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
AX6 Interface segregation — no exported interface declares behaviour
AX7 Slice cohesion — not applicable — not a vertical-slice architecture
AXB1 Runtime evidence locked — no reproducible boot — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
C1 Data Protection — Not assessed: these personal data controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) 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. Absence of an idiom this check recognises is NOT evidence that this repository lacks personal data controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
C2 Access Controls — Not assessed: these authorization controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) 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. Absence of an idiom this check recognises is NOT evidence that this repository lacks authorization controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
D11 Test Reliability — Test reliability not included — the .swift suite was found but not re-run
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.
D22 Internal API Consistency — API consistency is measured on C# only; the exposed Swift surface was not measured.
D23 Boundary Type-Coupling — No bounded-context organisation was detected either — neither a context-shaped layout, nor 2+ sibling source directories each declaring an aggregate root, nor 2+ sibling projects each declaring an entity of their own or taking another project's integration events. Declaring this codebase's bounded contexts (≥2) would let cross-boundary type coupling be assessed. Declare them in `.codehealth/config.yaml` at the repository root (create it if absent), mapping each context name to the module-path or namespace prefixes that belong to it — e.g. `architecture:` → `contexts:` → `Billing: ["src/billing", "Acme.Billing"]`, `Catalog: ["src/catalog", "Acme.Catalog"]`.
D24 Comment Value — D24 reads C#, Visual Basic, TypeScript and JavaScript comments only; comments in this repository's .py, .rb, .swift source were not judged.
D25 ADR Conformance — no ADRs to check
D31 IaC & Container Security — No Infrastructure-as-Code or container manifests found (Dockerfile, Docker Compose, Terraform, Kubernetes/Helm, CloudFormation, ARM, Bicep, Ansible); nothing to scan.
D32 Data Compliance (PII/GDPR) — 38 file(s) were not parsed by semgrep — the PII/GDPR ruleset never ran over them
D37 Vulnerability-disclosure Policy — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed.
D40 Network Egress Confinement — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here.
D41 Kernel & Syscall Confinement — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here.
D42 Runtime Threat Enforcement — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here.
D44 Platform End-of-Life — Platform end-of-life not assessed — this repository declares no platform this pass reads
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
D8 Code Coverage — Coverage not measured — Swift suite
DM1 Domain Modelling — not scored — this repository shows only 1 of the 3 signals this lens looks for (5 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
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
GD1 Unfinished & placeholder code — no source files were read — this check reads C#, F#, JavaScript/TypeScript, Dart, Ruby and Scala, and none was read for this repository's product. That is a limit of the analyzer, not a finding about your code.
IC1 Incompleteness & stubs — 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
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 JavaScript/TypeScript, Swift source, so there is no service whose uptime a failing dependency could take down
P8 Schema migrations — no ORM, schema-migration tool or schema auto-create was found in this repository's dependency manifests or source, so there is no database schema for this check to judge
P9 Domain vs controller coverage — coverage not measured: this check compares the coverage of the analyzer's own test run across the domain and web layers, and that run measured none here — Test coverage (D8) says why
PF2 Allocation hygiene — Not scored: this check counted allocation-aware idioms (Span, pools, stackalloc) per line, which describes what kind of code a repository is rather than whether it has an allocation problem, so it was withdrawn. Nothing here is a finding about your code.
R11 Import Boundaries — No recognizable feature-sliced/layered src layout — boundary rules not applicable.
R4 Test Coverage — the JS/TS workspace (6 production file(s)) has no JavaScript/TypeScript test, but it is 2.41% of this repository's production source and the other 97.59% carries 42,418 line(s) of test code this pass cannot read — an incidental frontend's reachability is not the repository's test posture, so it is not scored as one
S1 Web-Security Posture — Not assessed: these web-security controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) 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. Absence of an idiom this check recognises is NOT evidence that this repository lacks web-security controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
SC1 Supply-chain hygiene — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
X1 Async correctness — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X12 Unreachable branch — X12 reached only 17% of this repository's production lines — swift (45,493 lines), c (58 lines) was left unread. Not scored: a score over a minority of the product would be published as the whole of it.
X13 Undrained process stream — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X15 Unvalidated length from an untrusted reader — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X16 Unfloored truncation loop — X16 reached only 3% of this repository's production lines — swift (45,493 lines), python (7,323 lines), c (58 lines) was left unread. Not scored: a score over a minority of the product would be published as the whole of it.
X17 Uncapped recursion over a caller-supplied document — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X18 Disposal-pattern correctness — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X19 Unrestored process-global state — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X2 Cancellation propagation — 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
X20 Mistyped argument guard — This check asks whether an argument guard reports an EMPTY value as a NULL one, which needs a language that throws a null-specific argument exception — .NET's ArgumentNullException, the JVM's NullPointerException, Dart's ArgumentError.notNull. This repository contains none of those languages: the ones it is written in have a single exception for a bad argument, so there is no pair of exceptions to confuse and nothing here for it to assess. Not a gap in the analyzer and not a finding about your code.
X21 Side-effecting pattern guard — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X22 Contradicted release guard — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X23 Unguarded diagnostic materialisation — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X24 Document value interpolated into markup unescaped — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X25 Inert configuration knob — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X27 Collection changed while being enumerated — 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
X29 Per-element action decided by a fixed element — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X30 Support guard that admits what it rejects — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X32 Type resolved by simple name across every loaded assembly — 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.
No assertions: inertAdditionsKeepTheLayout Tests/AgentBatchReferencePlanTests.swift:187— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: secureOrLocalIsAccepted Tests/AgentCommandURLTests.swift:13— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: tapRowsAdmitImpliedGestures Tests/AgentReferenceTapAdmissionTests.swift:24— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: semanticFocusDoesNotRequireObjectMetadata Tests/AnonymousNativeInputPolicyTests.swift:84— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: legacySelectableCommandsStillPassAdmission Tests/BatchSelectedAdmissionTests.swift:66— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: acceptedRequests Tests/BrokerBoundPlainInputTests.swift:22— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: randomNumbersMatchDecoder Tests/CLIOutputJSONDecodingTests.swift:102— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: fallbackMatchesDecoder Tests/CLIOutputJSONDecodingTests.swift:128— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: encodingsMatchDecoder Tests/CLIOutputJSONDecodingTests.swift:174— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: leadingZeroWidthNoBreakSpaceIsKept Tests/CLIOutputJSONDecodingTests.swift:182— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: validKeyOptions Tests/CommandValidationTests.swift:41— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: brokerCleanupIsSocketSpecific Tests/HIDBrokerTests.swift:345— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: invalidDataFails Tests/JPEGFrameContractTests.swift:31— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: nondefaultScalingUsesPixels Tests/JPEGFrameContractTests.swift:65— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: drag Tests/PlaygroundAgentDragTests.swift:10— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: focusAndType Tests/PlaygroundAgentFocusAndTypeTests.swift:15— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: key Tests/PlaygroundAgentKeyboardTests.swift:13— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: shortcut Tests/PlaygroundAgentKeyboardTests.swift:23— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: sequence Tests/PlaygroundAgentKeyboardTests.swift:34— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: keyboardFocusedFresh Tests/PlaygroundAgentObservationTests.swift:16— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: keyboardFocusedPageAndReuse Tests/PlaygroundAgentObservationTests.swift:24— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: substringTap Tests/PlaygroundAgentSelectorTests.swift:6— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: regexTap Tests/PlaygroundAgentSelectorTests.swift:8— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: decimalFrameTap Tests/PlaygroundAgentSelectorTests.swift:10— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: missingSelector Tests/PlaygroundAgentSelectorTests.swift:12— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
Hotspot: Sources/AXe/Utilities/AgentModeProtocol.swift Sources/AXe/Utilities/AgentModeProtocol.swift:39— Sources/AXe/Utilities/AgentModeProtocol.swift changed 21 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 300 in AgentModeRequest.validate at line 39. 4 of those changes were fix/bug commits, and the other 17 changed it for other reasons — this file is under both repair and feature pressure. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-08-17..2026-11-15, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-17 02:11:05 +07:00' --until='2026-11-15 02:11:05 +07:00' --full-history --no-merges -- Sources/AXe/Utilities/AgentModeProtocol.swift`: 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: Sources/AXe/Utilities/SelectedHIDProtocol.swift Sources/AXe/Utilities/SelectedHIDProtocol.swift:98— Sources/AXe/Utilities/SelectedHIDProtocol.swift changed 31 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 101 in SelectedHIDRequest.validate at line 98. 3 of those changes were fix/bug commits, and the other 28 changed it for other reasons — this file is under both repair and feature pressure. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-08-17..2026-11-15, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-17 02:11:05 +07:00' --until='2026-11-15 02:11:05 +07:00' --full-history --no-merges -- Sources/AXe/Utilities/SelectedHIDProtocol.swift`: 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: Sources/AXe/Utilities/SelectedHIDOwner.swift Sources/AXe/Utilities/SelectedHIDOwner.swift:44— Sources/AXe/Utilities/SelectedHIDOwner.swift changed 30 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 70 in SelectedHIDOwner.performRequest at line 44. 7 of those changes were fix/bug commits, and the other 23 changed it for other reasons — this file is under both repair and feature pressure. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-08-17..2026-11-15, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-17 02:11:05 +07:00' --until='2026-11-15 02:11:05 +07:00' --full-history --no-merges -- Sources/AXe/Utilities/SelectedHIDOwner.swift`: 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: Sources/AXe/Utilities/AgentModeController.swift Sources/AXe/Utilities/AgentModeController.swift:104— Sources/AXe/Utilities/AgentModeController.swift changed 36 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 56 in AgentModeController.performReserved at line 104. 14 of those changes were fix/bug commits, and the other 22 changed it for other reasons — this file is under both repair and feature pressure. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-08-17..2026-11-15, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-17 02:11:05 +07:00' --until='2026-11-15 02:11:05 +07:00' --full-history --no-merges -- Sources/AXe/Utilities/AgentModeController.swift`: 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: Sources/AXe/Commands/Gesture.swift Sources/AXe/Commands/Gesture.swift:291— Sources/AXe/Commands/Gesture.swift changed 28 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 56 in Gesture.validate at line 291. 8 of those changes were fix/bug commits, and the other 20 changed it for other reasons — this file is under both repair and feature pressure. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-08-17..2026-11-15, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-17 02:11:05 +07:00' --until='2026-11-15 02:11:05 +07:00' --full-history --no-merges -- Sources/AXe/Commands/Gesture.swift`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: scripts/test-playground-matrix.py scripts/test-playground-matrix.py:310— scripts/test-playground-matrix.py changed 12 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 110 in test-playground-matrix.main at line 310. 3 of those changes were fix/bug commits, and the other 9 changed it for other reasons — this file is under both repair and feature pressure. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-08-17..2026-11-15, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-17 02:11:05 +07:00' --until='2026-11-15 02:11:05 +07:00' --full-history --no-merges -- scripts/test-playground-matrix.py`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: Sources/AXe/Utilities/AgentModeSnapshot.swift Sources/AXe/Utilities/AgentModeSnapshot.swift:31— Sources/AXe/Utilities/AgentModeSnapshot.swift changed 15 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 88 in AgentModeSnapshot.init at line 31. 5 of those changes were fix/bug commits, and the other 10 changed it for other reasons — this file is under both repair and feature pressure. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-08-17..2026-11-15, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-17 02:11:05 +07:00' --until='2026-11-15 02:11:05 +07:00' --full-history --no-merges -- Sources/AXe/Utilities/AgentModeSnapshot.swift`: 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: Sources/AXe/Utilities/SelectedAXOperation.swift Sources/AXe/Utilities/SelectedAXOperation.swift:9— Sources/AXe/Utilities/SelectedAXOperation.swift changed 16 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 82 in SelectedAXOperation.perform at line 9. 4 of those changes were fix/bug commits, and the other 12 changed it for other reasons — this file is under both repair and feature pressure. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-08-17..2026-11-15, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-17 02:11:05 +07:00' --until='2026-11-15 02:11:05 +07:00' --full-history --no-merges -- Sources/AXe/Utilities/SelectedAXOperation.swift`: 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: Sources/AXe/Commands/Tap.swift Sources/AXe/Commands/Tap.swift:143— Sources/AXe/Commands/Tap.swift changed 22 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 58 in Tap.validate at line 143. 4 of those changes were fix/bug commits, and the other 18 changed it for other reasons — this file is under both repair and feature pressure. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-08-17..2026-11-15, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-17 02:11:05 +07:00' --until='2026-11-15 02:11:05 +07:00' --full-history --no-merges -- Sources/AXe/Commands/Tap.swift`: 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: Sources/AXe/Utilities/SliderValue/SelectedSliderValueOperation.swift Sources/AXe/Utilities/SliderValue/SelectedSliderValueOperation.swift:161— Sources/AXe/Utilities/SliderValue/SelectedSliderValueOperation.swift changed 13 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 67 in SelectedSliderValueOperation.perform at line 161. 8 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-08-17..2026-11-15, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-17 02:11:05 +07:00' --until='2026-11-15 02:11:05 +07:00' --full-history --no-merges -- Sources/AXe/Utilities/SliderValue/SelectedSliderValueOperation.swift`: 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: Sources/AXe/Utilities/SelectedAXProtocol.swift Sources/AXe/Utilities/SelectedAXProtocol.swift:91— Sources/AXe/Utilities/SelectedAXProtocol.swift changed 7 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 118 in SelectedAXRequest.validate at line 91. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-08-17..2026-11-15, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-17 02:11:05 +07:00' --until='2026-11-15 02:11:05 +07:00' --full-history --no-merges -- Sources/AXe/Utilities/SelectedAXProtocol.swift`: 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: Sources/AXe/Utilities/Batch/SelectedBatch.swift Sources/AXe/Utilities/Batch/SelectedBatch.swift:26— Sources/AXe/Utilities/Batch/SelectedBatch.swift changed 19 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 39 in SelectedBatchStep.request at line 26. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-08-17..2026-11-15, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-17 02:11:05 +07:00' --until='2026-11-15 02:11:05 +07:00' --full-history --no-merges -- Sources/AXe/Utilities/Batch/SelectedBatch.swift`: 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: Sources/AXe/Commands/Batch.swift Sources/AXe/Commands/Batch.swift:72— Sources/AXe/Commands/Batch.swift changed 19 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 39 in Batch.validate at line 72. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-08-17..2026-11-15, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-17 02:11:05 +07:00' --until='2026-11-15 02:11:05 +07:00' --full-history --no-merges -- Sources/AXe/Commands/Batch.swift`: 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: Sources/AXe/Commands/Swipe.swift Sources/AXe/Commands/Swipe.swift:61— Sources/AXe/Commands/Swipe.swift changed 21 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 29 in Swipe.validate at line 61. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-08-17..2026-11-15, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-17 02:11:05 +07:00' --until='2026-11-15 02:11:05 +07:00' --full-history --no-merges -- Sources/AXe/Commands/Swipe.swift`: 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: Sources/AXe/Utilities/SelectedHIDBroker.swift Sources/AXe/Utilities/SelectedHIDBroker.swift:155— Sources/AXe/Utilities/SelectedHIDBroker.swift changed 19 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 29 in SelectedHIDBroker.serve at line 155. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-08-17..2026-11-15, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-17 02:11:05 +07:00' --until='2026-11-15 02:11:05 +07:00' --full-history --no-merges -- Sources/AXe/Utilities/SelectedHIDBroker.swift`: 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: Sources/AXe/Commands/Slider.swift Sources/AXe/Commands/Slider.swift:59— Sources/AXe/Commands/Slider.swift changed 18 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 29 in Slider.validate at line 59. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-08-17..2026-11-15, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-17 02:11:05 +07:00' --until='2026-11-15 02:11:05 +07:00' --full-history --no-merges -- Sources/AXe/Commands/Slider.swift`: 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: Sources/AXe/Utilities/SelectedHIDPath.swift Sources/AXe/Utilities/SelectedHIDPath.swift:48— Sources/AXe/Utilities/SelectedHIDPath.swift changed 7 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 69 in SelectedHIDPath.validate at line 48. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-08-17..2026-11-15, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-17 02:11:05 +07:00' --until='2026-11-15 02:11:05 +07:00' --full-history --no-merges -- Sources/AXe/Utilities/SelectedHIDPath.swift`: 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: Sources/AXe/Commands/Drag.swift Sources/AXe/Commands/Drag.swift:62— Sources/AXe/Commands/Drag.swift changed 17 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 27 in Drag.validate at line 62. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-08-17..2026-11-15, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-17 02:11:05 +07:00' --until='2026-11-15 02:11:05 +07:00' --full-history --no-merges -- Sources/AXe/Commands/Drag.swift`: 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: Sources/AXe/Utilities/AgentModeController+NativeRequest.swift Sources/AXe/Utilities/AgentModeController+NativeRequest.swift:6— Sources/AXe/Utilities/AgentModeController+NativeRequest.swift changed 5 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 90 in AgentModeController.nativeRequest at line 6. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-08-17..2026-11-15, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-17 02:11:05 +07:00' --until='2026-11-15 02:11:05 +07:00' --full-history --no-merges -- Sources/AXe/Utilities/AgentModeController+NativeRequest.swift`: 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: Sources/AXe/Utilities/SliderValue/SliderPickupReadPhase.swift Sources/AXe/Utilities/SliderValue/SliderPickupReadPhase.swift:153— Sources/AXe/Utilities/SliderValue/SliderPickupReadPhase.swift changed 3 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 143 in SliderPickupReadPhase.run 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-08-17..2026-11-15, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-17 02:11:05 +07:00' --until='2026-11-15 02:11:05 +07:00' --full-history --no-merges -- Sources/AXe/Utilities/SliderValue/SliderPickupReadPhase.swift`: 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: Sources/AXe/Commands/Touch.swift Sources/AXe/Commands/Touch.swift:49— Sources/AXe/Commands/Touch.swift changed 15 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 28 in Touch.validate at line 49. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-08-17..2026-11-15, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-17 02:11:05 +07:00' --until='2026-11-15 02:11:05 +07:00' --full-history --no-merges -- Sources/AXe/Commands/Touch.swift`: 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: Sources/AXe/Commands/DescribeUI.swift Sources/AXe/Commands/DescribeUI.swift:58— Sources/AXe/Commands/DescribeUI.swift changed 12 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 30 in DescribeUI.validate at line 58. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-08-17..2026-11-15, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-17 02:11:05 +07:00' --until='2026-11-15 02:11:05 +07:00' --full-history --no-merges -- Sources/AXe/Commands/DescribeUI.swift`: 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: Sources/AXe/Utilities/SliderValue/SliderPickupHelper.swift Sources/AXe/Utilities/SliderValue/SliderPickupHelper.swift:116— Sources/AXe/Utilities/SliderValue/SliderPickupHelper.swift changed 5 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 72 in SliderPickupHelper.prepare at line 116. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-08-17..2026-11-15, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-17 02:11:05 +07:00' --until='2026-11-15 02:11:05 +07:00' --full-history --no-merges -- Sources/AXe/Utilities/SliderValue/SliderPickupHelper.swift`: 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: benchmarks/transcript.py benchmarks/transcript.py:535— benchmarks/transcript.py changed 6 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 53 in transcript.read_transcript at line 535. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-08-17..2026-11-15, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-17 02:11:05 +07:00' --until='2026-11-15 02:11:05 +07:00' --full-history --no-merges -- benchmarks/transcript.py`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: Sources/AXe/Utilities/AgentModePathAdmissionGuard.swift Sources/AXe/Utilities/AgentModePathAdmissionGuard.swift:152— Sources/AXe/Utilities/AgentModePathAdmissionGuard.swift changed 10 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 29 in AgentModePathAdmissionGuard.validateRelationship at line 152. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-08-17..2026-11-15, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-17 02:11:05 +07:00' --until='2026-11-15 02:11:05 +07:00' --full-history --no-merges -- Sources/AXe/Utilities/AgentModePathAdmissionGuard.swift`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Swallowed exception (caught, then discarded) Sources/AXe/Utilities/AgentModeNativeOperation.swift:87— `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) Sources/AXe/Utilities/AgentModeSnapshot.swift:74— `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) Sources/AXe/Utilities/AgentModeSnapshot.swift:425— `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) Sources/AXe/Utilities/SelectedAXOperation.swift:316— `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) Sources/AXe/Utilities/SelectedHIDClientLifetime.swift:38— `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) Sources/AXe/Utilities/SelectedHIDOwner.swift:433— `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) Sources/AXe/Utilities/SelectedKeyboardOperation.swift:73— `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) Sources/AXe/Utilities/SliderValue/SelectedSliderValueOperation.swift:680— `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) Sources/AXe/Utilities/SliderValue/SliderPickupHelper.swift:259— `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) Sources/AXe/Device/DeviceServiceDirectory.swift:395— `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) Sources/AXe/Device/DeviceServiceDirectory.swift:415— `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) Sources/AXe/Device/PhysicalDeviceBrokerOwner.swift:279— `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) Sources/AXe/Device/PhysicalDeviceInputOwner.swift:338— `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) Sources/AXe/Device/PhysicalDeviceInputOwner.swift:344— `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) Sources/AXe/Device/PhysicalDeviceInputOwner.swift:350— `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) Sources/AXe/Device/PhysicalDeviceMedia.swift:75— `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/IDBKit/FBSimulatorControl/HID/FBSimulatorHIDSession.swift:481— `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/IDBKit/FBSimulatorControl/HID/FBSimulatorHIDSession.swift:562— `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/IDBKit/FBSimulatorControl/HID/FBSimulatorHIDSession.swift:779— `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/IDBKit/FBSimulatorControl/Commands/FBSimulatorApplicationCommands.swift:366— `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.
MethodTooLong: SelectedAXOperation.perform Sources/AXe/Utilities/SelectedAXOperation.swift:9— MethodTooLong — perform runs 266 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 166 over it, 2.66× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: SliderPickupReadPhase.run Sources/AXe/Utilities/SliderValue/SliderPickupReadPhase.swift:153— MethodTooLong — run runs 247 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 147 over it, 2.47× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: SimulatorAgentRunner.run Sources/AXe/Agent/SimulatorAgentRunner.swift:149— MethodTooLong — run runs 239 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 139 over it, 2.39× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: SelectedSliderValueOperation.perform Sources/AXe/Utilities/SliderValue/SelectedSliderValueOperation.swift:161— MethodTooLong — perform runs 182 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 82 over it, 1.82× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: AgentModeController.performReserved Sources/AXe/Utilities/AgentModeController.swift:104— MethodTooLong — performReserved runs 178 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 78 over it, 1.78× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: AgentModeController.nativeRequest Sources/AXe/Utilities/AgentModeController+NativeRequest.swift:6— MethodTooLong — nativeRequest runs 166 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 66 over it, 1.66× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: AgentPolicy.prepareRequest Sources/AXeCore/AgentPolicy.swift:13— MethodTooLong — prepareRequest runs 162 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 62 over it, 1.62× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: AgentModeRequest.validate Sources/AXe/Utilities/AgentModeProtocol.swift:39— MethodTooLong — validate runs 156 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 56 over it, 1.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.
MethodTooLong: AgentModeSnapshot.init Sources/AXe/Utilities/AgentModeSnapshot.swift:31— MethodTooLong — init runs 142 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 42 over it, 1.42× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: AgentModeController.performBatchReserved Sources/AXe/Utilities/AgentModeController+Batch.swift:97— MethodTooLong — performBatchReserved runs 136 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 36 over it, 1.36× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: GesturePresetsView.body AxePlaygroundApp/AxePlayground/Views/GesturePresetsView.swift:110— MethodTooLong — body runs 125 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 25 over it, 1.25× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: SelectedHIDOwner.performRequest Sources/AXe/Utilities/SelectedHIDOwner.swift:44— MethodTooLong — performRequest runs 124 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 24 over it, 1.24× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: SelectedHIDRequest.validate Sources/AXe/Utilities/SelectedHIDProtocol.swift:98— MethodTooLong — validate runs 114 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 14 over it, 1.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.
MethodTooLong: DuoControlsController.viewDidLoad AxePlaygroundApp/AxePlayground/Views/DuoControlsView.swift:42— MethodTooLong — viewDidLoad runs 101 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 1 over it, 1.01× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
Duplicated block (5 lines × 2) Sources/AXe/Utilities/AccessibilityFetcher.swift:90— Sources/AXe/Utilities/AccessibilityFetcher.swift:90-94 | Sources/AXe/Utilities/AccessibilityFetcher.swift:133-137 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (5 lines × 2) Sources/AXe/Utilities/AgentModeController.swift:151— Sources/AXe/Utilities/AgentModeController.swift:151-155 | Sources/AXe/Utilities/AgentModeController.swift:299-303 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `Sources/AXe/Utilities/AgentModeController.swift:151` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (5 lines × 2) Sources/AXe/Utilities/SelectedVideoRecording.swift:33— Sources/AXe/Utilities/SelectedVideoRecording.swift:33-37 | Sources/AXe/Utilities/SelectedVideoStream.swift:27-31 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (5 lines × 2) AxePlaygroundApp/AxePlayground/Views/DrawingView.swift:103— AxePlaygroundApp/AxePlayground/Views/DrawingView.swift:103-107 | AxePlaygroundApp/AxePlayground/Views/SketchView.swift:160-164 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (5 lines × 2) Sources/AXe/Commands/Gesture.swift:241— Sources/AXe/Commands/Gesture.swift:241-245 | Sources/AXe/Utilities/ScrollUntil.swift:29-33 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (5 lines × 2) Sources/AXe/Utilities/AgentModeController+Batch.swift:106— Sources/AXe/Utilities/AgentModeController+Batch.swift:106-110 | Sources/AXe/Utilities/AgentModeController+FocusAndType.swift:124-128 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `Sources/AXe/Utilities/AgentModeController+Batch.swift:111` calls `AgentBatchReceipt` and `Sources/AXe/Utilities/AgentModeController+FocusAndType.swift:129` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (5 lines × 2) Sources/AXe/Utilities/CLIOutputText.swift:21— Sources/AXe/Utilities/CLIOutputText.swift:21-25 | Sources/AXe/Utilities/CLIOutputText.swift:80-84 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `Sources/AXe/Utilities/CLIOutputText.swift:21` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (5 lines × 2) Sources/AXe/Utilities/FollowActiveVideoRecording.swift:52— Sources/AXe/Utilities/FollowActiveVideoRecording.swift:52-56 | Sources/AXe/Utilities/SelectedVideoRecording.swift:52-56 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `Sources/AXe/Utilities/FollowActiveVideoRecording.swift:52` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (5 lines × 2) scripts/fixtures/DuoHeldHardwareProbe.swift:47— scripts/fixtures/DuoHeldHardwareProbe.swift:47-51 | scripts/fixtures/DuoHeldModifierProbe.swift:47-51 — before extracting anything, compare `scripts/fixtures/DuoHeldHardwareProbe.swift` and `scripts/fixtures/DuoHeldModifierProbe.swift` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 51 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `scripts/fixtures/DuoHeldHardwareProbe.swift:47` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (5 lines × 2) scripts/bench-quick.py:115— scripts/bench-quick.py:115-119 | scripts/test-physical-devices.py:123-127 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (6 lines × 2) Sources/AXe/Commands/Slider.swift:178— Sources/AXe/Commands/Slider.swift:178-183 | Sources/AXe/Utilities/AccessibilityTargetResolver.swift:126-131 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (6 lines × 2) Sources/AXe/Device/PhysicalDeviceMedia.swift:126— Sources/AXe/Device/PhysicalDeviceMedia.swift:126-131 | Sources/AXe/Utilities/FollowActiveVideoRecording.swift:85-90 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `Sources/AXe/Device/PhysicalDeviceMedia.swift:126` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (6 lines × 2) Sources/AXe/Utilities/PhaseTiming.swift:50— Sources/AXe/Utilities/PhaseTiming.swift:50-55 | Sources/AXe/Utilities/PhaseTiming.swift:61-66 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (6 lines × 2) Sources/AXeCore/AgentTextModelClient.swift:107— Sources/AXeCore/AgentTextModelClient.swift:107-112 | Sources/AXeCore/TypeSafeClient.swift:167-172 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (6 lines × 2) Sources/AXe/Device/PhysicalDeviceMedia.swift:48— Sources/AXe/Device/PhysicalDeviceMedia.swift:48-53 | Sources/AXe/Utilities/SelectedVideoStream.swift:52-57 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (6 lines × 2) Sources/AXe/Utilities/FollowActiveVideoRecording.swift:76— Sources/AXe/Utilities/FollowActiveVideoRecording.swift:76-81 | Sources/AXe/Utilities/SelectedVideoRecording.swift:72-77 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `Sources/AXe/Utilities/FollowActiveVideoRecording.swift:76` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (6 lines × 2) Sources/AXe/Commands/Displays.swift:23— Sources/AXe/Commands/Displays.swift:23-28 | Sources/AXe/Commands/Shutdown.swift:16-21 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `Sources/AXe/Commands/Displays.swift:20` calls `Flag`, `customLong` and `Sources/AXe/Commands/Shutdown.swift:14` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
D4 · Code Duplication· Edited copy of a member (6 corresponding lines) · ×6
Edited copy of a member (6 corresponding lines) Sources/AXe/Utilities/AgentModeSnapshot.swift:248— Sources/AXe/Utilities/AgentModeSnapshot.swift:248-253 | Sources/AXe/Utilities/AgentModeSnapshot.swift:273-278 — These two members are one piece of code written twice and then edited apart: 6 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (6 corresponding lines) Sources/AXe/Utilities/AgentModeController+Batch.swift:48— Sources/AXe/Utilities/AgentModeController+Batch.swift:48-53 | Sources/AXe/Utilities/AgentModeController+Batch.swift:89-95 — These two members are one piece of code written twice and then edited apart: 6 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (6 corresponding lines) AxePlaygroundApp/AxePlayground/Views/DuoControlsTouchObserver.swift:33— AxePlaygroundApp/AxePlayground/Views/DuoControlsTouchObserver.swift:33-39 | AxePlaygroundApp/AxePlayground/Views/TouchMonitorView.swift:133-138 — These two members are one piece of code written twice and then edited apart: 6 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (6 corresponding lines) AxePlaygroundApp/AxePlayground/Views/DuoControlsView.swift:316— AxePlaygroundApp/AxePlayground/Views/DuoControlsView.swift:316-321 | AxePlaygroundApp/AxePlayground/Views/DuoControlsView.swift:322-328 — These two members are one piece of code written twice and then edited apart: 6 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (6 corresponding lines) Sources/AXe/Utilities/AgentBatchReferencePlan.swift:161— Sources/AXe/Utilities/AgentBatchReferencePlan.swift:161-166 | Sources/AXe/Utilities/AgentReferenceTapAdmission.swift:68-73 — These two members are one piece of code written twice and then edited apart: 6 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (6 corresponding lines) scripts/test-physical-devices.py:419— scripts/test-physical-devices.py:419-424 | scripts/test-physical-devices.py:427-432 — These two members are one piece of code written twice and then edited apart: 6 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
FileTooLong: src/scenes.tsx promo-video/src/scenes.tsx— FileTooLong — 622 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 122 over it, 1.24× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: AXeCore/RuntimeSnapshot.swift Sources/AXeCore/RuntimeSnapshot.swift— FileTooLong — 571 significant lines (blank, comment-only and punctuation-only lines excluded), about 61% of them inside a single declaration: RuntimeSnapshotBuilder (202-709). The bar is 500 significant lines; this is 71 over it, 1.14× 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: AXeCore/AgentPolicy.swift Sources/AXeCore/AgentPolicy.swift— FileTooLong — 527 significant lines (blank, comment-only and punctuation-only lines excluded), about 66% of them inside a single declaration: AgentPolicy (3-473). The bar is 500 significant lines; this is 27 over it, 1.05× 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: SliderValue/SelectedSliderValueOperation.swift Sources/AXe/Utilities/SliderValue/SelectedSliderValueOperation.swift— FileTooLong — 508 significant lines (blank, comment-only and punctuation-only lines excluded), about 92% of them inside a single declaration: SelectedSliderValueOperation (76-687). The bar is 500 significant lines; this is 8 over it, 1.02× 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: Utilities/AgentModeController.swift Sources/AXe/Utilities/AgentModeController.swift— FileTooLong — 502 significant lines (blank, comment-only and punctuation-only lines excluded), about 99% of them inside a single declaration: AgentModeController (8-712). The bar is 500 significant lines; this is 2 over it, 1.00× 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.
ClassTooLong: AgentModeController Sources/AXe/Utilities/AgentModeController.swift:7— ClassTooLong — 497 significant lines (blank, comment-only and punctuation-only lines excluded), 45 methods. The bar is 400 significant lines; this is 97 over it, 1.24× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
ClassTooLong: SelectedSliderValueOperation Sources/AXe/Utilities/SliderValue/SelectedSliderValueOperation.swift:75— ClassTooLong — 467 significant lines (blank, comment-only and punctuation-only lines excluded), 15 methods. The bar is 400 significant lines; this is 67 over it, 1.17× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
ClassTooLong: SelectedHIDOwner Sources/AXe/Utilities/SelectedHIDOwner.swift:7— ClassTooLong — 446 significant lines (blank, comment-only and punctuation-only lines excluded), 26 methods. The bar is 400 significant lines; this is 46 over it, 1.12× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
ClassTooLong: Tap Sources/AXe/Commands/Tap.swift:6— ClassTooLong — 420 significant lines (blank, comment-only and punctuation-only lines excluded), 21 methods. The bar is 400 significant lines; this is 20 over it, 1.05× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
ClassTooLong: SimulatorAgentRunner Sources/AXe/Agent/SimulatorAgentRunner.swift:93— ClassTooLong — 415 significant lines (blank, comment-only and punctuation-only lines excluded), 13 methods. The bar is 400 significant lines; this is 15 over it, 1.04× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
D4 · Code Duplication· Edited copy of a member (7 corresponding lines) · ×5
Edited copy of a member (7 corresponding lines) Sources/AXe/Utilities/SliderValue/SliderPickupReadPhase.swift:26— Packages/IDBKit/FBSimulatorControl/Commands/FBSimulatorAXTargetOperation.swift:672-680 | Sources/AXe/Utilities/SliderValue/SliderPickupReadPhase.swift:26-32 — These two members are one piece of code written twice and then edited apart: 7 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (7 corresponding lines) Sources/AXe/Utilities/SliderValue/SliderPickupReadPhase.swift:110— Packages/IDBKit/FBSimulatorControl/Commands/FBSimulatorAXTargetOperation.swift:728-735 | Sources/AXe/Utilities/SliderValue/SliderPickupReadPhase.swift:110-116 — These two members are one piece of code written twice and then edited apart: 7 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (7 corresponding lines) Sources/AXeCore/AgentTextModelClient.swift:144— Sources/AXeCore/AgentTextModelClient.swift:144-150 | Sources/AXeCore/TypeSafeClient.swift:211-217 — These two members are one piece of code written twice and then edited apart: 7 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (7 corresponding lines) Sources/AXe/Device/PhysicalDeviceMedia.swift:144— Sources/AXe/Device/PhysicalDeviceMedia.swift:144-150 | Sources/AXe/Utilities/SelectedVideoStream.swift:105-111 — These two members are one piece of code written twice and then edited apart: 7 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (7 corresponding lines) Sources/AXe/Utilities/SliderValue/SelectedSliderValueOperation.swift:153— Sources/AXe/Utilities/SliderValue/SelectedSliderValueOperation.swift:153-159 | Sources/AXe/Utilities/SliderValue/SliderPickupHelper.swift:39-45 — These two members are one piece of code written twice and then edited apart: 7 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (3 corresponding lines) · ×5
Edited copy of a member (3 corresponding lines) Sources/AXe/Utilities/DeviceStateOutput.swift:121— Sources/AXe/Utilities/DeviceStateOutput.swift:121-123 | Sources/AXe/Utilities/PhaseTiming.swift:196-198 — These two members are one piece of code written twice and then edited apart: 3 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (3 corresponding lines) Sources/AXe/Utilities/AccessibilityTargetResolver.swift:158— Sources/AXe/Utilities/AccessibilityTargetResolver.swift:158-160 | Sources/AXe/Utilities/OrientationAwareCoordinates.swift:530-535 — These two members are one piece of code written twice and then edited apart: 3 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (3 corresponding lines) Sources/AXe/Utilities/AgentBatchReferencePlan.swift:228— Sources/AXe/Utilities/AgentBatchReferencePlan.swift:228-230 | Sources/AXe/Utilities/AgentModeFingerprint.swift:7-9 — These two members are one piece of code written twice and then edited apart: 3 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (3 corresponding lines) Sources/AXe/Utilities/DeviceStateOutput.swift:87— Sources/AXe/Utilities/DeviceStateOutput.swift:87-90 | Sources/AXe/Utilities/TouchStroke.swift:76-78 — These two members are one piece of code written twice and then edited apart: 3 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (3 corresponding lines) Sources/AXe/Commands/PhysicalDeviceGestures.swift:156— Sources/AXe/Commands/PhysicalDeviceGestures.swift:156-158 | Sources/AXe/Device/PhysicalDeviceInputOwner.swift:372-374 — These two members are one piece of code written twice and then edited apart: 3 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Duplicated block (8 lines × 2) Sources/AXe/Commands/Drag.swift:144— Sources/AXe/Commands/Drag.swift:144-152 | Sources/AXe/Commands/Touch.swift:161-168 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `Sources/AXe/Commands/Drag.swift:144` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
Duplicated block (8 lines × 2) Sources/AXe/Utilities/AgentModeController.swift:637— Sources/AXe/Utilities/AgentModeController.swift:637-644 | Sources/AXe/Utilities/AgentModeNativeOperation.swift:23-30 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (8 lines × 2) AxePlaygroundApp/AxePlayground/Views/DrawingView.swift:94— AxePlaygroundApp/AxePlayground/Views/DrawingView.swift:94-101 | AxePlaygroundApp/AxePlayground/Views/SketchView.swift:139-146 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (8 lines × 2) scripts/fixtures/DuoHeldHardwareProbe.swift:78— scripts/fixtures/DuoHeldHardwareProbe.swift:78-85 | scripts/fixtures/DuoHeldModifierProbe.swift:78-85 — before extracting anything, compare `scripts/fixtures/DuoHeldHardwareProbe.swift` and `scripts/fixtures/DuoHeldModifierProbe.swift` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 51 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `scripts/fixtures/DuoHeldHardwareProbe.swift:78` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (8 lines × 2) scripts/test-playground-matrix.py:100— scripts/test-playground-matrix.py:100-107 | scripts/verification/wait-cold-broker.py:70-77 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (7 lines × 2) AxePlaygroundApp/AxePlayground/Views/DrawingView.swift:119— AxePlaygroundApp/AxePlayground/Views/DrawingView.swift:119-125 | AxePlaygroundApp/AxePlayground/Views/SketchView.swift:192-198 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `AxePlaygroundApp/AxePlayground/Views/DrawingView.swift:119` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (7 lines × 2) Sources/AXe/Commands/Drag.swift:161— Sources/AXe/Commands/Drag.swift:161-167 | Sources/AXe/Commands/Swipe.swift:219-225 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `Sources/AXe/Commands/Drag.swift:161` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
Duplicated block (7 lines × 2) Sources/AXe/Utilities/OrdinaryBrokerInput.swift:213— Sources/AXe/Utilities/OrdinaryBrokerInput.swift:213-219 | Sources/AXe/Utilities/OrdinaryBrokerInput.swift:232-238 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `Sources/AXe/Utilities/OrdinaryBrokerInput.swift:213` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
Duplicated block (7 lines × 2) Sources/AXe/Utilities/AgentModeController+Batch.swift:80— Sources/AXe/Utilities/AgentModeController+Batch.swift:80-86 | Sources/AXe/Utilities/AgentModeController.swift:440-446 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `Sources/AXe/Utilities/AgentModeController+Batch.swift:80` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (7 lines × 2) Sources/AXe/Commands/Hinge.swift:147— Sources/AXe/Commands/Hinge.swift:147-153 | Sources/AXe/Commands/Rotate.swift:102-108 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Repeated repair: Sources/AXe/Utilities/ScrollUntil.swift Sources/AXe/Utilities/ScrollUntil.swift:56— Sources/AXe/Utilities/ScrollUntil.swift changed 4 times in last 90 days and 4 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 12 (its worst body is ScrollUntilOptions.run at line 56), AT OR 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(gesture): End each scroll-until step at rest so nothing is flicked past”; “fix(gesture): Judge scroll-until only at rest, and let an element own its parts”; “fix(gesture): Wait for the content to rest before scroll-until succeeds”; “fix(gesture): Treat an empty point lookup as not visible while scrolling”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-08-17..2026-11-15, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-17 02:11:05 +07:00' --until='2026-11-15 02:11:05 +07:00' --full-history --no-merges -- Sources/AXe/Utilities/ScrollUntil.swift`: 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: Sources/AXe/Utilities/DeviceStateOutput.swift Sources/AXe/Utilities/DeviceStateOutput.swift:94— Sources/AXe/Utilities/DeviceStateOutput.swift changed 4 times in last 90 days and 4 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 13 (its worst body is DeviceStateText.screenLines at line 94), AT OR 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(duo): Trust a steady stale display report that fits the hinge”; “fix(output): Keep framework dumps out of messages; name unparsed commands”; “fix(output): Code every error and print compact results by default”; “fix(output): Keep exit status and codes the same with --verbose”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-08-17..2026-11-15, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-17 02:11:05 +07:00' --until='2026-11-15 02:11:05 +07:00' --full-history --no-merges -- Sources/AXe/Utilities/DeviceStateOutput.swift`: 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: benchmarks/preparation.py benchmarks/preparation.py:439— benchmarks/preparation.py 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 11 (its worst body is preparation._profile at line 439), AT OR 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(bench): Name stray contacts instead of misreading the list as a card”; “fix(benchmarks): Wait for each Contacts preparation screen to arrive”; “fix(benchmarks): Wait for each Reminders preparation target”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-08-17..2026-11-15, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-17 02:11:05 +07:00' --until='2026-11-15 02:11:05 +07:00' --full-history --no-merges -- benchmarks/preparation.py`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Repeated repair: benchmarks/suite.py benchmarks/suite.py:30— benchmarks/suite.py changed 3 times in last 90 days and 3 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 11 (its worst body is suite.make_suite at line 30), AT OR 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(plugin): Ship the plugin from its own folder, not the whole repo”; “fix(bench): Measure every tool with its official skill on UI interaction only”; “fix(benchmarks): Give AXe the skill that axe init installs”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-08-17..2026-11-15, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-17 02:11:05 +07:00' --until='2026-11-15 02:11:05 +07:00' --full-history --no-merges -- benchmarks/suite.py`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
D4 · Code Duplication· Edited copy of a member (12 corresponding lines) · ×4
Edited copy of a member (12 corresponding lines) Sources/AXe/Commands/Gesture.swift:392— Sources/AXe/Commands/Gesture.swift:392-403 | Sources/AXe/Commands/Swipe.swift:274-286 — These two members are one piece of code written twice and then edited apart: 12 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (12 corresponding lines) Sources/AXe/Commands/Type.swift:94— Sources/AXe/Commands/Type.swift:94-106 | Sources/AXe/Utilities/AgentModeCommandAdapter.swift:78-89 — These two members are one piece of code written twice and then edited apart: 12 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (12 corresponding lines) Sources/AXe/Utilities/SimulatorOrientationReader.swift:87— Sources/AXe/Utilities/SimulatorOrientationReader.swift:87-98 | Sources/AXe/Utilities/SimulatorOrientationReader.swift:100-111 — These two members are one piece of code written twice and then edited apart: 12 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (12 corresponding lines) Sources/AXe/Utilities/HIDBroker+Connection.swift:339— Sources/AXe/Utilities/HIDBroker+Connection.swift:339-356 | Sources/AXe/Utilities/HIDBroker+Connection.swift:358-369 — These two members are one piece of code written twice and then edited apart: 12 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (8 corresponding lines) · ×4
Edited copy of a member (8 corresponding lines) Sources/AXe/Utilities/AccessibilityElement.swift:94— Packages/IDBKit/FBSimulatorControl/Commands/FBSimulatorAXSnapshot.swift:127-134 | Sources/AXe/Utilities/AccessibilityElement.swift:94-117 — These two members are one piece of code written twice and then edited apart: 8 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (8 corresponding lines) Sources/AXe/Device/PhysicalDeviceMedia.swift:7— Sources/AXe/Device/PhysicalDeviceMedia.swift:7-14 | Sources/AXe/Device/PhysicalDeviceMedia.swift:16-24 — These two members are one piece of code written twice and then edited apart: 8 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (8 corresponding lines) AxePlaygroundApp/AxePlayground/Views/DuoControlsTargets.swift:90— AxePlaygroundApp/AxePlayground/Views/DuoControlsTargets.swift:90-97 | AxePlaygroundApp/AxePlayground/Views/DuoControlsView.swift:266-274 — These two members are one piece of code written twice and then edited apart: 8 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (8 corresponding lines) Sources/AXe/Commands/Clipboard.swift:36— Sources/AXe/Commands/Clipboard.swift:36-46 | Sources/AXe/Commands/Shutdown.swift:23-30 — These two members are one piece of code written twice and then edited apart: 8 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (4 corresponding lines) · ×4
Edited copy of a member (4 corresponding lines) Sources/AXe/Utilities/SliderValue/SliderPickupReadPhase.swift:508— Packages/IDBKit/FBSimulatorControl/Commands/FBSimulatorAXSnapshot.swift:207-210 | Sources/AXe/Utilities/SliderValue/SliderPickupReadPhase.swift:508-511 — These two members are one piece of code written twice and then edited apart: 4 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (4 corresponding lines) Sources/AXe/Device/PhysicalDisplayUDPReceiver.swift:209— Sources/AXe/Device/PhysicalDisplayUDPReceiver.swift:209-212 | Sources/AXe/Device/RemoteXPCConnection.swift:412-415 — These two members are one piece of code written twice and then edited apart: 4 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (4 corresponding lines) AxePlaygroundApp/AxePlayground/Views/DrawingView.swift:159— AxePlaygroundApp/AxePlayground/Views/DrawingView.swift:159-162 | AxePlaygroundApp/AxePlayground/Views/SketchView.swift:270-273 — These two members are one piece of code written twice and then edited apart: 4 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (4 corresponding lines) Sources/AXe/Device/PhysicalDeviceInputOwner.swift:321— Sources/AXe/Device/PhysicalDeviceInputOwner.swift:321-324 | Sources/AXe/Device/PhysicalDeviceMediaCapture.swift:93-96 — These two members are one piece of code written twice and then edited apart: 4 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Duplicated block (11 lines × 2) Sources/AXe/Commands/RecordVideo.swift:269— Sources/AXe/Commands/RecordVideo.swift:269-279 | Sources/AXe/Commands/Screenshot.swift:211-221 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `Sources/AXe/Commands/RecordVideo.swift:269` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (11 lines × 2) Sources/AXe/Commands/Tap.swift:490— Sources/AXe/Commands/Tap.swift:490-500 | Sources/AXe/Utilities/Batch/Command+BatchConvertible.swift:104-114 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `Sources/AXe/Commands/Tap.swift:490` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (11 lines × 2) Sources/AXeCore/AgentPolicy.swift:517— Sources/AXeCore/AgentPolicy.swift:517-527 | Sources/AXeCore/AgentPolicy.swift:529-539 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (11 lines × 2) Sources/AXe/Utilities/AgentModeController+Batch.swift:295— Sources/AXe/Utilities/AgentModeController+Batch.swift:295-305 | Sources/AXe/Utilities/AgentModeController+Batch.swift:347-357 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
TooManyMethods: AgentModeController Sources/AXe/Utilities/AgentModeController.swift:7— TooManyMethods — 45 methods, declared across 4 files: Utilities/AgentModeController.swift (31), Utilities/AgentModeController+Batch.swift (10), Utilities/AgentModeController+FocusAndType.swift (3), Utilities/AgentModeController+NativeRequest.swift (1). The bar is 30 methods; this is 15 over it, 1.50× the bar. That list is where to read them, not a suggestion to split the file: the members belong to the type wherever they are declared, so moving them between files leaves the count unchanged. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: DuoControlsController AxePlaygroundApp/AxePlayground/Views/DuoControlsView.swift:10— TooManyMethods — 39 methods. The bar is 30 methods; this is 9 over it, 1.30× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: AgentModeSnapshot Sources/AXe/Utilities/AgentModeSnapshot.swift:6— TooManyMethods — 32 methods, declared across 3 files: Utilities/AgentModeSnapshot.swift (28), Utilities/AgentModeFingerprint.swift (2), Utilities/AgentModeSnapshot+Capture.swift (2). The bar is 30 methods; this is 2 over it, 1.07× the bar. That list is where to read them, not a suggestion to split the file: the members belong to the type wherever they are declared, so moving them between files leaves the count unchanged. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
D4 · Code Duplication· Edited copy of a member (19 corresponding lines) · ×3
Edited copy of a member (19 corresponding lines) scripts/fixtures/DuoExternalStateChange.swift:311— Packages/IDBKit/FBSimulatorControl/HID/FBSimulatorHingeNative.swift:97-115 | scripts/fixtures/DuoExternalStateChange.swift:311-334 — These two members are one piece of code written twice and then edited apart: 19 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (19 corresponding lines) Sources/AXe/Utilities/AccessibilityFetcher.swift:89— Sources/AXe/Utilities/AccessibilityFetcher.swift:89-107 | Sources/AXe/Utilities/AccessibilityFetcher.swift:131-159 — These two members are one piece of code written twice and then edited apart: 19 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (19 corresponding lines) Sources/AXe/Utilities/Setup.swift:8— Sources/AXe/Utilities/Setup.swift:8-26 | Sources/AXe/Utilities/SimulatorUtilities.swift:6-24 — These two members are one piece of code written twice and then edited apart: 19 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copies of one member (3 members, 7+ corresponding lines) · ×3
Edited copies of one member (3 members, 7+ corresponding lines) Sources/AXe/Utilities/PhaseTiming.swift:48— Sources/AXe/Utilities/PhaseTiming.swift:48-55 | Sources/AXe/Utilities/PhaseTiming.swift:59-66 | Sources/AXe/Utilities/PhaseTiming.swift:68-74 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 7 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
Edited copies of one member (3 members, 7+ corresponding lines) Sources/AXe/Utilities/FollowActiveVideoRecording.swift:9— Sources/AXe/Utilities/FollowActiveVideoRecording.swift:9-15 | Sources/AXe/Utilities/SelectedVideoRecording.swift:10-18 | Sources/AXe/Utilities/SelectedVideoStream.swift:9-17 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 7 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
Edited copies of one member (3 members, 7+ corresponding lines) AxePlaygroundApp/AxePlayground/Views/DrawingView.swift:119— AxePlaygroundApp/AxePlayground/Views/DrawingView.swift:119-127 | AxePlaygroundApp/AxePlayground/Views/SketchView.swift:192-201 | AxePlaygroundApp/AxePlayground/Views/ZoomView.swift:111-117 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 7 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
Duplicated block (12 lines × 2) Sources/AXe/Commands/DescribeUI.swift:125— Sources/AXe/Commands/DescribeUI.swift:125-136 | Sources/AXe/Commands/Drag.swift:135-146 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `Sources/AXe/Commands/DescribeUI.swift:125` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (12 lines × 2) Sources/AXe/Device/RemoteXPCConnection.swift:328— Sources/AXe/Device/RemoteXPCConnection.swift:328-339 | Sources/AXe/Device/RemoteXPCConnection.swift:350-361 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `Sources/AXe/Device/RemoteXPCConnection.swift:328` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (12 lines × 2) Sources/AXe/Utilities/FollowActiveVideoRecording.swift:36— Sources/AXe/Utilities/FollowActiveVideoRecording.swift:36-47 | Sources/AXe/Utilities/SelectedVideoRecording.swift:38-49 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. The matched lines also register a scope-exit action (a `defer`-style statement) that runs when the function holding them returns: moved into a called unit it would run when THAT unit returns instead — before the caller uses what it releases — so keep the registration at the call site and extract only the work around it, or have the extracted unit hand the resource back for the caller to register. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `Sources/AXe/Utilities/SelectedVideoRecording.swift:37` calls `sessionObservation` and `Sources/AXe/Utilities/FollowActiveVideoRecording.swift:35` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (10 lines × 2) Sources/AXe/Commands/Clipboard.swift:295— Sources/AXe/Commands/Clipboard.swift:295-304 | Sources/AXe/Commands/Shutdown.swift:157-166 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (10 lines × 2) Sources/AXe/Commands/KeyCombo.swift:32— Sources/AXe/Commands/KeyCombo.swift:32-41 | Sources/AXe/Commands/KeySequence.swift:32-41 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `Sources/AXe/Commands/KeyCombo.swift:32` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (10 lines × 2) Sources/AXe/Commands/Slider.swift:351— Sources/AXe/Commands/Slider.swift:351-360 | Sources/AXe/Commands/Slider.swift:365-374 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `Sources/AXe/Commands/Slider.swift:351` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `Sources/AXe/Commands/Slider.swift:361` calls `sleep`, `seconds` and `Sources/AXe/Commands/Slider.swift:375` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
D4 · Code Duplication· Edited copy of a member (11 corresponding lines) · ×2
Edited copy of a member (11 corresponding lines) Sources/AXeCore/AgentJSON.swift:35— Packages/IDBKit/FBSimulatorControl/Commands/FBSimulatorAXSnapshot.swift:36-46 | Sources/AXeCore/AgentJSON.swift:35-52 — These two members are one piece of code written twice and then edited apart: 11 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (11 corresponding lines) Sources/AXe/Commands/Button.swift:104— Sources/AXe/Commands/Button.swift:104-114 | Sources/AXe/Utilities/SelectedButtonRequest.swift:59-70 — These two members are one piece of code written twice and then edited apart: 11 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (1 corresponding lines) · ×2
Edited copy of a member (1 corresponding lines) Sources/AXe/Utilities/HIDBroker.swift:19— Sources/AXe/Utilities/HIDBroker.swift:19-21 | Sources/AXe/Utilities/SelectedHIDProtocol.swift:301-301 — These two members are one piece of code written twice and then edited apart: 1 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (1 corresponding lines) Sources/AXe/Utilities/HIDBroker.swift:23— Sources/AXe/Utilities/HIDBroker.swift:23-25 | Sources/AXe/Utilities/SelectedHIDProtocol.swift:302-302 — These two members are one piece of code written twice and then edited apart: 1 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Duplicated block (15 lines × 2) Sources/AXe/Commands/RecordVideo.swift:63— Sources/AXe/Commands/RecordVideo.swift:63-77 | Sources/AXe/Commands/StreamVideo.swift:71-85 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `Sources/AXe/Commands/RecordVideo.swift:63` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `Sources/AXe/Commands/StreamVideo.swift:88` calls `ValidationError` and `Sources/AXe/Commands/RecordVideo.swift:78` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (15 lines × 2) scripts/fixtures/DuoHeldHardwareProbe.swift:112— scripts/fixtures/DuoHeldHardwareProbe.swift:112-126 | scripts/fixtures/DuoHeldModifierProbe.swift:113-127 — before extracting anything, compare `scripts/fixtures/DuoHeldHardwareProbe.swift` and `scripts/fixtures/DuoHeldModifierProbe.swift` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 51 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `scripts/fixtures/DuoHeldHardwareProbe.swift:112` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (9 lines × 2) Sources/AXe/Commands/RecordVideo.swift:252— Sources/AXe/Commands/RecordVideo.swift:252-260 | Sources/AXe/Commands/Screenshot.swift:195-203 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `Sources/AXe/Commands/RecordVideo.swift:252` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (9 lines × 2) AxePlaygroundApp/AxePlayground/Views/DrawingView.swift:109— AxePlaygroundApp/AxePlayground/Views/DrawingView.swift:109-117 | AxePlaygroundApp/AxePlayground/Views/SketchView.swift:182-190 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `AxePlaygroundApp/AxePlayground/Views/DrawingView.swift:109` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Low cohesion: DuoControlsTargets (LCOM4 5) AxePlaygroundApp/AxePlayground/Views/DuoControlsTargets.swift:4— DuoControlsTargets's methods fall into 5 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 5 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
Low cohesion: KeyCaptureUIView (LCOM4 5) AxePlaygroundApp/AxePlayground/Views/KeyPressView.swift:139— KeyCaptureUIView's methods fall into 5 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 5 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
Sync-over-async blocking Sources/AXe/Utilities/Batch/PhysicalDeviceBatch.swift:46— `sleep` is async and calls sleep — a blocking call inside async code stalls the cooperative pool's thread — one per core — and every task scheduled on it for as long as it runs.
Sync-over-async blocking scripts/fixtures/DuoExternalStateChange.swift:187— `send` is async and calls .wait() — a blocking call inside async code stalls the cooperative pool's thread — one per core — and every task scheduled on it for as long as it runs.
AgentModeRequest.validate (cyclomatic 300) Sources/AXe/Utilities/AgentModeProtocol.swift:39— AgentModeRequest.validate has cyclomatic complexity 300 (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.
SliderPickupReadPhase.run (cyclomatic 143) Sources/AXe/Utilities/SliderValue/SliderPickupReadPhase.swift:153— SliderPickupReadPhase.run has cyclomatic complexity 143 (threshold 15). Of this number, 141 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.
SelectedAXRequest.validate (cyclomatic 118) Sources/AXe/Utilities/SelectedAXProtocol.swift:91— SelectedAXRequest.validate has cyclomatic complexity 118 (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.
SelectedHIDRequest.validate (cyclomatic 101) Sources/AXe/Utilities/SelectedHIDProtocol.swift:98— SelectedHIDRequest.validate has cyclomatic complexity 101 (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.
AgentModeController.nativeRequest (cyclomatic 90) Sources/AXe/Utilities/AgentModeController+NativeRequest.swift:6— AgentModeController.nativeRequest has cyclomatic complexity 90 (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.
AgentModeSnapshot.init (cyclomatic 88) Sources/AXe/Utilities/AgentModeSnapshot.swift:31— AgentModeSnapshot.init has cyclomatic complexity 88 (threshold 15). Of this number, 76 points are the body's own statements and 12 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.
SelectedAXOperation.perform (cyclomatic 82) Sources/AXe/Utilities/SelectedAXOperation.swift:9— SelectedAXOperation.perform has cyclomatic complexity 82 (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.
SliderPickupHelper.prepare (cyclomatic 72) Sources/AXe/Utilities/SliderValue/SliderPickupHelper.swift:116— SliderPickupHelper.prepare has cyclomatic complexity 72 (threshold 15). Of this number, 55 points are the body's own statements and 17 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.
SelectedHIDOwner.performRequest (cyclomatic 70) Sources/AXe/Utilities/SelectedHIDOwner.swift:44— SelectedHIDOwner.performRequest has cyclomatic complexity 70 (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.
SelectedHIDPath.validate (cyclomatic 69) Sources/AXe/Utilities/SelectedHIDPath.swift:48— SelectedHIDPath.validate has cyclomatic complexity 69 (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.
SelectedHIDPath.validateOrdinary (cyclomatic 67) Sources/AXe/Utilities/SelectedHIDPath.swift:112— SelectedHIDPath.validateOrdinary has cyclomatic complexity 67 (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.
SelectedSliderValueOperation.perform (cyclomatic 67) Sources/AXe/Utilities/SliderValue/SelectedSliderValueOperation.swift:161— SelectedSliderValueOperation.perform has cyclomatic complexity 67 (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.
Tap.validate (cyclomatic 58) Sources/AXe/Commands/Tap.swift:143— Tap.validate has cyclomatic complexity 58 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
Gesture.validate (cyclomatic 56) Sources/AXe/Commands/Gesture.swift:291— Gesture.validate has cyclomatic complexity 56 (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.
AgentModeController.performReserved (cyclomatic 56) Sources/AXe/Utilities/AgentModeController.swift:104— AgentModeController.performReserved has cyclomatic complexity 56 (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.
SliderPickupRawAttributes.read (cyclomatic 54) Sources/AXe/Utilities/SliderValue/SliderPickupRawAttributes.swift:47— SliderPickupRawAttributes.read has cyclomatic complexity 54 (threshold 15). Of this number, 24 points are the body's own statements and 30 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.
RuntimeKeyboardLayout.isWellFormed (cyclomatic 51) Sources/AXe/Utilities/RuntimeKeyboardLayout.swift:157— RuntimeKeyboardLayout.isWellFormed has cyclomatic complexity 51 (threshold 15). Of this number, 45 points are the body's own statements and 6 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.
AgentModeCoarseScrollAdmission.validateIfAncestor (cyclomatic 50) Sources/AXe/Utilities/AgentModeCoarseScrollAdmission.swift:11— AgentModeCoarseScrollAdmission.validateIfAncestor has cyclomatic complexity 50 (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.
AgentModeController.performBatchReserved (cyclomatic 50) Sources/AXe/Utilities/AgentModeController+Batch.swift:97— AgentModeController.performBatchReserved has cyclomatic complexity 50 (threshold 15). Of this number, 42 points are the body's own statements and 8 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.
StreamMetadata.init (cyclomatic 47) Sources/AXe/Device/PhysicalDeviceDisplayStream.swift:310— StreamMetadata.init has cyclomatic complexity 47 (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.
HIDInputQuarantine.valid (cyclomatic 43) Sources/AXe/Utilities/HIDInputQuarantine.swift:75— HIDInputQuarantine.valid has cyclomatic complexity 43 (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.
CLIErrorMapping.failure (cyclomatic 42) Sources/AXe/Types/Errors.swift:64— CLIErrorMapping.failure has cyclomatic complexity 42 (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.
HIDInputQuarantine.persist (cyclomatic 41) Sources/AXe/Utilities/HIDInputQuarantine.swift:113— HIDInputQuarantine.persist has cyclomatic complexity 41 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
Gesture.selectedCompleteGesture (cyclomatic 40) Sources/AXe/Commands/Gesture.swift:447— Gesture.selectedCompleteGesture has cyclomatic complexity 40 (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.
Batch.validate (cyclomatic 39) Sources/AXe/Commands/Batch.swift:72— Batch.validate has cyclomatic complexity 39 (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.
DeviceAccessibilitySession.runChannel (cyclomatic 39) Sources/AXe/Device/DeviceAccessibilitySession.swift:143— DeviceAccessibilitySession.runChannel has cyclomatic complexity 39 (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.
SelectedBatchStep.request (cyclomatic 39) Sources/AXe/Utilities/Batch/SelectedBatch.swift:26— SelectedBatchStep.request has cyclomatic complexity 39 (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.
AgentModeKeyboardDetector.occlusion (cyclomatic 38) Sources/AXe/Utilities/AgentModeKeyboardObservation.swift:82— AgentModeKeyboardDetector.occlusion has cyclomatic complexity 38 (threshold 15). This file's own header attributes it to another copyright holder, so it is code this repository carries rather than code it wrote: restructuring the body in place forks it from upstream and turns every future re-sync into a manual merge. The performable moves are to leave the body as close to its upstream form as possible and keep it behind a narrow interface of your own, and to re-sync it when upstream changes — or, if it has already diverged far enough that you maintain it here, adopt it deliberately and then split the body into named stages.
AgentModeSnapshot.capture (cyclomatic 38) Sources/AXe/Utilities/AgentModeSnapshot+Capture.swift:6— AgentModeSnapshot.capture has cyclomatic complexity 38 (threshold 15). Of this number, 33 points are the body's own statements and 5 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.
AgentModeSwipePlanner.points (cyclomatic 38) Sources/AXe/Utilities/AgentModeSwipePlanner.swift:63— AgentModeSwipePlanner.points has cyclomatic complexity 38 (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.
AgentOutputProjection.compactCapture (cyclomatic 37) Sources/AXe/Utilities/AgentOutputProjection.swift:90— AgentOutputProjection.compactCapture has cyclomatic complexity 37 (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.
AgentModeKeyboardDetector.numericEvidence (cyclomatic 35) Sources/AXe/Utilities/AgentModeKeyboardObservation.swift:134— AgentModeKeyboardDetector.numericEvidence has cyclomatic complexity 35 (threshold 15). This file's own header attributes it to another copyright holder, so it is code this repository carries rather than code it wrote: restructuring the body in place forks it from upstream and turns every future re-sync into a manual merge. The performable moves are to leave the body as close to its upstream form as possible and keep it behind a narrow interface of your own, and to re-sync it when upstream changes — or, if it has already diverged far enough that you maintain it here, adopt it deliberately and then split the body into named stages.
RuntimeSnapshotBuilder.inferScrollableContainers (cyclomatic 33) Sources/AXeCore/RuntimeSnapshot.swift:501— RuntimeSnapshotBuilder.inferScrollableContainers has cyclomatic complexity 33 (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.
Page.init (cyclomatic 32) Sources/AXe/Utilities/AgentPageEnrichment.swift:116— Page.init has cyclomatic complexity 32 (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.
DescribeUI.validate (cyclomatic 30) Sources/AXe/Commands/DescribeUI.swift:58— DescribeUI.validate has cyclomatic complexity 30 (threshold 15). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
Slider.validate (cyclomatic 29) Sources/AXe/Commands/Slider.swift:59— Slider.validate 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.
Swipe.validate (cyclomatic 29) Sources/AXe/Commands/Swipe.swift:61— Swipe.validate has cyclomatic complexity 29 (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.
RemoteXPCConnection.handle (cyclomatic 29) Sources/AXe/Device/RemoteXPCConnection.swift:153— RemoteXPCConnection.handle 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.
AgentModePathAdmissionGuard.validateRelationship (cyclomatic 29) Sources/AXe/Utilities/AgentModePathAdmissionGuard.swift:152— AgentModePathAdmissionGuard.validateRelationship has cyclomatic complexity 29 (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.
CLIOutputInvocation.init (cyclomatic 29) Sources/AXe/Utilities/CLIOutputInvocation.swift:13— CLIOutputInvocation.init 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.
SelectedHIDBroker.serve (cyclomatic 29) Sources/AXe/Utilities/SelectedHIDBroker.swift:155— SelectedHIDBroker.serve 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.
SelectedSliderValueOperation.settledValue (cyclomatic 29) Sources/AXe/Utilities/SliderValue/SelectedSliderValueOperation.swift:552— SelectedSliderValueOperation.settledValue 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.
Touch.validate (cyclomatic 28) Sources/AXe/Commands/Touch.swift:49— Touch.validate has cyclomatic complexity 28 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
AgentFocusAndTypePlan.resolve (cyclomatic 28) Sources/AXe/Utilities/AgentFocusAndTypePlan.swift:45— AgentFocusAndTypePlan.resolve has cyclomatic complexity 28 (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.
SelectedHIDContract.semanticPressConfirmed (cyclomatic 28) Sources/AXe/Utilities/SelectedHIDContract.swift:65— SelectedHIDContract.semanticPressConfirmed has cyclomatic complexity 28 (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.
SelectedHIDOwner.requiresRetirement (cyclomatic 28) Sources/AXe/Utilities/SelectedHIDOwner.swift:547— SelectedHIDOwner.requiresRetirement has cyclomatic complexity 28 (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.
SelectedVideoStream.stream (cyclomatic 28) Sources/AXe/Utilities/SelectedVideoStream.swift:19— SelectedVideoStream.stream has cyclomatic complexity 28 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
Drag.validate (cyclomatic 27) Sources/AXe/Commands/Drag.swift:62— Drag.validate has cyclomatic complexity 27 (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.
ShellTokenizer.tokenize (cyclomatic 27) Sources/AXe/Utilities/ShellTokenizer.swift:25— ShellTokenizer.tokenize has cyclomatic complexity 27 (threshold 15). Of this number, 25 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.
SliderPickupHelper.readPhase (cyclomatic 27) Sources/AXe/Utilities/SliderValue/SliderPickupHelper.swift:59— SliderPickupHelper.readPhase has cyclomatic complexity 27 (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.
SimulatorClipboard.run (cyclomatic 26) Sources/AXe/Commands/Clipboard.swift:210— SimulatorClipboard.run 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.
AgentModeController.performFocusAndTypeReserved (cyclomatic 26) Sources/AXe/Utilities/AgentModeController+FocusAndType.swift:40— AgentModeController.performFocusAndTypeReserved 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.
AgentOutputProjection.completedBatch (cyclomatic 26) Sources/AXe/Utilities/AgentOutputProjection.swift:332— AgentOutputProjection.completedBatch has cyclomatic complexity 26 (threshold 15). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
PhysicalDeviceDisplay.init (cyclomatic 25) Sources/AXe/Device/PhysicalDeviceDisplay.swift:40— PhysicalDeviceDisplay.init has cyclomatic complexity 25 (threshold 15). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
SelectedHIDPinch.validate (cyclomatic 25) Sources/AXe/Utilities/SelectedHIDPinch.swift:23— SelectedHIDPinch.validate has cyclomatic complexity 25 (threshold 15). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
SliderPickupReadPhase.readGeneric (cyclomatic 25) Sources/AXe/Utilities/SliderValue/SliderPickupReadPhase.swift:513— SliderPickupReadPhase.readGeneric has cyclomatic complexity 25 (threshold 15). Of this number, 19 points are the body's own statements and 6 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.
Gesture.run (cyclomatic 24) Sources/AXe/Commands/Gesture.swift:588— Gesture.run has cyclomatic complexity 24 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
AccessibilityFetcher.isTransientPointFallback (cyclomatic 24) Sources/AXe/Utilities/AccessibilityFetcher.swift:417— AccessibilityFetcher.isTransientPointFallback has cyclomatic complexity 24 (threshold 15). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
AgentModeController.refusal (cyclomatic 24) Sources/AXe/Utilities/AgentModeController.swift:337— AgentModeController.refusal has cyclomatic complexity 24 (threshold 15). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
SelectedHIDOwner.isStateOnlyRotationFailure (cyclomatic 24) Sources/AXe/Utilities/SelectedHIDOwner.swift:516— SelectedHIDOwner.isStateOnlyRotationFailure has cyclomatic complexity 24 (threshold 15). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
SelectedHingeRequest.validate (cyclomatic 24) Sources/AXe/Utilities/SelectedHingeProtocol.swift:13— SelectedHingeRequest.validate has cyclomatic complexity 24 (threshold 15). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
SliderPickupHelper.confirm (cyclomatic 24) Sources/AXe/Utilities/SliderValue/SliderPickupHelper.swift:220— SliderPickupHelper.confirm has cyclomatic complexity 24 (threshold 15). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
AgentModeSwipePlanner.plan (cyclomatic 23) Sources/AXe/Utilities/AgentModeSwipePlanner.swift:18— AgentModeSwipePlanner.plan 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.
CLIOutputJSONParser.escapedString (cyclomatic 23) Sources/AXe/Utilities/CLIOutputValue.swift:187— CLIOutputJSONParser.escapedString 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.
SelectedHIDCompleteGesture.validate (cyclomatic 23) Sources/AXe/Utilities/SelectedHIDCompleteGesture.swift:71— SelectedHIDCompleteGesture.validate has cyclomatic complexity 23 (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.
SliderPickupReadPhase.readAXPParents (cyclomatic 23) Sources/AXe/Utilities/SliderValue/SliderPickupReadPhase.swift:443— SliderPickupReadPhase.readAXPParents 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.
SimulatorAgentRunner.run (cyclomatic 22) Sources/AXe/Agent/SimulatorAgentRunner.swift:149— SimulatorAgentRunner.run has cyclomatic complexity 22 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
Tap.validateAgent (cyclomatic 22) Sources/AXe/Commands/Tap.swift:236— Tap.validateAgent 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.
PhysicalAXTreeArchive.decode (cyclomatic 22) Sources/AXe/Device/PhysicalAXTreeArchive.swift:56— PhysicalAXTreeArchive.decode 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.
PhysicalDeviceInputOwner.perform (cyclomatic 22) Sources/AXe/Device/PhysicalDeviceInputOwner.swift:98— PhysicalDeviceInputOwner.perform has cyclomatic complexity 22 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
AgentModeSnapshot.match (cyclomatic 22) Sources/AXe/Utilities/AgentModeSnapshot.swift:437— AgentModeSnapshot.match has cyclomatic complexity 22 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
SelectedHIDContract.sliderCompleted (cyclomatic 22) Sources/AXe/Utilities/SelectedHIDContract.swift:42— SelectedHIDContract.sliderCompleted 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.
SelectedHIDPath.primitives (cyclomatic 22) Sources/AXe/Utilities/SelectedHIDPath.swift:232— SelectedHIDPath.primitives 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.
SelectedStreamFrame.encode (cyclomatic 22) Sources/AXe/Utilities/SelectedStreamFrame.swift:24— SelectedStreamFrame.encode 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.
scenes.Bento (cyclomatic 22) promo-video/src/scenes.tsx:612— scenes.Bento has cyclomatic complexity 22 (threshold 15). Most of this is not in the body itself: 1 of the 22 points is its own statement and the rest belongs to one function literal inside it that branches (line 623). 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.
AgentPageEnrichment.merge (cyclomatic 21) Sources/AXe/Utilities/AgentPageEnrichment.swift:47— AgentPageEnrichment.merge has cyclomatic complexity 21 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
HIDBroker.serve (cyclomatic 21) Sources/AXe/Utilities/HIDBroker.swift:94— HIDBroker.serve has cyclomatic complexity 21 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
Gesture.validateAgentGesture (cyclomatic 20) Sources/AXe/Commands/Gesture.swift:490— Gesture.validateAgentGesture has cyclomatic complexity 20 (threshold 15). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
VisibleTree.target (cyclomatic 20) Sources/AXe/Commands/PhysicalAccessibilityCommands.swift:181— VisibleTree.target has cyclomatic complexity 20 (threshold 15). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
RemoteXPCReader.readObject (cyclomatic 20) Sources/AXe/Device/RemoteXPCWire.swift:308— RemoteXPCReader.readObject has cyclomatic complexity 20 (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.
AgentModeKeyboardDetector.numericOcclusion (cyclomatic 20) Sources/AXe/Utilities/AgentModeKeyboardObservation.swift:169— AgentModeKeyboardDetector.numericOcclusion has cyclomatic complexity 20 (threshold 15). This file's own header attributes it to another copyright holder, so it is code this repository carries rather than code it wrote: restructuring the body in place forks it from upstream and turns every future re-sync into a manual merge. The performable moves are to leave the body as close to its upstream form as possible and keep it behind a narrow interface of your own, and to re-sync it when upstream changes — or, if it has already diverged far enough that you maintain it here, adopt it deliberately and then split the body into named stages.
HIDBroker.connectToReadyBroker (cyclomatic 20) Sources/AXe/Utilities/HIDBroker.swift:435— HIDBroker.connectToReadyBroker has cyclomatic complexity 20 (threshold 15). Of this number, 19 points are the body's own statements and 1 belongs to one function item inside it that branches. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
KeyboardPrimitives.validate (cyclomatic 20) Sources/AXe/Utilities/SelectedKeyboardProtocol.swift:103— KeyboardPrimitives.validate 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.
SelectedOpaqueFrameTapAdmission.validate (cyclomatic 20) Sources/AXe/Utilities/SelectedOpaqueFrameTapAdmission.swift:18— SelectedOpaqueFrameTapAdmission.validate has cyclomatic complexity 20 (threshold 15). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
RuntimeSnapshotBuilder.deriveRole (cyclomatic 20) Sources/AXeCore/RuntimeSnapshot.swift:345— RuntimeSnapshotBuilder.deriveRole has cyclomatic complexity 20 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
StreamVideo.validate (cyclomatic 19) Sources/AXe/Commands/StreamVideo.swift:58— StreamVideo.validate 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.
AgentBatchStep.validate (cyclomatic 19) Sources/AXe/Utilities/AgentBatchProtocol.swift:63— AgentBatchStep.validate 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.
AgentModeNativeOperation.perform (cyclomatic 19) Sources/AXe/Utilities/AgentModeNativeOperation.swift:8— AgentModeNativeOperation.perform 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.
AgentOutputProjection.project (cyclomatic 19) Sources/AXe/Utilities/AgentOutputProjection.swift:26— AgentOutputProjection.project 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.
CLIOutputJSONParser.number (cyclomatic 19) Sources/AXe/Utilities/CLIOutputValue.swift:276— CLIOutputJSONParser.number 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.
SelectedHIDOwner.performOrdinaryTouch (cyclomatic 19) Sources/AXe/Utilities/SelectedHIDOwner.swift:194— SelectedHIDOwner.performOrdinaryTouch 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.
SelectedHIDRequest.validate (cyclomatic 19) Sources/AXe/Utilities/SelectedHIDProtocol.swift:245— SelectedHIDRequest.validate has cyclomatic complexity 19 (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.
SliderPickupReadChild.close (cyclomatic 19) Sources/AXe/Utilities/SliderValue/SliderPickupReadChild.swift:123— SliderPickupReadChild.close 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.
AgentPolicy.prepareRequest (cyclomatic 19) Sources/AXeCore/AgentPolicy.swift:13— AgentPolicy.prepareRequest 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.
Gesture.validateAgentPinch (cyclomatic 18) Sources/AXe/Commands/Gesture.swift:512— Gesture.validateAgentPinch 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.
PhysicalAccessibilityCommands.tap (cyclomatic 18) Sources/AXe/Commands/PhysicalAccessibilityCommands.swift:43— PhysicalAccessibilityCommands.tap has cyclomatic complexity 18 (threshold 15). Of this number, 16 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.
RecordVideo.validate (cyclomatic 18) Sources/AXe/Commands/RecordVideo.swift:51— RecordVideo.validate 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.
DeviceAccessibilitySession.request (cyclomatic 18) Sources/AXe/Device/DeviceAccessibilitySession.swift:68— DeviceAccessibilitySession.request 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.
PhysicalDeviceBrokerClient.connectToWorker (cyclomatic 18) Sources/AXe/Device/PhysicalDeviceBrokerClient.swift:116— PhysicalDeviceBrokerClient.connectToWorker has cyclomatic complexity 18 (threshold 15). Of this number, 10 points are the body's own statements and 8 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.
PhysicalDeviceBrokerOperation.validate (cyclomatic 18) Sources/AXe/Device/PhysicalDeviceBrokerProtocol.swift:31— PhysicalDeviceBrokerOperation.validate 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.
PhysicalDisplayRTCP.observe (cyclomatic 18) Sources/AXe/Device/PhysicalDisplayRTCP.swift:28— PhysicalDisplayRTCP.observe 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.
AgentModeController.performBatchRetrying (cyclomatic 18) Sources/AXe/Utilities/AgentModeController+Batch.swift:8— AgentModeController.performBatchRetrying 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.
AgentModeSnapshot.physicalButtonExecutionTarget (cyclomatic 18) Sources/AXe/Utilities/AgentModeSnapshot.swift:318— AgentModeSnapshot.physicalButtonExecutionTarget 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.
AgentOutputProjection.addingScrollPreview (cyclomatic 18) Sources/AXe/Utilities/AgentOutputProjection.swift:187— AgentOutputProjection.addingScrollPreview 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.
CLIOutputText.agent (cyclomatic 18) Sources/AXe/Utilities/CLIOutputText.swift:18— CLIOutputText.agent 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.
SliderPickupReadChild.run (cyclomatic 18) Sources/AXe/Utilities/SliderValue/SliderPickupReadChild.swift:68— SliderPickupReadChild.run has cyclomatic complexity 18 (threshold 15). Of this number, 16 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.
Axe.formattedOutput (cyclomatic 17) Sources/AXe/main.swift:92— Axe.formattedOutput 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.
Touch.run (cyclomatic 17) Sources/AXe/Commands/Touch.swift:153— Touch.run 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.
Type.validate (cyclomatic 17) Sources/AXe/Commands/Type.swift:47— Type.validate 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.
PhysicalDeviceMedia.stream (cyclomatic 17) Sources/AXe/Device/PhysicalDeviceMedia.swift:26— PhysicalDeviceMedia.stream 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.
AgentModeController.reboundSteps (cyclomatic 17) Sources/AXe/Utilities/AgentModeController+Batch.swift:59— AgentModeController.reboundSteps has cyclomatic complexity 17 (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.
Recovery.canRecover (cyclomatic 17) Sources/AXe/Utilities/FollowActiveVideoRecording.swift:150— Recovery.canRecover 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.
HIDInputQuarantine.requireClear (cyclomatic 17) Sources/AXe/Utilities/HIDInputQuarantine.swift:45— HIDInputQuarantine.requireClear 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.
SelectedButtonExecutionEvidence.completed (cyclomatic 17) Sources/AXe/Utilities/SelectedHIDContract.swift:84— SelectedButtonExecutionEvidence.completed 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.
SelectedHIDPath.event (cyclomatic 17) Sources/AXe/Utilities/SelectedHIDPath.swift:169— SelectedHIDPath.event 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.
BatchPlanRunner.run (cyclomatic 17) Sources/AXe/Utilities/Batch/BatchPlanRunner.swift:21— BatchPlanRunner.run has cyclomatic complexity 17 (threshold 15). Of this number, 15 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.
SliderPickupRawAttributes.runtimeID (cyclomatic 17) Sources/AXe/Utilities/SliderValue/SliderPickupRawAttributes.swift:20— SliderPickupRawAttributes.runtimeID 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.
SimulatorAgentExecutor.execute (cyclomatic 16) Sources/AXe/Agent/SimulatorAgentExecutor.swift:26— SimulatorAgentExecutor.execute 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.
Slider.performOwnedSlider (cyclomatic 16) Sources/AXe/Commands/Slider.swift:268— Slider.performOwnedSlider 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.
StreamVideo.run (cyclomatic 16) Sources/AXe/Commands/StreamVideo.swift:92— StreamVideo.run 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.
StreamVideo.streamCompressedFrames (cyclomatic 16) Sources/AXe/Commands/StreamVideo.swift:153— StreamVideo.streamCompressedFrames 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.
Swipe.run (cyclomatic 16) Sources/AXe/Commands/Swipe.swift:187— Swipe.run 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.
VideoFrameUtilities.processJPEGData (cyclomatic 16) Sources/AXe/Commands/VideoCommandSupport.swift:107— VideoFrameUtilities.processJPEGData 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.
DeviceDTXMessage.read (cyclomatic 16) Sources/AXe/Device/DeviceDTXMessage.swift:21— DeviceDTXMessage.read 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.
H264RTPDepacketizer.finishUnit (cyclomatic 16) Sources/AXe/Device/H264RTPDepacketizer.swift:137— H264RTPDepacketizer.finishUnit 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.
PhysicalAXTreeArchive.shape (cyclomatic 16) Sources/AXe/Device/PhysicalAXTreeArchive.swift:112— PhysicalAXTreeArchive.shape has cyclomatic complexity 16 (threshold 15). Of this number, 12 points are the body's own statements and 4 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.
PhysicalDeviceBrokerOwner.perform (cyclomatic 16) Sources/AXe/Device/PhysicalDeviceBrokerOwner.swift:111— PhysicalDeviceBrokerOwner.perform has cyclomatic complexity 16 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function so the top-level body reads as a short sequence of named decisions.
PhysicalDeviceInputOwner.rotate (cyclomatic 16) Sources/AXe/Device/PhysicalDeviceInputOwner.swift:217— PhysicalDeviceInputOwner.rotate 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.
PhysicalDisplayUDPReceiver.receive (cyclomatic 16) Sources/AXe/Device/PhysicalDisplayUDPReceiver.swift:99— PhysicalDisplayUDPReceiver.receive 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.
AgentModeRequest.validateKeySequence (cyclomatic 16) Sources/AXe/Utilities/AgentModeProtocol.swift:237— AgentModeRequest.validateKeySequence 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.
HIDBroker.ensurePrivateDirectory (cyclomatic 16) Sources/AXe/Utilities/HIDBroker.swift:369— HIDBroker.ensurePrivateDirectory 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.
RuntimeKeyboardLayout.init (cyclomatic 16) Sources/AXe/Utilities/RuntimeKeyboardLayout.swift:51— RuntimeKeyboardLayout.init 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.
SimulatorKeyboardSettings.activeHardwareLayout (cyclomatic 16) Sources/AXe/Utilities/RuntimeKeyboardLayout.swift:258— SimulatorKeyboardSettings.activeHardwareLayout 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.
SelectedHIDPrimitive.validate (cyclomatic 16) Sources/AXe/Utilities/SelectedHIDProtocol.swift:303— SelectedHIDPrimitive.validate 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.
BatchStandardInput.read (cyclomatic 16) Sources/AXe/Utilities/Batch/BatchStandardInput.swift:8— BatchStandardInput.read has cyclomatic complexity 16 (threshold 15). Of this number, 13 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.
SelectedBatchRunner.run (cyclomatic 16) Sources/AXe/Utilities/Batch/SelectedBatch.swift:233— SelectedBatchRunner.run 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.
AgentPolicy.resolveDecision (cyclomatic 16) Sources/AXeCore/AgentPolicy.swift:258— AgentPolicy.resolveDecision 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.
AgentTextCandidateExtractor.candidates (cyclomatic 16) Sources/AXeCore/AgentPolicy.swift:476— AgentTextCandidateExtractor.candidates 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.
AgentModeRequest.validate (cognitive 322) Sources/AXe/Utilities/AgentModeProtocol.swift:39— AgentModeRequest.validate has cognitive complexity 322 (threshold 15). Drivers by points: boolean chains 247, if/else 51 (73 pts), ternaries 1 (2 pts) (nesting depth added 23). 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.
SliderPickupReadPhase.run (cognitive 225) Sources/AXe/Utilities/SliderValue/SliderPickupReadPhase.swift:153— SliderPickupReadPhase.run has cognitive complexity 225 (threshold 15). Drivers by points: if/else 45 (113 pts), boolean chains 90, ternaries 6 (16 pts), error handling 2, loops 1 (2 pts), match/switch 1 (2 pts) (nesting depth added 80). Of this number, 220 points are the body's own statements and 5 belong to 2 function items inside it that branch. To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
SelectedAXOperation.perform (cognitive 172) Sources/AXe/Utilities/SelectedAXOperation.swift:9— SelectedAXOperation.perform has cognitive complexity 172 (threshold 15). Drivers by points: if/else 58 (129 pts), boolean chains 18, ternaries 6 (15 pts), match/switch 2 (6 pts), error handling 2 (4 pts) (nesting depth added 86). 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.
SelectedAXRequest.validate (cognitive 122) Sources/AXe/Utilities/SelectedAXProtocol.swift:91— SelectedAXRequest.validate has cognitive complexity 122 (threshold 15). Drivers by points: boolean chains 84, if/else 25 (37 pts), match/switch 1 (nesting depth added 12). 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.
SelectedHIDRequest.validate (cognitive 122) Sources/AXe/Utilities/SelectedHIDProtocol.swift:98— SelectedHIDRequest.validate has cognitive complexity 122 (threshold 15). Drivers by points: if/else 41 (65 pts), boolean chains 46, match/switch 5 (8 pts), loops 1 (3 pts) (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.
SelectedHIDOwner.performRequest (cognitive 118) Sources/AXe/Utilities/SelectedHIDOwner.swift:44— SelectedHIDOwner.performRequest has cognitive complexity 118 (threshold 15). Drivers by points: if/else 35 (82 pts), boolean chains 26, error handling 5 (8 pts), match/switch 1 (2 pts) (nesting depth added 51). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
AgentModeController.nativeRequest (cognitive 109) Sources/AXe/Utilities/AgentModeController+NativeRequest.swift:6— AgentModeController.nativeRequest has cognitive complexity 109 (threshold 15). Drivers by points: if/else 39 (61 pts), boolean chains 38, match/switch 3 (6 pts), ternaries 2 (4 pts) (nesting depth added 27). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
AgentModeController.performReserved (cognitive 101) Sources/AXe/Utilities/AgentModeController.swift:104— AgentModeController.performReserved has cognitive complexity 101 (threshold 15). Drivers by points: if/else 31 (63 pts), boolean chains 26, error handling 4 (9 pts), ternaries 1 (3 pts) (nesting depth added 39). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
AgentModeController.performBatchReserved (cognitive 101) Sources/AXe/Utilities/AgentModeController+Batch.swift:97— AgentModeController.performBatchReserved has cognitive complexity 101 (threshold 15). Drivers by points: if/else 25 (68 pts), ternaries 10 (16 pts), boolean chains 13, error handling 2, loops 1 (2 pts) (nesting depth added 50). Of this number, 93 points are the body's own statements and 8 belong to one function item inside it that branches. To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
AgentModeSnapshot.init (cognitive 93) Sources/AXe/Utilities/AgentModeSnapshot.swift:31— AgentModeSnapshot.init has cognitive complexity 93 (threshold 15). Drivers by points: boolean chains 68, if/else 14 (17 pts), ternaries 4, loops 2 (3 pts), error handling 1 (nesting depth added 4). Of this number, 81 points are the body's own statements and 12 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.
SelectedSliderValueOperation.perform (cognitive 81) Sources/AXe/Utilities/SliderValue/SelectedSliderValueOperation.swift:161— SelectedSliderValueOperation.perform has cognitive complexity 81 (threshold 15). Drivers by points: if/else 27 (41 pts), boolean chains 37, loops 1, match/switch 1, ternaries 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.
RuntimeKeyboardLayout.isWellFormed (cognitive 78) Sources/AXe/Utilities/RuntimeKeyboardLayout.swift:157— RuntimeKeyboardLayout.isWellFormed has cognitive complexity 78 (threshold 15). Drivers by points: if/else 15 (35 pts), boolean chains 30, loops 4 (9 pts), ternaries 1 (4 pts) (nesting depth added 28). Of this number, 72 points are the body's own statements and 6 belong to 3 function items inside it that branch. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
SelectedHIDPath.validate (cognitive 78) Sources/AXe/Utilities/SelectedHIDPath.swift:48— SelectedHIDPath.validate has cognitive complexity 78 (threshold 15). Drivers by points: boolean chains 49, if/else 18 (25 pts), error handling 1 (2 pts), loops 1, ternaries 1 (nesting depth added 8). 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.
Tap.validate (cognitive 77) Sources/AXe/Commands/Tap.swift:143— Tap.validate has cognitive complexity 77 (threshold 15). Drivers by points: if/else 29 (47 pts), boolean chains 30 (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.
SliderPickupHelper.prepare (cognitive 74) Sources/AXe/Utilities/SliderValue/SliderPickupHelper.swift:116— SliderPickupHelper.prepare has cognitive complexity 74 (threshold 15). Drivers by points: boolean chains 55, if/else 17 (19 pts) (nesting depth added 2). Of this number, 57 points are the body's own statements and 17 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.
SelectedHIDPath.validateOrdinary (cognitive 72) Sources/AXe/Utilities/SelectedHIDPath.swift:112— SelectedHIDPath.validateOrdinary has cognitive complexity 72 (threshold 15). Drivers by points: boolean chains 55, if/else 12 (17 pts) (nesting depth added 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.
Gesture.validate (cognitive 68) Sources/AXe/Commands/Gesture.swift:291— Gesture.validate has cognitive complexity 68 (threshold 15). Drivers by points: if/else 26 (41 pts), boolean chains 26, match/switch 1 (nesting depth added 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
SelectedHIDBroker.serve (cognitive 63) Sources/AXe/Utilities/SelectedHIDBroker.swift:155— SelectedHIDBroker.serve has cognitive complexity 63 (threshold 15). Drivers by points: if/else 13 (33 pts), ternaries 3 (13 pts), boolean chains 8, loops 3 (5 pts), error handling 2 (4 pts) (nesting depth added 34). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
DeviceAccessibilitySession.runChannel (cognitive 59) Sources/AXe/Device/DeviceAccessibilitySession.swift:143— DeviceAccessibilitySession.runChannel has cognitive complexity 59 (threshold 15). Drivers by points: if/else 17 (36 pts), boolean chains 18, ternaries 2 (4 pts), loops 1 (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.
SelectedVideoStream.stream (cognitive 56) Sources/AXe/Utilities/SelectedVideoStream.swift:19— SelectedVideoStream.stream has cognitive complexity 56 (threshold 15). Drivers by points: if/else 13 (33 pts), ternaries 4 (9 pts), boolean chains 6, error handling 2 (4 pts), loops 2 (4 pts) (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.
AgentModeCoarseScrollAdmission.validateIfAncestor (cognitive 55) Sources/AXe/Utilities/AgentModeCoarseScrollAdmission.swift:11— AgentModeCoarseScrollAdmission.validateIfAncestor has cognitive complexity 55 (threshold 15). Drivers by points: boolean chains 37, if/else 10 (16 pts), loops 2 (nesting depth added 6). 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.
SliderPickupRawAttributes.read (cognitive 54) Sources/AXe/Utilities/SliderValue/SliderPickupRawAttributes.swift:47— SliderPickupRawAttributes.read has cognitive complexity 54 (threshold 15). Drivers by points: boolean chains 38, if/else 16. Of this number, 23 points are the body's own statements and 31 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.
SelectedSliderValueOperation.settledValue (cognitive 53) Sources/AXe/Utilities/SliderValue/SelectedSliderValueOperation.swift:552— SelectedSliderValueOperation.settledValue has cognitive complexity 53 (threshold 15). Drivers by points: if/else 13 (28 pts), ternaries 6 (14 pts), boolean chains 8, error handling 1 (2 pts), loops 1 (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.
ShellTokenizer.tokenize (cognitive 51) Sources/AXe/Utilities/ShellTokenizer.swift:25— ShellTokenizer.tokenize has cognitive complexity 51 (threshold 15). Drivers by points: if/else 17 (43 pts), boolean chains 4, match/switch 2 (3 pts), loops 1 (nesting depth added 27). Of this number, 49 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.
HIDBroker.serve (cognitive 50) Sources/AXe/Utilities/HIDBroker.swift:94— HIDBroker.serve has cognitive complexity 50 (threshold 15). Drivers by points: if/else 12 (35 pts), error handling 4 (10 pts), boolean chains 3, loops 1 (2 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.
HIDInputQuarantine.persist (cognitive 50) Sources/AXe/Utilities/HIDInputQuarantine.swift:113— HIDInputQuarantine.persist has cognitive complexity 50 (threshold 15). Drivers by points: if/else 19 (25 pts), boolean chains 20, ternaries 2 (4 pts), loops 1 (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
AgentModeSnapshot.capture (cognitive 47) Sources/AXe/Utilities/AgentModeSnapshot+Capture.swift:6— AgentModeSnapshot.capture has cognitive complexity 47 (threshold 15). Drivers by points: boolean chains 21, if/else 9 (17 pts), ternaries 6, loops 2 (3 pts) (nesting depth added 9). Of this number, 42 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.
StreamMetadata.init (cognitive 46) Sources/AXe/Device/PhysicalDeviceDisplayStream.swift:310— StreamMetadata.init has cognitive complexity 46 (threshold 15). Drivers by points: boolean chains 43, if/else 2, ternaries 1. To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
AgentModeSwipePlanner.points (cognitive 45) Sources/AXe/Utilities/AgentModeSwipePlanner.swift:63— AgentModeSwipePlanner.points has cognitive complexity 45 (threshold 15). Drivers by points: boolean chains 25, if/else 12 (19 pts), loops 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.
AgentPageEnrichment.merge (cognitive 45) Sources/AXe/Utilities/AgentPageEnrichment.swift:47— AgentPageEnrichment.merge has cognitive complexity 45 (threshold 15). Drivers by points: if/else 11 (30 pts), loops 7 (13 pts), boolean chains 2 (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.
AgentOutputProjection.compactCapture (cognitive 44) Sources/AXe/Utilities/AgentOutputProjection.swift:90— AgentOutputProjection.compactCapture has cognitive complexity 44 (threshold 15). Drivers by points: boolean chains 22, if/else 13 (20 pts), loops 2 (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.
CLIOutputInvocation.init (cognitive 44) Sources/AXe/Utilities/CLIOutputInvocation.swift:13— CLIOutputInvocation.init has cognitive complexity 44 (threshold 15). Drivers by points: if/else 12 (25 pts), boolean chains 13, ternaries 3 (5 pts), loops 1 (nesting depth added 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
RuntimeSnapshotBuilder.inferScrollableContainers (cognitive 44) Sources/AXeCore/RuntimeSnapshot.swift:501— RuntimeSnapshotBuilder.inferScrollableContainers has cognitive complexity 44 (threshold 15). Drivers by points: boolean chains 19, if/else 7 (17 pts), loops 6 (8 pts) (nesting depth added 12). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
Batch.validate (cognitive 43) Sources/AXe/Commands/Batch.swift:72— Batch.validate has cognitive complexity 43 (threshold 15). Drivers by points: boolean chains 24, if/else 13 (17 pts), ternaries 1 (2 pts) (nesting depth added 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.
SimulatorClipboard.run (cognitive 43) Sources/AXe/Commands/Clipboard.swift:210— SimulatorClipboard.run has cognitive complexity 43 (threshold 15). Drivers by points: if/else 11 (29 pts), boolean chains 9, loops 3, error handling 1, ternaries 1 (nesting depth added 18). 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.
RemoteXPCConnection.handle (cognitive 43) Sources/AXe/Device/RemoteXPCConnection.swift:153— RemoteXPCConnection.handle has cognitive complexity 43 (threshold 15). Drivers by points: if/else 12 (29 pts), boolean chains 8, loops 1 (3 pts), match/switch 2 (3 pts) (nesting depth added 20). 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.
AgentModeKeyboardDetector.numericEvidence (cognitive 43) Sources/AXe/Utilities/AgentModeKeyboardObservation.swift:134— AgentModeKeyboardDetector.numericEvidence has cognitive complexity 43 (threshold 15). Drivers by points: boolean chains 24, if/else 7 (15 pts), loops 2 (3 pts), ternaries 1 (nesting depth added 9). This file's own header attributes it to another copyright holder, so it is code this repository carries rather than code it wrote: restructuring the body in place forks it from upstream and turns every future re-sync into a manual merge. The performable moves are to leave the body as close to its upstream form as possible and keep it behind a narrow interface of your own, and to re-sync it when upstream changes — or, if it has already diverged far enough that you maintain it here, adopt it deliberately and then split the body into named stages.
HIDInputQuarantine.valid (cognitive 43) Sources/AXe/Utilities/HIDInputQuarantine.swift:75— HIDInputQuarantine.valid has cognitive complexity 43 (threshold 15). Drivers by points: boolean chains 35, if/else 7 (8 pts) (nesting depth added 1). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
Gesture.selectedCompleteGesture (cognitive 42) Sources/AXe/Commands/Gesture.swift:447— Gesture.selectedCompleteGesture has cognitive complexity 42 (threshold 15). Drivers by points: boolean chains 27, if/else 7 (14 pts), match/switch 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.
AgentModeKeyboardDetector.occlusion (cognitive 42) Sources/AXe/Utilities/AgentModeKeyboardObservation.swift:82— AgentModeKeyboardDetector.occlusion has cognitive complexity 42 (threshold 15). Drivers by points: boolean chains 27, if/else 8 (13 pts), loops 2 (nesting depth added 5). This file's own header attributes it to another copyright holder, so it is code this repository carries rather than code it wrote: restructuring the body in place forks it from upstream and turns every future re-sync into a manual merge. The performable moves are to leave the body as close to its upstream form as possible and keep it behind a narrow interface of your own, and to re-sync it when upstream changes — or, if it has already diverged far enough that you maintain it here, adopt it deliberately and then split the body into named stages.
SimulatorAgentRunner.run (cognitive 41) Sources/AXe/Agent/SimulatorAgentRunner.swift:149— SimulatorAgentRunner.run has cognitive complexity 41 (threshold 15). Drivers by points: if/else 14 (25 pts), ternaries 3 (9 pts), boolean chains 6, loops 1 (nesting depth added 17). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
AgentModeController.performFocusAndTypeReserved (cognitive 40) Sources/AXe/Utilities/AgentModeController+FocusAndType.swift:40— AgentModeController.performFocusAndTypeReserved has cognitive complexity 40 (threshold 15). Drivers by points: if/else 9 (22 pts), boolean chains 7, ternaries 6, loops 2 (4 pts), error handling 1 (nesting depth added 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
CLIErrorMapping.failure (cognitive 38) Sources/AXe/Types/Errors.swift:64— CLIErrorMapping.failure has cognitive complexity 38 (threshold 15). Drivers by points: if/else 13 (24 pts), match/switch 7 (13 pts), boolean chains 1 (nesting depth added 17). 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.
SelectedBatchStep.request (cognitive 37) Sources/AXe/Utilities/Batch/SelectedBatch.swift:26— SelectedBatchStep.request has cognitive complexity 37 (threshold 15). Drivers by points: if/else 16 (27 pts), boolean chains 7, match/switch 2 (3 pts) (nesting depth added 12). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
DescribeUI.validate (cognitive 36) Sources/AXe/Commands/DescribeUI.swift:58— DescribeUI.validate has cognitive complexity 36 (threshold 15). Drivers by points: boolean chains 18, if/else 11 (18 pts) (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.
SelectedHIDOwner.performOrdinaryTouch (cognitive 35) Sources/AXe/Utilities/SelectedHIDOwner.swift:194— SelectedHIDOwner.performOrdinaryTouch has cognitive complexity 35 (threshold 15). Drivers by points: if/else 13 (26 pts), boolean chains 5, ternaries 1 (3 pts), error handling 1 (nesting depth added 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
Slider.validate (cognitive 34) Sources/AXe/Commands/Slider.swift:59— Slider.validate has cognitive complexity 34 (threshold 15). Drivers by points: if/else 15 (20 pts), boolean chains 14 (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.
PhysicalDeviceMedia.stream (cognitive 34) Sources/AXe/Device/PhysicalDeviceMedia.swift:26— PhysicalDeviceMedia.stream has cognitive complexity 34 (threshold 15). Drivers by points: if/else 7 (17 pts), ternaries 3 (7 pts), error handling 2 (4 pts), loops 2 (4 pts), boolean chains 2 (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.
AgentModeNativeOperation.perform (cognitive 34) Sources/AXe/Utilities/AgentModeNativeOperation.swift:8— AgentModeNativeOperation.perform has cognitive complexity 34 (threshold 15). Drivers by points: if/else 15 (24 pts), error handling 3 (6 pts), boolean chains 2, ternaries 1 (2 pts) (nesting depth added 13). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
Swipe.validate (cognitive 32) Sources/AXe/Commands/Swipe.swift:61— Swipe.validate has cognitive complexity 32 (threshold 15). Drivers by points: if/else 16 (20 pts), boolean chains 12 (nesting depth added 4). 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.
Touch.validate (cognitive 32) Sources/AXe/Commands/Touch.swift:49— Touch.validate has cognitive complexity 32 (threshold 15). Drivers by points: if/else 13 (18 pts), boolean chains 14 (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.
Page.init (cognitive 32) Sources/AXe/Utilities/AgentPageEnrichment.swift:116— Page.init has cognitive complexity 32 (threshold 15). Drivers by points: boolean chains 25, if/else 4 (5 pts), loops 1, ternaries 1 (nesting depth added 1). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
SelectedBatchRunner.run (cognitive 32) Sources/AXe/Utilities/Batch/SelectedBatch.swift:233— SelectedBatchRunner.run has cognitive complexity 32 (threshold 15). Drivers by points: ternaries 6 (16 pts), if/else 3 (8 pts), error handling 2 (4 pts), match/switch 1 (2 pts), boolean chains 1, 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.
Drag.validate (cognitive 31) Sources/AXe/Commands/Drag.swift:62— Drag.validate has cognitive complexity 31 (threshold 15). Drivers by points: if/else 16 (21 pts), boolean chains 10 (nesting depth added 5). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition.
AgentModePathAdmissionGuard.validateRelationship (cognitive 30) Sources/AXe/Utilities/AgentModePathAdmissionGuard.swift:152— AgentModePathAdmissionGuard.validateRelationship has cognitive complexity 30 (threshold 15). Drivers by points: boolean chains 17, if/else 12 (13 pts) (nesting depth added 1). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
AgentModeSnapshot.match (cognitive 30) Sources/AXe/Utilities/AgentModeSnapshot.swift:437— AgentModeSnapshot.match has cognitive complexity 30 (threshold 15). Drivers by points: if/else 8 (16 pts), boolean chains 9, match/switch 2 (4 pts), loops 1 (nesting depth added 10). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
AgentFocusAndTypePlan.resolve (cognitive 29) Sources/AXe/Utilities/AgentFocusAndTypePlan.swift:45— AgentFocusAndTypePlan.resolve has cognitive complexity 29 (threshold 15). Drivers by points: boolean chains 17, if/else 9 (11 pts), ternaries 1 (nesting depth added 2). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
CLIOutputJSONParser.escapedString (cognitive 29) Sources/AXe/Utilities/CLIOutputValue.swift:187— CLIOutputJSONParser.escapedString has cognitive complexity 29 (threshold 15). Drivers by points: if/else 9 (20 pts), boolean chains 3, loops 2 (3 pts), match/switch 1 (3 pts) (nesting depth added 14). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
SliderPickupReadPhase.readAXPParents (cognitive 29) Sources/AXe/Utilities/SliderValue/SliderPickupReadPhase.swift:443— SliderPickupReadPhase.readAXPParents has cognitive complexity 29 (threshold 15). Drivers by points: boolean chains 15, if/else 6 (13 pts), loops 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.
AgentModeKeyboardDetector.observe (cognitive 28) Sources/AXe/Utilities/AgentModeKeyboardObservation.swift:218— AgentModeKeyboardDetector.observe has cognitive complexity 28 (threshold 15). Drivers by points: if/else 8 (21 pts), boolean chains 5, loops 1 (2 pts) (nesting depth added 14). This file's own header attributes it to another copyright holder, so it is code this repository carries rather than code it wrote: restructuring the body in place forks it from upstream and turns every future re-sync into a manual merge. The performable moves are to leave the body as close to its upstream form as possible and keep it behind a narrow interface of your own, and to re-sync it when upstream changes — or, if it has already diverged far enough that you maintain it here, adopt it deliberately and then split the body into named stages.
HIDBroker.connectToReadyBroker (cognitive 28) Sources/AXe/Utilities/HIDBroker.swift:435— HIDBroker.connectToReadyBroker has cognitive complexity 28 (threshold 15). Drivers by points: if/else 11 (18 pts), boolean chains 4, error handling 3 (4 pts), loops 1, ternaries 1 (nesting depth added 8). Of this number, 27 points are the body's own statements and 1 belongs to one function item inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
PhysicalDeviceInputOwner.perform (cognitive 27) Sources/AXe/Device/PhysicalDeviceInputOwner.swift:98— PhysicalDeviceInputOwner.perform has cognitive complexity 27 (threshold 15). Drivers by points: if/else 11 (16 pts), boolean chains 7, loops 1 (2 pts), error handling 1, match/switch 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.
PhysicalDisplayRTCP.observe (cognitive 27) Sources/AXe/Device/PhysicalDisplayRTCP.swift:28— PhysicalDisplayRTCP.observe has cognitive complexity 27 (threshold 15). Drivers by points: if/else 10 (20 pts), boolean chains 7 (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.
AgentModePathAdmissionGuard.validate (cognitive 27) Sources/AXe/Utilities/AgentModePathAdmissionGuard.swift:60— AgentModePathAdmissionGuard.validate has cognitive complexity 27 (threshold 15). Drivers by points: if/else 8 (15 pts), loops 3 (6 pts), match/switch 1 (3 pts), boolean chains 2, error handling 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.
SelectedHIDContract.semanticPressConfirmed (cognitive 27) Sources/AXe/Utilities/SelectedHIDContract.swift:65— SelectedHIDContract.semanticPressConfirmed has cognitive complexity 27 (threshold 15). Drivers by points: boolean chains 26, if/else 1. To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
SelectedHIDOwner.requiresRetirement (cognitive 27) Sources/AXe/Utilities/SelectedHIDOwner.swift:547— SelectedHIDOwner.requiresRetirement has cognitive complexity 27 (threshold 15). Drivers by points: boolean chains 26, if/else 1. To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
SelectedHingeRequest.validate (cognitive 27) Sources/AXe/Utilities/SelectedHingeProtocol.swift:13— SelectedHingeRequest.validate has cognitive complexity 27 (threshold 15). Drivers by points: boolean chains 15, if/else 6 (11 pts), match/switch 1 (nesting depth added 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.
KeyboardPrimitives.validate (cognitive 27) Sources/AXe/Utilities/SelectedKeyboardProtocol.swift:103— KeyboardPrimitives.validate has cognitive complexity 27 (threshold 15). Drivers by points: if/else 6 (13 pts), boolean chains 8, ternaries 1 (3 pts), match/switch 1 (2 pts), loops 1 (nesting depth added 10). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
BatchStandardInput.read (cognitive 27) Sources/AXe/Utilities/Batch/BatchStandardInput.swift:8— BatchStandardInput.read has cognitive complexity 27 (threshold 15). Drivers by points: if/else 10 (21 pts), boolean chains 3, loops 2 (3 pts) (nesting depth added 12). Of this number, 24 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.
SliderPickupHelper.readPhase (cognitive 27) Sources/AXe/Utilities/SliderValue/SliderPickupHelper.swift:59— SliderPickupHelper.readPhase has cognitive complexity 27 (threshold 15). Drivers by points: boolean chains 21, if/else 5 (6 pts) (nesting depth added 1). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
SliderPickupReadPhase.readGeneric (cognitive 27) Sources/AXe/Utilities/SliderValue/SliderPickupReadPhase.swift:513— SliderPickupReadPhase.readGeneric has cognitive complexity 27 (threshold 15). Drivers by points: boolean chains 10, if/else 10, error handling 1 (3 pts), loops 2 (3 pts), ternaries 1 (nesting depth added 3). Of this number, 21 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.
Gesture.run (cognitive 26) Sources/AXe/Commands/Gesture.swift:588— Gesture.run has cognitive complexity 26 (threshold 15). Drivers by points: if/else 12 (15 pts), boolean chains 9, match/switch 1 (2 pts) (nesting depth added 4). 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.
PhysicalDeviceBrokerServer.listen (cognitive 26) Sources/AXe/Device/PhysicalDeviceBrokerServer.swift:38— PhysicalDeviceBrokerServer.listen has cognitive complexity 26 (threshold 15). Drivers by points: if/else 6 (16 pts), boolean chains 4, ternaries 1 (3 pts), loops 1 (2 pts), error handling 1 (nesting depth added 13). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
PhysicalDisplayUDPReceiver.receive (cognitive 26) Sources/AXe/Device/PhysicalDisplayUDPReceiver.swift:99— PhysicalDisplayUDPReceiver.receive has cognitive complexity 26 (threshold 15). Drivers by points: if/else 9 (20 pts), boolean chains 5, 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.
SelectedHIDPath.primitives (cognitive 26) Sources/AXe/Utilities/SelectedHIDPath.swift:232— SelectedHIDPath.primitives has cognitive complexity 26 (threshold 15). Drivers by points: if/else 14 (16 pts), boolean chains 8, ternaries 1 (2 pts) (nesting depth added 3). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
SimulatorClipboard.readStdin (cognitive 25) Sources/AXe/Commands/Clipboard.swift:138— SimulatorClipboard.readStdin has cognitive complexity 25 (threshold 15). Drivers by points: if/else 8 (18 pts), boolean chains 4, loops 1 (2 pts), error handling 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.
PhysicalDeviceH264Stream.writeFrames (cognitive 25) Sources/AXe/Device/PhysicalDeviceH264Stream.swift:42— PhysicalDeviceH264Stream.writeFrames has cognitive complexity 25 (threshold 15). Drivers by points: if/else 6 (18 pts), error handling 2 (4 pts), loops 1 (2 pts), boolean chains 1 (nesting depth added 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
AccessibilityFetcher.isTransientPointFallback (cognitive 25) Sources/AXe/Utilities/AccessibilityFetcher.swift:417— AccessibilityFetcher.isTransientPointFallback has cognitive complexity 25 (threshold 15). Drivers by points: boolean chains 17, if/else 8. 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.
AgentModeController.refusal (cognitive 25) Sources/AXe/Utilities/AgentModeController.swift:337— AgentModeController.refusal has cognitive complexity 25 (threshold 15). Drivers by points: boolean chains 18, if/else 5 (7 pts) (nesting depth added 2). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
AgentModeKeyboardDetector.numericOcclusion (cognitive 25) Sources/AXe/Utilities/AgentModeKeyboardObservation.swift:169— AgentModeKeyboardDetector.numericOcclusion has cognitive complexity 25 (threshold 15). Drivers by points: boolean chains 13, if/else 5 (11 pts), loops 1 (nesting depth added 6). This file's own header attributes it to another copyright holder, so it is code this repository carries rather than code it wrote: restructuring the body in place forks it from upstream and turns every future re-sync into a manual merge. The performable moves are to leave the body as close to its upstream form as possible and keep it behind a narrow interface of your own, and to re-sync it when upstream changes — or, if it has already diverged far enough that you maintain it here, adopt it deliberately and then split the body into named stages.
AgentOutputProjection.completedBatch (cognitive 25) Sources/AXe/Utilities/AgentOutputProjection.swift:332— AgentOutputProjection.completedBatch has cognitive complexity 25 (threshold 15). Drivers by points: boolean chains 22, if/else 2, ternaries 1. To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
CLIOutputText.agent (cognitive 25) Sources/AXe/Utilities/CLIOutputText.swift:18— CLIOutputText.agent has cognitive complexity 25 (threshold 15). Drivers by points: if/else 13 (20 pts), loops 2 (3 pts), boolean chains 1, ternaries 1 (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
SelectedHIDCompleteGesture.validate (cognitive 25) Sources/AXe/Utilities/SelectedHIDCompleteGesture.swift:71— SelectedHIDCompleteGesture.validate has cognitive complexity 25 (threshold 15). Drivers by points: boolean chains 12, if/else 5 (10 pts), loops 1 (2 pts), match/switch 1 (nesting depth added 6). 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.
SelectedHIDPinch.validate (cognitive 25) Sources/AXe/Utilities/SelectedHIDPinch.swift:23— SelectedHIDPinch.validate has cognitive complexity 25 (threshold 15). Drivers by points: boolean chains 20, if/else 4 (5 pts) (nesting depth added 1). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
SliderPickupReadChild.run (cognitive 25) Sources/AXe/Utilities/SliderValue/SliderPickupReadChild.swift:68— SliderPickupReadChild.run has cognitive complexity 25 (threshold 15). Drivers by points: if/else 9 (16 pts), boolean chains 4, loops 2 (3 pts), error handling 1, ternaries 1 (nesting depth added 8). Of this number, 22 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.
PhysicalDeviceDisplay.init (cognitive 24) Sources/AXe/Device/PhysicalDeviceDisplay.swift:40— PhysicalDeviceDisplay.init has cognitive complexity 24 (threshold 15). Drivers by points: boolean chains 19, if/else 3, ternaries 2. To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
PhysicalDeviceInputOwner.keys (cognitive 24) Sources/AXe/Device/PhysicalDeviceInputOwner.swift:164— PhysicalDeviceInputOwner.keys has cognitive complexity 24 (threshold 15). Drivers by points: if/else 9 (19 pts), loops 2 (3 pts), boolean chains 1, error handling 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.
CLIOutputJSONParser.number (cognitive 24) Sources/AXe/Utilities/CLIOutputValue.swift:276— CLIOutputJSONParser.number has cognitive complexity 24 (threshold 15). Drivers by points: if/else 13 (19 pts), boolean chains 5 (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
SelectedAXWait.run (cognitive 24) Sources/AXe/Utilities/SelectedAXWait.swift:63— SelectedAXWait.run has cognitive complexity 24 (threshold 15). Drivers by points: if/else 7 (16 pts), error handling 2 (4 pts), boolean chains 2, loops 1 (2 pts) (nesting depth added 12). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
BatchPlanRunner.run (cognitive 24) Sources/AXe/Utilities/Batch/BatchPlanRunner.swift:21— BatchPlanRunner.run has cognitive complexity 24 (threshold 15). Drivers by points: if/else 5 (15 pts), match/switch 2 (5 pts), boolean chains 2, loops 1, ternaries 1 (nesting depth added 13). Of this number, 22 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.
SliderPickupReadChild.close (cognitive 24) Sources/AXe/Utilities/SliderValue/SliderPickupReadChild.swift:123— SliderPickupReadChild.close has cognitive complexity 24 (threshold 15). Drivers by points: if/else 7 (11 pts), boolean chains 8, loops 3 (5 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.
AgentPolicy.prepareRequest (cognitive 24) Sources/AXeCore/AgentPolicy.swift:13— AgentPolicy.prepareRequest has cognitive complexity 24 (threshold 15). Drivers by points: if/else 11 (13 pts), loops 4 (8 pts), boolean chains 3 (nesting depth added 6). 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.
Axe.formattedOutput (cognitive 23) Sources/AXe/main.swift:92— Axe.formattedOutput has cognitive complexity 23 (threshold 15). Drivers by points: if/else 8 (14 pts), boolean chains 7, error handling 2 (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.
StreamVideo.streamCompressedFrames (cognitive 23) Sources/AXe/Commands/StreamVideo.swift:153— StreamVideo.streamCompressedFrames has cognitive complexity 23 (threshold 15). Drivers by points: if/else 8 (16 pts), match/switch 1 (3 pts), error handling 1 (2 pts), boolean chains 1, loops 1 (nesting depth added 11). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
Tap.validateAgent (cognitive 23) Sources/AXe/Commands/Tap.swift:236— Tap.validateAgent has cognitive complexity 23 (threshold 15). Drivers by points: boolean chains 11, if/else 7 (9 pts), ternaries 2, 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.
PhysicalAXTreeArchive.decode (cognitive 23) Sources/AXe/Device/PhysicalAXTreeArchive.swift:56— PhysicalAXTreeArchive.decode has cognitive complexity 23 (threshold 15). Drivers by points: boolean chains 12, if/else 9, error handling 1, ternaries 1. To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
AgentModeSwipePlanner.plan (cognitive 23) Sources/AXe/Utilities/AgentModeSwipePlanner.swift:18— AgentModeSwipePlanner.plan has cognitive complexity 23 (threshold 15). Drivers by points: boolean chains 17, if/else 5 (6 pts) (nesting depth added 1). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
SimulatorKeyboardSettings.activeHardwareLayout (cognitive 23) Sources/AXe/Utilities/RuntimeKeyboardLayout.swift:258— SimulatorKeyboardSettings.activeHardwareLayout has cognitive complexity 23 (threshold 15). Drivers by points: if/else 7 (12 pts), boolean chains 5, loops 2 (5 pts), ternaries 1 (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
SelectedHIDOwner.isStateOnlyRotationFailure (cognitive 23) Sources/AXe/Utilities/SelectedHIDOwner.swift:516— SelectedHIDOwner.isStateOnlyRotationFailure has cognitive complexity 23 (threshold 15). Drivers by points: boolean chains 22, if/else 1. To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
SliderPickupHelper.confirm (cognitive 23) Sources/AXe/Utilities/SliderValue/SliderPickupHelper.swift:220— SliderPickupHelper.confirm has cognitive complexity 23 (threshold 15). Drivers by points: boolean chains 18, if/else 4, ternaries 1. To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
StreamVideo.validate (cognitive 22) Sources/AXe/Commands/StreamVideo.swift:58— StreamVideo.validate has cognitive complexity 22 (threshold 15). Drivers by points: if/else 9 (13 pts), boolean chains 9 (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.
Type.validate (cognitive 22) Sources/AXe/Commands/Type.swift:47— Type.validate has cognitive complexity 22 (threshold 15). Drivers by points: if/else 10 (15 pts), boolean chains 7 (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.
PhysicalDeviceBrokerOwner.semanticPress (cognitive 22) Sources/AXe/Device/PhysicalDeviceBrokerOwner.swift:223— PhysicalDeviceBrokerOwner.semanticPress has cognitive complexity 22 (threshold 15). Drivers by points: if/else 5 (12 pts), error handling 4 (5 pts), boolean chains 4, loops 1 (nesting depth added 8). 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, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
AgentBatchStep.validate (cognitive 22) Sources/AXe/Utilities/AgentBatchProtocol.swift:63— AgentBatchStep.validate has cognitive complexity 22 (threshold 15). Drivers by points: if/else 8 (13 pts), boolean chains 8, match/switch 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.
AgentOutputProjection.addingScrollPreview (cognitive 22) Sources/AXe/Utilities/AgentOutputProjection.swift:187— AgentOutputProjection.addingScrollPreview has cognitive complexity 22 (threshold 15). Drivers by points: boolean chains 9, if/else 5 (9 pts), loops 2 (3 pts), 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.
SelectedHIDContract.sliderCompleted (cognitive 22) Sources/AXe/Utilities/SelectedHIDContract.swift:42— SelectedHIDContract.sliderCompleted has cognitive complexity 22 (threshold 15). Drivers by points: boolean chains 16, if/else 4 (5 pts), match/switch 1 (nesting depth added 1). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
SelectedHingeOperation.perform (cognitive 22) Sources/AXe/Utilities/SelectedHingeOperation.swift:8— SelectedHingeOperation.perform has cognitive complexity 22 (threshold 15). Drivers by points: if/else 6 (11 pts), error handling 3 (5 pts), ternaries 2 (5 pts), boolean chains 1 (nesting depth added 10). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
SelectedOpaqueFrameTapAdmission.validate (cognitive 22) Sources/AXe/Utilities/SelectedOpaqueFrameTapAdmission.swift:18— SelectedOpaqueFrameTapAdmission.validate has cognitive complexity 22 (threshold 15). Drivers by points: boolean chains 11, if/else 7 (10 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.
AgentTextCandidateExtractor.candidates (cognitive 22) Sources/AXeCore/AgentPolicy.swift:476— AgentTextCandidateExtractor.candidates has cognitive complexity 22 (threshold 15). Drivers by points: if/else 8 (12 pts), loops 6 (9 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.
PhysicalAccessibilityCommands.tap (cognitive 21) Sources/AXe/Commands/PhysicalAccessibilityCommands.swift:43— PhysicalAccessibilityCommands.tap has cognitive complexity 21 (threshold 15). Drivers by points: if/else 11 (15 pts), boolean chains 4, loops 1, ternaries 1 (nesting depth added 4). Of this number, 19 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.
RecordVideo.validate (cognitive 21) Sources/AXe/Commands/RecordVideo.swift:51— RecordVideo.validate has cognitive complexity 21 (threshold 15). Drivers by points: if/else 8 (12 pts), boolean chains 9 (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.
AgentModeController.reboundSteps (cognitive 21) Sources/AXe/Utilities/AgentModeController+Batch.swift:59— AgentModeController.reboundSteps has cognitive complexity 21 (threshold 15). Drivers by points: boolean chains 9, if/else 5 (9 pts), loops 2 (3 pts) (nesting depth added 5). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
AgentModeController.performReferenceBatchStep (cognitive 21) Sources/AXe/Utilities/AgentModeController+Batch.swift:280— AgentModeController.performReferenceBatchStep has cognitive complexity 21 (threshold 15). Drivers by points: if/else 5 (11 pts), ternaries 3 (6 pts), boolean chains 3, error handling 1 (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
HIDInputQuarantine.requireClear (cognitive 21) Sources/AXe/Utilities/HIDInputQuarantine.swift:45— HIDInputQuarantine.requireClear has cognitive complexity 21 (threshold 15). Drivers by points: if/else 7 (12 pts), boolean chains 8, 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.
RuntimeKeyboardLayout.init (cognitive 21) Sources/AXe/Utilities/RuntimeKeyboardLayout.swift:51— RuntimeKeyboardLayout.init has cognitive complexity 21 (threshold 15). Drivers by points: if/else 6 (11 pts), boolean chains 6, loops 3 (4 pts) (nesting depth added 6). Of this number, 20 points are the body's own statements and 1 belongs to one function item inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
AgentPolicy.resolveDecision (cognitive 21) Sources/AXeCore/AgentPolicy.swift:258— AgentPolicy.resolveDecision has cognitive complexity 21 (threshold 15). Drivers by points: if/else 10 (16 pts), boolean chains 4, match/switch 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.
TypeSafeClient.systemOne (cognitive 21) Sources/AXeCore/TypeSafeClient.swift:162— TypeSafeClient.systemOne has cognitive complexity 21 (threshold 15). Drivers by points: if/else 3 (9 pts), error handling 3 (8 pts), boolean chains 3, 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.
KeySequence.validate (cognitive 20) Sources/AXe/Commands/KeySequence.swift:32— KeySequence.validate has cognitive complexity 20 (threshold 15). Drivers by points: if/else 11 (16 pts), boolean chains 3, 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.
PhysicalDeviceBrokerClient.connectToWorker (cognitive 20) Sources/AXe/Device/PhysicalDeviceBrokerClient.swift:116— PhysicalDeviceBrokerClient.connectToWorker has cognitive complexity 20 (threshold 15). Drivers by points: if/else 8 (11 pts), boolean chains 5, error handling 3, loops 1 (nesting depth added 3). Of this number, 12 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.
FollowActiveVideoRecording.record (cognitive 20) Sources/AXe/Utilities/FollowActiveVideoRecording.swift:17— FollowActiveVideoRecording.record has cognitive complexity 20 (threshold 15). Drivers by points: if/else 11 (17 pts), boolean chains 1, loops 1, ternaries 1 (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
SelectedVideoRecording.record (cognitive 20) Sources/AXe/Utilities/SelectedVideoRecording.swift:20— SelectedVideoRecording.record has cognitive complexity 20 (threshold 15). Drivers by points: if/else 10 (15 pts), boolean chains 3, loops 1, 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.
Gesture.validateAgentGesture (cognitive 19) Sources/AXe/Commands/Gesture.swift:490— Gesture.validateAgentGesture has cognitive complexity 19 (threshold 15). Drivers by points: boolean chains 15, if/else 4. To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
RecordVideo.recordVideo (cognitive 19) Sources/AXe/Commands/RecordVideo.swift:153— RecordVideo.recordVideo has cognitive complexity 19 (threshold 15). Drivers by points: if/else 7 (16 pts), error handling 1 (2 pts), loops 1 (nesting depth added 10). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
Swipe.run (cognitive 19) Sources/AXe/Commands/Swipe.swift:187— Swipe.run has cognitive complexity 19 (threshold 15). Drivers by points: if/else 10 (13 pts), boolean chains 6 (nesting depth added 3). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
Tap.run (cognitive 19) Sources/AXe/Commands/Tap.swift:444— Tap.run has cognitive complexity 19 (threshold 15). Drivers by points: if/else 14 (16 pts), boolean chains 3 (nesting depth added 2). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, 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.
Touch.run (cognitive 19) Sources/AXe/Commands/Touch.swift:153— Touch.run has cognitive complexity 19 (threshold 15). Drivers by points: if/else 11 (13 pts), boolean chains 6 (nesting depth added 2). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
DeviceAccessibilitySession.request (cognitive 19) Sources/AXe/Device/DeviceAccessibilitySession.swift:68— DeviceAccessibilitySession.request has cognitive complexity 19 (threshold 15). Drivers by points: if/else 8 (10 pts), boolean chains 9 (nesting depth added 2). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition.
DeviceDTXMessage.read (cognitive 19) Sources/AXe/Device/DeviceDTXMessage.swift:21— DeviceDTXMessage.read has cognitive complexity 19 (threshold 15). Drivers by points: boolean chains 9, if/else 6 (8 pts), loops 1 (2 pts) (nesting depth added 3). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
H264RTPDepacketizer.finishUnit (cognitive 19) Sources/AXe/Device/H264RTPDepacketizer.swift:137— H264RTPDepacketizer.finishUnit has cognitive complexity 19 (threshold 15). Drivers by points: if/else 7 (8 pts), boolean chains 4, ternaries 2 (4 pts), loops 2 (3 pts) (nesting depth added 4). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
PhysicalAXTreeArchive.shape (cognitive 19) Sources/AXe/Device/PhysicalAXTreeArchive.swift:112— PhysicalAXTreeArchive.shape has cognitive complexity 19 (threshold 15). Drivers by points: if/else 5 (9 pts), boolean chains 8, loops 2 (nesting depth added 4). Of this number, 13 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.
PhysicalDeviceInputOwner.rotate (cognitive 19) Sources/AXe/Device/PhysicalDeviceInputOwner.swift:217— PhysicalDeviceInputOwner.rotate has cognitive complexity 19 (threshold 15). Drivers by points: if/else 7 (10 pts), boolean chains 6, error handling 1 (2 pts), loops 1 (nesting depth added 4). 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 into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
AgentModeRequest.validateKeySequence (cognitive 19) Sources/AXe/Utilities/AgentModeProtocol.swift:237— AgentModeRequest.validateKeySequence has cognitive complexity 19 (threshold 15). Drivers by points: boolean chains 9, if/else 5 (9 pts), loops 1 (nesting depth added 4). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
AgentModeSwipePlanner.clearOfDragControls (cognitive 19) Sources/AXe/Utilities/AgentModeSwipePlanner.swift:134— AgentModeSwipePlanner.clearOfDragControls has cognitive complexity 19 (threshold 15). Drivers by points: boolean chains 7, if/else 3 (5 pts), ternaries 2 (4 pts), loops 2 (3 pts) (nesting depth added 5). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
AgentOutputProjection.project (cognitive 19) Sources/AXe/Utilities/AgentOutputProjection.swift:26— AgentOutputProjection.project has cognitive complexity 19 (threshold 15). Drivers by points: if/else 12, boolean chains 5, loops 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.
ScrollUntilOptions.run (cognitive 19) Sources/AXe/Utilities/ScrollUntil.swift:56— ScrollUntilOptions.run has cognitive complexity 19 (threshold 15). Drivers by points: if/else 5 (9 pts), ternaries 2 (6 pts), loops 2, boolean chains 1, match/switch 1 (nesting depth added 8). Of this number, 15 points are the body's own statements and 4 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.
SelectedHIDRequest.validate (cognitive 19) Sources/AXe/Utilities/SelectedHIDProtocol.swift:245— SelectedHIDRequest.validate has cognitive complexity 19 (threshold 15). Drivers by points: if/else 6 (10 pts), boolean chains 7, loops 1, match/switch 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.
SelectedStreamFrame.encode (cognitive 19) Sources/AXe/Utilities/SelectedStreamFrame.swift:24— SelectedStreamFrame.encode has cognitive complexity 19 (threshold 15). Drivers by points: boolean chains 11, if/else 5 (7 pts), match/switch 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.
RuntimeSnapshotBuilder.deriveRole (cognitive 19) Sources/AXeCore/RuntimeSnapshot.swift:345— RuntimeSnapshotBuilder.deriveRole has cognitive complexity 19 (threshold 15). Drivers by points: if/else 17, boolean chains 2. 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.
Slider.performOwnedSlider (cognitive 18) Sources/AXe/Commands/Slider.swift:268— Slider.performOwnedSlider has cognitive complexity 18 (threshold 15). Drivers by points: ternaries 6 (7 pts), if/else 5 (6 pts), boolean chains 5 (nesting depth added 2). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
AgentModeController.performBatchRetrying (cognitive 18) Sources/AXe/Utilities/AgentModeController+Batch.swift:8— AgentModeController.performBatchRetrying has cognitive complexity 18 (threshold 15). Drivers by points: boolean chains 10, if/else 5 (6 pts), ternaries 2 (nesting depth added 1). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
SelectedAXWire.readResponse (cognitive 18) Sources/AXe/Utilities/SelectedAXWire.swift:6— SelectedAXWire.readResponse has cognitive complexity 18 (threshold 15). Drivers by points: if/else 7 (15 pts), boolean chains 2, loops 1 (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
SelectedHIDPath.event (cognitive 18) Sources/AXe/Utilities/SelectedHIDPath.swift:169— SelectedHIDPath.event has cognitive complexity 18 (threshold 15). Drivers by points: if/else 8 (10 pts), boolean chains 8 (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.
Gesture.validateAgentPinch (cognitive 17) Sources/AXe/Commands/Gesture.swift:512— Gesture.validateAgentPinch has cognitive complexity 17 (threshold 15). Drivers by points: boolean chains 15, if/else 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.
VisibleTree.target (cognitive 17) Sources/AXe/Commands/PhysicalAccessibilityCommands.swift:181— VisibleTree.target has cognitive complexity 17 (threshold 15). Drivers by points: boolean chains 10, if/else 5, match/switch 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.
Screenshot.prepareOutputURL (cognitive 17) Sources/AXe/Commands/Screenshot.swift:180— Screenshot.prepareOutputURL has cognitive complexity 17 (threshold 15). Drivers by points: if/else 11 (15 pts), boolean chains 2 (nesting depth added 4). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
StreamVideo.run (cognitive 17) Sources/AXe/Commands/StreamVideo.swift:92— StreamVideo.run has cognitive complexity 17 (threshold 15). Drivers by points: if/else 9 (12 pts), boolean chains 4, match/switch 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.
Swipe.validateAgent (cognitive 17) Sources/AXe/Commands/Swipe.swift:117— Swipe.validateAgent has cognitive complexity 17 (threshold 15). Drivers by points: if/else 6 (9 pts), boolean chains 8 (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.
VideoFrameUtilities.processJPEGData (cognitive 17) Sources/AXe/Commands/VideoCommandSupport.swift:107— VideoFrameUtilities.processJPEGData has cognitive complexity 17 (threshold 15). Drivers by points: if/else 8 (10 pts), boolean chains 7 (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.
DeviceInspection.inspect (cognitive 17) Sources/AXe/Device/DeviceReadiness.swift:88— DeviceInspection.inspect has cognitive complexity 17 (threshold 15). Drivers by points: if/else 6 (10 pts), error handling 2 (5 pts), boolean chains 2 (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
DeviceTunnelAddress.portFromSockets (cognitive 17) Sources/AXe/Device/DeviceServiceDirectory.swift:323— DeviceTunnelAddress.portFromSockets has cognitive complexity 17 (threshold 15). Drivers by points: boolean chains 8, if/else 3 (6 pts), ternaries 2, 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.
PhysicalDeviceBrokerOperation.validate (cognitive 17) Sources/AXe/Device/PhysicalDeviceBrokerProtocol.swift:31— PhysicalDeviceBrokerOperation.validate has cognitive complexity 17 (threshold 15). Drivers by points: if/else 6 (11 pts), boolean chains 5, match/switch 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.
AgentModeSnapshot.physicalButtonExecutionTarget (cognitive 17) Sources/AXe/Utilities/AgentModeSnapshot.swift:318— AgentModeSnapshot.physicalButtonExecutionTarget has cognitive complexity 17 (threshold 15). Drivers by points: boolean chains 11, if/else 6. 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.
AgentModeSnapshot.match (cognitive 17) Sources/AXe/Utilities/AgentModeSnapshot.swift:345— AgentModeSnapshot.match has cognitive complexity 17 (threshold 15). Drivers by points: if/else 5 (11 pts), boolean chains 5, match/switch 1 (nesting depth added 6). 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.
Recovery.canRecover (cognitive 17) Sources/AXe/Utilities/FollowActiveVideoRecording.swift:150— Recovery.canRecover has cognitive complexity 17 (threshold 15). Drivers by points: boolean chains 10, if/else 6, match/switch 1. To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
SelectedHIDAdmission.enter (cognitive 17) Sources/AXe/Utilities/SelectedHIDProtocol.swift:421— SelectedHIDAdmission.enter has cognitive complexity 17 (threshold 15). Drivers by points: if/else 8 (14 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.
SelectedKeyboardOperation.perform (cognitive 17) Sources/AXe/Utilities/SelectedKeyboardOperation.swift:8— SelectedKeyboardOperation.perform has cognitive complexity 17 (threshold 15). Drivers by points: if/else 5 (10 pts), error handling 2 (4 pts), ternaries 1 (2 pts), boolean chains 1 (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
SliderPickupRawAttributes.runtimeID (cognitive 17) Sources/AXe/Utilities/SliderValue/SliderPickupRawAttributes.swift:20— SliderPickupRawAttributes.runtimeID has cognitive complexity 17 (threshold 15). Drivers by points: boolean chains 11, if/else 4 (5 pts), loops 1 (nesting depth added 1). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
DrawingCanvas.finish (cognitive 17) AxePlaygroundApp/AxePlayground/Views/DrawingView.swift:296— DrawingCanvas.finish has cognitive complexity 17 (threshold 15). Drivers by points: if/else 8 (15 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.
GesturePresetsView.body (cognitive 17) AxePlaygroundApp/AxePlayground/Views/GesturePresetsView.swift:110— GesturePresetsView.body has cognitive complexity 17 (threshold 15). Drivers by points: if/else 10, ternaries 4 (7 pts) (nesting depth added 3). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
AgentCommand.run (cognitive 16) Sources/AXe/Commands/AgentCommand.swift:64— AgentCommand.run has cognitive complexity 16 (threshold 15). Drivers by points: if/else 7 (9 pts), boolean chains 4, 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.
RecordVideo.run (cognitive 16) Sources/AXe/Commands/RecordVideo.swift:80— RecordVideo.run has cognitive complexity 16 (threshold 15). Drivers by points: if/else 8 (10 pts), boolean chains 5, error handling 1 (nesting depth added 2). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition.
Tap.runOnDevice (cognitive 16) Sources/AXe/Commands/Tap.swift:407— Tap.runOnDevice has cognitive complexity 16 (threshold 15). Drivers by points: if/else 11 (13 pts), ternaries 1 (2 pts), boolean chains 1 (nesting depth added 3). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
H264RTPDepacketizer.accept (cognitive 16) Sources/AXe/Device/H264RTPDepacketizer.swift:25— H264RTPDepacketizer.accept has cognitive complexity 16 (threshold 15). Drivers by points: if/else 10 (12 pts), boolean chains 4 (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.
RemoteXPCReader.readObject (cognitive 16) Sources/AXe/Device/RemoteXPCWire.swift:308— RemoteXPCReader.readObject has cognitive complexity 16 (threshold 15). Drivers by points: if/else 6 (11 pts), loops 2 (4 pts), match/switch 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.
AgentModeRequest.validateKeyCombo (cognitive 16) Sources/AXe/Utilities/AgentModeProtocol.swift:260— AgentModeRequest.validateKeyCombo has cognitive complexity 16 (threshold 15). Drivers by points: boolean chains 8, if/else 4 (6 pts), loops 2 (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.
CLIOutputJSONParser.object (cognitive 16) Sources/AXe/Utilities/CLIOutputValue.swift:129— CLIOutputJSONParser.object has cognitive complexity 16 (threshold 15). Drivers by points: if/else 7 (12 pts), boolean chains 3, 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.
HIDBroker.validate (cognitive 16) Sources/AXe/Utilities/HIDBroker.swift:279— HIDBroker.validate has cognitive complexity 16 (threshold 15). Drivers by points: if/else 4 (8 pts), boolean chains 5, match/switch 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.
HIDBroker.ensurePrivateDirectory (cognitive 16) Sources/AXe/Utilities/HIDBroker.swift:369— HIDBroker.ensurePrivateDirectory has cognitive complexity 16 (threshold 15). Drivers by points: if/else 9 (10 pts), boolean chains 6 (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.
OrientationAwareCoordinates.detectMapping (cognitive 16) Sources/AXe/Utilities/OrientationAwareCoordinates.swift:139— OrientationAwareCoordinates.detectMapping has cognitive complexity 16 (threshold 15). Drivers by points: if/else 9 (13 pts), match/switch 1 (2 pts), boolean chains 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.
SelectedAXWire.boundedResponse (cognitive 16) Sources/AXe/Utilities/SelectedAXWire.swift:35— SelectedAXWire.boundedResponse has cognitive complexity 16 (threshold 15). Drivers by points: if/else 4 (9 pts), ternaries 2 (6 pts), error handling 1 (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
SelectedButtonExecutionEvidence.completed (cognitive 16) Sources/AXe/Utilities/SelectedHIDContract.swift:84— SelectedButtonExecutionEvidence.completed has cognitive complexity 16 (threshold 15). Drivers by points: boolean chains 15, if/else 1. To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
SelectedHIDPrimitive.validate (cognitive 16) Sources/AXe/Utilities/SelectedHIDProtocol.swift:303— SelectedHIDPrimitive.validate has cognitive complexity 16 (threshold 15). Drivers by points: boolean chains 11, if/else 2 (4 pts), match/switch 1 (nesting depth added 2). 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.
SelectedStreamOutput.write (cognitive 16) Sources/AXe/Utilities/SelectedStreamOutput.swift:38— SelectedStreamOutput.write has cognitive complexity 16 (threshold 15). Drivers by points: if/else 7 (13 pts), boolean chains 2, loops 1 (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
SelectedSliderValueOperation.run (cognitive 16) Sources/AXe/Utilities/SliderValue/SelectedSliderValueOperation.swift:116— SelectedSliderValueOperation.run has cognitive complexity 16 (threshold 15). Drivers by points: if/else 8 (9 pts), ternaries 3 (4 pts), boolean chains 2, error handling 1 (nesting depth added 2). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, 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.
AgentFreshness.evaluate (cognitive 16) Sources/AXeCore/AgentFreshness.swift:28— AgentFreshness.evaluate has cognitive complexity 16 (threshold 15). Drivers by points: ternaries 3 (7 pts), if/else 3 (5 pts), boolean chains 3, match/switch 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.
Change-coupling hub: Drag.swift → Swipe.swift, Tap.swift, SelectedHIDOwner.swift Sources/AXe/Commands/Drag.swift— `Sources/AXe/Commands/Drag.swift` changes together with 3 other files — `Sources/AXe/Commands/Swipe.swift`, `Sources/AXe/Commands/Tap.swift`, `Sources/AXe/Utilities/SelectedHIDOwner.swift` — none of which declares a dependency on it: one file is the hub of 3 separate couplings, not 3 unrelated pairs. Read the hub first: if the others each duplicate a part of what it does, the shared concern belongs in ONE unit and extracting it clears every edge at once; if the hub is a registry, dispatcher or barrel that must name each of them, the coupling is structural and the question is whether that list can be discovered instead of enumerated. Fixing the hub is one change; breaking the couplings one pair at a time is 3.
Change coupling: Swipe.swift ↔ Touch.swift Sources/AXe/Commands/Swipe.swift:1— `Sources/AXe/Commands/Swipe.swift` and `Sources/AXe/Commands/Touch.swift` change together 55% of the time (6 of the 11 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets). They sit in the same directory, and in this ecosystem sibling files there normally share one namespace/package — so a direct reference between them needs no import and this pass cannot see whether one exists. Read the pair before acting: if one file only DECLARES what the other consumes (a constants/types file beside its user), the co-change is definitional and the question is whether the split earns its keep; if they duplicate structure, extract the common part into a shared function or type they both call; if neither holds, the coupling is hidden and worth breaking. You can check this without leaving the row: of the 6 shared commits counted here, the most recent 3 are `d4b9952f` perf(input): Let a running broker bind the screen for plain touch com…; `2f991f49` docs(help): Correct tap, batch and --expected-pid help; `3979992b` fix(input): Report a shut-down simulator as not booted — run `git show` on any of them.
Near-duplicate member pair (23 shared lines) Sources/AXe/Utilities/FollowActiveVideoRecording.swift:17— Sources/AXe/Utilities/FollowActiveVideoRecording.swift:17-93 | Sources/AXe/Utilities/SelectedVideoRecording.swift:20-87 — These two members are variants of one another: 23 of their lines are already reported as duplicated blocks below, spread through both bodies rather than gathered into one. Read them as a single construct written twice. The repair is at the members' grain — factor the shared pipeline into one implementation the two call with their differences as parameters or as an injected step, or, where the difference is systematic (sync against async, one transport against another), generate one from the other. Extracting the individual blocks below is not the same fix: it leaves the two bodies in place and the next edit still has to be made twice.
D4 · Code Duplication· Members sharing a duplicated core (7 members, 50+ identical tokens) · ×1
Members sharing a duplicated core (7 members, 50+ identical tokens) AxePlaygroundApp/AxePlayground/Views/AgentExamplesView.swift:33— AxePlaygroundApp/AxePlayground/Views/AgentExamplesView.swift:33-130 | AxePlaygroundApp/AxePlayground/Views/DrawingView.swift:35-92 | AxePlaygroundApp/AxePlayground/Views/DuoControlsView.swift:42-148 | AxePlaygroundApp/AxePlayground/Views/InsetWindowView.swift:72-105 | AxePlaygroundApp/AxePlayground/Views/SketchView.swift:59-137 | AxePlaygroundApp/AxePlayground/Views/TouchMonitorView.swift:24-62 | AxePlaygroundApp/AxePlayground/Views/ZoomView.swift:21-61 — These 7 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 7 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 7 times.
D4 · Code Duplication· Members sharing a duplicated core (4 members, 50+ identical tokens) · ×1
Members sharing a duplicated core (4 members, 50+ identical tokens) Sources/AXe/Utilities/OrdinaryBrokerInput.swift:121— Sources/AXe/Utilities/OrdinaryBrokerInput.swift:121-143 | Sources/AXe/Utilities/OrdinaryBrokerInput.swift:208-224 | Sources/AXe/Utilities/OrdinaryBrokerInput.swift:226-244 | Sources/AXe/Utilities/OrdinaryBrokerInput.swift:246-269 — These 4 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 4 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 4 times.
D4 · Code Duplication· Edited copy of a member (46 corresponding lines) · ×1
Edited copy of a member (46 corresponding lines) Sources/AXe/Commands/RecordVideo.swift:239— Sources/AXe/Commands/RecordVideo.swift:239-284 | Sources/AXe/Commands/Screenshot.swift:180-229 — These two members are one piece of code written twice and then edited apart: 46 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copies of one member (4 members, 18+ corresponding lines) · ×1
Edited copies of one member (4 members, 18+ corresponding lines) scripts/fixtures/DuoExternalStateChange.swift:270— Packages/IDBKit/FBSimulatorControl/HID/FBSimulatorDisplayInfoReader.swift:224-243 | Packages/IDBKit/FBSimulatorControl/HID/FBSimulatorHIDMotionFeed.swift:90-109 | Packages/IDBKit/FBSimulatorControl/HID/FBSimulatorHingeNative.swift:74-91 | scripts/fixtures/DuoExternalStateChange.swift:270-290 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 18 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 4 times and the copies will drift further apart.
D4 · Code Duplication· Edited copy of a member (21 corresponding lines) · ×1
Edited copy of a member (21 corresponding lines) Sources/AXe/Commands/Clipboard.swift:72— Sources/AXe/Commands/Clipboard.swift:72-99 | Sources/AXe/Utilities/SignalScope.swift:15-35 — These two members are one piece of code written twice and then edited apart: 21 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copies of one member (3 members, 25+ corresponding lines) · ×1
Edited copies of one member (3 members, 25+ corresponding lines) Sources/AXe/Commands/Key.swift:76— Sources/AXe/Commands/Key.swift:76-103 | Sources/AXe/Commands/KeyCombo.swift:92-116 | Sources/AXe/Commands/KeySequence.swift:100-124 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 25 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication· Edited copy of a member (9 corresponding lines) · ×1
Edited copy of a member (9 corresponding lines) Sources/AXeCore/AgentJSON.swift:12— Packages/IDBKit/FBSimulatorControl/Commands/FBSimulatorAXSnapshot.swift:26-34 | Sources/AXeCore/AgentJSON.swift:12-33 — These two members are one piece of code written twice and then edited apart: 9 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (20 corresponding lines) · ×1
Edited copy of a member (20 corresponding lines) Sources/AXe/Device/RemoteXPCConnection.swift:320— Sources/AXe/Device/RemoteXPCConnection.swift:320-341 | Sources/AXe/Device/RemoteXPCConnection.swift:343-362 — These two members are one piece of code written twice and then edited apart: 20 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (23 corresponding lines) · ×1
Edited copy of a member (23 corresponding lines) Sources/AXe/Utilities/HIDBroker+Connection.swift:56— Sources/AXe/Utilities/HIDBroker+Connection.swift:56-78 | Sources/AXe/Utilities/HIDBroker+Connection.swift:400-422 — These two members are one piece of code written twice and then edited apart: 23 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (16 corresponding lines) · ×1
Edited copy of a member (16 corresponding lines) Sources/AXe/Device/PhysicalDeviceBrokerSocket.swift:79— Sources/AXe/Device/PhysicalDeviceBrokerSocket.swift:79-94 | Sources/AXe/Device/PhysicalDeviceBrokerSocket.swift:107-123 — These two members are one piece of code written twice and then edited apart: 16 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copies of one member (4 members, 8+ corresponding lines) · ×1
Edited copies of one member (4 members, 8+ corresponding lines) Sources/AXe/Commands/Settings.swift:106— Sources/AXe/Commands/Settings.swift:106-113 | Sources/AXe/Commands/Settings.swift:121-128 | Sources/AXe/Commands/Settings.swift:136-143 | Sources/AXe/Commands/Settings.swift:156-163 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 8 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 4 times and the copies will drift further apart.
D4 · Code Duplication· Edited copies of one member (4 members, 14+ corresponding lines) · ×1
Edited copies of one member (4 members, 14+ corresponding lines) Sources/AXe/Utilities/OrientationAwareCoordinates.swift:424— Sources/AXe/Utilities/OrientationAwareCoordinates.swift:424-437 | Sources/AXe/Utilities/OrientationAwareCoordinates.swift:439-454 | Sources/AXe/Utilities/OrientationAwareCoordinates.swift:467-480 | Sources/AXe/Utilities/OrientationAwareCoordinates.swift:482-497 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 14 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 4 times and the copies will drift further apart.
D4 · Code Duplication· Edited copies of one member (3 members, 18+ corresponding lines) · ×1
Edited copies of one member (3 members, 18+ corresponding lines) Sources/AXe/Utilities/AccessibilityPoller.swift:5— Sources/AXe/Utilities/AccessibilityPoller.swift:5-23 | Sources/AXe/Utilities/AccessibilityPoller.swift:25-43 | Sources/AXe/Utilities/AccessibilityPoller.swift:45-62 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 18 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication· Edited copies of one member (3 members, 6+ corresponding lines) · ×1
Edited copies of one member (3 members, 6+ corresponding lines) Sources/AXe/Commands/Key.swift:58— Sources/AXe/Commands/Key.swift:58-63 | Sources/AXe/Commands/KeyCombo.swift:63-68 | Sources/AXe/Commands/KeySequence.swift:78-83 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 6 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication· Edited copies of one member (3 members, 5+ corresponding lines) · ×1
Edited copies of one member (3 members, 5+ corresponding lines) Sources/AXe/Device/PhysicalDeviceBrokerSocket.swift:52— Sources/AXe/Device/PhysicalDeviceBrokerSocket.swift:52-56 | Sources/AXe/Utilities/HIDBroker.swift:88-92 | Sources/AXe/Utilities/SelectedHIDBroker.swift:142-146 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 5 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication· Edited copy of a member (10 corresponding lines) · ×1
Edited copy of a member (10 corresponding lines) Sources/AXe/Commands/Tap.swift:599— Sources/AXe/Commands/Tap.swift:599-608 | Sources/AXe/Utilities/Batch/Command+BatchConvertible.swift:85-95 — These two members are one piece of code written twice and then edited apart: 10 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Duplicated block (25–26 lines × 2) Sources/AXe/Agent/SimulatorAgentRunner.swift:238— Sources/AXe/Agent/SimulatorAgentRunner.swift:238-262 | Sources/AXe/Agent/SimulatorAgentRunner.swift:278-303 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `Sources/AXe/Agent/SimulatorAgentRunner.swift:238` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (16 lines × 2) Sources/AXe/Commands/Gesture.swift:369— Sources/AXe/Commands/Gesture.swift:369-384 | Sources/AXe/Commands/Tap.swift:208-223 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `Sources/AXe/Commands/Gesture.swift:369` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (15 lines × 3) Sources/AXe/Commands/Key.swift:76— Sources/AXe/Commands/Key.swift:76-90 | Sources/AXe/Commands/KeyCombo.swift:92-106 | Sources/AXe/Commands/KeySequence.swift:100-114 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from all 3 call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `Sources/AXe/Commands/Key.swift:76` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (14 lines × 2) Sources/AXe/Commands/RecordVideo.swift:102— Sources/AXe/Commands/RecordVideo.swift:102-115 | Sources/AXe/Commands/StreamVideo.swift:111-124 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `Sources/AXe/Commands/RecordVideo.swift:102` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (11–12 lines × 3) Sources/AXe/Commands/Tap.swift:444— Sources/AXe/Commands/Tap.swift:444-455 | Sources/AXe/Commands/Touch.swift:153-163 | Sources/AXe/Commands/Type.swift:149-159 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from all 3 call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `Sources/AXe/Commands/Tap.swift:444` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `Sources/AXe/Commands/Touch.swift:164` calls `ValidationError` and `Sources/AXe/Commands/Tap.swift:456` does not — after which the two agree again for 3 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (10–11 lines × 2) Sources/AXe/Commands/Button.swift:150— Sources/AXe/Commands/Button.swift:150-160 | Sources/AXe/Commands/Draw.swift:122-131 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `Sources/AXe/Commands/Button.swift:150` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (10 lines × 3) Sources/AXe/Commands/Clipboard.swift:83— Sources/AXe/Commands/Clipboard.swift:83-92 | Sources/AXe/Device/PhysicalDeviceInput.swift:37-46 | Sources/AXe/Utilities/SignalScope.swift:24-33 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 3 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 3 times.
Duplicated block (8–10 lines × 2) Sources/AXe/Utilities/AgentModeNativeOperation.swift:59— Sources/AXe/Utilities/AgentModeNativeOperation.swift:59-66 | Sources/AXe/Utilities/SelectedKeyboardOperation.swift:47-56 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `Sources/AXe/Utilities/AgentModeNativeOperation.swift:59` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (9 lines × 3) Sources/AXe/Utilities/AgentModeNativeOperation.swift:58— Sources/AXe/Utilities/AgentModeNativeOperation.swift:58-66 | Sources/AXe/Utilities/SelectedAXOperation.swift:244-252 | Sources/AXe/Utilities/SelectedKeyboardOperation.swift:46-54 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from all 3 call sites, so a change lands once.
Duplicated block (8 lines × 7) AxePlaygroundApp/AxePlayground/Views/AgentExamplesView.swift:38— AxePlaygroundApp/AxePlayground/Views/AgentExamplesView.swift:38-45 | AxePlaygroundApp/AxePlayground/Views/DrawingView.swift:81-88 | AxePlaygroundApp/AxePlayground/Views/DuoControlsView.swift:52-59 | AxePlaygroundApp/AxePlayground/Views/InsetWindowView.swift:93-100 | AxePlaygroundApp/AxePlayground/Views/SketchView.swift:123-130 | AxePlaygroundApp/AxePlayground/Views/TouchMonitorView.swift:50-57 | AxePlaygroundApp/AxePlayground/Views/ZoomView.swift:50-57 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from all 7 call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `AxePlaygroundApp/AxePlayground/Views/AgentExamplesView.swift:38` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `AxePlaygroundApp/AxePlayground/Views/TouchMonitorView.swift:59` calls `constraint` and `AxePlaygroundApp/AxePlayground/Views/ZoomView.swift:59` does not — after which the two agree again for 3 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (13 lines × 2) scripts/fixtures/DuoExternalStateChange.swift:322— Packages/IDBKit/FBSimulatorControl/HID/FBSimulatorHingeNative.swift:103-115 | scripts/fixtures/DuoExternalStateChange.swift:322-334 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `Packages/IDBKit/FBSimulatorControl/HID/FBSimulatorHingeNative.swift:103` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The `return` at the foot of the matched lines is the enclosing body's own terminal exit, not an early one: it moves with them unchanged, and each site calls the extracted unit from the position that `return` occupied — no decision has to be handed back and re-acted on.
Duplicated block (5 lines × 4) Sources/AXe/Utilities/OrdinaryBrokerInput.swift:134— Sources/AXe/Utilities/OrdinaryBrokerInput.swift:134-138 | Sources/AXe/Utilities/OrdinaryBrokerInput.swift:215-220 | Sources/AXe/Utilities/OrdinaryBrokerInput.swift:234-239 | Sources/AXe/Utilities/OrdinaryBrokerInput.swift:254-259 — all 4 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `Sources/AXe/Utilities/OrdinaryBrokerInput.swift:134` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `Sources/AXe/Utilities/OrdinaryBrokerInput.swift:253` calls `validate` and `Sources/AXe/Utilities/OrdinaryBrokerInput.swift:214` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (7 lines × 3) Sources/AXe/Utilities/AgentModeProtocol.swift:128— Sources/AXe/Utilities/AgentModeProtocol.swift:128-134 | Sources/AXe/Utilities/AgentModeProtocol.swift:137-143 | Sources/AXe/Utilities/AgentModeProtocol.swift:147-153 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `Sources/AXe/Utilities/AgentModeProtocol.swift:144` calls `validateKeyCombo` and `Sources/AXe/Utilities/AgentModeProtocol.swift:135` does not — after which the two agree again for 4 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Near-duplicate member pair (51 shared lines) scripts/fixtures/DuoHeldHardwareProbe.swift:47— scripts/fixtures/DuoHeldHardwareProbe.swift:47-126 | scripts/fixtures/DuoHeldModifierProbe.swift:47-127 — These two members are variants of one another: 51 of their lines are already reported as duplicated blocks below, spread through both bodies rather than gathered into one. Read them as a single construct written twice. The repair is at the members' grain — factor the shared pipeline into one implementation the two call with their differences as parameters or as an injected step, or, where the difference is systematic (sync against async, one transport against another), generate one from the other. Extracting the individual blocks below is not the same fix: it leaves the two bodies in place and the next edit still has to be made twice.
D4 · Code Duplication· Edited copy of a member (22 corresponding lines) · ×1
Edited copy of a member (22 corresponding lines) scripts/verification/verify-duo-held-hardware.py:162— scripts/verification/verify-duo-held-hardware.py:162-183 | scripts/verification/verify-duo-held-key.py:41-63 — These two members are one piece of code written twice and then edited apart: 22 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (5 corresponding lines) · ×1
Edited copy of a member (5 corresponding lines) scripts/bench-quick.py:114— scripts/bench-quick.py:114-119 | scripts/test-physical-devices.py:123-127 — These two members are one piece of code written twice and then edited apart: 5 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Duplicated block (23 lines × 2) scripts/fixtures/DuoHeldHardwareProbe.swift:87— scripts/fixtures/DuoHeldHardwareProbe.swift:87-109 | scripts/fixtures/DuoHeldModifierProbe.swift:87-109 — before extracting anything, compare `scripts/fixtures/DuoHeldHardwareProbe.swift` and `scripts/fixtures/DuoHeldModifierProbe.swift` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 51 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `scripts/fixtures/DuoHeldHardwareProbe.swift:87` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (7–8 lines × 2) scripts/fixtures/DuoRetainedPairProbe.swift:138— scripts/fixtures/DuoRetainedPairProbe.swift:138-145 | scripts/fixtures/DuoRetainedPairProbe.swift:210-216 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `scripts/fixtures/DuoRetainedPairProbe.swift:138` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (6 lines × 3) scripts/bench-quick.py:105— scripts/bench-quick.py:105-110 | scripts/sketch_picture.py:37-42 | scripts/test-physical-devices.py:104-109 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from all 3 call sites, so a change lands once.
Off the main sequence: AXeCore — AXeCore: 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.
Type Safety — 5 typed · 3 plain JS — the untyped files are promo-video/make-music.mjs, scripts/generate-github-release-notes.mjs, scripts/release-context.mjs.
R10 · Code Duplication· Duplicated block with local edits (28 matched lines × 2 locations) · ×1
Duplicated block with local edits (28 matched lines × 2 locations) scripts/generate-github-release-notes.mjs:75— scripts/generate-github-release-notes.mjs:75 · scripts/release-context.mjs:19 — the two spans are one implementation copied and then locally edited — 90 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 (5 lines × 2 locations) promo-video/src/scenes.tsx:318— promo-video/src/scenes.tsx:318 · promo-video/src/scenes.tsx:533 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Complex function (anonymous) (cyclomatic 24, cognitive 19) promo-video/src/scenes.tsx:623— (anonymous) has cyclomatic complexity 24 and cognitive complexity 19; 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 parseArgs (cyclomatic 21, cognitive 45) scripts/generate-github-release-notes.mjs:28— parseArgs has cyclomatic complexity 21 and cognitive complexity 45; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function extractChangelogSection (cyclomatic 16, cognitive 26) scripts/generate-github-release-notes.mjs:135— extractChangelogSection has cyclomatic complexity 16 and cognitive complexity 26; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function parseArgs (cyclomatic 16, cognitive 18) scripts/release-context.mjs:5— parseArgs has cyclomatic complexity 16 and cognitive complexity 18; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function (anonymous) (cyclomatic 14, cognitive 14) promo-video/src/lib.tsx:217— (anonymous) has cyclomatic complexity 14 and cognitive complexity 14; 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 buildContext (cyclomatic 12, cognitive 18) scripts/release-context.mjs:114— buildContext has cyclomatic complexity 12 and cognitive complexity 18; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
promo-video/src/scenes.tsx: 703 lines of code promo-video/src/scenes.tsx:1— promo-video/src/scenes.tsx has 703 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
No lint script — test ✓ · lint ✗ · typecheck ✓ — read from this repository's package.json scripts and corroborated against its CI workflows. A script counts when its name or command matches the step: `test` for the suite, `lint` or `prettier` for linting, `typecheck`/`type-check`/`tsc` for type checking. ✗ therefore means no script or CI step under those names was found, NOT that the step is absent from your pipeline — a task invoked by a runner this check does not read, or named something else entirely, is not seen and is worth confirming before acting on a cross. A ✓ means the wiring is DECLARED — a script or CI step under those names exists. It is not a statement that the step passes, or that it runs at all: nothing here installs a dependency or executes a suite.
Unused dependency '@remotion/media-utils' — Declared in promo-video/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 scripts/verification/verify-duo-held-hardware.py:29— `args.pid > 0 and 0 <= args.fold_angle <= 180` appears character-identically in 2 files — scripts/verification/verify-duo-held-hardware.py, scripts/verification/verify-duo-held-key.py. 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 Sources/AXe/Commands/Serve.swift:114— `$0 == "--udid" || $0.hasPrefix("--udid=")` appears character-identically in 3 files — Sources/AXe/Commands/Serve.swift, Sources/AXe/Utilities/Batch/BatchStepParser.swift, Sources/AXe/Utilities/Batch/PhysicalDeviceBatch.swift. 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 Sources/AXe/Utilities/AgentBatchReferencePlan.swift:211— `actions.contains(.tap) || actions.contains(.typeText)` appears character-identically in 2 files — Sources/AXe/Utilities/AgentBatchReferencePlan.swift, Sources/AXe/Utilities/AgentModeSnapshot.swift. 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 Sources/AXe/Commands/Clipboard.swift:155— `code == EINTR || code == EAGAIN || code == EWOULDBLOCK` appears character-identically in 2 files — Sources/AXe/Commands/Clipboard.swift, Sources/AXe/Device/RemoteXPCConnection.swift. 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 Sources/AXe/Device/PhysicalDeviceBrokerServer.swift:197— `count == 0 || (count < 0 && errno == EINTR)` appears character-identically in 4 files — Sources/AXe/Device/PhysicalDeviceBrokerServer.swift, Sources/AXe/Device/PhysicalDeviceBrokerSocket.swift, Sources/AXe/Utilities/HIDBroker.swift, Sources/AXe/Utilities/SelectedHIDBroker.swift. 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 Sources/AXe/Utilities/AgentModeSnapshot.swift:483— `element.actions.contains(.tap) || element.actions.contains(.typeText)` appears character-identically in 2 files — Sources/AXe/Utilities/AgentModeSnapshot.swift, Sources/AXeCore/RuntimeSnapshot.swift. 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 Sources/AXe/Utilities/AccessibilityFetcher.swift:465— `point.x >= frame.x && point.x <= frame.x + frame.width && point.y >= frame.y && point.y <= frame.y + frame.height` appears character-identically in 2 files — Sources/AXe/Utilities/AccessibilityFetcher.swift, Sources/AXeCore/RuntimeSnapshot.swift. 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.
D21 · Naming Consistency· `axTranslationPid` spells `Pid` where 183 names in the project spell it `PID` · ×2
`axTranslationPid` spells `Pid` where 183 names in the project spell it `PID` Packages/IDBKit/FBSimulatorControl/Commands/FBAXPlatformElement.swift:51— 183 of 187 names in project AXe spell the token `PID` (183 of 187; unit: names in project AXe containing `PID`). Peers: FBAXAliasTapSelection.select(expectedPID) (Packages/IDBKit/FBSimulatorControl/Commands/FBAXAliasTapSelection.swift:13); FBAXAliasTapSelection.match(hitPID) (Packages/IDBKit/FBSimulatorControl/Commands/FBAXAliasTapSelection.swift:76); FBAXAliasDirectTreeRules.compare(expectedPID) (Packages/IDBKit/FBSimulatorControl/Commands/FBAXAliasTapSelection.swift:129); Fields.nativePID (Packages/IDBKit/FBSimulatorControl/Commands/FBAXAliasTapSelection.swift:197); FBAXCheckBoxChildSelection.select(expectedPID) (Packages/IDBKit/FBSimulatorControl/Commands/FBAXCheckBoxChildSelection.swift:14). Rename to `axTranslationPID`. [rule N6]
`axTranslationPid` spells `Pid` where 183 names in the project spell it `PID` Packages/IDBKit/FBSimulatorControl/Commands/FBAXPlatformElement.swift:136— 183 of 187 names in project AXe spell the token `PID` (183 of 187; unit: names in project AXe containing `PID`). Peers: FBAXAliasTapSelection.select(expectedPID) (Packages/IDBKit/FBSimulatorControl/Commands/FBAXAliasTapSelection.swift:13); FBAXAliasTapSelection.match(hitPID) (Packages/IDBKit/FBSimulatorControl/Commands/FBAXAliasTapSelection.swift:76); FBAXAliasDirectTreeRules.compare(expectedPID) (Packages/IDBKit/FBSimulatorControl/Commands/FBAXAliasTapSelection.swift:129); Fields.nativePID (Packages/IDBKit/FBSimulatorControl/Commands/FBAXAliasTapSelection.swift:197); FBAXCheckBoxChildSelection.select(expectedPID) (Packages/IDBKit/FBSimulatorControl/Commands/FBAXCheckBoxChildSelection.swift:14). Rename to `axTranslationPID`. [rule N6]
D21 · Naming Consistency· `frontmostPid` spells `Pid` where 183 names in the project spell it `PID` · ×2
`frontmostPid` spells `Pid` where 183 names in the project spell it `PID` Packages/IDBKit/FBSimulatorControl/Commands/FBAXTranslationRequest.swift:183— 183 of 187 names in project AXe spell the token `PID` (183 of 187; unit: names in project AXe containing `PID`). Peers: FBAXAliasTapSelection.select(expectedPID) (Packages/IDBKit/FBSimulatorControl/Commands/FBAXAliasTapSelection.swift:13); FBAXAliasTapSelection.match(hitPID) (Packages/IDBKit/FBSimulatorControl/Commands/FBAXAliasTapSelection.swift:76); FBAXAliasDirectTreeRules.compare(expectedPID) (Packages/IDBKit/FBSimulatorControl/Commands/FBAXAliasTapSelection.swift:129); Fields.nativePID (Packages/IDBKit/FBSimulatorControl/Commands/FBAXAliasTapSelection.swift:197); FBAXCheckBoxChildSelection.select(expectedPID) (Packages/IDBKit/FBSimulatorControl/Commands/FBAXCheckBoxChildSelection.swift:14). Rename to `frontmostPID`. [rule N6]
`frontmostPid` spells `Pid` where 183 names in the project spell it `PID` Packages/IDBKit/FBSimulatorControl/Commands/FBAXTranslationRequest.swift:276— 183 of 187 names in project AXe spell the token `PID` (183 of 187; unit: names in project AXe containing `PID`). Peers: FBAXAliasTapSelection.select(expectedPID) (Packages/IDBKit/FBSimulatorControl/Commands/FBAXAliasTapSelection.swift:13); FBAXAliasTapSelection.match(hitPID) (Packages/IDBKit/FBSimulatorControl/Commands/FBAXAliasTapSelection.swift:76); FBAXAliasDirectTreeRules.compare(expectedPID) (Packages/IDBKit/FBSimulatorControl/Commands/FBAXAliasTapSelection.swift:129); Fields.nativePID (Packages/IDBKit/FBSimulatorControl/Commands/FBAXAliasTapSelection.swift:197); FBAXCheckBoxChildSelection.select(expectedPID) (Packages/IDBKit/FBSimulatorControl/Commands/FBAXCheckBoxChildSelection.swift:14). Rename to `frontmostPID`. [rule N6]
No ADRs found Package.swift:35— No ADRs found. No recognised ADR directory (`docs/adr/`, `docs/decisions/`, `adr/`, `docs/rfcs/`, an `ADR0001/` folder, or their siblings) exists anywhere in this tree. What was searched, so you can tell an empty log from a search that missed one: every directory under the tree (build output, dependencies and VCS metadata excepted), for a document that is either any non-index page inside a recognised ADR directory, whatever its name and however deeply nested (`docs/adr/use-postgres.md`, `docs/adr/2024/0001-x.md`); or a file anywhere whose name is ADR-shaped (`0001-use-postgres.md`, `adr-012-caching.md`); or, when neither turned anything up, a document carrying the decision-record signature (an "Architecture Decision Record" heading, or Status / Context / Decision / Consequences as section headings). A decision log that clears none of these — unnumbered files outside any recognised directory, without those headings — is not seen by this check and this row is then wrong. If that is your case, say so rather than renaming anything; otherwise, consider recording architectural decisions in `docs/adr/`. ADRs are expected here because `Package.swift` makes this repository a deployable product (line 35).
D21 · Naming Consistency· `displayId` spells `Id` where 247 names in the project spell it `ID` · ×1
`displayId` spells `Id` where 247 names in the project spell it `ID` Packages/IDBKit/FBSimulatorControl/HID/FBSimulatorNativeContextReader.swift:320— 247 of 252 names in project AXe spell the token `ID` (247 of 252; unit: names in project AXe containing `ID`). Peers: DuoControlsContact.contactID (AxePlaygroundApp/AxePlayground/Views/DuoControlsState.swift:50); DuoControlsTouchObserver.nextID (AxePlaygroundApp/AxePlayground/Views/DuoControlsTouchObserver.swift:7); DuoControlsTouchObserver.record(contactID) (AxePlaygroundApp/AxePlayground/Views/DuoControlsTouchObserver.swift:41); TouchMonitorPad.nextContactID (AxePlaygroundApp/AxePlayground/Views/TouchMonitorView.swift:99); TouchMonitorPad.record(contactID) (AxePlaygroundApp/AxePlayground/Views/TouchMonitorView.swift:145). Rename to `displayID`. [rule N6]
D21 · Naming Consistency· `uniqueId` spells `Id` where 247 names in the project spell it `ID` · ×1
`uniqueId` spells `Id` where 247 names in the project spell it `ID` Packages/IDBKit/FBSimulatorControl/HID/FBSimulatorNativeContextReader.swift:321— 247 of 252 names in project AXe spell the token `ID` (247 of 252; unit: names in project AXe containing `ID`). Peers: DuoControlsContact.contactID (AxePlaygroundApp/AxePlayground/Views/DuoControlsState.swift:50); DuoControlsTouchObserver.nextID (AxePlaygroundApp/AxePlayground/Views/DuoControlsTouchObserver.swift:7); DuoControlsTouchObserver.record(contactID) (AxePlaygroundApp/AxePlayground/Views/DuoControlsTouchObserver.swift:41); TouchMonitorPad.nextContactID (AxePlaygroundApp/AxePlayground/Views/TouchMonitorView.swift:99); TouchMonitorPad.record(contactID) (AxePlaygroundApp/AxePlayground/Views/TouchMonitorView.swift:145). Rename to `uniqueID`. [rule N6]
D21 · Naming Consistency· `AXUniqueId` spells `Id` where 247 names in the project spell it `ID` · ×1
`AXUniqueId` spells `Id` where 247 names in the project spell it `ID` Sources/AXe/Utilities/AccessibilityElement.swift:38— 247 of 252 names in project AXe spell the token `ID` (247 of 252; unit: names in project AXe containing `ID`). Peers: DuoControlsContact.contactID (AxePlaygroundApp/AxePlayground/Views/DuoControlsState.swift:50); DuoControlsTouchObserver.nextID (AxePlaygroundApp/AxePlayground/Views/DuoControlsTouchObserver.swift:7); DuoControlsTouchObserver.record(contactID) (AxePlaygroundApp/AxePlayground/Views/DuoControlsTouchObserver.swift:41); TouchMonitorPad.nextContactID (AxePlaygroundApp/AxePlayground/Views/TouchMonitorView.swift:99); TouchMonitorPad.record(contactID) (AxePlaygroundApp/AxePlayground/Views/TouchMonitorView.swift:145). Rename to `AXUniqueID`. [rule N6]
D21 · Naming Consistency· `normalizedUniqueId` spells `Id` where 247 names in the project spell it `ID` · ×1
`normalizedUniqueId` spells `Id` where 247 names in the project spell it `ID` Sources/AXe/Utilities/AccessibilityElement.swift:123— 247 of 252 names in project AXe spell the token `ID` (247 of 252; unit: names in project AXe containing `ID`). Peers: DuoControlsContact.contactID (AxePlaygroundApp/AxePlayground/Views/DuoControlsState.swift:50); DuoControlsTouchObserver.nextID (AxePlaygroundApp/AxePlayground/Views/DuoControlsTouchObserver.swift:7); DuoControlsTouchObserver.record(contactID) (AxePlaygroundApp/AxePlayground/Views/DuoControlsTouchObserver.swift:41); TouchMonitorPad.nextContactID (AxePlaygroundApp/AxePlayground/Views/TouchMonitorView.swift:99); TouchMonitorPad.record(contactID) (AxePlaygroundApp/AxePlayground/Views/TouchMonitorView.swift:145). Rename to `normalizedUniqueID`. [rule N6]
D21 · Naming Consistency· `normalizedStableUniqueId` spells `Id` where 247 names in the project spell it `ID` · ×1
`normalizedStableUniqueId` spells `Id` where 247 names in the project spell it `ID` Sources/AXe/Utilities/AccessibilityElement.swift:127— 247 of 252 names in project AXe spell the token `ID` (247 of 252; unit: names in project AXe containing `ID`). Peers: DuoControlsContact.contactID (AxePlaygroundApp/AxePlayground/Views/DuoControlsState.swift:50); DuoControlsTouchObserver.nextID (AxePlaygroundApp/AxePlayground/Views/DuoControlsTouchObserver.swift:7); DuoControlsTouchObserver.record(contactID) (AxePlaygroundApp/AxePlayground/Views/DuoControlsTouchObserver.swift:41); TouchMonitorPad.nextContactID (AxePlaygroundApp/AxePlayground/Views/TouchMonitorView.swift:99); TouchMonitorPad.record(contactID) (AxePlaygroundApp/AxePlayground/Views/TouchMonitorView.swift:145). Rename to `normalizedStableUniqueID`. [rule N6]
D26 · Project Cohesion· Projects may be oversized for their cohesion · ×1
Projects may be oversized for their cohesion — 1 of 4 project(s) overshoot their size bounds, lowering Project Cohesion to 5.0/10. The most over is `(repository root)` (41146 LoC, 615 module-visible types across 14 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.
No SAST REDACTED:4— No static application security testing detected. For this repository's stack, add CodeQL's Swift pack (Swift/Xcode) (or `semgrep --config=auto`, which runs on any language) as a CI step. What was searched, so you can tell an absence from a miss: the 7 CI workflow file(s) in this repository, and the scanner and linter configuration checked in beside them. A scan that runs outside CI, one configured in your forge's web UI rather than in a committed file, or a tool whose name is none of those this check carries, is not seen — if that is your case the row is wrong, and saying so is more useful than adding a second scanner.
No dependency-update automation promo-video/package.json:10— `promo-video/package.json` declares packages, and nothing in the repository keeps them current: no Dependabot or Renovate configuration that schedules updates, and no dependency-review gate on pull requests. A pinned dependency stays at the version it was added at until someone notices — including after an advisory is published against it. Add a `.github/dependabot.yml` with one `package-ecosystem` entry per ecosystem the tree uses (or an enabled `renovate.json`), and gate pull requests with `actions/dependency-review-action`.
Silent fallback default in catch Sources/AXeCore/AgentPolicy.swift:634— `captures` turns every thrown error into `[]` — a data error becomes a silent behavior change with no trail. Log the error or let it propagate (`throws`). 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 at the `catch`, `guard` or `??`, or in the doc comment, and the row stops firing.
Skipped (documented): settingsOnDisk Tests/RuntimeKeyboardLayoutTests.swift:92— Skipped with a documented reason — a deferral, not lazy debt: conditionally enabled — runs only when its .enabled(if:) condition holds
Skipped (documented): damagedDataIsSafe Tests/RuntimeKeyboardLayoutTests.swift:139— Skipped with a documented reason — a deferral, not lazy debt: conditionally enabled — runs only when its .enabled(if:) condition holds
Skipped (documented): germanFromRuntime Tests/RuntimeKeyboardLayoutTests.swift:157— Skipped with a documented reason — a deferral, not lazy debt: conditionally enabled — runs only when its .enabled(if:) condition holds
Skipped (documented): usFromRuntimeMatchesStaticTable Tests/RuntimeKeyboardLayoutTests.swift:172— Skipped with a documented reason — a deferral, not lazy debt: conditionally enabled — runs only when its .enabled(if:) condition holds
Skipped (documented): unknownLayout Tests/RuntimeKeyboardLayoutTests.swift:182— Skipped with a documented reason — a deferral, not lazy debt: conditionally enabled — runs only when its .enabled(if:) condition holds
Skipped (documented): namedDeviceLayout Tests/RuntimeKeyboardLayoutTests.swift:207— Skipped with a documented reason — a deferral, not lazy debt: conditionally enabled — runs only when its .enabled(if:) condition holds
Skipped (documented): installedRuntimesAreFound Tests/RuntimeKeyboardLayoutTests.swift:233— Skipped with a documented reason — a deferral, not lazy debt: conditionally enabled — runs only when its .enabled(if:) condition holds
Skipped (documented): layoutTravelsWithRequests Tests/RuntimeKeyboardLayoutTests.swift:255— Skipped with a documented reason — a deferral, not lazy debt: conditionally enabled — runs only when its .enabled(if:) condition holds
Skipped (documented): detectedLayoutFallsBackToUS Tests/RuntimeKeyboardLayoutTests.swift:277— Skipped with a documented reason — a deferral, not lazy debt: conditionally enabled — runs only when its .enabled(if:) condition holds
Skipped (documented): keysThatHoldTheirCharacterAreRefused Tests/RuntimeKeyboardLayoutTests.swift:291— Skipped with a documented reason — a deferral, not lazy debt: conditionally enabled — runs only when its .enabled(if:) condition holds
Skipped (documented): usKeepsFixedTable Tests/RuntimeKeyboardLayoutTests.swift:314— Skipped with a documented reason — a deferral, not lazy debt: conditionally enabled — runs only when its .enabled(if:) condition holds
Outdated: swift-argument-parser — `swift-argument-parser` is resolved at 1.5.0, but 1.8.2 is the newest release tagged on https://github.com/apple/swift-argument-parser within the same major. SwiftPM resolves from git tags, and a `from:` requirement admits every release below the next major — so `swift package update swift-argument-parser` reaches this one with no change to Package.swift.
Appendix B — Reproduction & audit trail
Every external tool invocation behind a deep-scan dimension — the tool, its captured version, the exact command, how many findings it yielded, and a link to the retained raw output. To reproduce any finding: check out the same commit and run the command shown (repo-relative — never an absolute scratch path). The complete raw scanner output is retained verbatim under artifacts/raw/ (indexed in artifacts/raw/index.json); per-invocation exit codes and wall-clock durations are in sidecar.json — kept out of this table so the rendered report stays byte-identical across runs of the same commit.
trivy: not applicable — No Infrastructure-as-Code or container manifests found (Dockerfile, Docker Compose, Terraform, Kubernetes/Helm, CloudFormation, ARM, Bicep, Ansible); nothing to scan.
semgrep: not applicable — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that. semgrep could not parse 38 file(s) — `AxePlaygroundApp/AxePlayground/ContentView.swift`, `AxePlaygroundApp/AxePlayground/Views/TouchControlView.swift`, `Packages/IDBKit/FBControlCore/Async/AsyncFBFutureBridge.swift`, `Packages/IDBKit/FBControlCore/Configuration/FBiOSTargetConfiguration.swift`, `Packages/IDBKit/FBSimulatorControl/Commands/FBAXOpaqueFrameTapAdmission.swift`, … (+33 more) — so the PII/GDPR sweep did not cover the unparsed regions of them; rows reported elsewhere in those files are real.
disclosure: not applicable — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed.
runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here.
runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here.
runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here.
Run 01a1dcbe-9b94-7487-86cf-f04d60cda5f3 · every finding is also locatable in findings.md, and the complete scoring record (with exit codes + durations) in sidecar.json.
Issues: 22 · Warnings: 703 · Recommendations: 27 · Info: 12 — Appendix A · all findings · full markdown report.
Generated by the Canine Code Analyzer: deterministic code-health analysis. 15-11-2026 @ 01:07 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.