Public report of nguyenphutrong/quotio, published 14 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, 14 November 2026, 22:02 UTC · Survey ID cd_7017a18563604589a5e982b5478d4187

nguyenphutrong/quotio

Measured 14 November 2026, 22:00 UTC, at code version 3ea984c

CAI score 64out of 100 Adequate
CriticalWeakAdequateStrongExemplary
No change since the last survey

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

A large codebase: 107,852 lines of product code in 12 projects, tests not counted · Estimated rebuild effort: about 1.4 person-years · Weakest lens: Production Readiness, 60

Findings by how serious they are

3 critical 330 serious 22 minor

25 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
14 November 2026, 22:00 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 ▸

50of 50 dimensions measured by tools.
340of 355 findings point to an exact file and line, so you can open each one in the code. The other 15 concern the repository as a whole, such as missing documentation.
50dimensions across 7 lenses, read from 107,852 lines of product code in 12 projects.
Chapters

Executive summary

nguyenphutrong/quotio falls short of our standard for production, held back most by its Production Readiness lens, the way the code is tested, built, released and run. It scores 64 out of 100 and is rated Adequate, and two of its three critical findings are security problems in its code.

Production Readiness, at 60, is the weakest lens, level with Performance, and counts most in the score. The best first step is removing the blocking calls, worth about 4 points. Protecting outgoing calls with timeouts would lift Production Readiness itself, worth about 3 points. Raising Production Readiness to 70 would lift the score to about 67.

Two weaknesses in the code could be used by an attacker. One set of files in separate parts keeps changing together, which points to a hidden dependency. Fixing the weaknesses the scanner points to and making the hidden dependencies explicit would close both risks.

The product code is 107,852 lines, about €200,000 to rebuild.

A lens is capped at Adequate while one of its dimensions scores below 4 out of 10, however well the rest of the lens does. That way a serious problem in one place always shows in the lens's rating.

How the score is built: what each lens counts 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 60 · counts for 46%Performance 60 · counts for 25%Maturity 70 · counts for 14%Code Health 72 · counts for 8%Security and Compliance 84 · counts for 4%Architecture 94 · counts for 2%Domain Modelling 100 · counts for 1%

If Production Readiness rose from 60 to 70, the lowest score rated Strong, the score would rise from 64 to about 67.

Code composition: what the lines of code are
Product code 85%Tests 15%
New since the last survey: 119 findings

These 119 critical or serious findings weren't in the previous survey, on 28 October 2026. The first 100 are listed here, and the findings file in the download package lists them all.

  • Cyclomatic Complexity · package.macos (cyclomatic 33) apps/desktop/scripts/package.py
  • Cyclomatic Complexity · quotio_desktop::prefs::swift_preferences (cyclomatic 26) apps/desktop/src/prefs.rs
  • Cyclomatic Complexity · quotio_desktop::main (cyclomatic 22) apps/desktop/src/main.rs
  • Cyclomatic Complexity · quotio_desktop::ui::menu::burn_card (cyclomatic 21) apps/desktop/src/ui/menu.rs
  • Cyclomatic Complexity · package.main (cyclomatic 20) apps/desktop/scripts/package.py
  • Cyclomatic Complexity · QuotaHistory::plot (cyclomatic 16) apps/desktop/src/ui/settings/history.rs
  • Cognitive Complexity · package.macos (cognitive 45) apps/desktop/scripts/package.py
  • Cognitive Complexity · quotio_desktop::prefs::swift_preferences (cognitive 32) apps/desktop/src/prefs.rs
  • Cognitive Complexity · quotio_desktop::ui::menu::burn_card (cognitive 32) apps/desktop/src/ui/menu.rs
  • Cognitive Complexity · quotio_desktop::tray::icon::gauge (cognitive 31) apps/desktop/src/tray/icon.rs
  • Cognitive Complexity · quotio_desktop::notifier::check (cognitive 27) apps/desktop/src/notifier.rs
  • Cognitive Complexity · package.main (cognitive 26) apps/desktop/scripts/package.py
  • Cognitive Complexity · QuotaHistory::plot (cognitive 24) apps/desktop/src/ui/settings/history.rs
  • Cognitive Complexity · quotio_desktop::main (cognitive 22) apps/desktop/src/main.rs
  • Cognitive Complexity · quotio_desktop::proxy::init (cognitive 16) apps/desktop/src/proxy.rs
  • Cognitive Complexity · quotio_desktop::ui::settings::privacy::migration_section (cognitive 16) apps/desktop/src/ui/settings/privacy.rs
  • God Classes · MethodTooLong: SettingsWindow.accounts_page apps/desktop/src/ui/settings/accounts.rs
  • God Classes · FileTooLong: ui/menu.rs apps/desktop/src/ui/menu.rs
  • God Classes · ClassTooLong: ConnectFlow apps/desktop/src/ui/settings/connect.rs
  • God Classes · FileTooLong: settings/accounts.rs apps/desktop/src/ui/settings/accounts.rs
  • God Classes · FileTooLong: settings/connect.rs apps/desktop/src/ui/settings/connect.rs
  • God Classes · MethodTooLong: SettingsWindow.menu_bar_page apps/desktop/src/ui/settings/menu_bar.rs
  • God Classes · FunctionTooLong: quotio_desktop::ui::menu::burn_card apps/desktop/src/ui/menu.rs
  • God Classes · TooManyMethods: SettingsWindow apps/desktop/src/ui/settings/mod.rs
  • God Classes · MethodTooLong: SettingsWindow.proxy_server apps/desktop/src/ui/settings/cli_proxy.rs
  • God Classes · MethodTooLong: SettingsWindow.account_row apps/desktop/src/ui/settings/accounts.rs
  • God Classes · MethodTooLong: SettingsWindow.general_page apps/desktop/src/ui/settings/general.rs
  • God Classes · MethodTooLong: QuotaHistory.plot apps/desktop/src/ui/settings/history.rs
  • God Classes · ClassTooLong: QuotaHistory apps/desktop/src/ui/settings/history.rs
  • God Classes · FileTooLong: src/proxy.rs apps/desktop/src/proxy.rs
  • God Classes · FileTooLong: settings/menu_bar.rs apps/desktop/src/ui/settings/menu_bar.rs
  • God Classes · MethodTooLong: AccountPanel.render apps/desktop/src/ui/panel.rs
  • God Classes · MethodTooLong: ConnectFlow.browser_view apps/desktop/src/ui/settings/connect.rs
  • God Classes · MethodTooLong: SettingsWindow.about_page apps/desktop/src/ui/settings/about.rs
  • God Classes · FileTooLong: settings/iphone.rs apps/desktop/src/ui/settings/iphone.rs
  • God Classes · FunctionTooLong: quotio_desktop::prefs::swift_preferences apps/desktop/src/prefs.rs
  • God Classes · MethodTooLong: QuotaHistory.summary apps/desktop/src/ui/settings/history.rs
  • God Classes · FileTooLong: settings/history.rs apps/desktop/src/ui/settings/history.rs
  • God Classes · MethodTooLong: SettingsWindow.style_options apps/desktop/src/ui/settings/menu_bar.rs
  • God Classes · FunctionTooLong: quotio_desktop::ui::menu::gauge apps/desktop/src/ui/menu.rs
  • God Classes · FunctionTooLong: quotio_desktop::main apps/desktop/src/main.rs
  • God Classes · MethodTooLong: SettingsWindow.privacy_page apps/desktop/src/ui/settings/privacy.rs
  • Code Duplication · Edited copy of a member (31 corresponding lines) apps/desktop/src/ui/menu.rs
  • Code Duplication · Members sharing a duplicated core (4 members, 50+ identical tokens) Packages/QuotioCore/Sources/QuotioInfrastructure/Accounts/LocalProxyOAuthAuthorizer.swift
  • Code Duplication · Edited copy of a member (39 corresponding lines) Packages/QuotioCore/Sources/QuotioPresentation/MenuBar/StatusBarMenuRenderer.swift
  • Code Duplication · Edited copy of a member (31 corresponding lines) apps/desktop/src/ui/settings/accounts.rs
  • Code Duplication · Edited copy of a member (49 corresponding lines) Packages/QuotioCore/Sources/QuotioPresentation/Settings/ProxyVersionManagerSheet.swift
  • Code Duplication · Edited copy of a member (28 corresponding lines) Packages/QuotioCore/Sources/QuotioPresentation/Components/MenuBarBadge.swift
  • Code Duplication · Edited copy of a member (12 corresponding lines) Packages/QuotioCore/Sources/QuotioDomain/Proxy/ProxyManagementModels.swift
  • Code Duplication · Edited copy of a member (29 corresponding lines) Packages/QuotioCore/Sources/QuotioPresentation/Components/MenuBarBadge.swift
  • Code Duplication · Edited copy of a member (24 corresponding lines) apps/desktop/src/autostart.rs
  • Code Duplication · Edited copy of a member (18 corresponding lines) apps/desktop/src/theme.rs
  • Code Duplication · Edited copy of a member (45 corresponding lines) Packages/QuotioCore/Sources/QuotioPresentation/Components/ProviderAccountsGroup.swift
  • Code Duplication · Edited copy of a member (27 corresponding lines) apps/desktop/src/ui/settings/cli_proxy.rs
  • Code Duplication · Edited copy of a member (27 corresponding lines) Packages/QuotioCore/Sources/QuotioPresentation/Components/ProviderAccountsGroup.swift
  • Code Duplication · Edited copy of a member (13 corresponding lines) apps/desktop/src/ui/settings/iphone.rs
  • Code Duplication · Edited copy of a member (19 corresponding lines) Packages/QuotioCore/Sources/QuotioPresentation/Components/GLMAPIKeySheet.swift
  • Code Duplication · Edited copy of a member (16 corresponding lines) Packages/QuotioCore/Sources/QuotioApplication/Proxy/ProxyLifecycleController.swift
  • Code Duplication · Edited copy of a member (12 corresponding lines) Packages/QuotioCore/Sources/QuotioInfrastructure/HTTP/ProxyNetworkAdapters.swift
  • Code Duplication · Edited copy of a member (7 corresponding lines) apps/ios/Sources/QuotioMobile/QuotaFormat.swift
  • Code Duplication · Edited copy of a member (7 corresponding lines) Packages/QuotioCore/Sources/QuotioInfrastructure/QuotioCLI/QuotioCompanionService.swift
  • Code Duplication · Edited copy of a member (7 corresponding lines) Packages/QuotioHostClient/Sources/QuotioHostClient/QuotioHostHistory.swift
  • Code Duplication · Edited copy of a member (15 corresponding lines) Packages/QuotioCore/Sources/QuotioPresentation/Quota/QuotaHistoryServiceModel.swift
  • Code Duplication · Edited copy of a member (6 corresponding lines) Packages/QuotioCore/Sources/QuotioPresentation/MenuBar/StatusBarMenuRenderer.swift
  • Code Duplication · Edited copy of a member (9 corresponding lines) Packages/QuotioCore/Sources/QuotioPresentation/Settings/ProviderAccountsSection.swift
  • Code Duplication · Edited copy of a member (16 corresponding lines) Packages/QuotioCore/Sources/QuotioPresentation/Components/ProviderIcon.swift
  • Code Duplication · Edited copy of a member (5 corresponding lines) Packages/QuotioCore/Sources/QuotioApplication/CustomProviders/CustomProviderService.swift
  • Code Duplication · Edited copy of a member (10 corresponding lines) Packages/QuotioCore/Sources/QuotioApplication/Proxy/ProxyLifecycleController.swift
  • Code Duplication · Edited copies of one member (3 members, 13+ corresponding lines) Packages/QuotioCore/Sources/QuotioPresentation/Components/QuotioButtonStyles.swift
  • Code Duplication · Edited copy of a member (15 corresponding lines) Packages/QuotioCore/Sources/QuotioApplication/Accounts/AuthFileRepository.swift
  • Code Duplication · Edited copy of a member (11 corresponding lines) Packages/QuotioCore/Sources/QuotioApplication/Proxy/ProxyLifecycleController.swift
  • Code Duplication · Edited copy of a member (14 corresponding lines) apps/desktop/src/ui/mod.rs
  • Code Duplication · Edited copy of a member (10 corresponding lines) Packages/QuotioCore/Sources/QuotioPresentation/Proxy/ProxyManagementScreenModel.swift
  • Code Duplication · Edited copies of one member (3 members, 10+ corresponding lines) Packages/QuotioCore/Sources/QuotioApplication/Accounts/OAuthFlow.swift
  • Code Duplication · Edited copy of a member (5 corresponding lines) Packages/QuotioCore/Sources/QuotioPresentation/Components/ExperimentalBadge.swift
  • Code Duplication · Edited copy of a member (7 corresponding lines) Packages/QuotioCore/Sources/QuotioPresentation/MenuBar/StatusBarMenuRenderer.swift
  • Code Duplication · Edited copy of a member (10 corresponding lines) Packages/QuotioCore/Sources/QuotioPresentation/Quota/QuotaScreenModel.swift
  • Code Duplication · Edited copy of a member (5 corresponding lines) Packages/QuotioCore/Sources/QuotioInfrastructure/Antigravity/AntigravityAccountSwitcher.swift
  • Code Duplication · Edited copy of a member (4 corresponding lines) Packages/QuotioCore/Sources/QuotioInfrastructure/CustomProviders/CustomProviderAdapters.swift
  • Code Duplication · Edited copy of a member (6 corresponding lines) Packages/QuotioCore/Sources/QuotioDomain/CustomProviders/CustomProviderModels.swift
  • Code Duplication · Edited copy of a member (5 corresponding lines) Packages/QuotioCore/Sources/QuotioApplication/Proxy/ProxyLifecycleController.swift
  • Code Duplication · Edited copy of a member (6 corresponding lines) Packages/QuotioCore/Sources/QuotioDomain/Accounts/AntigravitySwitchModels.swift
  • Code Duplication · Edited copy of a member (3 corresponding lines) Packages/QuotioCore/Sources/QuotioInfrastructure/QuotioCLI/QuotioHostPresentationMapper.swift
  • Code Duplication · Edited copy of a member (5 corresponding lines) Packages/QuotioCore/Sources/QuotioDomain/Proxy/ProxyManagementModels.swift
  • Code Duplication · Duplicated block (6 lines × 2) Packages/QuotioCore/Sources/QuotioInfrastructure/Persistence/FileAccountMetadataRepository.swift
  • Code Duplication · Duplicated block (14–16 lines × 2) apps/desktop/src/app.rs
  • Code Duplication · Duplicated block (15 lines × 2) apps/desktop/src/theme.rs
  • Code Duplication · Duplicated block (14 lines × 2) apps/desktop/src/ui/menu.rs
  • Code Duplication · Duplicated block (13 lines × 2) apps/desktop/src/ui/menu.rs
  • Code Duplication · Duplicated block (8–9 lines × 2) apps/desktop/src/autostart.rs
  • Code Duplication · Duplicated block (8–9 lines × 2) apps/desktop/src/ui/menu.rs
  • Code Duplication · Duplicated block (9 lines × 2) apps/desktop/src/ui/settings/accounts.rs
  • Code Duplication · Duplicated block (7 lines × 2) apps/desktop/src/ui/settings/connect.rs
  • Code Duplication · Duplicated block (6 lines × 2) apps/desktop/src/ui/settings/accounts.rs
  • Code Duplication · Duplicated block (5 lines × 3) apps/desktop/src/ui/settings/accounts.rs
  • Code Duplication · Duplicated block (5 lines × 2) apps/desktop/src/host.rs
  • Code Duplication · Duplicated block (5 lines × 2) apps/desktop/src/app.rs
  • Code Duplication · Duplicated block (12 lines × 2) apps/desktop/src/ui/settings/connect.rs
  • Code Duplication · Duplicated block (10 lines × 2) apps/desktop/src/ui/settings/general.rs
  • Code Duplication · Duplicated block (8 lines × 2) apps/desktop/src/ui/settings/accounts.rs

We compare every finding with the previous survey's. A finding that has only moved to another line in the same file counts as the same finding, so only new findings appear here. Advisory notes from the AI model are left out, because the model words them afresh in every survey.

Fixed since the last survey: 18 findings

These 18 critical or serious findings were in the previous survey, on 28 October 2026, and are gone from this one.

  • Code Duplication · Members sharing a duplicated core (9 members, 50+ identical tokens) Packages/QuotioCore/Sources/QuotioApplication/Proxy/ProxyLifecycleController.swift
  • Code Duplication · Members sharing a duplicated core (4 members, 50+ identical tokens) Packages/QuotioCore/Sources/QuotioInfrastructure/Accounts/LocalProxyOAuthAuthorizer.swift
  • Code Duplication · Duplicated block (12 lines × 7) Packages/QuotioCore/Sources/QuotioApplication/Proxy/ProxyLifecycleController.swift
  • Code Duplication · Duplicated block (12 lines × 7) Packages/QuotioCore/Sources/QuotioApplication/Quota/QuotaPorts.swift
  • Code Duplication · Duplicated block (5 lines × 2) apps/ios/Sources/QuotioMobile/ConnectionIssue.swift
  • Code Duplication · Duplicated block (5 lines × 2) apps/ios/Sources/QuotioMobile/DisplayNames.swift
  • Code Duplication · Duplicated block (6 lines × 2) Packages/QuotioCore/Sources/QuotioDomain/Accounts/AntigravitySwitchModels.swift
  • Code Duplication · Duplicated block (6 lines × 2) Packages/QuotioCore/Sources/QuotioInfrastructure/Persistence/FileAccountMetadataRepository.swift
  • Code Duplication · Duplicated block (5 lines × 2) Packages/QuotioCore/Sources/QuotioDomain/CustomProviders/CustomProviderModels.swift
  • Churn × Complexity Hotspots · Hotspot: apps/cli/src/accounts/sources.rs apps/cli/src/accounts/sources.rs
  • Churn × Complexity Hotspots · Hotspot: apps/cli/src/accounts/oauth.rs apps/cli/src/accounts/oauth.rs
  • Churn × Complexity Hotspots · Hotspot: apps/cli/src/output/text.rs apps/cli/src/output/text.rs
  • Churn × Complexity Hotspots · Hotspot: Packages/QuotioCore/Sources/QuotioPresentation/Shared/ProviderPresentation.swift Packages/QuotioCore/Sources/QuotioPresentation/Shared/ProviderPresentation.swift
  • Churn × Complexity Hotspots · Hotspot: apps/cli/src/interactive.rs apps/cli/src/interactive.rs
  • Churn × Complexity Hotspots · Hotspot: Packages/QuotioCore/Sources/QuotioInfrastructure/Accounts/LocalProxyOAuthAuthorizer.swift Packages/QuotioCore/Sources/QuotioInfrastructure/Accounts/LocalProxyOAuthAuthorizer.swift
  • Churn × Complexity Hotspots · Hotspot: Packages/QuotioCore/Sources/QuotioPresentation/Components/OAuthSheet.swift Packages/QuotioCore/Sources/QuotioPresentation/Components/OAuthSheet.swift
  • Churn × Complexity Hotspots · Hotspot: Packages/QuotioCore/Sources/QuotioPresentation/App/PresentationValues.swift Packages/QuotioCore/Sources/QuotioPresentation/App/PresentationValues.swift
  • Dependency Vulnerabilities · Medium vulnerability: [GHSA redacted] REDACTED
Rebuild cost: about €200,000 · Estimate
Cost to rebuild€66,000 to €330,000, for 1,096 to 3,478 hours of work, about 1.4 person-years for 1 to 3 engineers
Difficulty of the problemHigh, 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.9 at a score of 64. 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.
SizeLarge: 107,852 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
Swift: await instead of blocking — `try await Task.sleep(for:)` for Thread.sleep/sleep, a checked continuation instead of a DispatchSemaphore or DispatchGroup wait, the async Process and URLSession APIs; never park a thread waiting on a Task — the cooperative pool cannot guarantee it progress.
Raises the score by about 4 points · Medium effort · Async & latency hygiene
2
Resolve the 1 No ADRs found finding(s) in ADR Quality — start with project.pbxproj.
Raises the score by about 2 points · Low effort · ADR Quality
3
Give every client a whole-request bound: `reqwest::Client::builder().timeout(Duration::from_secs(10))` (never `reqwest::get` or `Client::new()`, which have none), ureq's `timeout_global`, or wrap the call in `tokio::time::timeout`; add retry with back-off (`reqwest-retry`'s `RetryTransientMiddleware`, `backoff`) around dependencies that fail.
Raises the score by about 3 points · Medium effort · Outbound HTTP resilience

Diagnosis: what the measurements show together

Each conclusion below combines several dimensions into one point that no single dimension shows, and lists the measurements it rests on.

Where the investment is most exposed · Value at risk
This code would cost about €200,000 to build again, about 1.4 person-years of work. Its weakest lens is Production Readiness, at 60 (Adequate). 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
Swift: await instead of blocking — `try await Task.sleep(for:)` for Thread.sleep/sleep, a checked continuation instead of a DispatchSemaphore or DispatchGroup wait, the async Process and URLSession APIs; never park a thread waiting on a Task — the cooperative pool cannot guarantee it progress. Of all the actions in this report, it raises the score most for the work it takes: about 4 points for medium effort. The next survey will show the change in the score.
Based on: the ranked actions in Top priorities, by score gain and effort

Architecture — module dependency graph

Project dependencies, layered top-to-bottom; arrows show direction. Any dashed red edge points upward or sideways, which only happens where the projects form a dependency cycle. A graph without cycles has none.

arch Quotio (Xcode) Quotio (Xcode) QuotioApplication QuotioApplication Quotio (Xcode)->QuotioApplication QuotioDomain QuotioDomain Quotio (Xcode)->QuotioDomain QuotioInfrastructure QuotioInfrastructure Quotio (Xcode)->QuotioInfrastructure QuotioPresentation QuotioPresentation Quotio (Xcode)->QuotioPresentation QuotioApplication->QuotioDomain QuotioHostClient QuotioHostClient QuotioIOS QuotioIOS QuotioIOS->QuotioHostClient QuotioMobile QuotioMobile QuotioIOS->QuotioMobile QuotioInfrastructure->QuotioApplication QuotioInfrastructure->QuotioDomain QuotioInfrastructure->QuotioHostClient QuotioMobile->QuotioHostClient QuotioPresentation->QuotioApplication QuotioPresentation->QuotioDomain QuotioWidgets QuotioWidgets QuotioWidgets->QuotioHostClient QuotioWidgets->QuotioMobile quotio (Cargo) quotio (Cargo) quotio (npm) quotio (npm) quotio-desktop quotio-desktop quotio-desktop->quotio (Cargo)

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.

131 modules, with 320 dependencies between them. 5 loops run through 20 of the modules, marked above the diagonal.

The table shows the 40 modules with the most connections; 91 more are left out to keep it readable.

Which modules use which. The module on each row uses the module in each column, and the number counts the pairs of types that connect them. A cell above the diagonal is part of a loop.
uses →1 quotio.accounts.vault2 quotio.error3 quotio_desktop.theme4 Packages~QuotioHostClient~QuotioHostClient5 quotio.accounts.companion6 quotio.cli7 quotio.domain8 apps~ios~QuotioMobile9 quotio.accounts.sources10 quotio.providers11 quotio.settings12 quotio.accounts.adopt13 quotio.accounts.discovery14 quotio.accounts.oauth.copilot15 quotio.cache16 repository17 Packages~QuotioCore~QuotioPresentation18 quotio.contract19 quotio.server.security20 Packages~QuotioCore~QuotioInfrastructure21 quotio.history22 Packages~QuotioCore~QuotioDomain23 quotio.accounts24 quotio.accounts.proxy25 Packages~QuotioCore~QuotioApplication26 quotio.accounts.oauth.claude27 quotio.accounts.service28 quotio.contract.snapshot29 quotio.output.text30 quotio.providers.codex31 quotio_desktop.migration32 quotio.accounts.api33 quotio.accounts.oauth34 quotio.providers.factory35 quotio_desktop.prefs36 quotio.accounts.api.migration37 quotio.server38 quotio_desktop.model39 quotio.server.history40 quotio_desktop.ui.settings
1 quotio.accounts.vault
2 quotio.error
3 quotio_desktop.theme
4 Packages~QuotioHostClient~QuotioHostClient227337
5 quotio.accounts.companion1
6 quotio.cli1
7 quotio.domain2
8 apps~ios~QuotioMobile311316
9 quotio.accounts.sources11
10 quotio.providers3
11 quotio.settings3
12 quotio.accounts.adopt211
13 quotio.accounts.discovery34
14 quotio.accounts.oauth.copilot1
15 quotio.cache1142
16 repository17854233
17 Packages~QuotioCore~QuotioPresentation1233164190
18 quotio.contract11012
19 quotio.server.security211
20 Packages~QuotioCore~QuotioInfrastructure203097190
21 quotio.history1434
22 Packages~QuotioCore~QuotioDomain377102
23 quotio.accounts14211
24 quotio.accounts.proxy2241
25 Packages~QuotioCore~QuotioApplication3112106
26 quotio.accounts.oauth.claude1111
27 quotio.accounts.service34696
28 quotio.contract.snapshot141411
29 quotio.output.text3311
30 quotio.providers.codex323
31 quotio_desktop.migration11
32 quotio.accounts.api1323161
33 quotio.accounts.oauth142121
34 quotio.providers.factory1213111
35 quotio_desktop.prefs13
36 quotio.accounts.api.migration11111
37 quotio.server13114222211111
38 quotio_desktop.model2113
39 quotio.server.history111112
40 quotio_desktop.ui.settings22113
Uses a module listed above itPart of a loopThe module itself
1 quotio.accounts.vault2 quotio.error3 quotio_desktop.theme4 Packages~QuotioHostClient~QuotioHostClient5 quotio.accounts.companion6 quotio.cli7 quotio.domain8 apps~ios~QuotioMobile9 quotio.accounts.sources10 quotio.providers11 quotio.settings12 quotio.accounts.adopt13 quotio.accounts.discovery14 quotio.accounts.oauth.copilot15 quotio.cache16 repository17 Packages~QuotioCore~QuotioPresentation18 quotio.contract19 quotio.server.security20 Packages~QuotioCore~QuotioInfrastructure21 quotio.history22 Packages~QuotioCore~QuotioDomain23 quotio.accounts24 quotio.accounts.proxy25 Packages~QuotioCore~QuotioApplication26 quotio.accounts.oauth.claude27 quotio.accounts.service28 quotio.contract.snapshot29 quotio.output.text30 quotio.providers.codex31 quotio_desktop.migration32 quotio.accounts.api33 quotio.accounts.oauth34 quotio.providers.factory35 quotio_desktop.prefs36 quotio.accounts.api.migration37 quotio.server38 quotio_desktop.model39 quotio.server.history40 quotio_desktop.ui.settingsquotio.accounts.vault1quotio.error2quotio_desktop.theme3Packages~QuotioHostClient~QuotioHostClient4quotio.accounts.companion5quotio.cli6quotio.domain7apps~ios~QuotioMobile8quotio.accounts.sources9quotio.providers10quotio.settings11quotio.accounts.adopt12quotio.accounts.discovery13quotio.accounts.oauth.copilot14quotio.cache15repository16Packages~QuotioCore~QuotioPresentation17quotio.contract18quotio.server.security19Packages~QuotioCore~QuotioInfrastructure20quotio.history21Packages~QuotioCore~QuotioDomain22quotio.accounts23quotio.accounts.proxy24Packages~QuotioCore~QuotioApplication25quotio.accounts.oauth.claude26quotio.accounts.service27quotio.contract.snapshot28quotio.output.text29quotio.providers.codex30quotio_desktop.migration31quotio.accounts.api32quotio.accounts.oauth33quotio.providers.factory34quotio_desktop.prefs35quotio.accounts.api.migration36quotio.server37quotio_desktop.model38quotio.server.history39quotio_desktop.ui.settings4022733711231131611332113411142178542331233164190110122112030971901434377102142112241311210611113469614141133113231113231611421211213111131111113114222211111211311111222113+91 more modules (most-connected shown)

At a glance — Code Health · 72% · Strong ·

At a glance — Architecture · 94% · Exemplary ·

At a glance — Maturity · 70% · Adequate · gated by M2 ·

At a glance — Readiness · 60% · Adequate · gated by P7 ·

At a glance — Security · 84% · Checked 4 of 11 ·

At a glance — Domain Modelling · 100% · Exemplary ·

At a glance — Performance · 60% · Adequate ·

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
A03:2025 — Software Supply Chain Failures18Medium
A05:2025 — Injection2High / Critical
A01:2025 — Broken Access Control1Medium

Roadmap

Top priorities: Swift: await instead of blocking — `try await Task.sleep(for:)` for Thread.sleep/sleep, a checked continuation instead of a DispatchSemaphore or DispatchGroup wait, the async Process and URLSession APIs; never park a thread waiting on a Task — the cooperative pool cannot guarantee it progress; Give every client a whole-request bound: `reqwest::Client::builder().timeout(Duration::from_secs(10))` (never `reqwest::get` or `Client::new()`, which have none), ureq's `timeout_global`, or wrap the call in `tokio::time::timeout`; add retry with back-off (`reqwest-retry`'s `RetryTransientMiddleware`, `backoff`) around dependencies that fail; Document RTO/RPO and a tested restore procedure (a backup config alone isn't disaster recovery).

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

Do thisHelpsEffortDimension
Swift: await instead of blocking — `try await Task.sleep(for:)` for Thread.sleep/sleep, a checked continuation instead of a DispatchSemaphore or DispatchGroup wait, the async Process and URLSession APIs; never park a thread waiting on a Task — the cooperative pool cannot guarantee it progress.+4.2 ptsMediumAsync & latency hygiene
Resolve the 1 No ADRs found finding(s) in ADR Quality — start with project.pbxproj.+1.7 ptsLowADR Quality
Give every client a whole-request bound: `reqwest::Client::builder().timeout(Duration::from_secs(10))` (never `reqwest::get` or `Client::new()`, which have none), ureq's `timeout_global`, or wrap the call in `tokio::time::timeout`; add retry with back-off (`reqwest-retry`'s `RetryTransientMiddleware`, `backoff`) around dependencies that fail.+2.8 ptsMediumOutbound HTTP resilience
Document RTO/RPO and a tested restore procedure (a backup config alone isn't disaster recovery).+2.2 ptsMediumDR & Backup
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.+1.6 ptsMediumArchitecture documentation
Resolve the 2 `accountId` spells `Id` where 192 names in the project spell it `ID` finding(s) in Naming Consistency — start with QuotioCLIBackend.swift, QuotioCLIModels.swift.+0.4 ptsLowNaming Consistency
Resolve the 6 Skipped test finding(s) in Test Quality — start with AccountPersistenceTests.swift, AccountsScreenSnapshotTests.swift, CompanionScreenModelTests.swift.+0.7 ptsLowTest Quality
Swallowed exception (caught, then discarded)+1.2 ptsMediumException handling

File quality

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

FileScoreBandWorst signal
Packages/QuotioCore/Sources/QuotioInfrastructure/QuotioCLI/QuotioCLIBackend.swift4.3MixedCyclomatic Complexity: QuotioCLIBackend.historyRequest (cyclomatic 22)
REDACTED5.8MixedDependency Vulnerabilities: Medium vulnerability: REDACTED
Packages/QuotioCore/Sources/QuotioPresentation/Proxy/ProxyManagementScreenModel.swift6.3MixedGod Classes: TooManyMethods: ProxyManagementScreenModel
REDACTED6.9MixedDependency Vulnerabilities: Medium vulnerability: REDACTED
Packages/QuotioCore/Sources/QuotioApplication/Accounts/AuthFileRepository.swift7.0MixedCode Duplication: Edited copy of a member (15 corresponding lines)
apps/desktop/src/ui/menu.rs7.0MixedCyclomatic Complexity: quotio_desktop::ui::menu::burn_card (cyclomatic 21)
Packages/QuotioCore/Sources/QuotioApplication/Proxy/ProxyLifecycleController.swift7.0MixedCyclomatic Complexity: ProxyLifecycleController.install (cyclomatic 16)
apps/desktop/src/ui/settings/accounts.rs7.0MixedGod Classes: MethodTooLong: SettingsWindow.accounts_page
Packages/QuotioCore/Sources/QuotioPresentation/MenuBar/StatusBarMenuRenderer.swift7.0MixedCognitive Complexity: StatusBarMenuRenderer.buildMenu (cognitive 29)
Packages/QuotioCore/Sources/QuotioPresentation/Quota/QuotaHistoryScreenModel.swift7.1MixedCyclomatic Complexity: QuotaHistoryScreenModel.reload (cyclomatic 25)
apps/desktop/src/ui/settings/history.rs7.1MixedCyclomatic Complexity: QuotaHistory::plot (cyclomatic 16)
Packages/QuotioCore/Sources/QuotioInfrastructure/QuotioCLI/QuotioHostPresentationMapper.swift7.1MixedCyclomatic Complexity: QuotioHostPresentationMapper.resolvedSnapshot (cyclomatic 26)
Packages/QuotioHostClient/Sources/QuotioHostClient/QuotioHostHistory.swift7.1MixedCyclomatic Complexity: QuotioHostHistoryChart.validate (cyclomatic 25)
Packages/QuotioCore/Sources/QuotioPresentation/Quota/QuotaHistorySheet.swift7.1MixedCyclomatic Complexity: QuotaHistorySheet.timeline (cyclomatic 23)
apps/desktop/src/ui/settings/connect.rs7.1MixedGod Classes: ClassTooLong: ConnectFlow
apps/desktop/scripts/package.py7.2MixedCyclomatic Complexity: package.macos (cyclomatic 33)
apps/ios/QuotioWidgets/QuotioWidgets.swift7.2MixedCyclomatic Complexity: QuotaProvider.entry (cyclomatic 25)
REDACTED7.2MixedStatic Analysis (SAST): High: REDACTED
REDACTED7.2MixedStatic Analysis (SAST): High: REDACTED
Packages/QuotioCore/Sources/QuotioPresentation/Settings/AccountsSettingsScreen.swift7.4MixedCyclomatic Complexity: AccountsSettingsScreen.body (cyclomatic 31)

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

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

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

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

Could not be resolved — 25

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 50 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 — 50 dimensions across the health lenses
D1D2D3D4D5D6D10D12D13D14D15D17D19D20D21D26D27D28D29D30D32D34D35D36D43AX10AX3AX4AX5AX8AX9DM10DM12DM6DM9M1M2M3M4P1P10P2P3P4P5P6P7PF3X28X3

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, 340 of 355 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 01a1dc13-3099-7da4-b8a8-0231ad47e065.

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.

  • D8 Code Coverage — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Coverage NOT MEASURED: the JavaScript/TypeScript half measured 100.0% (node:test via `npm install --ignore-scripts` (no lockfile) in apps/cli/distribution/npm/); the Swift half could not be measured — the Swift suite in Packages/QuotioCore produced no coverage export. This repository's production source spans both ecosystems, and no partial figure is published as if it were the whole: coverage is excluded from the score rather than counted as a near-zero. This is OUR limitation, not a defect in the repo.
  • D10 Test Quality — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. The 473 test(s) behind this row are the ones the code-model census could read, and this repository also carries at least 15 test source file(s) (.rs, .cjs) that it cannot: it reads the test types the .swift frontend declared, so a suite in any other language is invisible to it. Skipped tests, zero-assertion tests and the other quality signals on this row are UNMEASURED in that suite — their absence from the counts above is a gap in this analyzer's language coverage, not a finding that those tests are sound.
  • D11 Test Reliability — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Test reliability NOT SCORED: this repository's production source includes .swift, and the swift executor ran against the .swift half and never executed — so reliability was not measured for the repository as a whole. The JavaScript/TypeScript (node:test via `npm install --ignore-scripts` (no lockfile) in apps/cli/distribution/npm/ (3 tests)): measured (0 flaky); Rust (apps/desktop, 79 test files): measured (0 flaky) suite(s) did re-run, and came back with 0 flaky across 2 measured tier(s) — but that is a figure for one half of the product, and we do not publish a partial one as if it were complete. This is OUR limitation, not a defect in the repo — test reliability is excluded from the score rather than counted. The half was driven by a runner we ship, so this is not a missing-runner gap.
  • D16 Bus Factor — not measured this run — This is a true statement about the repository that carries nothing for its owner to act on, so it is reported here rather than as a defect in their code. Single-maintainer repository — bus factor is not applicable (52 contributor(s) across 1184 commit(s) sampled, automation and bot accounts excluded). One of them holds 89% of the history; the other 51 hold 0.2% each on average, below the 5% at which there is somebody to hand the work to. That is a single maintainer with drive-by contributors, not a team whose knowledge has concentrated — so the bus factor is not applicable and there is nothing here for the owner to act on.
  • D19 Documentation Quality — measured, with a gap in what it reached — 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's deterministic call-shape rules are gated on C# first (docs/plans/deterministic-engine.md, P5): each other language is switched on only after its own concept suite and A/B gate pass. This says nothing about whether that surface is consistent.
  • D24 Comment Value — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Each source language's comment syntax, and the code a comment annotates in it, needs its own proof before D24 judges it. Until then those comments are left unread, not counted as clean.
  • D27 Navigability — 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. Tracing effort is measured over resolved call sites, and all 370 sampled here came from .swift files. This repository's .rs source is a material share of its production lines and contributed none, so the score above is a verdict about the part that was read. Not a finding that the unread half navigates well — it is unmeasured.
  • D32 Data Compliance (PII/GDPR) — 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. `Packages/QuotioCore/Sources/QuotioInfrastructure/Accounts/LocalProxyOAuthAuthorizer.swift`, `Packages/QuotioCore/Sources/QuotioInfrastructure/CustomProviders/CustomProviderAdapters.swift`, `Packages/QuotioCore/Sources/QuotioInfrastructure/HTTP/ProxyNetworkAdapters.swift`, `Packages/QuotioCore/Sources/QuotioInfrastructure/Platform/ProviderImageCacheAdapter.swift`, `Packages/QuotioCore/Sources/QuotioInfrastructure/Platform/SparkleApplicationUpdateAdapter.swift`, … (+42 more) produced a parse error, so every rule in this engine's `gdpr.yml` was absent there. That absence is NOT a clean result: these rules detect personal data crossing a boundary into a log sink, a URL or browser storage, and a file that was never parsed cannot report any of the three. The rest of the tree analysed normally and its rows above stand; only these files are unaccounted for. You can widen what we reach: fix the syntax error (or exclude the file deliberately) and re-scan to cover it.
  • D44 Platform End-of-Life — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This dimension reads a project's own statement about the platform it runs on: a TargetFramework in a .NET project file, a .nvmrc or .python-version, a capped requires-python, a Rust toolchain file or Cargo.toml rust-version, a .go-version, .java-version, .ruby-version, .tool-versions or .sdkmanrc, a go.mod go directive, a Maven or Gradle Java level or toolchain, a Gemfile's ruby directive, a mix.exs elixir requirement, a rebar.config minimum_otp_vsn, a pubspec.yaml SDK constraint, a build.sbt scalaVersion, or a framework major pinned by a dependency constraint. This repository carries none of them, so nothing about its platform was established. That is a gap in this analyzer's coverage, NOT a finding that the platform is supported — a language whose runtime is declared elsewhere (Package.swift, a Dockerfile) is simply not read here yet.
  • AX6 Interface segregation — 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 is computed over the public interfaces this run's compilations declare, and none was loaded, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
  • AXR1 Runtime accessibility — not measured this run — 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. User interface: a native UI project (apps/macos/Quotio.xcodeproj/project.pbxproj). Boot: the service booted and answers HTTP at http://127.0.0.1:6767, but serves no HTML page — nothing for the accessibility crawl.
  • C1 Data Protection — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These personal data controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks personal data controls.
  • C2 Access Controls — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These authorization controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks authorization controls.
  • C3 Audit Trail — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These audit controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks audit controls.
  • C4 Data Retention — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These retention controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks retention controls.
  • C5 Data-Subject Rights — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These data-subject rights controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks data-subject rights controls.
  • DM8 Value-object opportunities — 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 finds primitive parameters that travel together through several signatures of the domain (a missing value object). Its deterministic rule has not yet shown 95 % precision on adjudicated rows, so the clumps it finds are counted here and not published as findings, and the card carries no score. That is a limit of the analyzer, not a finding about your code.
  • DM9 Scattered domain decisions — 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. Arm two tells a construction that PRODUCES a measurement from one that merely passes it along, and this repository's frontend does not compute that fact. A measurement built independently in two places would not appear above.
  • DM9 Scattered domain decisions — 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. Some of this repository's production types come from a frontend that does not bind comparison operands to the members they read, which arm one needs, and those types were not walked for this dimension. The counts above speak for the languages that declare it.
  • GD1 Unfinished & placeholder code — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, F#, JavaScript/TypeScript, Dart, Ruby and Scala source only, and no C#, F#, JavaScript/TypeScript, Dart, Ruby or Scala was found, and this repository's Python, Rust, Swift is not read yet, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
  • IC1 Incompleteness & stubs — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, JavaScript/TypeScript, Java, Dart, Ruby and Scala source only, and no C#, JavaScript/TypeScript, Java, Dart, Ruby or Scala was found, and this repository's Python, Rust, Swift is not read yet, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
  • 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.
  • S1 Web-Security Posture — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These web-security controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks web-security controls.
  • X1 Async correctness — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check's reader does not cover most of the languages this repository's product is written in. What it read is kept, but it is too small a share to grade the product by. That is a gap in this analyzer's language reach — not a finding about this repository.
  • X12 Unreachable branch — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check's reader does not cover most of the languages this repository's product is written in. What it read is kept, but it is too small a share to grade the product by. That is a gap in this analyzer's language reach — not a finding about this repository.
  • X16 Unfloored truncation loop — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Java, PHP, Dart, Ruby, Scala and Kotlin source only, and no C# was loaded and no JavaScript/TypeScript, Java, PHP, Dart, Ruby, Scala or Kotlin 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.
  • X18 Disposal-pattern correctness — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Java, Kotlin, Dart, Ruby, Scala and PHP source only, and no C# was loaded and no JavaScript/TypeScript, Java, Kotlin, Dart, Ruby, Scala or PHP 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.
  • 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.
  • X21 Side-effecting pattern guard — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check's reader does not cover most of the languages this repository's product is written in. What it read is kept, but it is too small a share to grade the product by. That is a gap in this analyzer's language reach — not a finding about this repository.
  • X3 Exception handling — 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 check's reader does not cover every language in this repository. The score describes the part it read, which is most of the product; the rest is a gap in this analyzer's language reach.
  • X30 Support guard that admits what it rejects — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check's reader does not cover most of the languages this repository's product is written in. What it read is kept, but it is too small a share to grade the product by. That is a gap in this analyzer's language reach — not a finding about this repository.
  • X4 Structured logging — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check's reader does not cover most of the languages this repository's product is written in. What it read is kept, but it is too small a share to grade the product by. That is a gap in this analyzer's language reach — not a finding about this repository.
  • X5 Nullable reference types — 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 MSBuild project configuration, TypeScript source and its tsconfig files, Java source and its package and module declarations, PHP source and its PHPStan and Psalm configuration, Dart source and its pubspec language version, Ruby source and its Sorbet and Steep configuration, Scala source and its build's explicit-nulls, WartRemover and Scalafix settings, and Kotlin source only, and no C# was loaded, no TypeScript was found, and this repository's Python, Rust, Swift is not read yet, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.

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

Limitations & what we did not check

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

Per-dimension blind spots

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

  • D1 Cyclomatic Complexity: Cyclomatic complexity counts branches statically — it cannot tell an essential decision tree from accidental tangle, nor see complexity that lives in data or configuration (large switch-case token tables, DSL lexers/parsers, data-as-code rule tables) rather than control flow: a tokenizer's many single-character cases read as high complexity though each branch is trivial.
  • D2 Cognitive Complexity: Cognitive-complexity heuristics approximate how hard code is to follow; genuine domain difficulty and well-named intent that eases reading are not captured.
  • D3 God Classes: "God class" is sized by members and responsibilities visible in the type — a deliberately broad facade over a coherent subsystem can read the same as an accidental grab-bag. For front-end JS the file-length check is cohesion-aware (a single-responsibility module — one class/IIFE — earns a 3× threshold), but cohesion is approximated from top-level declarations, not true dependency structure.
  • D4 Code Duplication: Duplication is token-similarity — an in-process token-stream comparison over sliding windows, with type-aware normalization — so it finds copy-paste, not semantic duplication expressed differently. Committed machine-written code (scaffolded migrations, designer/codegen output, protobuf/OpenAPI stubs, model snapshots) is EXCLUDED — its repetition is the tool's, not the team's — so the score reflects hand-written duplication only.
  • D5 Coupling: Coupling is measured between projects/assemblies — runtime coupling through DI, reflection, messaging or shared databases is invisible to a static reference graph.
  • D6 Cohesion (LCOM4): LCOM4 cohesion is syntactic — it infers connectivity from which methods touch which fields/methods by name, not from real runtime behaviour or intent.
  • D10 Test Quality: Assertion density is structural — it cannot tell a meaningful behavioural assertion from a trivial one, only that an assertion is present.
  • D12 Dependency Hygiene: Dependency health reads manifests and lockfiles — a vulnerability in a vendored/copied dependency, or risk from how a dependency is actually used, is outside this view.
  • D13 Secret Scanning: Secret detection is signature- and entropy-based on the current tree — a secret that does not match a known pattern, or one already rotated, will not be flagged (a clean scan is "nothing matched", not "no secrets exist").
  • D14 License Compliance: License compatibility is checked against declared package metadata and a policy — mislabelled or missing license metadata, and obligations that depend on how you distribute, are not resolved here.
  • D15 Churn × Complexity Hotspots: Churn hotspots come from git history — a freshly imported or squashed repository has no churn signal, and recent rewrites can mask a historically risky file.
  • D17 Explicit Debt: Acknowledged-debt signals (TODO/FIXME, suppressions, dead code) are textual — undocumented debt that nobody marked, and debt that lives in design rather than annotations, is invisible. Committed machine-written code (scaffolded migrations, designer/codegen output, generated stubs) is excluded — it is never the team's dead code to delete.
  • D19 Documentation Quality: Documentation quality publishes two things only: a runnable or packaged unit with no example, and a multi-project root README that maps none of its parts. It does not judge clarity, and its other checks (overview, licence, boilerplate, structure, empty sections, XML-doc coverage) are withheld after adjudication: their candidates are counted in the card's gaps, not shown as rows. A false statement in a document is M4's; units are .NET projects only.
  • D20 ADR Quality: ADR quality checks the structure of the decision records present: it cannot know about decisions made and never recorded, and it does not judge how well a record argues its case. Records in a language the section lexicon does not cover are not evaluated.
  • D21 Naming Consistency: Naming consistency compares each name with the convention its structural peers follow in this repository: it cannot tell whether a consistently used name is a good one, and languages other than C# and TypeScript are not measured.
  • D26 Project Cohesion: Project focus is sized from members/namespaces per project — a project that is broad by deliberate design reads the same as one that has sprawled.
  • D27 Navigability: Indirection/navigability is structural — it measures hops to follow a call, not whether that indirection buys real flexibility or just ceremony.
  • D28 Secrets (history): Secret-history scanning sweeps the git log for known patterns — a secret that predates the available history, or never matched a signature, is not found (clean means "nothing matched in the history we can see").
  • D29 Static Analysis (SAST): SAST findings are pattern-based (semgrep) — it finds classes of bug it has rules for; logic flaws, auth/authorization gaps and issues needing runtime context are out of reach (and clean means "no rule matched").
  • D30 Dependency Vulnerabilities: CVE matching depends on accurate package/version metadata and on the advisory databases — a vulnerability with no published advisory, or in code not declared as a dependency, is not seen. Coverage needs a RESOLVED graph: an unpinned requirements.txt, or a pom without a resolved build, yields partial coverage rather than a clean verdict. An ecosystem the analyzer cannot scan is reported as unmeasured, never as clean.
  • D32 Data Compliance (PII/GDPR): PII/GDPR signals are heuristic pattern matches in code — they flag likely handling concerns, not legal compliance, and cannot trace where data actually flows at runtime.
  • D34 Knowledge Freshness: Freshness is decayed commit RECENCY, not comprehension — code read often but rarely committed reads as orphaned, and stable code that genuinely needs no changes is penalised the same as forgotten code; bot/squash commits distort it like the bus factor.
  • D35 Change Coupling: Change coupling is co-change in COMMITS — files split across separate commits, or coupled only through a shared config/build step, read as uncoupled, and a sweeping commit (rename/format) is excluded so it doesn't couple everything. It shows that files change together, not WHY: a high coupling can be a healthy cohesive pair as readily as a hidden leak.
  • D43 Malicious Dependencies: Only packages some vulnerability database has already NAMED as malicious are seen — a compromise published in the last hours, or never reported at all, is invisible here, and this dimension reading 10 is not evidence that a dependency is trustworthy. There is no typosquat or dependency-confusion analysis: a package nobody has reported is simply absent from the feeds. Coverage is the dependency scan's: an ecosystem that could not be scanned is disclosed as unmeasured, never as clean.
  • AX10 Code composition: Role is inferred from namespace/folder convention, not semantics — a domain concept living in a folder named "Services" reads as application, and the split is lines-of-code, not business value. The business-logic-share score is a SOFT, FLOORED signal: it contributes to the Architecture lens but is floored at the Critical gate, so an infrastructure-heavy design (a gateway, an ETL, a driver) is legitimately low without being nuked to zero.
  • AX9 CQS / query purity: Handlers are found by interface/name convention — a query handler using neither is not seen. Mutation is a resolved write/publish invocation (SaveChanges/repository/bus), so a write hidden behind a hand-rolled wrapper, reflection, or a string-keyed service locator resolves to a non-persistence type and isn't flagged; it detects that a query writes state, not whether the write is a legitimate read-side cache update. Clean means "no resolved write/publish in a query body", not a proof of CQS purity.
  • DM6 Domain ↔ infrastructure boundary: Infrastructure reached through a hand-rolled wrapper, a domain-named facade, reflection, or a string-keyed service locator resolves to a non-infra type and isn't seen; the body scan is symbol resolution over syntax, not full dataflow. A clean result means "no resolved infra reference in a domain body", not a proof of purity.
  • M4 Documentation accuracy: Documentation accuracy checks links, versions and artefact counts against the tree: other claims (paths, commands, settings, routes) are read but not checked, and it cannot run the onboarding or measure how long a real new joiner takes.
  • P4 Deployment & Rollback: Approval/branch-protection rules live in repository settings the scan cannot see — only their in-repo evidence (config files, workflows) is checked, so a control enforced purely in the host's settings reads as "not evidenced".
  • P5 DR & Backup: Backup/restore and disaster-recovery readiness is judged from in-repo evidence — a config that exists is not a tested restore, so the absence of positive evidence is reported as "not evidenced", never scored as present.
  • P6 Release Hygiene: Rollback/observability controls are inferred from repo artefacts (pipelines, dashboards-as-code) — controls configured in external tooling, with no in-repo trace, cannot be credited.

Dimensions

D1 · Cyclomatic Complexity6.8 / 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.8 / 10 · rule-coverage 100% · ceiling Prevented

35 method(s) exceeded the cyclomatic complexity threshold of 15; the worst was QuotioHostSnapshot.validate at 49. A further 11 method(s) were over the threshold but excluded as flat dispatchers (a long switch/match over independent cases: many branches, almost no nesting), the largest being HostError::fmt at 24 — they are counted neither in the figure above nor in this dimension's score. 7 files carry no cyclomatic complexity row at all for this reason — every one of their over-threshold methods was excluded, so the exclusion is disclosed nowhere in the file itself: apps/desktop/src/host.rs (HostError::fmt at 24), Packages/QuotioCore/Sources/QuotioInfrastructure/Accounts/LocalProxyOAuthAuthorizer.swift (LocalProxyOAuthAuthorizer.accountName at 19), Packages/QuotioCore/Sources/QuotioPresentation/Shared/ProviderPresentation.swift (QuotaProvider.displayName at 19), apps/desktop/src/providers.rs (quotio_desktop::providers::display_name at 19), Packages/QuotioCore/Sources/QuotioPresentation/Proxy/ProxyScreenModel.swift (ProxyScreenModel.message at 18), and 2 more not listed here. They are named here because the per-file figures other dimensions report are taken BEFORE this exclusion, so such a file can show a high maximum complexity elsewhere in this report and nothing here, with nothing to reconcile the two.

quotio_desktop::prefs::swift_preferences (cyclomatic 26) · ×3apps/desktop/src/prefs.rs:203
QuotioHostSnapshot.validate (cyclomatic 49)Packages/QuotioHostClient/Sources/QuotioHostClient/QuotioHostSnapshot.swift:130
package.macos (cyclomatic 33)apps/desktop/scripts/package.py:27
AccountsSettingsScreen.body (cyclomatic 31)Packages/QuotioCore/Sources/QuotioPresentation/Settings/AccountsSettingsScreen.swift:26
QuotioCLIServerProcess.start (cyclomatic 30)Packages/QuotioCore/Sources/QuotioInfrastructure/QuotioCLI/QuotioCLIServerProcess.swift:94

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

What to do

  1. Bring the 3 bodies over 30 down to 30 or less in Cyclomatic Complexity — start with QuotioHostSnapshot.validate (cyclomatic 49), package.macos (cyclomatic 33), AccountsSettingsScreen.body (cyclomatic 31). — 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 3 together lifts Cyclomatic Complexity from 6.8 to about 7.3/10, projected with the scoring formula itself and assuming each lands exactly at 30; a cleaner split scores higher.

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

D2 · Cognitive Complexity6.6 / 10Adequate✓ 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 6.6 / 10 · rule-coverage 100% · ceiling Prevented

54 method(s) exceeded the cognitive complexity threshold of 15; the worst was QuotioHostSnapshot.validate at 59.

quotio_desktop::prefs::swift_preferences (cognitive 32) · ×7apps/desktop/src/prefs.rs:203
QuotioHostSnapshot.validate (cognitive 59)Packages/QuotioHostClient/Sources/QuotioHostClient/QuotioHostSnapshot.swift:130
QuotaWidgetView.body (cognitive 57)apps/ios/QuotioWidgets/QuotioWidgets.swift:119
QuotaProvider.entry (cognitive 47)apps/ios/QuotioWidgets/QuotioWidgets.swift:61
package.macos (cognitive 45)apps/desktop/scripts/package.py:27

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

What to do

  1. Bring the 54 bodies over 15 down to 15 or less in Cognitive Complexity — start with QuotioHostSnapshot.validate (cognitive 59), QuotaWidgetView.body (cognitive 57), QuotaProvider.entry (cognitive 47). — This score is capped by its worst body, so a finding fixed alone moves it by almost nothing — the next one down takes its place. Refactoring these 54 together lifts Cognitive Complexity from 6.6 to about 10.0/10, projected with the scoring formula itself and assuming each lands exactly at 15.

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

D3 · God Classes8.8 / 10Strong✓ Tool-verified

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

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

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

41 god class(es) detected.

MethodTooLong: SettingsWindow.accounts_page · ×17apps/desktop/src/ui/settings/accounts.rs:59
FileTooLong: MenuBar/StatusBarMenuRenderer.swift · ×11Packages/QuotioCore/Sources/QuotioPresentation/MenuBar/StatusBarMenuRenderer.swift
TooManyMethods: QuotioCLIBackend · ×6Packages/QuotioCore/Sources/QuotioInfrastructure/QuotioCLI/QuotioCLIBackend.swift:7
FunctionTooLong: quotio_desktop::ui::menu::burn_card · ×4apps/desktop/src/ui/menu.rs:1070
ClassTooLong: ConnectFlow · ×3apps/desktop/src/ui/settings/connect.rs:84

What to do

  1. Resolve the 17 MethodTooLong finding(s) in God Classes — start with accounts.rs (2), menu_bar.rs (2), history.rs (2). — One of this dimension's main actionable groups (17 warning-level).
  2. Resolve the 11 FileTooLong finding(s) in God Classes — start with StatusBarMenuRenderer.swift, menu.rs, accounts.rs. — One of this dimension's main actionable groups (11 warning-level).
  3. Resolve the 6 TooManyMethods finding(s) in God Classes — start with QuotioCLIBackend.swift, mod.rs, ProxyLifecycleController.swift. — 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 Duplication9.3 / 10Stronggated by 74 serious findings✓ 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 9.3 / 10 · rule-coverage 100% · ceiling Verified

32 duplicated block group(s) detected. 1.6 % of the production lines (1,779 of 107,852) are in a reported copy. A further 44 rows report members as variants of one another; the share counts each copied line once, however many rows cite it.

Edited copy of a member (5 corresponding lines) · ×5Packages/QuotioCore/Sources/QuotioApplication/CustomProviders/CustomProviderService.swift:70
Edited copy of a member (7 corresponding lines) · ×4apps/ios/Sources/QuotioMobile/QuotaFormat.swift:42
Edited copy of a member (6 corresponding lines) · ×3Packages/QuotioCore/Sources/QuotioPresentation/MenuBar/StatusBarMenuRenderer.swift:1503
Edited copy of a member (10 corresponding lines) · ×3Packages/QuotioCore/Sources/QuotioApplication/Proxy/ProxyLifecycleController.swift:92
Duplicated block (9 lines × 2) · ×3Packages/QuotioCore/Sources/QuotioPresentation/Components/GLMAPIKeySheet.swift:98

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

What to do

  1. Resolve the 5 Edited copy of a member (5 corresponding lines) finding(s) in Code Duplication — start with CustomProviderService.swift, ExperimentalBadge.swift, AntigravityAccountSwitcher.swift. — One of this dimension's main actionable groups (5 warning-level).
  2. Resolve the 4 Edited copy of a member (7 corresponding lines) finding(s) in Code Duplication — start with QuotaFormat.swift, QuotioCompanionService.swift, QuotioHostHistory.swift. — One of this dimension's main actionable groups (4 warning-level).
  3. Resolve the 3 Edited copy of a member (6 corresponding lines) finding(s) in Code Duplication — start with StatusBarMenuRenderer.swift, CustomProviderModels.swift, AntigravitySwitchModels.swift. — One of this dimension's main actionable groups (3 warning-level).

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

D5 · Coupling8.7 / 10Strong✓ Tool-verified

What it measures: Whether volatile projects sit underneath others that depend on them (so their churn ripples upward), and whether project dependencies form cycles. A widely-depended-on but stable shared/kernel project is healthy, not penalised.

Method: Dependency cycles via elementary-DFS over real .csproj references, plus Martin instability (afferent/efferent) per project. Exhaustive over the reference graph, deterministic.

Coverage: Exhaustive · type-level: afferent/efferent coupling + cycles computed over every production type — the population is all types, not a name convention.

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

12 production modules (Cargo+npm+SwiftPM+Xcode), 0 dependency cycle(s), 0 unstable depended-on module(s). Read from the build's own module declarations; a workspace's implicit (product-name) dependency is not visible there; 2 module(s) off the main sequence, with abstractness counted on 8 of the 12 (the rest declare no modelled class or interface, export only macros, declare types in source no model reads, or have no source directory of their own).

Off the main sequence: QuotioDomain · ×2

What to do

  1. Resolve the 2 Off the main sequence finding(s) in Coupling. — One of this dimension's main actionable groups (2 warning-level).

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

D6 · Cohesion (LCOM4)9.6 / 10Stronggated by 3 serious findings✓ 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 9.6 / 10 · rule-coverage 100% · ceiling Verified

3 of 102 classes have LCOM4 above 3.

Low cohesion: QuotioCLIBackend (LCOM4 8) · ×3Packages/QuotioCore/Sources/QuotioInfrastructure/QuotioCLI/QuotioCLIBackend.swift:7

What to do

  1. Resolve the 3 Low cohesion finding(s) in Cohesion (LCOM4) — start with QuotioCLIBackend.swift, AuthFileRepository.swift, ProxyManagementScreenModel.swift. — One of this dimension's main actionable groups (3 warning-level).

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

D10 · Test Quality9.7 / 10Stronggated by 7 serious findings✓ Tool-verified

What it measures: Whether the tests truly assert behaviour rather than just running the code.

Method: Per-test assertions, skips, and mock references analyzed via Roslyn; structured skip-reason tags (BUG:/ENV:) separate documented deferrals from debt. Deterministic.

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

7 skipped (1 with a documented reason), 1 zero-assertion, no mocking-framework packages referenced (hand-written doubles or no mocking) across 473 tests. Measured on the .swift suite only — at least 15 test source file(s) (.rs, .cjs) went unread, so its test quality is unmeasured and is not in these counts.

Skipped test: testLegacyProtectedCredentialIsReadOnlyAndDoesNotResurrectAfterDeletion · ×6Packages/QuotioCore/Tests/QuotioInfrastructureTests/AccountPersistenceTests.swift:254
No assertions: testManualCompletionBelongsToCurrentAttemptPackages/QuotioCore/Tests/QuotioApplicationTests/OAuthFlowControllerTests.swift:79
Skipped (documented): liveRustTLSUsesPairedTrustWithAppTransportSecurityapps/ios/QuotioIOSUnitTests/HostStoreTests.swift:169

What to do

  1. Resolve the 6 Skipped test finding(s) in Test Quality — start with AccountPersistenceTests.swift, AccountsScreenSnapshotTests.swift, CompanionScreenModelTests.swift. — One of this dimension's main actionable groups (6 warning-level).
  2. Resolve the 1 No assertions finding(s) in Test Quality — start with OAuthFlowControllerTests.swift. — One of this dimension's main actionable groups (1 warning-level).

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

D12 · Dependency Hygiene9.9 / 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 9.9 / 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.

Outdated: sparkle

✓ On the Gold path — maintain.

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

D13 · Secret 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

Secret scan ran and found no leaked secrets. 1 detection(s) in paths this repository declares as reviewed specimen content (its credential-scanner allowlist) were excluded.

✓ 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 284 shipped crate(s) use a banned license. Licences were resolved from crates.io over the crates a consumer compiles — this repository's REDACTED closed over its manifests' `[dependencies]` and `[build-dependencies]`. Crates it asks for ONLY under `[dev-dependencies]` are excluded: they are not compiled by anything that depends on this repository. This repository publishes itself under MIT, which is its own choice and is not judged here.

✓ On the Gold path — maintain.

Detailed fixes: d14_recommendation.md.

D15 · Churn × Complexity Hotspots9.3 / 10Stronggated by 52 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: apps/cli/src/accounts/service.rs (79×26=2054); apps/cli/src/server.rs (75×27=2025); apps/cli/src/accounts/mod.rs (66×29=1914) Repeated repair below the complexity floor: apps/cli/src/accounts/oauth.rs (12 of 19 changes were fixes); apps/cli/src/accounts/authorization.rs (9 of 10 changes were fixes); apps/cli/src/providers/catalog/oauth_cloud.rs (4 of 7 changes were fixes)

Hotspot: apps/cli/src/accounts/service.rs · ×44apps/cli/src/accounts/service.rs:786
Repeated repair: apps/cli/src/accounts/oauth.rs · ×8apps/cli/src/accounts/oauth.rs:705

What to do

  1. Resolve the 44 Hotspot finding(s) in Churn × Complexity Hotspots — start with main.rs (2), service.rs, server.rs. — One of this dimension's main actionable groups (44 warning-level).
  2. Resolve the 8 Repeated repair finding(s) in Churn × Complexity Hotspots — start with oauth.rs, authorization.rs, oauth_cloud.rs. — One of this dimension's main actionable groups (8 warning-level).

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

D17 · Explicit Debt10.0 / 10Exemplary○ Nothing flagged

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

0 deducted task-comment markers across 107852 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.

✓ On the Gold path — maintain.

Detailed fixes: d17_recommendation.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. 16 document(s) read across 2 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 foundapps/macos/Quotio.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.0 / 10Adequate✓ 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.0 / 10 · rule-coverage 100% · ceiling Verified

5 naming inconsistencies among 166 declarations measured against a convention their peers follow.

`accountId` spells `Id` where 192 names in the project spell it `ID` · ×2Packages/QuotioCore/Sources/QuotioInfrastructure/QuotioCLI/QuotioCLIBackend.swift:11
`requestId` spells `Id` where 192 names in the project spell it `ID`Packages/QuotioCore/Sources/QuotioApplication/Warmup/ProxyWarmupExecutor.swift:96
`sessionId` spells `Id` where 192 names in the project spell it `ID`Packages/QuotioCore/Sources/QuotioApplication/Warmup/ProxyWarmupExecutor.swift:103
`tierId` spells `Id` where 192 names in the project spell it `ID`Packages/QuotioCore/Sources/QuotioDomain/Quota/QuotaModels.swift:378

What to do

  1. Resolve the 2 `accountId` spells `Id` where 192 names in the project spell it `ID` finding(s) in Naming Consistency — start with QuotioCLIBackend.swift, QuotioCLIModels.swift. — One of this dimension's main actionable groups (2 recommendation-level).
  2. Resolve the 1 `requestId` spells `Id` where 192 names in the project spell it `ID` finding(s) in Naming Consistency — start with ProxyWarmupExecutor.swift. — One of this dimension's main actionable groups (1 recommendation-level).
  3. Resolve the 1 `sessionId` spells `Id` where 192 names in the project spell it `ID` finding(s) in Naming Consistency — start with ProxyWarmupExecutor.swift. — One of this dimension's main actionable groups (1 recommendation-level).

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

D26 · Project Cohesion6.7 / 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 6.7 / 10 · rule-coverage 100% · ceiling Documented

1 of 6 build units (Cargo, SwiftPM, Xcode) flagged as possibly oversized/incoherent.

Projects may be oversized for their cohesion

What to do

  1. Resolve the 1 Projects may be oversized for their cohesion finding(s) in Project Cohesion. — One of this dimension's main actionable groups (1 recommendation-level).

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

D27 · Navigability8.1 / 10Strong✓ Tool-verified

What it measures: How far you must trace to follow a call — low indirection and co-located slices read easier.

Method: Call indirection (interface hops, cross-namespace calls, slice-locality scaled) over a sampled set of method invocations, size-aware baseline. Sampled; confidence discounted by symbol-resolution gaps. C# also names each pass-through layer (a class whose every public method only forwards its own parameters to one collaborator) as a located finding; the score is not affected.

Coverage: Slice locality from the first namespace segments, SAMPLED (≤400 methods) — not exhaustive.

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

1 % of calls cross a namespace and 38 % go through an interface, but 100 % of collaborators are co-located — so following a call takes several hops. Baseline: small — navigation cost is tolerated. Measured over the .swift source only — this repository's .rs was not sampled for call sites, so this score covers part of the tree, not all of it.

High interface indirection

What to do

  1. Resolve the 1 High interface indirection finding(s) in Navigability. — One of this dimension's main actionable groups (1 recommendation-level).

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

D28 · Secrets (history)10.0 / 10Exemplary○ Nothing flagged

What it measures: Whether any secrets were ever committed — scanned across the full git history, not just now.

Method: Secret scan via TWO gitleaks detect passes in an isolated checkout — the full git history, then a second --no-git pass over the working tree as it stands — merged and de-duplicated by (rule, file, line); each match flagged High. Both invocations are recorded in the audit trail. Exhaustive; when the tool is absent, or when its output cannot be parsed into the expected shape, the dimension is WITHHELD as an explicit measurement gap on our side — unscored and excluded from the lens, never a hedged middling score.

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

gitleaks scanned the full history AND the current working tree and found no secrets. 7 detection(s) in paths this repository declares as reviewed specimen content (its credential-scanner allowlist) were excluded.

✓ On the Gold path — maintain.

Detailed fixes: d28_recommendation.md.

D29 · Static Analysis (SAST)7.1 / 10Adequategated by 2 critical findings✓ 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 7.1 / 10 · rule-coverage 100% · ceiling Documented

2 finding(s): 0 critical, 2 high, 0 medium, 0 low. semgrep hit a parse error in 13 file(s) — `Packages/QuotioCore/Sources/QuotioInfrastructure/CustomProviders/CustomProviderAdapters.swift`, `Packages/QuotioCore/Sources/QuotioInfrastructure/HTTP/ProxyNetworkAdapters.swift` (line 195, line 204, line 209, …), `Packages/QuotioCore/Sources/QuotioInfrastructure/Proxy/URLSessionProxyManagementAPI.swift` (line 142, line 143, line 144, …), `apps/cli/scripts/sign-macos.sh` (line 48), `apps/cli/src/accounts/sources.rs` (line 1221, lines 1237–1238, lines 1245–1968, …), … (+8 more) — so no absence of findings in the named regions is evidence of anything; rows reported elsewhere in those files are real. Fix the syntax error (or exclude the file deliberately) and re-scan to cover them. Separately, one or more rules could not re-parse an embedded snippet in 1 file(s) (e.g. a workflow `run:` block read as shell). Those files WERE scanned and their other rows are unaffected; only those rules' view of those snippets is missing.

REDACTED

What to do

  1. Resolve the 2 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED, REDACTED. — One of this dimension's main actionable groups (2 issue-level).

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

D30 · Dependency Vulnerabilities7.6 / 10Strong✓ Tool-verified

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 7.6 / 10 · rule-coverage 100% · ceiling Documented

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

REDACTED
REDACTED
REDACTED
REDACTED

What to do

  1. Resolve the 9 Medium advisory (unmaintained) finding(s) in Dependency Vulnerabilities — start with REDACTED (9). — One of this dimension's main actionable groups (9 warning-level).
  2. Resolve the 2 Medium CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (2). — One of this dimension's main actionable groups (2 warning-level).
  3. Resolve the 2 Medium vulnerability finding(s) in Dependency Vulnerabilities — start with REDACTED (2). — One of this dimension's main actionable groups (2 warning-level).

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

D32 · Data Compliance (PII/GDPR)9.0 / 10Stronggated by 1 serious finding✓ Tool-verified

What it measures: Likely personal-data (PII / GDPR) handling concerns — logging or storing data without safeguards.

Method: Heuristic PII/GDPR LEAK scan via semgrep across the repo, using our own ruleset: personal data crossing a boundary it should not — reaching a log/console sink, a URL or query string, or unprotected browser storage. Matches map to severity and a 0-10 wide normalizer. A clean sweep is unscored rather than an unearned 10, and is a statement about the leak paths checked only — this dimension does not inventory the personal data a repository holds (the personal-data map and the C1-C5 compliance cards do that), so it never reports that a repository has no personal-data surface. Reported LOUDLY as a measurement gap if the ruleset is missing from the analyzer image. Exhaustive over the leak paths, advisory-leaning; degrades on parse failure.

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

1 finding(s): 0 critical, 0 high, 1 medium, 0 low. semgrep could not parse 47 file(s) — `Packages/QuotioCore/Sources/QuotioInfrastructure/Accounts/LocalProxyOAuthAuthorizer.swift`, `Packages/QuotioCore/Sources/QuotioInfrastructure/CustomProviders/CustomProviderAdapters.swift`, `Packages/QuotioCore/Sources/QuotioInfrastructure/HTTP/ProxyNetworkAdapters.swift`, `Packages/QuotioCore/Sources/QuotioInfrastructure/Platform/ProviderImageCacheAdapter.swift`, `Packages/QuotioCore/Sources/QuotioInfrastructure/Platform/SparkleApplicationUpdateAdapter.swift`, … (+42 more) — so the PII/GDPR sweep did not cover the unparsed regions of them; rows reported elsewhere in those files are real.

REDACTED

What to do

  1. Resolve the 1 REDACTED finding(s) in Data Compliance (PII/GDPR) — start with REDACTED. — One of this dimension's main actionable groups (1 warning-level).

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

D34 · Knowledge Freshness10.0 / 10Exemplary✓ 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 10.0 / 10 · rule-coverage 100% · ceiling Documented

Every significant source file has living knowledge — recently and meaningfully worked. Counted over 281 of the 386 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.

✓ On the Gold path — maintain.

Detailed fixes: d34_recommendation.md.

D35 · Change Coupling9.8 / 10Adequategated by 1 critical finding✓ 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.8 / 10 · rule-coverage 100% · ceiling Documented

Strongest change-coupling: QuotioCLIBackend.swift↔AccountsScreenModel.swift 71%; QuotioCLIBackend.swift↔QuotioCLIServerProcess.swift 62%; QuotioCLIBackend.swift↔QuotaFeatureController.swift 50%

Boundary-crossing change coupling: RootNavigationView.swift ↔ CompositionRoot.swiftPackages/QuotioCore/Sources/QuotioPresentation/App/RootNavigationView.swift:1
Change coupling: QuotaPorts.swift ↔ QuotioCLIModels.swift · ×2Packages/QuotioCore/Sources/QuotioApplication/Quota/QuotaPorts.swift:1
Change-coupling hub: QuotioCLIBackend.swift → QuotioCLIServerProcess.swift, AccountsScreenModel.swift, QuotaFeatureController.swiftPackages/QuotioCore/Sources/QuotioInfrastructure/QuotioCLI/QuotioCLIBackend.swift

What to do

  1. Resolve the 1 Boundary-crossing change coupling finding(s) in Change Coupling — start with RootNavigationView.swift. — One of this dimension's main actionable groups (1 issue-level).
  2. Resolve the 2 Change coupling finding(s) in Change Coupling — start with QuotaPorts.swift, config.rs. — One of this dimension's main actionable groups (2 warning-level).
  3. Resolve the 1 Change-coupling hub finding(s) in Change Coupling — start with QuotioCLIBackend.swift. — One of this dimension's main actionable groups (1 warning-level).

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

D36 · Supply-chain Provenance & Signing7.5 / 10Strong✓ Tool-verified

What it measures: Whether the build pipeline provides supply-chain integrity — generated provenance/attestation, signed artifacts (cosign/sigstore), an SBOM, and pinned build actions. Presence of the configuration, not a runtime guarantee.

Method: Supply-chain provenance/signing read deterministically from CI/build config (.github/workflows, .gitlab-ci.yml, azure-pipelines, Jenkinsfile, .circleci) + the release surface: four signals — generated provenance/attestation (SLSA/in-toto/actions-attest), artifact signing (cosign/sigstore/gitsign), an SBOM (syft/sbom-action/*.spdx.json/*.cdx.json), and SHA-pinned build actions — scored 10·present/denom. NotApplicable without a build pipeline. Detects configuration presence, not runtime enforcement.

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

3/4 supply-chain integrity signals present (provenance, signing, SBOM, pinned actions).

REDACTED
REDACTED
REDACTED

What to do

  1. Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 warning-level).
  2. Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 recommendation-level).
  3. Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 recommendation-level).

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

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.

Frontend & cross-cutting dimensions

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

AX10 · Code composition9.4 / 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.

AX4 · Dependency direction10.0 / 10Exemplary✓ Tool-verified

Other · Architecture — Whether dependencies point inward (Domain ← Application ← Infrastructure/Web) — the clean-architecture dependency rule, checked across the project graph.

Method: Layer violations by name-segment inference (Domain/Core to Application to Infrastructure/Web) over the project-reference graph. Exhaustive over all projects, deterministic.

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.

AX8 · Test isolation10.0 / 10Exemplary✓ Tool-verified

Other · Architecture — Whether production projects stay free of references to test projects — tests may depend on production, never the reverse.

Method: Csproj graph: each production project checked for references to test projects (identified by test-framework presence, not name). Zero violations is clean. Deterministic.

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.

DM10 · One transaction, one aggregate10.0 / 10Exemplary○ Nothing flagged

Other · Domain Modelling — Whether a single operation mutates more than one aggregate root. An aggregate is a consistency boundary, so saving two together fuses them into one — the second's invariants come to depend on the first's transaction, and the pair can no longer be separated. Reads of other aggregates are not counted.

Method: Neutral body surface (DDD-gated): every method body scanned for repository WRITE calls (Add/Update/Save/Remove/Delete/Insert/Store and their async forms), keyed on the ARGUMENT type rather than the repository type — three `IRepository<T>` writes collapse to one repository but are three distinct aggregates. Reads (Get/Find/Load/Query) are excluded, so loading another aggregate for context never counts. Score is offending methods over methods that write at all. Deterministic.

DM12 · Ambient inputs in the domain10.0 / 10Exemplary○ Nothing flagged

Other · Domain Modelling — Whether domain types receive the time and randomness their rules depend on, rather than reading the process clock or a global random source directly — an ambient read makes the rule it feeds untestable at the instant that matters and lets two reads inside one operation disagree.

Method: Roslyn (DDD-gated, C#/VB only): domain-layer types scanned for ambient reads — DateTime/DateTimeOffset.Now/UtcNow/Today, Random.Shared, new Random(), Stopwatch.GetTimestamp — resolved against the semantic model, with a comment/string-stripped token fallback only where resolution fails. Body reads are scored; field/property initialisers are surfaced unscored. Apply/When folds excluded (ES1 owns them). Deterministic, symbol-resolved.

DM6 · Domain ↔ infrastructure boundary10.0 / 10Exemplary✓ Tool-verified

Other · Domain Modelling — Whether the domain layer stays free of infrastructure dependencies (EF/Marten/HTTP/ASP.NET) — the clean-architecture dependency rule.

Method: Roslyn (DDD-gated): domain-layer types scanned for infrastructure usage in member SIGNATURES and inside method/accessor BODIES — resolved calls and object-creations into EF/Marten/HTTP/Mongo/Redis/message-bus types (not just a namespace allowlist). Deterministic, symbol-resolved, exhaustive over domain-layer bodies, DDD-native.

Coverage: Domain layer identified by NAMESPACE heuristic; infrastructure then resolved by symbol in member SIGNATURES and method/accessor BODIES — rename the layer and the check evaporates.

DM9 · Scattered domain decisions10.0 / 10Exemplary✓ Tool-verified

Other · Domain Modelling — Whether one domain rule is decided — or one measurement produced — in more than one place, rather than living on the type that owns it.

Method: Neutral body surface plus Roslyn (DDD-gated), two arms. DECISION (Roslyn only): a predicate over a domain type's members judged in two or more types, where none of those decisions live on the owning type — operands of comparisons and relational property patterns only, so a member merely passed as an argument is not judged. DERIVATION: a plain all-numeric carrier of ≥2 members, with no base type and exactly one constructor, CONSTRUCTED as the result of a method (returned or assigned, never inline as an argument) in two or more types other than its own — the same measurement produced twice, which centralising the judgement does not fix. DERIVATION runs on every language whose frontend declares the produced-or-passed fact per construction (Roslyn and the Java sidecar today); a target with only the derivation arm carries an engine gap naming the decision arm as not assessed, and a frontend that declares nothing keeps the dimension not measured rather than clean. Single-member rules, test code and generated code are out of population for both. Advisory.

M1 · Documentation (README)8.7 / 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 accuracy10.0 / 10Exemplary○ Nothing flagged

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.

P1 · CI/CD gates10.0 / 10Exemplary○ Nothing flagged

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.

P10 · Library API & versioning10.0 / 10Exemplary○ Nothing flagged

Readiness · Readiness — For a library: a deliberate (small) public API surface and explicit semantic versioning so consumers can depend on it safely.

Method: Roslyn scan: public API surface area and semantic-versioning markers (SemVer attributes, changelog entries) for libraries; off .NET, a library is the ecosystem's publication act (an npm package that is not private and names an entry point, a PyPI distribution with a build system, a Rust library crate, a Maven/Gradle module that publishes, a Go module with no package main, a gemspec, a Composer library, a SwiftPM library product, a pub.dev or Hex package), its surface is the share of types the language's code model records as public (Rust, Swift, Java, Kotlin, Go, Dart; not measured where the model records no type visibility or, as in TypeScript, only module-level export), and its version is read from the manifest, a semver CHANGELOG, release tooling or semver git tags. Exhaustive, deterministic.

P2 · Observability7.0 / 10Strong✓ 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.

  • Only 4/6 runnable modules use logging (modules with no entry point or server are excluded — they are libraries a runnable module hosts). Silent: `.`, `apps/ios`.

What to do

  • Extend structured logging to the remaining runnable modules so everything you run is diagnosable in production.
P3 · Security & performance tooling7.0 / 10Strong✓ 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.

What to do

  • Enable Dependabot/Renovate or a dependency-review gate.
P4 · Deployment & Rollback7.0 / 10Strong✓ Tool-verified

Readiness · Readiness — Whether releases are automated and safely reversible (probes, rolling updates, approval gates) — from manifests/pipeline files, not the live environment.

Method: Filesystem scan: deployment manifests/IaC (K8s YAML, Helm, Terraform) for rolling updates, probes, approval gates, migration hooks. Exhaustive, deterministic.

P5 · DR & Backup4.0 / 10Weak✓ Tool-verified

Readiness · Readiness — Whether disaster recovery is planned and codified — backups, geo-recovery, RTO/RPO, persistence guarantees — from IaC + container manifests + docs, never the live cloud.

Method: Filesystem scan: disaster recovery, backup, geo-recovery, RTO/RPO, persistence guarantees from IaC, manifests, and docs. Exhaustive, deterministic, never a live environment.

What to do

  • Document RTO/RPO and a tested restore procedure (a backup config alone isn't disaster recovery).
P6 · Release Hygiene10.0 / 10Exemplary✓ 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.

P7 · Outbound HTTP resilience3.0 / 10Weak✓ Tool-verified

Readiness · Readiness — Whether outbound HTTP calls are wrapped in resilience (retry/timeout/circuit-breaker) so a failing dependency doesn't cascade.

Method: Source scan: outbound HTTP clients and what bounds them — resilience handlers (Polly, AddStandardResilienceHandler) on .NET; on Go, the JVM, Python, JavaScript/TypeScript, Ruby, PHP, Rust, Elixir, Swift, Dart and Erlang, a timeout, deadline, retry or breaker beside each call, or a process-wide client default (a framework-wide deadline such as Drupal core's, Laravel's or actix's awc counts). Exhaustive, deterministic.

  • `reqwest::Client::builder(` makes an outbound HTTP call, and nothing bounds it: no timeout, deadline, retry or circuit breaker is set for it here, and the client has no process-wide default. A slow or failing dependency will hold this service's request, thread or connection until the call gives up on its own — or never, for a client with no default timeout. (×2) — apps/cli/src/usage.rs:146, apps/desktop/src/updater.rs:106

What to do

  • Give every client a whole-request bound: `reqwest::Client::builder().timeout(Duration::from_secs(10))` (never `reqwest::get` or `Client::new()`, which have none), ureq's `timeout_global`, or wrap the call in `tokio::time::timeout`; add retry with back-off (`reqwest-retry`'s `RetryTransientMiddleware`, `backoff`) around dependencies that fail.
PF3 · Async & latency hygiene6.0 / 10Adequate✓ 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.

  • `killHelpers` is async and calls .waitUntilExit() — a blocking call inside async code stalls the cooperative pool's thread — one per core — and every task scheduled on it for as long as it runs. — Packages/QuotioCore/Sources/QuotioInfrastructure/Antigravity/AntigravitySystemAdapters.swift:91
  • `sleep` is async and calls sleep — a blocking call inside async code stalls the cooperative pool's thread — one per core — and every task scheduled on it for as long as it runs. — Packages/QuotioCore/Sources/QuotioInfrastructure/Lifecycle/ContinuousSleeper.swift:6
  • `killProcesses` is async and calls .waitUntilExit() — a blocking call inside async code stalls the cooperative pool's thread — one per core — and every task scheduled on it for as long as it runs. — Packages/QuotioCore/Sources/QuotioInfrastructure/Process/ProxyProcessController.swift:154

What to do

  • Swift: await instead of blocking — `try await Task.sleep(for:)` for Thread.sleep/sleep, a checked continuation instead of a DispatchSemaphore or DispatchGroup wait, the async Process and URLSession APIs; never park a thread waiting on a Task — the cooperative pool cannot guarantee it progress.
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 handling5.0 / 10Adequate✓ 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` 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. (×32) — apps/macos/Quotio/App/AppRuntime.swift:200, apps/ios/QuotioWidgets/QuotioWidgets.swift:90, apps/ios/QuotioIOS/RootView.swift:39, …

What to do

  • Swallowed exception (caught, then discarded)

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 Health72%StrongSolid.
Architecture94%ExemplarySolid.
Maturity70%Adequate — gated by M2Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Readiness60%Adequate — gated by P7Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Security84%Checked 4 of 11Solid.
Domain Modelling100%ExemplaryStrongest area.
Performance60%AdequateAcceptable, with room to improve.
Unscored — 3 check(s) recorded observations but carry no score

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

  • AXO1 Runtime API surface — 5 observation(s) recorded · Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
  • X10 Duplicated predicate — 3 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
  • X7 Silent fallback defaults — 5 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
Not evidenced — 3 control(s) we could not find positive evidence for

These checks grade a working control, and the repository shows no evidence of one. That is deliberately not scored as a zero: a repository cannot show an ops runbook, a database TTL or an infrastructure-side audit log, so absence of evidence here is not evidence the control is missing. It is also not a statement that the check is irrelevant to this codebase — the thing it grades applies; we just could not see it. Excluded from the score either way.

  • C3 Audit Trail — Not assessed: these audit controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks audit controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
  • C4 Data Retention — Not assessed: these retention controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks retention controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
  • C5 Data-Subject Rights — Not assessed: these data-subject rights controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks data-subject rights controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
Not included — 75 check(s) not relevant to this codebase

These checks had nothing to measure here (no tests, no git history, the codebase is small, or the architecture style doesn't apply), so they're omitted above rather than scored low.

  • AC1 Text alternatives — No web markup found — accessibility is not applicable to this repository.
  • AC2 Forms & labels — No web markup found — accessibility is not applicable to this repository.
  • AC3 Page structure — No web markup found — accessibility is not applicable to this repository.
  • AC4 Keyboard semantics — No web markup found — accessibility is not applicable to this repository.
  • AC5 ARIA correctness — No web markup found — accessibility is not applicable to this repository.
  • AC6 Visual & motion safety — No web markup found — accessibility is not applicable to this repository.
  • AX1 Captive dependencies — Not applicable: Rust with no dependency-injection crate has no container to hand one lifetime's instance to another — every value is owned by the code that builds it, and the borrow checker rejects a longer-lived value keeping a borrow of a shorter-lived one; this repository's Swift imports no dependency-injection container and defines no container of its own — nothing that both registers and resolves bindings, and nothing that names two lifetimes — so nothing holds one lifetime's instance while handing out another's.
  • AX2 Stateful singletons — No container singleton was found, so there is no shared instance for concurrent requests to race on. No function in this Python code is served by a threaded web framework (a Flask, Bottle or FastAPI route, a Django or Pyramid view), so no module is shared between request threads. No Swift request handler (a Vapor, Hummingbird, Kitura, Swifter or Perfect route handler, as a method or a registered closure) is declared, so no state is shared between request threads. Rust's compiler refuses unsynchronised shared mutation — a value shared across threads must be Sync — so the race this check looks for cannot be written.
  • AX6 Interface segregation — not assessed — interface segregation is computed over a type surface that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
  • AX7 Slice cohesion — not applicable — not a vertical-slice architecture
  • AXB2 Runtime readiness — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
  • AXR1 Runtime accessibility — The runtime tier booted this repository's service, but the service booted and answers HTTP at http://127.0.0.1:6767, but serves no HTML page — nothing for the accessibility crawl. This repository also has a user interface (a native UI project (apps/macos/Quotio.xcodeproj/project.pbxproj)) that the booted service does not serve, and this scan has no strategy that reaches it — so no WCAG success criterion was verified in a rendered page on this run. That is a gap in OUR tooling, not a finding about your application: nothing here says the interface is inaccessible. The static accessibility checks still ran.
  • AXS1 Runtime exposed surface — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
  • C1 Data Protection — Not assessed: these personal data controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks personal data controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
  • C2 Access Controls — Not assessed: these authorization controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks authorization controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
  • D11 Test Reliability — Test reliability not scored — polyglot repository, one half's runner produced no measurement
  • D16 Bus Factor — single-maintainer repository — bus factor is not applicable
  • D18 Solution Shape — D18 scores the shape of a .NET solution; this repository has no .NET solution or project files, so the dimension does not apply.
  • D22 Internal API Consistency — API consistency is measured on C# only; the exposed Rust, Swift surface was not measured.
  • D23 Boundary Type-Coupling — No bounded-context organisation was detected either — neither a context-shaped layout, nor 2+ sibling source directories each declaring an aggregate root, nor 2+ sibling projects each declaring an entity of their own or taking another project's integration events. Declaring this codebase's bounded contexts (≥2) would let cross-boundary type coupling be assessed. Declare them in `.codehealth/config.yaml` at the repository root (create it if absent), mapping each context name to the module-path or namespace prefixes that belong to it — e.g. `architecture:` → `contexts:` → `Billing: ["src/billing", "Acme.Billing"]`, `Catalog: ["src/catalog", "Acme.Catalog"]`.
  • D24 Comment Value — D24 reads C#, Visual Basic, TypeScript and JavaScript comments only; comments in this repository's .py, .rs, .swift source were not judged.
  • D25 ADR Conformance — no ADRs to check
  • D31 IaC & Container Security — No Infrastructure-as-Code or container manifests found (Dockerfile, Docker Compose, Terraform, Kubernetes/Helm, CloudFormation, ARM, Bicep, Ansible); nothing to scan.
  • D37 Vulnerability-disclosure Policy — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed.
  • D40 Network Egress Confinement — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here.
  • D41 Kernel & Syscall Confinement — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here.
  • D42 Runtime Threat Enforcement — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here.
  • D44 Platform End-of-Life — Platform end-of-life not assessed — this repository declares no platform this pass reads
  • D7 Architectural Integrity — no checkable ADRs, and no project-reference graph for the cycle pass to read — so this dimension makes no claim about dependency cycles in either direction (where this repository's language has an import-cycle lens, cycles are reported there). Architectural integrity not assessed
  • D8 Code Coverage — Coverage not measured — Swift suite
  • DM1 Aggregate boundaries — no aggregates detected — aggregate-boundary check not applicable
  • DM11 Constructible invalid state — no entities detected — construction-time invariants not assessable
  • DM2 Strongly-typed ids — no id-bearing domain types detected — strongly-typed-id adoption not assessable
  • DM3 Integration-event coupling — no integration events detected — coupling check not applicable
  • DM4 Rich vs anemic model — no data-bearing entities detected — rich-vs-anemic model not assessable
  • DM5 Encapsulated state — no domain entities found — DM5 grades how entities protect their state, and this repository declares none
  • DM7 Repository granularity — no repository abstraction detected (e.g. uses a document session)
  • DM8 Value-object opportunities — not scored — the deterministic rule found 0 candidate clump(s); its rows are withheld until it has a measured precision of 95 % (a sample of fewer than 10 rows cannot show one)
  • ED2 Event/command shape — not scored — deciding whether a command has more than one competing handler requires resolving the call graph, and this analysis resolves a call's owner only where the receiver's type is written down in the source. Reported as guidance rather than measured
  • ED2 Event/command shape — not scored — deciding whether a command has more than one competing handler requires resolving the call graph, and a call made through an inferred or generic receiver has no resolvable owner in the source. Reported as guidance rather than measured
  • ED5 Idempotency — no mutating command handlers or message consumers detected — idempotency check not applicable
  • ES1 Event Sourcing — not scored — this repository shows none of the 3 signals this lens looks for
  • GD1 Unfinished & placeholder code — no source files were read — this check reads C#, F#, JavaScript/TypeScript, Dart, Ruby and Scala, and none was read for this repository's product. That is a limit of the analyzer, not a finding about your code.
  • IC1 Incompleteness & stubs — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
  • P12 CI test-gate honesty — Reported, not scored — and nothing was matched here. The coverage check applies to any stack, and the automatic-re-run check to any GitHub-Actions workflow, but the checks for excluded tests, skipped tests and sleep-based synchronisation currently recognise only some ecosystems' test-runner idioms, so on a repository built with another stack the zeros below mean 'not checked', not 'clean'.
  • 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 `#[bench]`, criterion's `bench_function`/`bench_with_input`, `#[divan::bench]` or `#[library_benchmark]` in any `.rs` file, or criterion, divan, iai or a `[[bench]]` target in a Cargo.toml, 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 — Not assessed: these web-security controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks web-security controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
  • X1 Async correctness — X1 reached only 31% of this repository's production lines — swift (32,735 lines) was left unread. Not scored: a score over a minority of the product would be published as the whole of it.
  • X12 Unreachable branch — X12 reached only 0% of this repository's production lines — swift (32,735 lines), rust (14,509 lines) was left unread. Not scored: a score over a minority of the product would be published as the whole of it.
  • X13 Undrained process stream — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
  • 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
  • X16 Unfloored truncation loop — 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
  • X17 Uncapped recursion over a caller-supplied document — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
  • X18 Disposal-pattern correctness — not 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
  • X19 Unrestored process-global state — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
  • X2 Cancellation propagation — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
  • X20 Mistyped argument guard — This check asks whether an argument guard reports an EMPTY value as a NULL one, which needs a language that throws a null-specific argument exception — .NET's ArgumentNullException, the JVM's NullPointerException, Dart's ArgumentError.notNull. This repository contains none of those languages: the ones it is written in have a single exception for a bad argument, so there is no pair of exceptions to confuse and nothing here for it to assess. Not a gap in the analyzer and not a finding about your code.
  • X21 Side-effecting pattern guard — X21 reached only 31% of this repository's production lines — swift (32,735 lines) was left unread. Not scored: a score over a minority of the product would be published as the whole of it.
  • X22 Contradicted release guard — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
  • X23 Unguarded diagnostic materialisation — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
  • X24 Document value interpolated into markup unescaped — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
  • X25 Inert configuration knob — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
  • 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
  • X27 Collection changed while being enumerated — 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
  • X30 Support guard that admits what it rejects — X30 reached only 31% of this repository's production lines — swift (32,735 lines) was left unread. Not scored: a score over a minority of the product would be published as the whole of it.
  • 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 — X4 reached only 31% of this repository's production lines — swift (32,735 lines) was left unread. Not scored: a score over a minority of the product would be published as the whole of it.
  • X5 Nullable reference types — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
  • X6 Hand-rolled structured-format parsing — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
  • 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 — 3 finding(s)
D29 · Static Analysis (SAST) · REDACTED
  • REDACTED
  • REDACTED
D35 · Change Coupling · Boundary-crossing change coupling · ×1
  • Boundary-crossing change coupling: RootNavigationView.swift ↔ CompositionRoot.swift Packages/QuotioCore/Sources/QuotioPresentation/App/RootNavigationView.swift:1 — `Packages/QuotioCore/Sources/QuotioPresentation/App/RootNavigationView.swift` (context QuotioCore) and `apps/macos/Quotio/App/CompositionRoot.swift` (context macos) sit in DIFFERENT parts of the tree yet change together 50% of the time (7 of the 14 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) — the bounded-context boundary may be in the wrong place, or one context is leaking into the other. This is the behavioural boundary violation a static scan can't see. You can check this without leaving the row: of the 7 shared commits counted here, the most recent 3 are `2bd21cce` fix(macos): restore cliproxyapi management and lifecycle; `8e434313` refactor(macos): remove retired services from the production graph; `fa16a824` refactor(macos): render account and quota state from host snapshots — run `git show` on any of them.
Serious — 330 finding(s)
D15 · Churn × Complexity Hotspots · Hotspot · ×44
  • Hotspot: apps/cli/src/accounts/service.rs apps/cli/src/accounts/service.rs:786 — apps/cli/src/accounts/service.rs changed 79 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 26 in ManagedProvider::read at line 786. 40 of those changes were fix/bug commits, so the churn is repair rather than feature work. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-08-13..2026-11-11, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-13 02:09:55 +00:00' --until='2026-11-11 02:09:55 +00:00' --full-history --no-merges -- apps/cli/src/accounts/service.rs`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
  • Hotspot: apps/cli/src/server.rs apps/cli/src/server.rs:1193 — apps/cli/src/server.rs changed 75 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 27 in quotio::server::serve at line 1193. 36 of those changes were fix/bug commits, and the other 39 changed it for other reasons — this file is under both repair and feature pressure. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-08-13..2026-11-11, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-13 02:09:55 +00:00' --until='2026-11-11 02:09:55 +00:00' --full-history --no-merges -- apps/cli/src/server.rs`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
  • Hotspot: apps/cli/src/accounts/mod.rs apps/cli/src/accounts/mod.rs:773 — apps/cli/src/accounts/mod.rs changed 66 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 29 in Document::absorb at line 773. 21 of those changes were fix/bug commits, and the other 45 changed it for other reasons — this file is under both repair and feature pressure. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-08-13..2026-11-11, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-13 02:09:55 +00:00' --until='2026-11-11 02:09:55 +00:00' --full-history --no-merges -- apps/cli/src/accounts/mod.rs`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
  • Hotspot: apps/cli/src/accounts/vault.rs apps/cli/src/accounts/vault.rs:391 — apps/cli/src/accounts/vault.rs changed 54 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 30 in Vault::begin at line 391. 17 of those changes were fix/bug commits, and the other 37 changed it for other reasons — this file is under both repair and feature pressure. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-08-13..2026-11-11, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-13 02:09:55 +00:00' --until='2026-11-11 02:09:55 +00:00' --full-history --no-merges -- apps/cli/src/accounts/vault.rs`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
  • Hotspot: Packages/QuotioCore/Sources/QuotioInfrastructure/QuotioCLI/QuotioCLIBackend.swift Packages/QuotioCore/Sources/QuotioInfrastructure/QuotioCLI/QuotioCLIBackend.swift:68 — Packages/QuotioCore/Sources/QuotioInfrastructure/QuotioCLI/QuotioCLIBackend.swift changed 69 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 22 in QuotioCLIBackend.historyRequest at line 68. 42 of those changes were fix/bug commits, so the churn is repair rather than feature work. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-08-13..2026-11-11, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-13 02:09:55 +00:00' --until='2026-11-11 02:09:55 +00:00' --full-history --no-merges -- Packages/QuotioCore/Sources/QuotioInfrastructure/QuotioCLI/QuotioCLIBackend.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: apps/cli/src/providers/capabilities.rs apps/cli/src/providers/capabilities.rs:189 — apps/cli/src/providers/capabilities.rs changed 34 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 40 in quotio::providers::capabilities::capability at line 189. 4 of those changes were fix/bug commits, and the other 30 changed it for other reasons — this file is under both repair and feature pressure. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-08-13..2026-11-11, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-13 02:09:55 +00:00' --until='2026-11-11 02:09:55 +00:00' --full-history --no-merges -- apps/cli/src/providers/capabilities.rs`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
  • Hotspot: apps/cli/src/server/management.rs apps/cli/src/server/management.rs:337 — apps/cli/src/server/management.rs changed 47 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 27 in quotio::server::management::mutate at line 337. 18 of those changes were fix/bug commits, and the other 29 changed it for other reasons — this file is under both repair and feature pressure. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-08-13..2026-11-11, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-13 02:09:55 +00:00' --until='2026-11-11 02:09:55 +00:00' --full-history --no-merges -- apps/cli/src/server/management.rs`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
  • Hotspot: apps/cli/src/accounts/api.rs apps/cli/src/accounts/api.rs:534 — apps/cli/src/accounts/api.rs changed 46 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 27 in quotio::accounts::api::prepare_source at line 534. 13 of those changes were fix/bug commits, and the other 33 changed it for other reasons — this file is under both repair and feature pressure. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-08-13..2026-11-11, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-13 02:09:55 +00:00' --until='2026-11-11 02:09:55 +00:00' --full-history --no-merges -- apps/cli/src/accounts/api.rs`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
  • Hotspot: apps/cli/src/main.rs apps/cli/src/main.rs:113 — apps/cli/src/main.rs changed 30 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 34 in quotio::run at line 113. 4 of those changes were fix/bug commits, and the other 26 changed it for other reasons — this file is under both repair and feature pressure. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-08-13..2026-11-11, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-13 02:09:55 +00:00' --until='2026-11-11 02:09:55 +00:00' --full-history --no-merges -- apps/cli/src/main.rs`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
  • Hotspot: apps/cli/src/accounts/discovery.rs apps/cli/src/accounts/discovery.rs:173 — apps/cli/src/accounts/discovery.rs changed 22 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 43 in Registry::inspect_for at line 173. 14 of those changes were fix/bug commits, so the churn is repair rather than feature work. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-08-13..2026-11-11, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-13 02:09:55 +00:00' --until='2026-11-11 02:09:55 +00:00' --full-history --no-merges -- apps/cli/src/accounts/discovery.rs`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
  • Hotspot: apps/cli/src/providers/amp.rs apps/cli/src/providers/amp.rs:206 — apps/cli/src/providers/amp.rs changed 28 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 28 in quotio::providers::amp::parse at line 206. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-08-13..2026-11-11, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-13 02:09:55 +00:00' --until='2026-11-11 02:09:55 +00:00' --full-history --no-merges -- apps/cli/src/providers/amp.rs`: 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:909 — REDACTED changed 26 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 26 in quotio::providers::catalog::oauth_editors::open_cursor_database_at_with_hooks at line 909. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-08-13..2026-11-11, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-13 02:09:55 +00:00' --until='2026-11-11 02:09:55 +00: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: apps/cli/src/accounts/command.rs apps/cli/src/accounts/command.rs:74 — apps/cli/src/accounts/command.rs changed 17 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 36 in quotio::accounts::command::run_with_vault 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 2026-08-13..2026-11-11, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-13 02:09:55 +00:00' --until='2026-11-11 02:09:55 +00:00' --full-history --no-merges -- apps/cli/src/accounts/command.rs`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
  • Hotspot: apps/cli/src/providers/antigravity.rs apps/cli/src/providers/antigravity.rs:347 — apps/cli/src/providers/antigravity.rs changed 29 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 18 in AntigravityProvider::fetch_with_token at line 347. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-08-13..2026-11-11, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-13 02:09:55 +00:00' --until='2026-11-11 02:09:55 +00:00' --full-history --no-merges -- apps/cli/src/providers/antigravity.rs`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
  • Hotspot: Packages/QuotioCore/Sources/QuotioInfrastructure/QuotioCLI/QuotioCLIServerProcess.swift Packages/QuotioCore/Sources/QuotioInfrastructure/QuotioCLI/QuotioCLIServerProcess.swift:94 — Packages/QuotioCore/Sources/QuotioInfrastructure/QuotioCLI/QuotioCLIServerProcess.swift changed 16 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 30 in QuotioCLIServerProcess.start at line 94. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-08-13..2026-11-11, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-13 02:09:55 +00:00' --until='2026-11-11 02:09:55 +00:00' --full-history --no-merges -- Packages/QuotioCore/Sources/QuotioInfrastructure/QuotioCLI/QuotioCLIServerProcess.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: apps/cli/src/accounts/resolved.rs apps/cli/src/accounts/resolved.rs:653 — apps/cli/src/accounts/resolved.rs changed 18 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 26 in Registry::validate at line 653. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-08-13..2026-11-11, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-13 02:09:55 +00:00' --until='2026-11-11 02:09:55 +00:00' --full-history --no-merges -- apps/cli/src/accounts/resolved.rs`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
  • Hotspot: apps/cli/src/cache.rs apps/cli/src/cache.rs:196 — apps/cli/src/cache.rs changed 14 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 33 in UsageCache::one at line 196. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-08-13..2026-11-11, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-13 02:09:55 +00:00' --until='2026-11-11 02:09:55 +00:00' --full-history --no-merges -- apps/cli/src/cache.rs`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
  • Hotspot: apps/cli/src/providers/key_api.rs apps/cli/src/providers/key_api.rs:267 — apps/cli/src/providers/key_api.rs changed 19 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 22 in quotio::providers::key_api::zai at line 267. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-08-13..2026-11-11, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-13 02:09:55 +00:00' --until='2026-11-11 02:09:55 +00:00' --full-history --no-merges -- apps/cli/src/providers/key_api.rs`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
  • Hotspot: apps/cli/src/providers/codex.rs apps/cli/src/providers/codex.rs:90 — apps/cli/src/providers/codex.rs changed 23 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 18 in quotio::providers::codex::parse at line 90. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-08-13..2026-11-11, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-13 02:09:55 +00:00' --until='2026-11-11 02:09:55 +00:00' --full-history --no-merges -- apps/cli/src/providers/codex.rs`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
  • Hotspot: Packages/QuotioHostClient/Sources/QuotioHostClient/QuotioHostSnapshot.swift Packages/QuotioHostClient/Sources/QuotioHostClient/QuotioHostSnapshot.swift:130 — Packages/QuotioHostClient/Sources/QuotioHostClient/QuotioHostSnapshot.swift changed 8 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 49 in QuotioHostSnapshot.validate at line 130. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-08-13..2026-11-11, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-13 02:09:55 +00:00' --until='2026-11-11 02:09:55 +00:00' --full-history --no-merges -- Packages/QuotioHostClient/Sources/QuotioHostClient/QuotioHostSnapshot.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: apps/cli/src/providers/catalog/oauth_primary.rs apps/cli/src/providers/catalog/oauth_primary.rs:434 — apps/cli/src/providers/catalog/oauth_primary.rs changed 20 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 16 in quotio::providers::catalog::oauth_primary::claude_windows at line 434. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-08-13..2026-11-11, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-13 02:09:55 +00:00' --until='2026-11-11 02:09:55 +00:00' --full-history --no-merges -- apps/cli/src/providers/catalog/oauth_primary.rs`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
  • Hotspot: apps/cli/src/contract/snapshot.rs apps/cli/src/contract/snapshot.rs:496 — apps/cli/src/contract/snapshot.rs changed 18 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 17 in quotio::contract::snapshot::project at line 496. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-08-13..2026-11-11, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-13 02:09:55 +00:00' --until='2026-11-11 02:09:55 +00:00' --full-history --no-merges -- apps/cli/src/contract/snapshot.rs`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
  • Hotspot: Packages/QuotioCore/Sources/QuotioPresentation/MenuBar/StatusBarManager.swift Packages/QuotioCore/Sources/QuotioPresentation/MenuBar/StatusBarManager.swift:90 — Packages/QuotioCore/Sources/QuotioPresentation/MenuBar/StatusBarManager.swift changed 18 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 16 in StatusBarManager.renderStatusBar at line 90. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-08-13..2026-11-11, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-13 02:09:55 +00:00' --until='2026-11-11 02:09:55 +00:00' --full-history --no-merges -- Packages/QuotioCore/Sources/QuotioPresentation/MenuBar/StatusBarManager.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: apps/cli/src/contract.rs apps/cli/src/contract.rs:210 — apps/cli/src/contract.rs changed 11 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 25 in Snapshot::validate at line 210. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-08-13..2026-11-11, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-13 02:09:55 +00:00' --until='2026-11-11 02:09:55 +00:00' --full-history --no-merges -- apps/cli/src/contract.rs`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
  • Hotspot: Packages/QuotioCore/Sources/QuotioPresentation/MenuBar/StatusBarMenuSnapshot.swift Packages/QuotioCore/Sources/QuotioPresentation/MenuBar/StatusBarMenuSnapshot.swift:141 — Packages/QuotioCore/Sources/QuotioPresentation/MenuBar/StatusBarMenuSnapshot.swift changed 15 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 17 in StatusBarMenuSnapshotMapper.makeSnapshot at line 141. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-08-13..2026-11-11, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-13 02:09:55 +00:00' --until='2026-11-11 02:09:55 +00:00' --full-history --no-merges -- Packages/QuotioCore/Sources/QuotioPresentation/MenuBar/StatusBarMenuSnapshot.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.
  • + 19 more in this group — see findings.md.
X3 · Exception handling · Swallowed exception (caught, then discarded) · ×32
  • Swallowed exception (caught, then discarded) apps/macos/Quotio/App/AppRuntime.swift:200 — `catch` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter.
  • Swallowed exception (caught, then discarded) apps/ios/QuotioWidgets/QuotioWidgets.swift:90 — `catch` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter.
  • Swallowed exception (caught, then discarded) apps/ios/QuotioIOS/RootView.swift:39 — `catch` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter.
  • Swallowed exception (caught, then discarded) Packages/QuotioCore/Sources/QuotioPresentation/Settings/AccountSettingsRow.swift:200 — `catch` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter.
  • Swallowed exception (caught, then discarded) Packages/QuotioCore/Sources/QuotioPresentation/Settings/AccountStorageAccessSection.swift:67 — `catch` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter.
  • Swallowed exception (caught, then discarded) Packages/QuotioCore/Sources/QuotioPresentation/Settings/AccountsSettingsScreen.swift:133 — `catch` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter.
  • Swallowed exception (caught, then discarded) Packages/QuotioCore/Sources/QuotioPresentation/Settings/AccountsSettingsScreen.swift:149 — `catch` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter.
  • Swallowed exception (caught, then discarded) Packages/QuotioCore/Sources/QuotioPresentation/Settings/AccountsSettingsScreen.swift:170 — `catch` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter.
  • Swallowed exception (caught, then discarded) Packages/QuotioCore/Sources/QuotioPresentation/Settings/AccountsSettingsScreenModel.swift:53 — `catch` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter.
  • Swallowed exception (caught, then discarded) Packages/QuotioCore/Sources/QuotioPresentation/Settings/CompanionPairingView.swift:61 — `catch` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter.
  • Swallowed exception (caught, then discarded) Packages/QuotioCore/Sources/QuotioPresentation/Settings/LocalAccountConnectionSheet.swift:132 — `catch` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter.
  • Swallowed exception (caught, then discarded) Packages/QuotioCore/Sources/QuotioPresentation/Settings/LoginSourceMenu.swift:25 — `catch` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter.
  • Swallowed exception (caught, then discarded) Packages/QuotioCore/Sources/QuotioPresentation/Settings/NativePermissionSheet.swift:38 — `catch` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter.
  • Swallowed exception (caught, then discarded) Packages/QuotioCore/Sources/QuotioPresentation/Quota/QuotaFeatureController.swift:190 — `catch` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter.
  • Swallowed exception (caught, then discarded) Packages/QuotioCore/Sources/QuotioPresentation/Logs/LogsScreenModel.swift:41 — `catch` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter.
  • Swallowed exception (caught, then discarded) Packages/QuotioCore/Sources/QuotioInfrastructure/Updates/GitHubAtomProxyUpdateFeed.swift:71 — `catch` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter.
  • Swallowed exception (caught, then discarded) Packages/QuotioCore/Sources/QuotioInfrastructure/Tunnel/CloudflaredService.swift:136 — `catch` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter.
  • Swallowed exception (caught, then discarded) Packages/QuotioCore/Sources/QuotioInfrastructure/QuotioCLI/QuotioCLILegacyAccountMigration.swift:65 — `catch` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter.
  • Swallowed exception (caught, then discarded) Packages/QuotioCore/Sources/QuotioInfrastructure/QuotioCLI/QuotioCLILegacyAccountMigration.swift:91 — `catch` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter.
  • Swallowed exception (caught, then discarded) Packages/QuotioCore/Sources/QuotioInfrastructure/Process/ProxyProcessController.swift:173 — `catch` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter.
  • Swallowed exception (caught, then discarded) Packages/QuotioCore/Sources/QuotioInfrastructure/Platform/UserNotificationCenterAdapter.swift:28 — `catch` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter.
  • Swallowed exception (caught, then discarded) Packages/QuotioCore/Sources/QuotioInfrastructure/HTTP/ProxyNetworkAdapters.swift:344 — `catch` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter.
  • Swallowed exception (caught, then discarded) Packages/QuotioCore/Sources/QuotioInfrastructure/Credentials/YubiKeySecretVault.swift:82 — `catch` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter.
  • Swallowed exception (caught, then discarded) Packages/QuotioCore/Sources/QuotioInfrastructure/Accounts/FileAntigravityAuthWorkaround.swift:47 — `catch` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter.
  • Swallowed exception (caught, then discarded) Packages/QuotioCore/Sources/QuotioInfrastructure/Accounts/LocalProxyOAuthAuthorizer.swift:137 — `catch` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter.
  • + 7 more in this group — see findings.md.
D3 · God Classes · MethodTooLong · ×17
  • MethodTooLong: SettingsWindow.accounts_page apps/desktop/src/ui/settings/accounts.rs:59 — MethodTooLong — accounts_page runs 267 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 167 over it, 2.67× 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: SettingsWindow.menu_bar_page apps/desktop/src/ui/settings/menu_bar.rs:26 — MethodTooLong — menu_bar_page runs 215 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 115 over it, 2.15× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
  • MethodTooLong: CompositionRoot.makeProduction apps/macos/Quotio/App/CompositionRoot.swift:16 — MethodTooLong — makeProduction runs 195 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 95 over it, 1.95× 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: SettingsWindow.proxy_server apps/desktop/src/ui/settings/cli_proxy.rs:63 — MethodTooLong — proxy_server runs 160 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) 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: SettingsWindow.account_row apps/desktop/src/ui/settings/accounts.rs:604 — MethodTooLong — account_row runs 152 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 52 over it, 1.52× 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: SettingsWindow.general_page apps/desktop/src/ui/settings/general.rs:34 — MethodTooLong — general_page runs 138 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) 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: QuotaHistory.plot apps/desktop/src/ui/settings/history.rs:400 — MethodTooLong — plot runs 130 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 30 over it, 1.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: AccountRow.body Packages/QuotioCore/Sources/QuotioPresentation/Components/AccountRow.swift:214 — MethodTooLong — body runs 125 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 25 over it, 1.25× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
  • MethodTooLong: OAuthStatusView.body Packages/QuotioCore/Sources/QuotioPresentation/Components/OAuthSheet.swift:168 — MethodTooLong — body runs 122 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 22 over it, 1.22× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
  • MethodTooLong: AccountPanel.render apps/desktop/src/ui/panel.rs:111 — MethodTooLong — render runs 120 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 20 over it, 1.20× 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: AccountsSettingsScreen.body Packages/QuotioCore/Sources/QuotioPresentation/Settings/AccountsSettingsScreen.swift:26 — MethodTooLong — body runs 119 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 19 over it, 1.19× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
  • MethodTooLong: ConnectFlow.browser_view apps/desktop/src/ui/settings/connect.rs:1015 — MethodTooLong — browser_view runs 119 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 19 over it, 1.19× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
  • MethodTooLong: SettingsWindow.about_page apps/desktop/src/ui/settings/about.rs:26 — MethodTooLong — about_page runs 118 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 18 over it, 1.18× 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: QuotaHistory.summary apps/desktop/src/ui/settings/history.rs:259 — MethodTooLong — summary runs 114 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 14 over it, 1.14× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
  • MethodTooLong: QuotioCLIServerProcess.start Packages/QuotioCore/Sources/QuotioInfrastructure/QuotioCLI/QuotioCLIServerProcess.swift:94 — MethodTooLong — start runs 111 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 11 over it, 1.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: SettingsWindow.style_options apps/desktop/src/ui/settings/menu_bar.rs:533 — MethodTooLong — style_options runs 111 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 11 over it, 1.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: SettingsWindow.privacy_page apps/desktop/src/ui/settings/privacy.rs:20 — MethodTooLong — privacy_page runs 101 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 1 over it, 1.01× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
D3 · God Classes · FileTooLong · ×11
  • FileTooLong: MenuBar/StatusBarMenuRenderer.swift Packages/QuotioCore/Sources/QuotioPresentation/MenuBar/StatusBarMenuRenderer.swift — FileTooLong — 1272 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 772 over it, 2.54× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
  • FileTooLong: ui/menu.rs apps/desktop/src/ui/menu.rs — FileTooLong — 1170 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted). The bar is 500 significant lines; this is 670 over it, 2.34× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
  • FileTooLong: settings/accounts.rs apps/desktop/src/ui/settings/accounts.rs — FileTooLong — 1104 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), about 91% of them inside a single declaration: SettingsWindow (58-1339). The bar is 500 significant lines; this is 604 over it, 2.21× 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: settings/connect.rs apps/desktop/src/ui/settings/connect.rs — FileTooLong — 1094 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), about 83% of them inside a single declaration: ConnectFlow (3 blocks, 84-1276). The bar is 500 significant lines; this is 594 over it, 2.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: QuotioCLI/QuotioCLIBackend.swift Packages/QuotioCore/Sources/QuotioInfrastructure/QuotioCLI/QuotioCLIBackend.swift — FileTooLong — 772 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 272 over it, 1.54× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
  • FileTooLong: Proxy/ProxyLifecycleController.swift Packages/QuotioCore/Sources/QuotioApplication/Proxy/ProxyLifecycleController.swift — FileTooLong — 713 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 213 over it, 1.43× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
  • FileTooLong: src/proxy.rs apps/desktop/src/proxy.rs — FileTooLong — 606 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), declaring 35 free functions. The bar is 500 significant lines; this is 106 over it, 1.21× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
  • FileTooLong: settings/menu_bar.rs apps/desktop/src/ui/settings/menu_bar.rs — FileTooLong — 600 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), about 92% of them inside a single declaration: SettingsWindow (25-711). The bar is 500 significant lines; this is 100 over it, 1.20× 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: settings/iphone.rs apps/desktop/src/ui/settings/iphone.rs — FileTooLong — 589 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted). The bar is 500 significant lines; this is 89 over it, 1.18× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
  • FileTooLong: settings/history.rs apps/desktop/src/ui/settings/history.rs — FileTooLong — 567 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), about 88% of them inside a single declaration: QuotaHistory (3 blocks, 45-670). The bar is 500 significant lines; this is 67 over it, 1.13× 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: Quota/QuotaHistorySheet.swift Packages/QuotioCore/Sources/QuotioPresentation/Quota/QuotaHistorySheet.swift — FileTooLong — 505 significant lines (blank, comment-only and punctuation-only lines excluded), about 99% of them inside a single declaration: QuotaHistorySheet (5-671). The bar is 500 significant lines; this is 5 over it, 1.01× 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.
D30 · Dependency Vulnerabilities · Medium advisory (unmaintained) · ×9
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
D15 · Churn × Complexity Hotspots · Repeated repair · ×8
  • Repeated repair: apps/cli/src/accounts/oauth.rs apps/cli/src/accounts/oauth.rs:705 — apps/cli/src/accounts/oauth.rs changed 19 times in last 90 days and 12 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 15 (its worst body is OAuthSessionManager::poll_device at line 705), AT OR UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “fix(accounts): tell a newer or corrupt account store apart from denied Keychain access (#553)”; “fix(auth): enforce revocation and host-local approval boundaries”; “fix(auth): isolate OAuth sessions and begin claims by client”; “fix(oauth): recover session begins with idempotency keys”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-08-13..2026-11-11, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-13 02:09:55 +00:00' --until='2026-11-11 02:09:55 +00:00' --full-history --no-merges -- apps/cli/src/accounts/oauth.rs`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
  • Repeated repair: apps/cli/src/accounts/authorization.rs apps/cli/src/accounts/authorization.rs:74 — apps/cli/src/accounts/authorization.rs changed 10 times in last 90 days and 9 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 8 (its worst body is quotio::accounts::authorization::authorize at line 74), AT OR UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “fix(cli): read gh, Cursor and Factory logins through the security tool”; “fix(cli): read Claude Code logins through the security tool”; “fix(antigravity): refresh native and proxy quota credentials”; “fix(factory): resolve omitted selectors before native authorization”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-08-13..2026-11-11, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-13 02:09:55 +00:00' --until='2026-11-11 02:09:55 +00:00' --full-history --no-merges -- apps/cli/src/accounts/authorization.rs`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
  • Repeated repair: apps/cli/src/providers/catalog/oauth_cloud.rs apps/cli/src/providers/catalog/oauth_cloud.rs:211 — apps/cli/src/providers/catalog/oauth_cloud.rs changed 7 times in last 90 days and 4 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 10 (its worst body is quotio::providers::catalog::oauth_cloud::native_file at line 211), AT OR UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “fix(antigravity): refresh native and proxy quota credentials”; “fix(kiro): validate complete profile ARNs before owned intake”; “fix(accounts): retain refresh lineage after concurrent removal”; “fix(kiro): prohibit borrowed refresh and stabilize machine identity”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-08-13..2026-11-11, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-13 02:09:55 +00:00' --until='2026-11-11 02:09:55 +00:00' --full-history --no-merges -- apps/cli/src/providers/catalog/oauth_cloud.rs`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
  • Repeated repair: Packages/QuotioCore/Sources/QuotioPresentation/Settings/ProviderAccountsSection.swift Packages/QuotioCore/Sources/QuotioPresentation/Settings/ProviderAccountsSection.swift:45 — Packages/QuotioCore/Sources/QuotioPresentation/Settings/ProviderAccountsSection.swift changed 6 times in last 90 days and 4 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 10 (its worst body is ProviderAccountsSection.header at line 45), AT OR UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “fix(settings): keep a paused provider's menu visible and show full issue text”; “fix(macos): show provider issues inside their provider card”; “fix(macos): hide empty provider cards and repeated provider names in attention rows”; “fix(macos): show loading feedback for refresh actions”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-08-13..2026-11-11, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-13 02:09:55 +00:00' --until='2026-11-11 02:09:55 +00:00' --full-history --no-merges -- Packages/QuotioCore/Sources/QuotioPresentation/Settings/ProviderAccountsSection.swift`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
  • Repeated repair: REDACTED REDACTED:267 — REDACTED changed 6 times in last 90 days and 4 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 11 (its worst body is Session::refresh_at at line 267), AT OR UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “fix(antigravity): refresh native and proxy quota credentials”; “fix(antigravity): read unified oauth state and report expired logins”; “fix(cli): stabilize helper signing and suppress background keychain prompts”; “fix(antigravity): validate native protobuf credential structure”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-08-13..2026-11-11, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-13 02:09:55 +00:00' --until='2026-11-11 02:09:55 +00:00' --full-history --no-merges -- REDACTED`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
  • Repeated repair: apps/cli/src/accounts/oauth/claude.rs apps/cli/src/accounts/oauth/claude.rs:38 — apps/cli/src/accounts/oauth/claude.rs changed 5 times in last 90 days and 4 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 5 (its worst body is quotio::accounts::oauth::claude::manual_code at line 38), AT OR UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “fix(cli): keep timeout classification for unsent Claude refreshes”; “fix(cli): release Claude refresh fence before waiting out a 429”; “fix(cli): release Claude refresh fence when the token was never used”; “fix(auth): persist Claude exchange before quota collection”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-08-13..2026-11-11, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-13 02:09:55 +00:00' --until='2026-11-11 02:09:55 +00:00' --full-history --no-merges -- apps/cli/src/accounts/oauth/claude.rs`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
  • Repeated repair: apps/cli/src/accounts/adopt.rs apps/cli/src/accounts/adopt.rs:75 — apps/cli/src/accounts/adopt.rs changed 4 times in last 90 days and 4 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 13 (its worst body is quotio::accounts::adopt::vault at line 75), AT OR UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “fix(accounts): preserve logical IDs and receipts during adoption”; “fix(cli): ask for Keychain access when adopting a former app vault”; “fix(cli): stop re-importing native preferences once adoption is done”; “fix(cli): defer the adoption marker until the former config is seeded”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-08-13..2026-11-11, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-13 02:09:55 +00:00' --until='2026-11-11 02:09:55 +00:00' --full-history --no-merges -- apps/cli/src/accounts/adopt.rs`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
  • Repeated repair: apps/cli/src/providers/catalog/devin_desktop.rs apps/cli/src/providers/catalog/devin_desktop.rs:179 — apps/cli/src/providers/catalog/devin_desktop.rs changed 5 times in last 90 days and 3 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 11 (its worst body is quotio::providers::catalog::devin_desktop::parse_usage at line 179), AT OR UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “fix(devin): expose percent consumption for progress metrics”; “fix(devin): merge native sessions by user and show account email”; “fix(auth): reject unsafe Devin native credential destinations”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-08-13..2026-11-11, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-13 02:09:55 +00:00' --until='2026-11-11 02:09:55 +00:00' --full-history --no-merges -- apps/cli/src/providers/catalog/devin_desktop.rs`: 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.
D2 · Cognitive Complexity · quotio_desktop · ×7
  • quotio_desktop::prefs::swift_preferences (cognitive 32) apps/desktop/src/prefs.rs:203 — quotio_desktop::prefs::swift_preferences has cognitive complexity 32 (threshold 15). Drivers by points: match/switch 9 (14 pts), if/else 8 (12 pts), loops 2 (5 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.
  • quotio_desktop::ui::menu::burn_card (cognitive 32) apps/desktop/src/ui/menu.rs:1070 — quotio_desktop::ui::menu::burn_card has cognitive complexity 32 (threshold 15). Drivers by points: if/else 27 (28 pts), boolean chains 3, match/switch 1 (nesting depth added 1). To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
  • quotio_desktop::tray::icon::gauge (cognitive 31) apps/desktop/src/tray/icon.rs:16 — quotio_desktop::tray::icon::gauge has cognitive complexity 31 (threshold 15). Drivers by points: if/else 6 (16 pts), loops 5 (13 pts), boolean chains 1, match/switch 1 (nesting depth added 18). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
  • quotio_desktop::notifier::check (cognitive 27) apps/desktop/src/notifier.rs:17 — quotio_desktop::notifier::check has cognitive complexity 27 (threshold 15). Drivers by points: if/else 8 (20 pts), loops 3 (4 pts), boolean chains 3 (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.
  • quotio_desktop::main (cognitive 22) apps/desktop/src/main.rs:73 — quotio_desktop::main has cognitive complexity 22 (threshold 15). Drivers by points: if/else 11 (13 pts), boolean chains 4, match/switch 3 (4 pts), loops 1 (nesting depth added 3). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition.
  • quotio_desktop::proxy::init (cognitive 16) apps/desktop/src/proxy.rs:222 — quotio_desktop::proxy::init has cognitive complexity 16 (threshold 15). Drivers by points: if/else 6 (11 pts), boolean chains 3, loops 2 (nesting depth added 5). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
  • quotio_desktop::ui::settings::privacy::migration_section (cognitive 16) apps/desktop/src/ui/settings/privacy.rs:145 — quotio_desktop::ui::settings::privacy::migration_section has cognitive complexity 16 (threshold 15). Drivers by points: if/else 8 (12 pts), match/switch 2 (3 pts), boolean chains 1 (nesting depth added 5). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D10 · Test Quality · Skipped test · ×6
  • Skipped test: testLegacyProtectedCredentialIsReadOnlyAndDoesNotResurrectAfterDeletion Packages/QuotioCore/Tests/QuotioInfrastructureTests/AccountPersistenceTests.swift:254 — Skipped — throws XCTSkip
  • Skipped test: testRenderAccountsScreenScenarios Packages/QuotioCore/Tests/QuotioPresentationTests/AccountsScreenSnapshotTests.swift:15 — Skipped — throws XCTSkip
  • Skipped test: testRenderPairingLayouts Packages/QuotioCore/Tests/QuotioPresentationTests/CompanionScreenModelTests.swift:85 — Skipped — throws XCTSkip
  • Skipped test: testRefreshClicksKeepNativeMenuOpen Packages/QuotioCore/Tests/QuotioPresentationTests/RefreshButtonTests.swift:158 — Skipped — throws XCTSkip
  • Skipped test: testTrackedMenuResizesExistingAccountViewWhenWarningAppearsAndClears Packages/QuotioCore/Tests/QuotioPresentationTests/StatusBarMenuTests.swift:300 — Skipped — throws XCTSkip
  • Skipped test: testLiveRustTLS Packages/QuotioHostClient/Tests/QuotioHostClientTests/QuotioHostTrustTests.swift:31 — Skipped — throws XCTSkip
D3 · God Classes · TooManyMethods · ×6
  • TooManyMethods: QuotioCLIBackend Packages/QuotioCore/Sources/QuotioInfrastructure/QuotioCLI/QuotioCLIBackend.swift:7 — TooManyMethods — 67 methods. The bar is 30 methods; this is 37 over it, 2.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.
  • TooManyMethods: SettingsWindow apps/desktop/src/ui/settings/mod.rs:98 — TooManyMethods — 56 methods, declared across 9 files: settings/accounts.rs (23), settings/iphone.rs (9), settings/menu_bar.rs (7), settings/mod.rs (5), +5 more file(s). The bar is 30 methods; this is 26 over it, 1.87× the bar. That list is where to read them, not a suggestion to split the file: the members belong to the type wherever they are declared, so moving them between files leaves the count unchanged. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
  • TooManyMethods: ProxyLifecycleController Packages/QuotioCore/Sources/QuotioApplication/Proxy/ProxyLifecycleController.swift:4 — TooManyMethods — 51 methods. The bar is 30 methods; this is 21 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.
  • TooManyMethods: URLSessionProxyManagementAPI Packages/QuotioCore/Sources/QuotioInfrastructure/Proxy/URLSessionProxyManagementAPI.swift:37 — TooManyMethods — 41 methods. The bar is 30 methods; this is 11 over it, 1.37× the bar. Most of these members implement Packages~QuotioCore~QuotioApplication.ProxyManagementAPI (32 of 39 members), so moving them onto a smaller type would remove them from that contract rather than reduce it. To reduce it, split the contract instead: give each cohesive group of operations its own smaller interface and its own implementing type. Where the contract has to stay whole, move the work behind these members into collaborator types, so what is left here is a forward per member rather than a responsibility per member.
  • TooManyMethods: QuotaHistorySheet Packages/QuotioCore/Sources/QuotioPresentation/Quota/QuotaHistorySheet.swift:5 — TooManyMethods — 41 methods. The bar is 30 methods; this is 11 over it, 1.37× 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: ProxyManagementScreenModel Packages/QuotioCore/Sources/QuotioPresentation/Proxy/ProxyManagementScreenModel.swift:6 — TooManyMethods — 36 methods. The bar is 30 methods; this is 6 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.
AXO1 · Runtime API surface · API operation answered with no credentials · ×5
  • API operation answered with no credentials: GET /health — http://127.0.0.1:6767/health returned HTTP 200 to two GET requests carrying nothing. Observed on the live app. We do not decide whether this operation is meant to be public. Advisory evidence for CRA Annex I (2)(d) and NIS2 IR.4.1.
  • API operation answered with no credentials: GET /openapi.json — http://127.0.0.1:6767/openapi.json returned HTTP 200 to two GET requests carrying nothing. Observed on the live app. We do not decide whether this operation is meant to be public. Advisory evidence for CRA Annex I (2)(d) and NIS2 IR.4.1.
  • API operation answered with no credentials: GET /v2/providers — http://127.0.0.1:6767/v2/providers returned HTTP 200 to two GET requests carrying nothing. Observed on the live app. We do not decide whether this operation is meant to be public. Advisory evidence for CRA Annex I (2)(d) and NIS2 IR.4.1.
  • API operation answered with no credentials: GET /v2/settings — http://127.0.0.1:6767/v2/settings returned HTTP 200 to two GET requests carrying nothing. Observed on the live app. We do not decide whether this operation is meant to be public. Advisory evidence for CRA Annex I (2)(d) and NIS2 IR.4.1.
  • API operation answered with no credentials: GET /v2/status — http://127.0.0.1:6767/v2/status returned HTTP 200 to two GET requests carrying nothing. Observed on the live app. We do not decide whether this operation is meant to be public. Advisory evidence for CRA Annex I (2)(d) and NIS2 IR.4.1.
D4 · Code Duplication · Edited copy of a member (5 corresponding lines) · ×5
  • Edited copy of a member (5 corresponding lines) Packages/QuotioCore/Sources/QuotioApplication/CustomProviders/CustomProviderService.swift:70 — Packages/QuotioCore/Sources/QuotioApplication/CustomProviders/CustomProviderService.swift:70-78 | Packages/QuotioCore/Sources/QuotioInfrastructure/CustomProviders/CustomProviderAdapters.swift:220-224 — These two members are one piece of code written twice and then edited apart: 5 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (5 corresponding lines) Packages/QuotioCore/Sources/QuotioPresentation/Components/ExperimentalBadge.swift:14 — Packages/QuotioCore/Sources/QuotioPresentation/Components/ExperimentalBadge.swift:14-25 | Packages/QuotioCore/Sources/QuotioPresentation/Quota/QuotaHistorySheet.swift:260-264 — These two members are one piece of code written twice and then edited apart: 5 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (5 corresponding lines) Packages/QuotioCore/Sources/QuotioInfrastructure/Antigravity/AntigravityAccountSwitcher.swift:236 — Packages/QuotioCore/Sources/QuotioInfrastructure/Antigravity/AntigravityAccountSwitcher.swift:236-241 | Packages/QuotioCore/Sources/QuotioInfrastructure/Credentials/FileAuthFileRepository.swift:391-395 — These two members are one piece of code written twice and then edited apart: 5 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (5 corresponding lines) Packages/QuotioCore/Sources/QuotioApplication/Proxy/ProxyLifecycleController.swift:930 — Packages/QuotioCore/Sources/QuotioApplication/Proxy/ProxyLifecycleController.swift:930-936 | Packages/QuotioCore/Sources/QuotioPresentation/App/PresentationValues.swift:119-123 — These two members are one piece of code written twice and then edited apart: 5 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (5 corresponding lines) Packages/QuotioCore/Sources/QuotioDomain/Proxy/ProxyManagementModels.swift:105 — Packages/QuotioCore/Sources/QuotioDomain/Proxy/ProxyManagementModels.swift:105-109 | Packages/QuotioCore/Sources/QuotioPresentation/Components/AccountRow.swift:167-172 — These two members are one piece of code written twice and then edited apart: 5 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D3 · God Classes · FunctionTooLong · ×4
  • FunctionTooLong: quotio_desktop::ui::menu::burn_card apps/desktop/src/ui/menu.rs:1070 — FunctionTooLong — quotio_desktop::ui::menu::burn_card runs 200 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 100 over it, 2.00× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
  • FunctionTooLong: quotio_desktop::prefs::swift_preferences apps/desktop/src/prefs.rs:203 — FunctionTooLong — quotio_desktop::prefs::swift_preferences runs 114 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 14 over it, 1.14× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
  • FunctionTooLong: quotio_desktop::ui::menu::gauge apps/desktop/src/ui/menu.rs:725 — FunctionTooLong — quotio_desktop::ui::menu::gauge runs 105 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 5 over it, 1.05× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
  • FunctionTooLong: quotio_desktop::main apps/desktop/src/main.rs:73 — FunctionTooLong — quotio_desktop::main runs 103 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 3 over it, 1.03× 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.
D4 · Code Duplication · Edited copy of a member (7 corresponding lines) · ×4
  • Edited copy of a member (7 corresponding lines) apps/ios/Sources/QuotioMobile/QuotaFormat.swift:42 — apps/ios/Sources/QuotioMobile/QuotaFormat.swift:42-48 | apps/ios/Sources/QuotioMobile/QuotaFormat.swift:51-57 — These two members are one piece of code written twice and then edited apart: 7 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (7 corresponding lines) Packages/QuotioCore/Sources/QuotioInfrastructure/QuotioCLI/QuotioCompanionService.swift:154 — Packages/QuotioCore/Sources/QuotioInfrastructure/QuotioCLI/QuotioCompanionService.swift:154-160 | apps/ios/Sources/QuotioMobile/Connection.swift:47-56 — These two members are one piece of code written twice and then edited apart: 7 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (7 corresponding lines) Packages/QuotioHostClient/Sources/QuotioHostClient/QuotioHostHistory.swift:198 — Packages/QuotioHostClient/Sources/QuotioHostClient/QuotioHostHistory.swift:198-204 | Packages/QuotioHostClient/Sources/QuotioHostClient/QuotioHostHistory.swift:205-211 — These two members are one piece of code written twice and then edited apart: 7 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (7 corresponding lines) Packages/QuotioCore/Sources/QuotioPresentation/MenuBar/StatusBarMenuRenderer.swift:1490 — Packages/QuotioCore/Sources/QuotioPresentation/MenuBar/StatusBarMenuRenderer.swift:1490-1496 | Packages/QuotioCore/Sources/QuotioPresentation/MenuBar/StatusBarMenuRenderer.swift:1569-1575 — These two members are one piece of code written twice and then edited apart: 7 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D1 · Cyclomatic Complexity · quotio_desktop · ×3
  • quotio_desktop::prefs::swift_preferences (cyclomatic 26) apps/desktop/src/prefs.rs:203 — quotio_desktop::prefs::swift_preferences has cyclomatic complexity 26 (threshold 15). To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Where every arm is uniform — the same kind of value, with no behaviour of its own — a table keyed by the case is the shorter form; wherever the arms carry different data or different behaviour, keep them as cases, because collapsing those trades an explicit, reviewable set of cases for nothing.
  • quotio_desktop::main (cyclomatic 22) apps/desktop/src/main.rs:73 — quotio_desktop::main has cyclomatic complexity 22 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
  • quotio_desktop::ui::menu::burn_card (cyclomatic 21) apps/desktop/src/ui/menu.rs:1070 — quotio_desktop::ui::menu::burn_card 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.
D3 · God Classes · ClassTooLong · ×3
  • ClassTooLong: ConnectFlow apps/desktop/src/ui/settings/connect.rs:84 — ClassTooLong — 909 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), 28 methods, 3 blocks, lines 84-1276. The bar is 400 significant lines; this is 509 over it, 2.27× 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: QuotaHistorySheet Packages/QuotioCore/Sources/QuotioPresentation/Quota/QuotaHistorySheet.swift:5 — ClassTooLong — 502 significant lines (blank, comment-only and punctuation-only lines excluded), 41 methods. The bar is 400 significant lines; this is 102 over it, 1.26× 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: QuotaHistory apps/desktop/src/ui/settings/history.rs:45 — ClassTooLong — 501 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), 10 methods, 3 blocks, lines 45-670. The bar is 400 significant lines; this is 101 over it, 1.25× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
D4 · Code Duplication · Edited copy of a member (6 corresponding lines) · ×3
  • Edited copy of a member (6 corresponding lines) Packages/QuotioCore/Sources/QuotioPresentation/MenuBar/StatusBarMenuRenderer.swift:1503 — Packages/QuotioCore/Sources/QuotioPresentation/MenuBar/StatusBarMenuRenderer.swift:1503-1508 | Packages/QuotioCore/Sources/QuotioPresentation/MenuBar/StatusBarMenuRenderer.swift:1810-1815 — These two members are one piece of code written twice and then edited apart: 6 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (6 corresponding lines) Packages/QuotioCore/Sources/QuotioDomain/CustomProviders/CustomProviderModels.swift:66 — Packages/QuotioCore/Sources/QuotioDomain/CustomProviders/CustomProviderModels.swift:66-71 | Packages/QuotioCore/Sources/QuotioDomain/Quota/WarpToken.swift:9-19 — These two members are one piece of code written twice and then edited apart: 6 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (6 corresponding lines) Packages/QuotioCore/Sources/QuotioDomain/Accounts/AntigravitySwitchModels.swift:39 — Packages/QuotioCore/Sources/QuotioDomain/Accounts/AntigravitySwitchModels.swift:39-44 | Packages/QuotioCore/Sources/QuotioDomain/Proxy/ProxyModels.swift:258-268 — These two members are one piece of code written twice and then edited apart: 6 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copy of a member (10 corresponding lines) · ×3
  • Edited copy of a member (10 corresponding lines) Packages/QuotioCore/Sources/QuotioApplication/Proxy/ProxyLifecycleController.swift:92 — Packages/QuotioCore/Sources/QuotioApplication/Proxy/ProxyLifecycleController.swift:92-101 | Packages/QuotioCore/Sources/QuotioInfrastructure/Antigravity/AntigravityAccountSwitcher.swift:70-79 — 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.
  • Edited copy of a member (10 corresponding lines) Packages/QuotioCore/Sources/QuotioPresentation/Proxy/ProxyManagementScreenModel.swift:292 — Packages/QuotioCore/Sources/QuotioPresentation/Proxy/ProxyManagementScreenModel.swift:292-301 | Packages/QuotioCore/Sources/QuotioPresentation/Proxy/ProxyManagementScreenModel.swift:303-312 — 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.
  • Edited copy of a member (10 corresponding lines) Packages/QuotioCore/Sources/QuotioPresentation/Quota/QuotaScreenModel.swift:111 — Packages/QuotioCore/Sources/QuotioPresentation/Quota/QuotaScreenModel.swift:111-121 | Packages/QuotioCore/Sources/QuotioPresentation/Tunnel/TunnelScreenModel.swift:76-85 — 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 · Duplicated block (9 lines × 2) · ×3
  • Duplicated block (9 lines × 2) Packages/QuotioCore/Sources/QuotioPresentation/Components/GLMAPIKeySheet.swift:98 — Packages/QuotioCore/Sources/QuotioPresentation/Components/GLMAPIKeySheet.swift:98-106 | Packages/QuotioCore/Sources/QuotioPresentation/Components/GLMAPIKeySheet.swift:120-128 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `Packages/QuotioCore/Sources/QuotioPresentation/Components/GLMAPIKeySheet.swift: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. Note first that the copies are not typed on the same thing: the declarations holding them bind `spacing` to `2` in one and `8` 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 before the matched lines, `Packages/QuotioCore/Sources/QuotioPresentation/Components/GLMAPIKeySheet.swift:114` calls `background`, `Color`, `opacity` and `Packages/QuotioCore/Sources/QuotioPresentation/Components/GLMAPIKeySheet.swift:93` 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 (9 lines × 2) apps/ios/QuotioIOS/DesignSystem/AccountCard.swift:71 — apps/ios/QuotioIOS/DesignSystem/AccountCard.swift:71-79 | apps/ios/QuotioIOS/DesignSystem/EmptyAccountRow.swift:34-42 — 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 `apps/ios/QuotioIOS/DesignSystem/AccountCard.swift:71` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (9 lines × 2) apps/desktop/src/ui/settings/accounts.rs:137 — apps/desktop/src/ui/settings/accounts.rs:137-145 | apps/desktop/src/ui/settings/accounts.rs:411-419 — 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.
D4 · Code Duplication · Duplicated block (7 lines × 2) · ×3
  • Duplicated block (7 lines × 2) Packages/QuotioCore/Sources/QuotioInfrastructure/Process/ProxyProcessController.swift:159 — Packages/QuotioCore/Sources/QuotioInfrastructure/Process/ProxyProcessController.swift:159-165 | Packages/QuotioCore/Sources/QuotioInfrastructure/Tunnel/CloudflaredService.swift:120-128 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `Packages/QuotioCore/Sources/QuotioInfrastructure/Process/ProxyProcessController.swift:159` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
  • Duplicated block (7 lines × 2) Packages/QuotioCore/Sources/QuotioPresentation/MenuBar/StatusBarMenuRenderer.swift:1616 — Packages/QuotioCore/Sources/QuotioPresentation/MenuBar/StatusBarMenuRenderer.swift:1616-1622 | Packages/QuotioCore/Sources/QuotioPresentation/MenuBar/StatusBarMenuRenderer.swift:1663-1669 — 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 `Packages/QuotioCore/Sources/QuotioPresentation/MenuBar/StatusBarMenuRenderer.swift:1616` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (7 lines × 2) apps/desktop/src/ui/settings/connect.rs:1267 — apps/desktop/src/ui/settings/connect.rs:1267-1273 | apps/desktop/src/ui/settings/iphone.rs:745-752 — 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 `apps/desktop/src/ui/settings/connect.rs:1267` 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 (6 lines × 2) · ×3
  • Duplicated block (6 lines × 2) Packages/QuotioCore/Sources/QuotioInfrastructure/Persistence/FileAccountMetadataRepository.swift:13 — Packages/QuotioCore/Sources/QuotioInfrastructure/Persistence/FileAccountMetadataRepository.swift:13-18 | Packages/QuotioCore/Sources/QuotioInfrastructure/Persistence/FileAccountSnapshotDataStore.swift:7-12 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
  • Duplicated block (6 lines × 2) apps/desktop/src/ui/settings/accounts.rs:1175 — apps/desktop/src/ui/settings/accounts.rs:1175-1180 | apps/desktop/src/ui/settings/accounts.rs:1246-1251 — 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 `apps/desktop/src/ui/settings/accounts.rs:1175` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (6 lines × 2) apps/desktop/src/notifier.rs:37 — apps/desktop/src/notifier.rs:37-42 | apps/desktop/src/notifier.rs:51-57 — 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 `apps/desktop/src/notifier.rs:37` 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 (5 lines × 2) · ×3
  • Duplicated block (5 lines × 2) apps/desktop/src/host.rs:259 — apps/cli/src/accounts/sources.rs:291-295 | apps/desktop/src/host.rs:259-263 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
  • Duplicated block (5 lines × 2) apps/desktop/src/app.rs:158 — apps/desktop/src/app.rs:158-162 | apps/desktop/src/app.rs:232-236 — 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 `apps/desktop/src/app.rs:158` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (5 lines × 2) apps/desktop/src/store.rs:204 — apps/desktop/src/store.rs:204-208 | apps/desktop/src/store.rs:224-228 — 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.
D6 · Cohesion (LCOM4) · Low cohesion · ×3
  • Low cohesion: QuotioCLIBackend (LCOM4 8) Packages/QuotioCore/Sources/QuotioInfrastructure/QuotioCLI/QuotioCLIBackend.swift:7 — QuotioCLIBackend's methods fall into 8 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 8 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
  • Low cohesion: String (LCOM4 5) Packages/QuotioCore/Sources/QuotioApplication/Accounts/AuthFileRepository.swift:122 — String'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: ProxyManagementScreenModel (LCOM4 4) Packages/QuotioCore/Sources/QuotioPresentation/Proxy/ProxyManagementScreenModel.swift:6 — ProxyManagementScreenModel'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.
PF3 · Async & latency hygiene · Sync-over-async blocking · ×3
  • Sync-over-async blocking Packages/QuotioCore/Sources/QuotioInfrastructure/Antigravity/AntigravitySystemAdapters.swift:91 — `killHelpers` is async and calls .waitUntilExit() — a blocking call inside async code stalls the cooperative pool's thread — one per core — and every task scheduled on it for as long as it runs.
  • Sync-over-async blocking Packages/QuotioCore/Sources/QuotioInfrastructure/Lifecycle/ContinuousSleeper.swift:6 — `sleep` is async and calls sleep — a blocking call inside async code stalls the cooperative pool's thread — one per core — and every task scheduled on it for as long as it runs.
  • Sync-over-async blocking Packages/QuotioCore/Sources/QuotioInfrastructure/Process/ProxyProcessController.swift:154 — `killProcesses` is async and calls .waitUntilExit() — a blocking call inside async code stalls the cooperative pool's thread — one per core — and every task scheduled on it for as long as it runs.
D30 · Dependency Vulnerabilities · Medium CVE · ×2
  • REDACTED
  • REDACTED
D30 · Dependency Vulnerabilities · Medium vulnerability · ×2
  • REDACTED
  • REDACTED
D30 · Dependency Vulnerabilities · Medium advisory (unsound) · ×2
  • REDACTED
  • REDACTED
D35 · Change Coupling · Change coupling · ×2
  • Change coupling: QuotaPorts.swift ↔ QuotioCLIModels.swift Packages/QuotioCore/Sources/QuotioApplication/Quota/QuotaPorts.swift:1 — `Packages/QuotioCore/Sources/QuotioApplication/Quota/QuotaPorts.swift` and `Packages/QuotioCore/Sources/QuotioInfrastructure/QuotioCLI/QuotioCLIModels.swift` change together 50% of the time (5 of the 10 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets). They sit in different directories, but in this ecosystem the namespace is declared in the FILE, not by the folder — so the two may well share one namespace and reference each other with no import for this pass to see. Read the pair before acting: if one derives from or overrides the other, the dependency is explicit in the type declaration and the co-change is definitional; if one registers itself into the other through a hook or an initialiser, the missing dependency is DELIBERATE and the thing to add is a comment saying so; if they simply belong together, co-locate them; if none of these holds, the coupling is hidden and worth breaking. You can check this without leaving the row: of the 5 shared commits counted here, the most recent 3 are `fa16a824` refactor(macos): render account and quota state from host snapshots; `24a03435` fix(accounts): retry native discovery and isolate source failures; `99d89fba` feat(macos): organize connections around provider settings — run `git show` on any of them.
  • Change coupling: config.rs ↔ tests.rs apps/cli/src/config.rs:1 — `apps/cli/src/config.rs` and `apps/cli/src/server/tests.rs` change together 50% of the time (5 of the 10 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) 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 5 shared commits counted here, the most recent 3 are `3262c1ab` fix(host): persist disabled borrowed sources across refreshes; `65d7ad0d` feat(host): schedule native discovery using persisted tracking settings; `27d44130` fix(usage): preserve helper account and refresh semantics — run `git show` on any of them.
D4 · Code Duplication · Edited copy of a member (31 corresponding lines) · ×2
  • Edited copy of a member (31 corresponding lines) apps/desktop/src/ui/menu.rs:550 — apps/desktop/src/ui/menu.rs:550-597 | apps/desktop/src/ui/menu.rs:725-846 — 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.
  • Edited copy of a member (31 corresponding lines) apps/desktop/src/ui/settings/accounts.rs:1297 — apps/desktop/src/ui/settings/accounts.rs:1297-1338 | apps/desktop/src/ui/settings/iphone.rs:380-410 — 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 (12 corresponding lines) · ×2
  • Edited copy of a member (12 corresponding lines) Packages/QuotioCore/Sources/QuotioDomain/Proxy/ProxyManagementModels.swift:23 — Packages/QuotioCore/Sources/QuotioDomain/Proxy/ProxyManagementModels.swift:23-61 | apps/ios/Sources/QuotioMobile/MobileSnapshot.swift:79-90 — These two members are one piece of code written twice and then edited apart: 12 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (12 corresponding lines) Packages/QuotioCore/Sources/QuotioInfrastructure/HTTP/ProxyNetworkAdapters.swift:179 — Packages/QuotioCore/Sources/QuotioInfrastructure/HTTP/ProxyNetworkAdapters.swift:179-190 | Packages/QuotioCore/Sources/QuotioInfrastructure/HTTP/ProxyNetworkAdapters.swift:277-295 — 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 (27 corresponding lines) · ×2
  • Edited copy of a member (27 corresponding lines) apps/desktop/src/ui/settings/cli_proxy.rs:476 — apps/desktop/src/ui/settings/cli_proxy.rs:476-502 | apps/desktop/src/ui/settings/widgets.rs:40-72 — These two members are one piece of code written twice and then edited apart: 27 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 (27 corresponding lines) Packages/QuotioCore/Sources/QuotioPresentation/Components/ProviderAccountsGroup.swift:60 — Packages/QuotioCore/Sources/QuotioPresentation/Components/ProviderAccountsGroup.swift:60-86 | Packages/QuotioCore/Sources/QuotioPresentation/Components/ProviderDisclosureGroup.swift:63-95 — These two members are one piece of code written twice and then edited apart: 27 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copy of a member (16 corresponding lines) · ×2
  • Edited copy of a member (16 corresponding lines) Packages/QuotioCore/Sources/QuotioApplication/Proxy/ProxyLifecycleController.swift:938 — Packages/QuotioCore/Sources/QuotioApplication/Proxy/ProxyLifecycleController.swift:938-953 | Packages/QuotioCore/Sources/QuotioInfrastructure/HTTP/ProxyNetworkAdapters.swift:49-68 — These two members are one piece of code written twice and then edited apart: 16 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (16 corresponding lines) Packages/QuotioCore/Sources/QuotioPresentation/Components/ProviderIcon.swift:17 — Packages/QuotioCore/Sources/QuotioPresentation/Components/ProviderIcon.swift:17-34 | Packages/QuotioCore/Sources/QuotioPresentation/MenuBar/StatusBarMenuRenderer.swift:694-709 — These two members are one piece of code written twice and then edited apart: 16 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copy of a member (15 corresponding lines) · ×2
  • Edited copy of a member (15 corresponding lines) Packages/QuotioCore/Sources/QuotioPresentation/Quota/QuotaHistoryServiceModel.swift:43 — Packages/QuotioCore/Sources/QuotioPresentation/Quota/QuotaHistoryServiceModel.swift:43-57 | Packages/QuotioCore/Sources/QuotioPresentation/Quota/QuotaHistoryServiceModel.swift:58-72 — 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.
  • Edited copy of a member (15 corresponding lines) Packages/QuotioCore/Sources/QuotioApplication/Accounts/AuthFileRepository.swift:77 — Packages/QuotioCore/Sources/QuotioApplication/Accounts/AuthFileRepository.swift:77-93 | Packages/QuotioCore/Sources/QuotioApplication/Accounts/CredentialPorts.swift:12-26 — 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 · Duplicated block (11 lines × 2) · ×2
  • Duplicated block (11 lines × 2) Packages/QuotioCore/Sources/QuotioPresentation/Components/QuotioButtonStyles.swift:78 — Packages/QuotioCore/Sources/QuotioPresentation/Components/QuotioButtonStyles.swift:78-88 | Packages/QuotioCore/Sources/QuotioPresentation/Components/QuotioButtonStyles.swift:117-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 `Packages/QuotioCore/Sources/QuotioPresentation/Components/QuotioButtonStyles.swift:78` 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 before the matched lines, `Packages/QuotioCore/Sources/QuotioPresentation/Components/QuotioButtonStyles.swift:76` calls `padding` and `Packages/QuotioCore/Sources/QuotioPresentation/Components/QuotioButtonStyles.swift:116` 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 (11 lines × 2) Packages/QuotioCore/Sources/QuotioPresentation/Settings/UsageDisplaySettingsSection.swift:32 — Packages/QuotioCore/Sources/QuotioPresentation/Settings/UsageDisplaySettingsSection.swift:32-42 | Packages/QuotioCore/Sources/QuotioPresentation/Settings/UsageDisplaySettingsSection.swift:51-61 — 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 `Packages/QuotioCore/Sources/QuotioPresentation/Settings/UsageDisplaySettingsSection.swift:32` 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 lines × 2) · ×2
  • Duplicated block (10 lines × 2) Packages/QuotioCore/Sources/QuotioPresentation/MenuBar/StatusBarMenuRenderer.swift:743 — Packages/QuotioCore/Sources/QuotioPresentation/MenuBar/StatusBarMenuRenderer.swift:743-752 | Packages/QuotioCore/Sources/QuotioPresentation/MenuBar/StatusBarMenuRenderer.swift:793-802 — 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 `Packages/QuotioCore/Sources/QuotioPresentation/MenuBar/StatusBarMenuRenderer.swift:743` 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 (10 lines × 2) apps/desktop/src/ui/settings/general.rs:157 — apps/desktop/src/ui/settings/general.rs:157-166 | apps/desktop/src/ui/settings/menu_bar.rs:145-154 — 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 `apps/desktop/src/ui/settings/general.rs:157` 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 (8 lines × 2) · ×2
  • Duplicated block (8 lines × 2) Packages/QuotioCore/Sources/QuotioDomain/Quota/QuotaModels.swift:31 — Packages/QuotioCore/Sources/QuotioDomain/Quota/QuotaModels.swift:31-38 | Packages/QuotioCore/Sources/QuotioDomain/Quota/QuotaModels.swift:124-131 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
  • Duplicated block (8 lines × 2) apps/desktop/src/ui/settings/accounts.rs:1203 — apps/desktop/src/ui/settings/accounts.rs:1203-1210 | apps/desktop/src/ui/settings/accounts.rs:1262-1269 — 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 `apps/desktop/src/ui/settings/accounts.rs:1203` 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–9 lines × 2) · ×2
  • Duplicated block (8–9 lines × 2) apps/desktop/src/autostart.rs:20 — apps/desktop/src/autostart.rs:20-28 | apps/desktop/src/autostart.rs:63-70 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
  • Duplicated block (8–9 lines × 2) apps/desktop/src/ui/menu.rs:247 — apps/desktop/src/ui/menu.rs:247-255 | apps/desktop/src/ui/settings/accounts.rs:549-556 — 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 `apps/desktop/src/ui/menu.rs:247` 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.
D5 · Coupling · Off the main sequence · ×2
  • Off the main sequence: QuotioDomain — QuotioDomain: abstractness 0.00, instability 0.00, distance 1.00 — zone of pain — concrete and depended on by 4 project(s), so it's rigid to change.
  • Off the main sequence: QuotioHostClient — QuotioHostClient: abstractness 0.00, instability 0.00, distance 1.00 — zone of pain — concrete and depended on by 4 project(s), so it's rigid to change.
P7 · Outbound HTTP resilience · Outbound HTTP without resilience · ×2
  • Outbound HTTP without resilience apps/cli/src/usage.rs:146 — `reqwest::Client::builder(` makes an outbound HTTP call, and nothing bounds it: no timeout, deadline, retry or circuit breaker is set for it here, and the client has no process-wide default. A slow or failing dependency will hold this service's request, thread or connection until the call gives up on its own — or never, for a client with no default timeout.
  • Outbound HTTP without resilience apps/desktop/src/updater.rs:106 — `reqwest::Client::builder(` makes an outbound HTTP call, and nothing bounds it: no timeout, deadline, retry or circuit breaker is set for it here, and the client has no process-wide default. A slow or failing dependency will hold this service's request, thread or connection until the call gives up on its own — or never, for a client with no default timeout.
D1 · Cyclomatic Complexity · QuotioHostSnapshot.validate (cyclomatic 49) · ×1
  • QuotioHostSnapshot.validate (cyclomatic 49) Packages/QuotioHostClient/Sources/QuotioHostClient/QuotioHostSnapshot.swift:130 — QuotioHostSnapshot.validate has cyclomatic complexity 49 (threshold 15). Of this number, 40 points are the body's own statements and 9 belong to one function item inside it that branches. To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
D1 · Cyclomatic Complexity · package.macos (cyclomatic 33) · ×1
  • package.macos (cyclomatic 33) apps/desktop/scripts/package.py:27 — package.macos has cyclomatic complexity 33 (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 · AccountsSettingsScreen.body (cyclomatic 31) · ×1
  • AccountsSettingsScreen.body (cyclomatic 31) Packages/QuotioCore/Sources/QuotioPresentation/Settings/AccountsSettingsScreen.swift:26 — AccountsSettingsScreen.body has cyclomatic complexity 31 (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 · QuotioCLIServerProcess.start (cyclomatic 30) · ×1
  • QuotioCLIServerProcess.start (cyclomatic 30) Packages/QuotioCore/Sources/QuotioInfrastructure/QuotioCLI/QuotioCLIServerProcess.swift:94 — QuotioCLIServerProcess.start has cyclomatic complexity 30 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · AccountRow.body (cyclomatic 29) · ×1
  • AccountRow.body (cyclomatic 29) Packages/QuotioCore/Sources/QuotioPresentation/Components/AccountRow.swift:214 — AccountRow.body has cyclomatic complexity 29 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
D1 · Cyclomatic Complexity · QuotioHostPresentationMapper.resolvedSnapshot (cyclomatic 26) · ×1
  • QuotioHostPresentationMapper.resolvedSnapshot (cyclomatic 26) Packages/QuotioCore/Sources/QuotioInfrastructure/QuotioCLI/QuotioHostPresentationMapper.swift:14 — QuotioHostPresentationMapper.resolvedSnapshot 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 · QuotaHistoryScreenModel.reload (cyclomatic 25) · ×1
  • QuotaHistoryScreenModel.reload (cyclomatic 25) Packages/QuotioCore/Sources/QuotioPresentation/Quota/QuotaHistoryScreenModel.swift:123 — QuotaHistoryScreenModel.reload has cyclomatic complexity 25 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · QuotioHostHistoryChart.validate (cyclomatic 25) · ×1
  • QuotioHostHistoryChart.validate (cyclomatic 25) Packages/QuotioHostClient/Sources/QuotioHostClient/QuotioHostHistory.swift:117 — QuotioHostHistoryChart.validate has cyclomatic complexity 25 (threshold 15). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
D1 · Cyclomatic Complexity · QuotaProvider.entry (cyclomatic 25) · ×1
  • QuotaProvider.entry (cyclomatic 25) apps/ios/QuotioWidgets/QuotioWidgets.swift:61 — QuotaProvider.entry has cyclomatic complexity 25 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · QuotaHistorySheet.timeline (cyclomatic 23) · ×1
  • QuotaHistorySheet.timeline (cyclomatic 23) Packages/QuotioCore/Sources/QuotioPresentation/Quota/QuotaHistorySheet.swift:322 — QuotaHistorySheet.timeline 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 · QuotioCLIBackend.historyRequest (cyclomatic 22) · ×1
  • QuotioCLIBackend.historyRequest (cyclomatic 22) Packages/QuotioCore/Sources/QuotioInfrastructure/QuotioCLI/QuotioCLIBackend.swift:68 — QuotioCLIBackend.historyRequest 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 · QuotioCLIBackend.performRefresh (cyclomatic 22) · ×1
  • QuotioCLIBackend.performRefresh (cyclomatic 22) Packages/QuotioCore/Sources/QuotioInfrastructure/QuotioCLI/QuotioCLIBackend.swift:669 — QuotioCLIBackend.performRefresh 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 · QuotioHostHTTPClient.responseData (cyclomatic 21) · ×1
  • QuotioHostHTTPClient.responseData (cyclomatic 21) Packages/QuotioHostClient/Sources/QuotioHostClient/QuotioHostHTTPClient.swift:106 — QuotioHostHTTPClient.responseData has cyclomatic complexity 21 (threshold 15). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
D1 · Cyclomatic Complexity · QuotioHostHistoryObservation.validate (cyclomatic 21) · ×1
  • QuotioHostHistoryObservation.validate (cyclomatic 21) Packages/QuotioHostClient/Sources/QuotioHostClient/QuotioHostHistory.swift:51 — QuotioHostHistoryObservation.validate has cyclomatic complexity 21 (threshold 15). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
D1 · Cyclomatic Complexity · QuotaWidgetView.body (cyclomatic 21) · ×1
  • QuotaWidgetView.body (cyclomatic 21) apps/ios/QuotioWidgets/QuotioWidgets.swift:119 — QuotaWidgetView.body 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 · CustomProviderYAMLSerializer.escapedString (cyclomatic 20) · ×1
  • CustomProviderYAMLSerializer.escapedString (cyclomatic 20) Packages/QuotioCore/Sources/QuotioInfrastructure/CustomProviders/CustomProviderYAMLSerializer.swift:41 — CustomProviderYAMLSerializer.escapedString has cyclomatic complexity 20 (threshold 15). To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Where every arm is uniform — the same kind of value, with no behaviour of its own — a table keyed by the case is the shorter form; wherever the arms carry different data or different behaviour, keep them as cases, because collapsing those trades an explicit, reviewable set of cases for nothing.
D1 · Cyclomatic Complexity · QuotioCLILegacyAccountMigration.migrate (cyclomatic 20) · ×1
  • QuotioCLILegacyAccountMigration.migrate (cyclomatic 20) Packages/QuotioCore/Sources/QuotioInfrastructure/QuotioCLI/QuotioCLILegacyAccountMigration.swift:35 — QuotioCLILegacyAccountMigration.migrate 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 · QuotioHostPresentationMapper.metric (cyclomatic 20) · ×1
  • QuotioHostPresentationMapper.metric (cyclomatic 20) Packages/QuotioCore/Sources/QuotioInfrastructure/QuotioCLI/QuotioHostPresentationMapper.swift:262 — QuotioHostPresentationMapper.metric has cyclomatic complexity 20 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function so the top-level body reads as a short sequence of named decisions.
D1 · Cyclomatic Complexity · QuotaHistoryScreenModel.start (cyclomatic 20) · ×1
  • QuotaHistoryScreenModel.start (cyclomatic 20) Packages/QuotioCore/Sources/QuotioPresentation/Quota/QuotaHistoryScreenModel.swift:58 — QuotaHistoryScreenModel.start 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 · package.main (cyclomatic 20) · ×1
  • package.main (cyclomatic 20) apps/desktop/scripts/package.py:165 — package.main 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 · ProviderSettingsState.init (cyclomatic 19) · ×1
  • ProviderSettingsState.init (cyclomatic 19) Packages/QuotioCore/Sources/QuotioApplication/Accounts/ProviderSettingsState.swift:21 — ProviderSettingsState.init has cyclomatic complexity 19 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · QuotioCLIBackend.loadSnapshot (cyclomatic 18) · ×1
  • QuotioCLIBackend.loadSnapshot (cyclomatic 18) Packages/QuotioCore/Sources/QuotioInfrastructure/QuotioCLI/QuotioCLIBackend.swift:733 — QuotioCLIBackend.loadSnapshot has cyclomatic complexity 18 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · StatusBarMenuSnapshotMapper.makeSnapshot (cyclomatic 17) · ×1
  • StatusBarMenuSnapshotMapper.makeSnapshot (cyclomatic 17) Packages/QuotioCore/Sources/QuotioPresentation/MenuBar/StatusBarMenuSnapshot.swift:141 — StatusBarMenuSnapshotMapper.makeSnapshot has cyclomatic complexity 17 (threshold 15). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
D1 · Cyclomatic Complexity · QuotaHistoryScreenModel.loadMoreEvents (cyclomatic 17) · ×1
  • QuotaHistoryScreenModel.loadMoreEvents (cyclomatic 17) Packages/QuotioCore/Sources/QuotioPresentation/Quota/QuotaHistoryScreenModel.swift:171 — QuotaHistoryScreenModel.loadMoreEvents has cyclomatic complexity 17 (threshold 15). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
D1 · Cyclomatic Complexity · HostStore.refresh (cyclomatic 17) · ×1
  • HostStore.refresh (cyclomatic 17) apps/ios/QuotioIOS/HostStore.swift:108 — HostStore.refresh 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 · ProxyLifecycleController.install (cyclomatic 16) · ×1
  • ProxyLifecycleController.install (cyclomatic 16) Packages/QuotioCore/Sources/QuotioApplication/Proxy/ProxyLifecycleController.swift:236 — ProxyLifecycleController.install 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 · KeychainCredentialDataStore.readData (cyclomatic 16) · ×1
  • KeychainCredentialDataStore.readData (cyclomatic 16) Packages/QuotioCore/Sources/QuotioInfrastructure/Credentials/KeychainCredentialStores.swift:81 — KeychainCredentialDataStore.readData 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 · QuotioCLIBackend.resolvedAccount (cyclomatic 16) · ×1
  • QuotioCLIBackend.resolvedAccount (cyclomatic 16) Packages/QuotioCore/Sources/QuotioInfrastructure/QuotioCLI/QuotioCLIBackend.swift:794 — QuotioCLIBackend.resolvedAccount has cyclomatic complexity 16 (threshold 15). Of this number, 10 points are the body's own statements and 6 belong to 2 function items inside it that branch. To reduce it, separate the branches: extract each independent case into its own named function so the top-level body reads as a short sequence of named decisions.
D1 · Cyclomatic Complexity · QuotioCLIOAuthAuthorizer.begin (cyclomatic 16) · ×1
  • QuotioCLIOAuthAuthorizer.begin (cyclomatic 16) Packages/QuotioCore/Sources/QuotioInfrastructure/QuotioCLI/QuotioCLIOAuthAuthorizer.swift:19 — QuotioCLIOAuthAuthorizer.begin has cyclomatic complexity 16 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function so the top-level body reads as a short sequence of named decisions.
D1 · Cyclomatic Complexity · StatusBarManager.renderStatusBar (cyclomatic 16) · ×1
  • StatusBarManager.renderStatusBar (cyclomatic 16) Packages/QuotioCore/Sources/QuotioPresentation/MenuBar/StatusBarManager.swift:90 — StatusBarManager.renderStatusBar 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.
D1 · Cyclomatic Complexity · AppSettingsPage.body (cyclomatic 16) · ×1
  • AppSettingsPage.body (cyclomatic 16) Packages/QuotioCore/Sources/QuotioPresentation/Settings/AppSettingsPage.swift:15 — AppSettingsPage.body 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 · QuotaHistory · ×1
  • QuotaHistory::plot (cyclomatic 16) apps/desktop/src/ui/settings/history.rs:400 — QuotaHistory::plot 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.
D10 · Test Quality · No assertions · ×1
  • No assertions: testManualCompletionBelongsToCurrentAttempt Packages/QuotioCore/Tests/QuotioApplicationTests/OAuthFlowControllerTests.swift:79 — This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
D2 · Cognitive Complexity · QuotioHostSnapshot.validate (cognitive 59) · ×1
  • QuotioHostSnapshot.validate (cognitive 59) Packages/QuotioHostClient/Sources/QuotioHostClient/QuotioHostSnapshot.swift:130 — QuotioHostSnapshot.validate has cognitive complexity 59 (threshold 15). Drivers by points: boolean chains 34, if/else 10 (20 pts), loops 4 (5 pts) (nesting depth added 11). Of this number, 50 points are the body's own statements and 9 belong to one function item inside it that branches. To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
D2 · Cognitive Complexity · QuotaWidgetView.body (cognitive 57) · ×1
  • QuotaWidgetView.body (cognitive 57) apps/ios/QuotioWidgets/QuotioWidgets.swift:119 — QuotaWidgetView.body has cognitive complexity 57 (threshold 15). Drivers by points: ternaries 8 (28 pts), if/else 11 (25 pts), boolean chains 2, match/switch 1 (2 pts) (nesting depth added 35). To reduce it, split the body into named stages: move each independent 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 · QuotaProvider.entry (cognitive 47) · ×1
  • QuotaProvider.entry (cognitive 47) apps/ios/QuotioWidgets/QuotioWidgets.swift:61 — QuotaProvider.entry has cognitive complexity 47 (threshold 15). Drivers by points: if/else 9 (24 pts), error handling 5 (13 pts), boolean chains 10 (nesting depth added 23). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · package.macos (cognitive 45) · ×1
  • package.macos (cognitive 45) apps/desktop/scripts/package.py:27 — package.macos has cognitive complexity 45 (threshold 15). Drivers by points: if/else 16 (20 pts), loops 7 (13 pts), boolean chains 9, ternaries 1 (3 pts) (nesting depth added 12). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · QuotioCLIServerProcess.start (cognitive 43) · ×1
  • QuotioCLIServerProcess.start (cognitive 43) Packages/QuotioCore/Sources/QuotioInfrastructure/QuotioCLI/QuotioCLIServerProcess.swift:94 — QuotioCLIServerProcess.start has cognitive complexity 43 (threshold 15). Drivers by points: if/else 16 (28 pts), boolean chains 9, loops 2 (3 pts), match/switch 1 (2 pts), error handling 1 (nesting depth added 14). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · QuotioHostPresentationMapper.resolvedSnapshot (cognitive 41) · ×1
  • QuotioHostPresentationMapper.resolvedSnapshot (cognitive 41) Packages/QuotioCore/Sources/QuotioInfrastructure/QuotioCLI/QuotioHostPresentationMapper.swift:14 — QuotioHostPresentationMapper.resolvedSnapshot has cognitive complexity 41 (threshold 15). Drivers by points: if/else 11 (22 pts), ternaries 2 (7 pts), loops 4 (5 pts), match/switch 2 (4 pts), boolean chains 3 (nesting depth added 19). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · QuotaHistoryScreenModel.start (cognitive 38) · ×1
  • QuotaHistoryScreenModel.start (cognitive 38) Packages/QuotioCore/Sources/QuotioPresentation/Quota/QuotaHistoryScreenModel.swift:58 — QuotaHistoryScreenModel.start has cognitive complexity 38 (threshold 15). Drivers by points: if/else 11 (29 pts), boolean chains 7, loops 1 (2 pts) (nesting depth added 19). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · QuotaHistoryScreenModel.reload (cognitive 37) · ×1
  • QuotaHistoryScreenModel.reload (cognitive 37) Packages/QuotioCore/Sources/QuotioPresentation/Quota/QuotaHistoryScreenModel.swift:123 — QuotaHistoryScreenModel.reload has cognitive complexity 37 (threshold 15). Drivers by points: if/else 15 (28 pts), boolean chains 8, error handling 1 (nesting depth added 13). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · QuotioCLIBackend.historyRequest (cognitive 34) · ×1
  • QuotioCLIBackend.historyRequest (cognitive 34) Packages/QuotioCore/Sources/QuotioInfrastructure/QuotioCLI/QuotioCLIBackend.swift:68 — QuotioCLIBackend.historyRequest has cognitive complexity 34 (threshold 15). Drivers by points: if/else 13 (26 pts), boolean chains 4, match/switch 1 (3 pts), error handling 1 (nesting depth added 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · QuotioCLIBackend.performRefresh (cognitive 34) · ×1
  • QuotioCLIBackend.performRefresh (cognitive 34) Packages/QuotioCore/Sources/QuotioInfrastructure/QuotioCLI/QuotioCLIBackend.swift:669 — QuotioCLIBackend.performRefresh has cognitive complexity 34 (threshold 15). Drivers by points: if/else 11 (22 pts), boolean chains 6, ternaries 2 (3 pts), loops 1 (2 pts), error handling 1 (nesting depth added 13). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · AccountRow.body (cognitive 33) · ×1
  • AccountRow.body (cognitive 33) Packages/QuotioCore/Sources/QuotioPresentation/Components/AccountRow.swift:214 — AccountRow.body has cognitive complexity 33 (threshold 15). Drivers by points: if/else 17 (18 pts), boolean chains 11, ternaries 2 (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 · QuotioCLILegacyAccountMigration.migrate (cognitive 30) · ×1
  • QuotioCLILegacyAccountMigration.migrate (cognitive 30) Packages/QuotioCore/Sources/QuotioInfrastructure/QuotioCLI/QuotioCLILegacyAccountMigration.swift:35 — QuotioCLILegacyAccountMigration.migrate has cognitive complexity 30 (threshold 15). Drivers by points: if/else 8 (17 pts), boolean chains 6, error handling 4 (6 pts), loops 1 (nesting depth added 11). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · StatusBarMenuRenderer.buildMenu (cognitive 29) · ×1
  • StatusBarMenuRenderer.buildMenu (cognitive 29) Packages/QuotioCore/Sources/QuotioPresentation/MenuBar/StatusBarMenuRenderer.swift:171 — StatusBarMenuRenderer.buildMenu has cognitive complexity 29 (threshold 15). Drivers by points: if/else 8 (21 pts), loops 3 (7 pts), boolean chains 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 · AccountsSettingsScreen.body (cognitive 29) · ×1
  • AccountsSettingsScreen.body (cognitive 29) Packages/QuotioCore/Sources/QuotioPresentation/Settings/AccountsSettingsScreen.swift:26 — AccountsSettingsScreen.body has cognitive complexity 29 (threshold 15). Drivers by points: if/else 18 (20 pts), boolean chains 5, error handling 3, 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.
D2 · Cognitive Complexity · QuotioCLIBackend.loadSnapshot (cognitive 28) · ×1
  • QuotioCLIBackend.loadSnapshot (cognitive 28) Packages/QuotioCore/Sources/QuotioInfrastructure/QuotioCLI/QuotioCLIBackend.swift:733 — QuotioCLIBackend.loadSnapshot has cognitive complexity 28 (threshold 15). Drivers by points: if/else 9 (19 pts), boolean chains 6, loops 1 (2 pts), error handling 1 (nesting depth added 11). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · ProviderSettingsState.init (cognitive 27) · ×1
  • ProviderSettingsState.init (cognitive 27) Packages/QuotioCore/Sources/QuotioApplication/Accounts/ProviderSettingsState.swift:21 — ProviderSettingsState.init has cognitive complexity 27 (threshold 15). Drivers by points: if/else 9 (15 pts), boolean chains 8, loops 2 (4 pts) (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · LocalProxyOAuthAuthorizer.runManagementFlow (cognitive 27) · ×1
  • LocalProxyOAuthAuthorizer.runManagementFlow (cognitive 27) Packages/QuotioCore/Sources/QuotioInfrastructure/Accounts/LocalProxyOAuthAuthorizer.swift:88 — LocalProxyOAuthAuthorizer.runManagementFlow has cognitive complexity 27 (threshold 15). Drivers by points: if/else 6 (11 pts), error handling 3 (7 pts), match/switch 1 (4 pts), boolean chains 3, loops 1 (2 pts) (nesting depth added 13). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · QuotioHostHistoryChart.validate (cognitive 26) · ×1
  • QuotioHostHistoryChart.validate (cognitive 26) Packages/QuotioHostClient/Sources/QuotioHostClient/QuotioHostHistory.swift:117 — QuotioHostHistoryChart.validate has cognitive complexity 26 (threshold 15). Drivers by points: boolean chains 20, if/else 3 (5 pts), loops 1 (nesting depth added 2). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
D2 · Cognitive Complexity · package.main (cognitive 26) · ×1
  • package.main (cognitive 26) apps/desktop/scripts/package.py:165 — package.main has cognitive complexity 26 (threshold 15). Drivers by points: if/else 11 (12 pts), boolean chains 6, ternaries 3 (6 pts), loops 1 (2 pts) (nesting depth added 5). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
D2 · Cognitive Complexity · ProxyLifecycleController.install (cognitive 25) · ×1
  • ProxyLifecycleController.install (cognitive 25) Packages/QuotioCore/Sources/QuotioApplication/Proxy/ProxyLifecycleController.swift:236 — ProxyLifecycleController.install has cognitive complexity 25 (threshold 15). Drivers by points: if/else 9 (18 pts), boolean chains 6, 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 · OAuthStatusView.body (cognitive 25) · ×1
  • OAuthStatusView.body (cognitive 25) Packages/QuotioCore/Sources/QuotioPresentation/Components/OAuthSheet.swift:168 — OAuthStatusView.body has cognitive complexity 25 (threshold 15). Drivers by points: if/else 7 (13 pts), ternaries 2 (8 pts), boolean chains 3, match/switch 1 (nesting depth added 12). The drivers above price the dispatch low by construction — a dispatch is charged once however many cases it lists, while each branch inside an arm is charged in full — so most of this count is what the case bodies hold, and the arms are where it can be reduced. To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident.
D2 · Cognitive Complexity · QuotaHistory · ×1
  • QuotaHistory::plot (cognitive 24) apps/desktop/src/ui/settings/history.rs:400 — QuotaHistory::plot has cognitive complexity 24 (threshold 15). Drivers by points: if/else 15 (20 pts), boolean chains 2, loops 1, match/switch 1 (nesting depth added 5). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · KeychainCredentialDataStore.readData (cognitive 23) · ×1
  • KeychainCredentialDataStore.readData (cognitive 23) Packages/QuotioCore/Sources/QuotioInfrastructure/Credentials/KeychainCredentialStores.swift:81 — KeychainCredentialDataStore.readData has cognitive complexity 23 (threshold 15). Drivers by points: if/else 8 (14 pts), ternaries 2 (4 pts), match/switch 1 (3 pts), boolean chains 1, loops 1 (nesting depth added 10). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · QuotaHistorySheet.timeline (cognitive 23) · ×1
  • QuotaHistorySheet.timeline (cognitive 23) Packages/QuotioCore/Sources/QuotioPresentation/Quota/QuotaHistorySheet.swift:322 — QuotaHistorySheet.timeline has cognitive complexity 23 (threshold 15). Drivers by points: if/else 9 (12 pts), boolean chains 5, ternaries 3 (4 pts), match/switch 2 (nesting depth added 4). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · QuotioHostPresentationMapper.metric (cognitive 22) · ×1
  • QuotioHostPresentationMapper.metric (cognitive 22) Packages/QuotioCore/Sources/QuotioInfrastructure/QuotioCLI/QuotioHostPresentationMapper.swift:262 — QuotioHostPresentationMapper.metric has cognitive complexity 22 (threshold 15). Drivers by points: boolean chains 9, if/else 7 (9 pts), match/switch 2, ternaries 1 (2 pts) (nesting depth added 3). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · QuotioHostHistoryObservation.validate (cognitive 22) · ×1
  • QuotioHostHistoryObservation.validate (cognitive 22) Packages/QuotioHostClient/Sources/QuotioHostClient/QuotioHostHistory.swift:51 — QuotioHostHistoryObservation.validate has cognitive complexity 22 (threshold 15). Drivers by points: boolean chains 14, if/else 6 (8 pts) (nesting depth added 2). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
D2 · Cognitive Complexity · AppSettingsPage.body (cognitive 21) · ×1
  • AppSettingsPage.body (cognitive 21) Packages/QuotioCore/Sources/QuotioPresentation/Settings/AppSettingsPage.swift:15 — AppSettingsPage.body has cognitive complexity 21 (threshold 15). Drivers by points: if/else 6 (13 pts), boolean chains 5, match/switch 2 (3 pts) (nesting depth added 8). The drivers above price the dispatch low by construction — a dispatch is charged once however many cases it lists, while each branch inside an arm is charged in full — so most of this count is what the case bodies hold, and the arms are where it can be reduced. To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident.
D2 · Cognitive Complexity · QuotioHostHTTPClient.responseData (cognitive 20) · ×1
  • QuotioHostHTTPClient.responseData (cognitive 20) Packages/QuotioHostClient/Sources/QuotioHostClient/QuotioHostHTTPClient.swift:106 — QuotioHostHTTPClient.responseData has cognitive complexity 20 (threshold 15). Drivers by points: boolean chains 12, if/else 8. To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
D2 · Cognitive Complexity · HostStore.refresh (cognitive 20) · ×1
  • HostStore.refresh (cognitive 20) apps/ios/QuotioIOS/HostStore.swift:108 — HostStore.refresh has cognitive complexity 20 (threshold 15). Drivers by points: if/else 7 (11 pts), boolean chains 7, error handling 2 (nesting depth added 4). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · FileProxyConfigurationRepository.ensureAPIKey (cognitive 19) · ×1
  • FileProxyConfigurationRepository.ensureAPIKey (cognitive 19) Packages/QuotioCore/Sources/QuotioInfrastructure/Proxy/FileProxyConfigurationRepository.swift:100 — FileProxyConfigurationRepository.ensureAPIKey has cognitive complexity 19 (threshold 15). Drivers by points: if/else 7 (16 pts), loops 1 (2 pts), boolean chains 1 (nesting depth added 10). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · QuotaHistoryScreenModel.loadMoreEvents (cognitive 19) · ×1
  • QuotaHistoryScreenModel.loadMoreEvents (cognitive 19) Packages/QuotioCore/Sources/QuotioPresentation/Quota/QuotaHistoryScreenModel.swift:171 — QuotaHistoryScreenModel.loadMoreEvents has cognitive complexity 19 (threshold 15). Drivers by points: boolean chains 10, if/else 5 (8 pts), error handling 1 (nesting depth added 3). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
D2 · Cognitive Complexity · AntigravityAccountSwitcher.switchAccount (cognitive 18) · ×1
  • AntigravityAccountSwitcher.switchAccount (cognitive 18) Packages/QuotioCore/Sources/QuotioInfrastructure/Antigravity/AntigravityAccountSwitcher.swift:112 — AntigravityAccountSwitcher.switchAccount has cognitive complexity 18 (threshold 15). Drivers by points: if/else 6 (11 pts), boolean chains 3, error handling 2, ternaries 1 (2 pts) (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · QuotioCLIOAuthAuthorizer.begin (cognitive 18) · ×1
  • QuotioCLIOAuthAuthorizer.begin (cognitive 18) Packages/QuotioCore/Sources/QuotioInfrastructure/QuotioCLI/QuotioCLIOAuthAuthorizer.swift:19 — QuotioCLIOAuthAuthorizer.begin has cognitive complexity 18 (threshold 15). Drivers by points: boolean chains 7, if/else 5 (7 pts), error handling 2, match/switch 1 (2 pts) (nesting depth added 3). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · StatusBarManager.renderStatusBar (cognitive 18) · ×1
  • StatusBarManager.renderStatusBar (cognitive 18) Packages/QuotioCore/Sources/QuotioPresentation/MenuBar/StatusBarManager.swift:90 — StatusBarManager.renderStatusBar has cognitive complexity 18 (threshold 15). Drivers by points: if/else 9 (11 pts), boolean chains 4, ternaries 2 (3 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.
D2 · Cognitive Complexity · CompanionConnectionSetupView.body (cognitive 18) · ×1
  • CompanionConnectionSetupView.body (cognitive 18) Packages/QuotioCore/Sources/QuotioPresentation/Settings/CompanionConnectionSetupView.swift:9 — CompanionConnectionSetupView.body has cognitive complexity 18 (threshold 15). Drivers by points: if/else 8 (11 pts), ternaries 2 (5 pts), boolean chains 2 (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · CustomProviderYAMLSerializer.keyBlock (cognitive 17) · ×1
  • CustomProviderYAMLSerializer.keyBlock (cognitive 17) Packages/QuotioCore/Sources/QuotioInfrastructure/CustomProviders/CustomProviderYAMLSerializer.swift:110 — CustomProviderYAMLSerializer.keyBlock has cognitive complexity 17 (threshold 15). Drivers by points: if/else 4 (8 pts), boolean chains 5, loops 2 (4 pts) (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · GitHubAtomProxyUpdateFeed.latestVersion (cognitive 17) · ×1
  • GitHubAtomProxyUpdateFeed.latestVersion (cognitive 17) Packages/QuotioCore/Sources/QuotioInfrastructure/Updates/GitHubAtomProxyUpdateFeed.swift:35 — GitHubAtomProxyUpdateFeed.latestVersion has cognitive complexity 17 (threshold 15). Drivers by points: if/else 8 (13 pts), match/switch 1 (2 pts), error handling 1, ternaries 1 (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · PairHostView.body (cognitive 17) · ×1
  • PairHostView.body (cognitive 17) apps/ios/QuotioIOS/PairHostView.swift:21 — PairHostView.body has cognitive complexity 17 (threshold 15). Drivers by points: if/else 9 (16 pts), boolean chains 1 (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · ProxyLifecycleController.activate (cognitive 16) · ×1
  • ProxyLifecycleController.activate (cognitive 16) Packages/QuotioCore/Sources/QuotioApplication/Proxy/ProxyLifecycleController.swift:348 — ProxyLifecycleController.activate has cognitive complexity 16 (threshold 15). Drivers by points: if/else 5 (12 pts), boolean chains 3, error handling 1 (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · QuotaPace.init (cognitive 16) · ×1
  • QuotaPace.init (cognitive 16) Packages/QuotioCore/Sources/QuotioDomain/Quota/QuotaPace.swift:32 — QuotaPace.init has cognitive complexity 16 (threshold 15). Drivers by points: boolean chains 7, if/else 7, ternaries 1 (2 pts) (nesting depth added 1). To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
D2 · Cognitive Complexity · QuotioCLIBackend.apply (cognitive 16) · ×1
  • QuotioCLIBackend.apply (cognitive 16) Packages/QuotioCore/Sources/QuotioInfrastructure/QuotioCLI/QuotioCLIBackend.swift:871 — QuotioCLIBackend.apply has cognitive complexity 16 (threshold 15). Drivers by points: if/else 5 (8 pts), boolean chains 3, loops 2 (3 pts), ternaries 1 (2 pts) (nesting depth added 5). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · QuotioCompanionService.configure (cognitive 16) · ×1
  • QuotioCompanionService.configure (cognitive 16) Packages/QuotioCore/Sources/QuotioInfrastructure/QuotioCLI/QuotioCompanionService.swift:74 — QuotioCompanionService.configure has cognitive complexity 16 (threshold 15). Drivers by points: if/else 7 (11 pts), boolean chains 5 (nesting depth added 4). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · OAuthSheet.body (cognitive 16) · ×1
  • OAuthSheet.body (cognitive 16) Packages/QuotioCore/Sources/QuotioPresentation/Components/OAuthSheet.swift:51 — OAuthSheet.body has cognitive complexity 16 (threshold 15). Drivers by points: if/else 8 (9 pts), ternaries 2 (4 pts), boolean chains 3 (nesting depth added 3). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, 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 · StatusBarMenuSnapshotMapper.makeSnapshot (cognitive 16) · ×1
  • StatusBarMenuSnapshotMapper.makeSnapshot (cognitive 16) Packages/QuotioCore/Sources/QuotioPresentation/MenuBar/StatusBarMenuSnapshot.swift:141 — StatusBarMenuSnapshotMapper.makeSnapshot has cognitive complexity 16 (threshold 15). Drivers by points: boolean chains 10, if/else 4, ternaries 2. To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
D2 · Cognitive Complexity · DisplayNames.metricLabel (cognitive 16) · ×1
  • DisplayNames.metricLabel (cognitive 16) apps/ios/Sources/QuotioMobile/DisplayNames.swift:62 — DisplayNames.metricLabel has cognitive complexity 16 (threshold 15). Drivers by points: if/else 6 (8 pts), boolean chains 6, loops 1, ternaries 1 (nesting depth added 2). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition.
D2 · Cognitive Complexity · DisplayNames.resetHint (cognitive 16) · ×1
  • DisplayNames.resetHint (cognitive 16) apps/ios/Sources/QuotioMobile/DisplayNames.swift:166 — DisplayNames.resetHint has cognitive complexity 16 (threshold 15). Drivers by points: if/else 7 (9 pts), match/switch 1 (3 pts), ternaries 1 (3 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 · RootView.body (cognitive 16) · ×1
  • RootView.body (cognitive 16) apps/ios/QuotioIOS/RootView.swift:11 — RootView.body has cognitive complexity 16 (threshold 15). Drivers by points: boolean chains 6, if/else 4, ternaries 1 (3 pts), error handling 1 (2 pts), loops 1 (nesting depth added 3). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D32 · Data Compliance (PII/GDPR) · REDACTED · ×1
  • REDACTED
D35 · Change Coupling · Change-coupling hub · ×1
  • Change-coupling hub: QuotioCLIBackend.swift → QuotioCLIServerProcess.swift, AccountsScreenModel.swift, QuotaFeatureController.swift Packages/QuotioCore/Sources/QuotioInfrastructure/QuotioCLI/QuotioCLIBackend.swift — `Packages/QuotioCore/Sources/QuotioInfrastructure/QuotioCLI/QuotioCLIBackend.swift` changes together with 3 other files — `Packages/QuotioCore/Sources/QuotioInfrastructure/QuotioCLI/QuotioCLIServerProcess.swift`, `Packages/QuotioCore/Sources/QuotioPresentation/Accounts/AccountsScreenModel.swift`, `Packages/QuotioCore/Sources/QuotioPresentation/Quota/QuotaFeatureController.swift` — none of which declares a dependency on it: one file is the hub of 3 separate couplings, not 3 unrelated pairs. Read the hub first: if the others each duplicate a part of what it does, the shared concern belongs in ONE unit and extracting it clears every edge at once; if the hub is a registry, dispatcher or barrel that must name each of them, the coupling is structural and the question is whether that list can be discovered instead of enumerated. Fixing the hub is one change; breaking the couplings one pair at a time is 3.
D36 · Supply-chain Provenance & Signing · REDACTED · ×1
  • REDACTED
D4 · Code Duplication · Members sharing a duplicated core (4 members, 50+ identical tokens) · ×1
  • Members sharing a duplicated core (4 members, 50+ identical tokens) Packages/QuotioCore/Sources/QuotioInfrastructure/Accounts/LocalProxyOAuthAuthorizer.swift:233 — Packages/QuotioCore/Sources/QuotioInfrastructure/Accounts/LocalProxyOAuthAuthorizer.swift:233-255 | Packages/QuotioCore/Sources/QuotioPresentation/Shared/ProviderPresentation.swift:5-27 | Packages/QuotioCore/Sources/QuotioPresentation/Shared/ProviderPresentation.swift:29-51 | Packages/QuotioCore/Sources/QuotioPresentation/Shared/ProviderPresentation.swift:103-125 — 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 (39 corresponding lines) · ×1
  • Edited copy of a member (39 corresponding lines) Packages/QuotioCore/Sources/QuotioPresentation/MenuBar/StatusBarMenuRenderer.swift:1586 — Packages/QuotioCore/Sources/QuotioPresentation/MenuBar/StatusBarMenuRenderer.swift:1586-1624 | Packages/QuotioCore/Sources/QuotioPresentation/MenuBar/StatusBarMenuRenderer.swift:1626-1671 — These two members are one piece of code written twice and then edited apart: 39 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 (49 corresponding lines) · ×1
  • Edited copy of a member (49 corresponding lines) Packages/QuotioCore/Sources/QuotioPresentation/Settings/ProxyVersionManagerSheet.swift:281 — Packages/QuotioCore/Sources/QuotioPresentation/Settings/ProxyVersionManagerSheet.swift:281-329 | Packages/QuotioCore/Sources/QuotioPresentation/Settings/ProxyVersionManagerSheet.swift:338-392 — These two members are one piece of code written twice and then edited apart: 49 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 (28 corresponding lines) · ×1
  • Edited copy of a member (28 corresponding lines) Packages/QuotioCore/Sources/QuotioPresentation/Components/MenuBarBadge.swift:70 — Packages/QuotioCore/Sources/QuotioPresentation/Components/MenuBarBadge.swift:70-97 | Packages/QuotioCore/Sources/QuotioPresentation/MenuBar/MenuTooltipPresenter.swift:62-95 — These two members are one piece of code written twice and then edited apart: 28 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 (29 corresponding lines) · ×1
  • Edited copy of a member (29 corresponding lines) Packages/QuotioCore/Sources/QuotioPresentation/Components/MenuBarBadge.swift:40 — Packages/QuotioCore/Sources/QuotioPresentation/Components/MenuBarBadge.swift:40-68 | Packages/QuotioCore/Sources/QuotioPresentation/MenuBar/MenuTooltipPresenter.swift:32-60 — These two members are one piece of code written twice and then edited apart: 29 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 (24 corresponding lines) · ×1
  • Edited copy of a member (24 corresponding lines) apps/desktop/src/autostart.rs:19 — apps/desktop/src/autostart.rs:19-46 | apps/desktop/src/autostart.rs:62-85 — These two members are one piece of code written twice and then edited apart: 24 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 (18 corresponding lines) · ×1
  • Edited copy of a member (18 corresponding lines) apps/desktop/src/theme.rs:49 — apps/desktop/src/theme.rs:49-66 | apps/desktop/src/theme.rs:68-85 — These two members are one piece of code written twice and then edited apart: 18 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 (45 corresponding lines) · ×1
  • Edited copy of a member (45 corresponding lines) Packages/QuotioCore/Sources/QuotioPresentation/Components/ProviderAccountsGroup.swift:180 — Packages/QuotioCore/Sources/QuotioPresentation/Components/ProviderAccountsGroup.swift:180-229 | Packages/QuotioCore/Sources/QuotioPresentation/Components/ProviderDisclosureGroup.swift:100-144 — These two members are one piece of code written twice and then edited apart: 45 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 (13 corresponding lines) · ×1
  • Edited copy of a member (13 corresponding lines) apps/desktop/src/ui/settings/iphone.rs:33 — apps/desktop/src/ui/settings/iphone.rs:33-45 | apps/desktop/src/ui/settings/mod.rs:216-228 — These two members are one piece of code written twice and then edited apart: 13 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 (19 corresponding lines) · ×1
  • Edited copy of a member (19 corresponding lines) Packages/QuotioCore/Sources/QuotioPresentation/Components/GLMAPIKeySheet.swift:98 — Packages/QuotioCore/Sources/QuotioPresentation/Components/GLMAPIKeySheet.swift:98-116 | Packages/QuotioCore/Sources/QuotioPresentation/Components/GLMAPIKeySheet.swift:120-142 — These two members are one piece of code written twice and then edited apart: 19 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copy of a member (9 corresponding lines) · ×1
  • Edited copy of a member (9 corresponding lines) Packages/QuotioCore/Sources/QuotioPresentation/Settings/ProviderAccountsSection.swift:153 — Packages/QuotioCore/Sources/QuotioPresentation/Settings/ProviderAccountsSection.swift:153-162 | Packages/QuotioCore/Sources/QuotioPresentation/Settings/ProviderAccountsSection.swift:172-180 — These two members are one piece of code written twice and then edited apart: 9 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copies of one member (3 members, 13+ corresponding lines) · ×1
  • Edited copies of one member (3 members, 13+ corresponding lines) Packages/QuotioCore/Sources/QuotioPresentation/Components/QuotioButtonStyles.swift:74 — Packages/QuotioCore/Sources/QuotioPresentation/Components/QuotioButtonStyles.swift:74-88 | Packages/QuotioCore/Sources/QuotioPresentation/Components/QuotioButtonStyles.swift:115-127 | Packages/QuotioCore/Sources/QuotioPresentation/Components/QuotioButtonStyles.swift:154-167 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 13 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 (11 corresponding lines) · ×1
  • Edited copy of a member (11 corresponding lines) Packages/QuotioCore/Sources/QuotioApplication/Proxy/ProxyLifecycleController.swift:778 — Packages/QuotioCore/Sources/QuotioApplication/Proxy/ProxyLifecycleController.swift:778-788 | Packages/QuotioCore/Sources/QuotioApplication/Proxy/ProxyLifecycleController.swift:812-823 — These two members are one piece of code written twice and then edited apart: 11 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copy of a member (14 corresponding lines) · ×1
  • Edited copy of a member (14 corresponding lines) apps/desktop/src/ui/mod.rs:176 — apps/desktop/src/ui/mod.rs:176-189 | apps/desktop/src/ui/settings/connect.rs:695-713 — 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 copies of one member (3 members, 10+ corresponding lines) · ×1
  • Edited copies of one member (3 members, 10+ corresponding lines) Packages/QuotioCore/Sources/QuotioApplication/Accounts/OAuthFlow.swift:140 — Packages/QuotioCore/Sources/QuotioApplication/Accounts/OAuthFlow.swift:140-149 | Packages/QuotioCore/Sources/QuotioApplication/Warmup/WarmupSchedulerService.swift:128-137 | Packages/QuotioCore/Sources/QuotioInfrastructure/QuotioCLI/QuotioCLIBackend.swift:177-186 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 10 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 (4 corresponding lines) · ×1
  • Edited copy of a member (4 corresponding lines) Packages/QuotioCore/Sources/QuotioInfrastructure/CustomProviders/CustomProviderAdapters.swift:13 — Packages/QuotioCore/Sources/QuotioInfrastructure/CustomProviders/CustomProviderAdapters.swift:13-18 | Packages/QuotioCore/Sources/QuotioInfrastructure/Persistence/UserDefaultsWarpTokenRepository.swift:13-16 — These two members are one piece of code written twice and then edited apart: 4 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copy of a member (3 corresponding lines) · ×1
  • Edited copy of a member (3 corresponding lines) Packages/QuotioCore/Sources/QuotioInfrastructure/QuotioCLI/QuotioHostPresentationMapper.swift:183 — Packages/QuotioCore/Sources/QuotioInfrastructure/QuotioCLI/QuotioHostPresentationMapper.swift:183-185 | Packages/QuotioCore/Sources/QuotioPresentation/App/PresentationValues.swift:67-69 — These two members are one piece of code written twice and then edited apart: 3 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Duplicated block (19 lines × 2) · ×1
  • Duplicated block (19 lines × 2) Packages/QuotioCore/Sources/QuotioPresentation/Screens/AboutScreen.swift:321 — Packages/QuotioCore/Sources/QuotioPresentation/Screens/AboutScreen.swift:321-339 | Packages/QuotioCore/Sources/QuotioPresentation/Screens/AboutScreen.swift:482-500 — 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 `Packages/QuotioCore/Sources/QuotioPresentation/Screens/AboutScreen.swift:321` 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, `Packages/QuotioCore/Sources/QuotioPresentation/Screens/AboutScreen.swift:501` calls `sheet`, `ProxyVersionManagerSheet`, `environment` and `Packages/QuotioCore/Sources/QuotioPresentation/Screens/AboutScreen.swift:340` 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 (18 lines × 4) · ×1
  • Duplicated block (18 lines × 4) Packages/QuotioCore/Sources/QuotioInfrastructure/Accounts/LocalProxyOAuthAuthorizer.swift:235 — Packages/QuotioCore/Sources/QuotioInfrastructure/Accounts/LocalProxyOAuthAuthorizer.swift:235-252 | Packages/QuotioCore/Sources/QuotioPresentation/Shared/ProviderPresentation.swift:7-24 | Packages/QuotioCore/Sources/QuotioPresentation/Shared/ProviderPresentation.swift:31-48 | Packages/QuotioCore/Sources/QuotioPresentation/Shared/ProviderPresentation.swift:105-122 — there are 4 copies across 2 file(s) — more copies than files, so at least one file holds the block twice. Extract it once into a single shared function every call site can reach and call it from all 4 sites; resolving a subset leaves the remainder to drift apart. Read the line range as the matched WINDOW rather than a finished unit: at `Packages/QuotioCore/Sources/QuotioInfrastructure/Accounts/LocalProxyOAuthAuthorizer.swift:235` 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 (17 lines × 2) · ×1
  • Duplicated block (17 lines × 2) Packages/QuotioCore/Sources/QuotioPresentation/Components/ProviderAccountsGroup.swift:183 — Packages/QuotioCore/Sources/QuotioPresentation/Components/ProviderAccountsGroup.swift:183-199 | Packages/QuotioCore/Sources/QuotioPresentation/Components/ProviderDisclosureGroup.swift:104-120 — 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 `Packages/QuotioCore/Sources/QuotioPresentation/Components/ProviderAccountsGroup.swift:183` 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 lines × 2) · ×1
  • Duplicated block (16 lines × 2) Packages/QuotioCore/Sources/QuotioPresentation/Components/GLMAPIKeySheet.swift:77 — Packages/QuotioCore/Sources/QuotioPresentation/Components/GLMAPIKeySheet.swift:77-92 | Packages/QuotioCore/Sources/QuotioPresentation/Settings/ProxyVersionManagerSheet.swift:42-57 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `Packages/QuotioCore/Sources/QuotioPresentation/Components/GLMAPIKeySheet.swift:77` 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–13 lines × 2) · ×1
  • Duplicated block (11–13 lines × 2) Packages/QuotioCore/Sources/QuotioPresentation/Components/MenuBarBadge.swift:52 — Packages/QuotioCore/Sources/QuotioPresentation/Components/MenuBarBadge.swift:52-62 | Packages/QuotioCore/Sources/QuotioPresentation/MenuBar/MenuTooltipPresenter.swift:43-55 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `Packages/QuotioCore/Sources/QuotioPresentation/Components/MenuBarBadge.swift:52` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (8 lines × 3) · ×1
  • Duplicated block (8 lines × 3) Packages/QuotioCore/Sources/QuotioPresentation/Components/TunnelSheet.swift:163 — Packages/QuotioCore/Sources/QuotioPresentation/Components/TunnelSheet.swift:163-170 | Packages/QuotioCore/Sources/QuotioPresentation/Components/TunnelSheet.swift:223-230 | Packages/QuotioCore/Sources/QuotioPresentation/Components/TunnelSheet.swift:294-301 — 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 `Packages/QuotioCore/Sources/QuotioPresentation/Components/TunnelSheet.swift:163` 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 before the matched lines, `Packages/QuotioCore/Sources/QuotioPresentation/Components/TunnelSheet.swift:161` calls `background`, `Color`, `opacity` and `Packages/QuotioCore/Sources/QuotioPresentation/Components/TunnelSheet.swift:222` 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 (14–16 lines × 2) · ×1
  • Duplicated block (14–16 lines × 2) apps/desktop/src/app.rs:140 — apps/desktop/src/app.rs:140-153 | apps/desktop/src/app.rs:215-230 — 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 `apps/desktop/src/app.rs:140` 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 (15 lines × 2) · ×1
  • Duplicated block (15 lines × 2) apps/desktop/src/theme.rs:52 — apps/desktop/src/theme.rs:52-66 | apps/desktop/src/theme.rs:71-85 — 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 `apps/desktop/src/theme.rs:52` 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 (14 lines × 2) · ×1
  • Duplicated block (14 lines × 2) apps/desktop/src/ui/menu.rs:620 — apps/desktop/src/ui/menu.rs:620-633 | apps/desktop/src/ui/menu.rs:998-1011 — 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 `apps/desktop/src/ui/menu.rs:620` 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) · ×1
  • Duplicated block (13 lines × 2) apps/desktop/src/ui/menu.rs:551 — apps/desktop/src/ui/menu.rs:551-563 | apps/desktop/src/ui/menu.rs: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. Read the line range as the matched WINDOW rather than a finished unit: at `apps/desktop/src/ui/menu.rs:551` 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 × 3) · ×1
  • Duplicated block (5 lines × 3) apps/desktop/src/ui/settings/accounts.rs:1300 — apps/desktop/src/ui/settings/accounts.rs:1300-1304 | apps/desktop/src/ui/settings/iphone.rs:382-386 | apps/desktop/src/ui/settings/menu_bar.rs:387-391 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from all 3 call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `apps/desktop/src/ui/settings/accounts.rs:1300` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `apps/desktop/src/ui/settings/accounts.rs:1299` calls `clone` and `apps/desktop/src/ui/settings/iphone.rs:381` 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.
D4 · Code Duplication · Duplicated block (12 lines × 2) · ×1
  • Duplicated block (12 lines × 2) apps/desktop/src/ui/settings/connect.rs:1114 — apps/desktop/src/ui/settings/connect.rs:1114-1125 | apps/desktop/src/ui/settings/connect.rs:1129-1140 — 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 `apps/desktop/src/ui/settings/connect.rs:1114` 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.
Minor — 20 finding(s)
X7 · Silent fallback defaults · Silent fallback default in catch · ×4
  • Silent fallback default in catch Packages/QuotioCore/Sources/QuotioApplication/Warmup/WarmupSchedulerService.swift:294 — `models` turns every thrown error into `[]` — a data error becomes a silent behavior change with no trail. Log the error or let it propagate (`throws`). If that constant is the correct answer rather than a stand-in for a value that could not be read, say so in a comment at the `catch`, `guard` or `??`, or in the doc comment, and the row stops firing.
  • Silent fallback default in catch Packages/QuotioCore/Sources/QuotioInfrastructure/Credentials/FileAuthFileRepository.swift:27 — `scanAllAuthFiles` turns every thrown error into `[]` — a data error becomes a silent behavior change with no trail. Log the error or let it propagate (`throws`). If that constant is the correct answer rather than a stand-in for a value that could not be read, say so in a comment at the `catch`, `guard` or `??`, or in the doc comment, and the row stops firing.
  • Silent fallback default in catch Packages/QuotioCore/Sources/QuotioInfrastructure/CustomProviders/CustomProviderAdapters.swift:111 — `topLevelSectionRanges` turns every thrown error into `[]` — a data error becomes a silent behavior change with no trail. Log the error or let it propagate (`throws`). If that constant is the correct answer rather than a stand-in for a value that could not be read, say so in a comment at the `catch`, `guard` or `??`, or in the doc comment, and the row stops firing.
  • Silent fallback default in catch Packages/QuotioCore/Sources/QuotioInfrastructure/Proxy/FileProxyVersionRepository.swift:156 — `listInstalledVersions` turns every thrown error into `[]` — a data error becomes a silent behavior change with no trail. Log the error or let it propagate (`throws`). If that constant is the correct answer rather than a stand-in for a value that could not be read, say so in a comment at the `catch`, `guard` or `??`, or in the doc comment, and the row stops firing.
X10 · Duplicated predicate · Duplicated predicate · ×3
  • Duplicated predicate apps/desktop/src/ui/settings/connect.rs:1374 — `rest.is_empty() || rest.starts_with(['/', '\\'])` appears character-identically in 2 files — apps/desktop/src/ui/settings/connect.rs, apps/desktop/src/ui/settings/privacy.rs. 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 Packages/QuotioCore/Sources/QuotioApplication/CustomProviders/CustomProviderService.swift:60 — `components.path.isEmpty || components.path == "/"` appears character-identically in 2 files — Packages/QuotioCore/Sources/QuotioApplication/CustomProviders/CustomProviderService.swift, apps/ios/Sources/QuotioMobile/Connection.swift. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate Packages/QuotioCore/Sources/QuotioDomain/Tunnel/TunnelModels.swift:59 — `status == .starting || status == .stopping` appears character-identically in 2 files — Packages/QuotioCore/Sources/QuotioDomain/Tunnel/TunnelModels.swift, Packages/QuotioCore/Sources/QuotioPresentation/Components/TunnelStatusBadge.swift. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
D21 · Naming Consistency · `accountId` spells `Id` where 192 names in the project spell it `ID` · ×2
  • `accountId` spells `Id` where 192 names in the project spell it `ID` Packages/QuotioCore/Sources/QuotioInfrastructure/QuotioCLI/QuotioCLIBackend.swift:11 — 192 of 197 names in project Packages~QuotioCore~QuotioApplication spell the token `ID` (192 of 197; unit: names in project Packages~QuotioCore~QuotioApplication containing `ID`). Peers: AccountManaging.setDisabled(accountID) (Packages/QuotioCore/Sources/QuotioApplication/Accounts/AccountService.swift:97); AccountManaging.delete(accountID) (Packages/QuotioCore/Sources/QuotioApplication/Accounts/AccountService.swift:98); AccountManaging.setSourceEnabled(sourceID) (Packages/QuotioCore/Sources/QuotioApplication/Accounts/AccountService.swift:100); AccountManaging.unlinkSource(sourceID) (Packages/QuotioCore/Sources/QuotioApplication/Accounts/AccountService.swift:101); AccountManaging.saveAPIKey(providerID) (Packages/QuotioCore/Sources/QuotioApplication/Accounts/AccountService.swift:102). Rename to `accountID`. [rule N6]
  • `accountId` spells `Id` where 192 names in the project spell it `ID` Packages/QuotioCore/Sources/QuotioInfrastructure/QuotioCLI/QuotioCLIModels.swift:17 — 192 of 197 names in project Packages~QuotioCore~QuotioApplication spell the token `ID` (192 of 197; unit: names in project Packages~QuotioCore~QuotioApplication containing `ID`). Peers: AccountManaging.setDisabled(accountID) (Packages/QuotioCore/Sources/QuotioApplication/Accounts/AccountService.swift:97); AccountManaging.delete(accountID) (Packages/QuotioCore/Sources/QuotioApplication/Accounts/AccountService.swift:98); AccountManaging.setSourceEnabled(sourceID) (Packages/QuotioCore/Sources/QuotioApplication/Accounts/AccountService.swift:100); AccountManaging.unlinkSource(sourceID) (Packages/QuotioCore/Sources/QuotioApplication/Accounts/AccountService.swift:101); AccountManaging.saveAPIKey(providerID) (Packages/QuotioCore/Sources/QuotioApplication/Accounts/AccountService.swift:102). Rename to `accountID`. [rule N6]
D20 · ADR Quality · No ADRs found · ×1
  • No ADRs found apps/macos/Quotio.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 `apps/macos/Quotio.xcodeproj/project.pbxproj` makes this repository a deployable product (line 1).
D21 · Naming Consistency · `requestId` spells `Id` where 192 names in the project spell it `ID` · ×1
  • `requestId` spells `Id` where 192 names in the project spell it `ID` Packages/QuotioCore/Sources/QuotioApplication/Warmup/ProxyWarmupExecutor.swift:96 — 192 of 197 names in project Packages~QuotioCore~QuotioApplication spell the token `ID` (192 of 197; unit: names in project Packages~QuotioCore~QuotioApplication containing `ID`). Peers: AccountManaging.setDisabled(accountID) (Packages/QuotioCore/Sources/QuotioApplication/Accounts/AccountService.swift:97); AccountManaging.delete(accountID) (Packages/QuotioCore/Sources/QuotioApplication/Accounts/AccountService.swift:98); AccountManaging.setSourceEnabled(sourceID) (Packages/QuotioCore/Sources/QuotioApplication/Accounts/AccountService.swift:100); AccountManaging.unlinkSource(sourceID) (Packages/QuotioCore/Sources/QuotioApplication/Accounts/AccountService.swift:101); AccountManaging.saveAPIKey(providerID) (Packages/QuotioCore/Sources/QuotioApplication/Accounts/AccountService.swift:102). Rename to `requestID`. [rule N6]
D21 · Naming Consistency · `sessionId` spells `Id` where 192 names in the project spell it `ID` · ×1
  • `sessionId` spells `Id` where 192 names in the project spell it `ID` Packages/QuotioCore/Sources/QuotioApplication/Warmup/ProxyWarmupExecutor.swift:103 — 192 of 197 names in project Packages~QuotioCore~QuotioApplication spell the token `ID` (192 of 197; unit: names in project Packages~QuotioCore~QuotioApplication containing `ID`). Peers: AccountManaging.setDisabled(accountID) (Packages/QuotioCore/Sources/QuotioApplication/Accounts/AccountService.swift:97); AccountManaging.delete(accountID) (Packages/QuotioCore/Sources/QuotioApplication/Accounts/AccountService.swift:98); AccountManaging.setSourceEnabled(sourceID) (Packages/QuotioCore/Sources/QuotioApplication/Accounts/AccountService.swift:100); AccountManaging.unlinkSource(sourceID) (Packages/QuotioCore/Sources/QuotioApplication/Accounts/AccountService.swift:101); AccountManaging.saveAPIKey(providerID) (Packages/QuotioCore/Sources/QuotioApplication/Accounts/AccountService.swift:102). Rename to `sessionID`. [rule N6]
D21 · Naming Consistency · `tierId` spells `Id` where 192 names in the project spell it `ID` · ×1
  • `tierId` spells `Id` where 192 names in the project spell it `ID` Packages/QuotioCore/Sources/QuotioDomain/Quota/QuotaModels.swift:378 — 192 of 197 names in project Packages~QuotioCore~QuotioApplication spell the token `ID` (192 of 197; unit: names in project Packages~QuotioCore~QuotioApplication containing `ID`). Peers: AccountManaging.setDisabled(accountID) (Packages/QuotioCore/Sources/QuotioApplication/Accounts/AccountService.swift:97); AccountManaging.delete(accountID) (Packages/QuotioCore/Sources/QuotioApplication/Accounts/AccountService.swift:98); AccountManaging.setSourceEnabled(sourceID) (Packages/QuotioCore/Sources/QuotioApplication/Accounts/AccountService.swift:100); AccountManaging.unlinkSource(sourceID) (Packages/QuotioCore/Sources/QuotioApplication/Accounts/AccountService.swift:101); AccountManaging.saveAPIKey(providerID) (Packages/QuotioCore/Sources/QuotioApplication/Accounts/AccountService.swift:102). Rename to `tierID`. [rule N6]
D26 · Project Cohesion · Projects may be oversized for their cohesion · ×1
  • Projects may be oversized for their cohesion — 1 of 6 project(s) overshoot their size bounds, lowering Project Cohesion to 6.7/10. The most over is `Packages/QuotioCore` (28069 LoC, 589 module-visible types across 52 directories). Review these for cohesion — draw the boundary inside the module first (group each responsibility into its own package or directory and keep the cross-boundary members non-public), since splitting a published package moves types between packages and breaks consumers.
D27 · Navigability · High interface indirection · ×1
  • High interface indirection — 38 % of calls go through an interface — tracing a call means resolving the implementation each hop. Prefer concrete types where there's a single implementation.
D36 · Supply-chain Provenance & Signing · REDACTED · ×1
  • REDACTED
D36 · Supply-chain Provenance & Signing · REDACTED · ×1
  • REDACTED
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.
P2 · Observability · Logging is not universal · ×1
  • Logging is not universal — Only 4/6 runnable modules use logging (modules with no entry point or server are excluded — they are libraries a runnable module hosts). Silent: `.`, `apps/ios`.
X7 · Silent fallback defaults · Silent fallback default on Err · ×1
  • Silent fallback default on Err apps/cli/src/output/text.rs:41 — `timestamp` turns every `Err` into `"unknown".into()` — a failure becomes a plausible value and a silent behavior change with no trail. Log the error or propagate it with `?`. If that constant is the correct answer rather than a stand-in for a value that could not be read, say so in a comment on the arm or in the doc comment, and the row stops firing.
Minor — 2 finding(s)
D10 · Test Quality · Skipped (documented) · ×1
  • Skipped (documented): liveRustTLSUsesPairedTrustWithAppTransportSecurity apps/ios/QuotioIOSUnitTests/HostStoreTests.swift:169 — Skipped with a documented reason — a deferral, not lazy debt: conditionally enabled — runs only when its .enabled(if:) condition holds
D12 · Dependency Hygiene · Outdated · ×1
  • Outdated: sparkle — `sparkle` is resolved at 2.8.1, but 2.10.1 is the newest release tagged on https://github.com/sparkle-project/Sparkle within the same major. SwiftPM resolves from git tags, and a `from:` requirement admits every release below the next major — so `swift package update sparkle` reaches this one with no change to Package.swift.

Appendix B — Reproduction & audit trail

Every external tool invocation behind a deep-scan dimension — the tool, its captured version, the exact command, how many findings it yielded, and a link to the retained raw output. To reproduce any finding: check out the same commit and run the command shown (repo-relative — never an absolute scratch path). The complete raw scanner output is retained verbatim under artifacts/raw/ (indexed in artifacts/raw/index.json); per-invocation exit codes and wall-clock durations are in sidecar.json — kept out of this table so the rendered report stays byte-identical across runs of the same commit.

DimensionToolVersionCommandFindingsRaw output
D28 · Secrets (history)gitleaks—gitleaks detect --no-banner --config /opt/gitleaks-rules/canine-gitleaks.toml --report-format json --report-path /tmp/watchdog-gitleaks-dcfafae0430d4a908a5109ab0bae9641/history.json --exit-code 0 --source .7artifacts/raw/gitleaks-history.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-dcfafae0430d4a908a5109ab0bae9641/tree.json --exit-code 0 --source .2artifacts/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 --exclude .codex .2artifacts/raw/semgrep.json
D30 · Dependency Vulnerabilitiestrivy—trivy fs --scanners vuln --format json --quiet --severity CRITICAL,HIGH,MEDIUM,LOW --skip-dirs **/bin/** --skip-dirs **/obj/** .15artifacts/raw/trivy-fs.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 --config /opt/semgrep-rules/gdpr.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 --exclude .codex .1artifacts/raw/semgrep-gdpr.json
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 Dependenciestrivy—trivy fs --scanners vuln --format json --quiet --severity CRITICAL,HIGH,MEDIUM,LOW --skip-dirs **/bin/** --skip-dirs **/obj/** .0artifacts/raw/trivy-fs.json

Run 01a1dc13-3099-7da4-b8a8-0231ad47e065 · 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