Public report of OpenSwiftUIProject/OpenSwiftUI, published 29 October 2026. It has the same score, grades and number of
findings as the full report. The details of security findings (where they are in the code, which known
vulnerabilities and which passwords or keys were found) are left out, so nobody can use them against the project.
Public
Executive reportMeasured under the Code Assurance Index, an open standard for code quality, using its published scoring rules (rubric version 2026.10.5). Watchdog signed this survey and filed it in the standard's public register, where anyone can look it up by its survey ID. Check this survey →
Signed and filed in the standard's public register, 29 October 2026, 09:03 UTC · Survey ID cd_016215d26a304facbf3199121997ff90
OpenSwiftUIProject/OpenSwiftUI
Measured 29 October 2026, 08:57 UTC, at code version b480c9a
No regression since the last survey
A regression is a drop of 0.5 points or more in the score, or of 2.5 or more out of 10 in a dimension, since the last survey.
CAI scoreAdequate
CriticalWeakAdequateStrongExemplary
No change since the last survey
The score is built from these lenses. Each lens grades one area of the code, such as how easy it is to change or how well it is protected. The weakest lens counts most, so one weak area pulls the score down instead of being averaged away.
A large codebase: 210,795 lines of product code in 8 projects, tests not counted · Estimated rebuild effort: about 1.8 person-years · Weakest lens: Production Readiness, 45
Findings by how serious they are
99 critical1058 serious258 minor
18 dimensions are left out of the score. For each one, Watchdog either couldn't measure it in this code, or found no evidence of the safeguard it looks for, such as a tested backup restore. They count neither for nor against the score, and Limitations lists each one with its reason.
This survey was produced by
Watchdog
Producer
Canine Development
Analyzer
Watchdog engine 1.0.0
Measured
29 October 2026, 08:57 UTC
A measurement, not a certificate. The Code Assurance Index records a number
together with the evidence it was worked out from, so anyone can recalculate it, but it doesn't certify or guarantee
the code. The standard was written by Canine Development, which also builds Watchdog. It is open to any tool that
implements it, and today Watchdog is the only one that does.
The score is deterministic, which means the same code always gets the same score. Watchdog works it out with tools that follow published rules, and an AI model never decides it, so anyone who applies the same rules to the same code gets the same number. How it is done is explained under Methodology ▸
66of 66 dimensions measured by tools.
1387of 1415 findings point to an exact file and line, so you can open each one in the code. The other 28 concern the repository as a whole, such as missing documentation.
66dimensions across 6 lenses, read from 210,795 lines of product code in 8 projects.
OpenSwiftUIProject/OpenSwiftUI falls short of our standard for a preview release, in part because we found no automated security scanning of the code, its secrets or its dependencies. It scores 58 out of 100 and is rated Adequate, and 98 of its 99 critical findings are security problems.
Production Readiness, at 45, is the weakest lens and counts most in the score. The best first step for the work it takes is making the tests check their results, worth about 5 points. Adding automated security scanning would lift Production Readiness itself, worth about 8 points. Raising Production Readiness to 62 would lift the score to about 66.
Eighty-nine pipeline tools are referenced by a changeable name, so the build pipeline can be tampered with. Five secrets can leak from the build pipeline, and three pipeline steps put outside input straight into a shell command, so an attacker can run commands in the build pipeline. Pinning each tool to an exact version, limiting each secret to its own step and passing outside input through environment variables would close these risks. The password or key in the code's history needs replacing, with the old one switched off. The test that checks nothing needs to check the result it produces.
The product code is 210,795 lines, about €260,000 to rebuild.
A lens is capped at Adequate while one of its dimensions scores below 4 out of 10, however well the rest of the lens does. That way a serious problem in one place always shows in the lens's rating.
How the score is built: what each lens counts forThe lenses don't count equally. The weakest lens counts most, the next weakest a little less, and so on, so a weak area pulls the score down instead of being averaged away. In the bar below, each part's width shows how much that lens counts and its colour shows its rating. Improving the widest part moves the score most, and as that lens improves, it counts for less, because another lens becomes the weakest.
If Production Readiness rose from 45 to 62, the lowest score rated Strong, the score would rise from 58 to about 66.
Code composition: what the lines of code are
Product code 85%Tests 15%
New since the last survey: 223 findings
These 223 critical or serious findings weren't in the previous survey, on 15 October 2026. The first 100 are listed here, and the findings file in the download package lists them all.
Watchdog compares every finding with the previous survey's. A finding that has only moved to another line in the same file counts as the same finding, so only new findings appear here. Advisory notes from the AI model are left out, because the model words them afresh in every survey.
Fixed since the last survey: 55 findings
These 55 critical or serious findings were in the previous survey, on 15 October 2026, and are gone from this one.
€86,000 to €430,000, for 1,433 to 4,546 hours of work, about 1.8 person-years for 1 to 4 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 58. Better code takes more work to write, so the factor is ×1.0 at a score of 70, lower below it and higher above it.
Size
Large: 210,795 lines of product code
What it is not
Not a quotation: nobody has offered to build it for that. Not a valuation: it says nothing about what the business is worth. Not a certified figure: no professional has signed it as one.
How the estimate is made: Watchdog prices the hours a team would need to write this code again, at €60 to €95 an hour. Declarations and boilerplate are priced at a fast rate and logic at a slower one, and the logic is then multiplied by the difficulty of the problem and by the quality factor. The estimate can be about 30% off either way, and it moves most with the hourly rate and the difficulty. For this code, every line is priced as straight logic, which keeps the estimate on the low side.
Top priorities
The three actions that raise the score most for the work they take. The full ranked list is in the Roadmap.
1
Resolve the 1 No assertions (empty test) finding(s) in Test Quality — start with DynamicPropertyTests.swift.
Raises the score by about 5 points · Low effort · Test Quality
2
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.
Raises the score by about 5 points · Medium effort · Test Distribution
Diagnosis: what the measurements show together
Each conclusion below combines several dimensions into one point that no single dimension shows, and lists the measurements it rests on.
Where the investment is most exposed · Value at risk
This code would cost about €260,000 to build again, about 1.8 person-years of work. Its weakest lens is Production Readiness, at 45 (Weak). Production Readiness is about whether the product is ready to run in production and to change without breaking. Because the weakest lens counts most in the score, work on Production Readiness also moves the score most.
Based on: the rebuild estimate · the Production Readiness grade · how much each lens counts
What to do: Start with the Production Readiness actions in Top priorities.
If you do one thing first · First action
Resolve the 1 No assertions (empty test) finding(s) in Test Quality. Of all the actions in this report, it raises the score most for the work it takes: about 5 points for low effort, because it clears the 1 Test Quality 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 7.0 out of 10. Code at that level is slower to change than clean code, and Watchdog estimates the extra work at 2% to 5% on every change. The history of the code shows how much it changes: about 122,007 lines over the last 90 days, which is about 494,806 lines a year. At that pace, the extra work comes to an estimated 29.8 to 179 engineer-days a year, and it grows as more code changes.
How this is estimated: The number of changed lines is measured from the history of the code. The rest rests on two assumptions of Watchdog's own: code scoring 8 out of 10 or more adds no extra work, and each point below 8 adds 2.5% to 5.6% to every change, never less than 2% to 5% and never more than 40% to 60% in all; and an engineer changes 150 to 400 lines in a day. The result is a range for planning, not a measurement.
Based on: Cyclomatic Complexity · Cognitive Complexity · 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.
11 modules, with 10 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.
Uses a module listed above itPart of a loopThe module itself
5→9 OpenSwiftUICore uses OpenSwiftUIpart of a loop✕
Connections
705 pairs of types, where a type in OpenSwiftUICore uses a type in OpenSwiftUI. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
OpenSwiftUIExtension uses OpenSwiftUICore, so a change to OpenSwiftUICore can break OpenSwiftUIExtension, while a change to OpenSwiftUIExtension can't break OpenSwiftUICore.
Position
Below the diagonal: OpenSwiftUIExtension uses a module listed above it, which is the healthy direction.
OpenSwiftUIMacros uses OpenSwiftUICore, so a change to OpenSwiftUICore can break OpenSwiftUIMacros, while a change to OpenSwiftUIMacros can't break OpenSwiftUICore.
Position
Below the diagonal: OpenSwiftUIMacros uses a module listed above it, which is the healthy direction.
54 pairs of types, where a type in OpenSwiftUITestsSupport uses a type in OpenSwiftUICore. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
OpenSwiftUITestsSupport uses OpenSwiftUICore, so a change to OpenSwiftUICore can break OpenSwiftUITestsSupport, while a change to OpenSwiftUITestsSupport can't break OpenSwiftUICore.
Position
Below the diagonal: OpenSwiftUITestsSupport uses a module listed above it, which is the healthy direction.
3626 pairs of types, where a type in OpenSwiftUI uses a type in OpenSwiftUICore. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
OpenSwiftUI uses OpenSwiftUITestsSupport, so a change to OpenSwiftUITestsSupport can break OpenSwiftUI, while a change to OpenSwiftUI can't break OpenSwiftUITestsSupport.
Position
Below the diagonal: OpenSwiftUI uses a module listed above it, which is the healthy direction.
OpenSwiftUIBridge uses OpenSwiftUICore, so a change to OpenSwiftUICore can break OpenSwiftUIBridge, while a change to OpenSwiftUIBridge can't break OpenSwiftUICore.
Position
Below the diagonal: OpenSwiftUIBridge uses a module listed above it, which is the healthy direction.
OpenSwiftUIBridge uses OpenSwiftUI, so a change to OpenSwiftUI can break OpenSwiftUIBridge, while a change to OpenSwiftUIBridge can't break OpenSwiftUI.
Position
Below the diagonal: OpenSwiftUIBridge uses a module listed above it, which is the healthy direction.
Findings mapped to OWASP categories; the specific CVEs/secrets are in the Security dimension cards below and findings.md (redacted only on the public version of this report).
OWASP category
Findings
Severity
A05:2025 — Injection
97
High / Critical
A03:2025 — Software Supply Chain Failures
7
Medium
A07:2025 — Authentication Failures
2
High / Critical
Roadmap
First, integrate automated security scanning into the CI pipeline to block regressions before they land. Next, enhance test distribution and eliminate empty tests to improve overall quality. Finally, enforce manual approval gates for releases to prevent bad builds from going live, and begin adopting TypeScript in the frontend to strengthen type safety.
Ranked by impact ÷ effort. "Helps" is the estimated gain on the 0–100 health score.
Do this
Helps
Effort
Dimension
Resolve the 1 No assertions (empty test) finding(s) in Test Quality — start with DynamicPropertyTests.swift.
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.
Make sure a person approves each release. The release job names an environment, but its approval rules live in the code host's settings, where Watchdog can't see them. Check that a reviewer must approve each release, or publish releases as drafts first, so a bad build can be stopped before anyone downloads it.
Adopt TypeScript for the frontend: add a typecheck step to the build, then either type-check the existing JavaScript in place (`checkJs`/JSDoc types) or convert the highest-traffic modules first — no file is typed today, so this is an adoption, not a clean-up.
Every finding carries one of four grades. Three say how serious it is. The fourth says this
survey could not settle it — and it is a grade, not a gap.
Critical — 99
A definite problem that already costs you something and drags the score down: a
missing authorisation check, a dependency with a known exploit, a build that does not reproduce. Failure here
tends to cause failures elsewhere.
Serious — 1058
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 — 258
Recorded, with no effect on how the codebase functions.
Present so the survey is complete, not because it needs doing.
Could not be resolved — 18
Something this survey could not settle
from the outside, and which could be critical or serious. Either a control was required and no
positive evidence of it exists in the repository — a backup job that nothing shows was ever restored from proves
nothing about restores — or our own analysis could not run over that part of the tree. This is not a clean
result. These are excluded from the score rather than awarded a pass, so the number on the cover neither
rewards nor penalises them: if you act on this survey without resolving them, you carry that risk yourself. Each
one is named under Limitations.
Methodology & how to trust this report
Watchdog is a deep, periodic assessment — run each sprint, monthly, or quarterly, taking the time to go wider and deeper than a quick check and surfacing in one coherent report what you'd otherwise piece together from a dozen separate tools. It scores deterministically: the same commit yields the same score, every run. 66 of 66 evaluated dimensions are computed purely by tools and static analysis (confidence 1.0); none rely on LLM judgement. Overall confidence is 0.8 — the weighted average across measured dimensions; it falls as more of the score leans on LLM-assisted judgement and rises when it's fully tool-backed.
Every figure here is one of three kinds, and we label which: ✓ Measured — a deterministic fact (LoC, complexity, coverage); ~ Modeled — an estimate from a stated model (cost, effort, value-at-risk), always a range with its assumptions, never a precise fact; ◐ Advisory — an LLM prose judgement. We never present a modelled estimate as if it were measured. Perfect or absent scores carry their provenance too (ADR-0011): ✓ Tool-verified means the property itself was measured across the surface; ○ Nothing flagged means the probes came back clean — a claim bounded by what a repository can show; ⊘ Not evidenced means a working control (a tested restore, an automated rollback) showed no positive evidence — absence of evidence is not evidence of a control, so it's excluded from the score rather than awarded a spurious 10; ◐ Sampled · advisory marks an LLM verdict over a bounded sample — advisory, never a deterministic measurement.
What we checked — 66 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, 1387 of 1415 do; the remainder are repo-wide signals — a dimension-level measurement, not a single line. (Every path in this report is repo-relative by construction: paths are normalized at the producer and the report is rejected if any rooted path leaks through.)
Is there a tool behind the number? Every score below names the method that produced it — Roslyn, git, a scanner, or (for a handful of documentation/naming dimensions) an LLM labelled sampled · advisory — not a narrative.
Does re-running give the same result? Run it again on the same commit and the score — and this report, byte for byte — is identical. A report whose numbers move between runs is describing the run, not the code.
This report answers yes to all three. That's the bar to hold any assessment to.
Tools & methods
The actual versions used this run (captured at analysis time) — re-run on the same commit for the identical score.
Method
Backs
Version
Evaluator
Roslyn static analysis
Complexity, cohesion, coupling, dead code, API surface, layering
What ran differently this time — a tool absent, degraded, or that fell back to an estimate. Named openly, not folded silently into the scores. A degraded run also records its exact cause in diagnostics.md.
D8 Code Coverage — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. 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 — a Codecov configuration (.codecov.yml) and a coverage step in CI (`xcrun llvm-cov`) shows coverage is measured in your own CI. Commit the lcov/Cobertura report it produces and the real number is read on the next scan. You can widen what we reach: optional: commit the lcov/Cobertura report your CI produces, and the real number is read on the next scan.
D11 Test Reliability — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Test source is present (.swift) and this repository declares a SwiftPM test suite (2 packages), but it was not re-run: the analyzer environment could not run it. 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 — Watchdog measured this, but not all of it. What it did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. 4 of this repository's SwiftPM dependencies could not be fetched at a pinned revision and are repositories api.deps.dev has not indexed, so their licences were not read and the verdict does not cover them: lookinserver, lookinside-release, opencombine, versioneddocc.
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 (7 contributor(s) across 1320 commit(s) sampled, automation and bot accounts excluded). One of them holds 96% of the history; the other 6 hold 0.7% 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 — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. D21's deterministic naming rules are gated on C# first (docs/plans/deterministic-engine.md, P5): each other language is switched on only after its own concept suite and A/B gate pass. Until then its declarations carry no naming verdict this run — this says nothing about whether its names are consistent.
D22 Internal API Consistency — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. D22 identifies the intentionally-exposed surface from `IsPackable` and `.Contracts` project names, MSBuild conventions read off the loaded project set. This target exposed no such projects, so the probe never ran; this says nothing about whether the repository has a public API. This repository commits no C#/VB source at all, so there was never an MSBuild project set to read these conventions off. That is OUR side and it is a COLLECTOR gap, not an environment fault: it declares a published package (Package.swift), but no published-package marker D22 reads admitted any project here, so this ecosystem's public API has no collector, and the remedy is to write one — no change to the scan image can close it.
D24 Comment Value — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check's reader does not cover the language this repository's product is written in, so it had nothing of the product to read. That is a gap in this analyzer's language reach — not a finding about this repository.
D27 Navigability — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Navigability is taken over call sites whose callee resolved. For C# that population includes calls into referenced assemblies; for this language only calls declared inside the repository count, so the abstention threshold reads the repository's use of its standard library as a resolution failure. That is a limit of this analyzer, not a build problem in this repository.
D32 Data Compliance (PII/GDPR) — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. `Example/Shared/Animation/Animatable/ViewUnanimatableExample.swift`, `Example/Shared/Animation/Animation/AnimationCompleteExample.swift`, `Example/Shared/Animation/Animation/ColorAnimationExample.swift`, `Example/Shared/Animation/Animation/ElasticEaseInEaseOutAnimationExample.swift`, `Example/Shared/Animation/Animation/RepeatAnimationExample.swift`, … (+693 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 — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This dimension reads a project's own statement about the platform it runs on: a TargetFramework in a .NET project file, a .nvmrc or .python-version, a capped requires-python, a Rust toolchain file or Cargo.toml rust-version, a .go-version, .java-version, .ruby-version, .tool-versions or .sdkmanrc, a go.mod go directive, a Maven or Gradle Java level or toolchain, a Gemfile's ruby directive, a mix.exs elixir requirement, a rebar.config minimum_otp_vsn, a pubspec.yaml SDK constraint, a build.sbt scalaVersion, or a framework major pinned by a dependency constraint. This repository carries none of them, so nothing about its platform was established. That is a gap in this analyzer's coverage, NOT a finding that the platform is supported — a language whose runtime is declared elsewhere (Package.swift, a Dockerfile) is simply not read here yet.
AX6 Interface segregation — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is computed over the public interfaces this run's compilations declare, and none was loaded, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
C1 Data Protection — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. 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 — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. 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 — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. 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.
GD1 Unfinished & placeholder code — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, F#, JavaScript/TypeScript, Dart, Ruby and Scala source only, and this repository's Python, 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 — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, JavaScript/TypeScript, Java, Dart, Ruby and Scala source only, and this repository's Python, 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 — Watchdog measured this, but not all of it. What it did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. M4 checks only the claim kinds adjudicated at or above 95 % precision: links and versions (PREREGISTRATION version 9), 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 — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. 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.
X2 Cancellation propagation — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, 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; 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.
X4 Structured logging — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Java, Kotlin, Python, PHP, Dart, Ruby, Scala and Rust source only, and no C# was loaded, and this repository's JavaScript/TypeScript, Python and PHP make no call through a named logger, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
X5 Nullable reference types — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax and MSBuild project configuration, TypeScript source and its tsconfig files, Java source and its package and module declarations, PHP source and its PHPStan and Psalm configuration, Dart source and its pubspec language version, Ruby source and its Sorbet and Steep configuration, Scala source and its build's explicit-nulls, WartRemover and Scalafix settings, and Kotlin source only, and no C# was loaded, no TypeScript was found, and this repository's C, Objectivec, Python, Swift 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.
Repo exclusion declarations (.gitattributes linguist-generated/vendored, .editorconfig generated_code): none declared — every source file was scored.
Limitations & what we did not check
Watchdog assesses the repository exactly as committed, and only the repository. By design it does not reach outside the source tree: the live cloud account, the running CI/CD pipeline, the host's branch-protection and approval rules, the production configuration, or a restore actually exercised against a backup are all out of scope. That boundary is a feature, not a gap — a repo-relative, deterministic scan re-runs identically on any commit and every finding opens at a real file and line, where a live audit can neither be reproduced nor traced. The visible consequence is that controls which leave no in-repo evidence are reported as "not evidenced" and excluded from the score rather than awarded a number a static scan cannot justify.
Per-dimension blind spots
For each dimension that was measured, what a static, repo-only scan structurally cannot see — the honest edge of the measurement, not a failure of it.
D1 Cyclomatic Complexity: Cyclomatic complexity counts branches statically — it cannot tell an essential decision tree from accidental tangle, nor see complexity that lives in data or configuration (large switch-case token tables, DSL lexers/parsers, data-as-code rule tables) rather than control flow: a tokenizer's many single-character cases read as high complexity though each branch is trivial.
D2 Cognitive Complexity: Cognitive-complexity heuristics approximate how hard code is to follow; genuine domain difficulty and well-named intent that eases reading are not captured.
D3 God Classes: "God class" is sized by members and responsibilities visible in the type — a deliberately broad facade over a coherent subsystem can read the same as an accidental grab-bag. For front-end JS the file-length check is cohesion-aware (a single-responsibility module — one class/IIFE — earns a 3× threshold), but cohesion is approximated from top-level declarations, not true dependency structure.
D4 Code Duplication: Duplication is token-similarity — an in-process token-stream comparison over sliding windows, with type-aware normalization — so it finds copy-paste, not semantic duplication expressed differently. Committed machine-written code (scaffolded migrations, designer/codegen output, protobuf/OpenAPI stubs, model snapshots) is EXCLUDED — its repetition is the tool's, not the team's — so the score reflects hand-written duplication only.
D5 Coupling: Coupling is measured between projects/assemblies — runtime coupling through DI, reflection, messaging or shared databases is invisible to a static reference graph.
D6 Cohesion (LCOM4): LCOM4 cohesion is syntactic — it infers connectivity from which methods touch which fields/methods by name, not from real runtime behaviour or intent.
D9 Test Distribution: The test-pyramid shape is inferred from project/folder naming and references, with a single test host bucketed per-file by its path tier and content signals — a suite that names tiers unconventionally and gives no per-file signal can still be mis-bucketed.
D10 Test Quality: Assertion density is structural — it cannot tell a meaningful behavioural assertion from a trivial one, only that an assertion is present.
D12 Dependency Hygiene: Dependency health reads manifests and lockfiles — a vulnerability in a vendored/copied dependency, or risk from how a dependency is actually used, is outside this view.
D13 REDACTED Scanning: REDACTED detection is signature- and entropy-based on the current tree — a secret that does not match a known pattern, or one already rotated, will not be flagged (a clean scan is "nothing matched", not "no secrets exist").
D14 License Compliance: License compatibility is checked against declared package metadata and a policy — mislabelled or missing license metadata, and obligations that depend on how you distribute, are not resolved here.
D15 Churn × Complexity Hotspots: Churn hotspots come from git history — a freshly imported or squashed repository has no churn signal, and recent rewrites can mask a historically risky file.
D17 Explicit Debt: Acknowledged-debt signals (TODO/FIXME, suppressions, dead code) are textual — undocumented debt that nobody marked, and debt that lives in design rather than annotations, is invisible. Committed machine-written code (scaffolded migrations, designer/codegen output, generated stubs) is excluded — it is never the team's dead code to delete.
D20 ADR Quality: ADR quality is an LLM read of the decision records present — it cannot know about decisions made and never recorded, and its verdict is sampled and advisory.
D26 Project Cohesion: Project focus is sized from members/namespaces per project — a project that is broad by deliberate design reads the same as one that has sprawled.
D28 Secrets (history): Secret-history scanning sweeps the git log for known patterns — a secret that predates the available history, or never matched a signature, is not found (clean means "nothing matched in the history we can see").
D29 Static Analysis (SAST): SAST findings are pattern-based (semgrep) — it finds classes of bug it has rules for; logic flaws, auth/authorization gaps and issues needing runtime context are out of reach (and clean means "no rule matched").
D30 Dependency Vulnerabilities: CVE matching depends on accurate package/version metadata and on the advisory databases — a vulnerability with no published advisory, or in code not declared as a dependency, is not seen. Coverage needs a RESOLVED graph: an unpinned requirements.txt, or a pom without a resolved build, yields partial coverage rather than a clean verdict. An ecosystem the analyzer cannot scan is reported as unmeasured, never as clean.
D34 Knowledge Freshness: Freshness is decayed commit RECENCY, not comprehension — code read often but rarely committed reads as orphaned, and stable code that genuinely needs no changes is penalised the same as forgotten code; bot/squash commits distort it like the bus factor.
D35 Change Coupling: Change coupling is co-change in COMMITS — files split across separate commits, or coupled only through a shared config/build step, read as uncoupled, and a sweeping commit (rename/format) is excluded so it doesn't couple everything. It shows that files change together, not WHY: a high coupling can be a healthy cohesive pair as readily as a hidden leak.
D43 Malicious Dependencies: Only packages some vulnerability database has already NAMED as malicious are seen — a compromise published in the last hours, or never reported at all, is invisible here, and this dimension reading 10 is not evidence that a dependency is trustworthy. There is no typosquat or dependency-confusion analysis: a package nobody has reported is simply absent from the feeds. Coverage is the dependency scan's: an ecosystem that could not be scanned is disclosed as unmeasured, never as clean.
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: Onboarding quality is an LLM read of the docs/setup present — it cannot run the onboarding or measure how long a real new joiner takes; the verdict is sampled and advisory.
P4 Deployment & Rollback: Approval/branch-protection rules live in repository settings the scan cannot see — only their in-repo evidence (config files, workflows) is checked, so a control enforced purely in the host's settings reads as "not evidenced".
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.
87 method(s) exceeded the cyclomatic complexity threshold of 15; the worst was DefaultSystemColorDefinition_PhoneTV.value at 88. A further 11 method(s) were over the threshold but excluded as flat dispatchers (a long switch/match over independent cases: many branches, almost no nesting), the largest being AccessibilityTrait.uiTrait at 23 — they are counted neither in the figure above nor in this dimension's score. 5 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/OpenSwiftUICore/Accessibility/AccessibilityTraits.swift (AccessibilityTrait.uiTrait at 23), Sources/OpenSwiftUICore/Graphic/GraphicsConversions.swift (BlendMode.init at 22), Sources/OpenSwiftUICore/Graphic/GraphicsFilter.swift (GraphicsBlendMode.init at 22), Sources/OpenSwiftUICore/Graphic/Color/CoreUIDefaultSystemColorDefinition.swift (CoreUIDefaultSystemColorDefinition.value at 19), Sources/OpenSwiftUICore/Accessibility/AccessibilityNodeAttachment.swift (V3.init at 18). 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.
+ 81 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Bring the 2 bodies over 60 down to 60 or less in Cyclomatic Complexity — start with DefaultSystemColorDefinition_PhoneTV.value (cyclomatic 88), CustomRecursiveStringConvertible.swift.colorNameForColorComponents (cyclomatic 66). — 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 2 together lifts Cyclomatic Complexity from 6.1 to about 6.5/10, projected with the scoring formula itself and assuming each lands exactly at 60; a cleaner split scores higher.
Enforce Cyclomatic Complexity in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
Detailed fixes: d1_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: How hard the code is for a person to follow, beyond raw branching.
Method: Cognitive complexity per method (Sonar-style nesting-penalized score), computed exhaustively over production code, excluding test projects. Deterministic.
+ 132 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Bring the 9 bodies over 60 down to 60 or less in Cognitive Complexity — start with DefaultSystemColorDefinition_PhoneTV.value (cognitive 128), DynamicContainerInfo.updateValue (cognitive 100), Platform.updateItemView (cognitive 91). — 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 9 together lifts Cognitive Complexity from 5.8 to about 6.5/10, projected with the scoring formula itself and assuming each lands exactly at 60; a cleaner split scores higher.
Enforce Cognitive Complexity in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
Detailed fixes: d2_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D3 · God Classes8.8 / 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 37 FileTooLong finding(s) in God Classes — start with DisplayListViewPlatform.swift, ViewList.swift, Text+View.swift. — One of this dimension's main actionable groups (37 warning-level).
Resolve the 19 TooManyMethods finding(s) in God Classes — start with NSHostingView.swift, UIHostingView.swift, ProtobufEncoder.swift. — One of this dimension's main actionable groups (19 warning-level).
Resolve the 11 MethodTooLong finding(s) in God Classes — start with DisplayListViewPlatform.swift (3), _SymbolEffect.swift, SystemColors.swift. — One of this dimension's main actionable groups (11 warning-level).
Enforce God Classes in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
Detailed fixes: d3_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Copy-pasted code that should be shared instead.
Method: Code duplication via token-stream sliding windows with type-aware normalization (locals masked, type names preserved), density-scored per KLoC of production code. Deterministic.
165 duplicated block group(s) detected. A further 4 rows report members as variants of one another; they aggregate block groups already counted above and are not themselves counted. 9 of the 169 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.
+ 49 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Resolve the 15 Duplicated block (11 lines × 2) finding(s) in Code Duplication — start with TaskModifier.swift (2), FocusBridge.swift, PreferenceSceneModifier.swift. — One of this dimension's main actionable groups (15 warning-level).
Resolve the 15 Duplicated block (7 lines × 2) finding(s) in Code Duplication — start with SliderMark.swift, Stepper.swift, ColorMatrix.swift. — One of this dimension's main actionable groups (15 warning-level).
Resolve the 15 Duplicated block (5 lines × 2) finding(s) in Code Duplication — start with SystemColors.swift (3), AccessibilityActionCategory.swift, DynamicProperty.swift. — One of this dimension's main actionable groups (15 warning-level).
Enforce Code Duplication in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Verified — provenance only; does not change the score.
Detailed fixes: d4_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D5 · Coupling9.0 / 10Stronggated by 1 serious finding✓ 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.
8 production modules (SwiftPM), 0 dependency cycle(s), 0 unstable depended-on module(s). Read from the build's own module declarations; 1 module(s) off the main sequence, with abstractness counted on 5 of the 8 (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: OpenSwiftUICore
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).
Enforce Coupling in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
Detailed fixes: d5_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether a class's methods are focused on a single responsibility.
Method: LCOM4 cohesion per production class with at least two methods: connected components of methods sharing state or calls, computed syntactically. Deterministic, not a proxy.
Coverage: Exhaustive · type-level: LCOM4 cohesion computed over every production class — the population is all types, not a name convention.
Resolve the 65 Low cohesion finding(s) in Cohesion (LCOM4) — start with CalendarDependentFormatStyle.swift (3), CoreGlue.swift (2), SizeAdaptiveFormatStyle.swift (2). — One of this dimension's main actionable groups (65 warning-level).
Enforce Cohesion (LCOM4) in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Verified — provenance only; does not change the score.
Detailed fixes: d6_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D9 · Test Distribution7.8 / 10Strong✓ Tool-verified
What it measures: Whether the test suite has a healthy mix of unit / integration / end-to-end tests.
Method: Test projects classified (Unit/Integration/BDD/E2E) from compiled metadata; test methods counted exhaustively across projects with placement-agnostic disk fallback. Deterministic.
1741 test methods: 1358 unit, 84 integration, 0 BDD, 299 e2e.
What to do
Improve Test Distribution — currently 7.8/10. — 1741 test methods: 1358 unit, 84 integration, 0 BDD, 299 e2e.
Detailed fixes: d9_recommendation.md.
Do you agree with this assessment?
D10 · Test Quality9.3 / 10Adequategated by 1 critical finding✓ 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.
42 skipped (39 with a documented reason), 271 zero-assertion, no mocking-framework packages referenced (hand-written doubles or no mocking) across 1741 tests (2 harness-style project(s) excluded from the assertion penalty).
No assertions (empty test): exampleTests/OpenSwiftUICoreTests/Data/DynamicProperty/DynamicPropertyTests.swift:9
No assertions: application · ×80Tests/COpenSwiftUITests/Shims/AppKitPrivateTests.swift:12
No direct assertions: testEntryMacroExpansion · ×190Tests/OpenSwiftUIMacrosTests/EntryMacroTests.swift:22
Test project verifies nothing: OpenSwiftUIMacrosTestsTests/OpenSwiftUIMacrosTests/EntryMacroTests.swift:22
+ 1 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Resolve the 1 No assertions (empty test) finding(s) in Test Quality — start with DynamicPropertyTests.swift. — One of this dimension's main actionable groups (1 issue-level).
Resolve the 80 No assertions finding(s) in Test Quality — start with InsetViewModifierTests.swift (5), GradientTests.swift (4), AngleCompatibilityTests.swift (4). — One of this dimension's main actionable groups (80 warning-level).
Resolve the 3 Skipped test finding(s) in Test Quality — start with TimerUtilsTests.swift (2), ForEachUpdateTests.swift. — One of this dimension's main actionable groups (3 warning-level).
Enforce Test Quality in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
Detailed fixes: d10_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether dependencies are current, secure, and not bloated.
Method: Manifest scan via dotnet list package across all projects; worst-signal-per-package deduction (saturating for vulnerabilities, capped-linear for deprecation/outdated) per KLoC. Exhaustive, deterministic.
2 outdated direct SwiftPM dependencies, 14 pinning defect(s). 10 of 27 direct dependencies had their releases listed (0 naming no readable repository, 17 pinned to a branch or a revision rather than a version). 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.
Dependency not covered by the committed resolution: opencombine · ×7
Floating branch dependency: equatable · ×6
No Package.resolved committed (Renderer/Stdout/Tuist/Package.swift)
Outdated: package-benchmark · ×2
What to do
Resolve the 7 Dependency not covered by the committed resolution finding(s) in Dependency Hygiene. — One of this dimension's main actionable groups (7 warning-level).
Resolve the 6 Floating branch dependency finding(s) in Dependency Hygiene. — One of this dimension's main actionable groups (6 warning-level).
Resolve the 1 No Package.resolved committed (Renderer/Stdout/Tuist/Package.swift) finding(s) in Dependency Hygiene. — One of this dimension's main actionable groups (1 warning-level).
Enforce Dependency Hygiene in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Verified — provenance only; does not change the score.
Detailed fixes: d12_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether any secrets (keys, tokens, passwords) have leaked into the code.
Method: In-process native secret scanner (entropy plus signature patterns) across all tracked files; no external tool. A clean result is a measured 10, not no-data zero. Deterministic.
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 28 SwiftPM package(s) use a banned license. SwiftPM has no package registry, so each package's licence is the one its repository declares: 26 of them read from the licence file the repository carries at the revision Package.resolved pins, and 2 — 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. 11 of them are declared by a manifest that commits no Package.resolved (a library, whose resolution is its consumer's), so their own dependencies are resolved by whoever builds it and are not in this verdict. ★ 4 package(s) could not be read at a pinned revision and are not known to the index, and were NOT graded — this verdict does not cover them: `lookinserver`, `lookinside-release`, `opencombine`, `versioneddocc`.
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.
Resolve the 4 Hotspot finding(s) in Churn × Complexity Hotspots — start with UIHostingView.swift, Path.swift, ShapeLayer.swift. — One of this dimension's main actionable groups (4 warning-level).
Resolve the 1 Repeated repair finding(s) in Churn × Complexity Hotspots — start with release.js. — One of this dimension's main actionable groups (1 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.
548 deducted task-comment markers across 210795 LoC (0.3/KLoC) → score 9.5. 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.
TodoComment · ×346Package.swift:308
FixmeComment · ×66Package.swift:224
FixmeComment repeated across 35 filesSources/OpenSwiftUICore/View/ViewDebug.swift:205
TodoComment repeated across 29 filesSources/OpenSwiftUICore/View/Text/AttributedString/AttributedStringKey+Extension.swift:11
What to do
Resolve the 346 TodoComment finding(s) in Explicit Debt — start with AccessibilityConfiguration.swift (32), ArchivedView.swift (29), NSHostingView.swift (25). — One of this dimension's main actionable groups (346 warning-level).
Resolve the 66 FixmeComment finding(s) in Explicit Debt — start with Package.swift (7), Path.swift (4), EquatableViewCompatibilityTests.swift (3). — One of this dimension's main actionable groups (66 warning-level).
Resolve the 1 FixmeComment repeated across 35 files finding(s) in Explicit Debt — start with ViewDebug.swift. — One of this dimension's main actionable groups (1 warning-level).
Enforce Explicit Debt in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
Detailed fixes: d17_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D20 · ADR Quality0.0 / 10Critical✓ Tool-verified
What it measures: Whether architecture decisions are recorded well (context, decision, consequences).
Method: Per-ADR judgment by language model at low temperature with two-pass stability; confidence is share of ADRs evaluated; enforcement-field presence detected deterministically. Advisory.
1 of 3 build units (SwiftPM) flagged as possibly oversized/incoherent.
Projects may be oversized for their cohesion
What to do
Resolve the 1 Projects may be oversized for their cohesion finding(s) in Project Cohesion. — One of this dimension's main actionable groups (1 recommendation-level).
Detailed fixes: d26_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether any secrets were ever committed — scanned across the full git history, not just now.
Method: REDACTED scan via TWO gitleaks detect passes in an isolated checkout — the full git history, then a second --no-git pass over the working tree as it stands — merged and de-duplicated by (rule, file, line); each match flagged High. Both invocations are recorded in the audit trail. Exhaustive; when the tool is absent, or when its output cannot be parsed into the expected shape, the dimension is WITHHELD as an explicit measurement gap on our side — unscored and excluded from the lens, never a hedged middling score.
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).
97 finding(s): 0 critical, 97 high, 0 medium, 0 low. 82 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 31 file(s) — `Scripts/build_xcframework_slice.sh` (line 54, line 117), `Scripts/extract-documentation-symbol-graphs.sh` (lines 154–300), `Sources/COpenSwiftUI/Overlay/UIKit/UIKitFocusableViewResponderItemBase.h` (lines 17–18, line 19, line 20), `Sources/COpenSwiftUI/Shims/AppKit/AppKit_Private.h` (line 12, lines 20–23, line 26, …), `Sources/COpenSwiftUI/Shims/AppKit/NSGestureRecognizer_Private.h` (line 13, lines 19–20, line 22, …), … (+26 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 5 file(s) (e.g. a workflow `run:` block read as shell). Those files WERE scanned and their other rows are unaffected; only those rules' view of those snippets is missing.
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
+ 2 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Resolve the 5 REDACTED finding(s) charged to Static Analysis (SAST) — the other 80 are reported here at file:line but scored by D36 (supply-chain provenance), which charges them once. — One of this dimension's main actionable groups (85 issue-level, 5 of them charged here).
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).
No action in Static Analysis (SAST) — all 2 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 (2 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.
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 682 of the 1083 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.
What it measures: Whether files that change together actually belong together — pairs that repeatedly co-change in git history despite having no explicit code dependency, surfacing the hidden/logical coupling (and boundaries in the wrong place) a static scan can't see.
Method: Pairwise co-occurrence over the per-commit file sets in git history (production source only — tests and generated dropped): Degree-of-Coupling = shared ÷ min individual revisions, reported above noise floors (each file ≥10 revisions, ≥5 shared commits, ≥50% strength); sweeping commits excluded. Deterministic over fixed history.
Coverage: Population: PRODUCTION source files only — test and generated files are dropped before pairing, so a class co-changing with its own test (trivially ~100%) can't drown the real production↔production coupling. Pairs ranked by Degree-of-Coupling. A non-source file is never a coupling PARTICIPANT either: documentation, schemas, config and data files are dropped with the rest, so a code↔docs pair — a command and the reference page that restates it — is not reported however strongly the two co-change; nor is coupling that runs THROUGH a build step or config file.
Resolve the 2 Change coupling finding(s) in Change Coupling — start with AppKitDisplayList.swift, CustomViewModifier.swift. — One of this dimension's main actionable groups (2 warning-level).
Detailed fixes: d35_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether the 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 2 REDACTED finding(s) in Supply-chain Provenance & Signing — start with REDACTED, REDACTED. — One of this dimension's main actionable groups (2 warning-level).
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. — One of this dimension's main actionable groups (1 recommendation-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. Scored apart from D30 because the answer is binary: there is no safe version to upgrade to, and the fix is to remove the package and rotate every credential it could have read.
Method: The same dependency scan D30 reads, partitioned on the scanner's own classification rather than rescanned: a row is MALICIOUS when its id is in the `MAL-` space (the ossf/malicious-packages feed) OR its `database_specific.cwe_ids` carries `CWE-506` ("Embedded Malicious Code"). Both channels are structural; the summary text is deliberately NOT read, because a malicious-package record whose summary says only "Critical severity vulnerability" is a real shape ([GHSA redacted]) and a text matcher misses it. Scored BINARY: any surviving row is 0, whatever its severity and however many CVEs sit beside it — a hostile dependency is not a quantity. Applicability and degradation are D30's: NotApplicable only when no ecosystem is readable, and an unscannable ecosystem degrades rather than reading clean. SCORED, not informational.
Other · Architecture — How the codebase splits by code ROLE — domain, application, infrastructure, test, generated. The significance map behind the knowledge/coupling weighting, and a DDD signal in its own right: a thin domain core under fat infrastructure is the anemic-domain smell, quantified. How each file's role is decided, because the split is only as good as that: a generated name or a build-output tree makes it Generated, a test project makes it Test, and otherwise the file's NAMESPACE and PATH words are matched against fixed vocabularies in a fixed ORDER — domain, then infrastructure, then application — so a file whose words hit two layers is counted under the earlier one. A production file matching none of them counts as application, so that share reads 'application or unclassified' rather than a measured application layer. Roles come from naming convention, never from what the code does. On this repository the split was taken from the source tree on disk rather than from a loaded .NET workspace, so a file's role is decided by its PATH segments alone — no declared namespace was available to add to the evidence — and generated output is excluded from the census entirely rather than counted as a generated share.
Method: Roslyn line-count by code ROLE: every source file classified Domain/Application/Infrastructure/Test/Generated by namespace + path convention (the shared CodeRoleClassifier), then significant lines summed per role. Deterministic; the advisory score is the business-logic (domain+application) share of production code.
Coverage: Population: ALL source files, each bucketed into ONE of five roles (Domain/Application/Infrastructure/Test/Generated) by namespace + path convention — a file whose layer isn't named in the convention falls to Application (the neutral default), and the split is line-count, not semantic depth or business value.
What to do
The domain core is a small share of production code, but most of the rest matched no layer vocabulary at all — so this is not yet an anemic-domain finding. The namespace/path convention could not place that code, which makes the composition above a statement about the naming, not about the design. Name the layers (or check that the repository's conventions differ from the ones this check knows) before reading a thin domain into it.
Other · Architecture — Whether the project-reference graph is acyclic (cycles block independent build/deploy and signal eroding boundaries).
Method: Project reference cycles via elementary-DFS over real .csproj references, using the engine shared with D5/D7; cyclic versus acyclic. Exhaustive, deterministic.
Other · Architecture — Whether dependencies point inward (Domain ← Application ← Infrastructure/Web) — the clean-architecture dependency rule, checked across the project graph.
Method: Layer violations by name-segment inference (Domain/Core to Application to Infrastructure/Web) over the project-reference graph. Exhaustive over all projects, deterministic.
Do you agree with this assessment?
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 repo and its projects have a README, and whether it's substantive and current.
Method: Filesystem scan: README presence, word count, and headings for depth; git history for staleness. Exhaustive across root and project dirs, deterministic.
What to do
Add a README to the 2 of 4 project(s) that lack one — worth up to 1 pts.
Maturity · Maturity — Whether key decisions (ADRs) and the high-level shape (C4/diagrams) are written down.
Method: Filesystem scan: ADR folder/naming conventions or content, plus Mermaid/PlantUML/C4/architecture.md discovery. Exhaustive, deterministic.
No Architecture Decision Records found — no conventional ADR directory, no numbered `NNNN-title` documents in any markup this check reads, and nothing ADR-shaped by content. Design rationale recorded elsewhere (a design-notes tree, a mailing list, pull-request discussion) is not visible to this check and is not re-findable per decision, so a future maintainer cannot ask why one choice was made and get an answer.
What to do
Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them.
Maturity · Maturity — Whether the README actually describes the code that exists (LLM-judged, advisory).
Method: Judged by language model at low temperature: README accuracy versus actual projects, within a disclosed tolerance. Advisory, not a measured number.
Only 1/2 runnable modules use logging (modules with no entry point or server are excluded — they are libraries a runnable module hosts). Silent: `Renderer/Stdout`.
What to do
Extend structured logging to the remaining runnable modules so everything you run is diagnosable in production.
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 117208 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:22
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.
What to do
Make sure a person approves each release. The release job names an environment, but its approval rules live in the code host's settings, where Watchdog can't see them. Check that a reviewer must approve each release, or publish releases as drafts first, so a bad build can be stopped before anyone downloads it.
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 the code is written to minimise allocations so it doesn't pressure its host's memory manager — buffer/slice views over copies, object pooling, stack or value-type allocation, and buffer writers. Reward-only: credited where present, never penalised where a simpler style is fine.
Method: Production-source scan: density (per 1k LoC) of allocation-aware APIs — in .NET Span/Memory, ArrayPool/ObjectPool, stackalloc, ValueTask, value-type structs, IBufferWriter, string.Create, SkipLocalsInit; off .NET, with comments and strings blanked, Go's sync.Pool, preallocated slices/maps, Grow, strconv.Append* and buf[:0] reuse; the JVM's NIO buffer views, MemorySegment, primitive collections, pools and literal presizes (plus Kotlin primitive arrays and value classes, Scala AnyVal and @specialized); Swift's reserveCapacity, ContiguousArray, withUnsafe* access and ~Copyable. Activated off .NET on the same floor (400 lines, and benchmarks or 8 uses); Rust and garbage-collected scripting languages are not applicable. Reward-only. Deterministic, syntax/text detection.
What to do
Raise allocation-aware density on the hot paths — currently 63 use(s) across 229,450 production line(s) (~0.3/1k). More of the idioms below on the allocation-heavy paths climbs this toward 10.
Swift: on hot paths, reserveCapacity before appending, use ContiguousArray for class-element arrays, work in place with withUnsafeBufferPointer/withUnsafeTemporaryAllocation, and make large values ~Copyable with borrowing/consuming parameters.
Readiness · Performance — Whether asynchronous code stays responsive — it avoids sync-over-async blocking (a .NET .Wait()/.GetAwaiter().GetResult(), a time.sleep or blocking HTTP call inside a Python coroutine, a *Sync call inside an async JavaScript function, block_on inside a Rust async fn, runBlocking inside a Kotlin suspend function, block() inside a Reactor publisher) that stalls a thread or event loop and risks deadlock, and, where the code is a reusable library on .NET, awaits with ConfigureAwait(false) so it never captures and stalls its caller's context.
Method: Production-source scan: sync-over-async blocking counted everywhere — .Wait()/.GetAwaiter().GetResult() in .NET; off .NET, read from the language model, a blocking call inside an async function (Python, TS/JS, Rust, Kotlin, Swift, Dart) or inside a Java method returning a Reactor Mono/Flux or a Scala method returning a Future or effect — and, for a .NET library with ≥5 awaits, the share of awaits using ConfigureAwait(false). Deterministic, syntax/text detection.
Do you agree with this assessment?
R1 · Type Safety0.0 / 10Critical✓ Tool-verified
React / JS · Code Health — How much of the frontend is typed TypeScript vs untyped JavaScript.
Method: Frontend file inventory: the share of typed TypeScript vs untyped JavaScript across the source tree. Deterministic, exhaustive over frontend files.
0 typed · 13 plain JS — the untyped files are Scripts/CI/Tests/availability-interface-tests.js, Scripts/CI/Tests/binary-interface-tests.js, Scripts/CI/Tests/binary-package-tests.js, Scripts/CI/Tests/binary-version-tests.js, Scripts/CI/Tests/framework-dependency-tests.js, Scripts/CI/Tests/interaction-test-action-tests.mjs (+7 more).
What to do
Adopt TypeScript for the frontend: add a typecheck step to the build, then either type-check the existing JavaScript in place (`checkJs`/JSDoc types) or convert the highest-traffic modules first — no file is typed today, so this is an adoption, not a clean-up.
React / JS · Code Health — Near-exact copy-pasted blocks of substantial extent across the frontend (the D4 clone algorithm over JS/TS tokens, D-386): a block is reported only where its copies still agree on most of their own identifiers and literals, or were renamed as they were pasted but kept most of their constants, and where the copies carry enough code to stand on their own or the copied extent reaches 30 lines — so a re-implementation sharing neither names nor values, and a small pasted declaration, are both found and deliberately not reported, and a clean R10 is not a claim that nothing was copied.
Method: Near-exact copy-pasted blocks of substantial extent across the frontend (the D4 clone algorithm run over JS/TS tokens). Masking finds the candidates; a block is reported when its copies still agree on most of their own identifiers and literals, or when a renamed copy still agrees on most of its constants, AND the copies carry enough code to stand on their own — or when the copied extent reaches 30 lines. So a re-implementation sharing neither names nor values, and a small pasted declaration, are deliberately not counted. Deterministic.
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.
runTests has cyclomatic complexity 41 and cognitive complexity 54; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — Scripts/CI/Tests/interaction-test-action-tests.mjs:226
nonCodeEnd has cyclomatic complexity 20 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/normalize_swiftinterface.js:37
snapshotRequest has cyclomatic complexity 14 and cognitive complexity 13; 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. — Scripts/CI/Tests/optional-ci-tests.mjs:400
(anonymous) has cyclomatic complexity 12 and cognitive complexity 25; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — Scripts/CI/Tests/optional-ci-tests.mjs:511
request has cyclomatic complexity 12 and cognitive complexity 11; 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. — Scripts/CI/Tests/optional-ci-tests.mjs:52
What to do
Break down the listed branch-heavy functions; aim P95 cyclomatic ≤ 5.
Do you agree with this assessment?
R3 · Large Files10.0 / 10Exemplary✓ 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.
Do you agree with this assessment?
R4 · Test Coverage10.0 / 10Exemplary✓ Tool-verified
React / JS · Readiness — Static test reachability (D-386): the share of production files reachable from any test via the import graph — measured without running anything.
Method: Static test reachability: the share of production files reachable from any test via the import graph — measured without running anything. Deterministic.
Do you agree with this assessment?
R7 · Dead Code10.0 / 10Exemplary✓ Tool-verified
React / JS · Code Health — Files unreachable from every application/tooling/test entry point, and exports nothing imports (module-graph reachability, D-386).
Method: Dead code: files unreachable from every application/tooling/test entry point plus exports nothing imports, via module-graph reachability. Deterministic, exhaustive over the import graph.
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 · Code Health — Whether the code avoids sync-over-async (deadlock-prone blocking on tasks) and async void.
Method: Roslyn syntax scan: async methods scanned for .Wait()/.GetAwaiter().GetResult() and async-void outside event handlers. Deterministic, hard fact per invocation.
Other · Code Health — Whether any branch is dead by construction — a switch arm whose label can never equal a case-normalised subject, or an `else if` whose predicate the arm above has already swallowed.
Method: Roslyn syntax + semantics: switch labels compared against the subject's own case normaliser, and if/else-if chains checked for a literal an earlier arm's containment test already swallows. Deterministic, provable per finding. Advisory.
Do you agree with this assessment?
X13 · Undrained process stream10.0 / 10Exemplary○ Nothing flagged
Other · Code Health — Whether a child process that has BOTH standard streams redirected drains both — reading one to the end while the other is never read deadlocks once the child fills the unread pipe.
Method: Roslyn syntax + semantics: ProcessStartInfo launches with both streams redirected, checked for a drain of each stream across the enclosing type. On a repository with no .NET source it reads JavaScript/TypeScript off the engine’s own token stream (test, vendored and minified paths not) with the same rule: a `spawn` imported from `child_process` whose stdout and stderr are both pipes (no options, no `stdio`, or `stdio` of `'pipe'`), bound to a local that never leaves its scope, where exactly one of the two streams is read, the other never, and the child’s `close`/`exit` (or the read stream’s end) is awaited; a shell redirect in the call’s arguments or a `kill` of the child suppresses it. The same rule reads Python’s `subprocess.Popen`, Dart’s `Process.start`, Ruby’s `Open3.popen3`, and Scala’s JDK process starts (`new ProcessBuilder(…).start()` with no `redirectErrorStream`/`redirectError`/`redirectOutput`/`inheritIO`, `Runtime.getRuntime.exec`) where one of `getInputStream`/`getErrorStream` is read and the other never while `waitFor()` is called or the read stream is read to its end. Deterministic, provable per finding. Advisory.
Other · Security — Whether a hand-rolled public/private IP check can be walked past — a method that unwraps IPv4-mapped IPv6 but returns the opposite verdict for the same host written as IPv4-compatible, 6to4 or NAT64.
Method: Roslyn syntax + semantics: methods that unwrap IPv4-mapped IPv6 and hand-roll IPv4 range carve-outs, checked for whether the IPv6 branch also accounts for the IPv4-compatible, 6to4 and NAT64 embeddings. Deterministic, provable per finding. Advisory.
Do you agree with this assessment?
X15 · Unvalidated length from an untrusted reader10.0 / 10Exemplary○ Nothing flagged
Other · Security — Whether a length read out of the stream being parsed is bounded before it is allocated or read — an unchecked count taken from the input lets the input choose the allocation.
Method: Roslyn syntax + semantics: integer lengths read from a BinaryReader and spent on a bulk read or an array allocation, checked for any comparison or bounding call on the value anywhere in the method. Deterministic, provable per finding. Advisory.
Other · Code Health — Whether a loop that shortens a string until it fits a length budget has a floor — one with none grinds the value down to the empty string, or past it into a negative-length `Substring`.
Method: Roslyn syntax + semantics: while/do loops whose body's only effect on a string is to drop its last character, checked for whether anything — a direct comparison on the length, a body guard, a break — bounds that length below. On a repository with no .NET source it reads JavaScript/TypeScript off the engine’s own token stream (test, vendored and minified paths not) with the same rule: a `while`/`do` loop whose body’s one assignment to a value is `x = x.slice(0, -1)` or `x = x.slice|substring|substr(0, x.length - 1)`, driven by a condition that reads `x.length` only as a term of a larger expression — never compared directly, never tested for truthiness, and with no other read of `x` — and whose body has no `break`, `return`, `throw` or `if` naming `x`. Deterministic, provable per finding. Advisory.
Do you agree with this assessment?
X17 · Uncapped recursion over a caller-supplied document10.0 / 10Exemplary○ Nothing flagged
Other · Security — Whether a walk that recurses through a JSON/XML tree handed in by its caller bounds how deep it will go — an uncapped walk lets the document's nesting choose the stack depth, and the resulting StackOverflowException cannot be caught.
Method: Roslyn syntax + semantics: methods that take a JSON/XML document node and call themselves with a child of it, reachable from an externally-callable member of the same type that accepts a document, checked for any depth parameter, descent counter or threaded arithmetic anywhere in the walk. On a repository with no .NET source it reads TypeScript off the engine’s own token stream (test, vendored, generated and minified paths and `.d.ts` not) with the same rule: a function or method with a parameter typed as a document value — `unknown`, `any`, `object`, `Record<string, unknown|any>`, a JSON alias (`JsonValue`, `JSONObject`, …) or a DOM node global the file does not rebind — that calls itself (bare, or through `this` for a method, or hands itself to a call over the value as in `value.map(walk)`) with something it took out of that value and never through an ancestor accessor such as `closest()` or `parentElement`, that is exported or reached from an exported function (a public method of the same exported class) taking such a value, and that names no depth, level, nesting, recursion, remaining or budget anywhere and threads no `+`/`-` arithmetic through a self-call. Plain JavaScript is not read: with no annotation nothing tells a parsed document from a tree the code built itself. Deterministic, provable per finding. Advisory.
Other · Code Health — Whether a type's disposal matches what it OWNS — releasing what it created, leaving alone what it was handed, and not declaring a finalizer for state that has nothing unmanaged to finalize.
Method: Roslyn syntax + semantics: every assignment to a disposable field is read to decide whether the type CREATED the value or was handed it, and the type's disposal is checked against that answer — an injected interface it disposes, a value it constructed and never releases, a finalizer on a type holding nothing unmanaged, and a disposable local whose every reference is a plain member read. A value handed to a container that disposes its contents (a parent control's `Controls` collection, a component `IContainer`) is released by that container and is not reported; generated code is out of population. On a repository with no .NET source the same ownership questions are read in JavaScript/TypeScript off the engine’s own token stream (test, vendored, generated and minified paths not): a class declaring `dispose()`, `[Symbol.dispose]()` or `[Symbol.asyncDispose]()` that disposes a field it was handed through a constructor parameter typed as a repository interface or resolved by a dependency-injection container; that assigns a field only ever from `new X(…)` of a disposable class and neither releases it anywhere in the class nor names it in its disposal member or a method that member calls, nor hands it to anything else; and a `const`/`let` local built from literals only whose every reference opens a statement operating on a non-release member of it. A class is disposable when every repository declaration of its name declares or inherits a disposal member, or when it is a documented library disposable (`vscode` EventEmitter, CancellationTokenSource and Disposable; three.js geometries, materials, textures, render targets, renderers, controls and composers). The finalizer arm has no JavaScript counterpart: a class cannot declare one. Dart is read for the owned-and-never-released arm: a Flutter `State` (or a class declaring `dispose()`/`close()`) whose library-private field is written only with direct creations of a framework controller, `FocusNode`, `StreamController` or periodic `Timer` (or a `.listen(…)` into a field declared `StreamSubscription`), which nothing in the class or its library releases (`dispose`/`close`/`cancel`) and which is never handed on except as a named argument. Ruby is read for the owned-and-never-released arm and the abandoned-local arm: a class declaring an instance `close`, `dispose`, `shutdown`, `stop`, `disconnect` or `terminate` whose instance variable is written only with a blockless core descriptor creation (`File.open`/`new`, `Tempfile`, `Dir.open`, `IO.popen`, the `socket` and `openssl` socket classes) that no method of the class closes and that is never handed on (passed, returned, stored, exposed by `attr_reader`, delegated) — a class whose superclass or mixin lies outside the repository is not judged — and a blockless creation read through and dropped (`File.open(path).read`) or held in a local that is never closed, returned, passed or stored (a `&:read` block-pass, an `autoclose: false` borrow and a `fileno` hand-over are not abandonment). PHP is read for the same two arms: a class (not a trait, and not one using a trait) declaring an instance `close`, `dispose`, `shutdown`, `stop`, `disconnect` or `terminate` whose `private` property (or a `final` class's `protected` one) is written only with a direct core `fopen`, `tmpfile`, `popen`, `proc_open`, `fsockopen`, `stream_socket_client`/`server` or `opendir` that nothing in the class closes (`fclose`, `pclose`, `closedir`, `unset`, a reset to `null`) and that is never handed on, and a handle held in a function's local, or read through as the argument of a reader, that is never closed, returned, passed, captured or stored; a `php://` stream, `curl_init`, `SplFileObject`, `PDO` and a function the repository declares under the core name are not read. Deterministic, provable per finding. Advisory.
Other · Code Health — Whether a method that temporarily changes state belonging to the whole process — the working directory, an environment variable — puts it back on EVERY path: a restore reached only when nothing throws leaks the change to the rest of the process.
Method: Roslyn syntax + semantics: method bodies that write the process working directory or an environment variable and write it back in the same body, checked for whether that restore sits in a `finally`/`catch` or only on the straight-line path. On a repository with no .NET source the same rule reads production JavaScript/TypeScript off the engine’s own token stream (test, vendored and minified paths not): `process.chdir`, `process.env.NAME =`/`["NAME"] =` and `delete process.env.NAME`, and Deno’s `Deno.chdir`/`Deno.env.set`/`Deno.env.delete`, paired per function body (a nested function or arrow is its own body, and module top-level code is none), where the last write puts back a local the body captured from the same global or deletes a variable the first write set, with at least one statement between them; a write in a `catch`/`finally` of that body silences it. Deterministic, provable per finding. Advisory.
Other · Code Health — Whether a `when` guard is free of side effects — a guard that increments a counter or assigns while deciding whether its arm matches applies that change during PATTERN MATCHING, on an arm that may not be selected, and skips it entirely when a short-circuit to its left answers first.
Method: Roslyn syntax: `when` guards on case labels and switch-expression arms, read for a mutation (`++`/`--`/assignment) sitting in a position the guard's own `&&`/`||`/`??`/`?:`/`?.` can skip. Deterministic, provable per finding. Advisory.
Other · Code Health — Whether a method that TAKES a lock or semaphore and gives it back from a flag-guarded `finally` returns the value that flag implies — reporting success while the guard hands the primitive back admits a second caller the exclusion was there to keep out, and reporting failure while the guard keeps it leaves nothing to ever give it back.
Method: Roslyn syntax: `try` statements whose `finally` releases a synchronisation primitive under a bare local-bool guard, where the method also TOOK that same primitive before the `try`, checked for a `return` of a bool literal whose value disagrees with the flag state the method's own straight-line assignments put it in. Deterministic, provable per finding. Advisory.
Other · Code Health — Whether the work a diagnostic log line costs is paid only when that line is wanted — C# evaluates a call's arguments BEFORE the call, so a trace/debug message joined or projected out of a collection is built in full on every pass, and then discarded by a sink the shipped configuration leaves switched off.
Method: Roslyn syntax: log calls at a diagnostic level (a `Log`-prefixed method naming Trace/Debug/Verbose, or a bare `Debug`/`Trace`/`Verbose` on a receiver named for a logger), whose argument list is read for a call whose cost scales with a sequence — a LINQ operator, a materialisation, `string.Join`, a serializer — with no enclosing level check or conditional-compilation region. On a repository with no .NET source it reads JavaScript/TypeScript off the engine’s own token stream (test, vendored and minified paths not) with the same rule: a `debug`/`trace`/`verbose` call on a receiver named for a logger, or a `log`-prefixed method naming the level, whose argument calls an array operator (`map`/`filter`/`reduce`/`sort`/…), `Array.from`, `Object.keys/values/entries`, `JSON.stringify`/`util.inspect` over anything but a literal, or an array `join` — outside any arrow or function passed as an argument, which the logger calls only when the level is on — with no enclosing `if`, `&&` or `?:` whose condition names a level, a level string, or the `NODE_ENV`/`__DEV__`/`DEV` build switch. Deterministic, provable per finding. Advisory.
Do you agree with this assessment?
X24 · Document value interpolated into markup unescaped10.0 / 10Exemplary○ Nothing flagged
Other · Security — Whether text read out of the document being converted is escaped before it is written into generated markup — a value the document's author chose, interpolated into an attribute the surrounding literal delimits, can close that attribute and open another.
Method: Roslyn semantic model over the whole compilation: a string-typed `Value`/`InnerText`/`InnerXml`/`Text` member declared inside `DocumentFormat.OpenXml` or `System.Xml` is a taint SOURCE, propagated through assignments, returns, arguments, tuple elements and string composition to its transitive closure, then read at interpolated-string holes that sit in a markup position the surrounding literal itself delimits. Escaper/encoder calls and enclosing validator conditions cut the flow. Flow- and container-insensitive by construction. A second arm needs no provenance at all and reports a type that CONTRADICTS ITSELF — the same expression escaped at one delimited markup hole and interpolated raw at another hole in the same markup position of the same type, which the type's own escaping proves is a defect without knowing where the value came from. On a repository with no .NET source it reads JavaScript/TypeScript off the token stream with the same rule: a DOM read of raw document text (`getAttribute`, `textContent`, `innerText`, `nodeValue`) is the source, propagated through local bindings and string composition, and judged at template-literal and concatenation holes in the same two delimited markup positions; escapers and validating conditions cut it, and documentation-site, test, vendored and minified scripts are not read. Deterministic, provable per finding. Advisory.
Other · Code Health — Whether a value the caller is invited to supply is the value the type actually uses — a constructor parameter stored in a private field that nothing ever reads while the default it was given is spelled out a second time at the site that should have read it, a keyed lookup that falls back to a different setting than the one its key names while the same type falls back to the matching one for that same key, or a culture-sensitive parse given no format provider by a type that feeds its own settable culture to the same kind of parse elsewhere, or a number an entry point writes to standard output under the host's culture while the same entry point formats with the invariant culture elsewhere. Either way, every caller who supplies a value silently gets something else.
Method: Roslyn syntax: private instance fields of a non-partial type assigned in a constructor from one of its own parameters with a `??` fallback, checked for whether anything in the type body reads the field and whether that same fallback expression is spelled out again outside the constructor; and `??` fallbacks onto a member access from a lookup call carrying exactly one string literal, grouped by that key across the type and checked for a fallback member whose folded name disagrees with the key while a sibling site for the same key agrees with it. On a repository with no .NET source the first two arms read JavaScript/TypeScript off the engine’s own token stream (tests included, bundles and vendored paths not): a `#x`, `private` or `private` parameter-property instance field filled in the constructor from a parameter (or one member of one) through `??`/`||` or a parameter default, never read anywhere in the file by name, whose constructed default is spelled again in the class body; and `lookup("key") ?? s.member` grouped by key per class, or per module outside every class. The culture arm has no JavaScript counterpart: its parses take no locale. Deterministic, provable per finding. Advisory.
Other · Code Health — Whether a value handed from a callback to the body that waits on it crosses on something built to be crossed — a `Queue<T>`/`List<T>`/`Dictionary<K,V>` written inside an event handler and read back outside it is mutated by two flows at once, and the semaphore or completion source beside it orders how MANY items exist while leaving the collection's own head, tail and backing array unprotected.
Method: Roslyn syntax: method, accessor, local-function and lambda bodies that declare BOTH a non-thread-safe generic collection (`Queue`/`Stack`/`List`/`Dictionary`/`HashSet`/`Sorted*`/`LinkedList`) and a synchronisation primitive (`SemaphoreSlim`/`TaskCompletionSource`/`ManualResetEvent(Slim)`/`AutoResetEvent`/`CountdownEvent`) as locals, then read for a `+=`-registered lambda that raises that primitive while the body outside every lambda waits on it — and, in that scope, a mutating call on the collection inside the lambda paired with a mention of it outside. Any `lock` in the scope abstains it. On a repository with no .NET source the same handoff is read in Java off the engine’s own token stream (test source sets, vendored and demonstration paths not): an `ArrayList`/`LinkedList`/`ArrayDeque`/`PriorityQueue`/`Hash*`/`LinkedHash*`/`Tree*` local and a `CountDownLatch`/`Semaphore`/`CompletableFuture` local, a lambda or anonymous class that raises the primitive and mutates the collection, and a wait outside it; any `synchronized` or `lock()` abstains the body. Because each of those primitives orders what the callback wrote before raising it, only a touch that provably overlaps the callback is convicted: one after the registration and before the next wait, or one in a loop registered-before, waiting on every pass and not declaring the collection. Deterministic, provable per finding. Advisory.
Do you agree with this assessment?
X27 · Collection changed while being enumerated10.0 / 10Exemplary○ Nothing flagged
Other · Code Health — Whether a `for` loop leaves the `dict`, `set` or `deque` it is walking alone — CPython's iterators over those check that the collection has not changed size since the loop began, so a body that removes from (or empties) the very collection the loop is walking makes the next step raise `RuntimeError: dictionary changed size during iteration` and the remaining items are never seen.
Method: Roslyn syntax + semantics: `foreach` statements whose body calls a structural mutator (`Add`/`Remove`/`Clear`/`Insert`/…) on the very expression the loop is enumerating. Two arms. ARM A — the source is a concrete fragile BCL collection, or a live `Keys`/`Values` view over one, and the mutator resolves to that same collection's own member; concurrent and immutable collections and arrays are outside the population by construction, since their enumerators survive a structural change. ARM B — the source is an argument-less accessor CALL on a receiver whose body is in source: the accessor must return a stored field VERBATIM and a sibling member must structurally change that same field, both read off the implementations rather than from the members' names. A mutation the loop provably exits immediately after (`break`/`return`/`throw`/`goto`), or one written inside a nested loop or a lambda, is counted and never reported. Deterministic, provable per finding. Advisory.
Do you agree with this assessment?
X28 · Index access outside its own emptiness guard10.0 / 10Exemplary○ Nothing flagged
Other · Code Health — Whether a condition that tests a value for emptiness indexes that same value only where the test holds — an `||` written one parenthesis too far to the left leaves an index access outside the guard beside it, so the empty case the guard exists to anticipate reaches the index and throws.
Method: Roslyn syntax only, no semantic model: the OUTERMOST `&&`/`||` of every boolean condition, read for a symbol the condition tests for emptiness (`string.IsNullOrEmpty`/`IsNullOrWhiteSpace`, a `Length`/`Count` comparison against a literal, `Any()`, a `Length`/`Count` pattern, or a comparison against `""`) and ALSO indexes. Each `symbol[...]` access is placed by a boolean-reachability walk from the access up to the outermost connective: an access is COVERED when some enclosing step has it in the right operand and the left operand, under the truth value that step forces, proves the symbol non-empty — a recursion over `&&`/`||` whose true- and false-directions are asymmetric. A finding needs BOTH an uncovered access and a covered one on the same symbol in the same condition, which is the agreeing twin that separates a misplaced parenthesis from an unrelated length test. Bare index accesses with no emptiness test in the condition are neither counted nor reported; a non-identifier receiver and a lambda nested inside the condition are outside the population. Deterministic, provable per finding. Advisory.
Do you agree with this assessment?
X29 · Per-element action decided by a fixed element10.0 / 10Exemplary○ Nothing flagged
Other · Code Health — Whether a decision taken once per element is taken ABOUT that element — a test inside a counted loop that reads a fixed subscript of the very collection its guarded statement indexes by the loop variable applies element zero's answer to all of them, so the elements that differ from it are all handled wrongly, and in the same direction.
Method: Roslyn syntax only, no semantic model: every `for` statement declaring exactly ONE loop variable, and every `if` inside its body that is not under a nested loop or a lambda. A site enters the population when the `if`’s condition never mentions the loop variable while the statement it guards indexes some collection by that variable ALONE (`c[i]`; `c[i + 1]` and `c[i, j]` are outside it). A finding additionally needs the AGREEING TWIN at the same-collection grain: the condition must read THAT SAME collection at a subscript that does not move — written into the condition, or reached through a local declared BEFORE the loop, so an alias bound inside the body is not followed. Both collection expressions must be simple identifiers. On a repository with no .NET source the same rule reads JavaScript/TypeScript off the engine’s own token stream (tests included, bundles and vendored paths not): a `for (let|var|const x = …; …; …)` with one declarator and a braced body, an alias followed only when it is declared before the loop in a block that encloses it and never assigned inside the loop. Deterministic, provable per finding. Advisory.
Other · Code Health — Whether exceptions are handled rather than silently swallowed or rethrown with lost stack traces.
Method: Roslyn syntax scan: every catch clause counted; empty catches and bare rethrows flagged. Population is all catch clauses, not estimated. Deterministic, hard fact.
Do you agree with this assessment?
X30 · Support guard that admits what it rejects10.0 / 10Exemplary○ Nothing flagged
Other · Code Health — Whether a guard written as a NEGATED `||` says what its author meant — `!(a || b || x != k)` is `!a && !b && x == k` by De Morgan, so a bail-out that mixes capabilities the code needs with a fault it refuses turns inside out: it fires only where the capabilities are ABSENT, and lets every value the fault term names walk straight into the body that cannot handle it.
Method: Roslyn syntax only, no semantic model: every logical-not whose operand is a parenthesised `||` chain of two or more disjuncts, flattened (a left-nested `a || b || c` read once would see `(a || b)` as one disjunct). A site enters the population on that shape alone. A finding additionally needs the disjuncts to DISAGREE in polarity: at least one bare boolean read — an identifier or member access, never an invocation, which is a predicate rather than a capability flag — and at least one `x != <constant>`, the only form that negates into an exact-value pin (`== null` negates into a looser requirement and is outside the fault set). Consistently-polarised disjunctions, all-fault or all-capability, are counted and never reported; a negated `&&` is outside the population entirely. No same-receiver gate: it was measured to cost a real defect and remove no false positive. Deterministic, provable per finding. Advisory.
Do you agree with this assessment?
Reference — by lens
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 — 1 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 — 16 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
Not evidenced — 2 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.
P5 DR & Backup — not evidenced — repo shows no backup/RTO/RPO controls; absence of evidence is not evidence of a working control
Not included — 60 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 web markup found — accessibility is not applicable to this repository.
AC2 Forms & labels — No web markup found — accessibility is not applicable to this repository.
AC3 Page structure — No web markup found — accessibility is not applicable to this repository.
AC4 Keyboard semantics — No web markup found — accessibility is not applicable to this repository.
AC5 ARIA correctness — No web markup found — accessibility is not applicable to this repository.
AC6 Visual & motion safety — No web markup found — accessibility is not applicable to this repository.
AC7 A11y enforcement — No web markup found — accessibility is not applicable to this repository.
AX1 Captive dependencies — Not applicable: this repository's Swift imports no dependency-injection container and defines no container of its own — nothing that both registers and resolves bindings, and nothing that names two lifetimes — so nothing holds one lifetime's instance while handing out another's.
AX2 Stateful singletons — No container singleton was found, so there is no shared instance for concurrent requests to race on. No 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 — not assessed — interface segregation is computed over a type surface that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
AX7 Slice cohesion — not applicable — not a vertical-slice architecture
AXB1 Runtime evidence locked — no reproducible boot — This repository has nothing the runtime tiers could boot or serve — no markup, no UI framework or web-server dependency, no UI component source, no native UI project and no API definition — nothing here is a surface to boot — so runtime a11y/egress/header evidence has no subject here. Not applicable: this is neither a gap in the scan nor a finding about your code.
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.
C4 Data Retention — No personal data detected in a persisted data model — no PII-named property (email, firstName, dateOfBirth, phoneNumber, …) or stored credential on a SwiftData @Model, a Core Data, Realm, GRDB or Fluent type, a GRDB or SQLite.swift column, or in a SQL CREATE TABLE or ALTER TABLE — and no database or data-store client (CoreData, SwiftData, GRDB, RealmSwift, SQLite, Firebase, …) imported either, so this repository keeps no personal data whose lifetime a retention limit would bound.
C5 Data-Subject Rights — No personal data detected in a persisted data model — no PII-named property (email, firstName, dateOfBirth, phoneNumber, …) or stored credential on a SwiftData @Model, a Core Data, Realm, GRDB or Fluent type, a GRDB or SQLite.swift column, or in a SQL CREATE TABLE or ALTER TABLE — and no database or data-store client (CoreData, SwiftData, GRDB, RealmSwift, SQLite, Firebase, …) imported either, so this repository keeps no personal data for a data subject to erase, export or consent over.
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.
D19 Documentation Quality — No runnable or published unit to look for an example in, and no multi-project root README to look for a map in; the other documentation kinds are withheld (see the gaps), so documentation quality is not applicable here.
D21 Naming Consistency — Naming consistency is measured on C# only; JavaScript, Python, Swift not measured.
D22 Internal API Consistency — The exposed public-API surface could not be collected — no C#/VB projects loaded.
D23 Boundary Type-Coupling — No bounded-context organisation was detected either — neither a context-shaped layout, nor 2+ sibling source directories each declaring an aggregate root, nor 2+ 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# and Visual Basic comments only — this repository's production source is .py, .rb, .swift, which was left unread. Not scored: this is a gap in the analyzer, not a verdict about this repository.
D25 ADR Conformance — no ADRs to check
D27 Navigability — D27 counts a call into the standard library or a dependency as unresolved for this repository's language (.swift), so too few call sites counted as resolved to assess navigability. Not scored: this is a gap in the analyzer, not a verdict about this repository.
D31 IaC & Container Security — No Infrastructure-as-Code or container manifests found (Dockerfile, Docker Compose, Terraform, Kubernetes/Helm, CloudFormation, ARM, Bicep, Ansible); nothing to scan.
D32 Data Compliance (PII/GDPR) — 698 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.
D39 IL Efficiency — D39 measures the IL emitted by a .NET build; this repository has no .NET solution or project files, so the dimension does not apply.
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 none of the 3 signals this lens looks for
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 — this card publishes what the CI gate does with the test inventory rather than grading it. The findings above are its output.
P7 Outbound HTTP resilience — not applicable — no HTTP server, API framework or worker entry point was found in the JavaScript/TypeScript, Python, 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 — no coverage report found on disk — produce a coverage report in a standard format (lcov — `swift test --enable-code-coverage` (SwiftPM) or `xcodebuild test -scheme <YourScheme> -enableCodeCoverage YES` (an .xcodeproj/.xcworkspace suite), then `xcrun llvm-cov export -format=lcov`) and commit it — a hosted scan measures a clone of the repository, so a report that exists only in a working tree, a CI runner's or your own, never reaches it; the artefact is commonly gitignored, so `git add -f` that one file (or un-ignore its path) and commit it alongside the code it measures, or wire coverage collection into CI, to enable this cross-layer check
R11 Import Boundaries — No recognizable feature-sliced/layered src layout — boundary rules not applicable.
R5 Dependency Freshness — no package-lock.json — dependency freshness not measured (would require an npm lockfile); JS/npm CVEs are scored in D30 (Dependency Vulnerabilities), which answers every ecosystem
R6 Tooling — no package.json in the repository — test/lint/typecheck wiring is read from package.json scripts (corroborated against CI), so this project's own toolchain isn't measured here
R8 Dependency Hygiene — Not measured — no package.json declares any dependency, so there is nothing to check imports against (imports may resolve through a host runtime rather than node).
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.
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.
X32 Type resolved by simple name across every loaded assembly — This check is about how a .NET program searches the assemblies loaded into its process for a type, and this repository contains no .NET source, so there is nothing here for it to assess. Not a gap in the analyzer and not a finding about your code.
X4 Structured logging — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
X5 Nullable reference types — not 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.
X7 Silent fallback defaults — 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.
D10 · Test Quality· No assertions (empty test) · ×1
No assertions (empty test): example Tests/OpenSwiftUICoreTests/Data/DynamicProperty/DynamicPropertyTests.swift:9— Test method has an empty body — it asserts nothing and exercises no code.
TodoComment Package.swift:308— // TODO: Add visionOS support — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment Tests/OpenSwiftUISymbolDualTests/Render/DisplayList/DisplayListPrinterDualTests.swift:536— // TODO: Use a real non nil shader case here after we implement ORBShader — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment Sources/OpenSwiftUICore/View/Text/Text/Text+Renderer.swift:16— // TODO: TextRenderer — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment Sources/OpenSwiftUICore/View/Text/Text/Text+Renderer.swift:35— // TODO: View + textRenderer — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment Sources/OpenSwiftUICore/View/Text/Text/Text+Renderer.swift:141— // TODO: _TextRendererViewModifier — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment Sources/OpenSwiftUICore/View/Text/Text/Text+Renderer.swift:478— // TODO: AnyTextLayoutRenderer — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment Sources/OpenSwiftUICore/View/Text/Text/Text+Renderer.swift:540— // TODO: GraphicsContext + draw for Text.Layout — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment Sources/OpenSwiftUICore/View/Text/Text/Text+Renderer.swift:542— // TODO: Text.Layout + foregroundColor — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment Sources/OpenSwiftUICore/View/Text/Text/Text+StringDrawingContext.swift:557— // TODO: CoreGraphicsContext.current + RB with cgStyleHandler — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment Sources/OpenSwiftUICore/View/Text/Text/Text+Suffix.swift:54— // TODO: ResolvedStyledText is not implemented yet — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment Sources/OpenSwiftUICore/View/Text/Text/Text+Suffix.swift:110— // TODO: helper — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment Sources/OpenSwiftUICore/View/Text/Text/Text+View.swift:304— // TODO: ContentTransition — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment Sources/OpenSwiftUICore/View/Text/Text/Text+View.swift:319— // TODO: outputs.applyInterpolatorGroup — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment Sources/OpenSwiftUICore/View/Text/Text/Text+View.swift:334— // TODO: Text.Layout.Key — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment Sources/OpenSwiftUICore/View/Text/Text/Text+View.swift:523— // MARK: - TextLayoutProperties + ProtobufMessage [TODO] — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment Sources/OpenSwiftUICore/View/Text/Text/Text+View.swift:900— // TODO: RB — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment Sources/OpenSwiftUICore/Render/PlatformViewFactory.swift:265— // TODO: RB — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment Sources/OpenSwiftUICore/Render/PlatformViewFactory.swift:288— // TODO: RB — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment Sources/OpenSwiftUICore/Render/PlatformViewFactory.swift:316— // TODO: RB — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment Sources/OpenSwiftUICore/View/Text/FormatStyle/SystemFormatStyle+Timer.swift:236— // TODO: Use the decoded attributes once swift-foundation supports bridging NSAttributedString attributes to AttributeContainer. — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment Sources/OpenSwiftUICore/View/Text/Font/ModifiedFont.swift:214— // TODO: Use a FourCC macro for these raw values. — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment Sources/OpenSwiftUICore/View/Text/AttributedString/Text+NSAttributedString.swift:145— // TODO: append ConcreteCustomTextAttachment(LineAttachment(line:bounds:)) — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment Sources/OpenSwiftUICore/View/Scroll/ScrollPosition+Modifiers.swift:6— // Status: TODO — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment Sources/OpenSwiftUICore/View/Scroll/ScrollStateRequest.swift:6— // Status: TODO — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment Sources/OpenSwiftUI/Modifier/ViewModifier/PresentedSceneValueInputModifier.swift:6— // Status: TODO — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
No assertions: application Tests/COpenSwiftUITests/Shims/AppKitPrivateTests.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* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: testBasicAnyView Tests/OpenSwiftUICompatibilityTests/Integration/PlatformHostingControllerCompatibilityTests.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* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: testBasicAnyViewWithProperty Tests/OpenSwiftUICompatibilityTests/Integration/PlatformHostingControllerCompatibilityTests.swift:27— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: nonEquatable Tests/OpenSwiftUICompatibilityTests/View/EquatableViewCompatibilityTests.swift:88— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: equatable Tests/OpenSwiftUICompatibilityTests/View/EquatableViewCompatibilityTests.swift:100— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: equatableProxy Tests/OpenSwiftUICompatibilityTests/View/EquatableViewCompatibilityTests.swift:144— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: idAfterOnAppear Tests/OpenSwiftUICompatibilityTests/View/IDViewCompatibilityTests.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* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: idBeforeOnAppear Tests/OpenSwiftUICompatibilityTests/View/IDViewCompatibilityTests.swift:43— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: pbMessage Tests/OpenSwiftUICoreTests/Graphic/BlurStyleTests.swift:51— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: deviceConversionOut Tests/OpenSwiftUICoreTests/Graphics/GradientTests.swift:532— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: perceptualConversionOut Tests/OpenSwiftUICoreTests/Graphics/GradientTests.swift:570— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: midpointDependsOnColorSpace Tests/OpenSwiftUICoreTests/Graphics/GradientTests.swift:583— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: emptyEncodingOmitsOnlyDevice Tests/OpenSwiftUICoreTests/Graphics/GradientTests.swift:654— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: protobufEncoding Tests/OpenSwiftUICoreTests/Render/SymbolEffectTests.swift:78— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: mainActorAssumePass Tests/OpenSwiftUICoreTests/Util/MainActorUtilsTests.swift:29— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: mainActorAssumeFail Tests/OpenSwiftUICoreTests/Util/MainActorUtilsTests.swift:35— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: nonMainActorAssumeFailWithRuntimeIssue Tests/OpenSwiftUICoreTests/Util/MainActorUtilsTests.swift:50— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: mainActor Tests/OpenSwiftUICoreTests/Util/ThreadUtilsTests.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* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: onMainThreadFromDetachedTask Tests/OpenSwiftUICoreTests/Util/ThreadUtilsTests.swift:30— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: deinitCheck Tests/OpenSwiftUICoreTests/Util/ThreadUtilsTests.swift:107— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: removeGlobalActorIsolation Tests/OpenSwiftUICoreTests/Util/_RemoveGlobalActorTests.swift:14— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: viewExtension Tests/OpenSwiftUICoreTests/View/IDViewTests.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* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: pbMessage Tests/OpenSwiftUISymbolDualTests/Animation/CodableEffectAnimationDualTests.swift:25— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: gradientFallback Tests/OpenSwiftUI_SPITests/Util/DynamicCastInterposeTests.swift:54— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: bodyTrigger Tests/OpenSwiftUICompatibilityTests/Data/Observation/ObservationUtilsCompatibilityTests.swift:42— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
FixmeComment Package.swift:224— // FIXME: -unavailable-decl-optimization=stub is not working somehow (eg. Color.vibrancy). Dig into this later — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
FixmeComment Package.swift:404— // FIXME: Weird SwiftPM behavior for test Target. Otherwize we'll get the following error message — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
FixmeComment Package.swift:410— // FIXME: Weird SwiftPM behavior for test Target. Otherwize we'll get the following error message — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
FixmeComment Package.swift:416— // FIXME: Weird SwiftPM behavior for test Target. Otherwize we'll get the following error message — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
FixmeComment Package.swift:422— // FIXME: Weird SwiftPM behavior for test Target. Otherwize we'll get the following error message — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
FixmeComment Package.swift:464— // FIXME: Weird SwiftPM behavior for test Target. Otherwize we'll get the following error message — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
FixmeComment Package.swift:1002— // FIXME: on Linux platform: OG contains unsafe build flags which prevents us using version dependency — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
FixmeComment Tests/OpenSwiftUISymbolDualTests/Data/PropertyListTests.swift:227— // FIXME: Compiler limitation — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
FixmeComment Tests/OpenSwiftUICoreTests/Util/TimerUtilsTests.swift:98— // FIXME: The elapsed time is sometimes not correct on non-Darwin platform — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
FixmeComment Tests/OpenSwiftUICoreTests/Util/TimerUtilsTests.swift:115— // FIXME: callbackExecuted is sometimes not correct on non-Darwin platform — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
FixmeComment Tests/OpenSwiftUICoreTests/Semantic/SemanticsTests.swift:96— // FIXME: Temporary compatibility for Xcode 26.6 CI running on macOS 15 and iOS 18.5. — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
FixmeComment Tests/OpenSwiftUICoreTests/Semantic/SemanticsTests.swift:162— // FIXME: Temporary compatibility for Xcode 26.6 CI running on macOS 15. — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
FixmeComment Tests/OpenSwiftUICoreTests/Data/UpdateTests.swift:8— // FIXME: Add this test on non-Darwin platform — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
FixmeComment Tests/OpenSwiftUICoreTests/Data/Protobuf/ProtobufEncoderTests.swift:10— // FIXME: extra () is a workaround for swiftlang/swift-testing#756
FixmeComment Tests/OpenSwiftUICoreTests/Data/DynamicProperty/DynamicPropertyCacheTests.swift:10— // FIXME: Remove after we implement forEachField — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
FixmeComment Tests/OpenSwiftUICoreTests/Data/DynamicProperty/DynamicPropertyCacheTests.swift:147— // FIXME: Figure this out when OAG implements forEachField — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
FixmeComment Tests/OpenSwiftUICoreTests/Data/Binding/BindingTests.swift:98— // FIXME: uncomment it when `GraphHost.isUpdating` is supported — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
FixmeComment Tests/OpenSwiftUICompatibilityTests/View/EquatableViewCompatibilityTests.swift:18— // FIXME: 1. ?: Changing NumberView to non-POD types seems not working here — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
FixmeComment Tests/OpenSwiftUICompatibilityTests/View/EquatableViewCompatibilityTests.swift:19— // FIXME: 2. the count is not accurate on Unit Test target — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
FixmeComment Tests/OpenSwiftUICompatibilityTests/View/EquatableViewCompatibilityTests.swift:102— // FIXME: CI sometimes to be 1 / 2 / 3. Can't reproduce it locally. Local is alwa2ys 2. — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
FixmeComment Tests/OpenSwiftUICompatibilityTests/View/IdentifiedView/IdentifiedViewProxyCompatibilityTests.swift:14— // FIXME: add _identified modifier — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
FixmeComment Sources/OpenSwiftUICore/View/Text/Text/Text+View.swift:990— // FIXME: RB — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
FixmeComment Sources/OpenSwiftUICore/Graphic/Shader/Shader.swift:54— // FIXME: RB — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
FixmeComment Sources/OpenSwiftUICore/View/Image/Image.swift:180— // TBA: FIXME when we implement ContentTransition and ORBAnimation — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
FixmeComment Sources/OpenSwiftUICore/View/Archive/ArchivedViewHost.swift:72— // MARK: - ArchiveWriter [FIXME] — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
Low cohesion: NSHostingView (LCOM4 22) Sources/OpenSwiftUI/Integration/Hosting/AppKit/View/NSHostingView.swift:32— NSHostingView's methods fall into 22 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 22 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: CGRect (LCOM4 18) Sources/OpenSwiftUI/View/Scroll/HostingScrollView+Focus.swift:221— CGRect's methods fall into 18 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 18 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: CGPoint (LCOM4 18) Sources/OpenSwiftUICore/Layout/Edge/EdgeInsets.swift:354— CGPoint's methods fall into 18 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 18 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: CGSize (LCOM4 16) Sources/OpenSwiftUICore/Layout/AspectRatioLayout.swift:226— CGSize's methods fall into 16 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 16 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: CoreGlue (LCOM4 14) Sources/OpenSwiftUICore/Util/CoreGlue.swift:28— CoreGlue's methods fall into 14 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 14 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: _UIHostingView (LCOM4 13) Sources/OpenSwiftUI/Integration/Hosting/UIKit/View/UIHostingView.swift:21— _UIHostingView's methods fall into 13 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 13 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: CAHostingLayer (LCOM4 13) Sources/OpenSwiftUICore/Render/DisplayList/CAHostingLayer.swift:14— CAHostingLayer's methods fall into 13 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 13 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: ResolvedStyledText (LCOM4 13) Sources/OpenSwiftUICore/View/Text/Text/Text+View.swift:594— ResolvedStyledText's methods fall into 13 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 13 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: Stopwatch (LCOM4 13) Sources/OpenSwiftUICore/View/Text/FormatStyle/SizeAdaptiveFormatStyle.swift:366— Stopwatch's methods fall into 13 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 13 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: AppSceneDelegate (LCOM4 10) Sources/OpenSwiftUI/App/App/UIKit/UIKitAppDelegate.swift:131— AppSceneDelegate's methods fall into 10 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 10 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: UIKitResponderGestureRecognizer (LCOM4 10) Sources/OpenSwiftUI/Event/Platform/UIKit/UIKitResponderGestureRecognizer.swift:20— UIKitResponderGestureRecognizer's methods fall into 10 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 10 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: PlatformViewHost (LCOM4 10) Sources/OpenSwiftUI/Integration/Representable/Platform/PlatformViewHost.swift:25— PlatformViewHost's methods fall into 10 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 10 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: UIHostingViewBase (LCOM4 10) Sources/OpenSwiftUI/Integration/Hosting/UIKit/View/UIHostingViewBase.swift:21— UIHostingViewBase's methods fall into 10 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 10 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: AccessibilityNode (LCOM4 9) Sources/OpenSwiftUI/Accessibility/AccessibilityNode.swift:24— AccessibilityNode's methods fall into 9 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 9 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: OpenSwiftUIGlue (LCOM4 9) Sources/OpenSwiftUI/Util/OpenSwiftUIGlue.swift:28— OpenSwiftUIGlue's methods fall into 9 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 9 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: Attribute (LCOM4 9) Sources/OpenSwiftUICore/Graph/GraphReuse.swift:145— Attribute's methods fall into 9 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 9 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: Timer (LCOM4 9) Sources/OpenSwiftUICore/View/Text/FormatStyle/SizeAdaptiveFormatStyle.swift:380— Timer's methods fall into 9 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 9 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: AppGraph (LCOM4 8) Sources/OpenSwiftUI/App/App/AppGraph.swift:20— AppGraph's methods fall into 8 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 8 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: SelectionTextField (LCOM4 8) Sources/OpenSwiftUI/View/Text/Text+Selection_macOS.swift:150— SelectionTextField's methods fall into 8 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 8 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: AnyLayoutBox (LCOM4 8) Sources/OpenSwiftUICore/Layout/AnyLayout.swift:502— AnyLayoutBox's methods fall into 8 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 8 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: CoreGlue2 (LCOM4 8) Sources/OpenSwiftUICore/Util/CoreGlue.swift:206— CoreGlue2's methods fall into 8 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 8 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: OpenSwiftUIGlue2 (LCOM4 7) Sources/OpenSwiftUI/Util/OpenSwiftUIGlue.swift:155— OpenSwiftUIGlue2's methods fall into 7 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 7 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: GestureResponder (LCOM4 7) Sources/OpenSwiftUICore/Event/Gesture/GestureViewModifier.swift:275— GestureResponder's methods fall into 7 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 7 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: NSMutableAttributedString (LCOM4 7) Sources/OpenSwiftUICore/Shim/TextNonDarwinShims.swift:233— NSMutableAttributedString's methods fall into 7 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 7 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: DateReference (LCOM4 7) Sources/OpenSwiftUICore/View/Text/FormatStyle/CalendarDependentFormatStyle.swift:93— DateReference's methods fall into 7 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 7 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.
FileTooLong: DisplayList/DisplayListViewPlatform.swift Sources/OpenSwiftUICore/Render/DisplayList/DisplayListViewPlatform.swift— FileTooLong — 1687 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 1187 over it, 3.37× 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: Input/ViewList.swift Sources/OpenSwiftUICore/View/Input/ViewList.swift— FileTooLong — 1649 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 1149 over it, 3.30× 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: Text/Text+View.swift Sources/OpenSwiftUICore/View/Text/Text/Text+View.swift— FileTooLong — 1416 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 916 over it, 2.83× 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: Layout/JindoTripleVStack.swift Sources/OpenSwiftUI/Layout/JindoTripleVStack.swift— FileTooLong — 1175 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 675 over it, 2.35× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: Image/NamedImage.swift Sources/OpenSwiftUICore/View/Image/NamedImage.swift— FileTooLong — 1062 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 562 over it, 2.12× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: DynamicViewContent/ForEach.swift Sources/OpenSwiftUICore/View/DynamicViewContent/ForEach.swift— FileTooLong — 1051 significant lines (blank, comment-only and punctuation-only lines excluded), about 80% of them inside a single declaration: ForEachState (311-1439). The bar is 500 significant lines; this is 551 over it, 2.10× 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: FormatStyle/SystemFormatStyle+Timer.swift Sources/OpenSwiftUICore/View/Text/FormatStyle/SystemFormatStyle+Timer.swift— FileTooLong — 935 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 435 over it, 1.87× 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: View/NSHostingView.swift Sources/OpenSwiftUI/Integration/Hosting/AppKit/View/NSHostingView.swift— FileTooLong — 915 significant lines (blank, comment-only and punctuation-only lines excluded), about 72% of them inside a single declaration: NSHostingView (36-1143). The bar is 500 significant lines; this is 415 over it, 1.83× 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: DisplayList/DisplayList.swift Sources/OpenSwiftUICore/Render/DisplayList/DisplayList.swift— FileTooLong — 826 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 326 over it, 1.65× 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: Focus/Focusable.swift Sources/OpenSwiftUI/Event/Focus/Focusable.swift— FileTooLong — 746 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 246 over it, 1.49× 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: Shape/Path.swift Sources/OpenSwiftUICore/Shape/Path.swift— FileTooLong — 724 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 224 over it, 1.45× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: View/UIHostingViewBase.swift Sources/OpenSwiftUI/Integration/Hosting/UIKit/View/UIHostingViewBase.swift— FileTooLong — 686 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 186 over it, 1.37× 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: Shape/ShapeLayer.swift Sources/OpenSwiftUICore/Shape/ShapeLayer.swift— FileTooLong — 686 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 186 over it, 1.37× 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: Localized/Text+Localized.swift Sources/OpenSwiftUICore/View/Text/Localized/Text+Localized.swift— FileTooLong — 674 significant lines (blank, comment-only and punctuation-only lines excluded), about 68% of them inside a single declaration: LocalizedStringKey (183-1009). The bar is 500 significant lines; this is 174 over it, 1.35× 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: Gradient/GradientStyle.swift Sources/OpenSwiftUICore/Graphic/Gradient/GradientStyle.swift— FileTooLong — 673 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 173 over it, 1.35× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: PlatformItemList/WidgetAuxiliaryViewMetadata.swift Sources/OpenSwiftUI/Integration/PlatformItemList/WidgetAuxiliaryViewMetadata.swift— FileTooLong — 656 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 156 over it, 1.31× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: View/ViewTransform.swift Sources/OpenSwiftUICore/Layout/View/ViewTransform.swift— FileTooLong — 648 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 148 over it, 1.30× 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: SymbolEffect/_SymbolEffect.swift Sources/OpenSwiftUICore/Render/SymbolEffect/_SymbolEffect.swift— FileTooLong — 644 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 144 over it, 1.29× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: Button/AppKitButton.swift Sources/OpenSwiftUI/View/Control/Button/AppKitButton.swift— FileTooLong — 638 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 138 over it, 1.28× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: ShapeStyle/ShapeStylePack.swift Sources/OpenSwiftUICore/Shape/ShapeStyle/ShapeStylePack.swift— FileTooLong — 617 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 117 over it, 1.23× 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: Platform/PlatformViewRepresentable.swift Sources/OpenSwiftUI/Integration/Representable/Platform/PlatformViewRepresentable.swift— FileTooLong — 616 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 116 over it, 1.23× 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: Accessibility/AccessibilityViewModifier.swift Sources/OpenSwiftUI/Accessibility/AccessibilityViewModifier.swift— FileTooLong — 592 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 92 over it, 1.18× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: Layout/Layout.swift Sources/OpenSwiftUICore/Layout/Layout.swift— FileTooLong — 588 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 88 over it, 1.18× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: Graph/ViewGraph.swift Sources/OpenSwiftUICore/View/Graph/ViewGraph.swift— FileTooLong — 582 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 82 over it, 1.16× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: Dynamic/DynamicContainer.swift Sources/OpenSwiftUICore/Layout/Dynamic/DynamicContainer.swift— FileTooLong — 576 significant lines (blank, comment-only and punctuation-only lines excluded), about 63% of them inside a single declaration: DynamicContainerInfo (285-751). The bar is 500 significant lines; this is 76 over it, 1.15× 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.
TooManyMethods: NSHostingView Sources/OpenSwiftUI/Integration/Hosting/AppKit/View/NSHostingView.swift:32— TooManyMethods — 82 methods. The bar is 30 methods; this is 52 over it, 2.73× 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: _UIHostingView Sources/OpenSwiftUI/Integration/Hosting/UIKit/View/UIHostingView.swift:21— TooManyMethods — 65 methods, declared across 2 files: View/UIHostingView.swift (35), View/UIHostingView+Extension.swift (30). The bar is 30 methods; this is 35 over it, 2.17× 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: ProtobufEncoder Sources/OpenSwiftUICore/Data/Protobuf/ProtobufEncoder.swift:12— TooManyMethods — 63 methods. The bar is 30 methods; this is 33 over it, 2.10× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: Text Sources/OpenSwiftUI/Integration/PlatformItemList/WidgetAuxiliaryViewMetadata.swift:30— TooManyMethods — 59 methods, declared across 18 files: Text/Text+Renderer.swift (23), Text/Text+Date.swift (9), Text/Text+View.swift (3), Text/Text.swift (3), +14 more file(s). The bar is 30 methods; this is 29 over it, 1.97× 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: Path Sources/OpenSwiftUICore/Shape/Path.swift:18— TooManyMethods — 54 methods, declared across 3 files: Shape/Path.swift (51), View/ViewTransform.swift (2), DisplayList/DisplayListViewModel.swift (1). The bar is 30 methods; this is 24 over it, 1.80× 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: Font Sources/OpenSwiftUICore/View/Text/Font/Font.swift:20— TooManyMethods — 50 methods, declared across 8 files: Font/ModifiedFont.swift (19), Font/Font.swift (12), Font/CustomFont.swift (6), Font/TextStyle.swift (6), +4 more file(s). The bar is 30 methods; this is 20 over it, 1.67× 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: UIHostingViewBase Sources/OpenSwiftUI/Integration/Hosting/UIKit/View/UIHostingViewBase.swift:21— TooManyMethods — 45 methods. The bar is 30 methods; this is 15 over it, 1.50× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: CGPoint Sources/OpenSwiftUICore/Layout/Edge/EdgeInsets.swift:354— TooManyMethods — 41 methods, declared across 8 files: Extension/CGPoint+Extension.swift (17), Extension/CGPoint+Math.swift (10), Extension/Round+Extension.swift (6), Geometry/Anchor+Point.swift (2), +4 more file(s). The bar is 30 methods; this is 11 over it, 1.37× 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: Platform Sources/OpenSwiftUI/Event/Gesture/DragGesture.swift:116— TooManyMethods — 40 methods. The bar is 30 methods; this is 10 over it, 1.33× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: CGSize Sources/OpenSwiftUICore/Layout/AspectRatioLayout.swift:226— TooManyMethods — 40 methods, declared across 9 files: Extension/CGSize+Extension.swift (12), Extension/CGSize+Math.swift (11), Layout/AspectRatioLayout.swift (6), Extension/Round+Extension.swift (4), +5 more file(s). The bar is 30 methods; this is 10 over it, 1.33× 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: ViewGraph Sources/OpenSwiftUICore/View/Graph/ViewGraph.swift:20— TooManyMethods — 39 methods, declared across 3 files: Graph/ViewGraph.swift (35), Focus/FocusViewGraph.swift (3), Util/ScrapeableContent.swift (1). The bar is 30 methods; this is 9 over it, 1.30× 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: ModifiedContent Sources/OpenSwiftUICore/Modifier/ViewModifier.swift:387— TooManyMethods — 38 methods, declared across 11 files: Accessibility/AccessibilityActionKind.swift (8), Modifier/ViewModifier.swift (8), Accessibility/AccessibilityTraitsAdditions.swift (7), Accessibility/AccessibilityAppIntentAction.swift (3), +7 more file(s). The bar is 30 methods; this is 8 over it, 1.27× 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: AccessibilityNode Sources/OpenSwiftUI/Accessibility/AccessibilityNode.swift:24— TooManyMethods — 36 methods, declared across 2 files: Accessibility/AccessibilityNode.swift (32), Platform/AppKitAccessibility.swift (4). The bar is 30 methods; this is 6 over it, 1.20× 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: Color Sources/OpenSwiftUICore/Graphic/Color/Color.swift:74— TooManyMethods — 36 methods, declared across 15 files: Color/Color.swift (8), Color/ModifiedColor.swift (7), Color/Color+ShapeStyle.swift (3), Color/RGBColorSpace.swift (3), +11 more file(s). The bar is 30 methods; this is 6 over it, 1.20× 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: PlatformViewHost Sources/OpenSwiftUI/Integration/Representable/Platform/PlatformViewHost.swift:25— TooManyMethods — 35 methods. The bar is 30 methods; this is 5 over it, 1.17× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: CGRect Sources/OpenSwiftUI/View/Scroll/HostingScrollView+Focus.swift:221— TooManyMethods — 35 methods, declared across 8 files: Extension/CGRect+Extension.swift (20), Edge/EdgeInsets.swift (4), View/ViewTransform.swift (3), Geometry/Anchor+Rect.swift (2), +4 more file(s). The bar is 30 methods; this is 5 over it, 1.17× 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: Animation Sources/OpenSwiftUICore/Animation/Animation/Animation.swift:106— TooManyMethods — 35 methods, declared across 12 files: Spring/FluidSpringAnimation.swift (11), Animation/Animation.swift (7), Animation/BezierAnimation.swift (6), Animation/RepeatAnimation.swift (2), +8 more file(s). The bar is 30 methods; this is 5 over it, 1.17× 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: GraphHost Sources/OpenSwiftUICore/Graph/GraphHost.swift:45— TooManyMethods — 35 methods. The bar is 30 methods; this is 5 over it, 1.17× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: CAHostingLayer Sources/OpenSwiftUICore/Render/DisplayList/CAHostingLayer.swift:14— TooManyMethods — 31 methods. The bar is 30 methods; this is 1 over it, 1.03× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
Duplicated block (11 lines × 2) Sources/OpenSwiftUI/Event/Focus/FocusBridge.swift:336— Sources/OpenSwiftUI/Event/Focus/FocusBridge.swift:336-346 | Sources/OpenSwiftUI/Event/Focus/FocusBridge.swift:702-712 — 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/OpenSwiftUI/Event/Focus/FocusBridge.swift:336` 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 (11 lines × 2) Sources/OpenSwiftUI/Modifier/SceneModifier/PreferenceSceneModifier.swift:17— Sources/OpenSwiftUI/Modifier/SceneModifier/PreferenceSceneModifier.swift:17-27 | Sources/OpenSwiftUICore/Data/Preference/PreferenceWritingModifier.swift:31-41 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit. Note first that the copies are not typed on the same thing: the declarations holding them bind `body` to `@escaping (_Graph, _SceneInputs) -> _SceneOutputs` in one and `@escaping (_Graph, _ViewInputs) -> _ViewOutputs` in another, and the duplicated lines use it. The extracted unit therefore needs a parameter type that fits BOTH — their common supertype where they have one, or a new abstraction over them where they do not — and settling that is the step that comes BEFORE the extraction above. Where the two types are deliberately unrelated, the duplication is the price of that separation and the honest resolution is to record the decision rather than to extract.
Duplicated block (11 lines × 2) Sources/OpenSwiftUI/Modifier/SceneModifier/ValueActionSceneModifier.swift:105— Sources/OpenSwiftUI/Modifier/SceneModifier/ValueActionSceneModifier.swift:105-115 | Sources/OpenSwiftUI/Modifier/SceneModifier/ValueActionSceneModifier.swift:249-259 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `Sources/OpenSwiftUI/Modifier/SceneModifier/ValueActionSceneModifier.swift:105` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
Duplicated block (11 lines × 2) Sources/OpenSwiftUI/Modifier/ViewModifier/TaskModifier.swift:171— Sources/OpenSwiftUI/Modifier/ViewModifier/TaskModifier.swift:171-181 | Sources/OpenSwiftUI/Modifier/ViewModifier/TaskModifier.swift:260-270 — 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/OpenSwiftUI/Modifier/ViewModifier/TaskModifier.swift:183— Sources/OpenSwiftUI/Modifier/ViewModifier/TaskModifier.swift:183-193 | Sources/OpenSwiftUI/Modifier/ViewModifier/TaskModifier.swift:272-282 — 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/OpenSwiftUI/View/Container/TraitValues.swift:87— Sources/OpenSwiftUI/View/Container/TraitValues.swift:87-97 | Sources/OpenSwiftUICore/View/Container/ContainerValueWritingModifier.swift:143-153 — before extracting anything, compare `Sources/OpenSwiftUI/View/Container/TraitValues.swift` and `Sources/OpenSwiftUICore/View/Container/ContainerValueWritingModifier.swift` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 31 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `Sources/OpenSwiftUI/View/Container/TraitValues.swift:87` 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/OpenSwiftUICore/Animation/Animation/UnitCurve.swift:79— Sources/OpenSwiftUICore/Animation/Animation/UnitCurve.swift:79-89 | Sources/OpenSwiftUICore/Animation/Animation/UnitCurve.swift:118-128 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `Sources/OpenSwiftUICore/Animation/Animation/UnitCurve.swift:79` 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/OpenSwiftUICore/Layout/PlacementContext.swift:76— Sources/OpenSwiftUICore/Layout/PlacementContext.swift:76-86 | Sources/OpenSwiftUICore/Layout/PlacementContext.swift:151-161 — 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/OpenSwiftUICore/Layout/PlacementContext.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 (11 lines × 2) Sources/OpenSwiftUICore/Modifier/ViewModifier/ValueActionModifier.swift:127— Sources/OpenSwiftUICore/Modifier/ViewModifier/ValueActionModifier.swift:127-137 | Sources/OpenSwiftUICore/Modifier/ViewModifier/ValueActionModifier.swift:358-368 — 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/OpenSwiftUICore/Modifier/ViewModifier/ValueActionModifier.swift:127` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
Duplicated block (11 lines × 2) Sources/OpenSwiftUICore/View/Text/FormatStyle/SystemFormatStyle+Timer.swift:963— Sources/OpenSwiftUICore/View/Text/FormatStyle/SystemFormatStyle+Timer.swift:963-973 | Sources/OpenSwiftUICore/View/Text/FormatStyle/SystemFormatStyle+Timer.swift:978-988 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (11 lines × 2) Sources/OpenSwiftUICore/View/Text/Resolve/ResolvableTextSegmentAttribute.swift:368— Sources/OpenSwiftUICore/View/Text/Resolve/ResolvableTextSegmentAttribute.swift:368-378 | Sources/OpenSwiftUICore/View/Text/Resolve/ResolvableTextSegmentAttribute.swift:406-416 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `Sources/OpenSwiftUICore/View/Text/Resolve/ResolvableTextSegmentAttribute.swift:368` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
Duplicated block (11 lines × 2) Sources/OpenSwiftUI/App/App/AppKit/AppWindowsController.swift:140— Sources/OpenSwiftUI/App/App/AppKit/AppWindowsController.swift:140-150 | Sources/OpenSwiftUI/App/App/UIKit/UIKitAppDelegate.swift:666-676 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (11 lines × 2) Example/Project.swift:117— Example/Project.swift:117-127 | Example/Project.swift:182-192 — 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 `Example/Project.swift:117` 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) Example/Shared/Shape/FlowerView.swift:13— Example/Shared/Shape/FlowerView.swift:13-23 | Example/Shared/Shape/FlowerView.swift:30-40 — 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 `Example/Shared/Shape/FlowerView.swift:13` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (11 lines × 2) Example/Shared/Graphics/Gradient/GradientExample.swift:70— Example/Shared/Graphics/Gradient/GradientExample.swift:70-80 | Example/Shared/Render/RendererEffect/ColorEffectExample.swift:24-34 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (7 lines × 2) Sources/OpenSwiftUI/View/Control/Slider/SliderMark.swift:73— Sources/OpenSwiftUI/View/Control/Slider/SliderMark.swift:73-79 | Sources/OpenSwiftUI/View/Control/Slider/SliderMark.swift:95-101 — 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/OpenSwiftUI/View/Control/Slider/SliderMark.swift:73` 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/OpenSwiftUI/View/Control/Stepper/Stepper.swift:338— Sources/OpenSwiftUI/View/Control/Stepper/Stepper.swift:338-344 | Sources/OpenSwiftUI/View/Control/Stepper/Stepper.swift:418-424 — 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/OpenSwiftUI/View/Control/Stepper/Stepper.swift:338` 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/OpenSwiftUICore/Graphic/Color/ColorMatrix.swift:293— Sources/OpenSwiftUICore/Graphic/Color/ColorMatrix.swift:293-299 | Sources/OpenSwiftUICore/Graphic/Color/ColorMatrix.swift:313-319 — 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/OpenSwiftUICore/Graphic/Color/ColorMatrix.swift:293` 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 (7 lines × 2) Sources/OpenSwiftUICore/Tracing/CustomEventTrace.swift:209— Sources/OpenSwiftUICore/Tracing/CustomEventTrace.swift:209-215 | Sources/OpenSwiftUICore/Tracing/CustomEventTrace.swift:254-260 — 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/OpenSwiftUICore/Tracing/CustomEventTrace.swift:209` 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/OpenSwiftUI/Integration/Hosting/AppKit/View/NSHostingView.swift:710— Sources/OpenSwiftUI/Integration/Hosting/AppKit/View/NSHostingView.swift:710-716 | Sources/OpenSwiftUI/Integration/Hosting/UIKit/View/UIHostingView.swift:406-412 — 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 (7 lines × 2) Sources/OpenSwiftUICore/Animation/Animation/Codable/CodableEffectAnimation.swift:55— Sources/OpenSwiftUICore/Animation/Animation/Codable/CodableEffectAnimation.swift:55-61 | Sources/OpenSwiftUICore/Animation/Animation/CustomAnimation.swift:217-223 — 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 (7 lines × 2) Sources/OpenSwiftUICore/Layout/Modifier/DefaultPadding.swift:112— Sources/OpenSwiftUICore/Layout/Modifier/DefaultPadding.swift:112-118 | Sources/OpenSwiftUICore/Layout/SpacingLayout.swift:17-23 — 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 (7 lines × 2) Sources/OpenSwiftUICore/Modifier/CustomViewModifier.swift:105— Sources/OpenSwiftUICore/Modifier/CustomViewModifier.swift:105-111 | Sources/OpenSwiftUICore/View/VariadicView/VariadicView.swift:299-305 — 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 (7 lines × 2) Sources/OpenSwiftUICore/Render/GeometryEffect/GeometryEffect.swift:84— Sources/OpenSwiftUICore/Render/GeometryEffect/GeometryEffect.swift:84-90 | Sources/OpenSwiftUICore/Render/RendererEffect/RendererEffect.swift:134-140 — 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 (7 lines × 2) Sources/OpenSwiftUI/Accessibility/AccessibilityFocusState.swift:95— Sources/OpenSwiftUI/Accessibility/AccessibilityFocusState.swift:95-101 | Sources/OpenSwiftUI/Event/Focus/FocusState.swift:148-154 — 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 (7 lines × 2) Sources/OpenSwiftUICore/Graphic/Gradient/AnyGradient.swift:41— Sources/OpenSwiftUICore/Graphic/Gradient/AnyGradient.swift:41-47 | Sources/OpenSwiftUICore/Graphic/Gradient/Gradient.swift:103-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 both call sites, so a change lands once.
Duplicated block (7 lines × 2) Sources/OpenSwiftUICore/Layout/Geometry/UnitRect.swift:16— Sources/OpenSwiftUICore/Layout/Geometry/UnitRect.swift:16-22 | Sources/OpenSwiftUICore/Shape/RoundedCornerStyle.swift:294-300 — 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 (7 lines × 2) Sources/OpenSwiftUICore/Layout/Stack/HVStack.swift:35— Sources/OpenSwiftUICore/Layout/Stack/HVStack.swift:35-41 | Sources/OpenSwiftUICore/View/VariadicView/VariadicView.swift:291-297 — 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 (7 lines × 2) Sources/OpenSwiftUICore/Render/HoverEffect/CustomHoverEffect.swift:85— Sources/OpenSwiftUICore/Render/HoverEffect/CustomHoverEffect.swift:85-91 | Sources/OpenSwiftUICore/Render/HoverEffect/HoverEffectContentCore.swift:50-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. Note first that the copies are not typed on the same thing: the declarations holding them bind `body` to `@escaping (_CustomHoverEffectInputs) -> _CustomHoverEffectOutputs` in one and `@escaping (_HoverEffectContentInputs) -> _HoverEffectContentOutputs` in another, and the duplicated lines use it. The extracted unit therefore needs a parameter type that fits BOTH — their common supertype where they have one, or a new abstraction over them where they do not — and settling that is the step that comes BEFORE the extraction above. Where the two types are deliberately unrelated, the duplication is the price of that separation and the honest resolution is to record the decision rather than to extract.
Duplicated block (7 lines × 2) Example/Shared/View/Image/ImageConversionsExample.swift:20— Example/Shared/View/Image/ImageConversionsExample.swift:20-26 | Example/Shared/View/Image/ImageConversionsExample.swift:28-34 — 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 `Example/Shared/View/Image/ImageConversionsExample.swift:20` 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/OpenSwiftUI/Accessibility/AccessibilityActionCategory.swift:141— Sources/OpenSwiftUI/Accessibility/AccessibilityActionCategory.swift:141-145 | Sources/OpenSwiftUI/Accessibility/AccessibilityActionKind.swift:235-239 — 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/OpenSwiftUI/Accessibility/AccessibilityActionCategory.swift:141` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (5 lines × 2) Sources/OpenSwiftUICore/Data/DynamicProperty/DynamicProperty.swift:428— Sources/OpenSwiftUICore/Data/DynamicProperty/DynamicProperty.swift:428-432 | Sources/OpenSwiftUICore/Data/DynamicProperty/DynamicProperty.swift:508-512 — 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 (5 lines × 2) Sources/OpenSwiftUICore/Graphic/BlurStyle/BlurStyle.swift:47— Sources/OpenSwiftUICore/Graphic/BlurStyle/BlurStyle.swift:47-51 | Sources/OpenSwiftUICore/Graphic/BlurStyle/VariableBlurStyle.swift:66-70 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `Sources/OpenSwiftUICore/Graphic/BlurStyle/BlurStyle.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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `Sources/OpenSwiftUICore/Graphic/BlurStyle/VariableBlurStyle.swift:71` calls `messageField` and `Sources/OpenSwiftUICore/Graphic/BlurStyle/BlurStyle.swift:52` does not — after which the two agree again for 4 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (5 lines × 2) Sources/OpenSwiftUICore/Graphic/Color/SystemColors.swift:304— Sources/OpenSwiftUICore/Graphic/Color/SystemColors.swift:304-308 | Sources/OpenSwiftUICore/Graphic/Color/SystemColors.swift:422-426 — 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/OpenSwiftUICore/Graphic/Color/SystemColors.swift:304` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (5 lines × 2) Sources/OpenSwiftUICore/Graphic/Color/SystemColors.swift:309— Sources/OpenSwiftUICore/Graphic/Color/SystemColors.swift:309-313 | Sources/OpenSwiftUICore/Graphic/Color/SystemColors.swift:427-431 — 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/OpenSwiftUICore/Graphic/Color/SystemColors.swift:309` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (5 lines × 2) Sources/OpenSwiftUICore/Graphic/Color/SystemColors.swift:339— Sources/OpenSwiftUICore/Graphic/Color/SystemColors.swift:339-343 | Sources/OpenSwiftUICore/Graphic/Color/SystemColors.swift:454-458 — 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/OpenSwiftUICore/Graphic/Color/SystemColors.swift:339` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (5 lines × 2) Sources/OpenSwiftUICore/Runtime/ConditionalMetadata.swift:145— Sources/OpenSwiftUICore/Runtime/ConditionalMetadata.swift:145-149 | Sources/OpenSwiftUICore/Runtime/ConditionalMetadata.swift:165-170 — 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/OpenSwiftUICore/Runtime/ConditionalMetadata.swift:145` 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/OpenSwiftUI/Event/Gesture/GestureState.swift:317— Sources/OpenSwiftUI/Event/Gesture/GestureState.swift:317-321 | Sources/OpenSwiftUICore/Event/Gesture/CallbacksGesture.swift:385-389 — 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 (5 lines × 2) Sources/OpenSwiftUI/App/App/AppKit/AppKitAppDelegate.swift:46— Sources/OpenSwiftUI/App/App/AppKit/AppKitAppDelegate.swift:46-50 | Sources/OpenSwiftUI/App/App/UIKit/UIKitAppDelegate.swift:76-80 — 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 (5 lines × 2) Sources/OpenSwiftUI/View/Container/TraitValues.swift:113— Sources/OpenSwiftUI/View/Container/TraitValues.swift:113-117 | Sources/OpenSwiftUICore/View/Container/ContainerValueWritingModifier.swift:168-172 — before extracting anything, compare `Sources/OpenSwiftUI/View/Container/TraitValues.swift` and `Sources/OpenSwiftUICore/View/Container/ContainerValueWritingModifier.swift` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 31 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `Sources/OpenSwiftUI/View/Container/TraitValues.swift:121` calls `_spi` and `Sources/OpenSwiftUICore/View/Container/ContainerValueWritingModifier.swift:176` 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/OpenSwiftUICore/Layout/Geometry/Anchor+Point.swift:15— Sources/OpenSwiftUICore/Layout/Geometry/Anchor+Point.swift:15-19 | Sources/OpenSwiftUICore/Layout/Geometry/Anchor+Rect.swift:17-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.
Duplicated block (5 lines × 2) Sources/OpenSwiftUICore/Util/Extension/CGPoint+Extension.swift:79— Sources/OpenSwiftUICore/Util/Extension/CGPoint+Extension.swift:79-83 | Sources/OpenSwiftUICore/Util/Extension/CGSize+Extension.swift:80-84 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (5 lines × 2) Sources/OpenSwiftUICore/View/Text/Text/Text+Date.swift:455— Sources/OpenSwiftUICore/View/Text/Text/Text+Date.swift:455-459 | Sources/OpenSwiftUICore/View/Text/Text/Text+Image.swift:31-35 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (5 lines × 2) Sources/OpenSwiftUICore/Render/DisplayList/DisplayListViewModel.swift:413— Sources/OpenSwiftUICore/Render/DisplayList/DisplayListViewModel.swift:413-417 | Sources/OpenSwiftUICore/Render/DisplayList/DisplayListViewModel.swift:425-429 — 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/OpenSwiftUICore/Render/DisplayList/DisplayListViewModel.swift:413` 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/OpenSwiftUICore/View/VariadicView/VariadicView.swift:316— Sources/OpenSwiftUICore/View/VariadicView/VariadicView.swift:316-320 | Sources/OpenSwiftUICore/View/VariadicView/VariadicView.swift:333-337 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Note first that the copies are not typed on the same thing: the declarations holding them bind `body` to `(_Graph, _ViewInputs) -> _ViewListOutputs` in one and `@escaping (_Graph, _ViewListInputs) -> _ViewListOutputs` in another, and the duplicated lines use it. The extracted unit therefore needs a parameter type that fits BOTH — their common supertype where they have one, or a new abstraction over them where they do not — and settling that is the step that comes BEFORE the extraction above. Where the two types are deliberately unrelated, the duplication is the price of that separation and the honest resolution is to record the decision rather than to extract.
Duplicated block (8 lines × 2) Sources/OpenSwiftUI/Accessibility/AccessibilityAttachmentModifier.swift:80— Sources/OpenSwiftUI/Accessibility/AccessibilityAttachmentModifier.swift:80-87 | Sources/OpenSwiftUI/Accessibility/AccessibilityPlatform.swift:41-48 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `Sources/OpenSwiftUI/Accessibility/AccessibilityAttachmentModifier.swift:80` 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) Sources/OpenSwiftUI/View/Control/Slider/Slider.swift:541— Sources/OpenSwiftUI/View/Control/Slider/Slider.swift:541-548 | Sources/OpenSwiftUI/View/Control/Stepper/Stepper.swift:1323-1330 — 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/OpenSwiftUI/View/Control/Slider/Slider.swift:541` 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) Sources/OpenSwiftUI/View/Control/Slider/SliderMark.swift:24— Sources/OpenSwiftUI/View/Control/Slider/SliderMark.swift:24-31 | Sources/OpenSwiftUI/View/Control/Slider/SliderMark.swift:74-81 — 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/OpenSwiftUI/View/Control/Slider/SliderMark.swift:24` 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/OpenSwiftUI/View/Control/Slider/SliderMark.swift:47— Sources/OpenSwiftUI/View/Control/Slider/SliderMark.swift:47-54 | Sources/OpenSwiftUI/View/Control/Slider/SliderMark.swift:96-103 — 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/OpenSwiftUI/View/Control/Slider/SliderMark.swift:47` 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/OpenSwiftUI/View/Control/Stepper/Stepper.swift:843— Sources/OpenSwiftUI/View/Control/Stepper/Stepper.swift:843-850 | Sources/OpenSwiftUI/View/Control/Stepper/Stepper.swift:911-918 — 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/OpenSwiftUI/View/Control/Stepper/Stepper.swift:843` 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/OpenSwiftUICore/Data/Preference/PreferenceActionModifier.swift:47— Sources/OpenSwiftUICore/Data/Preference/PreferenceActionModifier.swift:47-54 | Sources/OpenSwiftUICore/Data/Preference/PreferenceActionModifier.swift:136-143 — 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/OpenSwiftUICore/Data/Preference/PreferenceActionModifier.swift:47` 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/OpenSwiftUICore/Modifier/ViewModifier/BackgroundModifier.swift:335— Sources/OpenSwiftUICore/Modifier/ViewModifier/BackgroundModifier.swift:335-342 | Sources/OpenSwiftUICore/Modifier/ViewModifier/OverlayModifier.swift:149-156 — 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/OpenSwiftUICore/Modifier/ViewModifier/BackgroundModifier.swift:335` 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) Sources/OpenSwiftUICore/Render/SymbolEffect/_SymbolEffect.swift:797— Sources/OpenSwiftUICore/Render/SymbolEffect/_SymbolEffect.swift:797-804 | Sources/OpenSwiftUICore/Render/SymbolEffect/_SymbolEffect.swift:853-860 — 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/OpenSwiftUICore/Render/SymbolEffect/_SymbolEffect.swift:797` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (8 lines × 2) Sources/OpenSwiftUI/Data/State/LazyState.swift:58— Sources/OpenSwiftUI/Data/State/LazyState.swift:58-65 | Sources/OpenSwiftUICore/Data/State/State.swift:376-383 — 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 (8 lines × 2) Sources/OpenSwiftUI/Event/Responder/ContentShapeModifier.swift:118— Sources/OpenSwiftUI/Event/Responder/ContentShapeModifier.swift:118-125 | Sources/OpenSwiftUICore/Event/Responder/LeafViewResponder.swift:108-115 — 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 (8 lines × 2) Sources/OpenSwiftUI/Modifier/SceneModifier/SceneModifier.swift:234— Sources/OpenSwiftUI/Modifier/SceneModifier/SceneModifier.swift:234-241 | Sources/OpenSwiftUICore/Modifier/CustomViewModifier.swift:337-344 — 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 (8 lines × 2) Sources/OpenSwiftUI/Render/DisplayList/DisplayListViewDrawing.swift:100— Sources/OpenSwiftUI/Render/DisplayList/DisplayListViewDrawing.swift:100-107 | Sources/OpenSwiftUICore/Render/DisplayList/CAHostingLayerPlatformDefinition.swift:135-142 — 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 (8 lines × 2) Sources/OpenSwiftUI/Render/DisplayList/DisplayListViewDrawing.swift:130— Sources/OpenSwiftUI/Render/DisplayList/DisplayListViewDrawing.swift:130-137 | Sources/OpenSwiftUICore/Render/DisplayList/CAHostingLayerPlatformDefinition.swift:153-160 — 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 (8 lines × 2) Sources/OpenSwiftUI/View/Container/TraitValues.swift:70— Sources/OpenSwiftUI/View/Container/TraitValues.swift:70-77 | Sources/OpenSwiftUICore/View/Container/ContainerValueWritingModifier.swift:126-133 — before extracting anything, compare `Sources/OpenSwiftUI/View/Container/TraitValues.swift` and `Sources/OpenSwiftUICore/View/Container/ContainerValueWritingModifier.swift` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 31 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (6 lines × 2) Sources/OpenSwiftUI/Accessibility/AccessibilityActionCategory.swift:140— Sources/OpenSwiftUI/Accessibility/AccessibilityActionCategory.swift:140-145 | Sources/OpenSwiftUI/Accessibility/AccessibilityActionKind.swift:215-220 — 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/OpenSwiftUI/Accessibility/AccessibilityActionCategory.swift:140` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
Duplicated block (6 lines × 2) Sources/OpenSwiftUI/Integration/Representable/AppKit/NSViewRepresentable.swift:239— Sources/OpenSwiftUI/Integration/Representable/AppKit/NSViewRepresentable.swift:239-244 | Sources/OpenSwiftUI/Integration/Representable/UIKit/UIViewRepresentable.swift:224-229 — before extracting anything, compare `Sources/OpenSwiftUI/Integration/Representable/AppKit/NSViewRepresentable.swift` and `Sources/OpenSwiftUI/Integration/Representable/UIKit/UIViewRepresentable.swift` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 36 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `Sources/OpenSwiftUI/Integration/Representable/AppKit/NSViewRepresentable.swift:239` 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/OpenSwiftUICore/Graphic/Color/SystemColors.swift:351— Sources/OpenSwiftUICore/Graphic/Color/SystemColors.swift:351-356 | Sources/OpenSwiftUICore/Graphic/Color/SystemColors.swift:466-471 — 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/OpenSwiftUICore/Graphic/Color/SystemColors.swift:351` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (6 lines × 2) Sources/OpenSwiftUICore/Graphic/Color/SystemColors.swift:357— Sources/OpenSwiftUICore/Graphic/Color/SystemColors.swift:357-362 | Sources/OpenSwiftUICore/Graphic/Color/SystemColors.swift:472-477 — 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/OpenSwiftUICore/Graphic/Color/SystemColors.swift:357` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (6 lines × 2) Sources/OpenSwiftUICore/Runtime/ConditionalMetadata.swift:190— Sources/OpenSwiftUICore/Runtime/ConditionalMetadata.swift:190-195 | Sources/OpenSwiftUICore/Runtime/ConditionalMetadata.swift:201-206 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. 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/OpenSwiftUICore/Shape/MaskLayer.swift:80— Sources/OpenSwiftUICore/Shape/MaskLayer.swift:80-85 | Sources/OpenSwiftUICore/Shape/MaskLayer.swift:89-94 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (6 lines × 2) Sources/OpenSwiftUICore/Shape/ShapeView.swift:210— Sources/OpenSwiftUICore/Shape/ShapeView.swift:210-215 | Sources/OpenSwiftUICore/Shape/ShapeView.swift:237-243 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (6 lines × 2) Sources/OpenSwiftUICore/View/Image/ImageOrientation.swift:129— Sources/OpenSwiftUICore/View/Image/ImageOrientation.swift:129-134 | Sources/OpenSwiftUICore/View/Image/ImageOrientation.swift:150-155 — 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/OpenSwiftUICore/View/Image/ImageOrientation.swift:129` 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/OpenSwiftUICore/View/Text/Text/Text+View.swift:1141— Sources/OpenSwiftUICore/View/Text/Text/Text+View.swift:1141-1146 | Sources/OpenSwiftUICore/View/Text/Text/Text+View.swift:1169-1174 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (6 lines × 2) Sources/OpenSwiftUICore/View/DynamicViewContent/ForEach.swift:1431— Sources/OpenSwiftUICore/View/DynamicViewContent/ForEach.swift:1431-1436 | Sources/OpenSwiftUICore/View/Input/ViewList.swift:1706-1711 — 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/OpenSwiftUICore/View/Text/FormatStyle/CalendarDependentFormatStyle.swift:16— Sources/OpenSwiftUICore/View/Text/FormatStyle/CalendarDependentFormatStyle.swift:16-21 | Sources/OpenSwiftUICore/View/Text/FormatStyle/TimeZoneDependentFormatStyle.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.
Duplicated block (6 lines × 2) Example/Shared/Render/RendererEffect/BlendModeExample.swift:20— Example/Shared/Render/RendererEffect/BlendModeExample.swift:20-25 | Example/Shared/Render/RendererEffect/BlendModeExample.swift:40-45 — 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 `Example/Shared/Render/RendererEffect/BlendModeExample.swift:20` 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.
MethodTooLong: Platform.updateItemView Sources/OpenSwiftUICore/Render/DisplayList/DisplayListViewPlatform.swift:378— MethodTooLong — updateItemView runs 204 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 104 over it, 2.04× 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: ORBSymbolAnimator.updateSymbolEffects Sources/OpenSwiftUICore/Render/SymbolEffect/_SymbolEffect.swift:366— MethodTooLong — updateSymbolEffects runs 150 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 50 over it, 1.50× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: DefaultSystemColorDefinition_PhoneTV.value Sources/OpenSwiftUICore/Graphic/Color/SystemColors.swift:280— MethodTooLong — value runs 148 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 48 over it, 1.48× 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: Platform.updateItemViewAsync Sources/OpenSwiftUICore/Render/DisplayList/DisplayListViewPlatform.swift:689— MethodTooLong — updateItemViewAsync runs 144 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 44 over it, 1.44× 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: _ShapeStyle_RenderedShape.renderVectorGlyph Sources/OpenSwiftUICore/Shape/ShapeStyle/ShapeStyleRendering.swift:290— MethodTooLong — renderVectorGlyph runs 135 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 35 over it, 1.35× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: Platform._makeItemView Sources/OpenSwiftUICore/Render/DisplayList/DisplayListViewPlatform.swift:1171— MethodTooLong — _makeItemView runs 122 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 22 over it, 1.22× 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: _FocusableModifier._makeView Sources/OpenSwiftUI/Event/Focus/Focusable.swift:195— MethodTooLong — _makeView runs 119 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 19 over it, 1.19× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: Style.nsAttributes Sources/OpenSwiftUICore/View/Text/AttributedString/Text+NSAttributedString.swift:273— MethodTooLong — nsAttributes runs 106 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 6 over it, 1.06× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: DynamicContainerInfo.updateValue Sources/OpenSwiftUICore/Layout/Dynamic/DynamicContainer.swift:322— MethodTooLong — updateValue runs 105 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 5 over it, 1.05× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: Timer.timeStyle Sources/OpenSwiftUICore/View/Text/FormatStyle/SystemFormatStyle+Timer.swift:579— MethodTooLong — timeStyle runs 102 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 2 over it, 1.02× 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: AppSceneDelegate.scene Sources/OpenSwiftUI/App/App/UIKit/UIKitAppDelegate.swift:172— MethodTooLong — scene 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 (10 lines × 2) Sources/OpenSwiftUI/Accessibility/AccessibilityFocusState.swift:136— Sources/OpenSwiftUI/Accessibility/AccessibilityFocusState.swift:136-145 | Sources/OpenSwiftUI/Event/Focus/FocusState.swift:208-217 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (10 lines × 2) Sources/OpenSwiftUI/View/ArchivedView/ArchivableView.swift:49— Sources/OpenSwiftUI/View/ArchivedView/ArchivableView.swift:49-58 | Sources/OpenSwiftUI/View/ArchivedView/ArchivableViewModifier.swift:67-76 — 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/OpenSwiftUI/View/ArchivedView/ArchivableView.swift:49` 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/OpenSwiftUI/View/Control/Slider/Slider.swift:338— Sources/OpenSwiftUI/View/Control/Slider/Slider.swift:338-347 | Sources/OpenSwiftUI/View/Control/Slider/SliderMark.swift:75-84 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `Sources/OpenSwiftUI/View/Control/Slider/Slider.swift:338` 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 (10 lines × 2) Sources/OpenSwiftUI/View/Control/Slider/Slider.swift:372— Sources/OpenSwiftUI/View/Control/Slider/Slider.swift:372-381 | Sources/OpenSwiftUI/View/Control/Slider/SliderMark.swift:97-106 — 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/OpenSwiftUI/View/Control/Slider/Slider.swift:372` 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 (10 lines × 2) Sources/OpenSwiftUICore/Event/Gesture/ExclusiveGesture.swift:90— Sources/OpenSwiftUICore/Event/Gesture/ExclusiveGesture.swift:90-100 | Sources/OpenSwiftUICore/Event/Gesture/SimultaneousGesture.swift:89-98 — 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/OpenSwiftUICore/Event/Gesture/ExclusiveGesture.swift:90` 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 (10 lines × 2) Sources/OpenSwiftUICore/Layout/AspectRatioLayout.swift:228— Sources/OpenSwiftUICore/Layout/AspectRatioLayout.swift:228-237 | Sources/OpenSwiftUICore/Layout/AspectRatioLayout.swift:242-251 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (10 lines × 2) Sources/OpenSwiftUICore/Layout/Edge/EdgeInsets.swift:398— Sources/OpenSwiftUICore/Layout/Edge/EdgeInsets.swift:398-407 | Sources/OpenSwiftUICore/Util/Extension/CGRect+Extension.swift:256-265 — 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/OpenSwiftUICore/Layout/Edge/EdgeInsets.swift:398` 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 (10 lines × 2) Sources/OpenSwiftUICore/Log/Signposts.swift:311— Sources/OpenSwiftUICore/Log/Signposts.swift:311-320 | Sources/OpenSwiftUICore/Log/Signposts.swift:327-337 — 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/OpenSwiftUICore/Log/Signposts.swift:327` 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 (10 lines × 2) Sources/OpenSwiftUICore/Shape/Path.swift:310— Sources/OpenSwiftUICore/Shape/Path.swift:310-319 | Sources/OpenSwiftUICore/Shape/Path.swift:335-344 — 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 (10 lines × 2) Sources/OpenSwiftUICore/Shape/ShapeStyle/ShapeStylePair.swift:38— Sources/OpenSwiftUICore/Shape/ShapeStyle/ShapeStylePair.swift:38-47 | Sources/OpenSwiftUICore/Shape/ShapeStyle/ShapeStylePair.swift:108-117 — 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/OpenSwiftUICore/Shape/ShapeStyle/ShapeStylePair.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, `Sources/OpenSwiftUICore/Shape/ShapeStyle/ShapeStylePair.swift:119` calls `_apply` and `Sources/OpenSwiftUICore/Shape/ShapeStyle/ShapeStylePair.swift:48` 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 lines × 2) Sources/OpenSwiftUICore/View/Text/FormatStyle/SafelySerializableDiscreteFormatStyle.swift:203— Sources/OpenSwiftUICore/View/Text/FormatStyle/SafelySerializableDiscreteFormatStyle.swift:203-212 | Sources/OpenSwiftUICore/View/Text/FormatStyle/SafelySerializableDiscreteFormatStyle.swift:260-269 — 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/OpenSwiftUICore/View/Text/FormatStyle/SafelySerializableDiscreteFormatStyle.swift:203` 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.
D12 · Dependency Hygiene· Dependency not covered by the committed resolution · ×7
Dependency not covered by the committed resolution: opencombine — `opencombine` is declared in Example/Tuist/Package.swift but has no entry in the committed `Package.resolved` beside it, so its version is resolved rather than pinned. Resolve the package and commit the updated `Package.resolved`.
Dependency not covered by the committed resolution: lookinside-release — `lookinside-release` is declared in Example/Tuist/Package.swift but has no entry in the committed `Package.resolved` beside it, so its version is resolved rather than pinned. Resolve the package and commit the updated `Package.resolved`.
Dependency not covered by the committed resolution: lookinserver — `lookinserver` is declared in Example/Tuist/Package.swift but has no entry in the committed `Package.resolved` beside it, so its version is resolved rather than pinned. Resolve the package and commit the updated `Package.resolved`.
Dependency not covered by the committed resolution: versioneddocc — `versioneddocc` is declared in Package.swift but has no entry in the committed `Package.resolved` beside it, so its version is resolved rather than pinned. Resolve the package and commit the updated `Package.resolved`.
Dependency not covered by the committed resolution: opencombine — `opencombine` is declared in Package.swift but has no entry in the committed `Package.resolved` beside it, so its version is resolved rather than pinned. Resolve the package and commit the updated `Package.resolved`.
Dependency not covered by the committed resolution: swift-log — `swift-log` is declared in Package.swift but has no entry in the committed `Package.resolved` beside it, so its version is resolved rather than pinned. Resolve the package and commit the updated `Package.resolved`.
Dependency not covered by the committed resolution: swift-crypto — `swift-crypto` is declared in Package.swift but has no entry in the committed `Package.resolved` beside it, so its version is resolved rather than pinned. Resolve the package and commit the updated `Package.resolved`.
Duplicated block (9 lines × 2) Sources/OpenSwiftUI/View/Control/Slider/Slider.swift:186— Sources/OpenSwiftUI/View/Control/Slider/Slider.swift:186-194 | Sources/OpenSwiftUI/View/Control/Slider/Slider.swift:227-235 — 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/OpenSwiftUI/View/Control/Slider/Slider.swift:186` 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 (9 lines × 2) Sources/OpenSwiftUI/View/Control/Slider/SliderMark.swift:21— Sources/OpenSwiftUI/View/Control/Slider/SliderMark.swift:21-29 | Sources/OpenSwiftUI/View/Control/Slider/SliderMark.swift:44-52 — 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/OpenSwiftUI/View/Control/Slider/SliderMark.swift:21` 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 (9 lines × 2) Sources/OpenSwiftUICore/Layout/Layout.swift:1315— Sources/OpenSwiftUICore/Layout/Layout.swift:1315-1323 | Sources/OpenSwiftUICore/Layout/Layout.swift:1327-1335 — 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/OpenSwiftUICore/Layout/Layout.swift:1315` 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 (9 lines × 2) Sources/OpenSwiftUICore/Shape/ContainerShape.swift:138— Sources/OpenSwiftUICore/Shape/ContainerShape.swift:138-146 | Sources/OpenSwiftUICore/Shape/ContainerShape.swift:191-199 — 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/OpenSwiftUICore/Shape/ContainerShape.swift:138` 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 (9 lines × 2) Sources/OpenSwiftUICore/View/Text/FormatStyle/SafelySerializableDiscreteFormatStyle.swift:162— Sources/OpenSwiftUICore/View/Text/FormatStyle/SafelySerializableDiscreteFormatStyle.swift:162-170 | Sources/OpenSwiftUICore/View/Text/FormatStyle/SystemFormatStyle+DateOffset.swift:463-471 — 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/OpenSwiftUICore/View/Text/FormatStyle/SafelySerializableDiscreteFormatStyle.swift:162` 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) Sources/OpenSwiftUI/App/App/AppKit/AppKitAppDelegate.swift:86— Sources/OpenSwiftUI/App/App/AppKit/AppKitAppDelegate.swift:86-94 | Sources/OpenSwiftUI/App/App/UIKit/UIKitApp.swift:64-72 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (9 lines × 2) Sources/OpenSwiftUICore/Layout/Stack/HStack.swift:69— Sources/OpenSwiftUICore/Layout/Stack/HStack.swift:69-77 | Sources/OpenSwiftUICore/Layout/Stack/VStack.swift:69-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.
Floating branch dependency: equatable — Dependency `equatable` is declared in Example/Tuist/Package.swift against branch `main` — the declaration pins no immutable point, so `swift package update` moves this dependency to whatever that branch holds at the time, which is code nobody reviewed. Pin it to a version requirement (`from:`, `.upToNextMajor(from:)`, `exact:`) or to a `revision:` commit SHA.
Floating branch dependency: opencoregraphics — Dependency `opencoregraphics` is declared in Package.swift against branch `main` — the declaration pins no immutable point, so `swift package update` moves this dependency to whatever that branch holds at the time, which is code nobody reviewed. Pin it to a version requirement (`from:`, `.upToNextMajor(from:)`, `exact:`) or to a `revision:` commit SHA.
Floating branch dependency: openattributegraph — Dependency `openattributegraph` is declared in Package.swift against branch `main` — the declaration pins no immutable point, so `swift package update` moves this dependency to whatever that branch holds at the time, which is code nobody reviewed. Pin it to a version requirement (`from:`, `.upToNextMajor(from:)`, `exact:`) or to a `revision:` commit SHA.
Floating branch dependency: openrenderbox — Dependency `openrenderbox` is declared in Package.swift against branch `main` — the declaration pins no immutable point, so `swift package update` moves this dependency to whatever that branch holds at the time, which is code nobody reviewed. Pin it to a version requirement (`from:`, `.upToNextMajor(from:)`, `exact:`) or to a `revision:` commit SHA.
Floating branch dependency: openobservation — Dependency `openobservation` is declared in Package.swift against branch `main` — the declaration pins no immutable point, so `swift package update` moves this dependency to whatever that branch holds at the time, which is code nobody reviewed. Pin it to a version requirement (`from:`, `.upToNextMajor(from:)`, `exact:`) or to a `revision:` commit SHA.
Floating branch dependency: darwinprivateframeworks — Dependency `darwinprivateframeworks` is declared in Package.swift against branch `main` — the declaration pins no immutable point, so `swift package update` moves this dependency to whatever that branch holds at the time, which is code nobody reviewed. Pin it to a version requirement (`from:`, `.upToNextMajor(from:)`, `exact:`) or to a `revision:` commit SHA.
Duplicated block (13 lines × 2) Sources/OpenSwiftUI/Integration/Graphic/UIKit/UIKitConversions.swift:257— Sources/OpenSwiftUI/Integration/Graphic/UIKit/UIKitConversions.swift:257-269 | Sources/OpenSwiftUI/Integration/Graphic/UIKit/UIKitConversions.swift:311-323 — 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/OpenSwiftUI/Integration/Graphic/UIKit/UIKitConversions.swift:257` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (13 lines × 2) Sources/OpenSwiftUICore/Data/Preference/PreferenceTransformModifier.swift:137— Sources/OpenSwiftUICore/Data/Preference/PreferenceTransformModifier.swift:137-149 | Sources/OpenSwiftUICore/Data/Preference/PreferenceWritingModifier.swift:129-141 — 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/OpenSwiftUICore/Data/Preference/PreferenceTransformModifier.swift:137` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (13 lines × 2) Sources/OpenSwiftUICore/View/DynamicViewContent/ForEach.swift:818— Sources/OpenSwiftUICore/View/DynamicViewContent/ForEach.swift:818-830 | Sources/OpenSwiftUICore/View/DynamicViewContent/ForEach.swift:861-873 — 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/OpenSwiftUICore/View/DynamicViewContent/ForEach.swift:818` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
Duplicated block (13 lines × 2) Sources/OpenSwiftUICore/View/Image/Image.swift:221— Sources/OpenSwiftUICore/View/Image/Image.swift:221-233 | Sources/OpenSwiftUICore/View/Image/Image.swift:240-252 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. The `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 (13 lines × 2) Sources/OpenSwiftUICore/View/ViewTrait.swift:54— Sources/OpenSwiftUICore/View/ViewTrait.swift:54-66 | Sources/OpenSwiftUICore/View/ViewTrait.swift:127-139 — 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/OpenSwiftUICore/View/ViewTrait.swift:54` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (13 lines × 2) Sources/OpenSwiftUI/Accessibility/AccessibilityFocusState.swift:193— Sources/OpenSwiftUI/Accessibility/AccessibilityFocusState.swift:193-205 | Sources/OpenSwiftUI/Event/Focus/FocusState.swift:247-259 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (12 lines × 2) Sources/OpenSwiftUI/Event/Responder/ContentShapeKindModifier.swift:127— Sources/OpenSwiftUI/Event/Responder/ContentShapeKindModifier.swift:127-138 | Sources/OpenSwiftUI/Event/Responder/ContentShapeModifier.swift:105-116 — 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/OpenSwiftUI/Event/Responder/ContentShapeKindModifier.swift:127` 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `Sources/OpenSwiftUI/Event/Responder/ContentShapeKindModifier.swift:124` calls `contains`, `containsGlobalPoints` and `Sources/OpenSwiftUI/Event/Responder/ContentShapeModifier.swift:104` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (12 lines × 2) Sources/OpenSwiftUI/View/Control/SensoryFeedback/UIKit/UIKitSensoryFeedbackCache.swift:83— Sources/OpenSwiftUI/View/Control/SensoryFeedback/UIKit/UIKitSensoryFeedbackCache.swift:83-94 | Sources/OpenSwiftUI/View/Control/SensoryFeedback/UIKit/UIKitSensoryFeedbackCache.swift:101-112 — 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/OpenSwiftUI/View/Control/SensoryFeedback/UIKit/UIKitSensoryFeedbackCache.swift:83` 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/OpenSwiftUICore/Event/Gesture/ExclusiveGesture.swift:77— Sources/OpenSwiftUICore/Event/Gesture/ExclusiveGesture.swift:77-88 | Sources/OpenSwiftUICore/Event/Gesture/SimultaneousGesture.swift:76-87 — 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/OpenSwiftUICore/Event/Gesture/ExclusiveGesture.swift:77` 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 (12 lines × 2) Sources/OpenSwiftUI/Integration/Representable/AppKit/NSViewControllerRepresentable.swift:445— Sources/OpenSwiftUI/Integration/Representable/AppKit/NSViewControllerRepresentable.swift:445-456 | Sources/OpenSwiftUI/Integration/Representable/AppKit/NSViewRepresentable.swift:490-501 — before extracting anything, compare `Sources/OpenSwiftUI/Integration/Representable/AppKit/NSViewControllerRepresentable.swift` and `Sources/OpenSwiftUI/Integration/Representable/AppKit/NSViewRepresentable.swift` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 42 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (12 lines × 2) Sources/OpenSwiftUICore/Layout/Stack/HStack.swift:56— Sources/OpenSwiftUICore/Layout/Stack/HStack.swift:56-67 | Sources/OpenSwiftUICore/Layout/Stack/VStack.swift:56-67 — 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.
Hotspot: Sources/OpenSwiftUI/Integration/Hosting/UIKit/View/UIHostingView.swift Sources/OpenSwiftUI/Integration/Hosting/UIKit/View/UIHostingView.swift:481— Sources/OpenSwiftUI/Integration/Hosting/UIKit/View/UIHostingView.swift changed 12 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 19 in _UIHostingView._hitTest at line 481. 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-07-31..2026-10-29, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-31 00:37:40 +08:00' --until='2026-10-29 00:37:40 +08:00' --full-history --no-merges -- Sources/OpenSwiftUI/Integration/Hosting/UIKit/View/UIHostingView.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/OpenSwiftUICore/Shape/Path.swift Sources/OpenSwiftUICore/Shape/Path.swift:987— Sources/OpenSwiftUICore/Shape/Path.swift changed 6 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 24 in Path.mapPoints at line 987. 2 of those changes were fix/bug commits, and the other 4 changed it for other reasons — this file is under both repair and feature pressure. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-07-31..2026-10-29, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-31 00:37:40 +08:00' --until='2026-10-29 00:37:40 +08:00' --full-history --no-merges -- Sources/OpenSwiftUICore/Shape/Path.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/OpenSwiftUICore/Shape/ShapeLayer.swift Sources/OpenSwiftUICore/Shape/ShapeLayer.swift:586— Sources/OpenSwiftUICore/Shape/ShapeLayer.swift changed 4 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 19 in ShapeLayerAsyncHelper.visitPaint at line 586. 2 of those changes were fix/bug commits, and the other 2 changed it for other reasons — this file is under both repair and feature pressure. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-07-31..2026-10-29, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-31 00:37:40 +08:00' --until='2026-10-29 00:37:40 +08:00' --full-history --no-merges -- Sources/OpenSwiftUICore/Shape/ShapeLayer.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/OpenSwiftUI/Accessibility/AccessibilityFocus.swift Sources/OpenSwiftUI/Accessibility/AccessibilityFocus.swift:58— Sources/OpenSwiftUI/Accessibility/AccessibilityFocus.swift changed 2 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 18 in Target.match at line 58. 1 of those changes was a fix/bug commit, and the other 1 changed it for other reasons — this file is under both repair and feature pressure. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-07-31..2026-10-29, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-31 00:37:40 +08:00' --until='2026-10-29 00:37:40 +08:00' --full-history --no-merges -- Sources/OpenSwiftUI/Accessibility/AccessibilityFocus.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.
ClassTooLong: ForEachState Sources/OpenSwiftUICore/View/DynamicViewContent/ForEach.swift:311— ClassTooLong — 836 significant lines (blank, comment-only and punctuation-only lines excluded), 17 methods. The bar is 400 significant lines; this is 436 over it, 2.09× 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: NSHostingView Sources/OpenSwiftUI/Integration/Hosting/AppKit/View/NSHostingView.swift:32— ClassTooLong — 656 significant lines (blank, comment-only and punctuation-only lines excluded), 82 methods. The bar is 400 significant lines; this is 256 over it, 1.64× 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: LocalizedStringKey Sources/OpenSwiftUICore/View/Text/Localized/Text+Localized.swift:181— ClassTooLong — 457 significant lines (blank, comment-only and punctuation-only lines excluded), 11 methods. The bar is 400 significant lines; this is 57 over it, 1.14× 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: PlatformViewHost Sources/OpenSwiftUI/Integration/Representable/Platform/PlatformViewHost.swift:25— ClassTooLong — 420 significant lines (blank, comment-only and punctuation-only lines excluded), 35 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.
Duplicated block (19 lines × 2) Sources/OpenSwiftUI/App/Commands/TupleCommandContent.swift:42— Sources/OpenSwiftUI/App/Commands/TupleCommandContent.swift:42-60 | Sources/OpenSwiftUI/App/Scene/TupleScene.swift:58-76 — 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/OpenSwiftUI/App/Commands/TupleCommandContent.swift:42` 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. Note first that the copies are not typed on the same thing: the declarations holding them bind `inputs` to `_CommandsInputs` in one and `_SceneInputs` in another, and the duplicated lines use it. The extracted unit therefore needs a parameter type that fits BOTH — their common supertype where they have one, or a new abstraction over them where they do not — and settling that is the step that comes BEFORE the extraction above. Where the two types are deliberately unrelated, the duplication is the price of that separation and the honest resolution is to record the decision rather than to extract.
Duplicated block (19 lines × 2) Sources/OpenSwiftUICore/View/Text/FormatStyle/SystemFormatStyle+DateOffset.swift:321— Sources/OpenSwiftUICore/View/Text/FormatStyle/SystemFormatStyle+DateOffset.swift:321-339 | Sources/OpenSwiftUICore/View/Text/FormatStyle/SystemFormatStyle+DateReference.swift:192-210 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (19 lines × 2) Sources/OpenSwiftUICore/View/Text/Text/Text+View.swift:1375— Sources/OpenSwiftUICore/View/Text/Text/Text+View.swift:1375-1393 | Sources/OpenSwiftUICore/View/Text/Text/Text+View.swift:1616-1634 — 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/OpenSwiftUICore/View/Text/Text/Text+View.swift:1375` 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 (19 lines × 2) Example/Project.swift:283— Example/Project.swift:283-301 | Example/Project.swift:319-337 — 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 `Example/Project.swift:283` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (15 lines × 2) Sources/OpenSwiftUICore/Animation/Animatable/AnimatableAttribute.swift:70— Sources/OpenSwiftUICore/Animation/Animatable/AnimatableAttribute.swift:70-84 | Sources/OpenSwiftUICore/Animation/Animatable/AnimatableAttribute.swift:144-158 — 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/OpenSwiftUICore/Animation/Animatable/AnimatableAttribute.swift:70` 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/OpenSwiftUICore/Animation/Animatable/AnimatableAttribute.swift:159` calls `FrameVelocityFilter` and `Sources/OpenSwiftUICore/Animation/Animatable/AnimatableAttribute.swift:85` does not — after which the two agree again for 4 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (15 lines × 2) Sources/OpenSwiftUICore/Data/Binding/Binding.swift:151— Sources/OpenSwiftUICore/Data/Binding/Binding.swift:151-165 | Sources/OpenSwiftUICore/Data/Binding/Binding.swift:227-241 — 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/OpenSwiftUICore/Data/Binding/Binding.swift:151` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (15 lines × 2) Sources/OpenSwiftUICore/Layout/Modifier/FrameLayout.swift:212— Sources/OpenSwiftUICore/Layout/Modifier/FrameLayout.swift:212-226 | Sources/OpenSwiftUICore/Layout/Modifier/FrameLayout.swift:227-241 — 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 (15 lines × 2) Sources/OpenSwiftUICore/View/Text/Localized/Text+Localized.swift:491— Sources/OpenSwiftUICore/View/Text/Localized/Text+Localized.swift:491-505 | Sources/OpenSwiftUICore/View/Text/Localized/Text+Localized.swift:526-540 — 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/OpenSwiftUICore/View/Text/Localized/Text+Localized.swift:491` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
D4 · Code Duplication· Members sharing a duplicated core (4 members, 50+ identical tokens) · ×3
Members sharing a duplicated core (4 members, 50+ identical tokens) Sources/OpenSwiftUI/App/Commands/Commands.swift:97— Sources/OpenSwiftUI/App/Commands/Commands.swift:97-108 | Sources/OpenSwiftUI/App/Scene/Scene.swift:147-158 | Sources/OpenSwiftUICore/Modifier/CustomViewModifier.swift:164-175 | Sources/OpenSwiftUICore/View/CustomView.swift:50-61 — These 4 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 4 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 4 times.
Members sharing a duplicated core (4 members, 50+ identical tokens) Sources/OpenSwiftUICore/Layout/Edge/EdgeInsets.swift:396— Sources/OpenSwiftUICore/Layout/Edge/EdgeInsets.swift:396-407 | Sources/OpenSwiftUICore/Layout/Geometry/ProjectionTransform.swift:202-214 | Sources/OpenSwiftUICore/Util/Extension/CGAffineTransform+Extension.swift:50-62 | Sources/OpenSwiftUICore/Util/Extension/CGRect+Extension.swift:254-265 — These 4 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 4 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 4 times.
Members sharing a duplicated core (4 members, 50+ identical tokens) Sources/OpenSwiftUICore/Layout/Edge/EdgeInsets.swift:409— Sources/OpenSwiftUICore/Layout/Edge/EdgeInsets.swift:409-423 | Sources/OpenSwiftUICore/Layout/Geometry/ProjectionTransform.swift:216-230 | Sources/OpenSwiftUICore/Util/Extension/CGAffineTransform+Extension.swift:64-78 | Sources/OpenSwiftUICore/Util/Extension/CGRect+Extension.swift:267-281 — These 4 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 4 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 4 times.
Duplicated block (18 lines × 2) Sources/OpenSwiftUI/View/Control/ProgressView/ArchivableProgressView.swift:95— Sources/OpenSwiftUI/View/Control/ProgressView/ArchivableProgressView.swift:95-112 | Sources/OpenSwiftUI/View/Control/ProgressView/UIKitProgressView.swift:20-37 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (18 lines × 2) Sources/OpenSwiftUICore/Animation/Animation/CustomAnimationModifier.swift:102— Sources/OpenSwiftUICore/Animation/Animation/CustomAnimationModifier.swift:102-119 | Sources/OpenSwiftUICore/Animation/Animation/CustomAnimationModifier.swift:186-203 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Note first that the copies are not typed on the same thing: the declarations holding them bind `base` to `Animation.Function` in one and `Base` in another, and the duplicated lines use it. The extracted unit therefore needs a parameter type that fits BOTH — their common supertype where they have one, or a new abstraction over them where they do not — and settling that is the step that comes BEFORE the extraction above. Where the two types are deliberately unrelated, the duplication is the price of that separation and the honest resolution is to record the decision rather than to extract.
Duplicated block (18 lines × 2) Sources/OpenSwiftUICore/Layout/Layout.swift:707— Sources/OpenSwiftUICore/Layout/Layout.swift:707-724 | Sources/OpenSwiftUICore/Layout/Layout.swift:728-745 — 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/OpenSwiftUICore/Layout/Layout.swift:707` 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 (14 lines × 2) Sources/OpenSwiftUI/App/Scene/SceneBridge.swift:693— Sources/OpenSwiftUI/App/Scene/SceneBridge.swift:693-706 | Sources/OpenSwiftUI/App/Scene/SceneBridge.swift:718-731 — 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/OpenSwiftUI/App/Scene/SceneBridge.swift:693` 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 (14 lines × 2) Sources/OpenSwiftUICore/Layout/Modifier/FrameLayout.swift:306— Sources/OpenSwiftUICore/Layout/Modifier/FrameLayout.swift:306-319 | Sources/OpenSwiftUICore/Layout/Modifier/FrameLayout.swift:320-333 — 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 (14 lines × 2) Sources/OpenSwiftUICore/Render/DisplayList/DisplayListViewPlatform.swift:1477— Sources/OpenSwiftUICore/Render/DisplayList/DisplayListViewPlatform.swift:1477-1490 | Sources/OpenSwiftUICore/Render/DisplayList/DisplayListViewPlatform.swift:1491-1504 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (8 lines × 3) Sources/OpenSwiftUICore/Graphic/Gradient/GradientStyle.swift:482— Sources/OpenSwiftUICore/Graphic/Gradient/GradientStyle.swift:482-489 | Sources/OpenSwiftUICore/Graphic/Gradient/GradientStyle.swift:590-597 | Sources/OpenSwiftUICore/Graphic/Gradient/GradientStyle.swift:891-898 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
Duplicated block (8 lines × 3) Sources/OpenSwiftUI/Integration/Representable/AppKit/NSViewControllerRepresentable.swift:383— Sources/OpenSwiftUI/Integration/Representable/AppKit/NSViewControllerRepresentable.swift:383-390 | Sources/OpenSwiftUI/Integration/Representable/AppKit/NSViewRepresentable.swift:427-434 | Sources/OpenSwiftUI/Integration/Representable/UIKit/UIViewRepresentable.swift:385-392 — before extracting anything, compare `Sources/OpenSwiftUI/Integration/Representable/AppKit/NSViewControllerRepresentable.swift` and `Sources/OpenSwiftUI/Integration/Representable/AppKit/NSViewRepresentable.swift` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 42 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (8 lines × 3) Sources/OpenSwiftUI/Integration/Representable/AppKit/NSViewControllerRepresentable.swift:244— Sources/OpenSwiftUI/Integration/Representable/AppKit/NSViewControllerRepresentable.swift:244-251 | Sources/OpenSwiftUI/Integration/Representable/AppKit/NSViewRepresentable.swift:261-268 | Sources/OpenSwiftUI/Integration/Representable/UIKit/UIViewRepresentable.swift:246-253 — before extracting anything, compare `Sources/OpenSwiftUI/Integration/Representable/AppKit/NSViewControllerRepresentable.swift` and `Sources/OpenSwiftUI/Integration/Representable/AppKit/NSViewRepresentable.swift` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 42 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (6 lines × 3) Sources/OpenSwiftUICore/Render/SymbolEffect/_SymbolEffect.swift:793— Sources/OpenSwiftUICore/Render/SymbolEffect/_SymbolEffect.swift:793-798 | Sources/OpenSwiftUICore/Render/SymbolEffect/_SymbolEffect.swift:849-854 | Sources/OpenSwiftUICore/Render/SymbolEffect/_SymbolEffect.swift:954-959 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `Sources/OpenSwiftUICore/Render/SymbolEffect/_SymbolEffect.swift:793` 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/OpenSwiftUICore/Render/SymbolEffect/_SymbolEffect.swift:951` calls `floatField` and `Sources/OpenSwiftUICore/Render/SymbolEffect/_SymbolEffect.swift:790` 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 (6 lines × 3) Sources/OpenSwiftUI/Accessibility/AccessibilityConfiguration.swift:72— Sources/OpenSwiftUI/Accessibility/AccessibilityConfiguration.swift:72-77 | Sources/OpenSwiftUI/Accessibility/AccessibilityConfiguration.swift:133-138 | Sources/OpenSwiftUI/Accessibility/AccessibilityViewModifier.swift:835-840 — there are 3 copies across 2 file(s) — more copies than files, so at least one file holds the block twice. Extract it once into a single shared function every call site can reach and call it from all 3 sites; resolving a subset leaves the remainder to drift apart.
Duplicated block (6 lines × 3) Sources/OpenSwiftUICore/Modifier/ViewModifier/BackgroundModifier.swift:216— Sources/OpenSwiftUICore/Modifier/ViewModifier/BackgroundModifier.swift:216-221 | Sources/OpenSwiftUICore/Modifier/ViewModifier/BackgroundModifier.swift:328-333 | Sources/OpenSwiftUICore/Modifier/ViewModifier/OverlayModifier.swift:142-147 — there are 3 copies across 2 file(s) — more copies than files, so at least one file holds the block twice. Extract it once into a single shared function every call site can reach and call it from all 3 sites; resolving a subset leaves the remainder to drift apart.
Duplicated block (7 lines × 4) Sources/OpenSwiftUI/View/Container/TraitValues.swift:79— Sources/OpenSwiftUI/View/Container/TraitValues.swift:79-85 | Sources/OpenSwiftUICore/Modifier/ViewModifier.swift:309-315 | Sources/OpenSwiftUICore/View/Container/ContainerValueWritingModifier.swift:135-141 | Sources/OpenSwiftUICore/View/ViewTrait.swift:184-190 — before extracting anything, compare `Sources/OpenSwiftUI/View/Container/TraitValues.swift` and `Sources/OpenSwiftUICore/View/Container/ContainerValueWritingModifier.swift` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 31 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (7 lines × 4) Sources/OpenSwiftUI/View/Control/Slider/SystemSliderStyle_Mac.swift:128— Sources/OpenSwiftUI/View/Control/Slider/SystemSliderStyle_Mac.swift:128-134 | Sources/OpenSwiftUI/View/Control/Stepper/ArrowStepperStyle.swift:67-73 | Sources/OpenSwiftUI/View/Text/Text+Selection_macOS.swift:172-178 | Sources/OpenSwiftUI/View/Toggle/SwitchToggleStyle.swift:224-230 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 4 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 4 times.
Duplicated block (7 lines × 4) Sources/OpenSwiftUI/View/ArchivedView/ArchivableViewModifier.swift:32— Sources/OpenSwiftUI/View/ArchivedView/ArchivableViewModifier.swift:32-38 | Sources/OpenSwiftUICore/Layout/LayoutView.swift:46-52 | Sources/OpenSwiftUICore/Modifier/CustomViewModifier.swift:97-103 | Sources/OpenSwiftUICore/Render/GeometryEffect/GeometryEffect.swift:39-45 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 4 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 4 times. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `Sources/OpenSwiftUICore/Render/GeometryEffect/GeometryEffect.swift:37` calls `available` and `Sources/OpenSwiftUICore/Layout/LayoutView.swift:44` 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.
Timer.discreteInput (cyclomatic 16) Sources/OpenSwiftUICore/View/Text/FormatStyle/SystemFormatStyle+Timer.swift:992— Timer.discreteInput has cyclomatic complexity 16 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top. This shape REPEATS in the file: one other method here (Timer.discreteInput) has the same decision points, in the same order, at the same nesting depths — so this is one pattern written twice rather than two separate problems. Splitting this body alone leaves the other exactly as it is. Where these are variations on one operation, the change that clears both is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
Timer.discreteInput (cyclomatic 16) Sources/OpenSwiftUICore/View/Text/FormatStyle/SystemFormatStyle+Timer.swift:1034— Timer.discreteInput has cyclomatic complexity 16 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top. This shape REPEATS in the file: one other method here (Timer.discreteInput) has the same decision points, in the same order, at the same nesting depths — so this is one pattern written twice rather than two separate problems. Splitting this body alone leaves the other exactly as it is. Where these are variations on one operation, the change that clears both is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
Timer.discreteInput (cognitive 19) Sources/OpenSwiftUICore/View/Text/FormatStyle/SystemFormatStyle+Timer.swift:992— Timer.discreteInput has cognitive complexity 19 (threshold 15). Drivers by points: if/else 7 (12 pts), boolean chains 4, match/switch 2 (3 pts) (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body. This shape REPEATS in the file: one other method here (Timer.discreteInput) has the same decision points, in the same order, at the same nesting depths — so this is one pattern written twice rather than two separate problems. Splitting this body alone leaves the other exactly as it is. Where these are variations on one operation, the change that clears both is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
Timer.discreteInput (cognitive 19) Sources/OpenSwiftUICore/View/Text/FormatStyle/SystemFormatStyle+Timer.swift:1034— Timer.discreteInput has cognitive complexity 19 (threshold 15). Drivers by points: if/else 7 (12 pts), boolean chains 4, match/switch 2 (3 pts) (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body. This shape REPEATS in the file: one other method here (Timer.discreteInput) has the same decision points, in the same order, at the same nesting depths — so this is one pattern written twice rather than two separate problems. Splitting this body alone leaves the other exactly as it is. Where these are variations on one operation, the change that clears both is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
Change coupling: AppKitDisplayList.swift ↔ UIKitDisplayList.swift Sources/OpenSwiftUI/Render/DisplayList/AppKitDisplayList.swift:1— `Sources/OpenSwiftUI/Render/DisplayList/AppKitDisplayList.swift` and `Sources/OpenSwiftUI/Render/DisplayList/UIKitDisplayList.swift` change together 64% of the time (7 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 7 shared commits counted here, the most recent 3 are `899460fa` Enable OSUI ViewRenderer by default (#872); `410618c0` [NFC] Use RB for properties and function and ORB for type (#821); `9e06f2da` Update to use ORB instead of RB (#820) — run `git show` on any of them.
Change coupling: CustomViewModifier.swift ↔ CustomView.swift Sources/OpenSwiftUICore/Modifier/CustomViewModifier.swift:1— `Sources/OpenSwiftUICore/Modifier/CustomViewModifier.swift` and `Sources/OpenSwiftUICore/View/CustomView.swift` change together 50% of the time (5 of the 10 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets). They sit in different directories, but in this ecosystem the namespace is declared in the FILE, not by the folder — so the two may well share one namespace and reference each other with no import for this pass to see. Read the pair before acting: if one derives from or overrides the other, the dependency is explicit in the type declaration and the co-change is definitional; if one registers itself into the other through a hook or an initialiser, the missing dependency is DELIBERATE and the thing to add is a comment saying so; if they simply belong together, co-locate them; if none of these holds, the coupling is hidden and worth breaking. You can check this without leaving the row: of the 5 shared commits counted here, the most recent 3 are `fe4aca66` [NFC] Optimize logging code (#650); `ba1069a3` Implement EnvironmentalModifier (#493); `65459f2c` Update VariadicView — run `git show` on any of them.
Duplicated block (29 lines × 2) Sources/OpenSwiftUI/App/App/AppKit/AppWindowsController.swift:159— Sources/OpenSwiftUI/App/App/AppKit/AppWindowsController.swift:159-187 | Sources/OpenSwiftUI/App/App/UIKit/UIKitAppDelegate.swift:685-713 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (29 lines × 2) Sources/OpenSwiftUICore/Graphic/Color/SystemColors.swift:363— Sources/OpenSwiftUICore/Graphic/Color/SystemColors.swift:363-391 | Sources/OpenSwiftUICore/Graphic/Color/SystemColors.swift:478-506 — 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/OpenSwiftUICore/Graphic/Color/SystemColors.swift:363` 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 (13–17 lines × 2) Sources/OpenSwiftUICore/View/Archive/ConditionallyArchivableView.swift:25— Sources/OpenSwiftUICore/View/Archive/ConditionallyArchivableView.swift:25-41 | Sources/OpenSwiftUICore/View/ConditionalGraphicsView.swift:64-76 — before extracting anything, compare `Sources/OpenSwiftUICore/View/Archive/ConditionallyArchivableView.swift` and `Sources/OpenSwiftUICore/View/ConditionalGraphicsView.swift` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 47 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `Sources/OpenSwiftUICore/View/Archive/ConditionallyArchivableView.swift:23` calls `available` and `Sources/OpenSwiftUICore/View/ConditionalGraphicsView.swift:62` 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–17 lines × 2) Sources/OpenSwiftUICore/View/Archive/ConditionallyArchivableView.swift:43— Sources/OpenSwiftUICore/View/Archive/ConditionallyArchivableView.swift:43-59 | Sources/OpenSwiftUICore/View/ConditionalGraphicsView.swift:78-90 — before extracting anything, compare `Sources/OpenSwiftUICore/View/Archive/ConditionallyArchivableView.swift` and `Sources/OpenSwiftUICore/View/ConditionalGraphicsView.swift` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 47 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (14 lines × 3) Sources/OpenSwiftUI/Event/Gesture/LayoutGestureModifier.swift:50— Sources/OpenSwiftUI/Event/Gesture/LayoutGestureModifier.swift:50-63 | Sources/OpenSwiftUICore/Event/Gesture/GestureViewModifier.swift:179-192 | Sources/OpenSwiftUICore/Event/Responder/DefaultLayoutViewResponder.swift:65-78 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 3 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 3 times. Read the line range as the matched WINDOW rather than a finished unit: at `Sources/OpenSwiftUI/Event/Gesture/LayoutGestureModifier.swift:50` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (14 lines × 3) Sources/OpenSwiftUICore/Data/Protobuf/ProtobufDecoder.swift:109— Sources/OpenSwiftUICore/Data/Protobuf/ProtobufDecoder.swift:109-122 | Sources/OpenSwiftUICore/Data/Protobuf/ProtobufDecoder.swift:171-184 | Sources/OpenSwiftUICore/Data/Protobuf/ProtobufDecoder.swift:193-206 — 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. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (8–11 lines × 2) Sources/OpenSwiftUICore/View/ConditionalContent.swift:58— Sources/OpenSwiftUICore/View/ConditionalContent.swift:58-65 | Sources/OpenSwiftUICore/View/OptionalView.swift:16-26 — 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–11 lines × 2) Example/Shared/Render/GeometryEffect/MatchedGeometryEffectExample.swift:35— Example/Shared/Render/GeometryEffect/MatchedGeometryEffectExample.swift:35-42 | Example/Shared/Render/GeometryEffect/MatchedGeometryEffectExample.swift:72-82 — 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 `Example/Shared/Render/GeometryEffect/MatchedGeometryEffectExample.swift:35` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (9 lines × 4) Sources/OpenSwiftUI/App/Commands/Commands.swift:97— Sources/OpenSwiftUI/App/Commands/Commands.swift:97-105 | Sources/OpenSwiftUI/App/Scene/Scene.swift:147-155 | Sources/OpenSwiftUICore/Modifier/CustomViewModifier.swift:164-172 | Sources/OpenSwiftUICore/View/CustomView.swift:50-58 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 4 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 4 times. Read the line range as the matched WINDOW rather than a finished unit: at `Sources/OpenSwiftUI/App/Commands/Commands.swift:97` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (9 lines × 4) Sources/OpenSwiftUI/Render/SymbolEffect/SymbolEffect.swift:637— Sources/OpenSwiftUI/Render/SymbolEffect/SymbolEffect.swift:637-645 | Sources/OpenSwiftUI/Render/SymbolEffect/SymbolEffectAPI.swift:117-125 | Sources/OpenSwiftUI/Render/SymbolEffect/SymbolEffectAPI.swift:173-181 | Sources/OpenSwiftUI/Render/SymbolEffect/SymbolEffectAPI.swift:232-240 — there are 4 copies across 2 file(s) — more copies than files, so at least one file holds the block twice. Extract it once into a single shared function every call site can reach and call it from all 4 sites; resolving a subset leaves the remainder to drift apart.
Duplicated block (6 lines × 4) Sources/OpenSwiftUI/Integration/Representable/AppKit/NSViewControllerRepresentable.swift:215— Sources/OpenSwiftUI/Integration/Representable/AppKit/NSViewControllerRepresentable.swift:215-220 | Sources/OpenSwiftUI/Integration/Representable/AppKit/NSViewRepresentable.swift:248-253 | Sources/OpenSwiftUI/Integration/Representable/UIKit/UIViewControllerRepresentable.swift:231-236 | Sources/OpenSwiftUI/Integration/Representable/UIKit/UIViewRepresentable.swift:233-238 — before extracting anything, compare `Sources/OpenSwiftUI/Integration/Representable/AppKit/NSViewControllerRepresentable.swift` and `Sources/OpenSwiftUI/Integration/Representable/AppKit/NSViewRepresentable.swift` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 42 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (6 lines × 4) Sources/OpenSwiftUICore/Event/Event/HitTestableEvent.swift:42— Sources/OpenSwiftUICore/Event/Event/HitTestableEvent.swift:42-47 | Sources/OpenSwiftUICore/Event/Event/PanEvent.swift:75-80 | Sources/OpenSwiftUICore/Event/Event/SpatialEvent.swift:60-65 | Sources/OpenSwiftUICore/Event/Event/TappableEvent.swift:35-40 — 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 4 call sites, so a change lands once.
DefaultSystemColorDefinition_PhoneTV.value (cyclomatic 88) Sources/OpenSwiftUICore/Graphic/Color/SystemColors.swift:280— DefaultSystemColorDefinition_PhoneTV.value has cyclomatic complexity 88 (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.
CustomRecursiveStringConvertible.swift.colorNameForColorComponents (cyclomatic 66) Sources/OpenSwiftUICore/Util/CustomRecursiveStringConvertible.swift:239— CustomRecursiveStringConvertible.swift.colorNameForColorComponents has cyclomatic complexity 66 (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.
Platform.updateItemView (cyclomatic 54) Sources/OpenSwiftUICore/Render/DisplayList/DisplayListViewPlatform.swift:378— Platform.updateItemView has cyclomatic complexity 54 (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.
Item.canonicalize (cyclomatic 47) Sources/OpenSwiftUICore/Render/DisplayList/DisplayList.swift:741— Item.canonicalize has cyclomatic complexity 47 (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.
ORBSymbolAnimator.updateSymbolEffects (cyclomatic 45) Sources/OpenSwiftUICore/Render/SymbolEffect/_SymbolEffect.swift:366— ORBSymbolAnimator.updateSymbolEffects has cyclomatic complexity 45 (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.
_ShapeStyle_RenderedShape.renderVectorGlyph (cyclomatic 40) Sources/OpenSwiftUICore/Shape/ShapeStyle/ShapeStyleRendering.swift:290— _ShapeStyle_RenderedShape.renderVectorGlyph has cyclomatic complexity 40 (threshold 15). Of this number, 35 points are the body's own statements and 5 belong to one function item inside it that branches. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
Effect.print (cyclomatic 36) Sources/OpenSwiftUICore/Render/DisplayList/DisplayListPrinter.swift:212— Effect.print has cyclomatic complexity 36 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
DynamicContainerInfo.updateValue (cyclomatic 33) Sources/OpenSwiftUICore/Layout/Dynamic/DynamicContainer.swift:322— DynamicContainerInfo.updateValue has cyclomatic complexity 33 (threshold 15). Of this number, 32 points are the body's own statements and 1 belongs to one function item inside it that branches. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
AccessibilityProperties.merge (cyclomatic 32) Sources/OpenSwiftUI/Accessibility/AccessibilityProperties.swift:14— AccessibilityProperties.merge has cyclomatic complexity 32 (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.
PropertiesTransform.updateValue (cyclomatic 30) Sources/OpenSwiftUI/Accessibility/AccessibilityViewModifier.swift:625— PropertiesTransform.updateValue has cyclomatic complexity 30 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
Style.nsAttributes (cyclomatic 30) Sources/OpenSwiftUICore/View/Text/AttributedString/Text+NSAttributedString.swift:273— Style.nsAttributes has cyclomatic complexity 30 (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.
Dictionary.transferAttributedStringStyles (cyclomatic 30) Sources/OpenSwiftUICore/View/Text/AttributedString/Text+AttributedString.swift:683— Dictionary.transferAttributedStringStyles has cyclomatic complexity 30 (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.
Timer.timeStyle (cyclomatic 30) Sources/OpenSwiftUICore/View/Text/FormatStyle/SystemFormatStyle+Timer.swift:579— Timer.timeStyle has cyclomatic complexity 30 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
Timer.unitsStyle (cyclomatic 30) Sources/OpenSwiftUICore/View/Text/FormatStyle/SystemFormatStyle+Timer.swift:707— Timer.unitsStyle 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.
SystemVibrantColorStyle.apply (cyclomatic 29) Sources/OpenSwiftUICore/Graphic/Color/VibrantColorStyle.swift:25— SystemVibrantColorStyle.apply 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.
FocusBridge.moveFocus (cyclomatic 28) Sources/OpenSwiftUI/Event/Focus/FocusBridge.swift:112— FocusBridge.moveFocus 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.
ResolvedBorderedButton.materialBackgroundSpec (cyclomatic 28) Sources/OpenSwiftUI/View/Control/Button/BorderedButtonStyle_Phone.swift:214— ResolvedBorderedButton.materialBackgroundSpec 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.
CUICatalog.findAsset (cyclomatic 28) Sources/OpenSwiftUICore/Graphic/Color/NamedColor.swift:154— CUICatalog.findAsset has cyclomatic complexity 28 (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.
GradientLayer.clippedValues (cyclomatic 28) Sources/OpenSwiftUICore/Graphic/Gradient/GradientLayer.swift:62— GradientLayer.clippedValues has cyclomatic complexity 28 (threshold 15). Of this number, 26 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.
ViewTransform.convert (cyclomatic 28) Sources/OpenSwiftUICore/Layout/View/ViewTransform.swift:329— ViewTransform.convert 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.
AppSceneDelegate.scene (cyclomatic 27) Sources/OpenSwiftUI/App/App/UIKit/UIKitAppDelegate.swift:172— AppSceneDelegate.scene has cyclomatic complexity 27 (threshold 15). Of this number, 26 points are the body's own statements and 1 belongs to one function item inside it that branches. To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
ImageResolutionContext.willUpdateVectorGlyph (cyclomatic 27) Sources/OpenSwiftUICore/View/Image/Image.swift:154— ImageResolutionContext.willUpdateVectorGlyph has cyclomatic complexity 27 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
DynamicContainerInfo.updateItems (cyclomatic 26) Sources/OpenSwiftUICore/Layout/Dynamic/DynamicContainer.swift:523— DynamicContainerInfo.updateItems 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.
SharedFrame.updateValue (cyclomatic 26) Sources/OpenSwiftUICore/Render/GeometryEffect/MatchedGeometryEffect.swift:607— SharedFrame.updateValue 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.
FocusNavigationSequence.next (cyclomatic 25) Sources/OpenSwiftUI/Event/Focus/FocusNavigator.swift:141— FocusNavigationSequence.next has cyclomatic complexity 25 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
Platform.updateGeometry (cyclomatic 25) Sources/OpenSwiftUICore/Render/DisplayList/DisplayListViewPlatform.swift:1608— Platform.updateGeometry has cyclomatic complexity 25 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
MultiEventListenerPhase.updateValue (cyclomatic 25) Sources/OpenSwiftUI/Event/Gesture/MultiEventListener.swift:70— MultiEventListenerPhase.updateValue has cyclomatic complexity 25 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
ForEachState.update (cyclomatic 25) Sources/OpenSwiftUICore/View/DynamicViewContent/ForEach.swift:342— ForEachState.update has cyclomatic complexity 25 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
Platform.updateItemViewAsync (cyclomatic 24) Sources/OpenSwiftUICore/Render/DisplayList/DisplayListViewPlatform.swift:689— Platform.updateItemViewAsync has cyclomatic complexity 24 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
Path.mapPoints (cyclomatic 24) Sources/OpenSwiftUICore/Shape/Path.swift:987— Path.mapPoints has cyclomatic complexity 24 (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.
EventListenerPhase.updateValue (cyclomatic 24) Sources/OpenSwiftUICore/Event/Gesture/EventListener.swift:99— EventListenerPhase.updateValue has cyclomatic complexity 24 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
AccessibilityChildBehavior.defaultCombine (cyclomatic 23) Sources/OpenSwiftUI/Accessibility/AccessibilityChildBehavior.swift:130— AccessibilityChildBehavior.defaultCombine has cyclomatic complexity 23 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
FocusBridge.preferredFocusItems (cyclomatic 22) Sources/OpenSwiftUI/Event/Focus/UIKitHostContainerFocusItemInput.swift:498— FocusBridge.preferredFocusItems 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.
UpdateViewFocusItem.updateValue (cyclomatic 21) Sources/OpenSwiftUI/Event/Focus/Focusable.swift:1018— UpdateViewFocusItem.updateValue 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.
RawPanGesture.update (cyclomatic 21) Sources/OpenSwiftUI/Event/Gesture/PanGesture.swift:108— RawPanGesture.update 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.
PlatformViewHost._layoutSizeThatFits (cyclomatic 21) Sources/OpenSwiftUI/Integration/Representable/Platform/PlatformViewHost.swift:467— PlatformViewHost._layoutSizeThatFits 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.
ResolvedBorderedButton.opaqueBackgroundSpec (cyclomatic 21) Sources/OpenSwiftUI/View/Control/Button/BorderedButtonStyle_Phone.swift:293— ResolvedBorderedButton.opaqueBackgroundSpec 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.
EventBindingManager.sendDownstream (cyclomatic 21) Sources/OpenSwiftUICore/Event/Event/EventBindingManager.swift:50— EventBindingManager.sendDownstream 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.
ImageLayer.update (cyclomatic 21) Sources/OpenSwiftUICore/View/Image/ImageLayer.swift:40— ImageLayer.update has cyclomatic complexity 21 (threshold 15). To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Where every arm is uniform — the same kind of value, with no behaviour of its own — a table keyed by the case is the shorter form; wherever the arms carry different data or different behaviour, keep them as cases, because collapsing those trades an explicit, reviewable set of cases for nothing.
BitmapKey.loadBitmapInfo (cyclomatic 21) Sources/OpenSwiftUICore/View/Image/NamedImage.swift:306— BitmapKey.loadBitmapInfo 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.
ChangedBodyProperty.swift.changedBodyProperties (cyclomatic 21) Sources/OpenSwiftUICore/Data/DynamicProperty/ChangedBodyProperty.swift:13— ChangedBodyProperty.swift.changedBodyProperties has cyclomatic complexity 21 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function so the top-level body reads as a short sequence of named decisions.
LayoutScrollableTransform.updateValue (cyclomatic 20) Sources/OpenSwiftUI/Accessibility/AccessibilityScrolling.swift:83— LayoutScrollableTransform.updateValue 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.
PlatformAccessibilityElementProtocol._bridgedProperties (cyclomatic 20) Sources/OpenSwiftUI/Accessibility/Platform/AppKitAccessibility.swift:637— PlatformAccessibilityElementProtocol._bridgedProperties 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.
SafeAreaInsets.adjust (cyclomatic 20) Sources/OpenSwiftUICore/Layout/SafeAreaInsets.swift:93— SafeAreaInsets.adjust 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.
_ColorMatrix.init (cyclomatic 20) Sources/OpenSwiftUICore/Graphic/Color/ColorMatrix.swift:165— _ColorMatrix.init 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.
ViewGraph.updateOutputs (cyclomatic 20) Sources/OpenSwiftUICore/View/Graph/ViewGraph.swift:512— ViewGraph.updateOutputs 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.
NSAttributedString.measured (cyclomatic 20) Sources/OpenSwiftUICore/View/Text/Text/Text+StringDrawingContext.swift:155— NSAttributedString.measured has cyclomatic complexity 20 (threshold 15). Of this number, 18 points are the body's own statements and 2 belong to one function item inside it that branches. To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
normalize_swiftinterface.nonCodeEnd (cyclomatic 20) Scripts/normalize_swiftinterface.js:37— normalize_swiftinterface.nonCodeEnd 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.
DisplayListTransform.value (cyclomatic 19) Sources/OpenSwiftUI/Accessibility/AccessibilityViewModifier.swift:461— DisplayListTransform.value 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.
FocusBridge.firstResponderDidChange (cyclomatic 19) Sources/OpenSwiftUI/Event/Focus/FocusBridge.swift:679— FocusBridge.firstResponderDidChange 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.
_UIHostingView._hitTest (cyclomatic 19) Sources/OpenSwiftUI/Integration/Hosting/UIKit/View/UIHostingView.swift:481— _UIHostingView._hitTest 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.
DisplayLink.displayLinkTimer (cyclomatic 19) Sources/OpenSwiftUI/Integration/Hosting/UIKit/View/UIHostingViewBase.swift:940— DisplayLink.displayLinkTimer 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.
ShapeLayerAsyncHelper.visitPaint (cyclomatic 19) Sources/OpenSwiftUICore/Shape/ShapeLayer.swift:586— ShapeLayerAsyncHelper.visitPaint 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.
ResolvedGradientVector.add (cyclomatic 19) Sources/OpenSwiftUICore/Graphic/Gradient/Gradient.swift:517— ResolvedGradientVector.add has cyclomatic complexity 19 (threshold 15). Of this number, 16 points are the body's own statements and 3 belong to one function item inside it that branches. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
_FlexFrameLayout.sizeThatFits (cyclomatic 19) Sources/OpenSwiftUICore/Layout/Modifier/FrameLayout.swift:279— _FlexFrameLayout.sizeThatFits 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.
_SymbolEffect.init (cyclomatic 19) Sources/OpenSwiftUI/Render/SymbolEffect/SymbolEffectAPI.swift:404— _SymbolEffect.init 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.
ShapeStyleTriple._apply (cyclomatic 19) Sources/OpenSwiftUICore/Shape/ShapeStyle/ShapeStylePair.swift:84— ShapeStyleTriple._apply 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.
ShapeStyleResolver.updateValue (cyclomatic 19) Sources/OpenSwiftUICore/Shape/ShapeStyle/ShapeStyleResolver.swift:113— ShapeStyleResolver.updateValue 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.
Combine.combine (cyclomatic 18) Sources/OpenSwiftUI/Accessibility/AccessibilityChildBehavior.swift:304— Combine.combine 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.
Target.match (cyclomatic 18) Sources/OpenSwiftUI/Accessibility/AccessibilityFocus.swift:58— Target.match 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.
Value.print (cyclomatic 18) Sources/OpenSwiftUICore/Render/DisplayList/DisplayListPrinter.swift:110— Value.print has cyclomatic complexity 18 (threshold 15). To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Where every arm is uniform — the same kind of value, with no behaviour of its own — a table keyed by the case is the shorter form; wherever the arms carry different data or different behaviour, keep them as cases, because collapsing those trades an explicit, reviewable set of cases for nothing. This is NOT this file's highest cyclomatic complexity: Effect.printMinimally (cyclomatic 23) is higher and carries no row of its own — it was excluded as a flat dispatcher (a long switch/match over independent cases: many branches, almost no nesting), which this dimension does not treat as a refactor obligation. It is named here so the ranking you see in this file is not mistaken for the whole of it; the excluded method is counted neither in this dimension's figures nor in its score.
_ViewListOutputs.concat (cyclomatic 18) Sources/OpenSwiftUICore/View/Input/ViewList.swift:1479— _ViewListOutputs.concat has cyclomatic complexity 18 (threshold 15). Of this number, 12 points are the body's own statements and 6 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.
AccessibilityFocus.move (cyclomatic 17) Sources/OpenSwiftUI/Accessibility/AccessibilityFocus.swift:118— AccessibilityFocus.move 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.
Named.init (cyclomatic 17) Sources/OpenSwiftUI/Integration/PlatformItemList/WidgetAuxiliaryViewMetadata.swift:240— Named.init 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.
PlatformViewChild.updateValue (cyclomatic 17) Sources/OpenSwiftUI/Integration/Representable/Platform/PlatformViewRepresentable.swift:292— PlatformViewChild.updateValue 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.
ResolvedBorderedButton.imageBackgroundSpec (cyclomatic 17) Sources/OpenSwiftUI/View/Control/Button/BorderedButtonStyle_Phone.swift:134— ResolvedBorderedButton.imageBackgroundSpec 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.
UITraitCollection.resolvedTraitCollection (cyclomatic 17) Sources/OpenSwiftUI/Data/Environment/UIKitEnvironment.swift:43— UITraitCollection.resolvedTraitCollection 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.
UIRectEdge.init (cyclomatic 17) Sources/OpenSwiftUI/Integration/Graphic/UIKit/UIKitConversions.swift:18— UIRectEdge.init 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.
DurationPhase.updateValue (cyclomatic 17) Sources/OpenSwiftUICore/Event/Gesture/DurationGesture.swift:80— DurationPhase.updateValue 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.
ResponderNode.focusNavigationCohort (cyclomatic 17) Sources/OpenSwiftUI/Event/Focus/FocusNavigator.swift:264— ResponderNode.focusNavigationCohort 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.
VectorKey.symbolSizeScale (cyclomatic 17) Sources/OpenSwiftUICore/View/Image/NamedImage.swift:151— VectorKey.symbolSizeScale 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.
TextLayoutProperties.update (cyclomatic 17) Sources/OpenSwiftUICore/View/Text/Text/Text+View.swift:464— TextLayoutProperties.update 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.
AttributedString.isStyled (cyclomatic 17) Sources/OpenSwiftUICore/View/Text/AttributedString/Text+AttributedString.swift:536— AttributedString.isStyled 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.
Attributed.template (cyclomatic 17) Sources/OpenSwiftUICore/View/Text/FormatStyle/SafelySerializableDiscreteFormatStyle.swift:325— Attributed.template 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.
Item.discardContainingClips (cyclomatic 16) Sources/OpenSwiftUICore/Render/DisplayList/DisplayListViewModel.swift:660— Item.discardContainingClips 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.
SizeFittingState.applyChildren (cyclomatic 16) Sources/OpenSwiftUI/Layout/ViewThatFits.swift:171— SizeFittingState.applyChildren 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.
PlatformViewHost.intrinsicLayoutTraits (cyclomatic 16) Sources/OpenSwiftUI/Integration/Representable/Platform/PlatformViewHost.swift:124— PlatformViewHost.intrinsicLayoutTraits has cyclomatic complexity 16 (threshold 15). Most of this is not in the body itself: 4 of the 16 points are its own statements and the rest belongs to 2 function items inside it that branch (validateDimension, dimension). Those helpers are already separate functions, so extracting the branching again is not available. To reduce it, move them out of the body to the enclosing scope, where each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
UIKitSensoryFeedbackCache.implementation (cyclomatic 16) Sources/OpenSwiftUI/View/Control/SensoryFeedback/UIKit/UIKitSensoryFeedbackCache.swift:31— UIKitSensoryFeedbackCache.implementation has cyclomatic complexity 16 (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.
ShapeLayerHelper.visitPaint (cyclomatic 16) Sources/OpenSwiftUICore/Shape/ShapeLayer.swift:108— ShapeLayerHelper.visitPaint has cyclomatic complexity 16 (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.
NSParagraphStyle.isEqual (cyclomatic 16) Sources/OpenSwiftUICore/Shim/TextNonDarwinShims.swift:102— NSParagraphStyle.isEqual 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.
PropertyList.merge (cyclomatic 16) Sources/OpenSwiftUICore/Data/Util/PropertyList.swift:309— PropertyList.merge 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.
_FlexFrameLayout.init (cyclomatic 16) Sources/OpenSwiftUICore/Layout/Modifier/FrameLayout.swift:202— _FlexFrameLayout.init 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.
ForEachState.item (cyclomatic 16) Sources/OpenSwiftUICore/View/DynamicViewContent/ForEach.swift:460— ForEachState.item 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.
ResolvedTextHelper.resolve (cyclomatic 16) Sources/OpenSwiftUICore/View/Text/Text/Text+View.swift:1445— ResolvedTextHelper.resolve 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.
Modifier.modify (cyclomatic 16) Sources/OpenSwiftUICore/View/Text/Text/Text.swift:241— Modifier.modify 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.
D12 · Dependency Hygiene· No Package.resolved committed (Renderer/Stdout/Tuist/Package.swift) · ×1
No Package.resolved committed (Renderer/Stdout/Tuist/Package.swift) — Renderer/Stdout/Tuist/Package.swift declares 4 dependencies and no `.library` product, so it is an APPLICATION — but no `Package.resolved` is committed beside it. Nothing records the versions a working build resolved to, so `swift build` re-resolves against whatever each dependency's git host serves today and two builds of this commit are not guaranteed to be the same build. Build once and commit the resulting `Package.resolved`. (A published LIBRARY correctly omits its resolution — SwiftPM ignores a library's `Package.resolved` when the package is consumed — which is why this is asked only of a package that ships no `.library` product.)
Repeated repair: Scripts/CI/release.js Scripts/CI/release.js:92— Scripts/CI/release.js changed 7 times in last 90 days and 4 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 9 (its worst body is release.validateManifest at line 92), 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(release): normalize and verify binary interfaces (#1188)”; “fix: complete release checks and stabilize snapshot tests (#1184)”; “fix(release): sync OpenObservation macro sources (#1106)”; “fix(release): handle draft release lookups”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-07-31..2026-10-29, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-31 00:37:40 +08:00' --until='2026-10-29 00:37:40 +08:00' --full-history --no-merges -- Scripts/CI/release.js`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
FixmeComment repeated across 35 files Sources/OpenSwiftUICore/View/ViewDebug.swift:205— The identical FixmeComment appears in 35 files (51 occurrences) — almost certainly one boilerplate line from a single migration or decision, not 51 independent debts. Fix the systemic cause once rather than file-by-file. Text: "// FIXME". Source code is not a task system: track the cleanup where tasks live. (Every occurrence still counts toward the score and metrics.)
TodoComment repeated across 29 files Sources/OpenSwiftUICore/View/Text/AttributedString/AttributedStringKey+Extension.swift:11— The identical TodoComment appears in 29 files (85 occurrences) — almost certainly one boilerplate line from a single migration or decision, not 85 independent debts. Fix the systemic cause once rather than file-by-file. Text: "// TODO". Source code is not a task system: track the cleanup where tasks live. (Every occurrence still counts toward the score and metrics.)
DefaultSystemColorDefinition_PhoneTV.value (cognitive 128) Sources/OpenSwiftUICore/Graphic/Color/SystemColors.swift:280— DefaultSystemColorDefinition_PhoneTV.value has cognitive complexity 128 (threshold 15). Drivers by points: ternaries 41 (123 pts), match/switch 3 (5 pts) (nesting depth added 84). 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.
DynamicContainerInfo.updateValue (cognitive 100) Sources/OpenSwiftUICore/Layout/Dynamic/DynamicContainer.swift:322— DynamicContainerInfo.updateValue has cognitive complexity 100 (threshold 15). Drivers by points: if/else 30 (67 pts), loops 7 (22 pts), ternaries 2 (9 pts), boolean chains 2 (nesting depth added 59). Of this number, 96 points are the body's own statements and 4 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.
Platform.updateItemView (cognitive 91) Sources/OpenSwiftUICore/Render/DisplayList/DisplayListViewPlatform.swift:378— Platform.updateItemView has cognitive complexity 91 (threshold 15). Drivers by points: if/else 28 (76 pts), ternaries 2 (6 pts), match/switch 3 (5 pts), boolean chains 4 (nesting depth added 54). 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.
ORBSymbolAnimator.updateSymbolEffects (cognitive 82) Sources/OpenSwiftUICore/Render/SymbolEffect/_SymbolEffect.swift:366— ORBSymbolAnimator.updateSymbolEffects has cognitive complexity 82 (threshold 15). Drivers by points: if/else 20 (53 pts), boolean chains 13, ternaries 2 (8 pts), match/switch 2 (5 pts), loops 2 (3 pts) (nesting depth added 43). 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.
ResolvedBorderedButton.materialBackgroundSpec (cognitive 77) Sources/OpenSwiftUI/View/Control/Button/BorderedButtonStyle_Phone.swift:214— ResolvedBorderedButton.materialBackgroundSpec has cognitive complexity 77 (threshold 15). Drivers by points: ternaries 13 (44 pts), if/else 17 (31 pts), boolean chains 1, match/switch 1 (nesting depth added 45). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
ForEachState.update (cognitive 67) Sources/OpenSwiftUICore/View/DynamicViewContent/ForEach.swift:342— ForEachState.update has cognitive complexity 67 (threshold 15). Drivers by points: if/else 21 (52 pts), loops 4 (11 pts), boolean chains 4 (nesting depth added 38). 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.
CustomRecursiveStringConvertible.swift.colorNameForColorComponents (cognitive 67) Sources/OpenSwiftUICore/Util/CustomRecursiveStringConvertible.swift:239— CustomRecursiveStringConvertible.swift.colorNameForColorComponents has cognitive complexity 67 (threshold 15). Drivers by points: boolean chains 47, if/else 19 (20 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.
Item.canonicalize (cognitive 66) Sources/OpenSwiftUICore/Render/DisplayList/DisplayList.swift:741— Item.canonicalize has cognitive complexity 66 (threshold 15). Drivers by points: if/else 21 (48 pts), boolean chains 11, match/switch 4 (7 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.
PropertiesTransform.updateValue (cognitive 63) Sources/OpenSwiftUI/Accessibility/AccessibilityViewModifier.swift:625— PropertiesTransform.updateValue has cognitive complexity 63 (threshold 15). Drivers by points: if/else 20 (41 pts), loops 3 (9 pts), ternaries 3 (7 pts), boolean chains 6 (nesting depth added 31). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
_ShapeStyle_RenderedShape.renderVectorGlyph (cognitive 55) Sources/OpenSwiftUICore/Shape/ShapeStyle/ShapeStyleRendering.swift:290— _ShapeStyle_RenderedShape.renderVectorGlyph has cognitive complexity 55 (threshold 15). Drivers by points: if/else 21 (39 pts), boolean chains 8, loops 2 (3 pts), ternaries 1 (3 pts), match/switch 2 (nesting depth added 21). Of this number, 53 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.
DynamicContainerInfo.updateItems (cognitive 52) Sources/OpenSwiftUICore/Layout/Dynamic/DynamicContainer.swift:523— DynamicContainerInfo.updateItems has cognitive complexity 52 (threshold 15). Drivers by points: if/else 17 (37 pts), loops 3 (6 pts), boolean chains 5, ternaries 1 (4 pts) (nesting depth added 26). 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.
GradientLayer.clippedValues (cognitive 51) Sources/OpenSwiftUICore/Graphic/Gradient/GradientLayer.swift:62— GradientLayer.clippedValues has cognitive complexity 51 (threshold 15). Drivers by points: if/else 15 (32 pts), ternaries 9 (16 pts), loops 2, match/switch 1 (nesting depth added 24). 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.
ResolvedBorderedButton.opaqueBackgroundSpec (cognitive 50) Sources/OpenSwiftUI/View/Control/Button/BorderedButtonStyle_Phone.swift:293— ResolvedBorderedButton.opaqueBackgroundSpec has cognitive complexity 50 (threshold 15). Drivers by points: if/else 14 (25 pts), ternaries 8 (23 pts), boolean chains 1, match/switch 1 (nesting depth added 26). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
Timer.timeStyle (cognitive 45) Sources/OpenSwiftUICore/View/Text/FormatStyle/SystemFormatStyle+Timer.swift:579— Timer.timeStyle has cognitive complexity 45 (threshold 15). Drivers by points: if/else 14 (17 pts), ternaries 6 (15 pts), boolean chains 12, match/switch 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.
normalize_swiftinterface.nonCodeEnd (cognitive 45) Scripts/normalize_swiftinterface.js:37— normalize_swiftinterface.nonCodeEnd has cognitive complexity 45 (threshold 15). Drivers by points: if/else 15 (33 pts), loops 3 (7 pts), boolean chains 3, ternaries 1 (2 pts) (nesting depth added 23). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
RawPanGesture.update (cognitive 44) Sources/OpenSwiftUI/Event/Gesture/PanGesture.swift:108— RawPanGesture.update has cognitive complexity 44 (threshold 15). Drivers by points: if/else 17 (36 pts), ternaries 1 (4 pts), match/switch 1 (2 pts), boolean chains 1, loops 1 (nesting depth added 23). 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.
SharedFrame.updateValue (cognitive 44) Sources/OpenSwiftUICore/Render/GeometryEffect/MatchedGeometryEffect.swift:607— SharedFrame.updateValue has cognitive complexity 44 (threshold 15). Drivers by points: if/else 22 (38 pts), boolean chains 6 (nesting depth added 16). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
ImageResolutionContext.willUpdateVectorGlyph (cognitive 44) Sources/OpenSwiftUICore/View/Image/Image.swift:154— ImageResolutionContext.willUpdateVectorGlyph has cognitive complexity 44 (threshold 15). Drivers by points: if/else 18 (34 pts), boolean chains 6, ternaries 1 (3 pts), match/switch 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.
FocusNavigationSequence.next (cognitive 42) Sources/OpenSwiftUI/Event/Focus/FocusNavigator.swift:141— FocusNavigationSequence.next has cognitive complexity 42 (threshold 15). Drivers by points: if/else 10 (24 pts), boolean chains 11, ternaries 2 (4 pts), loops 2 (3 pts) (nesting depth added 17). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
Platform.updateItemViewAsync (cognitive 40) Sources/OpenSwiftUICore/Render/DisplayList/DisplayListViewPlatform.swift:689— Platform.updateItemViewAsync has cognitive complexity 40 (threshold 15). Drivers by points: if/else 14 (31 pts), match/switch 3 (5 pts), boolean chains 4 (nesting depth added 19). 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.
DisplayLink.displayLinkTimer (cognitive 40) Sources/OpenSwiftUI/Integration/Hosting/UIKit/View/UIHostingViewBase.swift:940— DisplayLink.displayLinkTimer has cognitive complexity 40 (threshold 15). Drivers by points: if/else 12 (28 pts), boolean chains 3, loops 1 (3 pts), match/switch 1 (3 pts), ternaries 1 (3 pts) (nesting depth added 22). 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.
AppSceneDelegate.scene (cognitive 39) Sources/OpenSwiftUI/App/App/UIKit/UIKitAppDelegate.swift:172— AppSceneDelegate.scene has cognitive complexity 39 (threshold 15). Drivers by points: if/else 23 (29 pts), boolean chains 9, loops 1 (nesting depth added 6). Of this number, 38 points are the body's own statements and 1 belongs to one function item inside it that branches. To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, 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.
EventListenerPhase.updateValue (cognitive 38) Sources/OpenSwiftUICore/Event/Gesture/EventListener.swift:99— EventListenerPhase.updateValue has cognitive complexity 38 (threshold 15). Drivers by points: if/else 16 (32 pts), boolean chains 4, loops 1, match/switch 1 (nesting depth added 16). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
ResolvedBorderedButton.imageBackgroundSpec (cognitive 37) Sources/OpenSwiftUI/View/Control/Button/BorderedButtonStyle_Phone.swift:134— ResolvedBorderedButton.imageBackgroundSpec has cognitive complexity 37 (threshold 15). Drivers by points: if/else 14 (25 pts), ternaries 4 (10 pts), boolean chains 1, match/switch 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.
FocusBridge.moveFocus (cognitive 36) Sources/OpenSwiftUI/Event/Focus/FocusBridge.swift:112— FocusBridge.moveFocus has cognitive complexity 36 (threshold 15). Drivers by points: if/else 17 (21 pts), boolean chains 8, ternaries 2 (6 pts), match/switch 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.
ChangedBodyProperty.swift.changedBodyProperties (cognitive 36) Sources/OpenSwiftUICore/Data/DynamicProperty/ChangedBodyProperty.swift:13— ChangedBodyProperty.swift.changedBodyProperties has cognitive complexity 36 (threshold 15). Drivers by points: if/else 5 (15 pts), boolean chains 10, loops 3 (8 pts), match/switch 1 (3 pts) (nesting depth added 17). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
Combine.combine (cognitive 35) Sources/OpenSwiftUI/Accessibility/AccessibilityChildBehavior.swift:304— Combine.combine has cognitive complexity 35 (threshold 15). Drivers by points: if/else 9 (21 pts), ternaries 3 (8 pts), loops 3 (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.
LayoutScrollableTransform.updateValue (cognitive 35) Sources/OpenSwiftUI/Accessibility/AccessibilityScrolling.swift:83— LayoutScrollableTransform.updateValue has cognitive complexity 35 (threshold 15). Drivers by points: if/else 10 (21 pts), loops 4 (6 pts), boolean chains 4, ternaries 2 (4 pts) (nesting depth added 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
MultiEventListenerPhase.updateValue (cognitive 35) Sources/OpenSwiftUI/Event/Gesture/MultiEventListener.swift:70— MultiEventListenerPhase.updateValue has cognitive complexity 35 (threshold 15). Drivers by points: if/else 14 (25 pts), boolean chains 5, loops 2, ternaries 1 (2 pts), match/switch 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.
ResolvedBorderedButton.specs (cognitive 35) Sources/OpenSwiftUI/View/Control/Button/WidgetBorderedButtonStyle.swift:76— ResolvedBorderedButton.specs has cognitive complexity 35 (threshold 15). Drivers by points: ternaries 7 (20 pts), if/else 9 (15 pts) (nesting depth added 19). To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
Style.nsAttributes (cognitive 34) Sources/OpenSwiftUICore/View/Text/AttributedString/Text+NSAttributedString.swift:273— Style.nsAttributes has cognitive complexity 34 (threshold 15). Drivers by points: if/else 23 (27 pts), boolean chains 7 (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.
Dictionary.transferAttributedStringStyles (cognitive 34) Sources/OpenSwiftUICore/View/Text/AttributedString/Text+AttributedString.swift:683— Dictionary.transferAttributedStringStyles has cognitive complexity 34 (threshold 15). Drivers by points: if/else 24 (29 pts), match/switch 2 (4 pts), boolean chains 1 (nesting depth added 7). 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.
Timer.unitsStyle (cognitive 34) Sources/OpenSwiftUICore/View/Text/FormatStyle/SystemFormatStyle+Timer.swift:707— Timer.unitsStyle has cognitive complexity 34 (threshold 15). Drivers by points: boolean chains 19, if/else 11, ternaries 2 (3 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.
CUICatalog.findAsset (cognitive 33) Sources/OpenSwiftUICore/Graphic/Color/NamedColor.swift:154— CUICatalog.findAsset has cognitive complexity 33 (threshold 15). Drivers by points: if/else 6 (16 pts), match/switch 4 (13 pts), loops 2 (3 pts), boolean chains 1 (nesting depth added 20). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
ViewTransform.convert (cognitive 33) Sources/OpenSwiftUICore/Layout/View/ViewTransform.swift:329— ViewTransform.convert has cognitive complexity 33 (threshold 15). Drivers by points: if/else 17 (28 pts), match/switch 4 (5 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.
Named.init (cognitive 32) Sources/OpenSwiftUI/Integration/PlatformItemList/WidgetAuxiliaryViewMetadata.swift:240— Named.init has cognitive complexity 32 (threshold 15). Drivers by points: if/else 13 (21 pts), ternaries 2 (6 pts), loops 1 (3 pts), boolean chains 1, match/switch 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.
AccessibilityProperties.merge (cognitive 32) Sources/OpenSwiftUI/Accessibility/AccessibilityProperties.swift:14— AccessibilityProperties.merge has cognitive complexity 32 (threshold 15). Drivers by points: if/else 30 (31 pts), boolean chains 1 (nesting depth added 1). To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
ResolvedGradientVector.add (cognitive 32) Sources/OpenSwiftUICore/Graphic/Gradient/Gradient.swift:517— ResolvedGradientVector.add has cognitive complexity 32 (threshold 15). Drivers by points: if/else 14 (19 pts), loops 3 (6 pts), ternaries 2 (4 pts), boolean chains 3 (nesting depth added 10). Of this number, 26 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.
DisplayList.forEachIdentity (cognitive 32) Sources/OpenSwiftUICore/Render/DisplayList/DisplayList.swift:168— DisplayList.forEachIdentity has cognitive complexity 32 (threshold 15). Drivers by points: if/else 8 (26 pts), loops 2 (4 pts), match/switch 1 (2 pts) (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.
SceneBridge.userActivityPreferencesDidChange (cognitive 31) Sources/OpenSwiftUI/App/Scene/SceneBridge.swift:257— SceneBridge.userActivityPreferencesDidChange has cognitive complexity 31 (threshold 15). Drivers by points: if/else 14 (26 pts), boolean chains 5 (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.
EventBindingManager.sendDownstream (cognitive 31) Sources/OpenSwiftUICore/Event/Event/EventBindingManager.swift:50— EventBindingManager.sendDownstream has cognitive complexity 31 (threshold 15). Drivers by points: if/else 15 (24 pts), boolean chains 5, loops 2 (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
ViewGraph.updateOutputs (cognitive 31) Sources/OpenSwiftUICore/View/Graph/ViewGraph.swift:512— ViewGraph.updateOutputs has cognitive complexity 31 (threshold 15). Drivers by points: if/else 11 (21 pts), boolean chains 5, loops 3 (5 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.
check_binary_version.module_slices (cognitive 31) Scripts/CI/check_binary_version.py:24— check_binary_version.module_slices has cognitive complexity 31 (threshold 15). Drivers by points: if/else 8 (21 pts), loops 3 (5 pts), ternaries 1 (3 pts), boolean chains 2 (nesting depth added 17). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
DisplayListTransform.value (cognitive 30) Sources/OpenSwiftUI/Accessibility/AccessibilityViewModifier.swift:461— DisplayListTransform.value has cognitive complexity 30 (threshold 15). Drivers by points: if/else 13 (22 pts), boolean chains 3, ternaries 3, loops 1 (2 pts) (nesting depth added 10). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
UpdateViewFocusItem.updateValue (cognitive 30) Sources/OpenSwiftUI/Event/Focus/Focusable.swift:1018— UpdateViewFocusItem.updateValue has cognitive complexity 30 (threshold 15). Drivers by points: if/else 7 (16 pts), boolean chains 14 (nesting depth added 9). 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.
SystemVibrantColorStyle.apply (cognitive 30) Sources/OpenSwiftUICore/Graphic/Color/VibrantColorStyle.swift:25— SystemVibrantColorStyle.apply has cognitive complexity 30 (threshold 15). Drivers by points: ternaries 12 (24 pts), if/else 3 (4 pts), match/switch 2 (nesting depth added 13). 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.
_FlexFrameLayout.sizeThatFits (cognitive 30) Sources/OpenSwiftUICore/Layout/Modifier/FrameLayout.swift:279— _FlexFrameLayout.sizeThatFits has cognitive complexity 30 (threshold 15). Drivers by points: if/else 15 (19 pts), match/switch 2 (6 pts), boolean chains 5 (nesting depth added 8). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
Platform.updateGeometry (cognitive 29) Sources/OpenSwiftUICore/Render/DisplayList/DisplayListViewPlatform.swift:1608— Platform.updateGeometry has cognitive complexity 29 (threshold 15). Drivers by points: if/else 13 (16 pts), boolean chains 12, match/switch 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.
PlatformViewHost._layoutSizeThatFits (cognitive 29) Sources/OpenSwiftUI/Integration/Representable/Platform/PlatformViewHost.swift:467— PlatformViewHost._layoutSizeThatFits has cognitive complexity 29 (threshold 15). Drivers by points: if/else 11 (15 pts), boolean chains 8, ternaries 2 (6 pts) (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
SafeAreaInsets.mergedInsets (cognitive 29) Sources/OpenSwiftUICore/Layout/SafeAreaInsets.swift:159— SafeAreaInsets.mergedInsets has cognitive complexity 29 (threshold 15). Drivers by points: if/else 11 (28 pts), 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.
_ViewListOutputs.concat (cognitive 29) Sources/OpenSwiftUICore/View/Input/ViewList.swift:1479— _ViewListOutputs.concat has cognitive complexity 29 (threshold 15). Drivers by points: if/else 13 (22 pts), loops 2 (3 pts), boolean chains 2, match/switch 2 (nesting depth added 10). Of this number, 19 points are the body's own statements and 10 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.
ViewTransform.forEach (cognitive 28) Sources/OpenSwiftUICore/Layout/View/ViewTransform.swift:245— ViewTransform.forEach has cognitive complexity 28 (threshold 15). Drivers by points: if/else 10 (22 pts), loops 3 (6 pts) (nesting depth added 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
NSAttributedString.measured (cognitive 28) Sources/OpenSwiftUICore/View/Text/Text/Text+StringDrawingContext.swift:155— NSAttributedString.measured has cognitive complexity 28 (threshold 15). Drivers by points: if/else 15 (20 pts), boolean chains 4, ternaries 3, match/switch 1 (nesting depth added 5). Of this number, 26 points are the body's own statements and 2 belong to one function item inside it that branches. To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
AccessibilityChildBehavior.defaultCombine (cognitive 27) Sources/OpenSwiftUI/Accessibility/AccessibilityChildBehavior.swift:130— AccessibilityChildBehavior.defaultCombine has cognitive complexity 27 (threshold 15). Drivers by points: if/else 11 (15 pts), boolean chains 8, loops 2, ternaries 2 (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.
PlatformItemListTransform.value (cognitive 27) Sources/OpenSwiftUI/Accessibility/AccessibilityViewModifier.swift:314— PlatformItemListTransform.value has cognitive complexity 27 (threshold 15). Drivers by points: if/else 7 (15 pts), loops 2 (6 pts), match/switch 2 (5 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.
FocusBridge.preferredFocusItems (cognitive 27) Sources/OpenSwiftUI/Event/Focus/UIKitHostContainerFocusItemInput.swift:498— FocusBridge.preferredFocusItems has cognitive complexity 27 (threshold 15). Drivers by points: if/else 9 (14 pts), boolean chains 12, 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.
ShapeStyleResolver.updateValue (cognitive 27) Sources/OpenSwiftUICore/Shape/ShapeStyle/ShapeStyleResolver.swift:113— ShapeStyleResolver.updateValue has cognitive complexity 27 (threshold 15). Drivers by points: if/else 16 (20 pts), boolean chains 5, ternaries 1 (2 pts) (nesting depth added 5). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, 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.
ForEachState.item (cognitive 27) Sources/OpenSwiftUICore/View/DynamicViewContent/ForEach.swift:460— ForEachState.item has cognitive complexity 27 (threshold 15). Drivers by points: if/else 12 (22 pts), boolean chains 5 (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.
Effect.print (cognitive 27) Sources/OpenSwiftUICore/Render/DisplayList/DisplayListPrinter.swift:212— Effect.print has cognitive complexity 27 (threshold 15). Drivers by points: if/else 13 (26 pts), match/switch 1 (nesting depth added 13). 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.
SizeFittingState.applyChildren (cognitive 26) Sources/OpenSwiftUI/Layout/ViewThatFits.swift:171— SizeFittingState.applyChildren has cognitive complexity 26 (threshold 15). Drivers by points: if/else 11 (21 pts), boolean chains 4, 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.
SafeAreaInsets.adjust (cognitive 26) Sources/OpenSwiftUICore/Layout/SafeAreaInsets.swift:93— SafeAreaInsets.adjust has cognitive complexity 26 (threshold 15). Drivers by points: if/else 12 (17 pts), boolean chains 7, match/switch 1 (2 pts) (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
MultiViewResponder.children (cognitive 26) Sources/OpenSwiftUICore/Event/Responder/MultiViewResponder.swift:28— MultiViewResponder.children has cognitive complexity 26 (threshold 15). Drivers by points: if/else 9 (20 pts), loops 3 (6 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.
ForEachState.evictItems (cognitive 26) Sources/OpenSwiftUICore/View/DynamicViewContent/ForEach.swift:591— ForEachState.evictItems has cognitive complexity 26 (threshold 15). Drivers by points: if/else 9 (22 pts), loops 2 (3 pts), boolean chains 1 (nesting depth added 14). 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.
ForEachState.forEachItem (cognitive 26) Sources/OpenSwiftUICore/View/DynamicViewContent/ForEach.swift:771— ForEachState.forEachItem has cognitive complexity 26 (threshold 15). Drivers by points: if/else 11 (20 pts), ternaries 1 (4 pts), boolean chains 1, loops 1 (nesting depth added 12). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
EnvironmentValues.appearance (cognitive 25) Sources/OpenSwiftUICore/Graphic/Appearance/Appearance.swift:100— EnvironmentValues.appearance has cognitive complexity 25 (threshold 15). Drivers by points: if/else 11 (23 pts), boolean chains 1, match/switch 1 (nesting depth added 12). 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.
ForEachState.estimatedCount (cognitive 25) Sources/OpenSwiftUICore/View/DynamicViewContent/ForEach.swift:860— ForEachState.estimatedCount has cognitive complexity 25 (threshold 15). Drivers by points: if/else 9 (17 pts), match/switch 1 (4 pts), loops 1 (3 pts), boolean chains 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.
ItemFilter.updateValue (cognitive 24) Sources/OpenSwiftUI/Accessibility/AccessibilityFocusStore.swift:291— ItemFilter.updateValue has cognitive complexity 24 (threshold 15). Drivers by points: if/else 8 (17 pts), boolean chains 4, loops 2 (3 pts) (nesting depth added 10). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
SizeConstraints.update (cognitive 24) Sources/OpenSwiftUI/Integration/Hosting/AppKit/View/NSHostingView.swift:795— SizeConstraints.update has cognitive complexity 24 (threshold 15). Drivers by points: if/else 10 (16 pts), ternaries 2 (6 pts), boolean chains 2 (nesting depth added 10). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
DurationPhase.updateValue (cognitive 24) Sources/OpenSwiftUICore/Event/Gesture/DurationGesture.swift:80— DurationPhase.updateValue has cognitive complexity 24 (threshold 15). Drivers by points: if/else 15 (20 pts), boolean chains 3, 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.
ForEachState.firstOffset (cognitive 24) Sources/OpenSwiftUICore/View/DynamicViewContent/ForEach.swift:960— ForEachState.firstOffset has cognitive complexity 24 (threshold 15). Drivers by points: if/else 10 (18 pts), match/switch 2 (5 pts), boolean chains 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.
BitmapKey.loadBitmapInfo (cognitive 24) Sources/OpenSwiftUICore/View/Image/NamedImage.swift:306— BitmapKey.loadBitmapInfo has cognitive complexity 24 (threshold 15). Drivers by points: if/else 9 (12 pts), boolean chains 8, ternaries 2 (3 pts), 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.
LocalizedStringKey.scan (cognitive 24) Sources/OpenSwiftUICore/View/Text/Localized/Text+Localized.swift:573— LocalizedStringKey.scan has cognitive complexity 24 (threshold 15). Drivers by points: if/else 6 (12 pts), ternaries 2 (8 pts), boolean chains 3, loops 1 (nesting depth added 12). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
Item.discardContainingClips (cognitive 23) Sources/OpenSwiftUICore/Render/DisplayList/DisplayListViewModel.swift:660— Item.discardContainingClips has cognitive complexity 23 (threshold 15). Drivers by points: if/else 8 (17 pts), boolean chains 3, 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.
AccessibilityViewModifier._makeView (cognitive 23) Sources/OpenSwiftUI/Accessibility/AccessibilityViewModifier.swift:66— AccessibilityViewModifier._makeView has cognitive complexity 23 (threshold 15). Drivers by points: if/else 10 (16 pts), boolean chains 4, ternaries 1 (3 pts) (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
_UIHostingView._hitTest (cognitive 23) Sources/OpenSwiftUI/Integration/Hosting/UIKit/View/UIHostingView.swift:481— _UIHostingView._hitTest has cognitive complexity 23 (threshold 15). Drivers by points: if/else 13 (18 pts), boolean chains 4, loops 1 (nesting depth added 5). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
PropertyList.merge (cognitive 23) Sources/OpenSwiftUICore/Data/Util/PropertyList.swift:309— PropertyList.merge has cognitive complexity 23 (threshold 15). Drivers by points: if/else 13 (18 pts), loops 3, boolean chains 2 (nesting depth added 5). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
DynamicPreferenceCombiner.value (cognitive 23) Sources/OpenSwiftUICore/Layout/Dynamic/DynamicContainer.swift:235— DynamicPreferenceCombiner.value has cognitive complexity 23 (threshold 15). Drivers by points: if/else 9 (16 pts), ternaries 2 (5 pts), boolean chains 1, loops 1 (nesting depth added 10). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
ShapeStyleTriple._apply (cognitive 23) Sources/OpenSwiftUICore/Shape/ShapeStyle/ShapeStylePair.swift:84— ShapeStyleTriple._apply has cognitive complexity 23 (threshold 15). Drivers by points: if/else 13 (20 pts), boolean chains 2, match/switch 1 (nesting depth added 7). 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.
PlatformViewChild.updateValue (cognitive 22) Sources/OpenSwiftUI/Integration/Representable/Platform/PlatformViewRepresentable.swift:292— PlatformViewChild.updateValue has cognitive complexity 22 (threshold 15). Drivers by points: if/else 12 (16 pts), boolean chains 6 (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.
PlatformAccessibilityElementProtocol._bridgedProperties (cognitive 22) Sources/OpenSwiftUI/Accessibility/Platform/AppKitAccessibility.swift:637— PlatformAccessibilityElementProtocol._bridgedProperties has cognitive complexity 22 (threshold 15). Drivers by points: if/else 11 (13 pts), boolean chains 7, loops 1 (2 pts) (nesting depth added 3). To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
VectorKey.symbolSizeScale (cognitive 22) Sources/OpenSwiftUICore/View/Image/NamedImage.swift:151— VectorKey.symbolSizeScale has cognitive complexity 22 (threshold 15). Drivers by points: if/else 9 (16 pts), loops 2 (3 pts), match/switch 1 (2 pts), boolean chains 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.
PropertyList.swift.findValueWithSecondaryLookup (cognitive 22) Sources/OpenSwiftUICore/Data/Util/PropertyList.swift:440— PropertyList.swift.findValueWithSecondaryLookup has cognitive complexity 22 (threshold 15). Drivers by points: if/else 10 (20 pts), boolean chains 1, loops 1 (nesting depth added 10). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
FocusBridge.firstResponderDidChange (cognitive 21) Sources/OpenSwiftUI/Event/Focus/FocusBridge.swift:679— FocusBridge.firstResponderDidChange has cognitive complexity 21 (threshold 15). Drivers by points: if/else 13 (15 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.
UIKitResponderGestureRecognizer.canPrevent (cognitive 21) Sources/OpenSwiftUI/Event/Platform/UIKit/UIKitResponderGestureRecognizer.swift:86— UIKitResponderGestureRecognizer.canPrevent has cognitive complexity 21 (threshold 15). Drivers by points: if/else 7 (13 pts), boolean chains 5, ternaries 1 (3 pts) (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
Path.intersectRoundedRects (cognitive 21) Sources/OpenSwiftUICore/Render/DisplayList/DisplayListViewModel.swift:404— Path.intersectRoundedRects has cognitive complexity 21 (threshold 15). Drivers by points: if/else 8 (10 pts), ternaries 2 (6 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.
_FlexFrameLayout.init (cognitive 21) Sources/OpenSwiftUICore/Layout/Modifier/FrameLayout.swift:202— _FlexFrameLayout.init has cognitive complexity 21 (threshold 15). Drivers by points: if/else 13, boolean chains 8. 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.
DynamicTextFilter.updateValue (cognitive 21) Sources/OpenSwiftUICore/View/Text/Text/Text+View.swift:1817— DynamicTextFilter.updateValue has cognitive complexity 21 (threshold 15). Drivers by points: if/else 12 (16 pts), boolean chains 5 (nesting depth added 4). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
ViewResponderTransform.updateValue (cognitive 20) Sources/OpenSwiftUI/Accessibility/AccessibilityGeometry.swift:235— ViewResponderTransform.updateValue has cognitive complexity 20 (threshold 15). Drivers by points: if/else 7 (10 pts), boolean chains 6, loops 2 (4 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.
NSHostingView.startAsyncRendering (cognitive 20) Sources/OpenSwiftUI/Integration/Hosting/AppKit/View/NSHostingView.swift:962— NSHostingView.startAsyncRendering has cognitive complexity 20 (threshold 15). Drivers by points: if/else 12 (18 pts), boolean chains 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.
ShapeLayerAsyncHelper.visitPaint (cognitive 20) Sources/OpenSwiftUICore/Shape/ShapeLayer.swift:586— ShapeLayerAsyncHelper.visitPaint has cognitive complexity 20 (threshold 15). Drivers by points: if/else 7 (12 pts), boolean chains 7, 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.
_ColorMatrix.init (cognitive 20) Sources/OpenSwiftUICore/Graphic/Color/ColorMatrix.swift:165— _ColorMatrix.init has cognitive complexity 20 (threshold 15). Drivers by points: if/else 10 (19 pts), match/switch 1 (nesting depth added 9). 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.
_SymbolEffect.init (cognitive 20) Sources/OpenSwiftUI/Render/SymbolEffect/SymbolEffectAPI.swift:404— _SymbolEffect.init has cognitive complexity 20 (threshold 15). Drivers by points: ternaries 3 (9 pts), if/else 4 (7 pts), boolean chains 3, match/switch 1 (nesting depth added 9). 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.
HierarchicalShapeStyle._apply (cognitive 20) Sources/OpenSwiftUICore/Shape/ShapeStyle/ContentStyle.swift:159— HierarchicalShapeStyle._apply has cognitive complexity 20 (threshold 15). Drivers by points: if/else 8 (15 pts), match/switch 2 (5 pts) (nesting depth added 10). 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.
Target.match (cognitive 19) Sources/OpenSwiftUI/Accessibility/AccessibilityFocus.swift:58— Target.match 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.
Platform.updateClipShapes (cognitive 19) Sources/OpenSwiftUICore/Render/DisplayList/DisplayListViewPlatform.swift:1551— Platform.updateClipShapes has cognitive complexity 19 (threshold 15). Drivers by points: if/else 9 (16 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.
PlatformViewHost.intrinsicLayoutTraits (cognitive 19) Sources/OpenSwiftUI/Integration/Representable/Platform/PlatformViewHost.swift:124— PlatformViewHost.intrinsicLayoutTraits has cognitive complexity 19 (threshold 15). Drivers by points: if/else 7, ternaries 5 (7 pts), boolean chains 5 (nesting depth added 2). Most of this is not in the body itself: 4 of the 19 points are its own statements and the rest belongs to 2 function items inside it that branch (validateDimension, dimension). Those helpers are already separate functions, so extracting the branching again is not available. To reduce it, move them out of the body to the enclosing scope, where each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
UIRectEdge.init (cognitive 19) Sources/OpenSwiftUI/Integration/Graphic/UIKit/UIKitConversions.swift:18— UIRectEdge.init has cognitive complexity 19 (threshold 15). Drivers by points: ternaries 4 (12 pts), match/switch 2 (4 pts), loops 1 (2 pts), if/else 1 (nesting depth added 11). 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.
DynamicPropertyCache.fields (cognitive 19) Sources/OpenSwiftUICore/Data/DynamicProperty/DynamicProperty.swift:198— DynamicPropertyCache.fields has cognitive complexity 19 (threshold 15). Drivers by points: if/else 6 (14 pts), loops 1 (3 pts), match/switch 1 (2 pts) (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.
DynamicLayoutMap.attributes (cognitive 19) Sources/OpenSwiftUICore/Layout/Dynamic/DynamicLayoutMap.swift:78— DynamicLayoutMap.attributes has cognitive complexity 19 (threshold 15). Drivers by points: if/else 7 (14 pts), loops 2 (4 pts), boolean chains 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.
_FrameLayout.init (cognitive 19) Sources/OpenSwiftUICore/Layout/Modifier/FrameLayout.swift:57— _FrameLayout.init has cognitive complexity 19 (threshold 15). Drivers by points: if/else 7 (10 pts), boolean chains 5, ternaries 2 (4 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.
Timer.format (cognitive 19) Sources/OpenSwiftUICore/View/Text/FormatStyle/SystemFormatStyle+Timer.swift:815— Timer.format has cognitive complexity 19 (threshold 15). Drivers by points: if/else 7 (11 pts), boolean chains 6, ternaries 1 (2 pts) (nesting depth added 5). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
AccessibilityFocus.move (cognitive 18) Sources/OpenSwiftUI/Accessibility/AccessibilityFocus.swift:118— AccessibilityFocus.move has cognitive complexity 18 (threshold 15). Drivers by points: boolean chains 10, 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.
FocusBridge.selectKeyView (cognitive 18) Sources/OpenSwiftUI/Event/Focus/FocusBridge.swift:650— FocusBridge.selectKeyView has cognitive complexity 18 (threshold 15). Drivers by points: if/else 8 (12 pts), ternaries 3 (5 pts), boolean chains 1 (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
UITraitCollection.resolvedTraitCollection (cognitive 18) Sources/OpenSwiftUI/Data/Environment/UIKitEnvironment.swift:43— UITraitCollection.resolvedTraitCollection has cognitive complexity 18 (threshold 15). Drivers by points: if/else 12 (14 pts), boolean chains 2, loops 1, ternaries 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.
AnyGestureResponder.isPrioritized (cognitive 18) Sources/OpenSwiftUICore/Event/Gesture/GestureViewModifier.swift:237— AnyGestureResponder.isPrioritized has cognitive complexity 18 (threshold 15). Drivers by points: if/else 5 (13 pts), loops 2 (4 pts), match/switch 1 (nesting depth added 10). 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.
ForegroundTransform.transform (cognitive 18) Sources/OpenSwiftUICore/Render/DisplayList/DisplayListTransforms.swift:81— ForegroundTransform.transform has cognitive complexity 18 (threshold 15). Drivers by points: if/else 5 (10 pts), loops 2 (5 pts), match/switch 2 (3 pts) (nesting depth added 9). 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.
GraphicsImage.layerStretchInPixels (cognitive 18) Sources/OpenSwiftUICore/View/Image/ImageLayer.swift:233— GraphicsImage.layerStretchInPixels has cognitive complexity 18 (threshold 15). Drivers by points: if/else 12 (15 pts), boolean chains 2, ternaries 1 (nesting depth added 3). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
ResolvedTextHelper.resolve (cognitive 18) Sources/OpenSwiftUICore/View/Text/Text/Text+View.swift:1445— ResolvedTextHelper.resolve has cognitive complexity 18 (threshold 15). Drivers by points: if/else 12 (13 pts), boolean chains 4, ternaries 1 (nesting depth added 1). To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
PropertyList.swift.compareLists (cognitive 18) Sources/OpenSwiftUICore/Data/Util/PropertyList.swift:485— PropertyList.swift.compareLists has cognitive complexity 18 (threshold 15). Drivers by points: if/else 8 (13 pts), boolean chains 4, loops 1 (nesting depth added 5). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
Platform.updateStateAsync (cognitive 17) Sources/OpenSwiftUICore/Render/DisplayList/DisplayListViewPlatform.swift:1093— Platform.updateStateAsync has cognitive complexity 17 (threshold 15). Drivers by points: if/else 10 (14 pts), boolean chains 3 (nesting depth added 4). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
PlatformViewResponderBase.containsGlobalPoints (cognitive 17) Sources/OpenSwiftUI/Event/Responder/PlatformViewResponderBase.swift:53— PlatformViewResponderBase.containsGlobalPoints has cognitive complexity 17 (threshold 15). Drivers by points: if/else 9 (12 pts), boolean chains 5 (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.
PlatformItem.merge (cognitive 17) Sources/OpenSwiftUI/Integration/PlatformItems/PlatformItems.swift:180— PlatformItem.merge has cognitive complexity 17 (threshold 15). Drivers by points: if/else 12 (16 pts), boolean chains 1 (nesting depth added 4). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
UIHostingViewBase.displayLinkTimer (cognitive 17) Sources/OpenSwiftUI/Integration/Hosting/UIKit/View/UIHostingViewBase.swift:465— UIHostingViewBase.displayLinkTimer 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.
V3.encode (cognitive 17) Sources/OpenSwiftUICore/Accessibility/AccessibilityNodeAttachment.swift:336— V3.encode has cognitive complexity 17 (threshold 15). Drivers by points: if/else 14 (15 pts), loops 1 (2 pts) (nesting depth added 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.
ResponderNode.focusNavigationCohort (cognitive 17) Sources/OpenSwiftUI/Event/Focus/FocusNavigator.swift:264— ResponderNode.focusNavigationCohort has cognitive complexity 17 (threshold 15). Drivers by points: if/else 8 (9 pts), boolean chains 8 (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.
ViewGraphTransform.apply (cognitive 17) Sources/OpenSwiftUICore/Render/DisplayList/DisplayListTransforms.swift:243— ViewGraphTransform.apply has cognitive complexity 17 (threshold 15). Drivers by points: if/else 8 (14 pts), match/switch 2 (3 pts) (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
ShapeStylePair._apply (cognitive 17) Sources/OpenSwiftUICore/Shape/ShapeStyle/ShapeStylePair.swift:22— ShapeStylePair._apply has cognitive complexity 17 (threshold 15). Drivers by points: if/else 9 (15 pts), boolean chains 1, 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.
ClosestFitCache.callAsFunction (cognitive 17) Sources/OpenSwiftUICore/View/Text/Text/Text+SizeFitting.swift:499— ClosestFitCache.callAsFunction has cognitive complexity 17 (threshold 15). Drivers by points: if/else 7 (11 pts), boolean chains 3, ternaries 1 (2 pts), loops 1 (nesting depth added 5). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
Modifier.modify (cognitive 17) Sources/OpenSwiftUICore/View/Text/Text/Text.swift:241— Modifier.modify has cognitive complexity 17 (threshold 15). Drivers by points: if/else 6 (10 pts), ternaries 2 (6 pts), match/switch 1 (nesting depth added 8). The drivers above price the dispatch low by construction — a dispatch is charged once however many cases it lists, while each branch inside an arm is charged in full — so most of this count is what the case bodies hold, and the arms are where it can be reduced. To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident.
AccessibilityFocusStoreLocation.set (cognitive 16) Sources/OpenSwiftUI/Accessibility/AccessibilityFocusStore.swift:104— AccessibilityFocusStoreLocation.set has cognitive complexity 16 (threshold 15). Drivers by points: if/else 6 (11 pts), loops 2 (5 pts) (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
TemporalStackChildren.updateValue (cognitive 16) Sources/OpenSwiftUI/Layout/TemporalStack.swift:254— TemporalStackChildren.updateValue has cognitive complexity 16 (threshold 15). Drivers by points: if/else 6 (13 pts), loops 2, boolean chains 1 (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
FocusBridge.updateDefaultKeyViewLoop (cognitive 16) Sources/OpenSwiftUI/Event/Focus/FocusBridge.swift:501— FocusBridge.updateDefaultKeyViewLoop has cognitive complexity 16 (threshold 15). Drivers by points: if/else 5 (11 pts), match/switch 1 (3 pts), loops 1 (2 pts) (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
FocusInteractions.resolve (cognitive 16) Sources/OpenSwiftUI/Event/Focus/Focusable.swift:380— FocusInteractions.resolve has cognitive complexity 16 (threshold 15). Drivers by points: if/else 9 (15 pts), boolean chains 1 (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
Text.makeCommonAttributes (cognitive 16) Sources/OpenSwiftUICore/View/Text/Text/Text+View.swift:69— Text.makeCommonAttributes has cognitive complexity 16 (threshold 15). Drivers by points: if/else 12 (14 pts), boolean chains 1, ternaries 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.
NSView.adoptEnvironment (cognitive 16) Sources/OpenSwiftUI/Integration/Graphic/AppKit/AppKitViewEnvironment.swift:14— NSView.adoptEnvironment has cognitive complexity 16 (threshold 15). Drivers by points: if/else 7 (9 pts), ternaries 3 (4 pts), boolean chains 3 (nesting depth added 3). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition.
Layout.makeStaticView (cognitive 16) Sources/OpenSwiftUICore/Layout/LayoutView.swift:100— Layout.makeStaticView has cognitive complexity 16 (threshold 15). Drivers by points: if/else 8 (13 pts), boolean chains 3 (nesting depth added 5). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
_PaddingLayout.spacing (cognitive 16) Sources/OpenSwiftUICore/Layout/Modifier/PaddingLayout.swift:46— _PaddingLayout.spacing has cognitive complexity 16 (threshold 15). Drivers by points: if/else 9 (16 pts) (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
ForEachState.count (cognitive 16) Sources/OpenSwiftUICore/View/DynamicViewContent/ForEach.swift:817— ForEachState.count has cognitive complexity 16 (threshold 15). Drivers by points: if/else 7 (10 pts), boolean chains 3, match/switch 1 (3 pts) (nesting depth added 5). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
ViewGraph.isHiddenForReuseDidChange (cognitive 16) Sources/OpenSwiftUICore/View/Graph/ViewGraph.swift:344— ViewGraph.isHiddenForReuseDidChange has cognitive complexity 16 (threshold 15). Drivers by points: if/else 5 (8 pts), loops 3 (7 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.
VectorImageLayer.init (cognitive 16) Sources/OpenSwiftUICore/View/Image/VectorImageLayer.swift:33— VectorImageLayer.init has cognitive complexity 16 (threshold 15). Drivers by points: if/else 7 (9 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, 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.
LocalizedStringKey.getArgumentsForInflection (cognitive 16) Sources/OpenSwiftUICore/View/Text/Localized/Text+Localized.swift:388— LocalizedStringKey.getArgumentsForInflection has cognitive complexity 16 (threshold 15). Drivers by points: if/else 6 (8 pts), boolean chains 7, loops 1 (nesting depth added 2). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
TextLayoutProperties.update (cognitive 16) Sources/OpenSwiftUICore/View/Text/Text/Text+View.swift:464— TextLayoutProperties.update has cognitive complexity 16 (threshold 15). Drivers by points: if/else 16. 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.
AttributedString.isStyled (cognitive 16) Sources/OpenSwiftUICore/View/Text/AttributedString/Text+AttributedString.swift:536— AttributedString.isStyled has cognitive complexity 16 (threshold 15). Drivers by points: if/else 15, boolean chains 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.
AttributedString.redact (cognitive 16) Sources/OpenSwiftUICore/View/Text/FormatStyle/TimeDataFormatting.swift:219— AttributedString.redact has cognitive complexity 16 (threshold 15). Drivers by points: if/else 8 (11 pts), boolean chains 4, loops 1 (nesting depth added 3). 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, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
Attributed.template (cognitive 16) Sources/OpenSwiftUICore/View/Text/FormatStyle/SafelySerializableDiscreteFormatStyle.swift:325— Attributed.template has cognitive complexity 16 (threshold 15). Drivers by points: if/else 14, 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.
PropertyList.swift.find1 (cognitive 16) Sources/OpenSwiftUICore/Data/Util/PropertyList.swift:409— PropertyList.swift.find1 has cognitive complexity 16 (threshold 15). Drivers by points: if/else 7 (15 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.
D4 · Code Duplication· Members sharing a duplicated core (5 members, 50+ identical tokens) · ×1
Members sharing a duplicated core (5 members, 50+ identical tokens) Sources/OpenSwiftUICore/Animation/Animation/BezierAnimation.swift:474— Sources/OpenSwiftUICore/Animation/Animation/BezierAnimation.swift:474-486 | Sources/OpenSwiftUICore/Animation/Animation/DefaultAnimation.swift:105-117 | Sources/OpenSwiftUICore/Animation/Animation/Spring/FluidSpringAnimation.swift:28-91 | Sources/OpenSwiftUICore/Animation/Animation/Spring/SpringAnimation.swift:36-57 | Sources/OpenSwiftUICore/Animation/Animation/UnitCurve.swift:410-422 — These 5 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 5 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 5 times.
Duplicated block (28–29 lines × 2) Sources/OpenSwiftUICore/View/Text/Text/Text+View.swift:1345— Sources/OpenSwiftUICore/View/Text/Text/Text+View.swift:1345-1372 | Sources/OpenSwiftUICore/View/Text/Text/Text+View.swift:1586-1614 — 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/OpenSwiftUICore/View/Text/Text/Text+View.swift:1345` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (27 lines × 2) Sources/OpenSwiftUICore/Animation/Animatable/AnimatableAttribute.swift:90— Sources/OpenSwiftUICore/Animation/Animatable/AnimatableAttribute.swift:90-116 | Sources/OpenSwiftUICore/Animation/Animatable/AnimatableAttribute.swift:165-191 — 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 (25 lines × 3) Sources/OpenSwiftUICore/View/Text/FormatStyle/SizeAdaptiveFormatStyle.swift:384— Sources/OpenSwiftUICore/View/Text/FormatStyle/SizeAdaptiveFormatStyle.swift:384-408 | Sources/OpenSwiftUICore/View/Text/FormatStyle/SizeAdaptiveFormatStyle.swift:419-443 | Sources/OpenSwiftUICore/View/Text/FormatStyle/SizeAdaptiveFormatStyle.swift:452-476 — 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. 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 (24 lines × 2) Sources/OpenSwiftUICore/View/Text/Localized/Text+Localized.swift:335— Sources/OpenSwiftUICore/View/Text/Localized/Text+Localized.swift:335-358 | Sources/OpenSwiftUICore/View/Text/Localized/Text+Localized.swift:361-384 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (21 lines × 2) Sources/OpenSwiftUICore/Graphic/GraphicsConversions.swift:30— Sources/OpenSwiftUICore/Graphic/GraphicsConversions.swift:30-50 | Sources/OpenSwiftUICore/Graphic/GraphicsFilter.swift:111-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/OpenSwiftUICore/Graphic/GraphicsConversions.swift:30` 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 (20 lines × 2) Sources/OpenSwiftUICore/Data/Protobuf/ProtobufDecoder.swift:216— Sources/OpenSwiftUICore/Data/Protobuf/ProtobufDecoder.swift:216-235 | Sources/OpenSwiftUICore/Data/Protobuf/ProtobufDecoder.swift:272-291 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (17 lines × 2) Sources/OpenSwiftUI/Modifier/ViewModifier/GeometryActionModifier.swift:40— Sources/OpenSwiftUI/Modifier/ViewModifier/GeometryActionModifier.swift:40-56 | Sources/OpenSwiftUI/Modifier/ViewModifier/GeometryActionModifier.swift:113-129 — 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 (16 lines × 2) Sources/OpenSwiftUITestsSupport/Integration/PlatformHostingControllerHelper.swift:74— Sources/OpenSwiftUITestsSupport/Integration/PlatformHostingControllerHelper.swift:74-89 | Sources/OpenSwiftUITestsSupport/Integration/PlatformHostingControllerHelper.swift:94-109 — 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/OpenSwiftUITestsSupport/Integration/PlatformHostingControllerHelper.swift:74` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note first that the copies are not typed on the same thing: the declarations holding them bind `expectedCount` to `Int = 1` in one and `some RangeExpression<Int> & Sendable & Sequence<Int>` in another, and the duplicated lines use it. The extracted unit therefore needs a parameter type that fits BOTH — their common supertype where they have one, or a new abstraction over them where they do not — and settling that is the step that comes BEFORE the extraction above. Where the two types are deliberately unrelated, the duplication is the price of that separation and the honest resolution is to record the decision rather than to extract.
Duplicated block (12–14 lines × 2) Sources/OpenSwiftUI/Integration/Hosting/AppKit/View/NSHostingView.swift:1055— Sources/OpenSwiftUI/Integration/Hosting/AppKit/View/NSHostingView.swift:1055-1066 | Sources/OpenSwiftUI/Integration/Hosting/UIKit/View/UIHostingViewBase.swift:438-451 — 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/OpenSwiftUI/Integration/Hosting/AppKit/View/NSHostingView.swift:1055` 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 (13–14 lines × 2) Sources/OpenSwiftUICore/Layout/Modifier/InsetViewModifier.swift:508— Sources/OpenSwiftUICore/Layout/Modifier/InsetViewModifier.swift:508-520 | Sources/OpenSwiftUICore/Layout/Modifier/InsetViewModifier.swift:581-594 — 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 (13 lines × 4) Sources/OpenSwiftUICore/Layout/Edge/EdgeInsets.swift:411— Sources/OpenSwiftUICore/Layout/Edge/EdgeInsets.swift:411-423 | Sources/OpenSwiftUICore/Layout/Geometry/ProjectionTransform.swift:218-230 | Sources/OpenSwiftUICore/Util/Extension/CGAffineTransform+Extension.swift:66-78 | Sources/OpenSwiftUICore/Util/Extension/CGRect+Extension.swift:269-281 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 4 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 4 times. Read the line range as the matched WINDOW rather than a finished unit: at `Sources/OpenSwiftUICore/Layout/Edge/EdgeInsets.swift:411` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (12–13 lines × 3) Sources/OpenSwiftUI/View/Control/ProgressView/ProgressView.swift:520— Sources/OpenSwiftUI/View/Control/ProgressView/ProgressView.swift:520-532 | Sources/OpenSwiftUICore/View/Image/SymbolRenderingMode.swift:190-201 | Sources/OpenSwiftUICore/View/Text/Util/EnvironmentParagraphStyle.swift:131-142 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 3 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 3 times. Read the line range as the matched WINDOW rather than a finished unit: at `Sources/OpenSwiftUI/View/Control/ProgressView/ProgressView.swift:520` 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–13 lines × 2) Sources/OpenSwiftUICore/View/Archive/ConditionallyArchivableView.swift:88— Sources/OpenSwiftUICore/View/Archive/ConditionallyArchivableView.swift:88-100 | Sources/OpenSwiftUICore/View/ConditionalGraphicsView.swift:114-120 — before extracting anything, compare `Sources/OpenSwiftUICore/View/Archive/ConditionallyArchivableView.swift` and `Sources/OpenSwiftUICore/View/ConditionalGraphicsView.swift` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 47 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `Sources/OpenSwiftUICore/View/Archive/ConditionallyArchivableView.swift:88` 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. Note first that the copies are not typed on the same thing: the declarations holding them bind `inputs` to `_ViewListCountInputs` in one and `inout _GraphInputs` in another, and the duplicated lines use it. The extracted unit therefore needs a parameter type that fits BOTH — their common supertype where they have one, or a new abstraction over them where they do not — and settling that is the step that comes BEFORE the extraction above. Where the two types are deliberately unrelated, the duplication is the price of that separation and the honest resolution is to record the decision rather than to extract.
Duplicated block (12 lines × 3) Sources/OpenSwiftUICore/Layout/Geometry/UnitPoint.swift:263— Sources/OpenSwiftUICore/Layout/Geometry/UnitPoint.swift:263-274 | Sources/OpenSwiftUICore/Util/Extension/CGPoint+Extension.swift:140-151 | Sources/OpenSwiftUICore/Util/Extension/CGSize+Extension.swift:154-165 — 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 (7–10 lines × 2) Sources/OpenSwiftUICore/Modifier/ViewModifier.swift:237— Sources/OpenSwiftUICore/Modifier/ViewModifier.swift:237-246 | Sources/OpenSwiftUICore/View/VariadicView/VariadicView.swift:204-210 — 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/OpenSwiftUICore/Modifier/ViewModifier.swift:237` 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–9 lines × 2) Sources/OpenSwiftUICore/Graphic/Color/NamedColor.swift:181— Sources/OpenSwiftUICore/Graphic/Color/NamedColor.swift:181-188 | Sources/OpenSwiftUICore/Graphic/Color/NamedColor.swift:190-198 — 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/OpenSwiftUICore/Graphic/Color/NamedColor.swift:190` 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 (4–8 lines × 3) Sources/OpenSwiftUI/Integration/Hosting/AppKit/View/NSHostingView.swift:1325— Sources/OpenSwiftUI/Integration/Hosting/AppKit/View/NSHostingView.swift:1325-1328 | Sources/OpenSwiftUI/Integration/Hosting/UIKit/View/UIHostingViewBase.swift:160-167 | Sources/OpenSwiftUICore/Render/DisplayList/StdoutRendererHost.swift:81-88 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 3 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 3 times. Read the line range as the matched WINDOW rather than a finished unit: at `Sources/OpenSwiftUI/Integration/Hosting/AppKit/View/NSHostingView.swift:1325` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (7–8 lines × 2) Sources/OpenSwiftUICore/Graphic/Gradient/GradientLayer.swift:111— Sources/OpenSwiftUICore/Graphic/Gradient/GradientLayer.swift:111-117 | Sources/OpenSwiftUICore/Graphic/Gradient/GradientLayer.swift:123-130 — 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/OpenSwiftUICore/Graphic/Gradient/GradientLayer.swift:111` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (6–7 lines × 4) Sources/OpenSwiftUICore/Layout/Edge/EdgeInsets.swift:397— Sources/OpenSwiftUICore/Layout/Edge/EdgeInsets.swift:397-403 | Sources/OpenSwiftUICore/Layout/Geometry/ProjectionTransform.swift:203-208 | Sources/OpenSwiftUICore/Util/Extension/CGAffineTransform+Extension.swift:51-56 | Sources/OpenSwiftUICore/Util/Extension/CGRect+Extension.swift:255-261 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 4 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 4 times. Read the line range as the matched WINDOW rather than a finished unit: at `Sources/OpenSwiftUICore/Layout/Edge/EdgeInsets.swift:397` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (6 lines × 5) Sources/OpenSwiftUICore/Animation/Animation/BezierAnimation.swift:475— Sources/OpenSwiftUICore/Animation/Animation/BezierAnimation.swift:475-480 | Sources/OpenSwiftUICore/Animation/Animation/DefaultAnimation.swift:106-111 | Sources/OpenSwiftUICore/Animation/Animation/Spring/FluidSpringAnimation.swift:29-34 | Sources/OpenSwiftUICore/Animation/Animation/Spring/SpringAnimation.swift:37-42 | Sources/OpenSwiftUICore/Animation/Animation/UnitCurve.swift:411-416 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 5 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 5 times. Read the line range as the matched WINDOW rather than a finished unit: at `Sources/OpenSwiftUICore/Animation/Animation/BezierAnimation.swift:475` 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 (134 lines × 2) Sources/OpenSwiftUI/App/App/AppKit/NSApplicationDelegateAdaptor.swift:81— Sources/OpenSwiftUI/App/App/AppKit/NSApplicationDelegateAdaptor.swift:81-217 | Sources/OpenSwiftUI/App/App/UIKit/UIApplicationDelegateAdaptor.swift:129-262 — 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/OpenSwiftUI/App/App/AppKit/NSApplicationDelegateAdaptor.swift:81` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
Duplicated block (11 lines × 3) Sources/OpenSwiftUI/View/Label/SidebarLabelStyle.swift:14— Sources/OpenSwiftUI/View/Label/SidebarLabelStyle.swift:14-24 | Sources/OpenSwiftUI/View/List/ListStyle.swift:18-94 | Sources/OpenSwiftUI/View/List/MultimodalListStyle.swift:19-32 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 3 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 3 times. Read the line range as the matched WINDOW rather than a finished unit: at `Sources/OpenSwiftUI/View/Label/SidebarLabelStyle.swift:14` 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 (9 lines × 3) Sources/OpenSwiftUI/Accessibility/AccessibilityAttachmentModifier.swift:70— Sources/OpenSwiftUI/Accessibility/AccessibilityAttachmentModifier.swift:70-78 | Sources/OpenSwiftUI/Accessibility/AccessibilityContainerModifier.swift:38-46 | Sources/OpenSwiftUI/Accessibility/AccessibilityScrolling.swift:248-256 — 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 (7 lines × 5) Sources/OpenSwiftUI/Accessibility/AccessibilityConfiguration.swift:79— Sources/OpenSwiftUI/Accessibility/AccessibilityConfiguration.swift:79-85 | Sources/OpenSwiftUI/Accessibility/AccessibilityConfiguration.swift:140-146 | Sources/OpenSwiftUI/Accessibility/AccessibilityScrolling.swift:214-220 | Sources/OpenSwiftUI/Accessibility/AccessibilityScrolling.swift:258-264 | Sources/OpenSwiftUI/Accessibility/AccessibilityViewModifier.swift:842-848 — there are 5 copies across 3 file(s) — more copies than files, so at least one file holds the block twice. Extract it once into a single shared function every call site can reach and call it from all 5 sites; resolving a subset leaves the remainder to drift apart.
Duplicated block (7 lines × 3) Sources/OpenSwiftUI/View/ArchivedView/ArchivableViewModifier.swift:40— Sources/OpenSwiftUI/View/ArchivedView/ArchivableViewModifier.swift:40-46 | Sources/OpenSwiftUICore/Modifier/ViewModifier.swift:144-150 | Sources/OpenSwiftUICore/Render/GeometryEffect/GeometryEffect.swift:76-82 — 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `Sources/OpenSwiftUICore/Render/GeometryEffect/GeometryEffect.swift:84` calls `available` and `Sources/OpenSwiftUI/View/ArchivedView/ArchivableViewModifier.swift:48` does not — after which the two agree again for 4 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (8 lines × 4) Sources/OpenSwiftUI/Integration/Representable/AppKit/NSViewControllerRepresentable.swift:187— Sources/OpenSwiftUI/Integration/Representable/AppKit/NSViewControllerRepresentable.swift:187-194 | Sources/OpenSwiftUI/Integration/Representable/AppKit/NSViewRepresentable.swift:223-230 | Sources/OpenSwiftUI/Integration/Representable/UIKit/UIViewControllerRepresentable.swift:181-188 | Sources/OpenSwiftUI/Integration/Representable/UIKit/UIViewRepresentable.swift:208-215 — before extracting anything, compare `Sources/OpenSwiftUI/Integration/Representable/AppKit/NSViewControllerRepresentable.swift` and `Sources/OpenSwiftUI/Integration/Representable/AppKit/NSViewRepresentable.swift` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 42 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (11 lines × 4) Sources/OpenSwiftUICore/Graphic/Color/ForegroundColor.swift:83— Sources/OpenSwiftUICore/Graphic/Color/ForegroundColor.swift:83-93 | Sources/OpenSwiftUICore/Shape/ShapeStyle/ForegroundStyle.swift:273-283 | Sources/OpenSwiftUICore/Shape/ShapeStyle/ForegroundStyle.swift:317-327 | Sources/OpenSwiftUICore/Shape/ShapeStyle/ForegroundStyle.swift:367-377 — there are 4 copies across 2 file(s) — more copies than files, so at least one file holds the block twice. Extract it once into a single shared function every call site can reach and call it from all 4 sites; resolving a subset leaves the remainder to drift apart.
Duplicated block (5 lines × 4) Sources/OpenSwiftUICore/Layout/Stack/HStack.swift:129— Sources/OpenSwiftUICore/Layout/Stack/HStack.swift:129-133 | Sources/OpenSwiftUICore/Layout/Stack/HStack.swift:185-189 | Sources/OpenSwiftUICore/Layout/Stack/VStack.swift:129-133 | Sources/OpenSwiftUICore/Layout/Stack/VStack.swift:185-189 — there are 4 copies across 2 file(s) — more copies than files, so at least one file holds the block twice. Extract it once into a single shared function every call site can reach and call it from all 4 sites; resolving a subset leaves the remainder to drift apart. Note first that the copies are not typed on the same thing: the declarations holding them bind `alignment` to `VerticalAlignment = .center` in one and `HorizontalAlignment = .center` in another, and the duplicated lines use it. The extracted unit therefore needs a parameter type that fits BOTH — their common supertype where they have one, or a new abstraction over them where they do not — and settling that is the step that comes BEFORE the extraction above. Where the two types are deliberately unrelated, the duplication is the price of that separation and the honest resolution is to record the decision rather than to extract.
Duplicated block (7–12 lines × 5) Example/Project.swift:467— Example/Project.swift:467-473 | Example/Project.swift:474-485 | Example/Project.swift:487-498 | Example/Project.swift:500-511 | Example/Project.swift:512-519 — all 5 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 `Example/Project.swift:467` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `Example/Project.swift:485` calls `targets` and `Example/Project.swift:473` does not — after which the two agree again for 5 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (64 lines × 2) Example/Example/ObservableExampleApp.swift:23— Example/Example/ObservableExampleApp.swift:23-104 | Example/Example/ObservableObjectExampleApp.swift:27-90 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `Example/Example/ObservableExampleApp.swift:23` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
Off the main sequence: OpenSwiftUICore — OpenSwiftUICore: abstractness 0.15, instability 0.00, distance 0.85 — zone of pain — concrete and depended on by 1 project(s), so it's rigid to change.
Complex function runTests (cyclomatic 41, cognitive 54) Scripts/CI/Tests/interaction-test-action-tests.mjs:226— runTests has cyclomatic complexity 41 and cognitive complexity 54; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function nonCodeEnd (cyclomatic 20, cognitive 45) Scripts/normalize_swiftinterface.js:37— nonCodeEnd has cyclomatic complexity 20 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 snapshotRequest (cyclomatic 14, cognitive 13) Scripts/CI/Tests/optional-ci-tests.mjs:400— snapshotRequest has cyclomatic complexity 14 and cognitive complexity 13; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function (anonymous) (cyclomatic 12, cognitive 25) Scripts/CI/Tests/optional-ci-tests.mjs:511— (anonymous) has cyclomatic complexity 12 and cognitive complexity 25; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function request (cyclomatic 12, cognitive 11) Scripts/CI/Tests/optional-ci-tests.mjs:52— request has cyclomatic complexity 12 and cognitive complexity 11; 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.
No direct assertions: testEntryMacroExpansion Tests/OpenSwiftUIMacrosTests/EntryMacroTests.swift:22— No conventional assertion call was detected, and 16 of 16 tests in `OpenSwiftUIMacrosTests` read the same way — so this is treated as that project's convention rather than a broken test, and it does not drag the score. Two things look like this: verification that happens indirectly (an approval/verifier harness or BDD step methods), or a project of runnable samples compiled as tests, where a run that does not throw is the only check. If it is the latter, these methods genuinely verify nothing.
No direct assertions: testEntryMacroExpansionWithIntType Tests/OpenSwiftUIMacrosTests/EntryMacroTests.swift:79— No conventional assertion call was detected, and 16 of 16 tests in `OpenSwiftUIMacrosTests` read the same way — so this is treated as that project's convention rather than a broken test, and it does not drag the score. Two things look like this: verification that happens indirectly (an approval/verifier harness or BDD step methods), or a project of runnable samples compiled as tests, where a run that does not throw is the only check. If it is the latter, these methods genuinely verify nothing.
No direct assertions: testEntryDefaultValueMacroExpansion Tests/OpenSwiftUIMacrosTests/EntryMacroTests.swift:111— No conventional assertion call was detected, and 16 of 16 tests in `OpenSwiftUIMacrosTests` read the same way — so this is treated as that project's convention rather than a broken test, and it does not drag the score. Two things look like this: verification that happens indirectly (an approval/verifier harness or BDD step methods), or a project of runnable samples compiled as tests, where a run that does not throw is the only check. If it is the latter, these methods genuinely verify nothing.
No direct assertions: testEntryMacroWithInferredType Tests/OpenSwiftUIMacrosTests/EntryMacroTests.swift:129— No conventional assertion call was detected, and 16 of 16 tests in `OpenSwiftUIMacrosTests` read the same way — so this is treated as that project's convention rather than a broken test, and it does not drag the score. Two things look like this: verification that happens indirectly (an approval/verifier harness or BDD step methods), or a project of runnable samples compiled as tests, where a run that does not throw is the only check. If it is the latter, these methods genuinely verify nothing.
No direct assertions: testEntryMacroWithOptionalType Tests/OpenSwiftUIMacrosTests/EntryMacroTests.swift:161— No conventional assertion call was detected, and 16 of 16 tests in `OpenSwiftUIMacrosTests` read the same way — so this is treated as that project's convention rather than a broken test, and it does not drag the score. Two things look like this: verification that happens indirectly (an approval/verifier harness or BDD step methods), or a project of runnable samples compiled as tests, where a run that does not throw is the only check. If it is the latter, these methods genuinely verify nothing.
No direct assertions: testEntryMacroWithCustomTypeInference Tests/OpenSwiftUIMacrosTests/EntryMacroTests.swift:193— No conventional assertion call was detected, and 16 of 16 tests in `OpenSwiftUIMacrosTests` read the same way — so this is treated as that project's convention rather than a broken test, and it does not drag the score. Two things look like this: verification that happens indirectly (an approval/verifier harness or BDD step methods), or a project of runnable samples compiled as tests, where a run that does not throw is the only check. If it is the latter, these methods genuinely verify nothing.
No direct assertions: testEntryMacroWithMemberFunctionCallInference Tests/OpenSwiftUIMacrosTests/EntryMacroTests.swift:229— No conventional assertion call was detected, and 16 of 16 tests in `OpenSwiftUIMacrosTests` read the same way — so this is treated as that project's convention rather than a broken test, and it does not drag the score. Two things look like this: verification that happens indirectly (an approval/verifier harness or BDD step methods), or a project of runnable samples compiled as tests, where a run that does not throw is the only check. If it is the latter, these methods genuinely verify nothing.
No direct assertions: testPreviewExpansion Tests/OpenSwiftUIMacrosTests/PreviewMacroTests.swift:17— No conventional assertion call was detected, and 16 of 16 tests in `OpenSwiftUIMacrosTests` read the same way — so this is treated as that project's convention rather than a broken test, and it does not drag the score. Two things look like this: verification that happens indirectly (an approval/verifier harness or BDD step methods), or a project of runnable samples compiled as tests, where a run that does not throw is the only check. If it is the latter, these methods genuinely verify nothing.
No direct assertions: testPreviewExpansionPreservesSourceLineAfterAvailability Tests/OpenSwiftUIMacrosTests/PreviewMacroTests.swift:54— No conventional assertion call was detected, and 16 of 16 tests in `OpenSwiftUIMacrosTests` read the same way — so this is treated as that project's convention rather than a broken test, and it does not drag the score. Two things look like this: verification that happens indirectly (an approval/verifier harness or BDD step methods), or a project of runnable samples compiled as tests, where a run that does not throw is the only check. If it is the latter, these methods genuinely verify nothing.
No direct assertions: testPreviewExpansionPreservesSourceColumnAfterAvailability Tests/OpenSwiftUIMacrosTests/PreviewMacroTests.swift:92— No conventional assertion call was detected, and 16 of 16 tests in `OpenSwiftUIMacrosTests` read the same way — so this is treated as that project's convention rather than a broken test, and it does not drag the score. Two things look like this: verification that happens indirectly (an approval/verifier harness or BDD step methods), or a project of runnable samples compiled as tests, where a run that does not throw is the only check. If it is the latter, these methods genuinely verify nothing.
No direct assertions: testPreviewExpansionPreservesViewBuilderBody Tests/OpenSwiftUIMacrosTests/PreviewMacroTests.swift:129— No conventional assertion call was detected, and 16 of 16 tests in `OpenSwiftUIMacrosTests` read the same way — so this is treated as that project's convention rather than a broken test, and it does not drag the score. Two things look like this: verification that happens indirectly (an approval/verifier harness or BDD step methods), or a project of runnable samples compiled as tests, where a run that does not throw is the only check. If it is the latter, these methods genuinely verify nothing.
No direct assertions: testPreviewExpansionPreservesTraits Tests/OpenSwiftUIMacrosTests/PreviewMacroTests.swift:172— No conventional assertion call was detected, and 16 of 16 tests in `OpenSwiftUIMacrosTests` read the same way — so this is treated as that project's convention rather than a broken test, and it does not drag the score. Two things look like this: verification that happens indirectly (an approval/verifier harness or BDD step methods), or a project of runnable samples compiled as tests, where a run that does not throw is the only check. If it is the latter, these methods genuinely verify nothing.
No direct assertions: testExplicitBodyArgumentExpansion Tests/OpenSwiftUIMacrosTests/PreviewMacroTests.swift:217— No conventional assertion call was detected, and 16 of 16 tests in `OpenSwiftUIMacrosTests` read the same way — so this is treated as that project's convention rather than a broken test, and it does not drag the score. Two things look like this: verification that happens indirectly (an approval/verifier harness or BDD step methods), or a project of runnable samples compiled as tests, where a run that does not throw is the only check. If it is the latter, these methods genuinely verify nothing.
No direct assertions: testBodyExpressionExpansionPreservesSourceLocation Tests/OpenSwiftUIMacrosTests/PreviewMacroTests.swift:254— No conventional assertion call was detected, and 16 of 16 tests in `OpenSwiftUIMacrosTests` read the same way — so this is treated as that project's convention rather than a broken test, and it does not drag the score. Two things look like this: verification that happens indirectly (an approval/verifier harness or BDD step methods), or a project of runnable samples compiled as tests, where a run that does not throw is the only check. If it is the latter, these methods genuinely verify nothing.
No direct assertions: testEmptyViewBuilderBodyExpansion Tests/OpenSwiftUIMacrosTests/PreviewMacroTests.swift:286— No conventional assertion call was detected, and 16 of 16 tests in `OpenSwiftUIMacrosTests` read the same way — so this is treated as that project's convention rather than a broken test, and it does not drag the score. Two things look like this: verification that happens indirectly (an approval/verifier harness or BDD step methods), or a project of runnable samples compiled as tests, where a run that does not throw is the only check. If it is the latter, these methods genuinely verify nothing.
No direct assertions: testMissingBodyDiagnostic Tests/OpenSwiftUIMacrosTests/PreviewMacroTests.swift:321— No conventional assertion call was detected, and 16 of 16 tests in `OpenSwiftUIMacrosTests` read the same way — so this is treated as that project's convention rather than a broken test, and it does not drag the score. Two things look like this: verification that happens indirectly (an approval/verifier harness or BDD step methods), or a project of runnable samples compiled as tests, where a run that does not throw is the only check. If it is the latter, these methods genuinely verify nothing.
No direct assertions: aspectRatioHalfInRect Example/Tests/OpenSwiftUIUITests/Layout/AspectRatioLayoutUITests.swift:11— No conventional assertion call was detected, and 174 of 177 tests in `OpenSwiftUIUITests` read the same way — so this is treated as that project's convention rather than a broken test, and it does not drag the score. Two things look like this: verification that happens indirectly (an approval/verifier harness or BDD step methods), or a project of runnable samples compiled as tests, where a run that does not throw is the only check. If it is the latter, these methods genuinely verify nothing.
No direct assertions: aspectRatioTwoInSquare Example/Tests/OpenSwiftUIUITests/Layout/AspectRatioLayoutUITests.swift:34— No conventional assertion call was detected, and 174 of 177 tests in `OpenSwiftUIUITests` read the same way — so this is treated as that project's convention rather than a broken test, and it does not drag the score. Two things look like this: verification that happens indirectly (an approval/verifier harness or BDD step methods), or a project of runnable samples compiled as tests, where a run that does not throw is the only check. If it is the latter, these methods genuinely verify nothing.
No direct assertions: aspectRatioNilInSquare Example/Tests/OpenSwiftUIUITests/Layout/AspectRatioLayoutUITests.swift:57— No conventional assertion call was detected, and 174 of 177 tests in `OpenSwiftUIUITests` read the same way — so this is treated as that project's convention rather than a broken test, and it does not drag the score. Two things look like this: verification that happens indirectly (an approval/verifier harness or BDD step methods), or a project of runnable samples compiled as tests, where a run that does not throw is the only check. If it is the latter, these methods genuinely verify nothing.
No direct assertions: colorFixedSize Example/Tests/OpenSwiftUIUITests/Layout/FixedSizeLayoutUITests.swift:11— No conventional assertion call was detected, and 174 of 177 tests in `OpenSwiftUIUITests` read the same way — so this is treated as that project's convention rather than a broken test, and it does not drag the score. Two things look like this: verification that happens indirectly (an approval/verifier harness or BDD step methods), or a project of runnable samples compiled as tests, where a run that does not throw is the only check. If it is the latter, these methods genuinely verify nothing.
No direct assertions: trailingContentMarginsInsetFromTrailingEdge Example/Tests/OpenSwiftUIUITests/Layout/JindoTripleVStackUITests.swift:51— No conventional assertion call was detected, and 174 of 177 tests in `OpenSwiftUIUITests` read the same way — so this is treated as that project's convention rather than a broken test, and it does not drag the score. Two things look like this: verification that happens indirectly (an approval/verifier harness or BDD step methods), or a project of runnable samples compiled as tests, where a run that does not throw is the only check. If it is the latter, these methods genuinely verify nothing.
No direct assertions: centerContentMarginsIgnoredInFullWidthStack Example/Tests/OpenSwiftUIUITests/Layout/JindoTripleVStackUITests.swift:76— No conventional assertion call was detected, and 174 of 177 tests in `OpenSwiftUIUITests` read the same way — so this is treated as that project's convention rather than a broken test, and it does not drag the score. Two things look like this: verification that happens indirectly (an approval/verifier harness or BDD step methods), or a project of runnable samples compiled as tests, where a run that does not throw is the only check. If it is the latter, these methods genuinely verify nothing.
No direct assertions: bottomChildSpacingIgnoredForSideSpacing Example/Tests/OpenSwiftUIUITests/Layout/JindoTripleVStackUITests.swift:102— No conventional assertion call was detected, and 174 of 177 tests in `OpenSwiftUIUITests` read the same way — so this is treated as that project's convention rather than a broken test, and it does not drag the score. Two things look like this: verification that happens indirectly (an approval/verifier harness or BDD step methods), or a project of runnable samples compiled as tests, where a run that does not throw is the only check. If it is the latter, these methods genuinely verify nothing.
No direct assertions: belowNotchChildStopsMinimumWidthScan Example/Tests/OpenSwiftUIUITests/Layout/JindoTripleVStackUITests.swift:129— No conventional assertion call was detected, and 174 of 177 tests in `OpenSwiftUIUITests` read the same way — so this is treated as that project's convention rather than a broken test, and it does not drag the score. Two things look like this: verification that happens indirectly (an approval/verifier harness or BDD step methods), or a project of runnable samples compiled as tests, where a run that does not throw is the only check. If it is the latter, these methods genuinely verify nothing.
No direct assertions: uploadProgressAlternatives Example/Tests/OpenSwiftUIUITests/Layout/ViewThatFitsUITests.swift:12— No conventional assertion call was detected, and 174 of 177 tests in `OpenSwiftUIUITests` read the same way — so this is treated as that project's convention rather than a broken test, and it does not drag the score. Two things look like this: verification that happens indirectly (an approval/verifier harness or BDD step methods), or a project of runnable samples compiled as tests, where a run that does not throw is the only check. If it is the latter, these methods genuinely verify nothing.
Duplicated predicate Sources/OpenSwiftUI/Event/Focus/FocusBridge.swift:436— `!$0.isVisible || $0._keyViewRedirectionDisabled` appears character-identically in 2 files — Sources/OpenSwiftUI/Event/Focus/FocusBridge.swift, Sources/OpenSwiftUI/Event/Focus/FocusNavigator.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/OpenSwiftUI/View/Control/ProgressView/CircularProgressViewStyle.swift:121— `!isLinkedOnOrAfter(.v5) || labelsVisibility != .hidden` appears character-identically in 2 files — Sources/OpenSwiftUI/View/Control/ProgressView/CircularProgressViewStyle.swift, Sources/OpenSwiftUI/View/Control/ProgressView/LinearProgressViewStyle.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/OpenSwiftUI/Accessibility/AccessibilityFocusState.swift:238— `(changed && newLocation.wasRead) || oldLocation == nil` appears character-identically in 2 files — Sources/OpenSwiftUI/Accessibility/AccessibilityFocusState.swift, Sources/OpenSwiftUI/Event/Focus/FocusState.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/OpenSwiftUI/Animation/Timeline/AlwaysOn.swift:9— `(os(iOS) || os(visionOS)) && OPENSWIFTUI_LINK_BACKLIGHTSERVICES` appears character-identically in 3 files — Sources/OpenSwiftUI/Animation/Timeline/AlwaysOn.swift, Sources/OpenSwiftUI/Animation/Timeline/AlwaysOnBridge.swift, Sources/OpenSwiftUI/Animation/Timeline/TimelineView.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/OpenSwiftUICore/Event/Gesture/GestureViewModifier.swift:331— `_gestureContainer != nil && viewSubgraph.isValid` appears character-identically in 2 files — Sources/OpenSwiftUICore/Event/Gesture/GestureViewModifier.swift, Sources/OpenSwiftUICore/Event/Responder/StyledTextResponder.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/OpenSwiftUI/Integration/Graphic/AppKit/AppKitAppearanceConversions.swift:8— `canImport(AppKit) && !targetEnvironment(macCatalyst)` appears character-identically in 6 files — Sources/OpenSwiftUI/Integration/Graphic/AppKit/AppKitAppearanceConversions.swift, Sources/OpenSwiftUI/Integration/Graphic/AppKit/AppKitColorConversions.swift, Sources/OpenSwiftUI/Integration/PlatformItemList/WidgetAuxiliaryViewMetadata.swift, Sources/OpenSwiftUI/Integration/PreviewShims.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/OpenSwiftUICore/Shape/Path.swift:27— `canImport(CoreGraphics) || !OPENSWIFTUI_CF_CGTYPES` appears character-identically in 2 files — Sources/OpenSwiftUICore/Shape/Path.swift, Sources/OpenSwiftUICore/Shape/RoundedCornerStyle.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/OpenSwiftUICore/Data/EnvironmentKeys/EnvironmentAdditions.swift:176— `canImport(Darwin) && OPENSWIFTUI_LINK_COREUI` appears character-identically in 6 files — Sources/OpenSwiftUICore/Data/EnvironmentKeys/EnvironmentAdditions.swift, Sources/OpenSwiftUICore/Graphic/Color/CoreUIDefaultSystemColorDefinition.swift, Sources/OpenSwiftUICore/Graphic/Color/NamedColor.swift, Sources/OpenSwiftUICore/Graphic/Color/SystemColors.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/OpenSwiftUICore/Layout/Dynamic/DynamicLayoutView.swift:29— `inputs.requestsLayoutComputer || inputs.needsGeometry` appears character-identically in 4 files — Sources/OpenSwiftUICore/Layout/Dynamic/DynamicLayoutView.swift, Sources/OpenSwiftUICore/Layout/LayoutComputer/UnaryLayoutView.swift, Sources/OpenSwiftUICore/Layout/LayoutView.swift, Sources/OpenSwiftUICore/Layout/Modifier/DefaultPadding.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/OpenSwiftUI/Render/DisplayList/AppKitDisplayList.swift:127— `kind != .platformView && kind != .platformGroup` appears character-identically in 2 files — Sources/OpenSwiftUI/Render/DisplayList/AppKitDisplayList.swift, Sources/OpenSwiftUI/Render/DisplayList/UIKitDisplayList.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/OpenSwiftUI/Event/Platform/AppKit/AppKitGestureRecognizer.swift:53— `lastState == .possible || lastState == .ended` appears character-identically in 2 files — Sources/OpenSwiftUI/Event/Platform/AppKit/AppKitGestureRecognizer.swift, Sources/OpenSwiftUI/Event/Platform/UIKit/UIKitGestureRecognizer.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/OpenSwiftUICore/Render/DisplayList/DisplayList.swift:280— `lhs.identity == rhs.identity && lhs.version == rhs.version` appears character-identically in 2 files — Sources/OpenSwiftUICore/Render/DisplayList/DisplayList.swift, Sources/OpenSwiftUICore/Render/HoverEffect/HoverEffectContentCore.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/OpenSwiftUI/Data/State/LazyState.swift:153— `oldLocation == nil || newLocation.wasRead` appears character-identically in 2 files — Sources/OpenSwiftUI/Data/State/LazyState.swift, Sources/OpenSwiftUICore/Data/State/State.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/OpenSwiftUI/Render/DisplayList/AppKitDisplayList.swift:70— `options.isAccelerated && ORBDevice.isSupported()` appears character-identically in 3 files — Sources/OpenSwiftUI/Render/DisplayList/AppKitDisplayList.swift, Sources/OpenSwiftUI/Render/DisplayList/UIKitDisplayList.swift, Sources/OpenSwiftUICore/Render/DisplayList/CAHostingLayerPlatformDefinition.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/OpenSwiftUI/Event/Focus/Focusable.swift:1091— `os(macOS) && !targetEnvironment(macCatalyst)` appears character-identically in 2 files — Sources/OpenSwiftUI/Event/Focus/Focusable.swift, Sources/OpenSwiftUI/Event/Responder/PlatformViewResponderBase.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/OpenSwiftUICore/View/Text/FormatStyle/SafelySerializableDiscreteFormatStyle.swift:289— `self == .abbreviated || self == .condensedAbbreviated` appears character-identically in 2 files — Sources/OpenSwiftUICore/View/Text/FormatStyle/SafelySerializableDiscreteFormatStyle.swift, Sources/OpenSwiftUICore/View/Text/FormatStyle/SizeAdaptiveFormatStyle.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.
D10 · Test Quality· Test project verifies nothing · ×1
Test project verifies nothing: OpenSwiftUIMacrosTests Tests/OpenSwiftUIMacrosTests/EntryMacroTests.swift:22— No conventional assertion call was detected in 16 of 16 tests in `OpenSwiftUIMacrosTests` — the project as a whole, not one method. Two things look like this: verification that happens indirectly (an approval/verifier harness or BDD step methods), or a suite that genuinely checks nothing. If it is the latter, this project passes unconditionally and cannot fail.
No ADRs found — No ADRs found. No recognised ADR directory (`docs/adr/`, `docs/decisions/`, `adr/`, `docs/rfcs/`, an `ADR0001/` folder, or their siblings) exists anywhere in this tree. What was searched, so you can tell an empty log from a search that missed one: every directory under the tree (build output, dependencies and VCS metadata excepted), for a document that is either any non-index page inside a recognised ADR directory, whatever its name and however deeply nested (`docs/adr/use-postgres.md`, `docs/adr/2024/0001-x.md`); or a file anywhere whose name is ADR-shaped (`0001-use-postgres.md`, `adr-012-caching.md`); or, when neither turned anything up, a document carrying the decision-record signature (an "Architecture Decision Record" heading, or Status / Context / Decision / Consequences as section headings). A decision log that clears none of these — unnumbered files outside any recognised directory, without those headings — is not seen by this check and this row is then wrong. If that is your case, say so rather than renaming anything; otherwise, consider recording architectural decisions in `docs/adr/`.
D26 · Project Cohesion· Projects may be oversized for their cohesion · ×1
Projects may be oversized for their cohesion — 1 of 3 project(s) overshoot their size bounds, lowering Project Cohesion to 3.3/10. The most over is `(repository root)` (209433 LoC, 3297 module-visible types across 218 directories). Review these for cohesion — draw the boundary inside the module first (group each responsibility into its own package or directory and keep the cross-boundary members non-public), since splitting a published package moves types between packages and breaks consumers.
D28 · Secrets (history)· Rotate the exposed credentials · ×1
No ADRs — No Architecture Decision Records found — no conventional ADR directory, no numbered `NNNN-title` documents in any markup this check reads, and nothing ADR-shaped by content. Design rationale recorded elsewhere (a design-notes tree, a mailing list, pull-request discussion) is not visible to this check and is not re-findable per decision, so a future maintainer cannot ask why one choice was made and get an answer.
Logging is not universal — Only 1/2 runnable modules use logging (modules with no entry point or server are excluded — they are libraries a runnable module hosts). Silent: `Renderer/Stdout`.
No SAST REDACTED:22— 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 117208 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.
Skipped (documented): example Tests/OpenSwiftUIBridgeTests/SwiftUI/SwiftUI.EnvironmentValues.swift:12— Skipped with a documented reason — a deferral, not lazy debt: wrapped in withKnownIssue — the body is expected to fail, so its failure is not reported
Skipped (documented): pbMessage Tests/OpenSwiftUICoreTests/Graphic/VariableBlurStyleTests.swift:82— Skipped with a documented reason — a deferral, not lazy debt: GraphicsImage encode/decode is not implemented yet
Skipped (documented): maskPBMessage Tests/OpenSwiftUICoreTests/Graphic/VariableBlurStyleTests.swift:98— Skipped with a documented reason — a deferral, not lazy debt: GraphicsImage encode/decode is not implemented yet
Skipped (documented): zIndexDisplayList Tests/OpenSwiftUICoreTests/Layout/ZIndexTests.swift:20— Skipped with a documented reason — a deferral, not lazy debt: disabled by a .disabled(…) trait
Skipped (documented): withDelayExecutesAfterSpecifiedTime Tests/OpenSwiftUICoreTests/Util/TimerUtilsTests.swift:25— Skipped with a documented reason — a deferral, not lazy debt: wrapped in withKnownIssue — the body is expected to fail, so its failure is not reported
Skipped (documented): withDelayRunsOnMainRunLoop Tests/OpenSwiftUICoreTests/Util/TimerUtilsTests.swift:64— Skipped with a documented reason — a deferral, not lazy debt: wrapped in withKnownIssue — the body is expected to fail, so its failure is not reported
Skipped (documented): idViewDisplayList Tests/OpenSwiftUICoreTests/View/IDViewTests.swift:20— Skipped with a documented reason — a deferral, not lazy debt: disabled by a .disabled(…) trait
Skipped (documented): mapsEachChildAndPreservesContent Tests/OpenSwiftUITests/View/MappedViewsTests.swift:27— Skipped with a documented reason — a deferral, not lazy debt: disabled by a .disabled(…) trait
Skipped (documented): emptyContentDoesNotCallTransform Tests/OpenSwiftUITests/View/MappedViewsTests.swift:40— Skipped with a documented reason — a deferral, not lazy debt: disabled by a .disabled(…) trait
Skipped (documented): nestedMappingRestoresEachPlaceholderBody Tests/OpenSwiftUITests/View/MappedViewsTests.swift:50— Skipped with a documented reason — a deferral, not lazy debt: disabled by a .disabled(…) trait
Skipped (documented): placeholderWithoutMappingProducesNoContent Tests/OpenSwiftUITests/View/MappedViewsTests.swift:63— Skipped with a documented reason — a deferral, not lazy debt: disabled by a .disabled(…) trait
Skipped (documented): transformTracksTraitChanges Tests/OpenSwiftUITests/View/MappedViewsTests.swift:70— Skipped with a documented reason — a deferral, not lazy debt: disabled by a .disabled(…) trait
Skipped (documented): skippedOutputsStillAdvanceElementIDs Tests/OpenSwiftUITests/View/MappedViewsTests.swift:97— Skipped with a documented reason — a deferral, not lazy debt: disabled by a .disabled(…) trait
Skipped (documented): reuseOnlyReplacesTheRuleAfterSuccessfulValidation Tests/OpenSwiftUITests/View/MappedViewsTests.swift:129— Skipped with a documented reason — a deferral, not lazy debt: disabled by a .disabled(…) trait
Skipped (documented): reuseRemovesExpiredCacheEntries Tests/OpenSwiftUITests/View/MappedViewsTests.swift:169— Skipped with a documented reason — a deferral, not lazy debt: disabled by a .disabled(…) trait
Skipped (documented): selectsFirstChildThatFits Tests/OpenSwiftUITests/View/ViewThatFitsTests.swift:21— Skipped with a documented reason — a deferral, not lazy debt: disabled by a .disabled(…) trait
Skipped (documented): circle Example/Tests/OpenSwiftUIUITests/Shape/ShapeUITests.swift:24— Skipped with a documented reason — a deferral, not lazy debt: Shape color does not match
Skipped (documented): shadow Example/Tests/OpenSwiftUIUITests/Shape/ShapeUITests.swift:37— Skipped with a documented reason — a deferral, not lazy debt: Shape color does not match
Skipped (documented): defaultDateProgressLabelInitializers Example/Tests/OpenSwiftUIUITests/View/ProgressViewUITests.swift:22— Skipped with a documented reason — a deferral, not lazy debt: TextLayoutManager is not implemented yet
Skipped (documented): foundationProgress Example/Tests/OpenSwiftUIUITests/View/ProgressViewUITests.swift:27— Skipped with a documented reason — a deferral, not lazy debt: wrapped in withKnownIssue — the body is expected to fail, so its failure is not reported
Skipped (documented): logicalAndRemovedComplete Tests/OpenSwiftUICompatibilityTests/Animation/Animation/AnimationCompletionCompatibilityTests.swift:10— Skipped with a documented reason — a deferral, not lazy debt: wrapped in withKnownIssue — the body is expected to fail, so its failure is not reported
Skipped (documented): environmentKeyTransformDifferentKeyPath Tests/OpenSwiftUICompatibilityTests/Data/Environment/EnvironmentKeyTransformModifierCompatibilityTests.swift:46— Skipped with a documented reason — a deferral, not lazy debt: wrapped in withKnownIssue — the body is expected to fail, so its failure is not reported
Skipped (documented): functionalLocation Tests/OpenSwiftUICoreTests/Data/Binding/LocationTests.swift:151— Skipped with a documented reason — a deferral, not lazy debt: wrapped in withKnownIssue — the body is expected to fail, so its failure is not reported
Skipped (documented): nonEquatableValuesComparison Tests/OpenSwiftUICoreTests/Data/Environment/EnvironmentKeyTests.swift:37— Skipped with a documented reason — a deferral, not lazy debt: disabled by a .disabled(…) trait
Skipped (documented): initType Tests/OpenSwiftUICoreTests/Data/Util/BloomFilterTests.swift:11— Skipped with a documented reason — a deferral, not lazy debt: conditionally enabled — runs only when its .enabled(if:) condition holds
Outdated: package-benchmark — `package-benchmark` is resolved at 1.20.0, but 1.38.1 is the newest release tagged on https://github.com/ordo-one/package-benchmark within the same major. SwiftPM resolves from git tags, and a `from:` requirement admits every release below the next major — so `swift package update package-benchmark` reaches this one with no change to Package.swift.
Outdated: swift-collections — `swift-collections` is resolved at 1.5.0, but 1.7.5 is the newest release tagged on https://github.com/apple/swift-collections 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-collections` 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 698 file(s) — `Example/Shared/Animation/Animatable/ViewUnanimatableExample.swift`, `Example/Shared/Animation/Animation/AnimationCompleteExample.swift`, `Example/Shared/Animation/Animation/ColorAnimationExample.swift`, `Example/Shared/Animation/Animation/ElasticEaseInEaseOutAnimationExample.swift`, `Example/Shared/Animation/Animation/RepeatAnimationExample.swift`, … (+693 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 01a186e1-0014-7232-b844-a8084f6de0d7 · every finding is also locatable in findings.md, and the complete scoring record (with exit codes + durations) in sidecar.json.
Issues: 99 · Warnings: 1058 · Recommendations: 217 · Info: 41 — Appendix A · all findings · full markdown report.
Generated by Watchdog — deterministic code-health analysis. 29-10-2026 @ 08:57 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.