Public report of DevelopedByDev/autoquill_ai, published 16 November 2026. It has the same score, grades and number of findings as the full report. The details of security findings (where they are in the code, which known vulnerabilities and which passwords or keys were found) are left out, so nobody can use them against the project.
Public
Executive report Measured under the Code Assurance Index, an open standard for code quality, using its published scoring rules (rubric version 2026.11.4). Assert signed this survey and filed it in the standard's public register, where anyone can look it up by its survey ID. Check this survey → Signed and filed in the standard's public register, 16 November 2026, 15:13 UTC · Survey ID cd_f24d90e3b10b44ffac9a97c3ea9ed5e1

DevelopedByDev/autoquill_ai

Measured 16 November 2026, 15:12 UTC, at code version 066282a

First survey, so nothing to compare with yet Code coverage: not measuredTest reliability: not measured

Code coverage is not measured: Xcode and a simulator are needed to run it.

Test reliability is not measured: The suite is built by Xcode and needs an Apple platform to run.

CAI score 47.8out of 100 Weak
CriticalWeakAdequateStrongExemplary

The score is built from these lenses. Each lens grades one area of the code, such as how easy it is to change or how well it is protected. The weakest lens counts most, so one weak area pulls the score down instead of being averaged away.

A medium codebase: 28,640 lines of product code in 4 projects, tests not counted · Estimated rebuild effort: about 0.2 person-years · Weakest lens: Production Readiness, 23.2

Findings by how serious they are

1 critical 341 serious 110 minor

13 dimensions are left out of the score. For each one, we either couldn't measure it in this code, or found no evidence of the safeguard we look for, such as a tested backup restore. They count neither for nor against the score, and Limitations lists each one with its reason.

This survey was produced by

Assert small markCanine Code Analyzer
Producer
Canine Development
Analyzer
Canine Code Analyzer engine 1.0.0
Measured
16 November 2026, 15:12 UTC

A measurement, not a certificate. The Code Assurance Index records a number together with the evidence it was worked out from, so anyone can recalculate it, but it doesn't certify or guarantee the code. The standard was written by Canine Development, which also builds the Canine Code Analyzer. It is open to any tool that implements it, and today the Canine Code Analyzer is the only one that does.

The score is deterministic, which means the same code always gets the same score. We work it out with tools that follow published rules, and an AI model never decides it, so anyone who applies the same rules to the same code gets the same number. How it is done is explained under Methodology ▸

51of 51 dimensions measured by tools.
444of 452 findings point to an exact file and line, so you can open each one in the code. The other 8 concern the repository as a whole, such as missing documentation.
51dimensions across 7 lenses, read from 28,640 lines of product code in 4 projects.
Chapters

Executive summary

DevelopedByDev/autoquill_ai falls short of our standard for production because we found no working pipeline that builds or tests changes to the code and no logging, tracing or health checks in the code. It scores 47.8 out of 100 and is rated Weak, and its one critical finding is a leaked password or key.

Production Readiness, at 23.2, is the weakest lens and counts most in the score. The best first step is having someone learn and document the 88 files no active contributor knows, worth about 6.9 points. Adding an automated build and test pipeline would lift Production Readiness itself, worth about 6.8 points. Raising Production Readiness to 70 would lift the score to about 65.9.

One password or key is open to anyone who can read the repository. Replacing the exposed password or key would close this risk.

The product code is 28,640 lines, about €33,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 for The 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.
Production Readiness 23.2 · counts for 46%Maturity 54.2 · counts for 25%Code Health 74.0 · counts for 14%Architecture 82.7 · counts for 8%Performance 85.0 · counts for 4%Security and Compliance 96.2 · counts for 2%Domain Modelling 100.0 · counts for 1%

If Production Readiness rose from 23.2 to 70, the lowest score rated Strong, the score would rise from 47.8 to about 65.9.

Code composition: what the lines of code are
Product code 100%Tests 0%
Rebuild cost: about €33,000 · Estimate
Cost to rebuild€11,000 to €54,000, for 181 to 573 hours of work, about 0.2 person-years for one engineer
Difficulty of the problemStandard, judged from the kind of software and how it is built. Code that solves a harder problem, such as payments or medical bookings, costs more per line to write.
Quality factor×0.7 at a score of 48. 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.
SizeMedium: 28,640 lines of product code
What it is notNot a quotation: nobody has offered to build it for that. Not a valuation: it says nothing about what the business is worth. Not a certified figure: no professional has signed it as one.

How the estimate is made: We price the hours a team would need to write this code again, at €60 to €95 an hour. Declarations and boilerplate are priced at a fast rate and logic at a slower one, and the logic is then multiplied by the difficulty of the problem and by the quality factor. The estimate can be about 30% off either way, and it moves most with the hourly rate and the difficulty. For this code, every line is priced as straight logic, which keeps the estimate on the low side.

Top priorities

The three actions that raise the score most for the work they take. The full ranked list is in the Roadmap.

1
Resolve the 88 Orphaned file finding(s) in Knowledge Freshness — start with hotkey_handler.dart (2), transcription_settings_page.dart, push_to_talk_handler.dart.
Raises the score by about 6.9 points · Medium effort · Knowledge Freshness
2
Resolve the 1 No ADRs found finding(s) in ADR Quality — start with project.pbxproj.
Raises the score by about 6.5 points · Low effort · ADR Quality
3
Resolve the 1 `_sendToGroqAPI` spells `API` where 39 names in the project spell it… finding(s) in Naming Consistency — start with REDACTED.
Raises the score by about 2.1 points · Low effort · Naming Consistency

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 €33,000 to build again, about 0.2 person-years of work. Its weakest lens is Production Readiness, at 23.2 (Critical). 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 88 Orphaned file finding(s) in Knowledge Freshness. Of all the actions in this report, it raises the score most for the work it takes: about 6.9 points for medium effort, because it clears the 88 Knowledge Freshness findings. The next survey will show the change in the score.
Based on: the ranked actions in Top priorities, by score gain and effort
What hard-to-read code costs each year · Cost
Four dimensions measure how easy the code is to work in: two measure how tangled its logic is, one how much of it is copied, and one how well each part sticks to a single job. In this codebase they average 4.5 out of 10. Code at that level is slower to change than clean code, and we estimate the extra work at 9% to 20% on every change. The history of the code shows how much it changes: about 31,510 lines over the last 90 days, which is about 127,791 lines a year. At that pace, the extra work comes to an estimated 27.7 to 166.3 engineer-days a year, and it grows as more code changes.
How this is estimated: The number of changed lines is measured from the history of the code. The rest rests on two assumptions of our own: code scoring 8 out of 10 or more adds no extra work, and each point below 8 adds 2.5% to 5.6% to every change, never less than 2% to 5% and never more than 40% to 60% in all; and an engineer changes 150 to 400 lines in a day. The result is a range for planning, not a measurement.
Based on: Cyclomatic Complexity · Cognitive Complexity · Code Duplication · Cohesion (LCOM4) · the code's change history
What to do: Start with the files listed under Churn × Complexity Hotspots, which change often and are hard to read, because that is where the extra work is paid most often.

Architecture: 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.

4 modules, with 2 dependencies between them. Every module uses only modules listed above it, so there are no loops.

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 →1 repository2 repository.core3 repository.features4 repository.widgets
1 repository
2 repository.core
3 repository.features14
4 repository.widgets4
Uses a module listed above itPart of a loopThe module itself
1 repository2 repository.core3 repository.features4 repository.widgetsrepository1repository.core2repository.features3repository.widgets4144

At a glance — Code Health · 74.0 · Adequate · gated by D2, D4 ·

At a glance — Architecture · 82.7 · Strong ·

At a glance — Maturity · 54.2 · Adequate · gated by D34, M2 ·

At a glance — Readiness · 23.2 · Critical · gated by P1, P2, P3 ·

At a glance — Security · 96.2 · Checked 3 of 7 ·

At a glance — Domain Modelling · 100.0 · Exemplary ·

At a glance — Performance · 85.0 · Strong ·

Security & Compliance — OWASP Top-10 mapping

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 categoryFindingsSeverity
A07:2025 — Authentication Failures2High / Critical
A05:2025 — Injection1Medium

Roadmap

Top priorities: Resolve the 88 Orphaned file finding(s) in Knowledge Freshness — start with hotkey_handler.dart (2), transcription_settings_page.dart, push_to_talk_handler.dart; Add a CI workflow that builds and runs the test suite on every push/PR; Write a diagnostic trail the user can hand back with a bug report: log through `package:logging` to a file in the app's support directory that a report can attach. Start with the error paths that emit nothing — a discarded error is the failure the user cannot describe and you cannot reproduce.

Ranked by impact ÷ effort. "Helps" is the estimated gain on the 0–100 health score.

Do thisHelpsEffortDimension
Resolve the 88 Orphaned file finding(s) in Knowledge Freshness — start with hotkey_handler.dart (2), transcription_settings_page.dart, push_to_talk_handler.dart.+6.9 ptsMediumKnowledge Freshness
Resolve the 1 No ADRs found finding(s) in ADR Quality — start with project.pbxproj.+6.5 ptsLowADR Quality
Resolve the 1 `_sendToGroqAPI` spells `API` where 39 names in the project spell it… finding(s) in Naming Consistency — start with REDACTED.+2.1 ptsLowNaming Consistency
Add a CI workflow that builds and runs the test suite on every push/PR.+6.8 ptsMediumCI/CD gates
Write a diagnostic trail the user can hand back with a bug report: log through `package:logging` to a file in the app's support directory that a report can attach. Start with the error paths that emit nothing — a discarded error is the failure the user cannot describe and you cannot reproduce.+6.8 ptsMediumObservability
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.+4.9 ptsMediumArchitecture documentation
Keep a changelog (e.g. Keep-a-Changelog) recording what shipped in each release.+2.9 ptsMediumRelease Hygiene
Resolve the 3 Most significant orphaned file finding(s) in Knowledge Freshness — start with settings_bloc.dart, onboarding_bloc.dart, general_settings_page.dart.+0.4 ptsLowKnowledge Freshness

File quality

Per-file score 0–10 — a quality signature. Of 72 files carrying findings, judged against the Production bar: 0% slop · 74% mixed · 26% near-clean.

FileScoreBandWorst signal
lib/features/onboarding/presentation/bloc/onboarding_bloc.dart5.5MixedCyclomatic Complexity: OnboardingBloc._onInitializeOnboarding (cyclomatic 23)
lib/features/settings/presentation/bloc/settings_bloc.dart5.5MixedCognitive Complexity: SettingsBloc._onAutoInitializeSelectedModel (cognitive 17)
lib/features/hotkeys/handlers/transcription_hotkey_handler.dart5.5MixedCyclomatic Complexity: TranscriptionHotkeyHandler.handleHotkey (cyclomatic 37)
REDACTED5.8MixedCyclomatic Complexity: AssistantService._sendToGroqAPI (cyclomatic 26)
lib/features/transcription/presentation/bloc/transcription_bloc.dart5.9MixedCyclomatic Complexity: TranscriptionBloc._onStartTranscription (cyclomatic 31)
lib/features/mobile/presentation/bloc/mobile_onboarding_bloc.dart5.9MixedCode Duplication: Edited copy of a member (19 corresponding lines)
lib/features/mobile/presentation/widgets/mobile_keyboard_extension_step.dart6.0MixedExplicit Debt: TodoComment
lib/features/mobile/presentation/widgets/mobile_local_models_step.dart6.0MixedExplicit Debt: TodoComment
lib/features/mobile/presentation/widgets/mobile_local_models_section.dart6.0MixedExplicit Debt: TodoComment
lib/features/mobile/presentation/widgets/mobile_permissions_step.dart6.0MixedExplicit Debt: TodoComment
lib/features/hotkeys/services/clipboard_service.dart6.3MixedCyclomatic Complexity: ClipboardService.copyToClipboard (cyclomatic 24)
lib/features/hotkeys/handlers/push_to_talk_handler.dart7.0MixedCyclomatic Complexity: PushToTalkHandler.handleKeyUp (cyclomatic 39)
lib/features/onboarding/presentation/widgets/local_step.dart7.0MixedCyclomatic Complexity: LocalStep._buildModelSelectionSection (cyclomatic 20)
lib/features/settings/presentation/pages/general_settings_page.dart7.0MixedCognitive Complexity: _GeneralSettingsPageState._selectInputDevice (cognitive 18)
lib/features/mobile/presentation/widgets/mobile_api_key_step.dart7.0MixedGod Classes: MethodTooLong: _MobileApiKeyStepState.build
lib/features/onboarding/presentation/widgets/api_key_step.dart7.0MixedCyclomatic Complexity: ApiKeyStep.build (cyclomatic 24)
lib/features/settings/presentation/pages/output_settings_page.dart7.0MixedCyclomatic Complexity: OutputSettingsPage._buildLanguageSection (cyclomatic 17)
lib/features/settings/presentation/pages/assistant_settings_page.dart7.0MixedCode Duplication: Near-duplicate member family (4 members, 48 shared lines)
lib/features/onboarding/presentation/widgets/permissions_step.dart7.1MixedCyclomatic Complexity: PermissionsStep._buildPermissionCard (cyclomatic 16)
lib/features/mobile/presentation/pages/mobile_onboarding_page.dart7.1MixedCognitive Complexity: MobileOnboardingPage.build (cognitive 18)

How the grades work

Every finding carries one of four grades. Three say how serious it is. The fourth says this survey could not settle it — and it is a grade, not a gap.

Critical — 1

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 — 341

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 — 110

Recorded, with no effect on how the codebase functions. Present so the survey is complete, not because it needs doing.

Could not be resolved — 13

Something this survey could not settle from the outside, and which could be critical or serious. Either a control was required and no positive evidence of it exists in the repository — a backup job that nothing shows was ever restored from proves nothing about restores — or our own analysis could not run over that part of the tree. This is not a clean result. These are excluded from the score rather than awarded a pass, so the number on the cover neither rewards nor penalises them: if you act on this survey without resolving them, you carry that risk yourself. Each one is named under Limitations.

Methodology & how to trust this report

This survey is a deep, periodic assessment — run each sprint, monthly, or quarterly, taking the time to go wider and deeper than a quick check and surfacing in one coherent report what you'd otherwise piece together from a dozen separate tools. It scores deterministically: the same commit yields the same score, every run. All 51 evaluated dimensions are computed by tools and static analysis; no language model sets or judges any of them. Overall confidence is 0.9, the weighted average across measured dimensions.

Every figure here is one of two kinds, and we label which: ✓ Measured — a deterministic fact (LoC, complexity, coverage); ~ Modeled — an estimate from a stated model (cost, effort, value-at-risk), always a range with its assumptions, never a precise fact. We never present a modelled estimate as if it were measured. Perfect or absent scores carry their provenance too (ADR-0011): ✓ Tool-verified means the property itself was measured across the surface; ○ Nothing flagged means the probes came back clean — a claim bounded by what a repository can show; ⊘ Not evidenced means a working control (a tested restore, an automated rollback) showed no positive evidence — absence of evidence is not evidence of a control, so it's excluded from the score rather than awarded a spurious 10.

What we checked — 51 dimensions across the health lenses
D1D2D3D4D5D6D12D13D14D15D17D19D20D21D26D28D29D30D34D35D43D44AX1AX10AX3AX5AX6AX7AX9DM5GD1IC1M1M2M3M4P1P2P3P6PF3X1X12X16X18X25X27X28X3X30X5

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
  1. 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, 444 of 452 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.)
  2. Is there a tool behind the number? Every score below names the method that produced it: Roslyn, git or a scanner, not a narrative.
  3. 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.

MethodBacksVersionEvaluator
Roslyn static analysisComplexity, cohesion, coupling, dead code, API surface, layering5.3.0✓ deterministic
Native secret scannerHardcoded secrets / credentials1.0.0✓ deterministic
Canine Code Analyzer duplication detector (in-process)Code duplication1.0.0✓ deterministic
Coverage (coverlet / dotnet-coverage)Line & branch coverage10.0.400✓ deterministic
NuGet / dotnetOutdated, vulnerable & deprecated dependencies10.0.400✓ deterministic
git / LibGit2SharpChurn hotspots, knowledge concentration, history2.43.0 · 0.31.0✓ deterministic
gitleaks · semgrep · trivySecrets in history, SAST, CVEs, IaC & container, PII / GDPR1.86.0 · 0.69.3✓ deterministic

Every finding is locatable in findings.md. Run 01a1e4ea-cd78-7085-a945-ae10b44100d4.

The exact command behind every deep-scan dimension — tool, version, invocation and retained raw output — is in Appendix B — Reproduction & audit trail.

Run transparency — what happened this run

What ran differently this time — a tool absent, degraded, or that fell back to an estimate. Named openly, not folded silently into the scores. A degraded run also records its exact cause in diagnostics.md.

  • D14 License Compliance — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. This repository declares a Gradle build (build.gradle/build.gradle.kts), but the licence verdict published here was taken over its pub package dependencies. Nothing was read about its Gradle dependencies' licensing in either direction, and a clean score on this card must not be read as covering them.
  • D16 Bus Factor — not measured this run — This is a true statement about the repository that carries nothing for its owner to act on, so it is reported here rather than as a defect in their code. Single-contributor repository — bus factor is not applicable (1 contributor(s) across 262 commit(s) sampled, automation and bot accounts excluded). Concentration needs a team to concentrate: with one contributor there is nobody to spread the knowledge to, so there is nothing here for the owner to act on.
  • D19 Documentation Quality — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. Each ecosystem's manifests (what makes a folder runnable or a published package) need their own proof before D19 judges its units. Until then those folders' READMEs are judged only as documents (boilerplate, structure), never counted as complete.
  • D22 Internal API Consistency — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. D22 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: 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 — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check's reader does not cover 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 — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. 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.
  • AXB1 Runtime evidence locked — no reproducible boot — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Subject: 1 markup document(s) — HTML, Razor, JSX, Vue, Svelte or server templates. The Runtime Evidence tier boots an app only via docker-compose, an Aspire AppHost, a Dockerfile, an npm dev script, a web service's own toolchain entry point (cargo, go, dotnet, Python, Spring Boot), or an Android app's own Gradle wrapper (run on an emulator); an Apple or Flutter app needs a host it lacks. None applied, so no live runtime a11y/egress/header evidence was collected. You can widen what we reach: add a docker-compose.yml (or an Aspire AppHost) that brings the app up with its dependencies. We then boot it in an isolated sandbox and gathers real runtime evidence — you change nothing in your pipeline (no CI step, no SDK).
  • C1 Data Protection — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. 'package:hive_flutter' is imported (lib/main.dart:10), but no entity, schema, table or model declaration this check reads was found beside it, so whether personal data is stored could not be decided.
  • C3 Audit Trail — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. 'package:hive_flutter' is imported (lib/main.dart:10), but no entity, schema, table or model declaration this check reads was found beside it, so whether personal data is stored could not be decided.
  • C4 Data Retention — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. 'package:hive_flutter' is imported (lib/main.dart:10), but no entity, schema, table or model declaration this check reads was found beside it, so whether personal data is stored could not be decided.
  • C5 Data-Subject Rights — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. 'package:hive_flutter' is imported (lib/main.dart:10), but no entity, schema, table or model declaration this check reads was found beside it, so whether personal data is stored could not be decided.
  • ED5 Idempotency — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads a handler's ENTRY METHODS to decide whether its mutation is safe to re-run. On these types it walked none of them, yet the same write oracle finds a persistent write in the type — so the mutation is there and the limit is in our entry-point recognition, not in the repository. Known shapes: a handler contract method implemented as an EXPLICIT INTERFACE IMPLEMENTATION, and a STATIC handler method (the Wolverine default).
  • M3 Folder & project structure — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. Whether the tests sit apart from production code is not visible here, because the suite is not in a form this pass reads. The test-separation credit is granted rather than withheld: this is a gap in the analyzer's language coverage, not a finding about the repository's tests. You can widen what we reach: keep the test surface somewhere a reader can find it without opening a binary — an exported/checked-in test source tree beside the production code makes the suite reviewable, diffable and discoverable by tooling.
  • M4 Documentation accuracy — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. M4 checks only the claim kinds adjudicated at or above 95 % precision: links and versions (PREREGISTRATION version 9), and artefact counts an order of magnitude off. Paths, command arguments, installs, environment variables, settings, projects, packages, routes, cd targets, infrastructure products and removed modules are read but not checked, and none of them is reported or counted.
  • P5 DR & Backup — not measured this run — This is a true statement about the repository that carries nothing for its owner to act on, so it is reported here rather than as a defect in their code. No backup/snapshot/replication config, RTO/RPO or restore-procedure documentation was found — and no production persistence was detected either (no data-access packages, no data-store services, no database resources), so there is nothing in this repository whose loss a DR control would recover. If this system's data lives in a platform or ops repo we can't see, that's where the DR evidence belongs.
  • X2 Cancellation propagation — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Go, PHP, Dart, Kotlin, Ruby, Scala, Java, Python and Rust source only, and no C# was loaded, and no named async function in this repository's JavaScript/TypeScript, nor any Go, PHP or Dart function or Kotlin suspend function, makes a request that can be cancelled (fetch, axios, ky, ofetch, got, undici, node:http; net/http, net.Dial; amphp; Dio; Ktor, OkHttp), so there is nothing to judge, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
  • X24 Document value interpolated into markup unescaped — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Java, Scala, Ruby and Python source only, and no C# was loaded and no JavaScript/TypeScript, Java, Scala, Ruby or Python was found in this repository, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.

Repo exclusion declarations (.gitattributes linguist-generated/vendored, .editorconfig generated_code): none declared — every source file was scored.

Limitations & what we did not check

We assess the repository exactly as committed, and only the repository. By design we do not reach outside the source tree: the live cloud account, the running CI/CD pipeline, the host's branch-protection and approval rules, the production configuration, or a restore actually exercised against a backup are all out of scope. That boundary is a feature, not a gap — a repo-relative, deterministic scan re-runs identically on any commit and every finding opens at a real file and line, where a live audit can neither be reproduced nor traced. The visible consequence is that controls which leave no in-repo evidence are reported as "not evidenced" and excluded from the score rather than awarded a number a static scan cannot justify.

Per-dimension blind spots

For each dimension that was measured, what a static, repo-only scan structurally cannot see — the honest edge of the measurement, not a failure of it.

  • D1 Cyclomatic Complexity: Cyclomatic complexity counts branches statically — it cannot tell an essential decision tree from accidental tangle, nor see complexity that lives in data or configuration (large switch-case token tables, DSL lexers/parsers, data-as-code rule tables) rather than control flow: a tokenizer's many single-character cases read as high complexity though each branch is trivial.
  • D2 Cognitive Complexity: Cognitive-complexity heuristics approximate how hard code is to follow; genuine domain difficulty and well-named intent that eases reading are not captured.
  • D3 God Classes: "God class" is sized by members and responsibilities visible in the type — a deliberately broad facade over a coherent subsystem can read the same as an accidental grab-bag. For front-end JS the file-length check is cohesion-aware (a single-responsibility module — one class/IIFE — earns a 3× threshold), but cohesion is approximated from top-level declarations, not true dependency structure.
  • D4 Code Duplication: Duplication is token-similarity — an in-process token-stream comparison over sliding windows, with type-aware normalization — so it finds copy-paste, not semantic duplication expressed differently. Committed machine-written code (scaffolded migrations, designer/codegen output, protobuf/OpenAPI stubs, model snapshots) is EXCLUDED — its repetition is the tool's, not the team's — so the score reflects hand-written duplication only.
  • D5 Coupling: Coupling is measured between projects/assemblies — runtime coupling through DI, reflection, messaging or shared databases is invisible to a static reference graph.
  • D6 Cohesion (LCOM4): LCOM4 cohesion is syntactic — it infers connectivity from which methods touch which fields/methods by name, not from real runtime behaviour or intent.
  • D12 Dependency Hygiene: Dependency health reads manifests and lockfiles — a vulnerability in a vendored/copied dependency, or risk from how a dependency is actually used, is outside this view.
  • D13 REDACTED Scanning: REDACTED detection is signature- and entropy-based on the current tree — a secret that does not match a known pattern, or one already rotated, will not be flagged (a clean scan is "nothing matched", not "no secrets exist").
  • D14 License Compliance: License compatibility is checked against declared package metadata and a policy — mislabelled or missing license metadata, and obligations that depend on how you distribute, are not resolved here.
  • D15 Churn × Complexity Hotspots: Churn hotspots come from git history — a freshly imported or squashed repository has no churn signal, and recent rewrites can mask a historically risky file.
  • D17 Explicit Debt: Acknowledged-debt signals (TODO/FIXME, suppressions, dead code) are textual — undocumented debt that nobody marked, and debt that lives in design rather than annotations, is invisible. Committed machine-written code (scaffolded migrations, designer/codegen output, generated stubs) is excluded — it is never the team's dead code to delete.
  • D19 Documentation Quality: Documentation quality publishes two things only: a runnable or packaged unit with no example, and a multi-project root README that maps none of its parts. It does not judge clarity, and its other checks (overview, licence, boilerplate, structure, empty sections, XML-doc coverage) are withheld after adjudication: their candidates are counted in the card's gaps, not shown as rows. A false statement in a document is M4's; units are .NET projects only.
  • D20 ADR Quality: ADR quality checks the structure of the decision records present: it cannot know about decisions made and never recorded, and it does not judge how well a record argues its case. Records in a language the section lexicon does not cover are not evaluated.
  • D21 Naming Consistency: Naming consistency compares each name with the convention its structural peers follow in this repository: it cannot tell whether a consistently used name is a good one, and languages other than C# and TypeScript are not measured.
  • D26 Project Cohesion: Project focus is sized from members/namespaces per project — a project that is broad by deliberate design reads the same as one that has sprawled.
  • 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.
  • D44 Platform End-of-Life: The support table is FROZEN, so it goes out of date by losing RECALL: a release that ended support after the table was written is missed until the table is refreshed, and this dimension reading 10 is not evidence that a platform is current. Only platforms the repository DECLARES in a place this pass reads are seen — a runtime named only in a Dockerfile (D31's subject), in a CI workflow (D29's), or in a file this pass does not parse (go.mod, a Gemfile ruby directive) is invisible here, which is why a repository declaring none of them abstains rather than scoring. Only frameworks with a PUBLISHED support policy are tracked: React, Flask and Express publish none, so their age cannot be judged and their absence from a report is not a statement that they are supported.
  • AX10 Code composition: Role is inferred from namespace/folder convention, not semantics — a domain concept living in a folder named "Services" reads as application, and the split is lines-of-code, not business value. The business-logic-share score is a SOFT, FLOORED signal: it contributes to the Architecture lens but is floored at the Critical gate, so an infrastructure-heavy design (a gateway, an ETL, a driver) is legitimately low without being nuked to zero.
  • AX9 CQS / query purity: Handlers are found by interface/name convention — a query handler using neither is not seen. Mutation is a resolved write/publish invocation (SaveChanges/repository/bus), so a write hidden behind a hand-rolled wrapper, reflection, or a string-keyed service locator resolves to a non-persistence type and isn't flagged; it detects that a query writes state, not whether the write is a legitimate read-side cache update. Clean means "no resolved write/publish in a query body", not a proof of CQS purity.
  • M4 Documentation accuracy: Documentation accuracy checks links, versions and artefact counts against the tree: other claims (paths, commands, settings, routes) are read but not checked, and it cannot run the onboarding or measure how long a real new joiner takes.
  • 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.

Dimensions

D1 · Cyclomatic Complexity6.5 / 10Adequate✓ Tool-verified

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.

Maturity: Documented → Verified → Prevented · effective 6.5 / 10 · rule-coverage 100% · ceiling Prevented

31 method(s) exceeded the cyclomatic complexity threshold of 15; the worst was PushToTalkHandler.handleKeyUp at 39.

PushToTalkHandler.handleKeyUp (cyclomatic 39)lib/features/hotkeys/handlers/push_to_talk_handler.dart:309
PushToTalkHandler._ensureRecordingCleanup (cyclomatic 39)lib/features/hotkeys/handlers/push_to_talk_handler.dart:857
TranscriptionHotkeyHandler.handleHotkey (cyclomatic 37)lib/features/hotkeys/handlers/transcription_hotkey_handler.dart:69
PushToTalkHandler.handleKeyDown (cyclomatic 31)lib/features/hotkeys/handlers/push_to_talk_handler.dart:113
TranscriptionBloc._onStartTranscription (cyclomatic 31)lib/features/transcription/presentation/bloc/transcription_bloc.dart:126

+ 26 more group(s) — more in Appendix A; the complete list is findings.md.

What to do

  1. Bring the 31 bodies over 15 down to 15 or less in Cyclomatic Complexity — start with PushToTalkHandler.handleKeyUp (cyclomatic 39), PushToTalkHandler._ensureRecordingCleanup (cyclomatic 39), TranscriptionHotkeyHandler.handleHotkey (cyclomatic 37). — 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 31 together lifts Cyclomatic Complexity from 6.5 to about 10.0/10, projected with the scoring formula itself and assuming each lands exactly at 15.

Detailed fixes: d1_recommendation.md · top locations in Appendix A, every location in findings.md.

D2 · Cognitive Complexity2.2 / 10Critical✓ Tool-verified

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.

Maturity: Documented → Verified → Prevented · effective 2.2 / 10 · rule-coverage 100% · ceiling Prevented

53 method(s) exceeded the cognitive complexity threshold of 15; the worst was TranscriptionHotkeyHandler.handleHotkey at 122.

TranscriptionHotkeyHandler.handleHotkey (cognitive 122)lib/features/hotkeys/handlers/transcription_hotkey_handler.dart:69
PushToTalkHandler._ensureRecordingCleanup (cognitive 105)lib/features/hotkeys/handlers/push_to_talk_handler.dart:857
AssistantService._sendToGroqAPI (cognitive 93)REDACTED:449
PushToTalkHandler.handleKeyUp (cognitive 88)lib/features/hotkeys/handlers/push_to_talk_handler.dart:309
OnboardingBloc._onCheckPermissions (cognitive 83)lib/features/onboarding/presentation/bloc/onboarding_bloc.dart:401

+ 48 more group(s) — more in Appendix A; the complete list is findings.md.

What to do

  1. Bring the 11 bodies over 60 down to 60 or less in Cognitive Complexity — start with TranscriptionHotkeyHandler.handleHotkey (cognitive 122), PushToTalkHandler._ensureRecordingCleanup (cognitive 105), AssistantService._sendToGroqAPI (cognitive 93). — This score is capped by its worst body, so a finding fixed alone moves it by almost nothing — the next one down takes its place. Refactoring these 11 together lifts Cognitive Complexity from 2.2 to about 4.2/10, projected with the scoring formula itself and assuming each lands exactly at 60; a cleaner split scores higher.

Detailed fixes: d2_recommendation.md · top locations in Appendix A, every location in findings.md.

D3 · God Classes5.3 / 10Adequate✓ Tool-verified

What it measures: Over-large classes that try to do too much ("god classes").

Method: God-class detection by line and method-count thresholds per logical type (partial classes unified), filtered for generated code and registration/contract false positives. Deterministic.

Maturity: Documented → Verified → Prevented · effective 5.3 / 10 · rule-coverage 100% · ceiling Prevented

52 god class(es) detected.

MethodTooLong: OnboardingPage.build · ×36lib/features/onboarding/presentation/pages/onboarding_page.dart:21
ClassTooLong: SettingsBloc · ×8lib/features/settings/presentation/bloc/settings_bloc.dart:18
FileTooLong: bloc/settings_bloc.dart · ×6lib/features/settings/presentation/bloc/settings_bloc.dart
TooManyMethods: SettingsBloc · ×2lib/features/settings/presentation/bloc/settings_bloc.dart:18

What to do

  1. Resolve the 36 MethodTooLong finding(s) in God Classes — start with output_settings_page.dart (3), general_settings_page.dart (3), local_step.dart (2). — One of this dimension's main actionable groups (36 warning-level).
  2. Resolve the 8 ClassTooLong finding(s) in God Classes — start with settings_bloc.dart, onboarding_bloc.dart, general_settings_page.dart. — One of this dimension's main actionable groups (8 warning-level).
  3. Resolve the 6 FileTooLong finding(s) in God Classes — start with settings_bloc.dart, onboarding_bloc.dart, general_settings_page.dart. — One of this dimension's main actionable groups (6 warning-level).

Detailed fixes: d3_recommendation.md · top locations in Appendix A, every location in findings.md.

D4 · Code Duplication1.2 / 10Critical✓ Tool-verified

What it measures: How much of the production code is copy-pasted: the share of production lines inside a reported copy (every copy of a duplicated block or of an edited member, each line once), 10 at none and 0 at a quarter of the lines.

Method: Code duplication via token-stream sliding windows with type-aware normalization (locals masked, type names preserved), scored on the share of production lines inside a reported copy (each line once; 10 at none, 0 at a quarter). Deterministic.

Maturity: Documented → Verified → Prevented · effective 1.2 / 10 · rule-coverage 100% · ceiling Verified

123 duplicated block group(s) detected. 22.1 % of the production lines (6,334 of 28,640) are in a reported copy. A further 40 rows report members as variants of one another; the share counts each copied line once, however many rows cite it.

Duplicated block (14 lines × 2) · ×6lib/features/onboarding/presentation/bloc/onboarding_bloc.dart:1224
Duplicated block (13 lines × 2) · ×6lib/features/home/presentation/pages/home_page.dart:86
Duplicated block (18 lines × 2) · ×5lib/features/mobile/presentation/widgets/mobile_keyboard_extension_step.dart:106
Duplicated block (17 lines × 2) · ×5lib/features/mobile/presentation/widgets/mobile_api_key_step.dart:69
Duplicated block (12 lines × 3) · ×4lib/features/mobile/presentation/widgets/mobile_local_models_step.dart:468

+ 114 more group(s) — more in Appendix A; the complete list is findings.md.

What to do

  1. Resolve the 6 Duplicated block (14 lines × 2) finding(s) in Code Duplication — start with onboarding_bloc.dart, hotkeys_step.dart, assistant_settings_page.dart. — One of this dimension's main actionable groups (6 warning-level).
  2. Resolve the 6 Duplicated block (13 lines × 2) finding(s) in Code Duplication — start with onboarding_bloc.dart (2), home_page.dart, permissions_step.dart. — One of this dimension's main actionable groups (6 warning-level).
  3. Resolve the 5 Duplicated block (18 lines × 2) finding(s) in Code Duplication — start with mobile_local_models_section.dart (2), mobile_permissions_step.dart (2), mobile_keyboard_extension_step.dart. — One of this dimension's main actionable groups (5 warning-level).

Detailed fixes: d4_recommendation.md · top locations in Appendix A, every location in findings.md.

D5 · Coupling10.0 / 10Exemplary✓ 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.

Maturity: Documented → Verified → Prevented · effective 10.0 / 10 · rule-coverage 100% · ceiling Prevented

3 production modules (Gradle+pub), 0 dependency cycle(s), 0 unstable depended-on module(s). Read from the build's own module declarations; edges a convention plugin adds from buildSrc or build-logic are not visible there; 0 module(s) off the main sequence, with abstractness counted on 2 of the 3 (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).

✓ On the Gold path — maintain.

Detailed fixes: d5_recommendation.md.

D6 · Cohesion (LCOM4)8.3 / 10Strong✓ Tool-verified

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.

Maturity: Documented → Verified → Prevented · effective 8.3 / 10 · rule-coverage 100% · ceiling Verified

5 of 36 classes have LCOM4 above 3.

Low cohesion: SettingsBloc (LCOM4 41) · ×5lib/features/settings/presentation/bloc/settings_bloc.dart:18

What to do

  1. Resolve the 5 Low cohesion finding(s) in Cohesion (LCOM4) — start with settings_bloc.dart, onboarding_bloc.dart, mobile_onboarding_bloc.dart. — One of this dimension's main actionable groups (5 warning-level).

Detailed fixes: d6_recommendation.md · top locations in Appendix A, every location in findings.md.

D12 · Dependency Hygiene10.0 / 10Exemplary✓ Tool-verified

What it measures: Whether dependencies are current, not deprecated, and not bloated. Known vulnerabilities are D30's.

Method: Manifest scan via dotnet list package across all projects; worst-signal-per-package deduction (capped-linear for deprecation, prerelease and outdated) per KLoC. Known-vulnerable packages are D30's and are not charged here (rubric-2026.11.2). Exhaustive.

Maturity: Documented → Verified → Prevented · effective 10.0 / 10 · rule-coverage 100% · ceiling Verified

1 outdated direct SwiftPM dependencies, 0 pinning defect(s). SwiftPM has no package registry: a dependency is a repository URL and its releases are that repository's semver tags, so currency is answered by listing tags rather than by querying an index. Only a newer tag on the SAME MAJOR is reported — a `from:` requirement admits everything below the next major and nothing above it, so a major crossing needs a Package.swift edit rather than an update, and naming the update as its remedy would be wrong. Whether any dependency is DEPRECATED or ABANDONED is not graded and cannot be: a repository publishes no such marker, and there is no registry that could carry one. Known CVEs in this dependency graph are D30's question. 1 third-party CocoaPods resolved by a committed Podfile.lock were graded against the CocoaPods trunk (cdn.cocoapods.org): a pod is behind only when the trunk lists a newer release on the same major, which `pod update` reaches under a `~>` requirement. A pod sourced from a path, git URL or local podspec has no trunk release to compare and is not asked about. Carthage dependencies are not graded.

Outdated: Sparkle

✓ On the Gold path — maintain.

Detailed fixes: d12_recommendation.md · top locations in Appendix A, every location in findings.md.

D13 · REDACTED Scanning10.0 / 10Exemplary○ Nothing flagged

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.

Maturity: Documented → Verified → Prevented · effective 10.0 / 10 · rule-coverage 100% · ceiling Prevented

REDACTED scan ran and found no leaked secrets.

✓ On the Gold path — maintain.

Detailed fixes: d13_recommendation.md.

D14 · License Compliance10.0 / 10Exemplary○ Nothing flagged

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.

Maturity: Documented → Verified → Prevented · effective 10.0 / 10 · rule-coverage 100% · ceiling Verified

0 of 115 resolved pub package(s) use a banned license. Licences were read from pub.dev's analysis of each package's licence file, over every package this repository's pubspec.lock resolves from pub.dev, direct and transitive, at the locked version; the 2 package(s) the lock marks direct dev are excluded, and SDK, path and git packages have no registry release to read. pub.dev analyses only recent releases, so for 48 package(s) locked at an older version the licence read is that of the package's latest analysed release, not of the locked one. 2 of them carry no licence pub.dev recognises; that is missing data, not a violation, and none of them is charged. ★ COVERAGE OF THIS VERDICT: it grades this repository's pub package dependencies and nothing else. The repository also declares a Gradle build (build.gradle/build.gradle.kts), and the licences of those dependencies were NOT read by this pass — a gap in this engine's coverage, not a statement about them. So this result says the graded closure carries no banned licence; it does NOT say this repository's licensing is clear.

✓ On the Gold path — maintain.

Detailed fixes: d14_recommendation.md.

D15 · Churn × Complexity Hotspots9.3 / 10Stronggated by 16 serious findings✓ Tool-verified

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.

Maturity: Documented → Verified → Prevented · effective 9.3 / 10 · rule-coverage 100% · ceiling Documented

Top hotspots: lib/features/hotkeys/handlers/push_to_talk_handler.dart (14×39=546); lib/features/hotkeys/handlers/transcription_hotkey_handler.dart (9×37=333); lib/features/onboarding/presentation/bloc/onboarding_bloc.dart (9×23=207)

Hotspot: lib/features/hotkeys/handlers/push_to_talk_handler.dart · ×16lib/features/hotkeys/handlers/push_to_talk_handler.dart:309

What to do

  1. Resolve the 16 Hotspot finding(s) in Churn × Complexity Hotspots — start with push_to_talk_handler.dart, transcription_hotkey_handler.dart, onboarding_bloc.dart. — One of this dimension's main actionable groups (16 warning-level).

Detailed fixes: d15_recommendation.md · top locations in Appendix A, every location in findings.md.

D17 · Explicit Debt10.0 / 10Stronggated by 6 serious findings✓ Tool-verified

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.

Maturity: Documented → Verified → Prevented · effective 10.0 / 10 · rule-coverage 100% · ceiling Prevented

6 deducted task-comment markers across 28640 LoC (0.0/KLoC) → score 10.0. Task comments only: this repository's language is read without a compiler, so D17's suppression, dead-code and commented-out-code arms did not run and this score counts fewer marker kinds than a .NET repository's would.

TodoComment · ×6lib/features/mobile/presentation/widgets/mobile_keyboard_extension_step.dart:177

What to do

  1. Resolve the 6 TodoComment finding(s) in Explicit Debt — start with mobile_permissions_step.dart (2), mobile_keyboard_extension_step.dart, mobile_local_models_section.dart. — One of this dimension's main actionable groups (6 warning-level).

Detailed fixes: d17_recommendation.md · top locations in Appendix A, every location in findings.md.

D19 · Documentation Quality10.0 / 10Exemplary○ Nothing flagged

What it measures: Whether the project's documentation is clear, complete, and useful.

Method: Every README, docs/ document and root guide parsed by its markup and measured in Unicode letters. Published: a runnable or packaged .NET project whose README (or a document it links, or a root guide) shows no example, and a root README naming none of three or more projects. Overview, licence, boilerplate, wall-of-text, empty-section and XML-doc rows are measured and withheld (counted in gaps) after adjudication. Deterministic, exhaustive, advisory.

Maturity: Documented → Verified → Prevented · effective 10.0 / 10 · rule-coverage 100% · ceiling Documented

1 of 1 documentation facets pass in full. 3 document(s) read across 1 unit(s).

✓ On the Gold path — maintain.

Detailed fixes: d19_recommendation.md.

D20 · ADR Quality0.0 / 10Critical✓ Tool-verified

What it measures: Whether architecture decisions are recorded well (context, decision, consequences).

Method: Every ADR read by its section structure: nine located rules (a missing Decision, Context or Consequences section, a stale status, two records deciding the same question, a dangling supersede link, a number-only title, a single option, no named cost, no status where the log uses one, no enforcement field where the log adopted one), each a fixed deduction from 10; the score is the mean over evaluated records. Deterministic, no model. Advisory.

Maturity: Documented → Verified → Prevented · effective 0.0 / 10 · rule-coverage 100% · ceiling Documented

No architecture decision records were found.

No ADRs foundmacos/Runner.xcodeproj/project.pbxproj:1

What to do

  1. Resolve the 1 No ADRs found finding(s) in ADR Quality — start with project.pbxproj. — One of this dimension's main actionable groups (1 recommendation-level).

Detailed fixes: d20_recommendation.md · top locations in Appendix A, every location in findings.md.

D21 · Naming Consistency7.5 / 10Strong✓ Tool-verified

What it measures: Whether names — types, methods, variables — are clear and consistent.

Method: Seven vocabulary-free rules (N1-N7) mine each naming convention from the repository and flag a name that breaks a convention its structural peers in the same unit follow; production C# and TypeScript, each its own population. Deterministic, no model, no sample. Advisory.

Maturity: Documented → Verified → Prevented · effective 7.5 / 10 · rule-coverage 100% · ceiling Verified

1 naming inconsistencies among 40 declarations measured against a convention their peers follow.

`_sendToGroqAPI` spells `API` where 39 names in the project spell it `Api`REDACTED:449

What to do

  1. Resolve the 1 `_sendToGroqAPI` spells `API` where 39 names in the project spell it… finding(s) in Naming Consistency — start with REDACTED. — One of this dimension's main actionable groups (1 recommendation-level).

Detailed fixes: d21_recommendation.md · top locations in Appendix A, every location in findings.md.

D26 · Project Cohesion5.0 / 10Adequate✓ Tool-verified

What it measures: Whether each project is a focused, coherent unit rather than an oversized grab-bag.

Method: Project size overshoot penalties (LoC / public-type count / namespace count, 2-of-3 flag) weighted by log magnitude. Exhaustive across projects, deterministic.

Maturity: Documented → Verified → Prevented · effective 5.0 / 10 · rule-coverage 100% · ceiling Documented

1 of 4 build units (Gradle, Xcode, pub) flagged as possibly oversized/incoherent.

Projects may be oversized for their cohesionpubspec.yaml:1

What to do

  1. Resolve the 1 Projects may be oversized for their cohesion finding(s) in Project Cohesion — start with pubspec.yaml. — 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.

D28 · Secrets (history)9.0 / 10Adequategated by 1 critical finding✓ Tool-verified

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.

Maturity: Documented → Verified → Prevented · effective 9.0 / 10 · rule-coverage 100% · ceiling Documented

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

  1. Resolve the 1 REDACTED finding(s) in Secrets (history) — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
  2. 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.

D29 · Static Analysis (SAST)9.9 / 10Exemplary✓ Tool-verified

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).

Maturity: Documented → Verified → Prevented · effective 9.9 / 10 · rule-coverage 100% · ceiling Documented

1 finding(s): 0 critical, 0 high, 0 medium, 1 low.

REDACTED

✓ On the Gold path — maintain.

Detailed fixes: d29_recommendation.md · top locations in Appendix A, every location in findings.md.

D30 · Dependency Vulnerabilities10.0 / 10Exemplary○ Nothing flagged

What it measures: Whether any dependency has a known published vulnerability (CVE), direct or transitive, in ANY ecosystem the repository declares — Dart pub, Elixir and Erlang via Hex, Go modules, Java and Kotlin via Maven/Gradle, JavaScript/npm, .NET/NuGet, PHP/Composer, Python/PyPI, RubyGems, Rust/Cargo and Swift.

Method: Dependency-CVE scan across every ecosystem the repository declares, scored ONCE. Three sources are unioned and deduplicated by advisory identity (rule id + alias closure, CVE<->GHSA) scoped to package+version, keeping the worst severity: `osv-scanner --recursive` over osv.dev for Dart pub, Elixir/Hex (and Erlang, whose `rebar.lock` syft first converts to a CycloneDX SBOM the scanner reads, with rows attributed back to the lock), Go, Java and Kotlin via Maven/Gradle (and Scala, whose sbt build's pinned direct declarations are written into a CycloneDX SBOM the scanner reads, with rows attributed back to the build file), npm, PHP/Composer, Python/PyPI, RubyGems, Rust/Cargo and Swift; `trivy fs --scanners vuln` for npm lockfiles; and `dotnet list package --vulnerable --include-transitive` for NuGet (with per-advisory collapse of the project x target-framework fan-out), plus a DECLARED-dependency arm that resolves a published gem's gemspec against rubygems.org where no Gemfile.lock is committed. `SeverityScore(c,h,m,l, normalizer 8.0)`. NotApplicable only when NO ecosystem is readable; if any applicable ecosystem could not be scanned the findings are REPORTED and the score is withheld. Supersedes the npm and OSV arms, retired 2026-09-05. Advisory since rubric-2026.11.2 (CAI decision 0006): every row is a match against a vulnerability database that changes daily, so the reading is shown and never moves a scored dimension, lens or the headline.

Maturity: Documented → Verified → Prevented · effective 10.0 / 10 · rule-coverage 100% · ceiling Documented

No known-vulnerable dependencies in any ecosystem this repository declares.

✓ On the Gold path — maintain.

Detailed fixes: d30_recommendation.md.

D34 · Knowledge Freshness0.0 / 10Critical✓ Tool-verified

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.

Maturity: Documented → Verified → Prevented · effective 0.0 / 10 · rule-coverage 100% · ceiling Documented

91 of 91 significant source file(s) are orphaned — their living knowledge has decayed to nothing, so no one currently understands them. The largest is lib/features/settings/presentation/bloc/settings_bloc.dart. Counted over 91 of the 130 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.

Orphaned file · ×88lib/features/settings/presentation/pages/transcription_settings_page.dart:1
Most significant orphaned file · ×3lib/features/settings/presentation/bloc/settings_bloc.dart:1
Dormant codebase

What to do

  1. Resolve the 88 Orphaned file finding(s) in Knowledge Freshness — start with hotkey_handler.dart (2), transcription_settings_page.dart, push_to_talk_handler.dart. — One of this dimension's main actionable groups (88 recommendation-level).
  2. Resolve the 3 Most significant orphaned file finding(s) in Knowledge Freshness — start with settings_bloc.dart, onboarding_bloc.dart, general_settings_page.dart. — One of this dimension's main actionable groups (3 recommendation-level).
  3. Resolve the 1 Dormant codebase finding(s) in Knowledge Freshness. — One of this dimension's main actionable groups (1 recommendation-level).

Detailed fixes: d34_recommendation.md · top locations in Appendix A, every location in findings.md.

D35 · Change Coupling9.2 / 10Stronggated by 5 serious findings✓ Tool-verified

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.

Maturity: Documented → Verified → Prevented · effective 9.2 / 10 · rule-coverage 100% · ceiling Documented

Strongest change-coupling: settings_event.dart↔settings_state.dart 96%; onboarding_event.dart↔onboarding_state.dart 90%; clipboard_service.dart↔transcription_bloc.dart 67%

Change coupling: settings_event.dart ↔ settings_state.dart · ×4lib/features/settings/presentation/bloc/settings_event.dart:1
Change-coupling hub: transcription_hotkey_handler.dart → REDACTED, push_to_talk_handler.dart, transcription_bloc.dartlib/features/hotkeys/handlers/transcription_hotkey_handler.dart

What to do

  1. Resolve the 4 Change coupling finding(s) in Change Coupling — start with settings_event.dart, onboarding_event.dart, clipboard_service.dart. — One of this dimension's main actionable groups (4 warning-level).
  2. Resolve the 1 Change-coupling hub finding(s) in Change Coupling — start with transcription_hotkey_handler.dart. — One of this dimension's main actionable groups (1 warning-level).

Detailed fixes: d35_recommendation.md · top locations in Appendix A, every location in findings.md.

D43 · Malicious Dependencies10.0 / 10Exemplary✓ Tool-verified

What it measures: Whether any dependency the repository declares is published as MALICIOUS rather than merely vulnerable — a package that is an attacker's work, in any ecosystem osv-scanner reads. Reported apart from D30 because the answer is binary: there is no safe version to upgrade to, and the fix is to remove the package and rotate every credential it could have read.

Method: The same dependency scan D30 reads, partitioned on the scanner's own classification rather than rescanned: a row is MALICIOUS when its id is in the `MAL-` space (the ossf/malicious-packages feed) OR its `database_specific.cwe_ids` carries `CWE-506` ("Embedded Malicious Code"). Both channels are structural; the summary text is deliberately NOT read, because a malicious-package record whose summary says only "Critical severity vulnerability" is a real shape ([GHSA redacted]) and a text matcher misses it. Scored BINARY: any surviving row is 0, whatever its severity and however many CVEs sit beside it — a hostile dependency is not a quantity. Applicability and degradation are D30's: NotApplicable only when no ecosystem is readable, and an unscannable ecosystem degrades rather than reading clean. Advisory since rubric-2026.11.2 (CAI decision 0006): the malicious-package feed is a database that changes daily, so the reading is shown and never moves a scored dimension, lens or the headline.

Maturity: Documented → Verified → Prevented · effective 10.0 / 10 · rule-coverage 100% · ceiling Documented

No dependency in any ecosystem this repository declares is published as malicious.

✓ On the Gold path — maintain.

Detailed fixes: d43_recommendation.md.

D44 · Platform End-of-Life10.0 / 10Exemplary✓ Tool-verified

What it measures: Whether anyone still ships security patches for the platform this repository RUNS ON — the runtime it pins and the framework majors its own constraints hold it to. Separate from D12 because the question differs: a current Django on an end-of-life Python is perfectly up to date and completely unsupported, and the fix is a migration rather than a version bump. What the repository says it merely SUPPORTS is never charged.

Method: End-of-life PLATFORM read from the repository's own declarations and graded against a FROZEN, dated table of vendor support dates — no network, no feed, no API, so this dimension answers identically inside a closed scan fence. Two subjects: a RUNTIME the project pins (a single or all-end-of-life TargetFramework, a .nvmrc or .python-version, a requires-python CAP) and a FRAMEWORK major a dependency constraint cannot move off (a caret, tilde or exact version; `vue@^2.7.16` pins Vue 2). A FLOOR is deliberately never charged — `requires-python = ">=3.8"` states what a package SUPPORTS, not what it runs on — and a multi-target project is charged only when EVERY target is out of support. Runtime 4.0/product capped 8.0, framework 1.5 capped 4.5. The table is safe to freeze because a statement about support that ended in the past cannot become false: it loses recall as it ages, never precision, and a test asserts every entry predates the freeze date. Disjoint from D31 (a container image's OS layer) and D29 (the toolchain a CI workflow installs). Abstains when the repository declares no platform this pass reads — never scores it clean.

Maturity: Documented → Verified → Prevented · effective 10.0 / 10 · rule-coverage 100% · ceiling Documented

0 end-of-life runtime(s) and 0 end-of-life framework(s), read from 2 platform declaration(s) and 0 dependency declaration(s). This dimension reads what the repository says about ITSELF — a pinned target framework, a version file, a capped requires-python, a Rust toolchain pin, a framework major a constraint cannot move off. A FLOOR is deliberately never charged: `requires-python = ">=3.8"` states what the package SUPPORTS, not what it runs on, and a well-maintained library declares exactly that while running its own CI on a current release. The end-of-life facts are FROZEN and dated, so this dimension needs no network and answers identically inside a closed scan fence; as the table ages it loses recall and never precision, because a statement about support that ended in the past cannot become false. The OS layer of a container image is D31's question and the toolchain a CI workflow installs is D29's; this row is neither.

✓ On the Gold path — maintain.

Detailed fixes: d44_recommendation.md.

Frontend & cross-cutting dimensions

R = React/JS · M = Maturity · P = Readiness.

AX1 · Captive dependencies10.0 / 10Exemplary✓ Tool-verified

Other · Architecture — Whether any singleton service captures a scoped/transient dependency — a silent lifetime/threading bug.

Method: Roslyn scan: DI registrations parsed from AddSingleton/Scoped/Transient; each singleton checked for captured shorter-lifetime dependencies. Exhaustive, deterministic.

AX10 · Code composition9.6 / 10Exemplary✓ Tool-verified

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.

AX3 · Project dependency cycles10.0 / 10Exemplary✓ Tool-verified

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.

AX5 · Architecture & structure10.0 / 10Exemplary✓ Tool-verified

Other · Architecture — Whether the codebase has a recognisable, scale-appropriate structure (a named architectural style, or modular enough for its size) rather than being an ad-hoc ball of mud.

Method: Roslyn plus csproj analysis: architecture style detection (DDD, clean, vertical-slice, CQRS) and structure fitness for repo size. Deterministic.

AX6 · Interface segregation10.0 / 10Exemplary✓ Tool-verified

Other · Architecture — Whether interfaces stay focused rather than fat — the Interface-Segregation principle (SOLID 'I').

Method: Roslyn scan: public interface declared-member counts (accessors fold into their property/event); fat-interface threshold (over 15 declared members) flagged per type. Each finding also reports the distinct-OPERATION count — members counted by name, so an overload group counts once — which decides whether it states the caller-side ISP harm or the implementer-side burden of an overload set. TypeScript: exported interfaces that declare behaviour, counted over their REQUIRED operations (method signatures and function-typed properties with no `?`, once per signature) — data-shape interfaces and ambient .d.ts declarations are outside the population; JavaScript declares no interfaces and is not applicable. Deterministic, type-level.

AX7 · Slice cohesion5.6 / 10Adequate✓ Tool-verified

Other · Architecture — Whether feature slices stay independent (no direct cross-slice references) — the discipline that makes vertical-slice architecture pay off.

Method: Roslyn scan (vertical-slice gated): feature slices resolved from namespaces (.Features.*, .Slices.*) or project names; cross-slice type references detected. Deterministic, traceable.

  • `HotkeyHandler` (slice 'hotkeys') depends on `AssistantService` from slice 'assistant'. — lib/features/hotkeys/core/hotkey_handler.dart:37

What to do

  • Keep slices independent: share cross-slice needs via an explicit contract/shared-kernel, not direct references between slices.
AX9 · CQS / query purity10.0 / 10Exemplary✓ Tool-verified

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.

DM5 · Encapsulated state10.0 / 10Exemplary✓ Tool-verified

Other · Domain Modelling — Whether an entity protects its own invariants — a class whose identity is derived from its fields (value equality) but whose fields are publicly mutable bypasses that invariant. Encapsulated state keeps identity-bearing fields immutable.

Method: Roslyn (DDD-gated): entities scanned for publicly writable state — public setters, and (C#/VB) own mutable collections handed out through an auto-property, a public field or a bare-field expression getter, where a computed/copying getter is never charged. One finding per entity; score softened when Marten/EF rehydration frameworks present. Deterministic, framework-aware.

Coverage: Population: entities by convention; encapsulation (setter shape) checked exhaustively within the set.

GD1 · Unfinished & placeholder code10.0 / 10Exemplary○ Nothing flagged

Other · Code Health — Unreviewed-generation residue in this repository's Dart: methods whose whole body still throws UnimplementedError or a "not implemented" error, and placeholder text (lorem ipsum, changeme/replace_me…) left in strings of non-test, non-generated code. Scored as a quality signature, never as a claim about authorship.

Method: Roslyn syntax scan: NotImplementedException throws and placeholder string literals in non-test, non-generated shipped code. Deterministic, code-shape signature.

IC1 · Incompleteness & stubs10.0 / 10Exemplary○ Nothing flagged

Other · Code Health — Unfinished work detected by code SHAPE, not keywords, in this repository's Dart: methods that only throw UnimplementedError or a "not implemented" exception, methods that take inputs and return a constant or do nothing, dead `if (false)` branches, and skeleton classes most of whose methods are holes.

Method: Roslyn syntax scan: incompleteness by code shape (constant-returning methods, async-never-await, #if false branches, guards that return what the code already falls through to, tests an earlier guard already decided, comparisons against NaN, skeleton types), not keyword-gated. Deterministic, code-shape heuristic.

M1 · Documentation (README)8.0 / 10Strong✓ Tool-verified

Maturity · Maturity — Whether the repository and its projects have a README, and whether it is substantive.

Method: Filesystem scan: README presence, word count, and headings for depth; git history for staleness. Exhaustive across root and project dirs, deterministic.

M2 · Architecture documentation2.0 / 10Critical✓ Tool-verified

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.
M3 · Folder & project structure10.0 / 10Exemplary✓ Tool-verified

Maturity · Maturity — Whether the repository is organised deliberately: production code and tests are set apart in a way its ecosystem or the repository itself declares.

Method: Filesystem scan: src/test folder separation and namespace-prefix consistency (majority RootNamespace agreement). Exhaustive across projects, deterministic.

M4 · Documentation accuracy8.0 / 10Strong✓ Tool-verified

Maturity · Maturity — Whether the project's current-state documentation describes the code that exists.

Method: Every current-state document's checkable claims looked up in the tree (links, versions, and artefact counts an order of magnitude off), plus two README checks: an advertised infrastructure product with no footprint, and a module the CHANGELOG records as removed. Deterministic, no model. Advisory.

  • README.md links to `BUILD_INSTRUCTIONS.md`, but `BUILD_INSTRUCTIONS.md` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — README.md:402

What to do

  • Reconcile the README with reality: README.md links to `BUILD_INSTRUCTIONS.md`, but `BUILD_INSTRUCTIONS.md` does not exist.
P1 · CI/CD gates0.0 / 10Critical✓ Tool-verified

Readiness · Readiness — Whether an automated pipeline builds and tests every change.

Method: Filesystem scan: CI workflow files (.github/workflows, .gitlab-ci.yml, etc.) for build and test stages. Exhaustive, deterministic.

  • No CI workflow found (.github/workflows, azure-pipelines.yml, .gitlab-ci.yml, …) — changes aren't gated by an automated build/test.

What to do

  • Add a CI workflow that builds and runs the test suite on every push/PR.
P2 · Observability0.0 / 10Critical✓ Tool-verified

Readiness · Readiness — Whether the code is diagnosable in production — structured logging, tracing/metrics, health checks.

Method: Filesystem/Roslyn scan: structured-logging frameworks (Serilog, NLog), OpenTelemetry, and health-check endpoint patterns. Exhaustive, deterministic.

  • No logging or diagnostics emission found. This repository ships a binary its users launch rather than a service you operate, so there is no operator to page — but when a run fails on a user's machine, neither they nor you have anything to read.

What to do

  • Write a diagnostic trail the user can hand back with a bug report: log through `package:logging` to a file in the app's support directory that a report can attach. Start with the error paths that emit nothing — a discarded error is the failure the user cannot describe and you cannot reproduce.
P3 · Security & performance tooling0.0 / 10Critical✓ Tool-verified

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 the Dart analyzer's security lints plus `semgrep --config=auto` — this repository has no CI pipeline yet, so run it locally to clear the existing findings, then make it a step of the first workflow you add so a regression fails the build. What was searched, so you can tell an absence from a miss: the 0 CI workflow file(s) in this repository, and the scanner and linter configuration checked in beside them. A scan that runs outside CI, one configured in your forge's web UI rather than in a committed file, or a tool whose name is none of those this check carries, is not seen — if that is your case the row is wrong, and saying so is more useful than adding a second scanner.

What to do

  • Run what this repository's stack ships: the Dart analyzer's security lints plus `semgrep --config=auto` — locally for now, since there is no CI pipeline here yet, and as a step of the first workflow you add 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.
P6 · Release Hygiene5.0 / 10Adequate✓ Tool-verified

Readiness · Readiness — Whether releases are traceable — a maintained changelog and explicit version stamping.

Method: Filesystem scan: changelog file presence and version tags in csproj or git tags. Exhaustive, deterministic.

  • No CHANGELOG/HISTORY/RELEASES file — what shipped when isn't easy to reconstruct for support or audit. (Versioning/tagging makes releases traceable, but a changelog records the what.)

What to do

  • Keep a changelog (e.g. Keep-a-Changelog) recording what shipped in each release.
PF3 · Async & latency hygiene8.5 / 10Strong✓ Tool-verified

Readiness · Performance — Whether asynchronous code stays responsive — it avoids sync-over-async blocking (a .NET .Wait()/.GetAwaiter().GetResult(), a time.sleep or blocking HTTP call inside a Python coroutine, a *Sync call inside an async JavaScript function, block_on inside a Rust async fn, runBlocking inside a Kotlin suspend function, block() inside a Reactor publisher) that stalls a thread or event loop and risks deadlock, and, where the code is a reusable library on .NET, awaits with ConfigureAwait(false) so it never captures and stalls its caller's context.

Method: Production-source scan: sync-over-async blocking counted everywhere — .Wait()/.GetAwaiter().GetResult() in .NET; off .NET, read from each language's code model, a blocking call inside an async function (Python, TS/JS, Rust, Kotlin, Swift, Dart) or inside a Java method returning a Reactor Mono/Flux or a Scala method returning a Future or effect — and, for a .NET library with ≥5 awaits, the share of awaits using ConfigureAwait(false). Deterministic, syntax/text detection.

  • `listTranscriptions` is async and calls listSync — a blocking call inside async code stalls the isolate's event loop — every other event, on Flutter the next frame, waits for as long as it runs. — lib/core/storage/transcription_storage.dart:41

What to do

  • Dart: await the async dart:io API (readAsString, writeAsString, Process.run, Future.delayed) instead of the *Sync variant or sleep(), or move heavy synchronous work to another isolate with Isolate.run.
X1 · Async correctness10.0 / 10Exemplary○ Nothing flagged

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.

X12 · Unreachable branch10.0 / 10Exemplary○ Nothing flagged

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.

X16 · Unfloored truncation loop10.0 / 10Exemplary○ Nothing flagged

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.

X18 · Disposal-pattern correctness10.0 / 10Exemplary○ Nothing flagged

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.

X25 · Inert configuration knob10.0 / 10Exemplary○ Nothing flagged

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.

X27 · Collection changed while being enumerated10.0 / 10Exemplary○ Nothing flagged

Other · Code Health — Whether a `for … in` loop leaves the `List`, `Map` or `Set` it is walking alone — Dart's collection iterators check that the collection has not changed since the loop began, so a body that adds to or removes from the very collection the loop is walking (or the map whose `keys`, `values` or `entries` it walks) makes the next step throw `ConcurrentModificationError` and the remaining elements are never seen. Whether a `for (x in c)` or `c.forEach { … }` leaves the collection it is walking alone — a `mutableListOf`/`ArrayList`, `mutableMapOf`/`HashMap` or `mutableSetOf`/`HashSet` is a `java.util` collection on the JVM and is walked by its own fail-fast iterator, so a body that adds to or removes from the very collection the loop is walking makes the next step throw `ConcurrentModificationException` and the remaining elements are never seen.

Method: Roslyn syntax + semantics: `foreach` statements whose body calls a structural mutator (`Add`/`Remove`/`Clear`/`Insert`/…) on the very expression the loop is enumerating. Two arms. ARM A — the source is a concrete fragile BCL collection, or a live `Keys`/`Values` view over one, and the mutator resolves to that same collection's own member; concurrent and immutable collections and arrays are outside the population by construction, since their enumerators survive a structural change. ARM B — the source is an argument-less accessor CALL on a receiver whose body is in source: the accessor must return a stored field VERBATIM and a sibling member must structurally change that same field, both read off the implementations rather than from the members' names. A mutation the loop provably exits immediately after (`break`/`return`/`throw`/`goto`), or one written inside a nested loop or a lambda, is counted and never reported. Deterministic, provable per finding. Advisory.

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.

X3 · Exception handling7.4 / 10Strong✓ Tool-verified

Other · Code Health — Whether exceptions are handled rather than silently swallowed or rethrown with lost stack traces.

Method: Roslyn syntax scan: every catch clause counted; empty catches and bare rethrows flagged. Population is all catch clauses, not estimated. Deterministic, hard fact.

  • `catch (e)` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter. (×2) — lib/features/settings/presentation/pages/general_settings_page.dart:32, lib/features/onboarding/presentation/widgets/completed_step.dart:196
  • An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it. (×4) — lib/features/hotkeys/handlers/push_to_talk_handler.dart:459, lib/features/hotkeys/handlers/transcription_hotkey_handler.dart:262, lib/features/hotkeys/handlers/transcription_hotkey_handler.dart:395, …

What to do

  • Swallowed exception (caught, then discarded)
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.

X5 · Nullable reference types9.4 / 10Exemplary✓ Tool-verified

Other · Code Health — Whether Dart's sound null safety is on and is not undermined by null assertions — a package whose `environment: sdk:` lower bound is 2.12 or above is null safe, so `String` cannot hold null and `String?` must be checked before use, and each postfix `!` is a run-time `Null check operator used on a null value` the author has told the analyzer cannot happen.

Method: Roslyn compiler-options scan: NullableContextOptions per project; null-forgiving (!) suppression density per 1k syntax nodes. Deterministic, adoption plus suppression penalty.

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.

LensScoreRatingImpact
Code Health74.0Adequate — gated by D2, D4Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Architecture82.7StrongSolid.
Maturity54.2Adequate — gated by D34, M2Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Readiness23.2Critical — gated by P1, P2, P3Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Security96.2Checked 3 of 7Solid.
Domain Modelling100.0ExemplaryStrongest area.
Performance85.0StrongSolid.
Unscored — 2 check(s) recorded observations but carry no score

These checks ran and found something, but they do not carry a score — either by design (an advisory check reports evidence rather than grading it) or because they could not be scored here. They are excluded from the score for that reason, not because there was nothing to see.

  • X10 Duplicated predicate — 7 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
  • X7 Silent fallback defaults — 1 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
Not evidenced — 5 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: this repository stores data through 'package:hive_flutter' (lib/main.dart:10) but declares no persisted model this check reads (Drift tables, ObjectBox/Floor @Entity, Isar @collection and Hive @HiveType classes, Serverpod table models). Personal data may be written through raw SQL or a hosted backend, so whether its changes need an audit trail could not be established, and the trail's absence is not scored.
  • C4 Data Retention — Not assessed: this repository stores data through 'package:hive_flutter' (lib/main.dart:10) but declares no persisted model this check reads (Drift tables, ObjectBox/Floor @Entity, Isar @collection and Hive @HiveType classes, Serverpod table models). Personal data may be written through raw SQL or a hosted backend, so whether a retention limit applies here could not be established, and its absence is not scored.
  • C5 Data-Subject Rights — Not assessed: this repository stores data through 'package:hive_flutter' (lib/main.dart:10) but declares no persisted model this check reads (Drift tables, ObjectBox/Floor @Entity, Isar @collection and Hive @HiveType classes, Serverpod table models). Personal data may be written through raw SQL or a hosted backend, so whether data-subject rights apply here could not be established, and their absence is not scored.
  • P4 Deployment & Rollback — not evidenced — no deploy/rollback/approval signal in the repo; absence of evidence is not evidence of a manual release
  • P5 DR & Backup — not evidenced — repo shows no backup/RTO/RPO controls; absence of evidence is not evidence of a working control
Not included — 64 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 — Frontend below the scale floor (15 DOM element(s) < 25) — too little surface to assess accessibility.
  • AC2 Forms & labels — Frontend below the scale floor (15 DOM element(s) < 25) — too little surface to assess accessibility.
  • AC3 Page structure — Frontend below the scale floor (15 DOM element(s) < 25) — too little surface to assess accessibility.
  • AC4 Keyboard semantics — Frontend below the scale floor (15 DOM element(s) < 25) — too little surface to assess accessibility.
  • AC5 ARIA correctness — Frontend below the scale floor (15 DOM element(s) < 25) — too little surface to assess accessibility.
  • AC6 Visual & motion safety — Frontend below the scale floor (15 DOM element(s) < 25) — too little surface to assess accessibility.
  • AX2 Stateful singletons — No container singleton was found, so there is no shared instance for concurrent requests to race on. No class in this Kotlin code is a Spring, JSR-330 or CDI singleton bean. No Swift request handler (a Vapor, Hummingbird, Kitura, Swifter or Perfect route handler, as a method or a registered closure) is declared, so no state is shared between request threads. Dart isolates share no mutable memory, so no two requests write one object at the same instant.
  • AX4 Dependency direction — not applicable to a vertical-slice architecture (the inward-dependency rule is for layered/clean styles)
  • AX8 Test isolation — no test/production split to check
  • AXB1 Runtime evidence locked — no reproducible boot — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
  • C1 Data Protection — Not assessed: this repository stores data through 'package:hive_flutter' (lib/main.dart:10) but declares no persisted model this check reads (Drift tables, Isar/ObjectBox/Floor/Hive entities, Serverpod table models). Personal data may be written through raw SQL or a hosted backend, so the absence of a personal-data field here is not evidence that none is stored, and encryption at rest is not scored over a subject that could not be established.
  • C2 Access Controls — No access-control surface detected in the analyzed source — this repository stands up no server another machine can reach (no HttpServer or shelf server bound beyond loopback, no dart_frog route, no Serverpod endpoint, no Conduit, Alfred or Angel application) and keeps no data in a hosted backend. Access control is therefore N/A here — a Flutter app or pub package is authorized by the server it calls, not by itself; hiding a screen authorizes nothing. If this codebase grows request handlers, the dimension reactivates and a default-deny posture is expected then.
  • D10 Test Quality — ~18 lines of test source are present (.swift) but no test cases reached the test census for this repository — no test root we could resolve declared them, or the files we read declare no cases in a test framework we recognise — so skipped/assertion-free tests couldn't be counted. Not scored — this is a gap in the analyzer, not a finding about this repository.
  • D11 Test Reliability — Test source is present (.swift) and this repository's suite is reachable only from an Apple platform: it ships Runner.xcodeproj and no SwiftPM manifest, so it is built by Xcode rather than by `swift test`. The analyzer runs on Linux, where no simulator exists, so the suite was not re-run. Not scored: nothing was exercised.
  • D16 Bus Factor — single-contributor repository — bus factor is not applicable
  • D18 Solution Shape — D18 scores the shape of a .NET solution; this repository has no .NET solution or project files, so the dimension does not apply.
  • D22 Internal API Consistency — 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#, Visual Basic, TypeScript and JavaScript comments only — this repository's production source is .dart, .kt, .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 (.dart), so too few call sites counted as resolved to assess navigability. Not scored: this is a gap in the analyzer, not a verdict about this repository.
  • D31 IaC & Container Security — No Infrastructure-as-Code or container manifests found (Dockerfile, Docker Compose, Terraform, Kubernetes/Helm, CloudFormation, ARM, Bicep, Ansible); nothing to scan.
  • D32 Data Compliance (PII/GDPR) — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that.
  • D36 Supply-chain Provenance & Signing — No CI/build pipeline found (.github/.forgejo/.gitea workflows, .circleci, .buildkite, .woodpecker, .teamcity, .gitlab-ci.yml, .travis.yml, bitbucket-pipelines.yml, .drone.yml, .cirrus.yml, .woodpecker.yml, appveyor.yml, azure-pipelines*.yml, .pipelines/, .vsts-ci/, .azuredevops/, Jenkinsfile); there is no build to attest provenance for.
  • D37 Vulnerability-disclosure Policy — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed.
  • D40 Network Egress Confinement — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here.
  • D41 Kernel & Syscall Confinement — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here.
  • D42 Runtime Threat Enforcement — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here.
  • 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: this repository's test suite is reachable only from an Apple platform — it ships Runner.xcodeproj and no SwiftPM manifest, so it is built by Xcode rather than by `swift test`. The analyzer runs on Linux, where no simulator exists, so the suite was not run and no coverage was instrumented. Not scored.
  • DM1 Aggregate boundaries — no aggregates detected — aggregate-boundary check not applicable
  • DM2 Strongly-typed ids — no in-repo typed-id idiom — primitive-obsession recorded as advisory DM8, DM2 not gated
  • DM3 Integration-event coupling — no integration events detected — coupling check not applicable
  • DM4 Rich vs anemic domain model — this Dart repository declares no domain-layer entity carrying stored data (every type is a typed-id wrapper, DTO/config, ORM row or presentation container), so DM4's rich-vs-anemic read has no population to be taken over
  • DM6 Domain ↔ infrastructure boundary — this Dart repository maps no type to a persistence framework (drift/floor/isar/objectbox/hive), so DM6's domain↔infrastructure fusion read has no population to be taken over
  • DM7 Repository granularity — no repository abstraction detected (e.g. uses a document session)
  • ED2 Event/command shape — not scored — deciding whether a command has more than one competing handler requires resolving the call graph, and this analysis resolves a call's owner only where the receiver's type is written down in the source. Reported as guidance rather than measured
  • ED2 Event/command shape — not scored — deciding whether a command has more than one competing handler requires resolving the call graph, which this analysis does not build from source alone for this language. Reported as guidance rather than measured
  • ED5 Idempotency — Not assessed, and this one is on us: 4 of the 4 handler(s) found here write to persistent state through an entry point this check does not yet recognise (an explicitly-implemented interface method, or a static handler method). Idempotency was neither confirmed nor ruled out for them — this is a limit of the analyzer, not a finding about your code.
  • ES1 Event Sourcing — not scored — this repository shows none of the 3 signals this lens looks for
  • P12 CI test-gate honesty — no CI workflow found
  • P7 Outbound HTTP resilience — not applicable — no HTTP server, API framework or worker entry point was found in the Dart, JVM, Swift source, so there is no service whose uptime a failing dependency could take down
  • P8 Schema migrations — no ORM, schema-migration tool or schema auto-create was found in this repository's dependency manifests or source, so there is no database schema for this check to judge
  • P9 Domain vs controller coverage — coverage not measured: this check compares the coverage of the analyzer's own test run across the domain and web layers, and that run measured none here — Test coverage (D8) says why
  • PF1 Benchmark discipline — Not applicable: no benchmark suite was found. This check searched for classes extending benchmark_harness's `BenchmarkBase`, `AsyncBenchmarkBase` or `PerfBenchmarkBase` (directly or through a base of your own), `benchmark(…)` calls under the pub `benchmark` package, Flutter's `benchmarkWidgets`, `watchPerformance` or `traceAction` in a test importing flutter_test, integration_test or flutter_driver, or benchmark_harness, benchmark or web_benchmarks in a pubspec.yaml, and for a `*benchmark*` script that this repository's CI runs. Benchmarks are credited as a bonus, so their absence is neither scored nor deducted.
  • PF2 Allocation hygiene — Not scored: this check counted allocation-aware idioms (Span, pools, stackalloc) per line, which describes what kind of code a repository is rather than whether it has an allocation problem, so it was withdrawn. Nothing here is a finding about your code.
  • S1 Web-Security Posture — No HTTP server of its own: 115 Dart file(s) were read for weak hashes and ciphers, key material fixed in the source and disabled TLS certificate validation, and none was found. This repository serves no HTTP of its own — no server framework among its pubspec dependencies, no `HttpServer` bound and no shelf, dart_frog or serverpod import in its production source or `bin/`. Its Flutter web build (`web/index.html`) compiles to static files that run in the browser and are served by whatever hosts them: static files cannot enforce HTTPS, send HSTS or any other response header, set an HttpOnly cookie or validate a request, so those controls are the host's, not this code's. Where this repository commits the host's configuration (an nginx, Caddy or Apache config, a serving Dockerfile, `_headers`, `vercel.json`, `netlify.toml`, `firebase.json`, `staticwebapp.config.json`) it is read for the security response headers it sets, and the shipped page is read for third-party scripts loaded without Subresource Integrity. Neither shows anything to report here. If this codebase starts serving HTTP, the dimension reactivates automatically.
  • X13 Undrained process stream — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
  • X14 Bypassable address classification — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
  • X15 Unvalidated length from an untrusted reader — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
  • X17 Uncapped recursion over a caller-supplied document — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
  • X19 Unrestored process-global state — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
  • X2 Cancellation propagation — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
  • X20 Mistyped argument guard — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
  • X21 Side-effecting pattern guard — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
  • X22 Contradicted release guard — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
  • X23 Unguarded diagnostic materialisation — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
  • X24 Document value interpolated into markup unescaped — not 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
  • X26 Unsynchronised callback handoff — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
  • X29 Per-element action decided by a fixed element — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
  • 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 — This check asks whether log calls keep a message's values apart from its text, which needs a logger that can carry them as fields. This repository's Dart was read, and it logs through none: package:logging, package:logger, talker and dart:developer take one finished message and no template arguments or fields (as log4net does in C#), so an interpolated message there loses nothing the API could have kept. Sentry's structured logs (`Sentry.logger`) would be judged.
  • X6 Hand-rolled structured-format parsing — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
  • X9 Subsumed condition operand — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.

Appendix A — Findings (grouped)

The findings behind the scores, grouped by severity, then by dimension and kind. The high-severity issues are enumerated in full below; items per group are capped at 25 with any overflow stated explicitly per group, never silently truncated. The complete machine-readable list of every finding (all severities) is the companion findings.md in this report's bundle.

Critical — 1 finding(s)
D28 · Secrets (history) · REDACTED · ×1
  • REDACTED
Serious — 341 finding(s)
D3 · God Classes · MethodTooLong · ×36
  • MethodTooLong: OnboardingPage.build lib/features/onboarding/presentation/pages/onboarding_page.dart:21 — MethodTooLong — build runs 244 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 144 over it, 2.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: ApiKeyStep.build lib/features/onboarding/presentation/widgets/api_key_step.dart:12 — MethodTooLong — build runs 242 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 142 over it, 2.42× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
  • MethodTooLong: _SettingsPageState.build lib/features/settings/presentation/pages/settings.dart:76 — MethodTooLong — build runs 232 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 132 over it, 2.32× 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: HotkeysStep.build lib/features/onboarding/presentation/widgets/hotkeys_step.dart:14 — MethodTooLong — build runs 230 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 130 over it, 2.30× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
  • MethodTooLong: LocalStep._buildModelSelectionSection lib/features/onboarding/presentation/widgets/local_step.dart:200 — MethodTooLong — _buildModelSelectionSection runs 211 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 111 over it, 2.11× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
  • MethodTooLong: TranscriptionSettingsPage._buildModelSelectionSection lib/features/settings/presentation/pages/transcription_settings_page.dart:191 — MethodTooLong — _buildModelSelectionSection runs 202 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 102 over it, 2.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: _MobileApiKeyStepState.build lib/features/mobile/presentation/widgets/mobile_api_key_step.dart:25 — MethodTooLong — build runs 194 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 94 over it, 1.94× 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: PermissionsStep._buildPermissionCard lib/features/onboarding/presentation/widgets/permissions_step.dart:241 — MethodTooLong — _buildPermissionCard runs 189 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 89 over it, 1.89× 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: _MainLayoutState.build lib/features/navigation/presentation/pages/main_layout.dart:111 — MethodTooLong — build runs 184 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 84 over it, 1.84× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
  • MethodTooLong: MobileKeyboardExtensionStep.build lib/features/mobile/presentation/widgets/mobile_keyboard_extension_step.dart:7 — MethodTooLong — build runs 171 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 71 over it, 1.71× 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: PermissionsStep.build lib/features/onboarding/presentation/widgets/permissions_step.dart:14 — MethodTooLong — build runs 166 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 66 over it, 1.66× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
  • MethodTooLong: OutputSettingsPage._buildPhraseReplacementSection lib/features/settings/presentation/pages/output_settings_page.dart:436 — MethodTooLong — _buildPhraseReplacementSection runs 160 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 60 over it, 1.60× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
  • MethodTooLong: DictionarySection.build lib/features/settings/presentation/widgets/dictionary_section.dart:16 — MethodTooLong — build runs 158 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 58 over it, 1.58× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
  • MethodTooLong: AssistantService._sendToGroqAPI REDACTED:449 — MethodTooLong — _sendToGroqAPI runs 157 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 57 over it, 1.57× 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: MobileOnboardingPage.build lib/features/mobile/presentation/pages/mobile_onboarding_page.dart:18 — MethodTooLong — build runs 157 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 57 over it, 1.57× 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: OutputSettingsPage._buildLanguageSection lib/features/settings/presentation/pages/output_settings_page.dart:57 — MethodTooLong — _buildLanguageSection runs 154 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 54 over it, 1.54× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
  • MethodTooLong: _HomePageViewState.build lib/features/home/presentation/pages/home_page.dart:111 — MethodTooLong — build 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: MobileLocalModelsStep._buildModelSelectionSection lib/features/mobile/presentation/widgets/mobile_local_models_step.dart:214 — MethodTooLong — _buildModelSelectionSection runs 146 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 46 over it, 1.46× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
  • MethodTooLong: MobileLocalModelsSection._buildModelSelection lib/features/mobile/presentation/widgets/mobile_local_models_section.dart:142 — MethodTooLong — _buildModelSelection runs 145 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 45 over it, 1.45× 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: MobileLocalModelsStep.build lib/features/mobile/presentation/widgets/mobile_local_models_step.dart:11 — MethodTooLong — build runs 145 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 45 over it, 1.45× 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: MobilePermissionsStep.build lib/features/mobile/presentation/widgets/mobile_permissions_step.dart:11 — MethodTooLong — build runs 139 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 39 over it, 1.39× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
  • MethodTooLong: InfoPage.build lib/features/info/presentation/pages/info_page.dart:8 — MethodTooLong — build runs 138 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 38 over it, 1.38× 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: LocalStep.build lib/features/onboarding/presentation/widgets/local_step.dart:14 — MethodTooLong — build runs 133 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 33 over it, 1.33× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
  • MethodTooLong: _GeneralSettingsPageState._buildSoundSettingsSection lib/features/settings/presentation/pages/general_settings_page.dart:112 — MethodTooLong — _buildSoundSettingsSection runs 132 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 32 over it, 1.32× 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: TranscriptionHotkeyHandler.handleHotkey lib/features/hotkeys/handlers/transcription_hotkey_handler.dart:69 — MethodTooLong — handleHotkey runs 129 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 29 over it, 1.29× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
  • + 11 more in this group — see findings.md.
D15 · Churn × Complexity Hotspots · Hotspot · ×16
  • Hotspot: lib/features/hotkeys/handlers/push_to_talk_handler.dart lib/features/hotkeys/handlers/push_to_talk_handler.dart:309 — lib/features/hotkeys/handlers/push_to_talk_handler.dart changed 14 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 39 in PushToTalkHandler.handleKeyUp at line 309. 4 of those changes were fix/bug commits, and the other 10 changed it for other reasons — this file is under both repair and feature pressure. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2025-05-25..2025-08-23, the 90 days ending at the analysed commit. Reproduce with `git log --since='2025-05-25 11:37:41 -04:00' --until='2025-08-23 11:37:41 -04:00' --full-history --no-merges -- lib/features/hotkeys/handlers/push_to_talk_handler.dart`: 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: lib/features/hotkeys/handlers/transcription_hotkey_handler.dart lib/features/hotkeys/handlers/transcription_hotkey_handler.dart:69 — lib/features/hotkeys/handlers/transcription_hotkey_handler.dart changed 9 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 37 in TranscriptionHotkeyHandler.handleHotkey at line 69. 1 of those changes was a fix/bug commit, and the other 8 changed it for other reasons — this file is under both repair and feature pressure. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2025-05-25..2025-08-23, the 90 days ending at the analysed commit. Reproduce with `git log --since='2025-05-25 11:37:41 -04:00' --until='2025-08-23 11:37:41 -04:00' --full-history --no-merges -- lib/features/hotkeys/handlers/transcription_hotkey_handler.dart`: 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: lib/features/onboarding/presentation/bloc/onboarding_bloc.dart lib/features/onboarding/presentation/bloc/onboarding_bloc.dart:264 — lib/features/onboarding/presentation/bloc/onboarding_bloc.dart changed 9 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 23 in OnboardingBloc._onInitializeOnboarding at line 264. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2025-05-25..2025-08-23, the 90 days ending at the analysed commit. Reproduce with `git log --since='2025-05-25 11:37:41 -04:00' --until='2025-08-23 11:37:41 -04:00' --full-history --no-merges -- lib/features/onboarding/presentation/bloc/onboarding_bloc.dart`: 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: macos/Runner/MainFlutterWindow.swift macos/Runner/MainFlutterWindow.swift:25 — macos/Runner/MainFlutterWindow.swift changed 10 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 19 in MainFlutterWindow.setupMethodChannel at line 25. 1 of those changes was a fix/bug commit, 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 2025-05-25..2025-08-23, the 90 days ending at the analysed commit. Reproduce with `git log --since='2025-05-25 11:37:41 -04:00' --until='2025-08-23 11:37:41 -04:00' --full-history --no-merges -- macos/Runner/MainFlutterWindow.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: lib/features/recording/data/datasources/recording_datasource.dart lib/features/recording/data/datasources/recording_datasource.dart:232 — lib/features/recording/data/datasources/recording_datasource.dart changed 7 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 22 in RecordingDataSourceImpl._setupAudioStreamProcessing at line 232. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2025-05-25..2025-08-23, the 90 days ending at the analysed commit. Reproduce with `git log --since='2025-05-25 11:37:41 -04:00' --until='2025-08-23 11:37:41 -04:00' --full-history --no-merges -- lib/features/recording/data/datasources/recording_datasource.dart`: 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: REDACTED REDACTED:313 — REDACTED changed 8 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 17 in AssistantService._stopRecordingAndProcess at line 313. 1 of those changes was a fix/bug commit, and the other 7 changed it for other reasons — this file is under both repair and feature pressure. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2025-05-25..2025-08-23, the 90 days ending at the analysed commit. Reproduce with `git log --since='2025-05-25 11:37:41 -04:00' --until='2025-08-23 11:37:41 -04:00' --full-history --no-merges -- REDACTED`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
  • Hotspot: lib/features/transcription/data/repositories/transcription_repository_impl.dart lib/features/transcription/data/repositories/transcription_repository_impl.dart:145 — lib/features/transcription/data/repositories/transcription_repository_impl.dart changed 5 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 24 in TranscriptionRepositoryImpl._transcribeAudioRemotely at line 145. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2025-05-25..2025-08-23, the 90 days ending at the analysed commit. Reproduce with `git log --since='2025-05-25 11:37:41 -04:00' --until='2025-08-23 11:37:41 -04:00' --full-history --no-merges -- lib/features/transcription/data/repositories/transcription_repository_impl.dart`: 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: lib/features/onboarding/presentation/widgets/api_key_step.dart lib/features/onboarding/presentation/widgets/api_key_step.dart:12 — lib/features/onboarding/presentation/widgets/api_key_step.dart changed 4 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 24 in ApiKeyStep.build at line 12. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2025-05-25..2025-08-23, the 90 days ending at the analysed commit. Reproduce with `git log --since='2025-05-25 11:37:41 -04:00' --until='2025-08-23 11:37:41 -04:00' --full-history --no-merges -- lib/features/onboarding/presentation/widgets/api_key_step.dart`: 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: lib/features/transcription/presentation/bloc/transcription_bloc.dart lib/features/transcription/presentation/bloc/transcription_bloc.dart:126 — lib/features/transcription/presentation/bloc/transcription_bloc.dart changed 3 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 31 in TranscriptionBloc._onStartTranscription at line 126. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2025-05-25..2025-08-23, the 90 days ending at the analysed commit. Reproduce with `git log --since='2025-05-25 11:37:41 -04:00' --until='2025-08-23 11:37:41 -04:00' --full-history --no-merges -- lib/features/transcription/presentation/bloc/transcription_bloc.dart`: 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: lib/features/onboarding/presentation/pages/onboarding_page.dart lib/features/onboarding/presentation/pages/onboarding_page.dart:21 — lib/features/onboarding/presentation/pages/onboarding_page.dart changed 4 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 23 in OnboardingPage.build at line 21. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2025-05-25..2025-08-23, the 90 days ending at the analysed commit. Reproduce with `git log --since='2025-05-25 11:37:41 -04:00' --until='2025-08-23 11:37:41 -04:00' --full-history --no-merges -- lib/features/onboarding/presentation/pages/onboarding_page.dart`: 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: lib/features/hotkeys/core/hotkey_handler.dart lib/features/hotkeys/core/hotkey_handler.dart:74 — lib/features/hotkeys/core/hotkey_handler.dart changed 5 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 17 in HotkeyHandler.keyDownHandler at line 74. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2025-05-25..2025-08-23, the 90 days ending at the analysed commit. Reproduce with `git log --since='2025-05-25 11:37:41 -04:00' --until='2025-08-23 11:37:41 -04:00' --full-history --no-merges -- lib/features/hotkeys/core/hotkey_handler.dart`: 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: lib/features/onboarding/presentation/widgets/permissions_step.dart lib/features/onboarding/presentation/widgets/permissions_step.dart:241 — lib/features/onboarding/presentation/widgets/permissions_step.dart changed 5 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 16 in PermissionsStep._buildPermissionCard at line 241. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2025-05-25..2025-08-23, the 90 days ending at the analysed commit. Reproduce with `git log --since='2025-05-25 11:37:41 -04:00' --until='2025-08-23 11:37:41 -04:00' --full-history --no-merges -- lib/features/onboarding/presentation/widgets/permissions_step.dart`: 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: lib/features/settings/presentation/pages/settings.dart lib/features/settings/presentation/pages/settings.dart:76 — lib/features/settings/presentation/pages/settings.dart changed 4 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 19 in _SettingsPageState.build at line 76. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2025-05-25..2025-08-23, the 90 days ending at the analysed commit. Reproduce with `git log --since='2025-05-25 11:37:41 -04:00' --until='2025-08-23 11:37:41 -04:00' --full-history --no-merges -- lib/features/settings/presentation/pages/settings.dart`: 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: lib/features/settings/presentation/pages/transcription_settings_page.dart lib/features/settings/presentation/pages/transcription_settings_page.dart:191 — lib/features/settings/presentation/pages/transcription_settings_page.dart changed 4 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 18 in TranscriptionSettingsPage._buildModelSelectionSection at line 191. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2025-05-25..2025-08-23, the 90 days ending at the analysed commit. Reproduce with `git log --since='2025-05-25 11:37:41 -04:00' --until='2025-08-23 11:37:41 -04:00' --full-history --no-merges -- lib/features/settings/presentation/pages/transcription_settings_page.dart`: 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: lib/features/hotkeys/services/clipboard_service.dart lib/features/hotkeys/services/clipboard_service.dart:13 — lib/features/hotkeys/services/clipboard_service.dart changed 2 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 24 in ClipboardService.copyToClipboard at line 13. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2025-05-25..2025-08-23, the 90 days ending at the analysed commit. Reproduce with `git log --since='2025-05-25 11:37:41 -04:00' --until='2025-08-23 11:37:41 -04:00' --full-history --no-merges -- lib/features/hotkeys/services/clipboard_service.dart`: 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: lib/features/settings/presentation/pages/output_settings_page.dart lib/features/settings/presentation/pages/output_settings_page.dart:57 — lib/features/settings/presentation/pages/output_settings_page.dart changed 2 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 17 in OutputSettingsPage._buildLanguageSection at line 57. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2025-05-25..2025-08-23, the 90 days ending at the analysed commit. Reproduce with `git log --since='2025-05-25 11:37:41 -04:00' --until='2025-08-23 11:37:41 -04:00' --full-history --no-merges -- lib/features/settings/presentation/pages/output_settings_page.dart`: 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.
D3 · God Classes · ClassTooLong · ×8
  • ClassTooLong: SettingsBloc lib/features/settings/presentation/bloc/settings_bloc.dart:18 — ClassTooLong — 831 significant lines (blank, comment-only and punctuation-only lines excluded), 48 methods. The bar is 400 significant lines; this is 431 over it, 2.08× 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: OnboardingBloc lib/features/onboarding/presentation/bloc/onboarding_bloc.dart:24 — ClassTooLong — 816 significant lines (blank, comment-only and punctuation-only lines excluded), 46 methods. The bar is 400 significant lines; this is 416 over it, 2.04× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
  • ClassTooLong: _GeneralSettingsPageState lib/features/settings/presentation/pages/general_settings_page.dart:24 — ClassTooLong — 679 significant lines (blank, comment-only and punctuation-only lines excluded), 13 methods. The bar is 400 significant lines; this is 279 over it, 1.70× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
  • ClassTooLong: TranscriptionSettingsPage lib/features/settings/presentation/pages/transcription_settings_page.dart:12 — ClassTooLong — 639 significant lines (blank, comment-only and punctuation-only lines excluded), 12 methods. The bar is 400 significant lines; this is 239 over it, 1.60× 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: PushToTalkHandler lib/features/hotkeys/handlers/push_to_talk_handler.dart:21 — ClassTooLong — 578 significant lines (blank, comment-only and punctuation-only lines excluded), 11 methods. The bar is 400 significant lines; this is 178 over it, 1.45× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
  • ClassTooLong: AssistantService REDACTED:21 — ClassTooLong — 490 significant lines (blank, comment-only and punctuation-only lines excluded), 19 methods. The bar is 400 significant lines; this is 90 over it, 1.23× 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: LocalStep lib/features/onboarding/presentation/widgets/local_step.dart:11 — ClassTooLong — 479 significant lines (blank, comment-only and punctuation-only lines excluded), 8 methods. The bar is 400 significant lines; this is 79 over it, 1.20× 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: OutputSettingsPage lib/features/settings/presentation/pages/output_settings_page.dart:12 — ClassTooLong — 470 significant lines (blank, comment-only and punctuation-only lines excluded), 5 methods. The bar is 400 significant lines; this is 70 over it, 1.18× 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.
D17 · Explicit Debt · TodoComment · ×6
  • TodoComment lib/features/mobile/presentation/widgets/mobile_keyboard_extension_step.dart:177 — // TODO: Open iOS Settings app to keyboard section — 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 lib/features/mobile/presentation/widgets/mobile_local_models_section.dart:353 — // TODO: Start download — 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 lib/features/mobile/presentation/widgets/mobile_local_models_step.dart:480 — // TODO: Implement download functionality — 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 lib/features/mobile/presentation/widgets/mobile_permissions_step.dart:238 — // TODO: Open app settings — 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 lib/features/mobile/presentation/widgets/mobile_permissions_step.dart:247 — // TODO: Open app settings — 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 lib/core/services/auto_update_service.dart:52 — // TODO: Show user-friendly message when update server is not available — 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.
D3 · God Classes · FileTooLong · ×6
  • FileTooLong: bloc/settings_bloc.dart lib/features/settings/presentation/bloc/settings_bloc.dart — FileTooLong — 846 significant lines (blank, comment-only and punctuation-only lines excluded), about 98% of them inside a single declaration: SettingsBloc (18-1413). The bar is 500 significant lines; this is 346 over it, 1.69× 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: bloc/onboarding_bloc.dart lib/features/onboarding/presentation/bloc/onboarding_bloc.dart — FileTooLong — 838 significant lines (blank, comment-only and punctuation-only lines excluded), about 97% of them inside a single declaration: OnboardingBloc (24-1376). The bar is 500 significant lines; this is 338 over it, 1.68× the bar. Moving the declarations that sit BESIDE it into sibling files will not shorten this file. Extract from INSIDE that declaration instead: lift each cohesive group of its body — the parts that share the same inputs and are named together — into its own unit in a sibling file, and have the original call them.
  • FileTooLong: pages/general_settings_page.dart lib/features/settings/presentation/pages/general_settings_page.dart — FileTooLong — 698 significant lines (blank, comment-only and punctuation-only lines excluded), about 97% of them inside a single declaration: _GeneralSettingsPageState (24-1032). The bar is 500 significant lines; this is 198 over it, 1.40× the bar. Moving the declarations that sit BESIDE it into sibling files will not shorten this file. Extract from INSIDE that declaration instead: lift each cohesive group of its body — the parts that share the same inputs and are named together — into its own unit in a sibling file, and have the original call them.
  • FileTooLong: pages/transcription_settings_page.dart lib/features/settings/presentation/pages/transcription_settings_page.dart — FileTooLong — 649 significant lines (blank, comment-only and punctuation-only lines excluded), about 98% of them inside a single declaration: TranscriptionSettingsPage (12-916). The bar is 500 significant lines; this is 149 over it, 1.30× 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: handlers/push_to_talk_handler.dart lib/features/hotkeys/handlers/push_to_talk_handler.dart — FileTooLong — 596 significant lines (blank, comment-only and punctuation-only lines excluded), about 97% of them inside a single declaration: PushToTalkHandler (22-1018). The bar is 500 significant lines; this is 96 over it, 1.19× 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: REDACTED REDACTED — FileTooLong — 509 significant lines (blank, comment-only and punctuation-only lines excluded), about 96% of them inside a single declaration: AssistantService (22-907). The bar is 500 significant lines; this is 9 over it, 1.02× the bar. Moving the declarations that sit BESIDE it into sibling files will not shorten this file. Extract from INSIDE that declaration instead: lift each cohesive group of its body — the parts that share the same inputs and are named together — into its own unit in a sibling file, and have the original call them.
D4 · Code Duplication · Duplicated block (14 lines × 2) · ×6
  • Duplicated block (14 lines × 2) lib/features/onboarding/presentation/bloc/onboarding_bloc.dart:1224 — lib/features/onboarding/presentation/bloc/onboarding_bloc.dart:1224-1237 | lib/features/settings/presentation/bloc/settings_bloc.dart:1042-1055 — before extracting anything, compare `lib/features/onboarding/presentation/bloc/onboarding_bloc.dart` and `lib/features/settings/presentation/bloc/settings_bloc.dart` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 68 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 `lib/features/onboarding/presentation/bloc/onboarding_bloc.dart:1224` 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 (14 lines × 2) lib/features/onboarding/presentation/widgets/hotkeys_step.dart:98 — lib/features/onboarding/presentation/widgets/hotkeys_step.dart:98-111 | lib/features/onboarding/presentation/widgets/hotkeys_step.dart:242-255 — 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 `lib/features/onboarding/presentation/widgets/hotkeys_step.dart:98` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (14 lines × 2) lib/features/settings/presentation/pages/assistant_settings_page.dart:59 — lib/features/settings/presentation/pages/assistant_settings_page.dart:59-72 | lib/features/settings/presentation/pages/general_settings_page.dart:749-762 — before extracting anything, compare `lib/features/settings/presentation/pages/assistant_settings_page.dart` and `lib/features/settings/presentation/pages/general_settings_page.dart` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 103 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `lib/features/settings/presentation/pages/assistant_settings_page.dart:59` 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) lib/features/settings/presentation/pages/general_settings_page.dart:873 — lib/features/settings/presentation/pages/general_settings_page.dart:873-886 | lib/features/settings/presentation/pages/transcription_settings_page.dart:752-765 — before extracting anything, compare `lib/features/settings/presentation/pages/general_settings_page.dart` and `lib/features/settings/presentation/pages/transcription_settings_page.dart` as WHOLE FILES: this scan already matched 9 separate duplicated blocks between them, totalling at least 150 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `lib/features/settings/presentation/pages/general_settings_page.dart:873` 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 (14 lines × 2) lib/features/settings/presentation/widgets/hotkey_settings_section.dart:13 — lib/features/settings/presentation/widgets/hotkey_settings_section.dart:13-26 | lib/features/settings/presentation/widgets/models_section.dart:10-23 — 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 `lib/features/settings/presentation/widgets/hotkey_settings_section.dart: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. 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) lib/features/settings/presentation/widgets/smart_transcription_section.dart:82 — lib/features/settings/presentation/widgets/smart_transcription_section.dart:82-95 | lib/features/settings/presentation/widgets/transcription_hotkey_settings_section.dart:142-155 — 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 `lib/features/settings/presentation/widgets/smart_transcription_section.dart:82` 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.
D4 · Code Duplication · Duplicated block (13 lines × 2) · ×6
  • Duplicated block (13 lines × 2) lib/features/home/presentation/pages/home_page.dart:86 — lib/features/home/presentation/pages/home_page.dart:86-98 | lib/features/mobile/presentation/pages/mobile_home_page.dart:57-69 — before extracting anything, compare `lib/features/home/presentation/pages/home_page.dart` and `lib/features/mobile/presentation/pages/mobile_home_page.dart` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 30 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 (13 lines × 2) lib/features/onboarding/presentation/bloc/onboarding_bloc.dart:768 — lib/features/onboarding/presentation/bloc/onboarding_bloc.dart:768-780 | lib/features/onboarding/presentation/bloc/onboarding_bloc.dart:801-813 — 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 × 2) lib/features/onboarding/presentation/bloc/onboarding_bloc.dart:1260 — lib/features/onboarding/presentation/bloc/onboarding_bloc.dart:1260-1272 | lib/features/settings/presentation/bloc/settings_bloc.dart:1090-1102 — before extracting anything, compare `lib/features/onboarding/presentation/bloc/onboarding_bloc.dart` and `lib/features/settings/presentation/bloc/settings_bloc.dart` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 68 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 (13 lines × 2) lib/features/onboarding/presentation/widgets/permissions_step.dart:275 — lib/features/onboarding/presentation/widgets/permissions_step.dart:275-290 | lib/features/onboarding/presentation/widgets/permissions_step.dart:294-306 — 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 (13 lines × 2) lib/features/settings/presentation/bloc/settings_bloc.dart:382 — lib/features/settings/presentation/bloc/settings_bloc.dart:382-394 | lib/features/settings/presentation/bloc/settings_bloc.dart:706-718 — 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 `lib/features/settings/presentation/bloc/settings_bloc.dart:382` 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 (13 lines × 2) lib/features/settings/presentation/widgets/models_section.dart:33 — lib/features/settings/presentation/widgets/models_section.dart:33-45 | lib/features/settings/presentation/widgets/models_section.dart:115-127 — 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 `lib/features/settings/presentation/widgets/models_section.dart:33` 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 · Duplicated block (18 lines × 2) · ×5
  • Duplicated block (18 lines × 2) lib/features/mobile/presentation/widgets/mobile_keyboard_extension_step.dart:106 — lib/features/mobile/presentation/widgets/mobile_keyboard_extension_step.dart:106-123 | lib/features/mobile/presentation/widgets/mobile_transcription_models_section.dart:21-38 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `lib/features/mobile/presentation/widgets/mobile_keyboard_extension_step.dart:106` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
  • Duplicated block (18 lines × 2) lib/features/mobile/presentation/widgets/mobile_local_models_section.dart:80 — lib/features/mobile/presentation/widgets/mobile_local_models_section.dart:80-97 | lib/features/mobile/presentation/widgets/mobile_theme_settings_section.dart:86-103 — 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 `lib/features/mobile/presentation/widgets/mobile_local_models_section.dart:80` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
  • Duplicated block (18 lines × 2) lib/features/mobile/presentation/widgets/mobile_local_models_section.dart:177 — lib/features/mobile/presentation/widgets/mobile_local_models_section.dart:177-194 | lib/features/mobile/presentation/widgets/mobile_local_models_step.dart:262-279 — before extracting anything, compare `lib/features/mobile/presentation/widgets/mobile_local_models_section.dart` and `lib/features/mobile/presentation/widgets/mobile_local_models_step.dart` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 161 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `lib/features/mobile/presentation/widgets/mobile_local_models_section.dart:177` 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `lib/features/mobile/presentation/widgets/mobile_local_models_step.dart:260` calls `contains` and `lib/features/mobile/presentation/widgets/mobile_local_models_section.dart:175` 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 (18 lines × 2) lib/features/mobile/presentation/widgets/mobile_permissions_step.dart:80 — lib/features/mobile/presentation/widgets/mobile_permissions_step.dart:80-97 | lib/features/mobile/presentation/widgets/mobile_theme_step.dart:107-124 — before extracting anything, compare `lib/features/mobile/presentation/widgets/mobile_permissions_step.dart` and `lib/features/mobile/presentation/widgets/mobile_theme_step.dart` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 94 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `lib/features/mobile/presentation/widgets/mobile_permissions_step.dart: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 (18 lines × 2) lib/features/mobile/presentation/widgets/mobile_permissions_step.dart:273 — lib/features/mobile/presentation/widgets/mobile_permissions_step.dart:273-290 | lib/features/onboarding/presentation/widgets/permissions_step.dart:347-364 — 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 `lib/features/mobile/presentation/widgets/mobile_permissions_step.dart:273` 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.
D4 · Code Duplication · Duplicated block (17 lines × 2) · ×5
  • Duplicated block (17 lines × 2) lib/features/mobile/presentation/widgets/mobile_api_key_step.dart:69 — lib/features/mobile/presentation/widgets/mobile_api_key_step.dart:69-85 | lib/features/mobile/presentation/widgets/mobile_local_models_step.dart:49-65 — before extracting anything, compare `lib/features/mobile/presentation/widgets/mobile_api_key_step.dart` and `lib/features/mobile/presentation/widgets/mobile_local_models_step.dart` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 119 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `lib/features/mobile/presentation/widgets/mobile_api_key_step.dart:69` 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 (17 lines × 2) lib/features/onboarding/presentation/widgets/local_step.dart:526 — lib/features/onboarding/presentation/widgets/local_step.dart:526-542 | lib/features/settings/presentation/pages/transcription_settings_page.dart:501-517 — before extracting anything, compare `lib/features/onboarding/presentation/widgets/local_step.dart` and `lib/features/settings/presentation/pages/transcription_settings_page.dart` as WHOLE FILES: this scan already matched 16 separate duplicated blocks between them, totalling at least 359 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 `lib/features/onboarding/presentation/widgets/local_step.dart:526` 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 (17 lines × 2) lib/features/onboarding/presentation/widgets/permissions_step.dart:418 — lib/features/onboarding/presentation/widgets/permissions_step.dart:418-434 | lib/features/settings/presentation/widgets/smart_transcription_section.dart:97-113 — 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 `lib/features/onboarding/presentation/widgets/permissions_step.dart:418` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (17 lines × 2) lib/features/settings/presentation/bloc/settings_bloc.dart:361 — lib/features/settings/presentation/bloc/settings_bloc.dart:361-377 | lib/features/settings/presentation/bloc/settings_bloc.dart:685-701 — 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 `event` to `UpdateRecordedHotkey` in one and `StartPushToTalkHotkeyRecording` 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 (17 lines × 2) lib/features/settings/presentation/pages/output_settings_page.dart:355 — lib/features/settings/presentation/pages/output_settings_page.dart:355-371 | lib/features/settings/presentation/pages/output_settings_page.dart:546-562 — 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 `lib/features/settings/presentation/pages/output_settings_page.dart:355` 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.
D6 · Cohesion (LCOM4) · Low cohesion · ×5
  • Low cohesion: SettingsBloc (LCOM4 41) lib/features/settings/presentation/bloc/settings_bloc.dart:18 — SettingsBloc's methods fall into 41 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 41 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: OnboardingBloc (LCOM4 34) lib/features/onboarding/presentation/bloc/onboarding_bloc.dart:24 — OnboardingBloc's methods fall into 34 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 34 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: MobileOnboardingBloc (LCOM4 11) lib/features/mobile/presentation/bloc/mobile_onboarding_bloc.dart:11 — MobileOnboardingBloc's methods fall into 11 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 11 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: TranscriptionBloc (LCOM4 5) lib/features/transcription/presentation/bloc/transcription_bloc.dart:87 — TranscriptionBloc's methods fall into 5 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 5 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
  • Low cohesion: RecordHotkeyDialogBloc (LCOM4 4) lib/widgets/record_hotkey_dialog/bloc/record_hotkey_dialog_bloc.dart:7 — RecordHotkeyDialogBloc's methods fall into 4 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 4 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
D35 · Change Coupling · Change coupling · ×4
  • Change coupling: settings_event.dart ↔ settings_state.dart lib/features/settings/presentation/bloc/settings_event.dart:1 — `lib/features/settings/presentation/bloc/settings_event.dart` and `lib/features/settings/presentation/bloc/settings_state.dart` change together 96% of the time (22 of the 23 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) with no explicit dependency between them. They sit in the same directory, but in this ecosystem each file is its own module — a sibling reference still needs an import — so the missing import edge is real: the coupling runs through shared behaviour, not a declared dependency. If they duplicate structure, extract the common part into one unit; otherwise the coupling is hidden and worth breaking. You can check this without leaving the row: of the 22 shared commits counted here, the most recent 3 are `8c8b649f` clipboard settings + auto enter key press setting working; `227b1eab` ui: audio input section reflects state changes; `203bfa22` backend and ui: audio input device selection complete — run `git show` on any of them.
  • Change coupling: onboarding_event.dart ↔ onboarding_state.dart lib/features/onboarding/presentation/bloc/onboarding_event.dart:1 — `lib/features/onboarding/presentation/bloc/onboarding_event.dart` and `lib/features/onboarding/presentation/bloc/onboarding_state.dart` change together 90% of the time (9 of the 10 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) with no explicit dependency between them. They sit in the same directory, but in this ecosystem each file is its own module — a sibling reference still needs an import — so the missing import edge is real: the coupling runs through shared behaviour, not a declared dependency. If they duplicate structure, extract the common part into one unit; otherwise the coupling is hidden and worth breaking. You can check this without leaving the row: of the 9 shared commits counted here, the most recent 3 are `1f7400b1` local model onboarding step working; `6a4dacf2` made api key step bloc compliant; `03340433` made permissions step bloc compliant — run `git show` on any of them.
  • Change coupling: clipboard_service.dart ↔ transcription_bloc.dart lib/features/hotkeys/services/clipboard_service.dart:1 — `lib/features/hotkeys/services/clipboard_service.dart` and `lib/features/transcription/presentation/bloc/transcription_bloc.dart` change together 67% of the time (8 of the 12 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) with no explicit dependency — the edge is real but nothing declares it. Read the pair before acting: if one registers itself into the other through a hook or an initialiser, the missing dependency is DELIBERATE — the registration is the link, and it is meant not to be an import — and the thing to add is a comment on each side naming the other, not a merge; if they simply belong together, co-locate them; if neither holds, the coupling is hidden and worth breaking. You can check this without leaving the row: of the 8 shared commits counted here, the most recent 3 are `733164cd` space added to the end of transcription; `6546907b` transcriptions being saved in AutoQuillAITranscriptions folder within…; `94677e62` sounds working with occasional 400 error when selecting text for cont… — run `git show` on any of them.
  • Change coupling: settings_state.dart ↔ transcription_repository_impl.dart lib/features/settings/presentation/bloc/settings_state.dart:1 — `lib/features/settings/presentation/bloc/settings_state.dart` and `lib/features/transcription/data/repositories/transcription_repository_impl.dart` change together 55% of the time (6 of the 11 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) with no explicit dependency — the edge is real but nothing declares it. Read the pair before acting: if one registers itself into the other through a hook or an initialiser, the missing dependency is DELIBERATE — the registration is the link, and it is meant not to be an import — and the thing to add is a comment on each side naming the other, not a merge; if they simply belong together, co-locate them; if neither holds, the coupling is hidden and worth breaking. You can check this without leaving the row: of the 6 shared commits counted here, the most recent 3 are `4b10eb49` local inference working perfectly; `0e673269` multilingual transcription working correctly; `006ee27d` massive speed improvements — run `git show` on any of them.
D4 · Code Duplication · Duplicated block (12 lines × 3) · ×4
  • Duplicated block (12 lines × 3) lib/features/mobile/presentation/widgets/mobile_local_models_step.dart:468 — lib/features/mobile/presentation/widgets/mobile_local_models_step.dart:468-479 | lib/features/onboarding/presentation/widgets/local_step.dart:543-554 | lib/features/settings/presentation/pages/transcription_settings_page.dart:543-554 — before extracting anything, compare `lib/features/mobile/presentation/widgets/mobile_local_models_step.dart` and `lib/features/onboarding/presentation/widgets/local_step.dart` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 133 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 `lib/features/mobile/presentation/widgets/mobile_local_models_step.dart:468` 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `lib/features/settings/presentation/pages/transcription_settings_page.dart:555` calls `add`, `DownloadModel` and `lib/features/mobile/presentation/widgets/mobile_local_models_step.dart:481` 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 (12 lines × 3) lib/features/settings/presentation/pages/assistant_settings_page.dart:61 — lib/features/settings/presentation/pages/assistant_settings_page.dart:61-72 | lib/features/settings/presentation/pages/general_settings_page.dart:751-762 | lib/features/settings/presentation/pages/transcription_settings_page.dart:63-74 — before extracting anything, compare `lib/features/settings/presentation/pages/assistant_settings_page.dart` and `lib/features/settings/presentation/pages/general_settings_page.dart` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 103 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `lib/features/settings/presentation/pages/assistant_settings_page.dart:61` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. 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 (12 lines × 3) lib/features/settings/presentation/pages/general_settings_page.dart:117 — lib/features/settings/presentation/pages/general_settings_page.dart:117-128 | lib/features/settings/presentation/pages/output_settings_page.dart:438-449 | lib/features/settings/presentation/widgets/smart_transcription_section.dart:17-28 — before extracting anything, compare `lib/features/settings/presentation/pages/general_settings_page.dart` and `lib/features/settings/presentation/pages/output_settings_page.dart` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 88 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `lib/features/settings/presentation/pages/general_settings_page.dart:117` 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 (12 lines × 3) lib/features/settings/presentation/pages/general_settings_page.dart:303 — lib/features/settings/presentation/pages/general_settings_page.dart:303-314 | lib/features/settings/presentation/pages/general_settings_page.dart:634-645 | lib/features/settings/presentation/pages/output_settings_page.dart:59-70 — before extracting anything, compare `lib/features/settings/presentation/pages/general_settings_page.dart` and `lib/features/settings/presentation/pages/output_settings_page.dart` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 88 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `lib/features/settings/presentation/pages/general_settings_page.dart:303` 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.
X3 · Exception handling · Swallowed exception (empty catch) · ×4
  • Swallowed exception (empty catch) lib/features/hotkeys/handlers/push_to_talk_handler.dart:459 — An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
  • Swallowed exception (empty catch) lib/features/hotkeys/handlers/transcription_hotkey_handler.dart:262 — An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
  • Swallowed exception (empty catch) lib/features/hotkeys/handlers/transcription_hotkey_handler.dart:395 — An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
  • Swallowed exception (empty catch) REDACTED:377 — An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
D4 · Code Duplication · Edited copy of a member (19 corresponding lines) · ×3
  • Edited copy of a member (19 corresponding lines) lib/features/settings/presentation/pages/general_settings_page.dart:865 — lib/features/settings/presentation/pages/general_settings_page.dart:865-886 | lib/features/settings/presentation/pages/transcription_settings_page.dart:747-765 — These two members are one piece of code written twice and then edited apart: 19 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (19 corresponding lines) lib/features/mobile/presentation/bloc/mobile_onboarding_bloc.dart:158 — lib/features/mobile/presentation/bloc/mobile_onboarding_bloc.dart:158-177 | lib/features/mobile/presentation/bloc/mobile_onboarding_bloc.dart:179-197 — These two members are one piece of code written twice and then edited apart: 19 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (19 corresponding lines) lib/core/theme/design_tokens.dart:289 — lib/core/theme/design_tokens.dart:289-307 | lib/core/theme/design_tokens.dart:310-328 — These two members are one piece of code written twice and then edited apart: 19 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Duplicated block (25 lines × 2) · ×3
  • Duplicated block (25 lines × 2) lib/features/mobile/presentation/widgets/mobile_local_models_section.dart:205 — lib/features/mobile/presentation/widgets/mobile_local_models_section.dart:205-229 | lib/features/mobile/presentation/widgets/mobile_transcription_models_section.dart:159-183 — 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 (25 lines × 2) lib/features/onboarding/presentation/widgets/completed_step.dart:29 — lib/features/onboarding/presentation/widgets/completed_step.dart:29-53 | lib/features/onboarding/presentation/widgets/welcome_step.dart:24-48 — before extracting anything, compare `lib/features/onboarding/presentation/widgets/completed_step.dart` and `lib/features/onboarding/presentation/widgets/welcome_step.dart` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 54 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `lib/features/onboarding/presentation/widgets/completed_step.dart:29` 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 (25 lines × 2) lib/features/onboarding/presentation/widgets/local_step.dart:487 — lib/features/onboarding/presentation/widgets/local_step.dart:487-511 | lib/features/settings/presentation/pages/transcription_settings_page.dart:459-483 — before extracting anything, compare `lib/features/onboarding/presentation/widgets/local_step.dart` and `lib/features/settings/presentation/pages/transcription_settings_page.dart` as WHOLE FILES: this scan already matched 16 separate duplicated blocks between them, totalling at least 359 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 `lib/features/onboarding/presentation/widgets/local_step.dart:487` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it. Note first that the copies are not typed on the same thing: the declarations holding them bind `state` to `OnboardingState` in one and `SettingsState` 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.
D4 · Code Duplication · Duplicated block (16 lines × 2) · ×3
  • Duplicated block (16 lines × 2) lib/features/onboarding/presentation/widgets/local_step.dart:255 — lib/features/onboarding/presentation/widgets/local_step.dart:255-270 | lib/features/settings/presentation/pages/transcription_settings_page.dart:240-255 — before extracting anything, compare `lib/features/onboarding/presentation/widgets/local_step.dart` and `lib/features/settings/presentation/pages/transcription_settings_page.dart` as WHOLE FILES: this scan already matched 16 separate duplicated blocks between them, totalling at least 359 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 `lib/features/onboarding/presentation/widgets/local_step.dart:255` 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `lib/features/onboarding/presentation/widgets/local_step.dart:254` calls `contains` and `lib/features/settings/presentation/pages/transcription_settings_page.dart:239` 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 (16 lines × 2) lib/features/onboarding/presentation/widgets/local_step.dart:556 — lib/features/onboarding/presentation/widgets/local_step.dart:556-571 | lib/features/settings/presentation/pages/transcription_settings_page.dart:556-571 — before extracting anything, compare `lib/features/onboarding/presentation/widgets/local_step.dart` and `lib/features/settings/presentation/pages/transcription_settings_page.dart` as WHOLE FILES: this scan already matched 16 separate duplicated blocks between them, totalling at least 359 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 `lib/features/onboarding/presentation/widgets/local_step.dart:556` 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 (16 lines × 2) lib/features/settings/presentation/widgets/dictionary_section.dart:25 — lib/features/settings/presentation/widgets/dictionary_section.dart:25-40 | lib/features/settings/presentation/widgets/dictionary_section.dart:112-127 — 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 `lib/features/settings/presentation/widgets/dictionary_section.dart:25` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (10 lines × 2) · ×3
  • Duplicated block (10 lines × 2) lib/features/onboarding/presentation/widgets/completed_step.dart:114 — lib/features/onboarding/presentation/widgets/completed_step.dart:114-123 | lib/features/onboarding/presentation/widgets/preferences_step.dart:137-146 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `lib/features/onboarding/presentation/widgets/completed_step.dart:114` 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) lib/features/settings/presentation/pages/general_settings_page.dart:632 — lib/features/settings/presentation/pages/general_settings_page.dart:632-641 | lib/features/settings/presentation/pages/general_settings_page.dart:749-758 — 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 `lib/features/settings/presentation/pages/general_settings_page.dart:632` 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 (10 lines × 2) lib/features/home/presentation/pages/home_page.dart:100 — lib/features/home/presentation/pages/home_page.dart:100-109 | lib/features/mobile/presentation/pages/mobile_home_page.dart:71-80 — before extracting anything, compare `lib/features/home/presentation/pages/home_page.dart` and `lib/features/mobile/presentation/pages/mobile_home_page.dart` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 30 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.
D4 · Code Duplication · Duplicated block (9 lines × 2) · ×3
  • Duplicated block (9 lines × 2) lib/features/settings/presentation/bloc/settings_bloc.dart:514 — lib/features/settings/presentation/bloc/settings_bloc.dart:514-522 | lib/features/settings/presentation/bloc/settings_bloc.dart:534-542 — 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 `lib/features/settings/presentation/bloc/settings_bloc.dart:514` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (9 lines × 2) REDACTED:36 — REDACTED:36-44 | lib/features/recording/presentation/bloc/recording_bloc.dart:79-87 — 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) lib/features/mobile/presentation/bloc/mobile_onboarding_bloc.dart:103 — lib/features/mobile/presentation/bloc/mobile_onboarding_bloc.dart:103-111 | lib/features/onboarding/presentation/bloc/onboarding_bloc.dart:619-627 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Note first that the copies are not typed on the same thing: the declarations holding them bind `emit` to `Emitter<MobileOnboardingState>` in one and `Emitter<OnboardingState>` 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.
D4 · Code Duplication · Duplicated block (7 lines × 2) · ×3
  • Duplicated block (7 lines × 2) lib/features/onboarding/presentation/bloc/onboarding_bloc.dart:65 — lib/features/onboarding/presentation/bloc/onboarding_bloc.dart:65-71 | lib/features/settings/presentation/bloc/settings_bloc.dart:89-95 — before extracting anything, compare `lib/features/onboarding/presentation/bloc/onboarding_bloc.dart` and `lib/features/settings/presentation/bloc/settings_bloc.dart` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 68 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 × 2) lib/features/home/presentation/pages/home_page.dart:10 — lib/features/home/presentation/pages/home_page.dart:10-16 | lib/features/mobile/presentation/pages/mobile_home_page.dart:10-16 — before extracting anything, compare `lib/features/home/presentation/pages/home_page.dart` and `lib/features/mobile/presentation/pages/mobile_home_page.dart` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 30 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 × 2) macos/Runner/RecordingOverlayWindow.swift:149 — macos/Runner/RecordingOverlayWindow.swift:149-155 | macos/Runner/RecordingOverlayWindow.swift:164-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 `macos/Runner/RecordingOverlayWindow.swift:149` 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.
D3 · God Classes · TooManyMethods · ×2
  • TooManyMethods: SettingsBloc lib/features/settings/presentation/bloc/settings_bloc.dart:18 — TooManyMethods — 48 methods. The bar is 30 methods; this is 18 over it, 1.60× 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: OnboardingBloc lib/features/onboarding/presentation/bloc/onboarding_bloc.dart:24 — TooManyMethods — 46 methods. The bar is 30 methods; this is 16 over it, 1.53× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
D4 · Code Duplication · Members sharing a duplicated core (5 members, 50+ identical tokens) · ×2
  • Members sharing a duplicated core (5 members, 50+ identical tokens) lib/features/mobile/presentation/pages/mobile_home_page.dart:82 — lib/features/mobile/presentation/pages/mobile_home_page.dart:82-221 | lib/features/mobile/presentation/widgets/mobile_api_key_section.dart:13-169 | lib/features/mobile/presentation/widgets/mobile_local_models_section.dart:11-140 | lib/features/mobile/presentation/widgets/mobile_theme_settings_section.dart:11-137 | lib/features/mobile/presentation/widgets/mobile_transcription_models_section.dart:11-102 — 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.
  • Members sharing a duplicated core (5 members, 50+ identical tokens) lib/features/settings/presentation/widgets/api_key_section.dart:16 — lib/features/settings/presentation/widgets/api_key_section.dart:16-110 | lib/features/settings/presentation/widgets/assistant_hotkey_settings_section.dart:16-36 | lib/features/settings/presentation/widgets/assistant_models_section.dart:12-32 | lib/features/settings/presentation/widgets/transcription_hotkey_settings_section.dart:16-39 | lib/features/settings/presentation/widgets/transcription_models_section.dart:12-32 — 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.
D4 · Code Duplication · Members sharing a duplicated core (4 members, 50+ identical tokens) · ×2
  • Members sharing a duplicated core (4 members, 50+ identical tokens) lib/features/onboarding/presentation/widgets/api_key_step.dart:12 — lib/features/onboarding/presentation/widgets/api_key_step.dart:12-366 | lib/features/onboarding/presentation/widgets/hotkeys_step.dart:14-346 | lib/features/onboarding/presentation/widgets/preferences_step.dart:10-131 | lib/features/onboarding/presentation/widgets/test_hotkeys_step.dart:69-212 — 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) lib/features/settings/presentation/pages/assistant_settings_page.dart:14 — lib/features/settings/presentation/pages/assistant_settings_page.dart:14-55 | lib/features/settings/presentation/pages/output_settings_page.dart:19-55 | lib/features/settings/presentation/pages/settings.dart:76-385 | lib/features/settings/presentation/pages/transcription_settings_page.dart:15-56 — These 4 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 4 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 4 times.
D4 · Code Duplication · Edited copy of a member (21 corresponding lines) · ×2
  • Edited copy of a member (21 corresponding lines) lib/features/settings/presentation/widgets/hotkey_settings_section.dart:13 — lib/features/settings/presentation/widgets/hotkey_settings_section.dart:13-34 | lib/features/settings/presentation/widgets/models_section.dart:10-30 — These two members are one piece of code written twice and then edited apart: 21 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (21 corresponding lines) lib/features/settings/presentation/bloc/settings_bloc.dart:405 — lib/features/settings/presentation/bloc/settings_bloc.dart:405-425 | lib/features/settings/presentation/bloc/settings_bloc.dart:720-740 — These two members are one piece of code written twice and then edited apart: 21 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copy of a member (17 corresponding lines) · ×2
  • Edited copy of a member (17 corresponding lines) macos/Runner/WhisperKitService.swift:24 — macos/Runner/WhisperKitService.swift:24-40 | macos/Runner/WhisperKitService.swift:190-208 — These two members are one piece of code written twice and then edited apart: 17 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (17 corresponding lines) lib/features/onboarding/presentation/bloc/onboarding_bloc.dart:90 — lib/features/onboarding/presentation/bloc/onboarding_bloc.dart:90-113 | lib/features/onboarding/presentation/bloc/onboarding_bloc.dart:140-156 — These two members are one piece of code written twice and then edited apart: 17 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Duplicated block (32 lines × 2) · ×2
  • Duplicated block (32 lines × 2) lib/features/onboarding/presentation/widgets/local_step.dart:202 — lib/features/onboarding/presentation/widgets/local_step.dart:202-233 | lib/features/settings/presentation/pages/transcription_settings_page.dart:193-224 — before extracting anything, compare `lib/features/onboarding/presentation/widgets/local_step.dart` and `lib/features/settings/presentation/pages/transcription_settings_page.dart` as WHOLE FILES: this scan already matched 16 separate duplicated blocks between them, totalling at least 359 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 `lib/features/onboarding/presentation/widgets/local_step.dart:202` 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 (32 lines × 2) lib/widgets/hotkey_display.dart:174 — lib/widgets/hotkey_display.dart:174-205 | lib/widgets/hotkey_display.dart:209-240 — 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.
D4 · Code Duplication · Duplicated block (29 lines × 2) · ×2
  • Duplicated block (29 lines × 2) lib/features/onboarding/presentation/widgets/local_step.dart:33 — lib/features/onboarding/presentation/widgets/local_step.dart:33-61 | lib/features/onboarding/presentation/widgets/permissions_step.dart:46-74 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `lib/features/onboarding/presentation/widgets/local_step.dart:33` 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 (29 lines × 2) lib/features/settings/presentation/pages/general_settings_page.dart:718 — lib/features/settings/presentation/pages/general_settings_page.dart:718-746 | lib/features/settings/presentation/pages/general_settings_page.dart:812-840 — 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 `lib/features/settings/presentation/pages/general_settings_page.dart:718` 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.
D4 · Code Duplication · Duplicated block (28 lines × 2) · ×2
  • Duplicated block (28 lines × 2) lib/features/mobile/presentation/widgets/mobile_local_models_section.dart:143 — lib/features/mobile/presentation/widgets/mobile_local_models_section.dart:143-170 | lib/features/mobile/presentation/widgets/mobile_local_models_step.dart:216-243 — before extracting anything, compare `lib/features/mobile/presentation/widgets/mobile_local_models_section.dart` and `lib/features/mobile/presentation/widgets/mobile_local_models_step.dart` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 161 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `lib/features/mobile/presentation/widgets/mobile_local_models_section.dart:143` 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 (28 lines × 2) lib/features/onboarding/presentation/widgets/hotkeys_step.dart:355 — lib/features/onboarding/presentation/widgets/hotkeys_step.dart:355-382 | lib/features/onboarding/presentation/widgets/test_hotkeys_step.dart:223-250 — before extracting anything, compare `lib/features/onboarding/presentation/widgets/hotkeys_step.dart` and `lib/features/onboarding/presentation/widgets/test_hotkeys_step.dart` as WHOLE FILES: this scan already matched 10 separate duplicated blocks between them, totalling at least 187 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `lib/features/onboarding/presentation/widgets/hotkeys_step.dart:355` 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.
D4 · Code Duplication · Duplicated block (21 lines × 3) · ×2
  • Duplicated block (21 lines × 3) lib/features/mobile/presentation/widgets/mobile_local_models_step.dart:428 — lib/features/mobile/presentation/widgets/mobile_local_models_step.dart:428-448 | lib/features/onboarding/presentation/widgets/local_step.dart:501-521 | lib/features/settings/presentation/pages/transcription_settings_page.dart:473-493 — before extracting anything, compare `lib/features/mobile/presentation/widgets/mobile_local_models_step.dart` and `lib/features/onboarding/presentation/widgets/local_step.dart` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 133 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 `lib/features/mobile/presentation/widgets/mobile_local_models_step.dart:428` 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 (21 lines × 3) lib/features/mobile/presentation/widgets/mobile_transcription_models_section.dart:168 — lib/features/mobile/presentation/widgets/mobile_transcription_models_section.dart:168-188 | lib/features/settings/presentation/widgets/assistant_models_section.dart:187-207 | lib/features/settings/presentation/widgets/transcription_models_section.dart:189-209 — before extracting anything, compare `lib/features/settings/presentation/widgets/assistant_models_section.dart` and `lib/features/settings/presentation/widgets/transcription_models_section.dart` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 218 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `lib/features/mobile/presentation/widgets/mobile_transcription_models_section.dart:168` 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.
D4 · Code Duplication · Duplicated block (17 lines × 3) · ×2
  • Duplicated block (17 lines × 3) lib/features/settings/presentation/pages/assistant_settings_page.dart:16 — lib/features/settings/presentation/pages/assistant_settings_page.dart:16-32 | lib/features/settings/presentation/pages/output_settings_page.dart:23-39 | lib/features/settings/presentation/pages/transcription_settings_page.dart:17-33 — before extracting anything, compare `lib/features/settings/presentation/pages/assistant_settings_page.dart` and `lib/features/settings/presentation/pages/output_settings_page.dart` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 95 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `lib/features/settings/presentation/pages/assistant_settings_page.dart:16` 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `lib/features/settings/presentation/pages/output_settings_page.dart:21` calls `of` and `lib/features/settings/presentation/pages/assistant_settings_page.dart:15` 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 (17 lines × 3) lib/features/settings/presentation/widgets/assistant_hotkey_settings_section.dart:102 — lib/features/settings/presentation/widgets/assistant_hotkey_settings_section.dart:102-118 | lib/features/settings/presentation/widgets/hotkey_settings_section.dart:91-107 | lib/features/settings/presentation/widgets/transcription_hotkey_settings_section.dart:105-121 — before extracting anything, compare `lib/features/settings/presentation/widgets/assistant_hotkey_settings_section.dart` and `lib/features/settings/presentation/widgets/transcription_hotkey_settings_section.dart` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 106 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
D4 · Code Duplication · Duplicated block (15–16 lines × 2) · ×2
  • Duplicated block (15–16 lines × 2) lib/features/navigation/presentation/pages/main_layout.dart:130 — lib/features/navigation/presentation/pages/main_layout.dart:130-144 | lib/features/settings/presentation/pages/settings.dart:110-125 — 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 `lib/features/navigation/presentation/pages/main_layout.dart:130` 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 (15–16 lines × 2) lib/features/settings/presentation/widgets/smart_transcription_section.dart:63 — lib/features/settings/presentation/widgets/smart_transcription_section.dart:63-78 | lib/features/settings/presentation/widgets/transcription_hotkey_settings_section.dart:124-138 — 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 `lib/features/settings/presentation/widgets/smart_transcription_section.dart:63` 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 · Duplicated block (12–13 lines × 2) · ×2
  • Duplicated block (12–13 lines × 2) lib/features/onboarding/presentation/bloc/onboarding_bloc.dart:901 — lib/features/onboarding/presentation/bloc/onboarding_bloc.dart:901-912 | lib/features/onboarding/presentation/bloc/onboarding_bloc.dart:949-961 — 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 `lib/features/onboarding/presentation/bloc/onboarding_bloc.dart:901` 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 × 2) lib/features/settings/presentation/pages/general_settings_page.dart:115 — lib/features/settings/presentation/pages/general_settings_page.dart:115-127 | lib/features/settings/presentation/widgets/smart_transcription_section.dart:16-27 — before extracting anything, compare `lib/features/settings/presentation/pages/general_settings_page.dart` and `lib/features/settings/presentation/widgets/smart_transcription_section.dart` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 89 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 `lib/features/settings/presentation/pages/general_settings_page.dart:115` 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.
X3 · Exception handling · Swallowed exception (caught, then discarded) · ×2
  • Swallowed exception (caught, then discarded) lib/features/settings/presentation/pages/general_settings_page.dart:32 — `catch (e)` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter.
  • Swallowed exception (caught, then discarded) lib/features/onboarding/presentation/widgets/completed_step.dart:196 — `catch (e)` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter.
AX7 · Slice cohesion · Cross-slice coupling · ×1
  • Cross-slice coupling: hotkeys → assistant lib/features/hotkeys/core/hotkey_handler.dart:37 — `HotkeyHandler` (slice 'hotkeys') depends on `AssistantService` from slice 'assistant'.
D1 · Cyclomatic Complexity · PushToTalkHandler.handleKeyUp (cyclomatic 39) · ×1
  • PushToTalkHandler.handleKeyUp (cyclomatic 39) lib/features/hotkeys/handlers/push_to_talk_handler.dart:309 — PushToTalkHandler.handleKeyUp has cyclomatic complexity 39 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top. This file is where this pass's cyclomatic complexity CONCENTRATES: lib/features/hotkeys/handlers/push_to_talk_handler.dart holds 5 of the 31 methods over the threshold — including the worst — and 74 of the 248 points over it (30%), 2.5× the next-largest file (lib/features/hotkeys/handlers/transcription_hotkey_handler.dart at 30). No single row can show this, because each is measured only against the threshold: reducing this one file moves this dimension further than any other file in the repository.
D1 · Cyclomatic Complexity · PushToTalkHandler._ensureRecordingCleanup (cyclomatic 39) · ×1
  • PushToTalkHandler._ensureRecordingCleanup (cyclomatic 39) lib/features/hotkeys/handlers/push_to_talk_handler.dart:857 — PushToTalkHandler._ensureRecordingCleanup has cyclomatic complexity 39 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top. This file is where this pass's cyclomatic complexity CONCENTRATES: lib/features/hotkeys/handlers/push_to_talk_handler.dart holds 5 of the 31 methods over the threshold — including the worst — and 74 of the 248 points over it (30%), 2.5× the next-largest file (lib/features/hotkeys/handlers/transcription_hotkey_handler.dart at 30). No single row can show this, because each is measured only against the threshold: reducing this one file moves this dimension further than any other file in the repository.
D1 · Cyclomatic Complexity · TranscriptionHotkeyHandler.handleHotkey (cyclomatic 37) · ×1
  • TranscriptionHotkeyHandler.handleHotkey (cyclomatic 37) lib/features/hotkeys/handlers/transcription_hotkey_handler.dart:69 — TranscriptionHotkeyHandler.handleHotkey has cyclomatic complexity 37 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · PushToTalkHandler.handleKeyDown (cyclomatic 31) · ×1
  • PushToTalkHandler.handleKeyDown (cyclomatic 31) lib/features/hotkeys/handlers/push_to_talk_handler.dart:113 — PushToTalkHandler.handleKeyDown has cyclomatic complexity 31 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top. This file is where this pass's cyclomatic complexity CONCENTRATES: lib/features/hotkeys/handlers/push_to_talk_handler.dart holds 5 of the 31 methods over the threshold — including the worst — and 74 of the 248 points over it (30%), 2.5× the next-largest file (lib/features/hotkeys/handlers/transcription_hotkey_handler.dart at 30). No single row can show this, because each is measured only against the threshold: reducing this one file moves this dimension further than any other file in the repository.
D1 · Cyclomatic Complexity · TranscriptionBloc._onStartTranscription (cyclomatic 31) · ×1
  • TranscriptionBloc._onStartTranscription (cyclomatic 31) lib/features/transcription/presentation/bloc/transcription_bloc.dart:126 — TranscriptionBloc._onStartTranscription has cyclomatic complexity 31 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · AssistantService._sendToGroqAPI (cyclomatic 26) · ×1
  • AssistantService._sendToGroqAPI (cyclomatic 26) REDACTED:449 — AssistantService._sendToGroqAPI 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.
D1 · Cyclomatic Complexity · HotkeyRegistration.prepareHotkeys (cyclomatic 26) · ×1
  • HotkeyRegistration.prepareHotkeys (cyclomatic 26) lib/features/hotkeys/utils/hotkey_registration.dart:73 — HotkeyRegistration.prepareHotkeys 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.
D1 · Cyclomatic Complexity · ClipboardService.copyToClipboard (cyclomatic 24) · ×1
  • ClipboardService.copyToClipboard (cyclomatic 24) lib/features/hotkeys/services/clipboard_service.dart:13 — ClipboardService.copyToClipboard 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.
D1 · Cyclomatic Complexity · ApiKeyStep.build (cyclomatic 24) · ×1
  • ApiKeyStep.build (cyclomatic 24) lib/features/onboarding/presentation/widgets/api_key_step.dart:12 — ApiKeyStep.build 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.
D1 · Cyclomatic Complexity · TranscriptionRepositoryImpl._transcribeAudioRemotely (cyclomatic 24) · ×1
  • TranscriptionRepositoryImpl._transcribeAudioRemotely (cyclomatic 24) lib/features/transcription/data/repositories/transcription_repository_impl.dart:145 — TranscriptionRepositoryImpl._transcribeAudioRemotely 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.
D1 · Cyclomatic Complexity · PushToTalkHandler._transcribeAndCopyToClipboard (cyclomatic 23) · ×1
  • PushToTalkHandler._transcribeAndCopyToClipboard (cyclomatic 23) lib/features/hotkeys/handlers/push_to_talk_handler.dart:492 — PushToTalkHandler._transcribeAndCopyToClipboard has cyclomatic complexity 23 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top. This file is where this pass's cyclomatic complexity CONCENTRATES: lib/features/hotkeys/handlers/push_to_talk_handler.dart holds 5 of the 31 methods over the threshold — including the worst — and 74 of the 248 points over it (30%), 2.5× the next-largest file (lib/features/hotkeys/handlers/transcription_hotkey_handler.dart at 30). No single row can show this, because each is measured only against the threshold: reducing this one file moves this dimension further than any other file in the repository.
D1 · Cyclomatic Complexity · TranscriptionHotkeyHandler._transcribeAndCopyToClipboard (cyclomatic 23) · ×1
  • TranscriptionHotkeyHandler._transcribeAndCopyToClipboard (cyclomatic 23) lib/features/hotkeys/handlers/transcription_hotkey_handler.dart:278 — TranscriptionHotkeyHandler._transcribeAndCopyToClipboard has cyclomatic complexity 23 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · OnboardingBloc._onInitializeOnboarding (cyclomatic 23) · ×1
  • OnboardingBloc._onInitializeOnboarding (cyclomatic 23) lib/features/onboarding/presentation/bloc/onboarding_bloc.dart:264 — OnboardingBloc._onInitializeOnboarding has cyclomatic complexity 23 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · OnboardingPage.build (cyclomatic 23) · ×1
  • OnboardingPage.build (cyclomatic 23) lib/features/onboarding/presentation/pages/onboarding_page.dart:21 — OnboardingPage.build has cyclomatic complexity 23 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · MinimalistToggle.build (cyclomatic 23) · ×1
  • MinimalistToggle.build (cyclomatic 23) lib/widgets/minimalist_toggle.dart:50 — MinimalistToggle.build 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.
D1 · Cyclomatic Complexity · RecordingDataSourceImpl._setupAudioStreamProcessing (cyclomatic 22) · ×1
  • RecordingDataSourceImpl._setupAudioStreamProcessing (cyclomatic 22) lib/features/recording/data/datasources/recording_datasource.dart:232 — RecordingDataSourceImpl._setupAudioStreamProcessing 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.
D1 · Cyclomatic Complexity · OnboardingBloc._onCheckPermissions (cyclomatic 21) · ×1
  • OnboardingBloc._onCheckPermissions (cyclomatic 21) lib/features/onboarding/presentation/bloc/onboarding_bloc.dart:401 — OnboardingBloc._onCheckPermissions 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.
D1 · Cyclomatic Complexity · _MinimalistInputState.build (cyclomatic 21) · ×1
  • _MinimalistInputState.build (cyclomatic 21) lib/widgets/minimalist_input.dart:116 — _MinimalistInputState.build has cyclomatic complexity 21 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
D1 · Cyclomatic Complexity · LocalStep._buildModelSelectionSection (cyclomatic 20) · ×1
  • LocalStep._buildModelSelectionSection (cyclomatic 20) lib/features/onboarding/presentation/widgets/local_step.dart:200 — LocalStep._buildModelSelectionSection 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.
D1 · Cyclomatic Complexity · AudioUtils.validateAudioFile (cyclomatic 20) · ×1
  • AudioUtils.validateAudioFile (cyclomatic 20) lib/features/recording/utils/audio_utils.dart:8 — AudioUtils.validateAudioFile 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.
D1 · Cyclomatic Complexity · MinimalistButton.build (cyclomatic 20) · ×1
  • MinimalistButton.build (cyclomatic 20) lib/widgets/minimalist_button.dart:69 — MinimalistButton.build 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.
D1 · Cyclomatic Complexity · _SettingsPageState.build (cyclomatic 19) · ×1
  • _SettingsPageState.build (cyclomatic 19) lib/features/settings/presentation/pages/settings.dart:76 — _SettingsPageState.build 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.
D1 · Cyclomatic Complexity · MainFlutterWindow.setupMethodChannel (cyclomatic 19) · ×1
  • MainFlutterWindow.setupMethodChannel (cyclomatic 19) macos/Runner/MainFlutterWindow.swift:25 — MainFlutterWindow.setupMethodChannel 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.
D1 · Cyclomatic Complexity · TranscriptionSettingsPage._buildModelSelectionSection (cyclomatic 18) · ×1
  • TranscriptionSettingsPage._buildModelSelectionSection (cyclomatic 18) lib/features/settings/presentation/pages/transcription_settings_page.dart:191 — TranscriptionSettingsPage._buildModelSelectionSection 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.
D1 · Cyclomatic Complexity · AssistantService._stopRecordingAndProcess (cyclomatic 17) · ×1
  • AssistantService._stopRecordingAndProcess (cyclomatic 17) REDACTED:313 — AssistantService._stopRecordingAndProcess 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.
D1 · Cyclomatic Complexity · HotkeyHandler.keyDownHandler (cyclomatic 17) · ×1
  • HotkeyHandler.keyDownHandler (cyclomatic 17) lib/features/hotkeys/core/hotkey_handler.dart:74 — HotkeyHandler.keyDownHandler 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.
D1 · Cyclomatic Complexity · PushToTalkHandler.cancelRecording (cyclomatic 17) · ×1
  • PushToTalkHandler.cancelRecording (cyclomatic 17) lib/features/hotkeys/handlers/push_to_talk_handler.dart:753 — PushToTalkHandler.cancelRecording 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. This file is where this pass's cyclomatic complexity CONCENTRATES: lib/features/hotkeys/handlers/push_to_talk_handler.dart holds 5 of the 31 methods over the threshold — including the worst — and 74 of the 248 points over it (30%), 2.5× the next-largest file (lib/features/hotkeys/handlers/transcription_hotkey_handler.dart at 30). No single row can show this, because each is measured only against the threshold: reducing this one file moves this dimension further than any other file in the repository.
D1 · Cyclomatic Complexity · OutputSettingsPage._buildLanguageSection (cyclomatic 17) · ×1
  • OutputSettingsPage._buildLanguageSection (cyclomatic 17) lib/features/settings/presentation/pages/output_settings_page.dart:57 — OutputSettingsPage._buildLanguageSection 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.
D1 · Cyclomatic Complexity · PhraseReplacementService.applyReplacements (cyclomatic 17) · ×1
  • PhraseReplacementService.applyReplacements (cyclomatic 17) lib/features/transcription/services/phrase_replacement_service.dart:4 — PhraseReplacementService.applyReplacements has cyclomatic complexity 17 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function so the top-level body reads as a short sequence of named decisions.
D1 · Cyclomatic Complexity · PermissionsStep._buildPermissionCard (cyclomatic 16) · ×1
  • PermissionsStep._buildPermissionCard (cyclomatic 16) lib/features/onboarding/presentation/widgets/permissions_step.dart:241 — PermissionsStep._buildPermissionCard 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.
D1 · Cyclomatic Complexity · _EnhancedButtonState.build (cyclomatic 16) · ×1
  • _EnhancedButtonState.build (cyclomatic 16) lib/widgets/enhanced_button.dart:212 — _EnhancedButtonState.build 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.
D2 · Cognitive Complexity · TranscriptionHotkeyHandler.handleHotkey (cognitive 122) · ×1
  • TranscriptionHotkeyHandler.handleHotkey (cognitive 122) lib/features/hotkeys/handlers/transcription_hotkey_handler.dart:69 — TranscriptionHotkeyHandler.handleHotkey has cognitive complexity 122 (threshold 15). Drivers by points: if/else 29 (95 pts), error handling 8 (25 pts), boolean chains 2 (nesting depth added 83). 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.
D2 · Cognitive Complexity · PushToTalkHandler._ensureRecordingCleanup (cognitive 105) · ×1
  • PushToTalkHandler._ensureRecordingCleanup (cognitive 105) lib/features/hotkeys/handlers/push_to_talk_handler.dart:857 — PushToTalkHandler._ensureRecordingCleanup has cognitive complexity 105 (threshold 15). Drivers by points: if/else 28 (82 pts), error handling 6 (15 pts), loops 2 (5 pts), boolean chains 3 (nesting depth added 66). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · AssistantService._sendToGroqAPI (cognitive 93) · ×1
  • AssistantService._sendToGroqAPI (cognitive 93) REDACTED:449 — AssistantService._sendToGroqAPI has cognitive complexity 93 (threshold 15). Drivers by points: if/else 25 (76 pts), error handling 4 (11 pts), ternaries 2 (6 pts) (nesting depth added 62). 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.
D2 · Cognitive Complexity · PushToTalkHandler.handleKeyUp (cognitive 88) · ×1
  • PushToTalkHandler.handleKeyUp (cognitive 88) lib/features/hotkeys/handlers/push_to_talk_handler.dart:309 — PushToTalkHandler.handleKeyUp has cognitive complexity 88 (threshold 15). Drivers by points: if/else 30 (68 pts), error handling 4 (11 pts), ternaries 3 (7 pts), boolean chains 2 (nesting depth added 49). 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.
D2 · Cognitive Complexity · OnboardingBloc._onCheckPermissions (cognitive 83) · ×1
  • OnboardingBloc._onCheckPermissions (cognitive 83) lib/features/onboarding/presentation/bloc/onboarding_bloc.dart:401 — OnboardingBloc._onCheckPermissions has cognitive complexity 83 (threshold 15). Drivers by points: if/else 20 (73 pts), loops 2 (7 pts), boolean chains 2, error handling 1 (nesting depth added 58). 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.
D2 · Cognitive Complexity · TranscriptionBloc._onStartTranscription (cognitive 77) · ×1
  • TranscriptionBloc._onStartTranscription (cognitive 77) lib/features/transcription/presentation/bloc/transcription_bloc.dart:126 — TranscriptionBloc._onStartTranscription has cognitive complexity 77 (threshold 15). Drivers by points: if/else 23 (63 pts), error handling 4 (11 pts), boolean chains 3 (nesting depth added 47). 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.
D2 · Cognitive Complexity · HotkeyRegistration.prepareHotkeys (cognitive 75) · ×1
  • HotkeyRegistration.prepareHotkeys (cognitive 75) lib/features/hotkeys/utils/hotkey_registration.dart:73 — HotkeyRegistration.prepareHotkeys has cognitive complexity 75 (threshold 15). Drivers by points: if/else 20 (64 pts), error handling 4 (10 pts), boolean chains 1 (nesting depth added 50). 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.
D2 · Cognitive Complexity · PushToTalkHandler.handleKeyDown (cognitive 71) · ×1
  • PushToTalkHandler.handleKeyDown (cognitive 71) lib/features/hotkeys/handlers/push_to_talk_handler.dart:113 — PushToTalkHandler.handleKeyDown has cognitive complexity 71 (threshold 15). Drivers by points: if/else 28 (64 pts), error handling 3 (6 pts), boolean chains 1 (nesting depth added 39). 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.
D2 · Cognitive Complexity · OnboardingBloc._onInitializeOnboarding (cognitive 67) · ×1
  • OnboardingBloc._onInitializeOnboarding (cognitive 67) lib/features/onboarding/presentation/bloc/onboarding_bloc.dart:264 — OnboardingBloc._onInitializeOnboarding has cognitive complexity 67 (threshold 15). Drivers by points: if/else 18 (56 pts), loops 2 (6 pts), boolean chains 2, ternaries 1 (2 pts), error handling 1 (nesting depth added 43). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · RecordingDataSourceImpl._setupAudioStreamProcessing (cognitive 63) · ×1
  • RecordingDataSourceImpl._setupAudioStreamProcessing (cognitive 63) lib/features/recording/data/datasources/recording_datasource.dart:232 — RecordingDataSourceImpl._setupAudioStreamProcessing has cognitive complexity 63 (threshold 15). Drivers by points: if/else 14 (49 pts), error handling 3 (8 pts), boolean chains 4, loops 1 (2 pts) (nesting depth added 41). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · PushToTalkHandler._transcribeAndCopyToClipboard (cognitive 61) · ×1
  • PushToTalkHandler._transcribeAndCopyToClipboard (cognitive 61) lib/features/hotkeys/handlers/push_to_talk_handler.dart:492 — PushToTalkHandler._transcribeAndCopyToClipboard has cognitive complexity 61 (threshold 15). Drivers by points: if/else 15 (46 pts), error handling 4 (11 pts), boolean chains 4 (nesting depth added 38). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · ClipboardService.copyToClipboard (cognitive 60) · ×1
  • ClipboardService.copyToClipboard (cognitive 60) lib/features/hotkeys/services/clipboard_service.dart:13 — ClipboardService.copyToClipboard has cognitive complexity 60 (threshold 15). Drivers by points: if/else 16 (45 pts), error handling 4 (10 pts), match/switch 1 (3 pts), boolean chains 2 (nesting depth added 37). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · TranscriptionHotkeyHandler._transcribeAndCopyToClipboard (cognitive 53) · ×1
  • TranscriptionHotkeyHandler._transcribeAndCopyToClipboard (cognitive 53) lib/features/hotkeys/handlers/transcription_hotkey_handler.dart:278 — TranscriptionHotkeyHandler._transcribeAndCopyToClipboard has cognitive complexity 53 (threshold 15). Drivers by points: if/else 14 (40 pts), error handling 4 (9 pts), boolean chains 4 (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.
D2 · Cognitive Complexity · AssistantService._stopRecordingAndProcess (cognitive 48) · ×1
  • AssistantService._stopRecordingAndProcess (cognitive 48) REDACTED:313 — AssistantService._stopRecordingAndProcess has cognitive complexity 48 (threshold 15). Drivers by points: if/else 11 (35 pts), error handling 4 (11 pts), boolean chains 2 (nesting depth added 31). 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.
D2 · Cognitive Complexity · PushToTalkHandler.cancelRecording (cognitive 43) · ×1
  • PushToTalkHandler.cancelRecording (cognitive 43) lib/features/hotkeys/handlers/push_to_talk_handler.dart:753 — PushToTalkHandler.cancelRecording has cognitive complexity 43 (threshold 15). Drivers by points: if/else 14 (37 pts), error handling 3 (6 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.
D2 · Cognitive Complexity · RecordingDataSourceImpl.stopRecording (cognitive 43) · ×1
  • RecordingDataSourceImpl.stopRecording (cognitive 43) lib/features/recording/data/datasources/recording_datasource.dart:402 — RecordingDataSourceImpl.stopRecording has cognitive complexity 43 (threshold 15). Drivers by points: if/else 12 (35 pts), error handling 2 (8 pts) (nesting depth added 29). 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.
D2 · Cognitive Complexity · OnboardingPage.build (cognitive 40) · ×1
  • OnboardingPage.build (cognitive 40) lib/features/onboarding/presentation/pages/onboarding_page.dart:21 — OnboardingPage.build has cognitive complexity 40 (threshold 15). Drivers by points: ternaries 14 (24 pts), if/else 10 (15 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.
D2 · Cognitive Complexity · ApiKeyStep.build (cognitive 40) · ×1
  • ApiKeyStep.build (cognitive 40) lib/features/onboarding/presentation/widgets/api_key_step.dart:12 — ApiKeyStep.build has cognitive complexity 40 (threshold 15). Drivers by points: if/else 10 (19 pts), ternaries 4 (10 pts), boolean chains 8, error handling 2 (3 pts) (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.
D2 · Cognitive Complexity · TranscriptionRepositoryImpl._transcribeAudioRemotely (cognitive 39) · ×1
  • TranscriptionRepositoryImpl._transcribeAudioRemotely (cognitive 39) lib/features/transcription/data/repositories/transcription_repository_impl.dart:145 — TranscriptionRepositoryImpl._transcribeAudioRemotely has cognitive complexity 39 (threshold 15). Drivers by points: if/else 19 (32 pts), boolean chains 3, error handling 2, ternaries 1 (2 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.
D2 · Cognitive Complexity · AudioUtils.validateAudioFile (cognitive 37) · ×1
  • AudioUtils.validateAudioFile (cognitive 37) lib/features/recording/utils/audio_utils.dart:8 — AudioUtils.validateAudioFile has cognitive complexity 37 (threshold 15). Drivers by points: if/else 10 (28 pts), boolean chains 8, error handling 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.
D2 · Cognitive Complexity · AssistantService._getHotkeyDisplayString (cognitive 36) · ×1
  • AssistantService._getHotkeyDisplayString (cognitive 36) REDACTED:729 — AssistantService._getHotkeyDisplayString has cognitive complexity 36 (threshold 15). Drivers by points: if/else 9 (28 pts), error handling 2 (4 pts), ternaries 1 (4 pts) (nesting depth added 24). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · PushToTalkHandler._getHotkeyDisplayString (cognitive 36) · ×1
  • PushToTalkHandler._getHotkeyDisplayString (cognitive 36) lib/features/hotkeys/handlers/push_to_talk_handler.dart:655 — PushToTalkHandler._getHotkeyDisplayString has cognitive complexity 36 (threshold 15). Drivers by points: if/else 9 (28 pts), error handling 2 (4 pts), ternaries 1 (4 pts) (nesting depth added 24). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · TranscriptionHotkeyHandler._getHotkeyDisplayString (cognitive 36) · ×1
  • TranscriptionHotkeyHandler._getHotkeyDisplayString (cognitive 36) lib/features/hotkeys/handlers/transcription_hotkey_handler.dart:420 — TranscriptionHotkeyHandler._getHotkeyDisplayString has cognitive complexity 36 (threshold 15). Drivers by points: if/else 9 (28 pts), error handling 2 (4 pts), ternaries 1 (4 pts) (nesting depth added 24). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · AssistantService.cancelRecording (cognitive 35) · ×1
  • AssistantService.cancelRecording (cognitive 35) REDACTED:825 — AssistantService.cancelRecording has cognitive complexity 35 (threshold 15). Drivers by points: if/else 11 (31 pts), error handling 2 (4 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.
D2 · Cognitive Complexity · TranscriptionHotkeyHandler.cancelRecording (cognitive 35) · ×1
  • TranscriptionHotkeyHandler.cancelRecording (cognitive 35) lib/features/hotkeys/handlers/transcription_hotkey_handler.dart:518 — TranscriptionHotkeyHandler.cancelRecording has cognitive complexity 35 (threshold 15). Drivers by points: if/else 11 (31 pts), error handling 2 (4 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.
D2 · Cognitive Complexity · AssistantService._startRecording (cognitive 34) · ×1
  • AssistantService._startRecording (cognitive 34) REDACTED:235 — AssistantService._startRecording has cognitive complexity 34 (threshold 15). Drivers by points: if/else 10 (30 pts), error handling 2 (4 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.
D2 · Cognitive Complexity · WhisperKitService.downloadModel (cognitive 32) · ×1
  • WhisperKitService.downloadModel (cognitive 32) lib/core/services/whisper_kit_service.dart:36 — WhisperKitService.downloadModel has cognitive complexity 32 (threshold 15). Drivers by points: if/else 12 (29 pts), loops 1 (2 pts), error handling 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.
D2 · Cognitive Complexity · PhraseReplacementService.applyReplacements (cognitive 29) · ×1
  • PhraseReplacementService.applyReplacements (cognitive 29) lib/features/transcription/services/phrase_replacement_service.dart:4 — PhraseReplacementService.applyReplacements has cognitive complexity 29 (threshold 15). Drivers by points: if/else 5 (13 pts), boolean chains 8, loops 3 (8 pts) (nesting depth added 13). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · HotkeyRegistration.ensureHotkeysLoadedAfterOnboarding (cognitive 28) · ×1
  • HotkeyRegistration.ensureHotkeysLoadedAfterOnboarding (cognitive 28) lib/features/hotkeys/utils/hotkey_registration.dart:367 — HotkeyRegistration.ensureHotkeysLoadedAfterOnboarding has cognitive complexity 28 (threshold 15). Drivers by points: if/else 10 (27 pts), error handling 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.
D2 · Cognitive Complexity · PermissionsStep._buildPermissionCard (cognitive 28) · ×1
  • PermissionsStep._buildPermissionCard (cognitive 28) lib/features/onboarding/presentation/widgets/permissions_step.dart:241 — PermissionsStep._buildPermissionCard has cognitive complexity 28 (threshold 15). Drivers by points: if/else 9 (14 pts), ternaries 5 (13 pts), match/switch 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.
D2 · Cognitive Complexity · _MinimalistInputState.build (cognitive 25) · ×1
  • _MinimalistInputState.build (cognitive 25) lib/widgets/minimalist_input.dart:116 — _MinimalistInputState.build has cognitive complexity 25 (threshold 15). Drivers by points: ternaries 11 (16 pts), if/else 6, boolean chains 3 (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.
D2 · Cognitive Complexity · VolumeService.muteVolume (cognitive 23) · ×1
  • VolumeService.muteVolume (cognitive 23) lib/core/services/volume_service.dart:60 — VolumeService.muteVolume has cognitive complexity 23 (threshold 15). Drivers by points: if/else 9 (21 pts), boolean chains 1, error handling 1 (nesting depth added 12). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body. This shape REPEATS in the file: one other method here (VolumeService.restoreVolume) 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.
D2 · Cognitive Complexity · VolumeService.restoreVolume (cognitive 23) · ×1
  • VolumeService.restoreVolume (cognitive 23) lib/core/services/volume_service.dart:113 — VolumeService.restoreVolume has cognitive complexity 23 (threshold 15). Drivers by points: if/else 9 (21 pts), boolean chains 1, error handling 1 (nesting depth added 12). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body. This shape REPEATS in the file: one other method here (VolumeService.muteVolume) 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.
D2 · Cognitive Complexity · HotkeyHandler.keyDownHandler (cognitive 22) · ×1
  • HotkeyHandler.keyDownHandler (cognitive 22) lib/features/hotkeys/core/hotkey_handler.dart:74 — HotkeyHandler.keyDownHandler has cognitive complexity 22 (threshold 15). Drivers by points: if/else 15 (21 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.
D2 · Cognitive Complexity · SmartTranscriptionService.enhanceTranscription (cognitive 22) · ×1
  • SmartTranscriptionService.enhanceTranscription (cognitive 22) lib/features/transcription/services/smart_transcription_service.dart:131 — SmartTranscriptionService.enhanceTranscription has cognitive complexity 22 (threshold 15). Drivers by points: if/else 9 (20 pts), boolean chains 1, error handling 1 (nesting depth added 11). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · OnboardingBloc._onRequestPermission (cognitive 21) · ×1
  • OnboardingBloc._onRequestPermission (cognitive 21) lib/features/onboarding/presentation/bloc/onboarding_bloc.dart:528 — OnboardingBloc._onRequestPermission has cognitive complexity 21 (threshold 15). Drivers by points: if/else 8 (20 pts), error handling 1 (nesting depth added 12). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · WhisperKitService.transcribeAudio (cognitive 20) · ×1
  • WhisperKitService.transcribeAudio (cognitive 20) lib/core/services/whisper_kit_service.dart:216 — WhisperKitService.transcribeAudio has cognitive complexity 20 (threshold 15). Drivers by points: if/else 5 (15 pts), error handling 2 (4 pts), boolean chains 1 (nesting depth added 12). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · MinimalistToggle.build (cognitive 20) · ×1
  • MinimalistToggle.build (cognitive 20) lib/widgets/minimalist_toggle.dart:50 — MinimalistToggle.build has cognitive complexity 20 (threshold 15). Drivers by points: ternaries 13, if/else 4, boolean chains 2, match/switch 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.
D2 · Cognitive Complexity · LocalStep._buildModelSelectionSection (cognitive 19) · ×1
  • LocalStep._buildModelSelectionSection (cognitive 19) lib/features/onboarding/presentation/widgets/local_step.dart:200 — LocalStep._buildModelSelectionSection has cognitive complexity 19 (threshold 15). Drivers by points: ternaries 16, if/else 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.
D2 · Cognitive Complexity · _EnhancedButtonState.build (cognitive 19) · ×1
  • _EnhancedButtonState.build (cognitive 19) lib/widgets/enhanced_button.dart:212 — _EnhancedButtonState.build has cognitive complexity 19 (threshold 15). Drivers by points: ternaries 9 (11 pts), boolean chains 4, if/else 3 (4 pts) (nesting depth added 3). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
D2 · Cognitive Complexity · MinimalistButton.build (cognitive 19) · ×1
  • MinimalistButton.build (cognitive 19) lib/widgets/minimalist_button.dart:69 — MinimalistButton.build has cognitive complexity 19 (threshold 15). Drivers by points: if/else 7 (8 pts), ternaries 5 (6 pts), boolean chains 4, match/switch 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.
D2 · Cognitive Complexity · MobileOnboardingPage.build (cognitive 18) · ×1
  • MobileOnboardingPage.build (cognitive 18) lib/features/mobile/presentation/pages/mobile_onboarding_page.dart:18 — MobileOnboardingPage.build has cognitive complexity 18 (threshold 15). Drivers by points: ternaries 7 (10 pts), if/else 6 (8 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.
D2 · Cognitive Complexity · _GeneralSettingsPageState._selectInputDevice (cognitive 18) · ×1
  • _GeneralSettingsPageState._selectInputDevice (cognitive 18) lib/features/settings/presentation/pages/general_settings_page.dart:888 — _GeneralSettingsPageState._selectInputDevice has cognitive complexity 18 (threshold 15). Drivers by points: if/else 6 (14 pts), ternaries 1 (3 pts), error handling 1 (nesting depth added 10). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · _SettingsPageState.build (cognitive 18) · ×1
  • _SettingsPageState.build (cognitive 18) lib/features/settings/presentation/pages/settings.dart:76 — _SettingsPageState.build has cognitive complexity 18 (threshold 15). Drivers by points: ternaries 16, if/else 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.
D2 · Cognitive Complexity · _SnackbarContent.build (cognitive 18) · ×1
  • _SnackbarContent.build (cognitive 18) lib/widgets/minimalist_snackbar.dart:130 — _SnackbarContent.build has cognitive complexity 18 (threshold 15). Drivers by points: ternaries 8 (16 pts), if/else 1, 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.
D2 · Cognitive Complexity · MainFlutterWindow.setupMethodChannel (cognitive 18) · ×1
  • MainFlutterWindow.setupMethodChannel (cognitive 18) macos/Runner/MainFlutterWindow.swift:25 — MainFlutterWindow.setupMethodChannel has cognitive complexity 18 (threshold 15). Drivers by points: if/else 9 (13 pts), boolean chains 4, match/switch 1 (nesting depth added 4). 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.
D2 · Cognitive Complexity · SoundPlayer._playSoundFile (cognitive 17) · ×1
  • SoundPlayer._playSoundFile (cognitive 17) lib/core/utils/sound_player.dart:79 — SoundPlayer._playSoundFile has cognitive complexity 17 (threshold 15). Drivers by points: if/else 7 (16 pts), error handling 1 (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · SettingsBloc._onAutoInitializeSelectedModel (cognitive 17) · ×1
  • SettingsBloc._onAutoInitializeSelectedModel (cognitive 17) lib/features/settings/presentation/bloc/settings_bloc.dart:1305 — SettingsBloc._onAutoInitializeSelectedModel has cognitive complexity 17 (threshold 15). Drivers by points: if/else 7 (16 pts), error handling 1 (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · TranscriptionSettingsPage._buildModelSelectionSection (cognitive 17) · ×1
  • TranscriptionSettingsPage._buildModelSelectionSection (cognitive 17) lib/features/settings/presentation/pages/transcription_settings_page.dart:191 — TranscriptionSettingsPage._buildModelSelectionSection has cognitive complexity 17 (threshold 15). Drivers by points: ternaries 15, if/else 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.
D2 · Cognitive Complexity · WhisperKitService.initializeModelWithTestAudio (cognitive 16) · ×1
  • WhisperKitService.initializeModelWithTestAudio (cognitive 16) lib/core/services/whisper_kit_service.dart:283 — WhisperKitService.initializeModelWithTestAudio has cognitive complexity 16 (threshold 15). Drivers by points: if/else 7 (15 pts), error handling 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.
D2 · Cognitive Complexity · RecordingDataSourceImpl.startRecording (cognitive 16) · ×1
  • RecordingDataSourceImpl.startRecording (cognitive 16) lib/features/recording/data/datasources/recording_datasource.dart:141 — RecordingDataSourceImpl.startRecording has cognitive complexity 16 (threshold 15). Drivers by points: if/else 10 (14 pts), error handling 1 (2 pts) (nesting depth added 5). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · OutputSettingsPage._buildLanguageSection (cognitive 16) · ×1
  • OutputSettingsPage._buildLanguageSection (cognitive 16) lib/features/settings/presentation/pages/output_settings_page.dart:57 — OutputSettingsPage._buildLanguageSection has cognitive complexity 16 (threshold 15). Drivers by points: ternaries 12, boolean chains 2, if/else 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.
D2 · Cognitive Complexity · TranscriptionRepositoryImpl.transcribeAudio (cognitive 16) · ×1
  • TranscriptionRepositoryImpl.transcribeAudio (cognitive 16) lib/features/transcription/data/repositories/transcription_repository_impl.dart:27 — TranscriptionRepositoryImpl.transcribeAudio has cognitive complexity 16 (threshold 15). Drivers by points: if/else 10 (16 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.
D35 · Change Coupling · Change-coupling hub · ×1
  • Change-coupling hub: transcription_hotkey_handler.dart → REDACTED, push_to_talk_handler.dart, transcription_bloc.dart lib/features/hotkeys/handlers/transcription_hotkey_handler.dart — `lib/features/hotkeys/handlers/transcription_hotkey_handler.dart` changes together with 3 other files — `REDACTED`, `lib/features/hotkeys/handlers/push_to_talk_handler.dart`, `lib/features/transcription/presentation/bloc/transcription_bloc.dart` — none of which declares a dependency on it: one file is the hub of 3 separate couplings, not 3 unrelated pairs. Read the hub first: if the others each duplicate a part of what it does, the shared concern belongs in ONE unit and extracting it clears every edge at once; if the hub is a registry, dispatcher or barrel that must name each of them, the coupling is structural and the question is whether that list can be discovered instead of enumerated. Fixing the hub is one change; breaking the couplings one pair at a time is 3.
D4 · Code Duplication · Near-duplicate member family (4 members, 50 shared lines) · ×1
  • Near-duplicate member family (4 members, 50 shared lines) lib/features/mobile/presentation/widgets/mobile_api_key_step.dart:25 — lib/features/mobile/presentation/widgets/mobile_api_key_step.dart:25-299 | lib/features/mobile/presentation/widgets/mobile_keyboard_extension_step.dart:7-244 | lib/features/mobile/presentation/widgets/mobile_local_models_step.dart:11-212 | lib/features/mobile/presentation/widgets/mobile_permissions_step.dart:11-207 — These 4 members are variants of one another: a block of 50 lines reported below appears in every one of them, and the pairwise near-duplicate rows they would otherwise produce are collapsed into this row. Read them as one construct written 4 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 4 times.
D4 · Code Duplication · Near-duplicate member family (4 members, 48 shared lines) · ×1
  • Near-duplicate member family (4 members, 48 shared lines) lib/features/settings/presentation/pages/assistant_settings_page.dart:57 — lib/features/settings/presentation/pages/assistant_settings_page.dart:57-154 | lib/features/settings/presentation/pages/general_settings_page.dart:112-296 | lib/features/settings/presentation/pages/general_settings_page.dart:298-457 | lib/features/settings/presentation/pages/transcription_settings_page.dart:58-177 — These 4 members are variants of one another: a block of 48 lines reported below appears in every one of them, and the pairwise near-duplicate rows they would otherwise produce are collapsed into this row. Read them as one construct written 4 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 4 times.
D4 · Code Duplication · Near-duplicate member family (4 members, 37 shared lines) · ×1
  • Near-duplicate member family (4 members, 37 shared lines) lib/features/settings/presentation/pages/general_settings_page.dart:112 — lib/features/settings/presentation/pages/general_settings_page.dart:112-296 | lib/features/settings/presentation/pages/general_settings_page.dart:298-457 | lib/features/settings/presentation/pages/transcription_settings_page.dart:58-177 | lib/features/settings/presentation/widgets/smart_transcription_section.dart:12-60 — These 4 members are variants of one another: a block of 37 lines reported below appears in every one of them, and the pairwise near-duplicate rows they would otherwise produce are collapsed into this row. Read them as one construct written 4 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 4 times.
D4 · Code Duplication · Near-duplicate member family (3 members, 44 shared lines) · ×1
  • Near-duplicate member family (3 members, 44 shared lines) lib/features/mobile/presentation/widgets/mobile_local_models_step.dart:409 — lib/features/mobile/presentation/widgets/mobile_local_models_step.dart:409-494 | lib/features/onboarding/presentation/widgets/local_step.dart:485-571 | lib/features/settings/presentation/pages/transcription_settings_page.dart:457-571 — These 3 members are variants of one another: a block of 44 lines reported below appears in every one of them, and the pairwise near-duplicate rows they would otherwise produce are collapsed into this row. Read them as one construct written 3 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 3 times.
D4 · Code Duplication · Near-duplicate member family (3 members, 26 shared lines) · ×1
  • Near-duplicate member family (3 members, 26 shared lines) lib/features/settings/presentation/pages/general_settings_page.dart:631 — lib/features/settings/presentation/pages/general_settings_page.dart:631-746 | lib/features/settings/presentation/pages/general_settings_page.dart:748-840 | lib/features/settings/presentation/pages/output_settings_page.dart:57-263 — These 3 members are variants of one another: a block of 26 lines reported below appears in every one of them, and the pairwise near-duplicate rows they would otherwise produce are collapsed into this row. Read them as one construct written 3 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 3 times.
D4 · Code Duplication · Near-duplicate member pair (201 shared lines) · ×1
  • Near-duplicate member pair (201 shared lines) lib/features/onboarding/presentation/widgets/local_step.dart:200 — lib/features/onboarding/presentation/widgets/local_step.dart:200-471 | lib/features/settings/presentation/pages/transcription_settings_page.dart:191-455 — These two members are variants of one another: 201 of their lines are already reported as duplicated blocks below, spread through both bodies rather than gathered into one. Read them as a single construct written twice. The repair is at the members' grain — factor the shared pipeline into one implementation the two call with their differences as parameters or as an injected step, or, where the difference is systematic (sync against async, one transport against another), generate one from the other. Extracting the individual blocks below is not the same fix: it leaves the two bodies in place and the next edit still has to be made twice.
D4 · Code Duplication · Near-duplicate member pair (142 shared lines) · ×1
  • Near-duplicate member pair (142 shared lines) lib/features/mobile/presentation/widgets/mobile_local_models_section.dart:142 — lib/features/mobile/presentation/widgets/mobile_local_models_section.dart:142-340 | lib/features/mobile/presentation/widgets/mobile_local_models_step.dart:214-407 — These two members are variants of one another: 142 of their lines are already reported as duplicated blocks below, spread through both bodies rather than gathered into one. Read them as a single construct written twice. The repair is at the members' grain — factor the shared pipeline into one implementation the two call with their differences as parameters or as an injected step, or, where the difference is systematic (sync against async, one transport against another), generate one from the other. Extracting the individual blocks below is not the same fix: it leaves the two bodies in place and the next edit still has to be made twice.
D4 · Code Duplication · Near-duplicate member pair (58 shared lines) · ×1
  • Near-duplicate member pair (58 shared lines) lib/features/settings/presentation/pages/output_settings_page.dart:265 — lib/features/settings/presentation/pages/output_settings_page.dart:265-434 | lib/features/settings/presentation/pages/output_settings_page.dart:436-645 — These two members are variants of one another: 58 of their lines are already reported as duplicated blocks below, spread through both bodies rather than gathered into one. Read them as a single construct written twice. The repair is at the members' grain — factor the shared pipeline into one implementation the two call with their differences as parameters or as an injected step, or, where the difference is systematic (sync against async, one transport against another), generate one from the other. Extracting the individual blocks below is not the same fix: it leaves the two bodies in place and the next edit still has to be made twice.
D4 · Code Duplication · Members sharing a duplicated core (8 members, 50+ identical tokens) · ×1
  • Members sharing a duplicated core (8 members, 50+ identical tokens) macos/Runner/AppDelegate.swift:170 — macos/Runner/AppDelegate.swift:170-214 | macos/Runner/AppDelegate.swift:264-290 | macos/Runner/AppDelegate.swift:297-306 | macos/Runner/AppDelegate.swift:308-317 | macos/Runner/AppDelegate.swift:319-328 | macos/Runner/AppDelegate.swift:362-381 | macos/Runner/AppDelegate.swift:383-402 | macos/Runner/AppDelegate.swift:404-413 — These 8 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 8 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 8 times.
D4 · Code Duplication · Edited copy of a member (82 corresponding lines) · ×1
  • Edited copy of a member (82 corresponding lines) lib/features/mobile/presentation/pages/mobile_onboarding_page.dart:241 — lib/features/mobile/presentation/pages/mobile_onboarding_page.dart:241-339 | lib/features/onboarding/presentation/widgets/welcome_step.dart:6-87 — These two members are one piece of code written twice and then edited apart: 82 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copy of a member (60 corresponding lines) · ×1
  • Edited copy of a member (60 corresponding lines) lib/features/onboarding/presentation/bloc/onboarding_state.dart:76 — lib/features/onboarding/presentation/bloc/onboarding_state.dart:76-135 | lib/features/settings/presentation/bloc/settings_state.dart:131-208 — These two members are one piece of code written twice and then edited apart: 60 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copy of a member (41 corresponding lines) · ×1
  • Edited copy of a member (41 corresponding lines) lib/features/settings/presentation/bloc/settings_bloc.dart:352 — lib/features/settings/presentation/bloc/settings_bloc.dart:352-394 | lib/features/settings/presentation/bloc/settings_bloc.dart:678-718 — These two members are one piece of code written twice and then edited apart: 41 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copy of a member (61 corresponding lines) · ×1
  • Edited copy of a member (61 corresponding lines) lib/features/mobile/presentation/widgets/mobile_api_key_step.dart:301 — lib/features/mobile/presentation/widgets/mobile_api_key_step.dart:301-361 | lib/features/onboarding/presentation/widgets/api_key_step.dart:368-431 — These two members are one piece of code written twice and then edited apart: 61 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copies of one member (3 members, 43+ corresponding lines) · ×1
  • Edited copies of one member (3 members, 43+ corresponding lines) lib/features/mobile/presentation/pages/mobile_onboarding_page.dart:341 — lib/features/mobile/presentation/pages/mobile_onboarding_page.dart:341-388 | lib/features/onboarding/presentation/widgets/completed_step.dart:109-162 | lib/features/onboarding/presentation/widgets/welcome_step.dart:89-131 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 43 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication · Edited copy of a member (40 corresponding lines) · ×1
  • Edited copy of a member (40 corresponding lines) lib/features/onboarding/presentation/bloc/onboarding_bloc.dart:1198 — lib/features/onboarding/presentation/bloc/onboarding_bloc.dart:1198-1237 | lib/features/settings/presentation/bloc/settings_bloc.dart:1007-1055 — These two members are one piece of code written twice and then edited apart: 40 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copy of a member (48 corresponding lines) · ×1
  • Edited copy of a member (48 corresponding lines) lib/features/onboarding/presentation/bloc/onboarding_bloc.dart:857 — lib/features/onboarding/presentation/bloc/onboarding_bloc.dart:857-912 | lib/features/onboarding/presentation/bloc/onboarding_bloc.dart:914-961 — These two members are one piece of code written twice and then edited apart: 48 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copy of a member (32 corresponding lines) · ×1
  • Edited copy of a member (32 corresponding lines) lib/features/onboarding/presentation/bloc/onboarding_bloc.dart:1321 — lib/features/onboarding/presentation/bloc/onboarding_bloc.dart:1321-1352 | lib/features/settings/presentation/bloc/settings_bloc.dart:1156-1193 — These two members are one piece of code written twice and then edited apart: 32 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copies of one member (6 members, 29+ corresponding lines) · ×1
  • Edited copies of one member (6 members, 29+ corresponding lines) lib/features/settings/presentation/bloc/settings_bloc.dart:743 — lib/features/settings/presentation/bloc/settings_bloc.dart:743-782 | lib/features/settings/presentation/bloc/settings_bloc.dart:785-815 | lib/features/settings/presentation/bloc/settings_bloc.dart:818-846 | lib/features/settings/presentation/bloc/settings_bloc.dart:938-971 | lib/features/settings/presentation/bloc/settings_bloc.dart:1349-1379 | lib/features/settings/presentation/bloc/settings_bloc.dart:1382-1412 — These 6 members are one piece of code written 6 times and then edited apart: every two of them correspond over at least 29 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 6 times and the copies will drift further apart.
D4 · Code Duplication · Edited copy of a member (31 corresponding lines) · ×1
  • Edited copy of a member (31 corresponding lines) lib/features/settings/presentation/bloc/settings_bloc.dart:874 — lib/features/settings/presentation/bloc/settings_bloc.dart:874-904 | lib/features/settings/presentation/bloc/settings_bloc.dart:974-1004 — These two members are one piece of code written twice and then edited apart: 31 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copy of a member (23 corresponding lines) · ×1
  • Edited copy of a member (23 corresponding lines) lib/features/settings/presentation/bloc/settings_bloc.dart:500 — lib/features/settings/presentation/bloc/settings_bloc.dart:500-522 | lib/features/settings/presentation/bloc/settings_bloc.dart:562-586 — These two members are one piece of code written twice and then edited apart: 23 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copies of one member (3 members, 12+ corresponding lines) · ×1
  • Edited copies of one member (3 members, 12+ corresponding lines) macos/Runner/AppDelegate.swift:96 — macos/Runner/AppDelegate.swift:96-107 | macos/Runner/AppDelegate.swift:109-123 | macos/Runner/AppDelegate.swift:125-136 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 12 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication · Edited copy of a member (14 corresponding lines) · ×1
  • Edited copy of a member (14 corresponding lines) macos/Runner/RecordingOverlayWindow.swift:148 — macos/Runner/RecordingOverlayWindow.swift:148-161 | macos/Runner/RecordingOverlayWindow.swift:163-176 — These two members are one piece of code written twice and then edited apart: 14 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copy of a member (15 corresponding lines) · ×1
  • Edited copy of a member (15 corresponding lines) lib/features/settings/presentation/bloc/settings_bloc.dart:484 — lib/features/settings/presentation/bloc/settings_bloc.dart:484-498 | lib/features/settings/presentation/bloc/settings_bloc.dart:545-560 — These two members are one piece of code written twice and then edited apart: 15 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copies of one member (4 members, 17+ corresponding lines) · ×1
  • Edited copies of one member (4 members, 17+ corresponding lines) lib/features/settings/presentation/bloc/settings_bloc.dart:524 — lib/features/settings/presentation/bloc/settings_bloc.dart:524-542 | lib/features/settings/presentation/bloc/settings_bloc.dart:588-606 | lib/features/settings/presentation/bloc/settings_bloc.dart:629-645 | lib/features/settings/presentation/bloc/settings_bloc.dart:648-667 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 17 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 4 times and the copies will drift further apart.
D4 · Code Duplication · Edited copy of a member (10 corresponding lines) · ×1
  • Edited copy of a member (10 corresponding lines) lib/features/settings/presentation/bloc/settings_bloc.dart:461 — lib/features/settings/presentation/bloc/settings_bloc.dart:461-470 | lib/features/settings/presentation/bloc/settings_bloc.dart:472-481 — These two members are one piece of code written twice and then edited apart: 10 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copy of a member (12 corresponding lines) · ×1
  • Edited copy of a member (12 corresponding lines) lib/features/settings/presentation/bloc/settings_bloc.dart:236 — lib/features/settings/presentation/bloc/settings_bloc.dart:236-247 | lib/features/settings/presentation/bloc/settings_bloc.dart:249-260 — These two members are one piece of code written twice and then edited apart: 12 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copy of a member (11 corresponding lines) · ×1
  • Edited copy of a member (11 corresponding lines) macos/Runner/PermissionService.swift:206 — macos/Runner/PermissionService.swift:206-216 | macos/Runner/PermissionService.swift:258-268 — These two members are one piece of code written twice and then edited apart: 11 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copies of one member (3 members, 16+ corresponding lines) · ×1
  • Edited copies of one member (3 members, 16+ corresponding lines) lib/features/mobile/presentation/pages/mobile_home_page.dart:31 — lib/features/mobile/presentation/pages/mobile_home_page.dart:31-49 | lib/features/settings/presentation/pages/settings.dart:51-68 | lib/widgets/enhanced_button.dart:52-67 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 16 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication · Edited copy of a member (9 corresponding lines) · ×1
  • Edited copy of a member (9 corresponding lines) lib/features/mobile/presentation/bloc/mobile_onboarding_bloc.dart:148 — lib/features/mobile/presentation/bloc/mobile_onboarding_bloc.dart:148-156 | lib/features/onboarding/presentation/bloc/onboarding_bloc.dart:167-176 — These two members are one piece of code written twice and then edited apart: 9 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Duplicated block (96–100 lines × 2) · ×1
  • Duplicated block (96–100 lines × 2) lib/features/mobile/presentation/widgets/mobile_local_models_section.dart:229 — lib/features/mobile/presentation/widgets/mobile_local_models_section.dart:229-328 | lib/features/mobile/presentation/widgets/mobile_local_models_step.dart:300-395 — before extracting anything, compare `lib/features/mobile/presentation/widgets/mobile_local_models_section.dart` and `lib/features/mobile/presentation/widgets/mobile_local_models_step.dart` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 161 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `lib/features/mobile/presentation/widgets/mobile_local_models_section.dart:229` 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.
D4 · Code Duplication · Duplicated block (83 lines × 2) · ×1
  • Duplicated block (83 lines × 2) lib/features/settings/presentation/widgets/assistant_models_section.dart:122 — lib/features/settings/presentation/widgets/assistant_models_section.dart:122-204 | lib/features/settings/presentation/widgets/transcription_models_section.dart:124-206 — before extracting anything, compare `lib/features/settings/presentation/widgets/assistant_models_section.dart` and `lib/features/settings/presentation/widgets/transcription_models_section.dart` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 218 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `lib/features/settings/presentation/widgets/assistant_models_section.dart:122` 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.
D4 · Code Duplication · Duplicated block (79 lines × 2) · ×1
  • Duplicated block (79 lines × 2) lib/features/onboarding/presentation/widgets/local_step.dart:291 — lib/features/onboarding/presentation/widgets/local_step.dart:291-369 | lib/features/settings/presentation/pages/transcription_settings_page.dart:263-341 — before extracting anything, compare `lib/features/onboarding/presentation/widgets/local_step.dart` and `lib/features/settings/presentation/pages/transcription_settings_page.dart` as WHOLE FILES: this scan already matched 16 separate duplicated blocks between them, totalling at least 359 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 `lib/features/onboarding/presentation/widgets/local_step.dart:291` 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.
D4 · Code Duplication · Duplicated block (51–54 lines × 2) · ×1
  • Duplicated block (51–54 lines × 2) lib/features/mobile/presentation/widgets/mobile_local_models_step.dart:71 — lib/features/mobile/presentation/widgets/mobile_local_models_step.dart:71-124 | lib/features/onboarding/presentation/widgets/local_step.dart:65-115 — before extracting anything, compare `lib/features/mobile/presentation/widgets/mobile_local_models_step.dart` and `lib/features/onboarding/presentation/widgets/local_step.dart` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 133 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 `lib/features/mobile/presentation/widgets/mobile_local_models_step.dart:71` 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.
D4 · Code Duplication · Duplicated block (52 lines × 2) · ×1
  • Duplicated block (52 lines × 2) lib/features/onboarding/presentation/widgets/local_step.dart:140 — lib/features/onboarding/presentation/widgets/local_step.dart:140-191 | lib/features/onboarding/presentation/widgets/permissions_step.dart:169-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.
D4 · Code Duplication · Duplicated block (48 lines × 2) · ×1
  • Duplicated block (48 lines × 2) lib/features/mobile/presentation/widgets/mobile_local_models_step.dart:156 — lib/features/mobile/presentation/widgets/mobile_local_models_step.dart:156-203 | lib/features/mobile/presentation/widgets/mobile_permissions_step.dart:128-175 — before extracting anything, compare `lib/features/mobile/presentation/widgets/mobile_local_models_step.dart` and `lib/features/mobile/presentation/widgets/mobile_permissions_step.dart` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 119 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `lib/features/mobile/presentation/widgets/mobile_local_models_step.dart:156` 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.
D4 · Code Duplication · Duplicated block (41 lines × 2) · ×1
  • Duplicated block (41 lines × 2) lib/features/settings/presentation/widgets/assistant_hotkey_settings_section.dart:38 — lib/features/settings/presentation/widgets/assistant_hotkey_settings_section.dart:38-78 | lib/features/settings/presentation/widgets/transcription_hotkey_settings_section.dart:41-81 — before extracting anything, compare `lib/features/settings/presentation/widgets/assistant_hotkey_settings_section.dart` and `lib/features/settings/presentation/widgets/transcription_hotkey_settings_section.dart` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 106 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
D4 · Code Duplication · Duplicated block (36–39 lines × 4) · ×1
  • Duplicated block (36–39 lines × 4) lib/features/mobile/presentation/widgets/mobile_api_key_step.dart:35 — lib/features/mobile/presentation/widgets/mobile_api_key_step.dart:35-73 | lib/features/mobile/presentation/widgets/mobile_keyboard_extension_step.dart:9-44 | lib/features/mobile/presentation/widgets/mobile_permissions_step.dart:21-59 | lib/features/mobile/presentation/widgets/mobile_theme_step.dart:17-55 — before extracting anything, compare `lib/features/mobile/presentation/widgets/mobile_api_key_step.dart` and `lib/features/mobile/presentation/widgets/mobile_keyboard_extension_step.dart` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 123 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `lib/features/mobile/presentation/widgets/mobile_api_key_step.dart:35` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. 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 · Duplicated block (39 lines × 2) · ×1
  • Duplicated block (39 lines × 2) lib/features/mobile/presentation/pages/mobile_onboarding_page.dart:88 — lib/features/mobile/presentation/pages/mobile_onboarding_page.dart:88-126 | lib/features/onboarding/presentation/pages/onboarding_page.dart:112-150 — 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 `lib/features/mobile/presentation/pages/mobile_onboarding_page.dart: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.
D4 · Code Duplication · Duplicated block (36–38 lines × 2) · ×1
  • Duplicated block (36–38 lines × 2) lib/features/settings/presentation/widgets/assistant_models_section.dart:35 — lib/features/settings/presentation/widgets/assistant_models_section.dart:35-70 | lib/features/settings/presentation/widgets/transcription_models_section.dart:35-72 — before extracting anything, compare `lib/features/settings/presentation/widgets/assistant_models_section.dart` and `lib/features/settings/presentation/widgets/transcription_models_section.dart` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 218 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `lib/features/settings/presentation/widgets/assistant_models_section.dart:35` 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 · Duplicated block (33–34 lines × 2) · ×1
  • Duplicated block (33–34 lines × 2) lib/features/onboarding/presentation/widgets/local_step.dart:603 — lib/features/onboarding/presentation/widgets/local_step.dart:603-635 | lib/features/settings/presentation/pages/transcription_settings_page.dart:640-673 — before extracting anything, compare `lib/features/onboarding/presentation/widgets/local_step.dart` and `lib/features/settings/presentation/pages/transcription_settings_page.dart` as WHOLE FILES: this scan already matched 16 separate duplicated blocks between them, totalling at least 359 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 `lib/features/onboarding/presentation/widgets/local_step.dart:603` 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.
D4 · Code Duplication · Duplicated block (29–30 lines × 2) · ×1
  • Duplicated block (29–30 lines × 2) lib/features/mobile/presentation/pages/mobile_onboarding_page.dart:58 — lib/features/mobile/presentation/pages/mobile_onboarding_page.dart:58-86 | lib/features/onboarding/presentation/pages/onboarding_page.dart:81-110 — 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 `lib/features/mobile/presentation/pages/mobile_onboarding_page.dart:58` 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.
D4 · Code Duplication · Duplicated block (25–29 lines × 4) · ×1
  • Duplicated block (25–29 lines × 4) lib/features/onboarding/presentation/widgets/api_key_step.dart:44 — lib/features/onboarding/presentation/widgets/api_key_step.dart:44-72 | lib/features/onboarding/presentation/widgets/hotkeys_step.dart:16-44 | lib/features/onboarding/presentation/widgets/preferences_step.dart:12-36 | lib/features/onboarding/presentation/widgets/test_hotkeys_step.dart:73-101 — before extracting anything, compare `lib/features/onboarding/presentation/widgets/api_key_step.dart` and `lib/features/onboarding/presentation/widgets/hotkeys_step.dart` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 100 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `lib/features/onboarding/presentation/widgets/api_key_step.dart:44` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. 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 · Duplicated block (23–28 lines × 4) · ×1
  • Duplicated block (23–28 lines × 4) lib/features/settings/presentation/pages/general_settings_page.dart:156 — lib/features/settings/presentation/pages/general_settings_page.dart:156-183 | lib/features/settings/presentation/pages/general_settings_page.dart:213-235 | lib/features/settings/presentation/pages/general_settings_page.dart:344-366 | lib/features/settings/presentation/pages/general_settings_page.dart:400-422 — all 4 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `lib/features/settings/presentation/pages/general_settings_page.dart:156` 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.
D4 · Code Duplication · Duplicated block (23–26 lines × 2) · ×1
  • Duplicated block (23–26 lines × 2) lib/features/onboarding/presentation/widgets/preferences_step.dart:96 — lib/features/onboarding/presentation/widgets/preferences_step.dart:96-118 | lib/features/onboarding/presentation/widgets/test_hotkeys_step.dart:162-187 — before extracting anything, compare `lib/features/onboarding/presentation/widgets/preferences_step.dart` and `lib/features/onboarding/presentation/widgets/test_hotkeys_step.dart` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 109 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `lib/features/onboarding/presentation/widgets/preferences_step.dart:96` 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.
D4 · Code Duplication · Duplicated block (25 lines × 6) · ×1
  • Duplicated block (25 lines × 6) lib/features/onboarding/presentation/widgets/local_step.dart:359 — lib/features/onboarding/presentation/widgets/local_step.dart:359-383 | lib/features/onboarding/presentation/widgets/local_step.dart:391-415 | lib/features/onboarding/presentation/widgets/local_step.dart:423-447 | lib/features/settings/presentation/pages/transcription_settings_page.dart:331-355 | lib/features/settings/presentation/pages/transcription_settings_page.dart:363-387 | lib/features/settings/presentation/pages/transcription_settings_page.dart:395-419 — before extracting anything, compare `lib/features/onboarding/presentation/widgets/local_step.dart` and `lib/features/settings/presentation/pages/transcription_settings_page.dart` as WHOLE FILES: this scan already matched 16 separate duplicated blocks between them, totalling at least 359 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 `lib/features/onboarding/presentation/widgets/local_step.dart:359` 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.
D4 · Code Duplication · Duplicated block (22–25 lines × 5) · ×1
  • Duplicated block (22–25 lines × 5) lib/features/settings/presentation/pages/assistant_settings_page.dart:116 — lib/features/settings/presentation/pages/assistant_settings_page.dart:116-137 | lib/features/settings/presentation/pages/general_settings_page.dart:179-200 | lib/features/settings/presentation/pages/general_settings_page.dart:362-383 | lib/features/settings/presentation/pages/general_settings_page.dart:418-439 | lib/features/settings/presentation/pages/transcription_settings_page.dart:129-153 — before extracting anything, compare `lib/features/settings/presentation/pages/assistant_settings_page.dart` and `lib/features/settings/presentation/pages/general_settings_page.dart` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 103 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `lib/features/settings/presentation/pages/assistant_settings_page.dart:116` 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.
D4 · Code Duplication · Duplicated block (23–25 lines × 3) · ×1
  • Duplicated block (23–25 lines × 3) lib/features/onboarding/presentation/widgets/api_key_step.dart:296 — lib/features/onboarding/presentation/widgets/api_key_step.dart:296-320 | lib/features/onboarding/presentation/widgets/hotkeys_step.dart:316-338 | lib/features/onboarding/presentation/widgets/test_hotkeys_step.dart:178-202 — before extracting anything, compare `lib/features/onboarding/presentation/widgets/api_key_step.dart` and `lib/features/onboarding/presentation/widgets/hotkeys_step.dart` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 100 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `lib/features/onboarding/presentation/widgets/api_key_step.dart:296` 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.
D4 · Code Duplication · Duplicated block (22–24 lines × 2) · ×1
  • Duplicated block (22–24 lines × 2) lib/features/mobile/presentation/widgets/mobile_api_key_section.dart:47 — lib/features/mobile/presentation/widgets/mobile_api_key_section.dart:47-68 | lib/features/mobile/presentation/widgets/mobile_local_models_section.dart:33-56 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `lib/features/mobile/presentation/widgets/mobile_api_key_section.dart:47` 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.
D4 · Code Duplication · Duplicated block (21–23 lines × 2) · ×1
  • Duplicated block (21–23 lines × 2) lib/features/mobile/presentation/widgets/mobile_api_key_section.dart:142 — lib/features/mobile/presentation/widgets/mobile_api_key_section.dart:142-164 | lib/features/settings/presentation/widgets/api_key_section.dart:86-106 — 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 `lib/features/mobile/presentation/widgets/mobile_api_key_section.dart:142` 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.
D4 · Code Duplication · Duplicated block (23 lines × 2) · ×1
  • Duplicated block (23 lines × 2) lib/features/onboarding/presentation/widgets/hotkeys_step.dart:179 — lib/features/onboarding/presentation/widgets/hotkeys_step.dart:179-201 | lib/features/onboarding/presentation/widgets/hotkeys_step.dart:269-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. Read the line range as the matched WINDOW rather than a finished unit: at `lib/features/onboarding/presentation/widgets/hotkeys_step.dart:179` 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.
D4 · Code Duplication · Duplicated block (20–22 lines × 5) · ×1
  • Duplicated block (20–22 lines × 5) lib/features/mobile/presentation/widgets/mobile_api_key_step.dart:37 — lib/features/mobile/presentation/widgets/mobile_api_key_step.dart:37-58 | lib/features/mobile/presentation/widgets/mobile_keyboard_extension_step.dart:11-30 | lib/features/mobile/presentation/widgets/mobile_local_models_step.dart:17-38 | lib/features/mobile/presentation/widgets/mobile_permissions_step.dart:23-44 | lib/features/mobile/presentation/widgets/mobile_theme_step.dart:19-40 — before extracting anything, compare `lib/features/mobile/presentation/widgets/mobile_api_key_step.dart` and `lib/features/mobile/presentation/widgets/mobile_keyboard_extension_step.dart` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 123 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `lib/features/mobile/presentation/widgets/mobile_api_key_step.dart:37` 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.
D4 · Code Duplication · Duplicated block (22 lines × 2) · ×1
  • Duplicated block (22 lines × 2) lib/features/mobile/presentation/widgets/mobile_theme_settings_section.dart:43 — lib/features/mobile/presentation/widgets/mobile_theme_settings_section.dart:43-64 | lib/features/mobile/presentation/widgets/mobile_transcription_models_section.dart:43-64 — before extracting anything, compare `lib/features/mobile/presentation/widgets/mobile_theme_settings_section.dart` and `lib/features/mobile/presentation/widgets/mobile_transcription_models_section.dart` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 65 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `lib/features/mobile/presentation/widgets/mobile_theme_settings_section.dart:43` 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.
D4 · Code Duplication · Duplicated block (21 lines × 11) · ×1
  • Duplicated block (21 lines × 11) lib/features/settings/presentation/pages/assistant_settings_page.dart:79 — lib/features/settings/presentation/pages/assistant_settings_page.dart:79-99 | lib/features/settings/presentation/pages/general_settings_page.dart:135-155 | lib/features/settings/presentation/pages/general_settings_page.dart:321-341 | lib/features/settings/presentation/pages/general_settings_page.dart:487-507 | lib/features/settings/presentation/pages/general_settings_page.dart:652-672 | lib/features/settings/presentation/pages/general_settings_page.dart:769-789 | lib/features/settings/presentation/pages/output_settings_page.dart:77-97 | lib/features/settings/presentation/pages/output_settings_page.dart:285-305 | lib/features/settings/presentation/pages/output_settings_page.dart:456-476 | lib/features/settings/presentation/pages/transcription_settings_page.dart:81-101 | lib/features/settings/presentation/widgets/smart_transcription_section.dart:35-55 — before extracting anything, compare `lib/features/settings/presentation/pages/assistant_settings_page.dart` and `lib/features/settings/presentation/pages/general_settings_page.dart` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 103 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `lib/features/settings/presentation/pages/assistant_settings_page.dart:79` 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.
D4 · Code Duplication · Duplicated block (21 lines × 2) · ×1
  • Duplicated block (21 lines × 2) lib/features/settings/presentation/widgets/assistant_hotkey_settings_section.dart:80 — lib/features/settings/presentation/widgets/assistant_hotkey_settings_section.dart:80-100 | lib/features/settings/presentation/widgets/transcription_hotkey_settings_section.dart:83-103 — before extracting anything, compare `lib/features/settings/presentation/widgets/assistant_hotkey_settings_section.dart` and `lib/features/settings/presentation/widgets/transcription_hotkey_settings_section.dart` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 106 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
D4 · Code Duplication · Duplicated block (20 lines × 2) · ×1
  • Duplicated block (20 lines × 2) lib/features/info/presentation/pages/info_page.dart:144 — lib/features/info/presentation/pages/info_page.dart:144-163 | lib/features/info/presentation/pages/info_page.dart:181-200 — 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 `lib/features/info/presentation/pages/info_page.dart:144` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
D4 · Code Duplication · Duplicated block (16–19 lines × 13) · ×1
  • Duplicated block (16–19 lines × 13) lib/features/home/presentation/pages/home_page.dart:225 — lib/features/home/presentation/pages/home_page.dart:225-243 | lib/features/settings/presentation/pages/assistant_settings_page.dart:74-89 | lib/features/settings/presentation/pages/general_settings_page.dart:130-145 | lib/features/settings/presentation/pages/general_settings_page.dart:316-331 | lib/features/settings/presentation/pages/general_settings_page.dart:482-497 | lib/features/settings/presentation/pages/general_settings_page.dart:647-662 | lib/features/settings/presentation/pages/general_settings_page.dart:764-779 | lib/features/settings/presentation/pages/output_settings_page.dart:72-87 | lib/features/settings/presentation/pages/output_settings_page.dart:280-295 | lib/features/settings/presentation/pages/output_settings_page.dart:451-466 | lib/features/settings/presentation/pages/transcription_settings_page.dart:76-91 | lib/features/settings/presentation/widgets/smart_transcription_section.dart:30-45 | lib/features/settings/presentation/widgets/theme_settings_section.dart:30-45 — before extracting anything, compare `lib/features/settings/presentation/pages/assistant_settings_page.dart` and `lib/features/settings/presentation/pages/general_settings_page.dart` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 103 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `lib/features/home/presentation/pages/home_page.dart:225` 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.
D4 · Code Duplication · Duplicated block (16–19 lines × 5) · ×1
  • Duplicated block (16–19 lines × 5) lib/features/settings/presentation/pages/general_settings_page.dart:170 — lib/features/settings/presentation/pages/general_settings_page.dart:170-185 | lib/features/settings/presentation/pages/general_settings_page.dart:222-237 | lib/features/settings/presentation/pages/general_settings_page.dart:353-368 | lib/features/settings/presentation/pages/general_settings_page.dart:409-424 | lib/features/settings/presentation/pages/transcription_settings_page.dart:118-136 — before extracting anything, compare `lib/features/settings/presentation/pages/general_settings_page.dart` and `lib/features/settings/presentation/pages/transcription_settings_page.dart` as WHOLE FILES: this scan already matched 9 separate duplicated blocks between them, totalling at least 150 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `lib/features/settings/presentation/pages/general_settings_page.dart:170` 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.
D4 · Code Duplication · Duplicated block (16–19 lines × 4) · ×1
  • Duplicated block (16–19 lines × 4) lib/features/onboarding/presentation/widgets/api_key_step.dart:292 — lib/features/onboarding/presentation/widgets/api_key_step.dart:292-310 | lib/features/onboarding/presentation/widgets/hotkeys_step.dart:312-328 | lib/features/onboarding/presentation/widgets/preferences_step.dart:108-123 | lib/features/onboarding/presentation/widgets/test_hotkeys_step.dart:174-192 — before extracting anything, compare `lib/features/onboarding/presentation/widgets/api_key_step.dart` and `lib/features/onboarding/presentation/widgets/hotkeys_step.dart` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 100 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `lib/features/onboarding/presentation/widgets/api_key_step.dart:292` 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.
D4 · Code Duplication · Duplicated block (17–19 lines × 3) · ×1
  • Duplicated block (17–19 lines × 3) lib/features/mobile/presentation/widgets/mobile_local_models_step.dart:72 — lib/features/mobile/presentation/widgets/mobile_local_models_step.dart:72-90 | lib/features/onboarding/presentation/widgets/local_step.dart:66-83 | lib/features/settings/presentation/pages/transcription_settings_page.dart:64-80 — before extracting anything, compare `lib/features/mobile/presentation/widgets/mobile_local_models_step.dart` and `lib/features/onboarding/presentation/widgets/local_step.dart` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 133 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 `lib/features/mobile/presentation/widgets/mobile_local_models_step.dart:72` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (18–19 lines × 3) · ×1
  • Duplicated block (18–19 lines × 3) lib/features/settings/presentation/pages/general_settings_page.dart:601 — lib/features/settings/presentation/pages/general_settings_page.dart:601-618 | lib/features/settings/presentation/pages/general_settings_page.dart:721-739 | lib/features/settings/presentation/pages/general_settings_page.dart:815-833 — 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 `lib/features/settings/presentation/pages/general_settings_page.dart:601` 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.
D4 · Code Duplication · Duplicated block (19 lines × 2) · ×1
  • Duplicated block (19 lines × 2) lib/features/onboarding/presentation/widgets/hotkeys_step.dart:397 — lib/features/onboarding/presentation/widgets/hotkeys_step.dart:397-415 | lib/features/onboarding/presentation/widgets/test_hotkeys_step.dart:291-309 — before extracting anything, compare `lib/features/onboarding/presentation/widgets/hotkeys_step.dart` and `lib/features/onboarding/presentation/widgets/test_hotkeys_step.dart` as WHOLE FILES: this scan already matched 10 separate duplicated blocks between them, totalling at least 187 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `lib/features/onboarding/presentation/widgets/hotkeys_step.dart:397` 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.
D4 · Code Duplication · Duplicated block (18 lines × 4) · ×1
  • Duplicated block (18 lines × 4) lib/features/onboarding/presentation/widgets/api_key_step.dart:273 — lib/features/onboarding/presentation/widgets/api_key_step.dart:273-290 | lib/features/onboarding/presentation/widgets/hotkeys_step.dart:293-310 | lib/features/onboarding/presentation/widgets/preferences_step.dart:89-106 | lib/features/onboarding/presentation/widgets/test_hotkeys_step.dart:155-172 — before extracting anything, compare `lib/features/onboarding/presentation/widgets/api_key_step.dart` and `lib/features/onboarding/presentation/widgets/hotkeys_step.dart` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 100 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `lib/features/onboarding/presentation/widgets/api_key_step.dart:273` 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.
D4 · Code Duplication · Duplicated block (18 lines × 3) · ×1
  • Duplicated block (18 lines × 3) lib/features/mobile/presentation/widgets/mobile_api_key_step.dart:209 — lib/features/mobile/presentation/widgets/mobile_api_key_step.dart:209-226 | lib/features/mobile/presentation/widgets/mobile_local_models_step.dart:151-168 | lib/features/mobile/presentation/widgets/mobile_permissions_step.dart:123-140 — before extracting anything, compare `lib/features/mobile/presentation/widgets/mobile_api_key_step.dart` and `lib/features/mobile/presentation/widgets/mobile_local_models_step.dart` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 119 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `lib/features/mobile/presentation/widgets/mobile_api_key_step.dart:209` 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.
D4 · Code Duplication · Duplicated block (15–18 lines × 3) · ×1
  • Duplicated block (15–18 lines × 3) lib/features/onboarding/presentation/widgets/completed_step.dart:128 — lib/features/onboarding/presentation/widgets/completed_step.dart:128-142 | lib/features/onboarding/presentation/widgets/hotkeys_step.dart:374-391 | lib/features/onboarding/presentation/widgets/test_hotkeys_step.dart:242-259 — before extracting anything, compare `lib/features/onboarding/presentation/widgets/completed_step.dart` and `lib/features/onboarding/presentation/widgets/hotkeys_step.dart` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 64 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `lib/features/onboarding/presentation/widgets/completed_step.dart:128` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `lib/features/onboarding/presentation/widgets/test_hotkeys_step.dart:260` calls `Row` and `lib/features/onboarding/presentation/widgets/completed_step.dart:143` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
D4 · Code Duplication · Duplicated block (17–18 lines × 2) · ×1
  • Duplicated block (17–18 lines × 2) lib/features/onboarding/presentation/bloc/onboarding_bloc.dart:1201 — lib/features/onboarding/presentation/bloc/onboarding_bloc.dart:1201-1218 | lib/features/settings/presentation/bloc/settings_bloc.dart:1009-1025 — before extracting anything, compare `lib/features/onboarding/presentation/bloc/onboarding_bloc.dart` and `lib/features/settings/presentation/bloc/settings_bloc.dart` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 68 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 `lib/features/onboarding/presentation/bloc/onboarding_bloc.dart:1201` 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.
D4 · Code Duplication · Duplicated block (14–17 lines × 5) · ×1
  • Duplicated block (14–17 lines × 5) lib/features/mobile/presentation/pages/mobile_home_page.dart:141 — lib/features/mobile/presentation/pages/mobile_home_page.dart:141-157 | lib/features/mobile/presentation/widgets/mobile_api_key_section.dart:44-57 | lib/features/mobile/presentation/widgets/mobile_local_models_section.dart:30-43 | lib/features/mobile/presentation/widgets/mobile_theme_settings_section.dart:40-53 | lib/features/mobile/presentation/widgets/mobile_transcription_models_section.dart:40-53 — before extracting anything, compare `lib/features/mobile/presentation/widgets/mobile_api_key_section.dart` and `lib/features/mobile/presentation/widgets/mobile_theme_settings_section.dart` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 43 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `lib/features/mobile/presentation/pages/mobile_home_page.dart:141` 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.
D4 · Code Duplication · Duplicated block (11–16 lines × 8) · ×1
  • Duplicated block (11–16 lines × 8) lib/features/settings/presentation/pages/general_settings_page.dart:153 — lib/features/settings/presentation/pages/general_settings_page.dart:153-168 | lib/features/settings/presentation/pages/general_settings_page.dart:210-220 | lib/features/settings/presentation/pages/general_settings_page.dart:339-351 | lib/features/settings/presentation/pages/general_settings_page.dart:395-407 | lib/features/settings/presentation/pages/general_settings_page.dart:505-515 | lib/features/settings/presentation/pages/general_settings_page.dart:670-685 | lib/features/settings/presentation/pages/general_settings_page.dart:787-802 | lib/features/settings/presentation/pages/transcription_settings_page.dart:99-114 — before extracting anything, compare `lib/features/settings/presentation/pages/general_settings_page.dart` and `lib/features/settings/presentation/pages/transcription_settings_page.dart` as WHOLE FILES: this scan already matched 9 separate duplicated blocks between them, totalling at least 150 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `lib/features/settings/presentation/pages/general_settings_page.dart:153` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `lib/features/settings/presentation/pages/general_settings_page.dart:169` calls `Row`, `Expanded` and `lib/features/settings/presentation/pages/general_settings_page.dart:516` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
D4 · Code Duplication · Duplicated block (16 lines × 4) · ×1
  • Duplicated block (16 lines × 4) lib/features/mobile/presentation/widgets/mobile_api_key_step.dart:205 — lib/features/mobile/presentation/widgets/mobile_api_key_step.dart:205-220 | lib/features/mobile/presentation/widgets/mobile_keyboard_extension_step.dart:196-211 | lib/features/mobile/presentation/widgets/mobile_local_models_step.dart:147-162 | lib/features/mobile/presentation/widgets/mobile_permissions_step.dart:119-134 — before extracting anything, compare `lib/features/mobile/presentation/widgets/mobile_api_key_step.dart` and `lib/features/mobile/presentation/widgets/mobile_keyboard_extension_step.dart` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 123 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `lib/features/mobile/presentation/widgets/mobile_api_key_step.dart:205` 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.
D4 · Code Duplication · Duplicated block (15–16 lines × 3) · ×1
  • Duplicated block (15–16 lines × 3) lib/features/mobile/presentation/widgets/mobile_api_key_step.dart:67 — lib/features/mobile/presentation/widgets/mobile_api_key_step.dart:67-82 | lib/features/mobile/presentation/widgets/mobile_keyboard_extension_step.dart:38-52 | lib/features/mobile/presentation/widgets/mobile_local_models_step.dart:47-62 — before extracting anything, compare `lib/features/mobile/presentation/widgets/mobile_api_key_step.dart` and `lib/features/mobile/presentation/widgets/mobile_keyboard_extension_step.dart` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 123 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `lib/features/mobile/presentation/widgets/mobile_api_key_step.dart:67` 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.
D4 · Code Duplication · Duplicated block (16 lines × 3) · ×1
  • Duplicated block (16 lines × 3) lib/features/settings/presentation/widgets/models_section.dart:55 — lib/features/settings/presentation/widgets/models_section.dart:55-70 | lib/features/settings/presentation/widgets/models_section.dart:72-87 | lib/features/settings/presentation/widgets/models_section.dart:89-104 — 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 `lib/features/settings/presentation/widgets/models_section.dart:55` 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.
D4 · Code Duplication · Duplicated block (14–16 lines × 2) · ×1
  • Duplicated block (14–16 lines × 2) lib/features/onboarding/presentation/bloc/onboarding_bloc.dart:1327 — lib/features/onboarding/presentation/bloc/onboarding_bloc.dart:1327-1340 | lib/features/settings/presentation/bloc/settings_bloc.dart:1164-1179 — before extracting anything, compare `lib/features/onboarding/presentation/bloc/onboarding_bloc.dart` and `lib/features/settings/presentation/bloc/settings_bloc.dart` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 68 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 `lib/features/settings/presentation/bloc/settings_bloc.dart:1164` 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.
D4 · Code Duplication · Duplicated block (12–15 lines × 6) · ×1
  • Duplicated block (12–15 lines × 6) lib/features/mobile/presentation/widgets/mobile_api_key_section.dart:20 — lib/features/mobile/presentation/widgets/mobile_api_key_section.dart:20-31 | lib/features/mobile/presentation/widgets/mobile_api_key_step.dart:79-93 | lib/features/mobile/presentation/widgets/mobile_keyboard_extension_step.dart:99-112 | lib/features/mobile/presentation/widgets/mobile_local_models_step.dart:59-73 | lib/features/mobile/presentation/widgets/mobile_theme_settings_section.dart:16-27 | lib/features/mobile/presentation/widgets/mobile_transcription_models_section.dart:16-27 — before extracting anything, compare `lib/features/mobile/presentation/widgets/mobile_api_key_section.dart` and `lib/features/mobile/presentation/widgets/mobile_theme_settings_section.dart` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 43 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `lib/features/mobile/presentation/widgets/mobile_api_key_section.dart: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.
D4 · Code Duplication · Duplicated block (14–15 lines × 5) · ×1
  • Duplicated block (14–15 lines × 5) lib/features/mobile/presentation/widgets/mobile_api_key_step.dart:62 — lib/features/mobile/presentation/widgets/mobile_api_key_step.dart:62-76 | lib/features/mobile/presentation/widgets/mobile_keyboard_extension_step.dart:34-47 | lib/features/mobile/presentation/widgets/mobile_local_models_step.dart:42-56 | lib/features/mobile/presentation/widgets/mobile_permissions_step.dart:48-62 | lib/features/mobile/presentation/widgets/mobile_theme_step.dart:44-58 — before extracting anything, compare `lib/features/mobile/presentation/widgets/mobile_api_key_step.dart` and `lib/features/mobile/presentation/widgets/mobile_keyboard_extension_step.dart` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 123 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.
D4 · Code Duplication · Duplicated block (15 lines × 4) · ×1
  • Duplicated block (15 lines × 4) lib/features/mobile/presentation/widgets/mobile_local_models_section.dart:152 — lib/features/mobile/presentation/widgets/mobile_local_models_section.dart:152-166 | lib/features/mobile/presentation/widgets/mobile_local_models_step.dart:225-239 | lib/features/onboarding/presentation/widgets/local_step.dart:213-227 | lib/features/settings/presentation/pages/transcription_settings_page.dart:204-218 — before extracting anything, compare `lib/features/mobile/presentation/widgets/mobile_local_models_section.dart` and `lib/features/mobile/presentation/widgets/mobile_local_models_step.dart` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 161 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `lib/features/mobile/presentation/widgets/mobile_local_models_section.dart:152` 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 · Duplicated block (15 lines × 3) · ×1
  • Duplicated block (15 lines × 3) lib/features/onboarding/presentation/widgets/completed_step.dart:136 — lib/features/onboarding/presentation/widgets/completed_step.dart:136-150 | lib/features/onboarding/presentation/widgets/hotkeys_step.dart:385-399 | lib/features/onboarding/presentation/widgets/welcome_step.dart:106-120 — before extracting anything, compare `lib/features/onboarding/presentation/widgets/completed_step.dart` and `lib/features/onboarding/presentation/widgets/hotkeys_step.dart` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 64 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `lib/features/onboarding/presentation/widgets/completed_step.dart:136` 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.
D4 · Code Duplication · Duplicated block (14–15 lines × 2) · ×1
  • Duplicated block (14–15 lines × 2) lib/features/onboarding/presentation/widgets/local_step.dart:120 — lib/features/onboarding/presentation/widgets/local_step.dart:120-134 | lib/features/settings/presentation/pages/transcription_settings_page.dart:159-172 — before extracting anything, compare `lib/features/onboarding/presentation/widgets/local_step.dart` and `lib/features/settings/presentation/pages/transcription_settings_page.dart` as WHOLE FILES: this scan already matched 16 separate duplicated blocks between them, totalling at least 359 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 `lib/features/onboarding/presentation/widgets/local_step.dart:120` 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.
D4 · Code Duplication · Duplicated block (10–15 lines × 2) · ×1
  • Duplicated block (10–15 lines × 2) lib/features/onboarding/presentation/widgets/local_step.dart:243 — lib/features/onboarding/presentation/widgets/local_step.dart:243-252 | lib/features/settings/presentation/pages/transcription_settings_page.dart:225-239 — before extracting anything, compare `lib/features/onboarding/presentation/widgets/local_step.dart` and `lib/features/settings/presentation/pages/transcription_settings_page.dart` as WHOLE FILES: this scan already matched 16 separate duplicated blocks between them, totalling at least 359 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 `lib/features/onboarding/presentation/widgets/local_step.dart:243` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note first that the copies are not typed on the same thing: the declarations holding them bind `state` to `OnboardingState` in one and `SettingsState` in another, and the duplicated lines use it. The extracted unit therefore needs a parameter type that fits BOTH — their common supertype where they have one, or a new abstraction over them where they do not — and settling that is the step that comes BEFORE the extraction above. Where the two types are deliberately unrelated, the duplication is the price of that separation and the honest resolution is to record the decision rather than to extract. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `lib/features/onboarding/presentation/widgets/local_step.dart:254` calls `contains` and `lib/features/settings/presentation/pages/transcription_settings_page.dart:240` 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.
D4 · Code Duplication · Duplicated block (15 lines × 2) · ×1
  • Duplicated block (15 lines × 2) lib/features/settings/presentation/pages/output_settings_page.dart:339 — lib/features/settings/presentation/pages/output_settings_page.dart:339-353 | lib/features/settings/presentation/pages/output_settings_page.dart:530-544 — 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 `lib/features/settings/presentation/pages/output_settings_page.dart:339` 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.
D4 · Code Duplication · Duplicated block (10–14 lines × 4) · ×1
  • Duplicated block (10–14 lines × 4) lib/features/onboarding/presentation/widgets/completed_step.dart:125 — lib/features/onboarding/presentation/widgets/completed_step.dart:125-134 | lib/features/onboarding/presentation/widgets/hotkeys_step.dart:370-383 | lib/features/onboarding/presentation/widgets/test_hotkeys_step.dart:238-251 | lib/features/onboarding/presentation/widgets/welcome_step.dart:96-105 — before extracting anything, compare `lib/features/onboarding/presentation/widgets/completed_step.dart` and `lib/features/onboarding/presentation/widgets/hotkeys_step.dart` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 64 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `lib/features/onboarding/presentation/widgets/completed_step.dart:125` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (14 lines × 4) · ×1
  • Duplicated block (14 lines × 4) lib/features/settings/presentation/widgets/assistant_hotkey_settings_section.dart:16 — lib/features/settings/presentation/widgets/assistant_hotkey_settings_section.dart:16-29 | lib/features/settings/presentation/widgets/assistant_models_section.dart:12-25 | lib/features/settings/presentation/widgets/transcription_hotkey_settings_section.dart:16-29 | lib/features/settings/presentation/widgets/transcription_models_section.dart:12-25 — before extracting anything, compare `lib/features/settings/presentation/widgets/assistant_hotkey_settings_section.dart` and `lib/features/settings/presentation/widgets/transcription_hotkey_settings_section.dart` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 106 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `lib/features/settings/presentation/widgets/assistant_hotkey_settings_section.dart:16` 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.
D4 · Code Duplication · Duplicated block (13 lines × 5) · ×1
  • Duplicated block (13 lines × 5) lib/features/settings/presentation/widgets/api_key_section.dart:22 — lib/features/settings/presentation/widgets/api_key_section.dart:22-34 | lib/features/settings/presentation/widgets/assistant_hotkey_settings_section.dart:19-31 | lib/features/settings/presentation/widgets/assistant_models_section.dart:15-27 | lib/features/settings/presentation/widgets/transcription_hotkey_settings_section.dart:19-31 | lib/features/settings/presentation/widgets/transcription_models_section.dart:15-27 — before extracting anything, compare `lib/features/settings/presentation/widgets/assistant_hotkey_settings_section.dart` and `lib/features/settings/presentation/widgets/transcription_hotkey_settings_section.dart` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 106 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `lib/features/settings/presentation/widgets/api_key_section.dart:22` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. 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 · Duplicated block (13 lines × 4) · ×1
  • Duplicated block (13 lines × 4) lib/features/settings/presentation/pages/assistant_settings_page.dart:19 — lib/features/settings/presentation/pages/assistant_settings_page.dart:19-31 | lib/features/settings/presentation/pages/output_settings_page.dart:26-38 | lib/features/settings/presentation/pages/settings.dart:83-95 | lib/features/settings/presentation/pages/transcription_settings_page.dart:20-32 — before extracting anything, compare `lib/features/settings/presentation/pages/assistant_settings_page.dart` and `lib/features/settings/presentation/pages/output_settings_page.dart` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 95 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `lib/features/settings/presentation/pages/assistant_settings_page.dart:19` 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.
D4 · Code Duplication · Duplicated block (12 lines × 13) · ×1
  • Duplicated block (12 lines × 13) lib/features/info/presentation/pages/info_page.dart:141 — lib/features/info/presentation/pages/info_page.dart:141-152 | lib/features/info/presentation/pages/info_page.dart:178-189 | lib/features/settings/presentation/pages/assistant_settings_page.dart:87-98 | lib/features/settings/presentation/pages/general_settings_page.dart:143-154 | lib/features/settings/presentation/pages/general_settings_page.dart:329-340 | lib/features/settings/presentation/pages/general_settings_page.dart:495-506 | lib/features/settings/presentation/pages/general_settings_page.dart:660-671 | lib/features/settings/presentation/pages/general_settings_page.dart:777-788 | lib/features/settings/presentation/pages/output_settings_page.dart:85-96 | lib/features/settings/presentation/pages/output_settings_page.dart:293-304 | lib/features/settings/presentation/pages/output_settings_page.dart:464-475 | lib/features/settings/presentation/pages/transcription_settings_page.dart:89-100 | lib/features/settings/presentation/widgets/smart_transcription_section.dart:43-54 — before extracting anything, compare `lib/features/settings/presentation/pages/assistant_settings_page.dart` and `lib/features/settings/presentation/pages/general_settings_page.dart` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 103 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `lib/features/info/presentation/pages/info_page.dart: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.
D4 · Code Duplication · Duplicated block (11–12 lines × 5) · ×1
  • Duplicated block (11–12 lines × 5) lib/features/settings/presentation/pages/general_settings_page.dart:113 — lib/features/settings/presentation/pages/general_settings_page.dart:113-124 | lib/features/settings/presentation/pages/general_settings_page.dart:299-310 | lib/features/settings/presentation/pages/transcription_settings_page.dart:59-70 | lib/features/settings/presentation/widgets/smart_transcription_section.dart:14-24 | lib/features/settings/presentation/widgets/theme_settings_section.dart:13-24 — before extracting anything, compare `lib/features/settings/presentation/pages/general_settings_page.dart` and `lib/features/settings/presentation/pages/transcription_settings_page.dart` as WHOLE FILES: this scan already matched 9 separate duplicated blocks between them, totalling at least 150 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `lib/features/settings/presentation/pages/general_settings_page.dart:113` 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.
D4 · Code Duplication · Duplicated block (11–12 lines × 3) · ×1
  • Duplicated block (11–12 lines × 3) lib/features/mobile/presentation/widgets/mobile_local_models_step.dart:452 — lib/features/mobile/presentation/widgets/mobile_local_models_step.dart:452-462 | lib/features/onboarding/presentation/widgets/local_step.dart:525-535 | lib/features/settings/presentation/pages/transcription_settings_page.dart:499-510 — before extracting anything, compare `lib/features/mobile/presentation/widgets/mobile_local_models_step.dart` and `lib/features/onboarding/presentation/widgets/local_step.dart` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 133 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 `lib/features/mobile/presentation/widgets/mobile_local_models_step.dart:452` 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.
D4 · Code Duplication · Duplicated block (12 lines × 2) · ×1
  • Duplicated block (12 lines × 2) lib/features/settings/presentation/pages/assistant_settings_page.dart:109 — lib/features/settings/presentation/pages/assistant_settings_page.dart:109-121 | lib/features/settings/presentation/pages/output_settings_page.dart:100-111 — before extracting anything, compare `lib/features/settings/presentation/pages/assistant_settings_page.dart` and `lib/features/settings/presentation/pages/output_settings_page.dart` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 95 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `lib/features/settings/presentation/pages/assistant_settings_page.dart:109` 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.
D4 · Code Duplication · Duplicated block (11–12 lines × 2) · ×1
  • Duplicated block (11–12 lines × 2) lib/features/settings/presentation/pages/general_settings_page.dart:689 — lib/features/settings/presentation/pages/general_settings_page.dart:689-700 | lib/features/settings/presentation/pages/output_settings_page.dart:234-244 — before extracting anything, compare `lib/features/settings/presentation/pages/general_settings_page.dart` and `lib/features/settings/presentation/pages/output_settings_page.dart` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 88 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `lib/features/settings/presentation/pages/general_settings_page.dart:689` 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.
D4 · Code Duplication · Duplicated block (11 lines × 3) · ×1
  • Duplicated block (11 lines × 3) lib/features/mobile/presentation/widgets/mobile_api_key_section.dart:59 — lib/features/mobile/presentation/widgets/mobile_api_key_section.dart:59-69 | lib/features/mobile/presentation/widgets/mobile_theme_settings_section.dart:55-65 | lib/features/mobile/presentation/widgets/mobile_transcription_models_section.dart:55-65 — before extracting anything, compare `lib/features/mobile/presentation/widgets/mobile_api_key_section.dart` and `lib/features/mobile/presentation/widgets/mobile_theme_settings_section.dart` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 43 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.
D4 · Code Duplication · Duplicated block (11 lines × 2) · ×1
  • Duplicated block (11 lines × 2) lib/features/settings/presentation/widgets/dictionary_section.dart:71 — lib/features/settings/presentation/widgets/dictionary_section.dart:71-81 | lib/features/settings/presentation/widgets/dictionary_section.dart:178-188 — 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 `lib/features/settings/presentation/widgets/dictionary_section.dart:71` 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.
D4 · Code Duplication · Duplicated block (9–10 lines × 2) · ×1
  • Duplicated block (9–10 lines × 2) lib/features/info/presentation/pages/info_page.dart:36 — lib/features/info/presentation/pages/info_page.dart:36-44 | lib/features/onboarding/presentation/widgets/local_step.dart:232-241 — 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 `lib/features/onboarding/presentation/widgets/local_step.dart:232` 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.
D4 · Code Duplication · Duplicated block (8 lines × 5) · ×1
  • Duplicated block (8 lines × 5) lib/features/onboarding/presentation/widgets/api_key_step.dart:276 — lib/features/onboarding/presentation/widgets/api_key_step.dart:276-284 | lib/features/onboarding/presentation/widgets/completed_step.dart:116-123 | lib/features/onboarding/presentation/widgets/hotkeys_step.dart:296-304 | lib/features/onboarding/presentation/widgets/preferences_step.dart:92-100 | lib/features/onboarding/presentation/widgets/test_hotkeys_step.dart:158-166 — before extracting anything, compare `lib/features/onboarding/presentation/widgets/api_key_step.dart` and `lib/features/onboarding/presentation/widgets/hotkeys_step.dart` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 100 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `lib/features/onboarding/presentation/widgets/api_key_step.dart:276` 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.
D4 · Code Duplication · Duplicated block (8 lines × 4) · ×1
  • Duplicated block (8 lines × 4) lib/features/onboarding/presentation/widgets/completed_step.dart:114 — lib/features/onboarding/presentation/widgets/completed_step.dart:114-121 | lib/features/onboarding/presentation/widgets/hotkeys_step.dart:355-362 | lib/features/onboarding/presentation/widgets/preferences_step.dart:137-144 | lib/features/onboarding/presentation/widgets/test_hotkeys_step.dart:223-230 — before extracting anything, compare `lib/features/onboarding/presentation/widgets/completed_step.dart` and `lib/features/onboarding/presentation/widgets/hotkeys_step.dart` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 64 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `lib/features/onboarding/presentation/widgets/completed_step.dart:114` 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.
D4 · Code Duplication · Duplicated block (6 lines × 2) · ×1
  • Duplicated block (6 lines × 2) lib/features/onboarding/presentation/widgets/local_step.dart:589 — lib/features/onboarding/presentation/widgets/local_step.dart:589-594 | lib/features/settings/presentation/pages/transcription_settings_page.dart:620-625 — before extracting anything, compare `lib/features/onboarding/presentation/widgets/local_step.dart` and `lib/features/settings/presentation/pages/transcription_settings_page.dart` as WHOLE FILES: this scan already matched 16 separate duplicated blocks between them, totalling at least 359 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. Note first that the copies are not typed on the same thing: the declarations holding them bind `state` to `OnboardingState` in one and `SettingsState` 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.
D4 · Code Duplication · Duplicated block (49 lines × 2) · ×1
  • Duplicated block (49 lines × 2) lib/features/settings/presentation/widgets/assistant_models_section.dart:72 — lib/features/settings/presentation/widgets/assistant_models_section.dart:72-120 | lib/features/settings/presentation/widgets/transcription_models_section.dart:74-122 — before extracting anything, compare `lib/features/settings/presentation/widgets/assistant_models_section.dart` and `lib/features/settings/presentation/widgets/transcription_models_section.dart` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 218 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.
D4 · Code Duplication · Duplicated block (8 lines × 3) · ×1
  • Duplicated block (8 lines × 3) macos/Runner/AppDelegate.swift:265 — macos/Runner/AppDelegate.swift:265-272 | macos/Runner/AppDelegate.swift:363-370 | macos/Runner/AppDelegate.swift:384-391 — 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 `macos/Runner/AppDelegate.swift:265` 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.
D4 · Code Duplication · Duplicated block (5 lines × 8) · ×1
  • Duplicated block (5 lines × 8) macos/Runner/AppDelegate.swift:171 — macos/Runner/AppDelegate.swift:171-175 | macos/Runner/AppDelegate.swift:265-269 | macos/Runner/AppDelegate.swift:298-302 | macos/Runner/AppDelegate.swift:309-313 | macos/Runner/AppDelegate.swift:320-324 | macos/Runner/AppDelegate.swift:363-367 | macos/Runner/AppDelegate.swift:384-388 | macos/Runner/AppDelegate.swift:405-409 — all 8 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.
D4 · Code Duplication · Duplicated block (6 lines × 3) · ×1
  • Duplicated block (6 lines × 3) macos/Runner/AppDelegate.swift:98 — macos/Runner/AppDelegate.swift:98-103 | macos/Runner/AppDelegate.swift:111-116 | macos/Runner/AppDelegate.swift:127-132 — 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.
P1 · CI/CD gates · No CI pipeline · ×1
  • No CI pipeline — No CI workflow found (.github/workflows, azure-pipelines.yml, .gitlab-ci.yml, …) — changes aren't gated by an automated build/test.
P2 · Observability · No structured logging · ×1
  • No structured logging — No logging or diagnostics emission found. This repository ships a binary its users launch rather than a service you operate, so there is no operator to page — but when a run fails on a user's machine, neither they nor you have anything to read.
PF3 · Async & latency hygiene · Sync-over-async blocking · ×1
  • Sync-over-async blocking lib/core/storage/transcription_storage.dart:41 — `listTranscriptions` is async and calls listSync — a blocking call inside async code stalls the isolate's event loop — every other event, on Flutter the next frame, waits for as long as it runs.
Minor — 109 finding(s)
D34 · Knowledge Freshness · Orphaned file · ×88
  • Orphaned file lib/features/settings/presentation/pages/transcription_settings_page.dart:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file lib/features/hotkeys/handlers/push_to_talk_handler.dart:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file REDACTED:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file lib/features/onboarding/presentation/widgets/local_step.dart:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file lib/features/settings/presentation/pages/output_settings_page.dart:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file lib/features/mobile/presentation/widgets/mobile_local_models_step.dart:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file macos/Runner/RecordingOverlayWindow.swift:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file macos/Runner/WhisperKitService.swift:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file lib/features/hotkeys/handlers/transcription_hotkey_handler.dart:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file lib/features/onboarding/presentation/widgets/permissions_step.dart:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file lib/features/onboarding/presentation/widgets/hotkeys_step.dart:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file lib/features/recording/data/datasources/recording_datasource.dart:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file lib/features/onboarding/presentation/pages/onboarding_page.dart:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file lib/features/onboarding/presentation/widgets/api_key_step.dart:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file lib/features/settings/presentation/pages/settings.dart:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file lib/features/mobile/presentation/pages/mobile_onboarding_page.dart:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file lib/features/navigation/presentation/pages/main_layout.dart:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file lib/features/mobile/presentation/widgets/mobile_api_key_step.dart:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file lib/features/hotkeys/utils/hotkey_registration.dart:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file lib/features/mobile/presentation/widgets/mobile_local_models_section.dart:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file lib/features/hotkeys/core/hotkey_handler.dart:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file lib/core/theme/app_theme.dart:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file macos/Runner/AppDelegate.swift:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file lib/features/mobile/presentation/widgets/mobile_permissions_step.dart:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file lib/features/info/presentation/pages/info_page.dart:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • + 63 more in this group — see findings.md.
X10 · Duplicated predicate · Duplicated predicate · ×7
  • Duplicated predicate lib/features/settings/presentation/pages/output_settings_page.dart:521 — `_fromPhraseController.text.isNotEmpty && _toPhraseController.text.isNotEmpty` appears character-identically in 2 files — lib/features/settings/presentation/pages/output_settings_page.dart, lib/features/settings/presentation/widgets/dictionary_section.dart. 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 lib/features/settings/presentation/pages/output_settings_page.dart:507 — `_fromPhraseController.text.isNotEmpty && value.isNotEmpty` appears character-identically in 2 files — lib/features/settings/presentation/pages/output_settings_page.dart, lib/features/settings/presentation/widgets/dictionary_section.dart. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate REDACTED:86 — `_recordingRepository == null || _transcriptionRepository == null` appears character-identically in 3 files — REDACTED, lib/features/hotkeys/handlers/push_to_talk_handler.dart, lib/features/hotkeys/handlers/transcription_hotkey_handler.dart. 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 lib/features/onboarding/presentation/widgets/local_step.dart:591 — `error.toLowerCase().contains('authorization') || error.toLowerCase().contains('authorizationrequired')` appears character-identically in 2 files — lib/features/onboarding/presentation/widgets/local_step.dart, lib/features/settings/presentation/pages/transcription_settings_page.dart. 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 lib/features/hotkeys/handlers/push_to_talk_handler.dart:546 — `smartTranscriptionEnabled && transcriptionText.isNotEmpty && apiKey.isNotEmpty` appears character-identically in 3 files — lib/features/hotkeys/handlers/push_to_talk_handler.dart, lib/features/hotkeys/handlers/transcription_hotkey_handler.dart, lib/features/transcription/presentation/bloc/transcription_bloc.dart. 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 lib/features/onboarding/presentation/widgets/completed_step.dart:64 — `state.transcriptionEnabled && state.assistantEnabled` appears character-identically in 2 files — lib/features/onboarding/presentation/widgets/completed_step.dart, lib/features/onboarding/presentation/widgets/hotkeys_step.dart. 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 lib/features/hotkeys/handlers/push_to_talk_handler.dart:520 — `storedReplacements != null && storedReplacements.isNotEmpty` appears character-identically in 3 files — lib/features/hotkeys/handlers/push_to_talk_handler.dart, lib/features/hotkeys/handlers/transcription_hotkey_handler.dart, lib/features/transcription/presentation/bloc/transcription_bloc.dart. 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.
D34 · Knowledge Freshness · Most significant orphaned file · ×3
  • Most significant orphaned file lib/features/settings/presentation/bloc/settings_bloc.dart:1 — One of the orphaned files carrying the most lost knowledge — ranked by size weighted by the file's role in the codebase, the same weighting behind the score above, so core code outranks equally large plumbing. A reasonable place to start a read-through before the aggregate risk above bites.
  • Most significant orphaned file lib/features/onboarding/presentation/bloc/onboarding_bloc.dart:1 — One of the orphaned files carrying the most lost knowledge — ranked by size weighted by the file's role in the codebase, the same weighting behind the score above, so core code outranks equally large plumbing. A reasonable place to start a read-through before the aggregate risk above bites.
  • Most significant orphaned file lib/features/settings/presentation/pages/general_settings_page.dart:1 — One of the orphaned files carrying the most lost knowledge — ranked by size weighted by the file's role in the codebase, the same weighting behind the score above, so core code outranks equally large plumbing. A reasonable place to start a read-through before the aggregate risk above bites.
D20 · ADR Quality · No ADRs found · ×1
  • No ADRs found macos/Runner.xcodeproj/project.pbxproj:1 — No ADRs found. No recognised ADR directory (`docs/adr/`, `docs/decisions/`, `adr/`, `docs/rfcs/`, an `ADR0001/` folder, or their siblings) exists anywhere in this tree. What was searched, so you can tell an empty log from a search that missed one: every directory under the tree (build output, dependencies and VCS metadata excepted), for a document that is either any non-index page inside a recognised ADR directory, whatever its name and however deeply nested (`docs/adr/use-postgres.md`, `docs/adr/2024/0001-x.md`); or a file anywhere whose name is ADR-shaped (`0001-use-postgres.md`, `adr-012-caching.md`); or, when neither turned anything up, a document carrying the decision-record signature (an "Architecture Decision Record" heading, or Status / Context / Decision / Consequences as section headings). A decision log that clears none of these — unnumbered files outside any recognised directory, without those headings — is not seen by this check and this row is then wrong. If that is your case, say so rather than renaming anything; otherwise, consider recording architectural decisions in `docs/adr/`. ADRs are expected here because `macos/Runner.xcodeproj/project.pbxproj` makes this repository a deployable product (line 1).
D21 · Naming Consistency · `_sendToGroqAPI` spells `API` where 39 names in the project spell it `Api` · ×1
  • `_sendToGroqAPI` spells `API` where 39 names in the project spell it `Api` REDACTED:449 — 39 of 40 names in project repository.features spell the token `Api` (39 of 40; unit: names in project repository.features containing `Api`). Peers: MobileOnboardingBloc._onUpdateApiKey (lib/features/mobile/presentation/bloc/mobile_onboarding_bloc.dart:103); MobileOnboardingBloc._onToggleApiKeyVisibility (lib/features/mobile/presentation/bloc/mobile_onboarding_bloc.dart:113); MobileOnboardingBloc._onValidateApiKey (lib/features/mobile/presentation/bloc/mobile_onboarding_bloc.dart:122); MobileOnboardingBloc._onClearApiKey (lib/features/mobile/presentation/bloc/mobile_onboarding_bloc.dart:148); repository.features.UpdateApiKey (lib/features/mobile/presentation/bloc/mobile_onboarding_event.dart:28). Rename to `_sendToGroqApi`. [rule N6]
D26 · Project Cohesion · Projects may be oversized for their cohesion · ×1
  • Projects may be oversized for their cohesion pubspec.yaml:1 — `(repository root)` (26677 LoC, 256 module-visible types across 43 directories) overshoots its size bounds. 1 of 4 build unit(s) (Gradle, Xcode, pub) overshoot their size bounds, lowering Project Cohesion to 5.0/10. 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
  • REDACTED
D29 · Static Analysis (SAST) · REDACTED · ×1
  • REDACTED
D34 · Knowledge Freshness · Dormant codebase · ×1
  • Dormant codebase — 91 of 91 significant files have no living knowledge — the codebase as a whole is dormant, not 91 separate risks. Counted over 91 of the 130 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over. Re-engage owners or document before change.
M2 · Architecture documentation · No ADRs · ×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.
M4 · Documentation accuracy · README/code drift · ×1
  • README/code drift README.md:402 — README.md links to `BUILD_INSTRUCTIONS.md`, but `BUILD_INSTRUCTIONS.md` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
P3 · Security & performance tooling · No SAST · ×1
  • No SAST — No static application security testing detected. For this repository's stack, add the Dart analyzer's security lints plus `semgrep --config=auto` — this repository has no CI pipeline yet, so run it locally to clear the existing findings, then make it a step of the first workflow you add so a regression fails the build. What was searched, so you can tell an absence from a miss: the 0 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.
P6 · Release Hygiene · No changelog · ×1
  • No changelog — No CHANGELOG/HISTORY/RELEASES file — what shipped when isn't easy to reconstruct for support or audit. (Versioning/tagging makes releases traceable, but a changelog records the what.)
X7 · Silent fallback defaults · Silent fallback default in catch · ×1
  • Silent fallback default in catch lib/features/onboarding/presentation/widgets/completed_step.dart:196 — `_formatHotkey` turns every thrown error into `'Custom Hotkey'` — a data error becomes a silent behavior change with no trail. Log the error or rethrow it. If that constant is the correct answer rather than a stand-in for a value that could not be read, say so in a comment at the `catch` or in the `///` doc, and the row stops firing.
Minor — 1 finding(s)
D12 · Dependency Hygiene · Outdated · ×1
  • Outdated: Sparkle — `Sparkle` is locked at 2.7.0 in macos/Podfile.lock, but 2.9.6 is the newest release the CocoaPods trunk lists within the same major. A `~>` requirement admits every release below the next major — so `pod update Sparkle` reaches this one with no change to the Podfile.

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.

DimensionToolVersionCommandFindingsRaw output
D28 · Secrets (history)gitleaks—gitleaks detect --no-banner --config /opt/gitleaks-rules/canine-gitleaks.toml --log-opts "--full-history --all --skip=0 --max-count=200" --report-format json --report-path /tmp/watchdog-gitleaks-4226b423ec254c34acd39854707086ba/history.json --exit-code 0 --source .0artifacts/raw/gitleaks-history.json
D28 · Secrets (history)gitleaks—gitleaks detect --no-banner --config /opt/gitleaks-rules/canine-gitleaks.toml --log-opts "--full-history --all --skip=200 --max-count=62" --report-format json --report-path /tmp/watchdog-gitleaks-4226b423ec254c34acd39854707086ba/history-1.json --exit-code 0 --source .1artifacts/raw/gitleaks-history-1.json
D28 · Secrets (history)gitleaks—gitleaks detect --no-git --no-banner --config /opt/gitleaks-rules/canine-gitleaks.toml --report-format json --report-path /tmp/watchdog-gitleaks-4226b423ec254c34acd39854707086ba/tree.json --exit-code 0 --source .0artifacts/raw/gitleaks-tree.json
D29 · Static Analysis (SAST)semgrep—semgrep --config /opt/semgrep-rules/security-audit.yml --config /opt/semgrep-rules/owasp-top-ten.yml --config /opt/semgrep-rules/canine-sast.yml --json --quiet --timeout 10 --timeout-threshold 3 --metrics off --exclude *.arrow --exclude *.avro --exclude *.csv --exclude *.dat --exclude *.db --exclude *.feather --exclude *.geojson --exclude *.h5 --exclude *.hdf5 --exclude *.jsonl --exclude *.log --exclude *.ndjson --exclude *.npy --exclude *.npz --exclude *.orc --exclude *.parquet --exclude *.pickle --exclude *.pkl --exclude *.psv --exclude *.sqlite --exclude *.sqlite3 --exclude *.tfrecord --exclude *.tsv --exclude *.txt .1artifacts/raw/semgrep.json
D30 · Dependency Vulnerabilitiesosv-scanner—osv-scanner --format json --recursive --experimental-disable-plugins transitivedependency/requirements --experimental-disable-plugins dotnet/csproj --experimental-disable-plugins dotnet/nugetcpm .0artifacts/raw/osv-scanner.json
D31 · IaC & Container Securitytrivy—trivy: not applicable — No Infrastructure-as-Code or container manifests found (Dockerfile, Docker Compose, Terraform, Kubernetes/Helm, CloudFormation, ARM, Bicep, Ansible); nothing to scan.0—
D32 · Data Compliance (PII/GDPR)semgrep—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.0—
D36 · Supply-chain Provenance & Signingprovenance—provenance: not applicable — No CI/build pipeline found (.github/.forgejo/.gitea workflows, .circleci, .buildkite, .woodpecker, .teamcity, .gitlab-ci.yml, .travis.yml, bitbucket-pipelines.yml, .drone.yml, .cirrus.yml, .woodpecker.yml, appveyor.yml, azure-pipelines*.yml, .pipelines/, .vsts-ci/, .azuredevops/, Jenkinsfile); there is no build to attest provenance for.0—
D37 · Vulnerability-disclosure Policydisclosure—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.0—
D40 · Network Egress Confinementruntime-hardening—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.0—
D41 · Kernel & Syscall Confinementruntime-hardening—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.0—
D42 · Runtime Threat Enforcementruntime-hardening—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.0—
D43 · Malicious Dependenciesosv-scanner—osv-scanner --format json --recursive --experimental-disable-plugins transitivedependency/requirements --experimental-disable-plugins dotnet/csproj --experimental-disable-plugins dotnet/nugetcpm .0artifacts/raw/osv-scanner.json

Run 01a1e4ea-cd78-7085-a945-ae10b44100d4 · every finding is also locatable in findings.md, and the complete scoring record (with exit codes + durations) in sidecar.json.

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.

⬇ Findings, MITRE CWE-tagged .sarif⬇ Health changelog .md