Public report of blokadaorg/blokada, published 12 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.3). 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, 12 November 2026, 05:52 UTC · Survey ID cd_d2483cc361ed48aaa9dba8afa4d2ff56

blokadaorg/blokada

Measured 12 November 2026, 05:51 UTC, at code version b151089

CAI score 61out of 100 Adequate
CriticalWeakAdequateStrongExemplary
Up 1 since the last survey

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

A medium codebase: 69,492 lines of product code in 8 projects, tests not counted · Estimated rebuild effort: about 0.8 person-years · Weakest lens: Code Health, 58

Findings by how serious they are

57 critical 498 serious 34 minor

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

This survey was produced by

Assert small markCanine Code Analyzer
Producer
Canine Development
Analyzer
Canine Code Analyzer engine 1.0.0
Measured
12 November 2026, 05:51 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 ▸

73of 73 dimensions measured by tools.
563of 589 findings point to an exact file and line, so you can open each one in the code. The other 26 concern the repository as a whole, such as missing documentation.
73dimensions across 7 lenses, read from 69,492 lines of product code in 8 projects.
Chapters

Executive summary

blokadaorg/blokada falls short of our standard for production, held back most by its Code Health lens, the quality of the code itself. It scores 61 out of 100 and is rated Adequate, and 44 of its 57 critical findings are security problems.

Code Health, at 58, is the weakest lens and counts most in the score. The best first step is removing the blocking calls, worth about 3 points. Adding type checking would lift Code Health itself, worth about 2 points. Raising Code Health to 70 would lift the score to about 64.

Thirty-eight pipeline tools are referenced by a changeable name, so the build pipeline can be tampered with. Four passwords or keys are open to anyone who can read the repository, and one automatic update takes new releases before a bad one can be spotted. Pinning each tool to an exact version, replacing each exposed password or key and setting a waiting period for automatic updates would close these risks. The unsafe setting in infrastructure or container files needs changing to safe values. Moving the business rules into the object that owns the data would take care of the 13 business objects that only hold data.

The product code is 69,492 lines, about €120,000 to rebuild.

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

How the score is built: what each lens counts 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.
Code Health 58 · counts for 46%Performance 60 · counts for 25%Production Readiness 65 · counts for 14%Security and Compliance 66 · counts for 8%Maturity 71 · counts for 4%Domain Modelling 80 · counts for 2%Architecture 93 · counts for 1%

If Code Health rose from 58 to 70, the lowest score rated Strong, the score would rise from 61 to about 64.

Code composition: what the lines of code are
Product code 73%Tests 27%
New since the last survey: 148 findings

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

  • Cyclomatic Complexity · DomainDetailSectionState._fetchSubdomains (cyclomatic 17) common/lib/src/features/stats/ui/domain_detail_section.dart
  • Cyclomatic Complexity · V6FiltersSectionState.build (cyclomatic 16) common/lib/src/app_variants/v6/widget/filters_section.dart
  • Cyclomatic Complexity · RadialChart.build (cyclomatic 16) common/lib/src/app_variants/v6/widget/home/stats/radial_chart.dart
  • Cyclomatic Complexity · NotificationAlarmReceiver.onReceive (cyclomatic 16) android/app/src/main/java/service/NotificationService.kt
  • Cognitive Complexity · V6FiltersSectionState.build (cognitive 22) common/lib/src/app_variants/v6/widget/filters_section.dart
  • Cognitive Complexity · platform.scrollIntoView (cognitive 17) automation/appium/wdio/src/support/platform.ts
  • Code Duplication · Members sharing a duplicated core (4 members, 50+ identical tokens) common/lib/src/features/plus/ui/device_limit_sheet.dart
  • Code Duplication · Edited copy of a member (60 corresponding lines) ios/Family/ContentView.swift
  • Code Duplication · Edited copy of a member (73 corresponding lines) common/lib/src/features/private_dns/ui/private_dns_setting_guide.dart
  • Code Duplication · Edited copy of a member (54 corresponding lines) common/lib/src/features/filter/domain/actor.dart
  • Code Duplication · Edited copies of one member (3 members, 41+ corresponding lines) ios/App/Binding/CommonBinding.swift
  • Code Duplication · Edited copy of a member (48 corresponding lines) common/lib/src/features/stats/ui/domain_detail_section.dart
  • Code Duplication · Edited copy of a member (44 corresponding lines) android/app/src/six/kotlin/ui/AdaptyPaymentFragment.kt
  • Code Duplication · Edited copy of a member (46 corresponding lines) common/lib/src/features/stats/ui/domain_detail_section.dart
  • Code Duplication · Edited copy of a member (32 corresponding lines) ios/Family/SplashView.swift
  • Code Duplication · Edited copy of a member (24 corresponding lines) common/lib/src/features/journal/domain/api.dart
  • Code Duplication · Edited copy of a member (32 corresponding lines) common/lib/src/app_variants/family/widget/main_screen.dart
  • Code Duplication · Edited copy of a member (27 corresponding lines) common/lib/src/app_variants/family/module/device_v3/actor.dart
  • Code Duplication · Edited copy of a member (24 corresponding lines) common/lib/src/features/stats/ui/stats_filter_device.dart
  • Code Duplication · Edited copy of a member (21 corresponding lines) ios/App/ServiceImpl/LoggerSaver.swift
  • Code Duplication · Edited copy of a member (33 corresponding lines) common/lib/src/app_variants/family/widget/home/device/home_device_header.dart
  • Code Duplication · Edited copy of a member (15 corresponding lines) common/lib/src/app_variants/family/module/device_v3/json.dart
  • Code Duplication · Edited copies of one member (3 members, 23+ corresponding lines) common/lib/src/app_variants/family/widget/home/home_devices.dart
  • Code Duplication · Edited copies of one member (3 members, 23+ corresponding lines) common/lib/mock/widget/background.dart
  • Code Duplication · Edited copy of a member (26 corresponding lines) common/lib/src/app_variants/family/widget/home/big_icon.dart
  • Code Duplication · Edited copy of a member (19 corresponding lines) android/app/src/family/kotlin/binding/FamilyBinding.kt
  • Code Duplication · Edited copy of a member (18 corresponding lines) common/lib/src/features/notification/domain/actor.dart
  • Code Duplication · Edited copy of a member (12 corresponding lines) ios/WireguardCopiedFiles/WgLoggerForApp.swift
  • Code Duplication · Edited copy of a member (14 corresponding lines) common/lib/src/core/persistence/value.dart
  • Code Duplication · Edited copy of a member (19 corresponding lines) common/lib/src/core/value.dart
  • Code Duplication · Edited copy of a member (15 corresponding lines) common/lib/src/platform/stats/stats.dart
  • Code Duplication · Edited copy of a member (19 corresponding lines) ios/App/UI/Main/AccountChangeView.swift
  • Code Duplication · Edited copy of a member (14 corresponding lines) common/lib/src/features/plus/domain/gateway/actor.dart
  • Code Duplication · Edited copies of one member (3 members, 13+ corresponding lines) common/lib/src/platform/command/command.dart
  • Code Duplication · Edited copy of a member (14 corresponding lines) common/lib/src/platform/app/start/start.dart
  • Code Duplication · Edited copy of a member (12 corresponding lines) common/lib/src/app_variants/family/module/schedule/json.dart
  • Code Duplication · Edited copy of a member (18 corresponding lines) common/lib/src/features/support/domain/json.dart
  • Code Duplication · Edited copy of a member (8 corresponding lines) common/lib/src/features/notification/domain/actor.dart
  • Code Duplication · Edited copy of a member (6 corresponding lines) common/lib/src/core/persistence/persistence.dart
  • Code Duplication · Edited copy of a member (13 corresponding lines) common/lib/src/features/plus/domain/vpn/actor.dart
  • Code Duplication · Edited copy of a member (3 corresponding lines) ios/App/Assets/UiGen.swift
  • Code Duplication · Edited copy of a member (15 corresponding lines) common/lib/src/core/value.dart
  • Code Duplication · Edited copy of a member (14 corresponding lines) common/lib/src/features/payment/domain/adapty.dart
  • Code Duplication · Edited copies of one member (4 members, 12+ corresponding lines) common/lib/src/features/journal/domain/api.dart
  • Code Duplication · Edited copy of a member (11 corresponding lines) common/lib/src/core/value.dart
  • Code Duplication · Edited copy of a member (15 corresponding lines) common/lib/src/features/customlist/domain/actor.dart
  • Code Duplication · Edited copy of a member (11 corresponding lines) ios/App/Service/SceneDelegate.swift
  • Code Duplication · Edited copies of one member (3 members, 12+ corresponding lines) common/lib/src/features/journal/domain/api.dart
  • Code Duplication · Edited copies of one member (3 members, 8+ corresponding lines) common/lib/src/platform/account/account.dart
  • Code Duplication · Edited copies of one member (3 members, 14+ corresponding lines) android/app/src/main/java/binding/CommonBinding.kt
  • Code Duplication · Edited copy of a member (8 corresponding lines) android/app/wireguard-android/ui/src/main/java/com/wireguard/android/configStore/FileConfigStore.kt
  • Code Duplication · Edited copy of a member (8 corresponding lines) ios/App/Binding/CommonBinding.swift
  • Code Duplication · Edited copy of a member (9 corresponding lines) common/lib/src/features/notification/domain/api.dart
  • Code Duplication · Edited copy of a member (11 corresponding lines) common/lib/src/platform/app/app.dart
  • Code Duplication · Edited copies of one member (3 members, 8+ corresponding lines) ios/App/Binding/Perm/PermBinding.swift
  • Code Duplication · Edited copy of a member (3 corresponding lines) ios/App/Util/BlockaLogger.swift
  • Code Duplication · Edited copy of a member (14 corresponding lines) common/lib/src/platform/plus/channel.dart
  • Code Duplication · Edited copies of one member (3 members, 8+ corresponding lines) ios/App/Binding/CommandsBinding.swift
  • Code Duplication · Edited copy of a member (9 corresponding lines) common/lib/src/platform/stats/api.dart
  • Code Duplication · Edited copy of a member (8 corresponding lines) common/lib/src/app_variants/family/module/device_v3/api.dart
  • Code Duplication · Edited copy of a member (9 corresponding lines) common/lib/src/app_variants/family/module/profile/api.dart
  • Code Duplication · Edited copy of a member (8 corresponding lines) common/lib/src/features/stats/ui/stats_filter.dart
  • Code Duplication · Edited copy of a member (8 corresponding lines) ios/WireguardCopiedFiles/RecentTunnelsTracker.swift
  • Code Duplication · Edited copies of one member (3 members, 9+ corresponding lines) common/lib/src/app_variants/family/module/device_v3/json.dart
  • Code Duplication · Edited copies of one member (3 members, 7+ corresponding lines) ios/App/Binding/CommandsBinding.swift
  • Code Duplication · Edited copy of a member (9 corresponding lines) ios/App/Binding/Vpn/NetxServiceIn.swift
  • Code Duplication · Edited copy of a member (7 corresponding lines) common/lib/src/features/journal/domain/actor.dart
  • Code Duplication · Edited copy of a member (9 corresponding lines) common/lib/src/app_variants/family/module/auth/json.dart
  • Code Duplication · Edited copy of a member (7 corresponding lines) common/lib/src/app_variants/family/module/auth/json.dart
  • Code Duplication · Edited copy of a member (8 corresponding lines) common/lib/src/platform/core/command.dart
  • Code Duplication · Edited copy of a member (6 corresponding lines) common/lib/src/platform/filter/actor.dart
  • Code Duplication · Edited copy of a member (6 corresponding lines) common/lib/src/app_variants/family/module/stats/json.dart
  • Code Duplication · Edited copy of a member (4 corresponding lines) ios/WireguardCopiedFiles/WgLoggerForApp.swift
  • Code Duplication · Edited copies of one member (4 members, 8+ corresponding lines) common/lib/src/app_variants/family/module/qrscan/qrscan.dart
  • Code Duplication · Edited copy of a member (4 corresponding lines) ios/WireguardCopiedFiles/WgLoggerForApp.swift
  • Code Duplication · Edited copy of a member (4 corresponding lines) common/lib/src/app_variants/family/module/stats/json.dart
  • Code Duplication · Edited copy of a member (7 corresponding lines) common/lib/src/shared/layout/detail_route.dart
  • Code Duplication · Edited copy of a member (3 corresponding lines) ios/App/Binding/CommonBinding.swift
  • Code Duplication · Edited copy of a member (4 corresponding lines) ios/App/Binding/CommonBinding.swift
  • Code Duplication · Edited copy of a member (5 corresponding lines) common/lib/src/app_variants/v6/widget/filters_section.dart
  • Code Duplication · Edited copy of a member (6 corresponding lines) common/lib/src/features/onboard/ui/onboard_screen.dart
  • Code Duplication · Edited copy of a member (3 corresponding lines) ios/App/Binding/UrlBinding.swift
  • Code Duplication · Edited copy of a member (3 corresponding lines) common/lib/src/app_variants/family/module/schedule/json.dart
  • Code Duplication · Edited copy of a member (5 corresponding lines) common/lib/src/app_variants/family/module/device_v3/actor.dart
  • Code Duplication · Edited copy of a member (4 corresponding lines) common/lib/src/app_variants/v6/widget/filters_section.dart
  • Code Duplication · Edited copies of one member (3 members, 4+ corresponding lines) common/lib/src/features/notification/domain/command.dart
  • Code Duplication · Edited copies of one member (3 members, 4+ corresponding lines) common/lib/src/features/notification/domain/command.dart
  • Code Duplication · Edited copy of a member (9 corresponding lines) android/app/src/family/kotlin/ui/MainApplication.kt
  • Code Duplication · Edited copies of one member (3 members, 3+ corresponding lines) ios/App/Binding/Vpn/NetxServiceIn.swift
  • Code Duplication · Duplicated block (32–33 lines × 2) common/lib/src/features/private_dns/ui/private_dns_sheet_ios.dart
  • Code Duplication · Duplicated block (28–30 lines × 2) common/lib/src/features/private_dns/ui/private_dns_sheet_ios.dart
  • Code Duplication · Duplicated block (23 lines × 2) common/lib/src/features/stats/ui/recent_activity.dart
  • Code Duplication · Duplicated block (19–21 lines × 3) common/lib/src/app_variants/family/widget/home/qr_scan_sheet_macos.dart
  • Code Duplication · Duplicated block (17–18 lines × 3) common/lib/src/app_variants/v6/widget/freemium/weekly_refresh_sheet.dart
  • Code Duplication · Duplicated block (17–18 lines × 3) common/lib/src/features/settings/ui/exceptions_section.dart
  • Code Duplication · Duplicated block (17–18 lines × 3) common/lib/src/features/settings/ui/exceptions_section.dart
  • Code Duplication · Duplicated block (18 lines × 2) common/lib/src/features/stats/ui/domain_detail_section.dart
  • Code Duplication · Duplicated block (17 lines × 4) common/lib/src/features/plus/ui/device_limit_sheet.dart
  • Code Duplication · Duplicated block (16 lines × 4) common/lib/src/app_variants/family/widget/home/qr_scan_sheet_macos.dart
  • Code Duplication · Duplicated block (13–15 lines × 2) common/lib/src/features/stats/ui/horizontal_radial_segment.dart

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: 70 findings

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

  • Cognitive Complexity · StatsDeltaStore.deltasFor (cognitive 18) common/lib/src/platform/stats/delta_store.dart
  • Cognitive Complexity · Handler.read_body (cognitive 16) tools/emu/pod/server.py
  • God Classes · MethodTooLong: PowerButtonPainter.paint common/lib/src/app_variants/v6/widget/home/power_button.dart
  • God Classes · FileTooLong: home/power_button.dart common/lib/src/app_variants/v6/widget/home/power_button.dart
  • God Classes · MethodTooLong: PrivateDnsSheetAndroidState.build common/lib/src/features/private_dns/ui/private_dns_sheet_android.dart
  • Code Duplication · Members sharing a duplicated core (6 members, 50+ identical tokens) common/lib/src/features/onboard/ui/onboard_screen.dart
  • Code Duplication · Duplicated block (23–24 lines × 2) common/lib/src/features/private_dns/ui/private_dns_sheet_ios.dart
  • Code Duplication · Duplicated block (23 lines × 3) common/lib/src/app_variants/v6/widget/freemium/weekly_refresh_sheet.dart
  • Code Duplication · Duplicated block (22 lines × 3) common/lib/src/features/plus/ui/device_limit_sheet.dart
  • Code Duplication · Duplicated block (20–22 lines × 3) common/lib/src/features/private_dns/ui/private_dns_sheet_android.dart
  • Code Duplication · Duplicated block (21 lines × 2) common/lib/src/features/onboard/ui/onboard_screen.dart
  • Code Duplication · Duplicated block (20–21 lines × 2) common/lib/src/features/settings/ui/exceptions_section.dart
  • Code Duplication · Duplicated block (20–21 lines × 2) common/lib/src/features/settings/ui/exceptions_section.dart
  • Code Duplication · Duplicated block (20 lines × 2) common/lib/src/features/stats/ui/domain_detail_section.dart
  • Code Duplication · Duplicated block (19 lines × 3) common/lib/src/app_variants/family/widget/home/qr_scan_sheet_macos.dart
  • Code Duplication · Duplicated block (18 lines × 2) common/lib/src/features/private_dns/ui/private_dns_sheet_ios.dart
  • Code Duplication · Duplicated block (18 lines × 2) common/lib/src/shared/ui/top_bar.dart
  • Code Duplication · Duplicated block (17 lines × 3) common/lib/src/app_variants/family/widget/home/qr_scan_sheet_macos.dart
  • Code Duplication · Duplicated block (16 lines × 6) common/lib/src/features/onboard/ui/onboard_screen.dart
  • Code Duplication · Duplicated block (16 lines × 4) common/lib/src/app_variants/family/widget/home/qr_scan_sheet_macos.dart
  • Code Duplication · Duplicated block (13–15 lines × 4) common/lib/src/app_variants/family/widget/home/qr_scan_sheet_macos.dart
  • Code Duplication · Duplicated block (15 lines × 2) common/lib/src/app_variants/v6/widget/freemium/weekly_refresh_sheet.dart
  • Code Duplication · Duplicated block (15 lines × 2) common/lib/src/features/onboard/ui/background.dart
  • Code Duplication · Duplicated block (14 lines × 2) common/lib/src/features/stats/ui/recent_activity.dart
  • Code Duplication · Duplicated block (12 lines × 3) common/lib/src/features/private_dns/ui/private_dns_sheet_android.dart
  • Code Duplication · Duplicated block (10–11 lines × 3) common/lib/src/features/stats/ui/domain_detail_section.dart
  • Code Duplication · Duplicated block (11 lines × 2) common/lib/src/features/lock/domain/actor.dart
  • Code Duplication · Duplicated block (10 lines × 2) common/lib/src/app_variants/v6/widget/home/stats/radial_chart.dart
  • Code Duplication · Duplicated block (10 lines × 2) common/lib/src/features/stats/ui/domain_detail_section.dart
  • Code Duplication · Duplicated block (9 lines × 2) common/lib/src/features/notification/domain/weekly_report.dart
  • Code Duplication · Duplicated block (8–9 lines × 2) common/lib/src/features/stats/ui/stats_filter.dart
  • Code Duplication · Duplicated block (8 lines × 3) common/lib/src/features/notification/domain/weekly_report.dart
  • Code Duplication · Duplicated block (8 lines × 2) common/lib/src/app_variants/v6/widget/home/power_button.dart
  • Code Duplication · Duplicated block (8 lines × 2) common/lib/src/app_variants/v6/widget/home/power_button.dart
  • Code Duplication · Duplicated block (14 lines × 2) common/lib/src/app_variants/v6/widget/activity_screen.dart
  • Code Duplication · Duplicated block (9 lines × 2) common/lib/src/app_variants/family/module/family/family.dart
  • Code Duplication · Duplicated block (33–34 lines × 2) android/app/src/six/kotlin/ui/AdaptyPaymentFragment.kt
  • Code Duplication · Duplicated block (11 lines × 2) android/app/src/family/kotlin/service/UncaughtExceptionService.kt
  • Code Duplication · Duplicated block (13 lines × 2) android/app/src/family/kotlin/service/Flavor.kt
  • Code Duplication · Duplicated block (5 lines × 2) android/app/src/main/java/binding/CoreBinding.kt
  • Code Duplication · Duplicated block (10 lines × 2) scripts/version.py
  • Code Duplication · Duplicated block (18 lines × 2) ios/Family/ContentView.swift
  • Code Duplication · Duplicated block (17 lines × 2) ios/Family/ContentView.swift
  • Code Duplication · Duplicated block (15–16 lines × 2) ios/App/Service/PrivateDnsService.swift
  • Code Duplication · Duplicated block (14–15 lines × 2) ios/App/Binding/Notification.swift
  • Code Duplication · Duplicated block (8 lines × 2) ios/App/Binding/CommonBinding.swift
  • Code Duplication · Duplicated block (8 lines × 2) ios/Family/HomeViewModel.swift
  • REDACTED Scanning · Leaked secret: hardcoded-credential scripts/test-build-number.sh
  • REDACTED Scanning · Leaked secret: hardcoded-credential REDACTED
  • REDACTED Scanning · Leaked secret: high-entropy-secret common/lib/src/features/payment/domain/adapty_key.dart
  • REDACTED Scanning · Leaked secret: high-entropy-secret common/lib/src/features/payment/domain/adapty_key.dart
  • Churn × Complexity Hotspots · Repeated repair: android/app/src/main/java/ui/MainActivity.kt android/app/src/main/java/ui/MainActivity.kt
  • Secrets (history) · High secret: REDACTED REDACTED
  • Static Analysis (SAST) · High: REDACTED REDACTED
  • Static Analysis (SAST) · Medium: REDACTED android/app/src/family/AndroidManifest.xml
  • Static Analysis (SAST) · Medium: watchdog-regexp-from-parameter-ts automation/appium/wdio/scripts/junit-summary.mjs
  • Dependency Vulnerabilities · Medium CVE: [GHSA redacted] REDACTED
  • Code Duplication · Duplicated block (13 lines × 2 locations) automation/appium/wdio/src/flows/home.ts
  • Code Duplication · Duplicated block (12 lines × 2 locations) automation/appium/wdio/src/flows/app.ts
  • Code Duplication · Duplicated block (7 lines × 2 locations) automation/appium/wdio/src/flows/account.ts
  • Test Coverage · No test reaches this file ios/BlockaWebExtension/Resources/popup.js
  • Test Coverage · No test reaches this file scripts/check-adapty-fallback-version.mjs
  • Test Coverage · No test reaches this file automation/appium/wdio/scripts/lib/capabilities.mjs
  • Dependency Hygiene · Unlisted import '@wdio/types' automation/appium/wdio/wdio.conf.ts
  • Exception handling · Swallowed exception (caught, then discarded) android/app/src/main/java/ui/CommandActivity.kt
  • Exception handling · Swallowed exception (empty catch) automation/appium/wdio/src/flows/alerts.ts
  • Exception handling · Swallowed exception (empty catch) automation/appium/wdio/src/flows/alerts.ts
  • Exception handling · Swallowed exception (empty catch) automation/appium/wdio/src/flows/alerts.ts
  • Exception handling · Swallowed exception (empty catch) automation/appium/wdio/src/flows/alerts.ts
  • Exception handling · Swallowed exception (empty catch) automation/appium/wdio/src/flows/account.ts
Rebuild cost: about €120,000 · Estimate
Cost to rebuild€40,000 to €200,000, for 665 to 2,109 hours of work, about 0.8 person-years for 1 to 2 engineers
Difficulty of the problemStandard, judged from the kind of software and how it is built. Code that solves a harder problem, such as payments or medical bookings, costs more per line to write.
Quality factor×0.8 at a score of 61. Better code takes more work to write, so the factor is ×1.0 at a score of 70, lower below it and higher above it.
SizeMedium: 69,492 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
TypeScript/JavaScript: use the promise APIs (fs/promises, a promisified child_process.execFile, the async zlib/crypto functions) and await them instead of the *Sync variants.
Raises the score by about 3 points · Medium effort · Async & latency hygiene
2
Migrate the remaining .js/.jsx files to TypeScript.
Raises the score by about 2 points · Medium effort · Type Safety
3
Thread an AbortSignal through async functions that make requests, so the work stops when its caller gives up.
Raises the score by about 2 points · Medium effort · Cancellation propagation

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 €120,000 to build again, about 0.8 person-years of work. Its weakest lens is Code Health, at 58 (Adequate). Code Health is about how easy the code is to read and change safely, and code that is hard to read is slow and risky to change, so every future change costs more than it should. Because the weakest lens counts most in the score, work on Code Health also moves the score most.
Based on: the rebuild estimate · the Code Health grade · how much each lens counts
What to do: Start with the Code Health actions in Top priorities.
If you do one thing first · First action
TypeScript/JavaScript: use the promise APIs (fs/promises, a promisified child_process.execFile, the async zlib/crypto functions) and await them instead of the *Sync variants. Of all the actions in this report, it raises the score most for the work it takes: about 3 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 :app :app @blokada/wdio-tests wdio-tests FamilyMocked FamilyMocked IOS (ios/IOS.xcodeproj) xcodeproj) Mocked Mocked WireGuardNetworkExtensioniOS WireGuardNetworkExtensioniOS common common six-android six-android

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.

76 modules, with 59 dependencies between them. 2 loops run through 7 of the modules, marked above the diagonal.

The table shows the 40 modules with the most connections; 36 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 automation.appium.wdio.src.flows.account2 automation.appium.wdio.src.flows.nav3 automation.appium.wdio.src.support.golden4 com.wireguard.android.configStore5 com.wireguard.android.model.TunnelComparator.NaturalSortString6 com.wireguard.android.util.BiometricAuthenticator7 service.ConnectivityService8 utils9 automation.appium.wdio.src.flows10 automation.appium.wdio.src.support11 com.wireguard.android.databinding.ObservableSortedKeyedArrayList12 com.wireguard.android.model.TunnelComparator13 com.wireguard.android.util14 com.wireguard.android.util.BiometricAuthenticator.Result15 model16 repository.src17 com.wireguard.android.databinding18 model.AccountType19 model.AppState20 model.Dns21 model.NetworkDescriptor22 model.NetworkType23 model.Tab24 model.TunnelStatus25 service26 com.wireguard.android.model27 repository28 service.AccountRescuePayload29 service.Sheet30 service.WeeklyReportPayload31 common~vendor~adapty_flutter~ios~adapty_flutter~adapty_flutter32 engine33 binding34 engine.EngineConfiguration35 ui36 ui.AdaptyPaymentFragment37 ui.AdaptyPaymentTabletDialogFragment38 ui.Command39 ui.home40 ui.home.LocationFragment
1 automation.appium.wdio.src.flows.account
2 automation.appium.wdio.src.flows.nav
3 automation.appium.wdio.src.support.golden
4 com.wireguard.android.configStore
5 com.wireguard.android.model.TunnelComparator.NaturalSortString
6 com.wireguard.android.util.BiometricAuthenticator
7 service.ConnectivityService
8 utils
9 automation.appium.wdio.src.flows11
10 automation.appium.wdio.src.support1
11 com.wireguard.android.databinding.ObservableSortedKeyedArrayList1
12 com.wireguard.android.model.TunnelComparator1
13 com.wireguard.android.util1
14 com.wireguard.android.util.BiometricAuthenticator.Result4
15 model1
16 repository.src12
17 com.wireguard.android.databinding1
18 model.AccountType3
19 model.AppState3
20 model.Dns1
21 model.NetworkDescriptor1
22 model.NetworkType3
23 model.Tab6
24 model.TunnelStatus4
25 service113111
26 com.wireguard.android.model12
27 repository3239
28 service.AccountRescuePayload1
29 service.Sheet7
30 service.WeeklyReportPayload1
31 common~vendor~adapty_flutter~ios~adapty_flutter~adapty_flutter7
32 engine21121
33 binding762822
34 engine.EngineConfiguration31
35 ui42816
36 ui.AdaptyPaymentFragment1
37 ui.AdaptyPaymentTabletDialogFragment1
38 ui.Command3
39 ui.home1343
40 ui.home.LocationFragment1
Uses a module listed above itPart of a loopThe module itself
1 automation.appium.wdio.src.flows.account2 automation.appium.wdio.src.flows.nav3 automation.appium.wdio.src.support.golden4 com.wireguard.android.configStore5 com.wireguard.android.model.TunnelComparator.NaturalSortString6 com.wireguard.android.util.BiometricAuthenticator7 service.ConnectivityService8 utils9 automation.appium.wdio.src.flows10 automation.appium.wdio.src.support11 com.wireguard.android.databinding.ObservableSortedKeyedArrayList12 com.wireguard.android.model.TunnelComparator13 com.wireguard.android.util14 com.wireguard.android.util.BiometricAuthenticator.Result15 model16 repository.src17 com.wireguard.android.databinding18 model.AccountType19 model.AppState20 model.Dns21 model.NetworkDescriptor22 model.NetworkType23 model.Tab24 model.TunnelStatus25 service26 com.wireguard.android.model27 repository28 service.AccountRescuePayload29 service.Sheet30 service.WeeklyReportPayload31 common~vendor~adapty_flutter~ios~adapty_flutter~adapty_flutter32 engine33 binding34 engine.EngineConfiguration35 ui36 ui.AdaptyPaymentFragment37 ui.AdaptyPaymentTabletDialogFragment38 ui.Command39 ui.home40 ui.home.LocationFragmentautomation.appium.wdio.src.flows.account1automation.appium.wdio.src.flows.nav2automation.appium.wdio.src.support.golden3com.wireguard.android.configStore4com.wireguard.android.model.TunnelComparator.NaturalSortString5com.wireguard.android.util.BiometricAuthenticator6service.ConnectivityService7utils8automation.appium.wdio.src.flows9automation.appium.wdio.src.support10com.wireguard.android.databinding.ObservableSortedKeyedArrayList11com.wireguard.android.model.TunnelComparator12com.wireguard.android.util13com.wireguard.android.util.BiometricAuthenticator.Result14model15repository.src16com.wireguard.android.databinding17model.AccountType18model.AppState19model.Dns20model.NetworkDescriptor21model.NetworkType22model.Tab23model.TunnelStatus24service25com.wireguard.android.model26repository27service.AccountRescuePayload28service.Sheet29service.WeeklyReportPayload30common~vendor~adapty_flutter~ios~adapty_flutter~adapty_flutter31engine32binding33engine.EngineConfiguration34ui35ui.AdaptyPaymentFragment36ui.AdaptyPaymentTabletDialogFragment37ui.Command38ui.home39ui.home.LocationFragment40111111411213311364113111123239171721121762822314281611313431+36 more modules (most-connected shown)

At a glance — Code Health · 58% · Adequate · gated by R1 ·

At a glance — Architecture · 93% · Adequate · gated by D26 ·

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

At a glance — Readiness · 65% · Adequate · gated by P3 ·

At a glance — Security · 66% · Checked 5 of 11 · gated by D36 ·

At a glance — Domain Modelling · 80% · Strong ·

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
A05:2025 — Injection46High / Critical
A03:2025 — Software Supply Chain Failures6Medium
A07:2025 — Authentication Failures5High / Critical
A02:2025 — Security Misconfiguration3High / Critical

Roadmap

Top priorities: TypeScript/JavaScript: use the promise APIs (fs/promises, a promisified child_process.execFile, the async zlib/crypto functions) and await them instead of the *Sync variants; Migrate the remaining .js/.jsx files to TypeScript; Thread an AbortSignal through async functions that make requests, so the work stops when its caller gives up.

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

Do thisHelpsEffortDimension
TypeScript/JavaScript: use the promise APIs (fs/promises, a promisified child_process.execFile, the async zlib/crypto functions) and await them instead of the *Sync variants.+2.6 ptsMediumAsync & latency hygiene
Migrate the remaining .js/.jsx files to TypeScript.+2.4 ptsMediumType Safety
Thread an AbortSignal through async functions that make requests, so the work stops when its caller gives up.+2.2 ptsMediumCancellation propagation
Resolve the 1 No ADRs found finding(s) in ADR Quality.+0.8 ptsLowADR Quality
Break down the listed branch-heavy functions; aim P95 cyclomatic ≤ 5.+1.5 ptsMediumCyclomatic Complexity
Swallowed exception (caught, then discarded)+1.3 ptsMediumException handling
Bring the 2 bodies over 60 down to 60 or less in Cognitive Complexity — start with DomainDetailSectionState._getSubtitleText (cognitive 144), ai-explorer-runner.runAiExplorer (cognitive 102).+1.0 ptsMediumCognitive Complexity
Resolve the 6 No assertions finding(s) in Test Quality — start with activity.spec.ts, exceptions-crud.spec.ts, paywall.spec.ts.+0.5 ptsLowTest Quality

File quality

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

FileScoreBandWorst signal
REDACTED2.5SlopStatic Analysis (SAST): High: REDACTED
REDACTED3.0SlopStatic Analysis (SAST): High: REDACTED
REDACTED4.4MixedIaC & Container Security: High IaC: REDACTED
REDACTED4.4MixedStatic Analysis (SAST): High: REDACTED
REDACTED4.8MixedStatic Analysis (SAST): High: REDACTED
REDACTED4.8MixedStatic Analysis (SAST): High: REDACTED
REDACTED4.8MixedStatic Analysis (SAST): High: REDACTED
REDACTED5.1MixedStatic Analysis (SAST): Medium: REDACTED
REDACTED5.1MixedStatic Analysis (SAST): High: REDACTED
REDACTED5.1MixedStatic Analysis (SAST): High: REDACTED
REDACTED5.1MixedStatic Analysis (SAST): High: REDACTED
REDACTED5.8MixedSecrets (history): REDACTED: REDACTED
REDACTED5.8MixedStatic Analysis (SAST): High: REDACTED
common/lib/src/features/stats/ui/top_domains.dart5.9MixedCyclomatic Complexity: TopDomainsState.build (cyclomatic 25)
common/lib/src/features/stats/ui/recent_activity.dart5.9MixedCognitive Complexity: RecentActivityState.build (cognitive 21)
common/lib/src/features/stats/ui/domain_detail_section.dart6.0MixedExplicit Debt: TodoComment
common/lib/src/app_variants/family/module/family/actor.dart6.0MixedExplicit Debt: TodoComment
common/lib/src/platform/app/start/start.dart6.0MixedExplicit Debt: TodoComment
ios/App/Binding/Stage/StageBinding.swift6.0MixedExplicit Debt: TodoComment
common/lib/src/features/support/domain/actor.dart6.0MixedExplicit Debt: TodoComment

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

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

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

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

Could not be resolved — 13

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

Methodology & how to trust this report

This survey is a deep, periodic assessment — run each sprint, monthly, or quarterly, taking the time to go wider and deeper than a quick check and surfacing in one coherent report what you'd otherwise piece together from a dozen separate tools. It scores deterministically: the same commit yields the same score, every run. All 73 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 — 73 dimensions across the health lenses
D1D2D3D4D5D6D10D12D13D14D15D17D19D20D24D26D28D29D30D31D34D35D36D43D44AX1AX10AX3AX4AX8AX9DM1DM4DM5GD1IC1M1M2M3M4P1P2P3P4P6PF3R1R10R2R3R4R5R6R7R8R9X1X12X13X14X16X18X19X2X21X23X25X27X28X29X3X30X5

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, 563 of 589 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 · trivy · checkovSecrets in history, SAST, CVEs, IaC & container, PII / GDPR1.86.0 · 0.69.3 · 3.2.533✓ deterministic

Every finding is locatable in findings.md. Run 01a1ce4f-765a-760c-ac73-b07ce5e0b807.

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 could not be measured — the JavaScript/TypeScript suite(s) run through a browser-driven runner the coverage collector does not drive — automation/appium/wdio/ (@wdio/cli/webdriverio), ios/BlockaWebExtension/ (@playwright/test) — a gap in the analyzer, not something this repository is missing. Coverage is excluded from the score rather than counted as a near-zero. This is OUR limitation, not a defect in the repo. In the meantime, commit (or publish into the working tree) the lcov/Cobertura report your CI produces and the real number is read on the next scan. You can widen what we reach: optional: commit the lcov/Cobertura report your CI produces, and the real number is read on the next scan.
  • 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 134 test(s) behind this row are the ones the JavaScript/TypeScript census could read, and this repository also carries at least 139 test source file(s) (.dart) that it cannot: it reads JavaScript/TypeScript test declarations off disk, so a JUnit/pytest-style suite is invisible to it. Skipped tests, zero-assertion tests and the other quality signals on this row are UNMEASURED in that suite — their absence from the counts above is a gap in this analyzer's language coverage, not a finding that those tests are sound.
  • D11 Test Reliability — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Test source is present (.dart, .ts, .js, .mjs) but the built-in reliability runner does not support this repository's ecosystem, so flakiness couldn't be assessed. Not scored — this is a gap in the analyzer's language coverage, not a finding about this repository.
  • D14 License Compliance — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. This repository declares a Swift Package.swift/Package.resolved, but the licence verdict published here was taken over its gem dependencies. Nothing was read about its SwiftPM dependencies' licensing in either direction, and a clean score on this card must not be read as covering them.
  • D14 License Compliance — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. This repository declares a Gradle build (build.gradle/build.gradle.kts), but the licence verdict published here was taken over its gem dependencies. Nothing was read about its Gradle dependencies' licensing in either direction, and a clean score on this card must not be read as covering them.
  • D14 License Compliance — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. This repository declares a Dart pubspec.yaml, but the licence verdict published here was taken over its gem dependencies. Nothing was read about its Dart dependencies' licensing in either direction, and a clean score on this card must not be read as covering them.
  • D16 Bus Factor — not measured this run — This is a true statement about the repository that carries nothing for its owner to act on, so it is reported here rather than as a defect in their code. Single-maintainer repository — bus factor is not applicable (3 contributor(s) across 2671 commit(s) sampled, automation and bot accounts excluded). One of them holds 91% of the history; the other 2 hold 4.5% each on average, below the 5% at which there is somebody to hand the work to. That is a single maintainer with drive-by contributors, not a team whose knowledge has concentrated — so the bus factor is not applicable and there is nothing here for the owner to act on.
  • 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.
  • 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. This kind did not reach the 95 % precision gate in three adjudicated runs (docs/plans/deterministic-engine/adjudication/D19-sample3-v3.md), so by the pre-registered fallback it publishes no row until a re-measurement shows it does. The candidates are counted here, not reported as findings, and the score does not include them.
  • D21 Naming 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. D21's deterministic naming rules are gated on C# first (docs/plans/deterministic-engine.md, P5): each other language is switched on only after its own concept suite and A/B gate pass. Until then its declarations carry no naming verdict this run — this says nothing about whether its names are consistent.
  • D22 Internal API Consistency — not measured this run — 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 — 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 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 — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Navigability is taken over call sites whose callee resolved. For C# that population includes calls into referenced assemblies; for this language only calls declared inside the repository count, so the abstention threshold reads the repository's use of its standard library as a resolution failure. That is a limit of this analyzer, not a build problem in this repository.
  • D32 Data Compliance (PII/GDPR) — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. `android/app/src/main/java/service/EnvironmentService.kt`, `android/app/wireguard-android/ui/src/main/java/com/wireguard/android/databinding/ObservableSortedKeyedArrayList.kt`, `ios/App/Util/Date+Extensions.swift` 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.
  • AX1 Captive dependencies — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. This repository also uses Factory, whose singleton and shorter-lived bindings can capture one another the same way, but this check does not read them yet. That is a gap in this analyzer's language reach — not a finding that those bindings are free of it.
  • 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.
  • M4 Documentation accuracy — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. M4 checks only the claim kinds adjudicated at or above 95 % precision: links and versions (PREREGISTRATION version 9), and artefact counts an order of magnitude off. Paths, command arguments, installs, environment variables, settings, projects, packages, routes, cd targets, infrastructure products and removed modules are read but not checked, and none of them is reported or counted.
  • P5 DR & Backup — not measured this run — This is a true statement about the repository that carries nothing for its owner to act on, so it is reported here rather than as a defect in their code. No backup/snapshot/replication config, RTO/RPO or restore-procedure documentation was found — and no production persistence was detected either (no data-access packages, no data-store services, no database resources), so there is nothing in this repository whose loss a DR control would recover. If this system's data lives in a platform or ops repo we can't see, that's where the DR evidence belongs.
  • R10 Code Duplication — 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 filesystem refused the listing or the read of: android/app/src/main/java/channel, ios/BlockaWebExtension/Resources/oisd-small.txt, ios/Channel. Every other path was read.
  • 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.
  • X24 Document value interpolated into markup unescaped — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check'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.
  • X26 Unsynchronised callback handoff — 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.

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

Limitations & what we did not check

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

Per-dimension blind spots

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

  • D1 Cyclomatic Complexity: Cyclomatic complexity counts branches statically — it cannot tell an essential decision tree from accidental tangle, nor see complexity that lives in data or configuration (large switch-case token tables, DSL lexers/parsers, data-as-code rule tables) rather than control flow: a tokenizer's many single-character cases read as high complexity though each branch is trivial.
  • D2 Cognitive Complexity: Cognitive-complexity heuristics approximate how hard code is to follow; genuine domain difficulty and well-named intent that eases reading are not captured.
  • D3 God Classes: "God class" is sized by members and responsibilities visible in the type — a deliberately broad facade over a coherent subsystem can read the same as an accidental grab-bag. For front-end JS the file-length check is cohesion-aware (a single-responsibility module — one class/IIFE — earns a 3× threshold), but cohesion is approximated from top-level declarations, not true dependency structure.
  • D4 Code Duplication: Duplication is token-similarity — an in-process token-stream comparison over sliding windows, with type-aware normalization — so it finds copy-paste, not semantic duplication expressed differently. Committed machine-written code (scaffolded migrations, designer/codegen output, protobuf/OpenAPI stubs, model snapshots) is EXCLUDED — its repetition is the tool's, not the team's — so the score reflects hand-written duplication only.
  • D5 Coupling: Coupling is measured between projects/assemblies — runtime coupling through DI, reflection, messaging or shared databases is invisible to a static reference graph.
  • D6 Cohesion (LCOM4): LCOM4 cohesion is syntactic — it infers connectivity from which methods touch which fields/methods by name, not from real runtime behaviour or intent.
  • D10 Test Quality: Assertion density is structural — it cannot tell a meaningful behavioural assertion from a trivial one, only that an assertion is present.
  • D12 Dependency Hygiene: Dependency health reads manifests and lockfiles — a vulnerability in a vendored/copied dependency, or risk from how a dependency is actually used, is outside this view.
  • D13 REDACTED Scanning: REDACTED detection is signature- and entropy-based on the current tree — a secret that does not match a known pattern, or one already rotated, will not be flagged (a clean scan is "nothing matched", not "no secrets exist").
  • D14 License Compliance: License compatibility is checked against declared package metadata and a policy — mislabelled or missing license metadata, and obligations that depend on how you distribute, are not resolved here.
  • D15 Churn × Complexity Hotspots: Churn hotspots come from git history — a freshly imported or squashed repository has no churn signal, and recent rewrites can mask a historically risky file.
  • D17 Explicit Debt: Acknowledged-debt signals (TODO/FIXME, suppressions, dead code) are textual — undocumented debt that nobody marked, and debt that lives in design rather than annotations, is invisible. Committed machine-written code (scaffolded migrations, designer/codegen output, generated stubs) is excluded — it is never the team's dead code to delete.
  • D19 Documentation Quality: Documentation quality publishes two things only: a runnable or packaged unit with no example, and a multi-project root README that maps none of its parts. It does not judge clarity, and its other checks (overview, licence, boilerplate, structure, empty sections, XML-doc coverage) are withheld after adjudication: their candidates are counted in the card's gaps, not shown as rows. A false statement in a document is M4's; units are .NET projects only.
  • D20 ADR Quality: ADR quality checks the structure of the decision records present: it cannot know about decisions made and never recorded, and it does not judge how well a record argues its case. Records in a language the section lexicon does not cover are not evaluated.
  • D24 Comment Value: Comment value is measured as redundancy only: a comment that repeats its code's words is found, but a paraphrase in other words, a vague comment, or one the code contradicts is not, and whether a comment is valuable is not claimed. Comments in other scripts or languages, and outside C#, are not judged.
  • D26 Project Cohesion: Project focus is sized from members/namespaces per project — a project that is broad by deliberate design reads the same as one that has sprawled.
  • D28 Secrets (history): Secret-history scanning sweeps the git log for known patterns — a secret that predates the available history, or never matched a signature, is not found (clean means "nothing matched in the history we can see").
  • D29 Static Analysis (SAST): SAST findings are pattern-based (semgrep) — it finds classes of bug it has rules for; logic flaws, auth/authorization gaps and issues needing runtime context are out of reach (and clean means "no rule matched").
  • D30 Dependency Vulnerabilities: CVE matching depends on accurate package/version metadata and on the advisory databases — a vulnerability with no published advisory, or in code not declared as a dependency, is not seen. Coverage needs a RESOLVED graph: an unpinned requirements.txt, or a pom without a resolved build, yields partial coverage rather than a clean verdict. An ecosystem the analyzer cannot scan is reported as unmeasured, never as clean.
  • D31 IaC & Container Security: IaC scanning checks Dockerfiles/Terraform/Kubernetes against best-practice rules — it cannot see the live cloud account, runtime configuration, or drift between the committed config and what is actually deployed.
  • D34 Knowledge Freshness: Freshness is decayed commit RECENCY, not comprehension — code read often but rarely committed reads as orphaned, and stable code that genuinely needs no changes is penalised the same as forgotten code; bot/squash commits distort it like the bus factor.
  • D35 Change Coupling: Change coupling is co-change in COMMITS — files split across separate commits, or coupled only through a shared config/build step, read as uncoupled, and a sweeping commit (rename/format) is excluded so it doesn't couple everything. It shows that files change together, not WHY: a high coupling can be a healthy cohesive pair as readily as a hidden leak.
  • D43 Malicious Dependencies: Only packages some vulnerability database has already NAMED as malicious are seen — a compromise published in the last hours, or never reported at all, is invisible here, and this dimension reading 10 is not evidence that a dependency is trustworthy. There is no typosquat or dependency-confusion analysis: a package nobody has reported is simply absent from the feeds. Coverage is the dependency scan's: an ecosystem that could not be scanned is disclosed as unmeasured, never as clean.
  • D44 Platform End-of-Life: The support table is FROZEN, so it goes out of date by losing RECALL: a release that ended support after the table was written is missed until the table is refreshed, and this dimension reading 10 is not evidence that a platform is current. Only platforms the repository DECLARES in a place this pass reads are seen — a runtime named only in a REDACTED (D31's subject), in a CI workflow (D29's), or in a file this pass does not parse (go.mod, a Gemfile ruby directive) is invisible here, which is why a repository declaring none of them abstains rather than scoring. Only frameworks with a PUBLISHED support policy are tracked: React, Flask and Express publish none, so their age cannot be judged and their absence from a report is not a statement that they are supported.
  • 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.
  • DM4 Rich vs anemic domain model: Behaviour is detected as state mutation inside a method body — a method that enforces an invariant by validating-and-throwing without mutating reads as a query, and mutation delegated through an interface the scan can't resolve isn't credited; entities with zero public properties still drop out of the population. It detects that state changes, not whether the rule is correct.
  • M4 Documentation accuracy: Documentation accuracy checks links, versions and artefact counts against the tree: other claims (paths, commands, settings, routes) are read but not checked, and it cannot run the onboarding or measure how long a real new joiner takes.
  • P4 Deployment & Rollback: Approval/branch-protection rules live in repository settings the scan cannot see — only their in-repo evidence (config files, workflows) is checked, so a control enforced purely in the host's settings reads as "not evidenced".
  • P6 Release Hygiene: Rollback/observability controls are inferred from repo artefacts (pipelines, dashboards-as-code) — controls configured in external tooling, with no in-repo trace, cannot be credited.

Dimensions

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

What it measures: How tangled the control flow is — methods with many branches are hard to test and change.

Method: Cyclomatic complexity per method (1 + decision points), computed exhaustively across production source; test projects separated by convention. Deterministic.

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

29 method(s) exceeded the cyclomatic complexity threshold of 15; the worst was ai-explorer-runner.runAiExplorer at 63. A further 8 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 devices.filterConnectedDevices at 24 — they are counted neither in the figure above nor in this dimension's score. 8 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: automation/shared/lib/devices.mjs (devices.filterConnectedDevices at 24), android/app/src/main/java/binding/StageBinding.kt (StageBinding.showDialog at 19), common/lib/src/platform/command/command.dart (CommandStore._execute at 18), android/app/src/six/kotlin/ui/home/LocationFragment.kt (LocationFragment.getFlag at 16), ios/App/Assets/Error.swift (Error.swift.mapSKErrorForDebug at 16), and 3 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.

ai-explorer-runner.runAiExplorer (cyclomatic 63)automation/appium/wdio/scripts/lib/ai-explorer-runner.mjs:1258
explorer-commands.runExplorerCommand (cyclomatic 49)automation/appium/wdio/scripts/lib/explorer-commands.mjs:417
DomainDetailSectionState._getSubtitleText (cyclomatic 47)common/lib/src/features/stats/ui/domain_detail_section.dart:137
filterConnectedDevices (cyclomatic 29)automation/shared/lib/devices.mjs:71
FamilyActor._updatePhaseNow (cyclomatic 27)common/lib/src/app_variants/family/module/family/actor.dart:208

+ 23 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 ai-explorer-runner.runAiExplorer (cyclomatic 63), explorer-commands.runExplorerCommand (cyclomatic 49), DomainDetailSectionState._getSubtitleText (cyclomatic 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 3 together lifts Cyclomatic Complexity from 6.5 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 Complexity5.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 5.6 / 10 · rule-coverage 100% · ceiling Prevented

54 method(s) exceeded the cognitive complexity threshold of 15; the worst was DomainDetailSectionState._getSubtitleText at 144.

DomainDetailSectionState._getSubtitleText (cognitive 144)common/lib/src/features/stats/ui/domain_detail_section.dart:137
ai-explorer-runner.runAiExplorer (cognitive 102)automation/appium/wdio/scripts/lib/ai-explorer-runner.mjs:1258
DomainDetailSectionState._fetchSubdomains (cognitive 48)common/lib/src/features/stats/ui/domain_detail_section.dart:610
TopDomainsState.build (cognitive 46)common/lib/src/features/stats/ui/top_domains.dart:76
ScheduleModel.validate (cognitive 37)common/lib/src/app_variants/family/module/schedule/json.dart:155

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

What to do

  1. Bring the 2 bodies over 60 down to 60 or less in Cognitive Complexity — start with DomainDetailSectionState._getSubtitleText (cognitive 144), ai-explorer-runner.runAiExplorer (cognitive 102). — This score is capped by its worst body, so a finding fixed alone moves it by almost nothing — the next one down takes its place. Refactoring these 2 together lifts Cognitive Complexity from 5.6 to about 6.5/10, projected with the scoring formula itself and assuming each lands exactly at 60; a cleaner split scores higher.

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

D3 · God Classes8.5 / 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.5 / 10 · rule-coverage 100% · ceiling Prevented

28 god class(es) detected.

MethodTooLong: SettingsState.build · ×13common/lib/src/features/settings/ui/settings_section.dart:101
FileTooLong: lib/ai-explorer-runner.mjs · ×6automation/appium/wdio/scripts/lib/ai-explorer-runner.mjs
TooManyMethods: PaymentBinding · ×4android/app/src/six/kotlin/binding/PaymentBinding.kt:58
ClassTooLong: DomainDetailSectionState · ×3common/lib/src/features/stats/ui/domain_detail_section.dart:61
FunctionTooLong: ai-explorer-runner.runAiExplorer · ×2automation/appium/wdio/scripts/lib/ai-explorer-runner.mjs:1258

What to do

  1. Resolve the 13 MethodTooLong finding(s) in God Classes — start with domain_detail_section.dart (2), settings_section.dart, device_section.dart. — One of this dimension's main actionable groups (13 warning-level).
  2. Resolve the 6 FileTooLong finding(s) in God Classes — start with ai-explorer-runner.mjs, domain_detail_section.dart, weekly_report.dart. — One of this dimension's main actionable groups (6 warning-level).
  3. Resolve the 4 TooManyMethods finding(s) in God Classes — start with PaymentBinding.kt, actor.dart, adapty.dart. — One of this dimension's main actionable groups (4 warning-level).

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

D4 · Code Duplication9.3 / 10Stronggated by 184 serious findings✓ Tool-verified

What it measures: Copy-pasted code that should be shared instead.

Method: Code duplication via token-stream sliding windows with type-aware normalization (locals masked, type names preserved), density-scored per KLoC of production code. Deterministic.

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

101 duplicated block group(s) detected. A further 83 rows report members as variants of one another; they aggregate block groups already counted above and are not themselves counted. 1 of the 184 are in trees this repository does not ship — vendored, example/demo, project-template, fixture and benchmark code — and are ranked below the shipped groups rather than excluded from them: the duplication there is real and is still counted in this dimension's score. The dimensions that publish a production-file census leave those trees out of theirs, so this count is deliberately drawn over the wider population.

Duplicated block (8 lines × 2) · ×12common/lib/src/app_variants/family/widget/home/smart_onboard.dart:137
Edited copy of a member (8 corresponding lines) · ×7common/lib/src/features/notification/domain/actor.dart:63
Duplicated block (7 lines × 2) · ×7common/lib/src/app_variants/family/module/device_v3/json.dart:85
Duplicated block (6 lines × 2) · ×7common/lib/src/app_variants/family/module/stats/json.dart:66
Edited copy of a member (9 corresponding lines) · ×6common/lib/src/features/notification/domain/api.dart:16

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

What to do

  1. Resolve the 12 Duplicated block (8 lines × 2) finding(s) in Code Duplication — start with HomeViewModel.swift (7), smart_onboard.dart, main_screen.dart. — One of this dimension's main actionable groups (12 warning-level).
  2. Resolve the 7 Edited copy of a member (8 corresponding lines) finding(s) in Code Duplication — start with actor.dart, FileConfigStore.kt, CommonBinding.swift. — One of this dimension's main actionable groups (7 warning-level).
  3. Resolve the 7 Duplicated block (7 lines × 2) finding(s) in Code Duplication — start with json.dart (3), stats_filter_device.dart, BlokadaView.swift. — One of this dimension's main actionable groups (7 warning-level).

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

D5 · Coupling10.0 / 10Exemplary✓ Tool-verified

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

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

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

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

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

✓ On the Gold path — maintain.

Detailed fixes: d5_recommendation.md.

D6 · Cohesion (LCOM4)9.4 / 10Stronggated by 12 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.4 / 10 · rule-coverage 100% · ceiling Verified

12 of 251 classes have LCOM4 above 3.

Low cohesion: AdaptyConfiguration (LCOM4 16) · ×12common/vendor/adapty_flutter/lib/src/models/adapty_configuration.dart:41

What to do

  1. Resolve the 12 Low cohesion finding(s) in Cohesion (LCOM4) — start with adapty_configuration.dart, adaptyui_flow_platform_view.dart, adaptyui.dart. — One of this dimension's main actionable groups (12 warning-level).

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

D10 · Test Quality9.3 / 10Stronggated by 6 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.3 / 10 · rule-coverage 100% · ceiling Prevented

0 skipped, 6 zero-assertion, no mocking-framework packages referenced (hand-written doubles or no mocking) across 134 tests. Measured on the JavaScript/TypeScript suite only — at least 139 test source file(s) (.dart) went unread, so its test quality is unmeasured and is not in these counts.

No assertions: opens the full Activity list from Privacy Pulse · ×6automation/appium/wdio/src/specs/smoke/activity.spec.ts:95

What to do

  1. Resolve the 6 No assertions finding(s) in Test Quality — start with activity.spec.ts, exceptions-crud.spec.ts, paywall.spec.ts. — One of this dimension's main actionable groups (6 warning-level).

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

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

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

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

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

0 outdated direct gem(s), 0 pinning defect(s). 2 declaration(s) graded against rubygems.org, 2 of them against a version resolved in a committed Gemfile.lock. Whether any of these gems is DEPRECATED or YANKED is not graded — rubygems.org publishes no deprecation marker, and a yank removes a version rather than flagging it. Whether any is UNMAINTAINED is not graded either: no registry publishes a maintenance status, and release age does not stand in for one. Whether any is UNUSED is a source question, not a registry one. Known CVEs in this dependency graph are D30's question, read from the manifest there.

✓ On the Gold path — maintain.

Detailed fixes: d12_recommendation.md.

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

What it measures: Whether any secrets (keys, tokens, passwords) have leaked into the code.

Method: In-process native secret scanner (entropy plus signature patterns) across all tracked files; no external tool. A clean result is a measured 10, not no-data zero. Deterministic.

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

REDACTED scan ran and found no leaked secrets. 3 detection(s) were excluded as holding no minted credential in material that runs: a name, reference or comparison rather than a value, a readable phrase or pattern, a value that declares itself fake, or development, test, example, mock or demo material.

✓ 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 105 shipped gem(s) use a banned license. Licences were resolved from rubygems.org over the 105 gem(s) a consumer installs — this repository's runtime declarations closed transitively over its committed Gemfile.lock. Development-group and `add_development_dependency` gems are excluded: they are not distributed with this repository. 1 of them publish no licence on rubygems.org; that is missing data, not a violation, and none of them is charged. ★ COVERAGE OF THIS VERDICT: it grades this repository's gem dependencies and nothing else. The repository also declares a Swift Package.swift/Package.resolved, a Gradle build (build.gradle/build.gradle.kts) and a Dart pubspec.yaml, and the licences of those dependency graphs were NOT read by this pass — a gap in this engine's coverage, not a statement about them. So this result says the graded closure carries no banned licence; it does NOT say this repository's licensing is clear.

✓ On the Gold path — maintain.

Detailed fixes: d14_recommendation.md.

D15 · Churn × Complexity Hotspots10.0 / 10Stronggated by 8 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 10.0 / 10 · rule-coverage 100% · ceiling Documented

Top hotspots: common/lib/src/features/stats/ui/top_domains.dart (10×25=250); common/lib/src/features/settings/ui/settings_section.dart (9×17=153); common/lib/src/app_variants/v6/widget/filters_section.dart (4×16=64) Repeated repair below the complexity floor: common/lib/src/shared/ui/top_bar.dart (5 of 8 changes were fixes); common/lib/src/features/payment/domain/adapty.dart (3 of 5 changes were fixes); android/app/src/six/kotlin/binding/PaymentBinding.kt (3 of 4 changes were fixes)

Hotspot: common/lib/src/features/stats/ui/top_domains.dart · ×5common/lib/src/features/stats/ui/top_domains.dart:76
Repeated repair: common/lib/src/shared/ui/top_bar.dart · ×3common/lib/src/shared/ui/top_bar.dart:67

What to do

  1. Resolve the 5 Hotspot finding(s) in Churn × Complexity Hotspots — start with top_domains.dart, settings_section.dart, filters_section.dart. — One of this dimension's main actionable groups (5 warning-level).
  2. Resolve the 3 Repeated repair finding(s) in Churn × Complexity Hotspots — start with top_bar.dart, adapty.dart, PaymentBinding.kt. — One of this dimension's main actionable groups (3 warning-level).

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

D17 · Explicit Debt9.8 / 10Stronggated by 57 serious findings✓ Tool-verified

What it measures: Acknowledged debt left in the code — TODOs, dead code, suppressed warnings.

Method: Roslyn syntactic debt markers (suppressions/TODO/FIXME/HACK/empty-catch/commented-code/Obsolete) plus SymbolFinder dead-code analysis; weighted-debt-per-KLoC density deducted 2.0x per unit. Deterministic, exhaustive.

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

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

TodoComment · ×52ios/WireguardCopiedFiles/TunnelsTracker.swift:68
XxxComment · ×3ios/App/Service/PrivateDnsService.swift:181
HackComment · ×2common/lib/modules.dart:247

What to do

  1. Resolve the 52 TodoComment finding(s) in Explicit Debt — start with actor.dart (13), ContentView.swift (2), modules.dart (2). — One of this dimension's main actionable groups (52 warning-level).
  2. Resolve the 3 XxxComment finding(s) in Explicit Debt — start with PrivateDnsService.swift (3). — One of this dimension's main actionable groups (3 warning-level).
  3. Resolve the 2 HackComment finding(s) in Explicit Debt — start with modules.dart (2). — One of this dimension's main actionable groups (2 warning-level).

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

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

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

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

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

1 of 1 documentation facets pass in full. 18 document(s) read across 3 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 found

What to do

  1. Resolve the 1 No ADRs found finding(s) in ADR Quality. — 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.

D24 · Comment Value7.6 7.5 / 10Strong✓ Tool-verified

What it measures: Whether comments are worth it — explaining WHY (valuable) rather than WHAT (redundant).

Method: Every inline C# comment compared word by word with the identifiers, literals and constructs of the code it annotates (taken from the syntax); a comment whose words that code already contains is redundant, as are closing-brace labels and generator template text. Comments giving a reason or a reference are kept; other scripts and languages are not judged. Deterministic, exhaustive, advisory.

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

6 of 249 judged comments only repeat the code they sit on (2.4 %). 2 comment(s) in another language or script were not judged.

redundant comment · ×2ios/BlockaWebExtension/Resources/popup.js:313

What to do

  1. Resolve the 2 redundant comment finding(s) in Comment Value — start with popup.js, popup.spec.js. — One of this dimension's main actionable groups (2 recommendation-level).

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

D26 · Project Cohesion1.4 / 10Critical✓ 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 1.4 / 10 · rule-coverage 100% · ceiling Documented

3 of 7 build units (Bundler, Gradle, Make, Python, npm, pub) 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.

D28 · Secrets (history)6.0 / 10Adequate✓ Tool-verified

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

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

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

4 finding(s): 0 critical, 4 high, 0 medium, 0 low. Remediation for historically-committed secrets is credential rotation — they remain in history regardless of later deletion.

REDACTED
REDACTED
REDACTED

What to do

  1. Resolve the 3 REDACTED finding(s) in Secrets (history) — start with REDACTED (2), REDACTED. — One of this dimension's main actionable groups (3 issue-level).
  2. Resolve the 1 High secret finding(s) in Secrets (history) — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
  3. Resolve the 1 Rotate the exposed credentials finding(s) in Secrets (history). — One of this dimension's main actionable groups (1 recommendation-level).

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

D29 · Static Analysis (SAST)4.9 / 10Weak✓ 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 4.9 / 10 · rule-coverage 100% · ceiling Documented

46 finding(s): 0 critical, 39 high, 7 medium, 0 low. 37 unpinned-GitHub-Actions row(s) are reported here but scored by D36 (supply-chain provenance), which measures that posture as `pinned_actions` — one pinning decision is charged once, not once per lens. semgrep hit a parse error in 4 file(s) — `android/gradlew` (line 74, line 178), `scripts/en_check_elf_alignment.sh` (line 78, line 85, line 221), `scripts/sign-ios-frameworks.sh` (line 41), `tools/emu/emu` (line 22, lines 212–213, line 273) — 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 4 file(s) (e.g. a workflow `run:` block read as shell). Those files WERE scanned and their other rows are unaffected; only those rules' view of those snippets is missing.

REDACTED
REDACTED
REDACTED
REDACTED
REDACTED

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

What to do

  1. Resolve the 1 REDACTED finding(s) charged to Static Analysis (SAST) — the other 37 are reported here at file:line but scored by D36 (supply-chain provenance), which charges them once. — One of this dimension's main actionable groups (38 issue-level, 1 of them charged here).
  2. Resolve the 1 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
  3. Resolve the 2 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED, REDACTED. — One of this dimension's main actionable groups (2 warning-level).

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

D30 · Dependency Vulnerabilities9.6 / 10Stronggated by 2 serious findings✓ 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 9.6 / 10 · rule-coverage 100% · ceiling Documented

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

REDACTED

What to do

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

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

D31 · IaC & Container Security9.5 / 10Adequategated by 1 critical finding✓ Tool-verified

What it measures: Whether Dockerfiles / Terraform / Kubernetes config follow security best practices.

Method: IaC/container misconfiguration scan via trivy config (REDACTED/Terraform/K8s/Helm/CloudFormation); severity rules to 0-10 moderate normalizer. NotApplicable without manifests. Exhaustive, deterministic.

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

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

REDACTED
REDACTED
REDACTED

What to do

  1. Resolve the 1 High IaC finding(s) in IaC & Container Security — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
  2. Resolve the 1 Medium IaC finding(s) in IaC & Container Security — start with REDACTED. — One of this dimension's main actionable groups (1 warning-level).
  3. Resolve the 1 Low IaC finding(s) in IaC & Container Security — start with REDACTED. — One of this dimension's main actionable groups (1 recommendation-level).

Detailed fixes: d31_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

1 of 313 significant source file(s) are orphaned — their living knowledge has decayed to nothing, so no one currently understands them. The largest is common/lib/src/features/lock/ui/keypad.dart. Counted over 313 of the 620 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.

Orphaned files with no living knowledge
Orphaned filecommon/lib/src/features/lock/ui/keypad.dart:1

✓ On the Gold path — maintain.

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

D35 · Change Coupling9.9 / 10Stronggated by 4 serious findings✓ Tool-verified

What it measures: Whether files that change together actually belong together — pairs that repeatedly co-change in git history despite having no explicit code dependency, surfacing the hidden/logical coupling (and boundaries in the wrong place) a static scan can't see.

Method: Pairwise co-occurrence over the per-commit file sets in git history (production source only — tests and generated dropped): Degree-of-Coupling = shared ÷ min individual revisions, reported above noise floors (each file ≥10 revisions, ≥5 shared commits, ≥50% strength); sweeping commits excluded. Deterministic over fixed history.

Coverage: Population: PRODUCTION source files only — test and generated files are dropped before pairing, so a class co-changing with its own test (trivially ~100%) can't drown the real production↔production coupling. Pairs ranked by Degree-of-Coupling. A non-source file is never a coupling PARTICIPANT either: documentation, schemas, config and data files are dropped with the rest, so a code↔docs pair — a command and the reference page that restates it — is not reported however strongly the two co-change; nor is coupling that runs THROUGH a build step or config file.

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

Strongest change-coupling: privacy_pulse_section.dart↔horizontal_radial_segment.dart 58%; recent_activity.dart↔top_domains.dart 54%; activity_screen.dart↔domain_detail_section.dart 54%

Change coupling: privacy_pulse_section.dart ↔ horizontal_radial_segment.dart · ×4common/lib/src/app_variants/v6/widget/home/stats/privacy_pulse_section.dart:1

What to do

  1. Resolve the 4 Change coupling finding(s) in Change Coupling — start with privacy_pulse_section.dart, recent_activity.dart, activity_screen.dart. — One of this dimension's main actionable groups (4 warning-level).

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

D36 · Supply-chain Provenance & Signing2.5 / 10Weak✓ 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 2.5 / 10 · rule-coverage 100% · ceiling Documented

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

REDACTED
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 warning-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.

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

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

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

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

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

✓ On the Gold path — maintain.

Detailed fixes: d44_recommendation.md.

Frontend & cross-cutting dimensions

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

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

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

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

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

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.

DM1 · Aggregate boundaries10.0 / 10Exemplary✓ Tool-verified

Other · Domain Modelling — Whether aggregates reference each other by identity (id) rather than by direct object reference — the core DDD consistency-boundary rule.

Method: Roslyn (DDD-gated): aggregate roots identified by convention; each aggregate field checked for direct references to other aggregates versus id-only. Deterministic, DDD-native.

Coverage: Population: aggregate roots identified by AggregateRoot/IAggregateRoot base/interface NAME convention; reference-by-identity then checked exhaustively within that set — a root not using those names is invisible.

DM4 · Rich vs anemic domain model5.3 / 10Adequate✓ Tool-verified

Other · Domain Modelling — Whether domain entities own their behaviour — a data-only entity with public mutable state whose logic lives in a foreign service is anemic. Rich models enforce their own invariants; an immutable `@freezed`/`@immutable` value class is rich by construction.

Method: Roslyn (DDD-gated): entity method BODIES classified mutator-vs-query — only methods that mutate the entity's own declared state count as invariant-protecting behaviour, so a getter/passthrough doesn't rescue an anemic class. Deterministic, exhaustive over domain-layer entities.

Coverage: Population: entities by name/base convention; rich-vs-anemic judged by classifying each method body mutator-vs-query — logic-bearing domain types outside the convention are invisible.

  • `HttpRequest` is a data-only domain entity with public mutable state and no invariant-enforcing behaviour of its own, while the repo holds the logic in a foreign service/manager/use-case — the anemic domain model. Move the behaviour onto the entity so it enforces its own invariants (or make it an immutable `@freezed` value object) rather than being driven from outside. — common/lib/src/features/api/domain/endpoint.dart:6
  • `JsonCustomListPayload` is a data-only domain entity with public mutable state and no invariant-enforcing behaviour of its own, while the repo holds the logic in a foreign service/manager/use-case — the anemic domain model. Move the behaviour onto the entity so it enforces its own invariants (or make it an immutable `@freezed` value object) rather than being driven from outside. — common/lib/src/features/customlist/domain/api.dart:67
  • `JsonJournalEntry` is a data-only domain entity with public mutable state and no invariant-enforcing behaviour of its own, while the repo holds the logic in a foreign service/manager/use-case — the anemic domain model. Move the behaviour onto the entity so it enforces its own invariants (or make it an immutable `@freezed` value object) rather than being driven from outside. — common/lib/src/features/journal/domain/api.dart:22
  • `JsonListItem` is a data-only domain entity with public mutable state and no invariant-enforcing behaviour of its own, while the repo holds the logic in a foreign service/manager/use-case — the anemic domain model. Move the behaviour onto the entity so it enforces its own invariants (or make it an immutable `@freezed` value object) rather than being driven from outside. — common/lib/src/features/list/domain/api.dart:29
  • `JsonFcmNotificationPayload` is a data-only domain entity with public mutable state and no invariant-enforcing behaviour of its own, while the repo holds the logic in a foreign service/manager/use-case — the anemic domain model. Move the behaviour onto the entity so it enforces its own invariants (or make it an immutable `@freezed` value object) rather than being driven from outside. — common/lib/src/features/notification/domain/api.dart:3
  • `JsonAdaptyPayload` is a data-only domain entity with public mutable state and no invariant-enforcing behaviour of its own, while the repo holds the logic in a foreign service/manager/use-case — the anemic domain model. Move the behaviour onto the entity so it enforces its own invariants (or make it an immutable `@freezed` value object) rather than being driven from outside. — common/lib/src/features/payment/domain/api.dart:3
  • `JsonLease` is a data-only domain entity with public mutable state and no invariant-enforcing behaviour of its own, while the repo holds the logic in a foreign service/manager/use-case — the anemic domain model. Move the behaviour onto the entity so it enforces its own invariants (or make it an immutable `@freezed` value object) rather than being driven from outside. — common/lib/src/features/plus/domain/lease/api.dart:24
  • `JsonLeasePayload` is a data-only domain entity with public mutable state and no invariant-enforcing behaviour of its own, while the repo holds the logic in a foreign service/manager/use-case — the anemic domain model. Move the behaviour onto the entity so it enforces its own invariants (or make it an immutable `@freezed` value object) rather than being driven from outside. — common/lib/src/features/plus/domain/lease/api.dart:68
  • `JsonSupportPayloadCreateSession` is a data-only domain entity with public mutable state and no invariant-enforcing behaviour of its own, while the repo holds the logic in a foreign service/manager/use-case — the anemic domain model. Move the behaviour onto the entity so it enforces its own invariants (or make it an immutable `@freezed` value object) rather than being driven from outside. — common/lib/src/features/support/domain/json.dart:3
  • `JsonSupportSession` is a data-only domain entity with public mutable state and no invariant-enforcing behaviour of its own, while the repo holds the logic in a foreign service/manager/use-case — the anemic domain model. Move the behaviour onto the entity so it enforces its own invariants (or make it an immutable `@freezed` value object) rather than being driven from outside. — common/lib/src/features/support/domain/json.dart:63
  • `JsonSupportPayloadMessage` is a data-only domain entity with public mutable state and no invariant-enforcing behaviour of its own, while the repo holds the logic in a foreign service/manager/use-case — the anemic domain model. Move the behaviour onto the entity so it enforces its own invariants (or make it an immutable `@freezed` value object) rather than being driven from outside. — common/lib/src/features/support/domain/json.dart:90
  • `JsonSupportHistoryItem` is a data-only domain entity with public mutable state and no invariant-enforcing behaviour of its own, while the repo holds the logic in a foreign service/manager/use-case — the anemic domain model. Move the behaviour onto the entity so it enforces its own invariants (or make it an immutable `@freezed` value object) rather than being driven from outside. — common/lib/src/features/support/domain/json.dart:152
  • `JsonSupportAction` is a data-only domain entity with public mutable state and no invariant-enforcing behaviour of its own, while the repo holds the logic in a foreign service/manager/use-case — the anemic domain model. Move the behaviour onto the entity so it enforces its own invariants (or make it an immutable `@freezed` value object) rather than being driven from outside. — common/lib/src/features/support/domain/json.dart:196

What to do

  • Move delegated behaviour onto the domain entity (or make it an immutable value object); keep invariants inside the type.
DM5 · Encapsulated state10.0 / 10Exemplary✓ Tool-verified

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

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

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

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

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

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

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

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

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

M1 · Documentation (README)8.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.

What to do

  • Add an 'Architecture' / 'How it works' section to the root README — the high-level shape.
  • Describe the projects a newcomer cannot place from the root README: 2 of 6 have no README of their own, in their folder or in their family's project (`android`, `android/app`).
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.

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.

P3 · Security & performance tooling3.0 / 10Weak✓ Tool-verified

Readiness · Readiness — Whether SAST, secret/dependency scanning and performance benchmarking are wired in (presence, not runtime).

Method: Filesystem scan: SAST configuration, dependency-update automation, secret scanning, and a benchmark harness or benchmark step — in this repository's own ecosystem. Exhaustive, deterministic.

  • No static application security testing detected. For this repository's stack, add the Dart analyzer's security lints plus `semgrep --config=auto` as a CI step. What was searched, so you can tell an absence from a miss: the 11 CI workflow file(s) in this repository, and the scanner and linter configuration checked in beside them. A scan that runs outside CI, one configured in your forge's web UI rather than in a committed file, or a tool whose name is none of those this check carries, is not seen — if that is your case the row is wrong, and saying so is more useful than adding a second scanner. — REDACTED:9
  • `REDACTED` schedules updates, but no `package-ecosystem` entry covers `pip`, `gitsubmodule`, which this tree depends on — so those dependencies get no update pull requests and no advisory pressure, however complete the dep-scan credit looks. Add the missing entries to the `updates:` list. — REDACTED:2

What to do

  • Add a SAST step to CI running what this repository's stack ships: the Dart analyzer's security lints plus `semgrep --config=auto` — so a security regression fails the build instead of landing.
  • Dependabot is configured but does not watch `pip`, `gitsubmodule` — add those `package-ecosystem` entries to REDACTED so those dependencies get the same automatic update and advisory pressure as the ones it already covers.
  • Add gitleaks/trufflehog in CI to block PRs that introduce committed secrets.
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.

P6 · Release Hygiene8.0 / 10Strong✓ 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.

  • The changelog this check read carries 0 versioned entries, against a bar of 3. Counted as either the distinct `x.y.z` versions it names (a link's target is not counted) or its version-shaped section headings (`## [1.2.0]`, `## V14.x.x`, `## Updates in 8.0.x`), whichever is the larger — so a log sectioned by minor series counts its sections, not its individual patch numbers. Entries recorded somewhere this check does not read — release notes generated at tag time from a generator config it did not recognise, or a log kept outside the repository — are not counted here, and this row is about what is re-findable in the tree rather than about how often you release.

What to do

  • Keep the changelog current — add a versioned entry (Keep-a-Changelog ## [x.y.z]) for each release so the history isn't a stub.
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.

  • `writeFileSync` in `savePageSource` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. — automation/appium/wdio/src/support/artifacts.ts:48
  • `writeFileSync` in `saveSyslog` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. — automation/appium/wdio/src/support/artifacts.ts:71
  • `existsSync` in `compareToGolden` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. — automation/appium/wdio/src/support/golden.ts:105
  • `readFileSync` in `compareToGolden` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. — automation/appium/wdio/src/support/golden.ts:115

What to do

  • TypeScript/JavaScript: use the promise APIs (fs/promises, a promisified child_process.execFile, the async zlib/crypto functions) and await them instead of the *Sync variants.
R1 · Type Safety3.7 / 10Weak✓ Tool-verified

React / JS · Code Health — How much of the frontend is typed TypeScript vs untyped JavaScript.

Method: Frontend file inventory: the share of typed TypeScript vs untyped JavaScript across the source tree. Deterministic, exhaustive over frontend files.

  • 29 typed · 50 plain JS — the untyped files are automation/appium/wdio/scripts/ai-explore.mjs, automation/appium/wdio/scripts/check-driver.mjs, automation/appium/wdio/scripts/explore.mjs, automation/appium/wdio/scripts/junit-summary.mjs, automation/appium/wdio/scripts/lib/ai-explorer-config.mjs, automation/appium/wdio/scripts/lib/ai-explorer-guardrails.mjs (+44 more).

What to do

  • Migrate the remaining .js/.jsx files to TypeScript.
R10 · Code Duplication9.1 / 10Exemplary✓ Tool-verified

React / JS · Code Health — Near-exact copy-pasted blocks of substantial extent across the frontend (the D4 clone algorithm over JS/TS tokens, D-386): a block is reported only where its copies still agree on most of their own identifiers and literals, or were renamed as they were pasted but kept most of their constants, and where the copies carry enough code to stand on their own or the copied extent reaches 30 lines — so a re-implementation sharing neither names nor values, and a small pasted declaration, are both found and deliberately not reported, and a clean R10 is not a claim that nothing was copied.

Method: Near-exact copy-pasted blocks of substantial extent across the frontend (the D4 clone algorithm run over JS/TS tokens). Masking finds the candidates; a block is reported when its copies still agree on most of their own identifiers and literals, or when a renamed copy still agrees on most of its constants, AND the copies carry enough code to stand on their own — or when the copied extent reaches 30 lines. So a re-implementation sharing neither names nor values, and a small pasted declaration, are deliberately not counted. Deterministic.

  • automation/appium/wdio/scripts/lib/explorer-commands.mjs:443 · automation/appium/wdio/scripts/lib/explorer-commands.mjs:470 — 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. — automation/appium/wdio/scripts/lib/explorer-commands.mjs:443
  • REDACTED:367 · REDACTED:400 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — REDACTED:367
  • automation/device/lib/log.mjs:105 · automation/device/lib/log.mjs:125 — 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. — automation/device/lib/log.mjs:105
  • automation/appium/wdio/scripts/lib/ai-explorer-runner.mjs:1493 · automation/appium/wdio/scripts/lib/ai-explorer-runner.mjs:1513 — 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. — automation/appium/wdio/scripts/lib/ai-explorer-runner.mjs:1493
  • automation/appium/wdio/scripts/lib/ai-explorer-config.mjs:24 · REDACTED:17 — the 2 copies sit in sibling files in one directory, so check first whether one of them (or an existing module there) already owns this behaviour and the others should call it; otherwise extract it into one module in that directory and have each site call it. — automation/appium/wdio/scripts/lib/ai-explorer-config.mjs:24
  • REDACTED:148 · REDACTED:162 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — REDACTED:148
  • automation/appium/wdio/src/flows/home.ts:57 · automation/appium/wdio/src/flows/home.ts:71 — 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. — automation/appium/wdio/src/flows/home.ts:57
  • automation/appium/wdio/src/flows/app.ts:18 · automation/appium/wdio/src/flows/app.ts:31 — 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. — automation/appium/wdio/src/flows/app.ts:18
  • automation/device/lib/log.mjs:72 · automation/device/lib/log.mjs:88 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — automation/device/lib/log.mjs:72
  • REDACTED:528 · REDACTED:538 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — REDACTED:528
  • automation/appium/wdio/scripts/lib/ai-explorer-config.mjs:4 · automation/appium/wdio/scripts/lib/ai-explorer-config.mjs:14 — 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. — automation/appium/wdio/scripts/lib/ai-explorer-config.mjs:4
  • automation/device/log.mjs:29 · automation/device/log.mjs:53 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — automation/device/log.mjs:29
  • ios/BlockaWebExtension/Resources/popup.js:95 · ios/BlockaWebExtension/Resources/popup.js:133 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — ios/BlockaWebExtension/Resources/popup.js:95
  • automation/appium/wdio/src/flows/account.ts:48 · automation/appium/wdio/src/flows/nav.ts:69 · automation/appium/wdio/src/flows/nav.ts:81 — the 3 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — automation/appium/wdio/src/flows/account.ts:48
  • ios/BlockaWebExtension/Resources/popup.js:128 · ios/BlockaWebExtension/Resources/popup.js:156 — 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. — ios/BlockaWebExtension/Resources/popup.js:128
  • automation/appium/wdio/scripts/lib/ai-explorer-runner.mjs:775 · automation/appium/wdio/scripts/lib/ai-explorer-runner.mjs:842 — 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. — automation/appium/wdio/scripts/lib/ai-explorer-runner.mjs:775
  • automation/appium/wdio/scripts/lib/ai-explorer-runner.mjs:930 · automation/appium/wdio/scripts/lib/ai-explorer-runner.mjs:937 — 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. — automation/appium/wdio/scripts/lib/ai-explorer-runner.mjs:930

What to do

  • Act on each finding's own remediation rather than one rule: the move depends on what recurs. Where the copies are executable blocks, give the shared part one home and call it from each site; where they are declarations, a listing, a specialisation already delegating to its base, or one shape repeated per entity, there is no call site and the move is a shared type, a generated set or a factory — sometimes there is nothing to extract.
R2 · Cyclomatic Complexity5.5 / 10Adequate✓ Tool-verified

React / JS · Code Health — Per-function cyclomatic/cognitive complexity from the token-level function scanner (D-386) — real branching, not a regex heuristic.

Method: Per-function cyclomatic/cognitive complexity from a token-level function scanner (real branching, not a regex heuristic), computed over every frontend function. Deterministic.

  • runAiExplorer has cyclomatic complexity 70 and cognitive complexity 112; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — automation/appium/wdio/scripts/lib/ai-explorer-runner.mjs:1258
  • runExplorerCommand has cyclomatic complexity 52 and cognitive complexity 40; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — automation/appium/wdio/scripts/lib/explorer-commands.mjs:417
  • (anonymous) has cyclomatic complexity 29 and cognitive complexity 9; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — automation/shared/lib/devices.mjs:72
  • evaluateSummary has cyclomatic complexity 25 and cognitive complexity 31; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — automation/appium/wdio/scripts/lib/ai-explorer-runner.mjs:633
  • command has cyclomatic complexity 22 and cognitive complexity 26; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — automation/appium/wdio/scripts/tests/ai-explorer-runner.test.mjs:57
  • renderMarkdownReport has cyclomatic complexity 20 and cognitive complexity 28; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — automation/appium/wdio/scripts/lib/ai-explorer-report.mjs:88
  • runMissionSurface has cyclomatic complexity 17 and cognitive complexity 29; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — automation/appium/wdio/scripts/lib/ai-explorer-runner.mjs:1060
  • filterLogText has cyclomatic complexity 17 and cognitive complexity 22; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — automation/device/lib/log.mjs:154
  • resolveTargetDevice has cyclomatic complexity 16 and cognitive complexity 18; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — automation/shared/lib/devices.mjs:185
  • openSettingsSection has cyclomatic complexity 15 and cognitive complexity 26; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — automation/appium/wdio/src/flows/settings.ts:294
  • compareToGolden has cyclomatic complexity 15 and cognitive complexity 22; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — automation/appium/wdio/src/support/golden.ts:86
  • inspectUi has cyclomatic complexity 15 and cognitive complexity 12; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — automation/appium/wdio/scripts/lib/explorer-commands.mjs:258
  • findJsonEnd has cyclomatic complexity 14 and cognitive complexity 29; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — automation/appium/wdio/scripts/lib/ai-explorer-model.mjs:40
  • renderReport has cyclomatic complexity 14 and cognitive complexity 17; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — automation/dep-validate/report.mjs:170
  • getFeaturesList has cyclomatic complexity 14 and cognitive complexity 12; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — ios/BlockaWebExtension/Resources/popup.js:174
  • execute has cyclomatic complexity 13 and cognitive complexity 18; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — automation/appium/wdio/scripts/tests/explorer-commands.test.mjs:146
  • parseSuites has cyclomatic complexity 13 and cognitive complexity 17; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — automation/appium/wdio/scripts/junit-summary.mjs:53
  • main has cyclomatic complexity 13 and cognitive complexity 16; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — automation/device/log.mjs:13
  • screenBodyValues has cyclomatic complexity 13 and cognitive complexity 10; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — automation/appium/wdio/scripts/lib/ai-explorer-runner.mjs:277

What to do

  • Break down the listed branch-heavy functions; aim P95 cyclomatic ≤ 5.
R3 · Large Files9.2 / 10Exemplary✓ Tool-verified

React / JS · Code Health — How many source files exceed the large-file threshold.

Method: Components/modules exceeding the large-file threshold, counted exhaustively across the frontend source tree. Deterministic.

  • automation/appium/wdio/src/flows/settings.ts has 444 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — automation/appium/wdio/src/flows/settings.ts:1

What to do

  • Split each oversized file along the responsibilities already in it, into smaller focused modules in the same package.
R4 · Test Coverage7.0 / 10Strong✓ Tool-verified

React / JS · Readiness — Static test reachability (D-386): the share of production files reachable from any test via the import graph — measured without running anything.

Method: Static test reachability: the share of production files reachable from any test via the import graph — measured without running anything. Deterministic.

  • No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one. (×14) — automation/dep-validate/report.mjs:1, automation/dep-validate/lib/queue.mjs:1, automation/appium/wdio/src/support/golden.ts:1, …

What to do

  • Add tests that import the unreached modules (directly or through their public entry).
R5 · Dependency Freshness10.0 / 10Exemplary✓ Tool-verified

React / JS · Readiness — How outdated the npm dependencies are (a maturity signal). JS/npm CVEs are scored separately in D30 (JS/npm Dependency Vulnerabilities).

Method: npm dependency staleness from manifest/registry metadata (a maturity signal; JS/npm CVEs are scored separately in D30, which answers dependency vulnerabilities for every ecosystem). Deterministic.

R6 · Tooling10.0 / 10Exemplary✓ Tool-verified

React / JS · Readiness — Whether the project wires up test, lint and typecheck — detected from each package.json script's COMMAND (eslint / tsc / vitest / jest / playwright), not just its name, and corroborated against CI-workflow invocations so a tool run only in CI still counts.

Method: package.json scanned for test/lint/typecheck script wiring. Deterministic presence check.

R7 · Dead Code9.2 / 10Exemplary✓ Tool-verified

React / JS · Code Health — Files unreachable from every application/tooling/test entry point, and exports nothing imports (module-graph reachability, D-386).

Method: Dead code: files unreachable from every application/tooling/test entry point plus exports nothing imports, via module-graph reachability. Deterministic, exhaustive over the import graph.

  • Unreachable from the 24 application, 16 tooling and 30 test entry point(s) detected in this repo. Nothing this repository declares compiles or type-checks these files, so a wrong deletion here would raise no compile error — gate removals on `npm test`, which loads the modules, and note that it only covers what it exercises. An undetected custom entry would make these reachable.
  • no import path from any entry point (24 application, 16 tooling, 30 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make — automation/appium/wdio/src/support/golden.ts
  • Nothing imports this binding — it is safe to review for removal. (×3) — automation/appium/wdio/src/flows/app.ts:53, automation/appium/wdio/src/flows/app.ts:77, automation/appium/wdio/src/support/automationIds.ts:60
  • This top-level declaration is not exported and its name occurs nowhere else in its module — not called, read, typed against, re-exported or named by a string. Nothing outside the module can reach a non-exported binding, so this is the whole search: remove it, or use it. (×3) — automation/appium/wdio/src/flows/settings.ts:31, automation/appium/wdio/src/flows/settings.ts:37, automation/appium/wdio/src/flows/settings.ts:146

What to do

  • Delete the dead files and unused exports — every line is maintenance cost and rebuild-estimate inflation with zero runtime value.
R8 · Dependency Hygiene8.0 / 10Strong✓ Tool-verified

React / JS · Readiness — npm dependency truthfulness (D-386): unused dependencies, imports not declared anywhere, and type-/test-only packages shipped as production deps.

Method: npm dependency truthfulness: unused dependencies, imports declared nowhere, and type-/test-only packages shipped as production deps — from the manifest + import graph. Deterministic.

  • Imported only as a TYPE and declared in no reachable package.json. The import is erased at compile time, so nothing is installed and no runtime resolution depends on it — but type-checking a clean clone will fail. Declare the typings it resolves through (or the package itself) in the owning package.json. — automation/appium/wdio/wdio.android.conf.ts:3

What to do

  • Remove unused dependencies, declare unlisted imports explicitly, and demote type-/test-only packages to devDependencies.
R9 · Circular Imports10.0 / 10Exemplary✓ Tool-verified

React / JS · Architecture — Import cycles in the module graph (D-386) — files that can only be understood and changed together.

Method: Import cycles in the module graph, detected exhaustively over JS/TS imports (the same cycle detection as the .NET coupling dimension). Deterministic.

X1 · Async correctness10.0 / 10Exemplary○ Nothing flagged

Other · Code Health — Whether the code avoids sync-over-async (deadlock-prone blocking on tasks) and async void.

Method: Roslyn syntax scan: async methods scanned for .Wait()/.GetAwaiter().GetResult() and async-void outside event handlers. Deterministic, hard fact per invocation.

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

Other · Code Health — Whether any branch is dead by construction — a switch arm whose label can never equal a case-normalised subject, or an `else if` whose predicate the arm above has already swallowed.

Method: Roslyn syntax + semantics: switch labels compared against the subject's own case normaliser, and if/else-if chains checked for a literal an earlier arm's containment test already swallows. Deterministic, provable per finding. Advisory.

X13 · Undrained process stream10.0 / 10Exemplary○ Nothing flagged

Other · Code Health — Whether a child process that has BOTH standard streams redirected drains both — reading one to the end while the other is never read deadlocks once the child fills the unread pipe.

Method: Roslyn syntax + semantics: ProcessStartInfo launches with both streams redirected, checked for a drain of each stream across the enclosing type. On a repository with no .NET source it reads JavaScript/TypeScript off the engine’s own token stream (test, vendored and minified paths not) with the same rule: a `spawn` imported from `child_process` whose stdout and stderr are both pipes (no options, no `stdio`, or `stdio` of `'pipe'`), bound to a local that never leaves its scope, where exactly one of the two streams is read, the other never, and the child’s `close`/`exit` (or the read stream’s end) is awaited; a shell redirect in the call’s arguments or a `kill` of the child suppresses it. The same rule reads Python’s `subprocess.Popen`, Dart’s `Process.start`, Ruby’s `Open3.popen3`, and Scala’s JDK process starts (`new ProcessBuilder(…).start()` with no `redirectErrorStream`/`redirectError`/`redirectOutput`/`inheritIO`, `Runtime.getRuntime.exec`) where one of `getInputStream`/`getErrorStream` is read and the other never while `waitFor()` is called or the read stream is read to its end. Deterministic, provable per finding. Advisory.

X14 · Bypassable address classification10.0 / 10Exemplary○ Nothing flagged

Other · Security — Whether a hand-rolled public/private IP check can be walked past — a method that unwraps IPv4-mapped IPv6 but returns the opposite verdict for the same host written as IPv4-compatible, 6to4 or NAT64.

Method: Roslyn syntax + semantics: methods that unwrap IPv4-mapped IPv6 and hand-roll IPv4 range carve-outs, checked for whether the IPv6 branch also accounts for the IPv4-compatible, 6to4 and NAT64 embeddings. Deterministic, provable per finding. Advisory.

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

Other · Code Health — Whether a loop that shortens a string until it fits a length budget has a floor — one with none grinds the value down to the empty string, or past it into a negative-length `Substring`.

Method: Roslyn syntax + semantics: while/do loops whose body's only effect on a string is to drop its last character, checked for whether anything — a direct comparison on the length, a body guard, a break — bounds that length below. On a repository with no .NET source it reads JavaScript/TypeScript off the engine’s own token stream (test, vendored and minified paths not) with the same rule: a `while`/`do` loop whose body’s one assignment to a value is `x = x.slice(0, -1)` or `x = x.slice|substring|substr(0, x.length - 1)`, driven by a condition that reads `x.length` only as a term of a larger expression — never compared directly, never tested for truthiness, and with no other read of `x` — and whose body has no `break`, `return`, `throw` or `if` naming `x`. Deterministic, provable per finding. Advisory.

X18 · Disposal-pattern correctness7.0 / 10Adequate✓ Tool-verified

Other · Code Health — Whether a type's disposal matches what it OWNS — releasing what it created, leaving alone what it was handed, and not declaring a finalizer for state that has nothing unmanaged to finalize.

Method: Roslyn syntax + semantics: every assignment to a disposable field is read to decide whether the type CREATED the value or was handed it, and the type's disposal is checked against that answer — an injected interface it disposes, a value it constructed and never releases, a finalizer on a type holding nothing unmanaged, and a disposable local whose every reference is a plain member read. A value handed to a container that disposes its contents (a parent control's `Controls` collection, a component `IContainer`) is released by that container and is not reported; generated code is out of population. On a repository with no .NET source the same ownership questions are read in JavaScript/TypeScript off the engine’s own token stream (test, vendored, generated and minified paths not): a class declaring `dispose()`, `[Symbol.dispose]()` or `[Symbol.asyncDispose]()` that disposes a field it was handed through a constructor parameter typed as a repository interface or resolved by a dependency-injection container; that assigns a field only ever from `new X(…)` of a disposable class and neither releases it anywhere in the class nor names it in its disposal member or a method that member calls, nor hands it to anything else; and a `const`/`let` local built from literals only whose every reference opens a statement operating on a non-release member of it. A class is disposable when every repository declaration of its name declares or inherits a disposal member, or when it is a documented library disposable (`vscode` EventEmitter, CancellationTokenSource and Disposable; three.js geometries, materials, textures, render targets, renderers, controls and composers). The finalizer arm has no JavaScript counterpart: a class cannot declare one. Dart is read for the owned-and-never-released arm: a Flutter `State` (or a class declaring `dispose()`/`close()`) whose library-private field is written only with direct creations of a framework controller, `FocusNode`, `StreamController` or periodic `Timer` (or a `.listen(…)` into a field declared `StreamSubscription`), which nothing in the class or its library releases (`dispose`/`close`/`cancel`) and which is never handed on except as a named argument. Ruby is read for the owned-and-never-released arm and the abandoned-local arm: a class declaring an instance `close`, `dispose`, `shutdown`, `stop`, `disconnect` or `terminate` whose instance variable is written only with a blockless core descriptor creation (`File.open`/`new`, `Tempfile`, `Dir.open`, `IO.popen`, the `socket` and `openssl` socket classes) that no method of the class closes and that is never handed on (passed, returned, stored, exposed by `attr_reader`, delegated) — a class whose superclass or mixin lies outside the repository is not judged — and a blockless creation read through and dropped (`File.open(path).read`) or held in a local that is never closed, returned, passed or stored (a `&:read` block-pass, an `autoclose: false` borrow and a `fileno` hand-over are not abandonment). PHP is read for the same two arms: a class (not a trait, and not one using a trait) declaring an instance `close`, `dispose`, `shutdown`, `stop`, `disconnect` or `terminate` whose `private` property (or a `final` class's `protected` one) is written only with a direct core `fopen`, `tmpfile`, `popen`, `proc_open`, `fsockopen`, `stream_socket_client`/`server` or `opendir` that nothing in the class closes (`fclose`, `pclose`, `closedir`, `unset`, a reset to `null`) and that is never handed on, and a handle held in a function's local, or read through as the argument of a reader, that is never closed, returned, passed, captured or stored; a `php://` stream, `curl_init`, `SplFileObject`, `PDO` and a function the repository declares under the core name are not read. Deterministic, provable per finding. Advisory.

  • `StatsFilterState` carries a disposal duty — a `State`, so the framework calls its `dispose()` when it leaves the tree — and it creates `_ctrl` itself (line 26, `TextEditingController`), which makes that instance its own. Nothing in the class releases it — no `_ctrl.dispose()`, no tear-off of it, on any path — nothing elsewhere in the library releases it through another instance, and it is never handed on as a value (passed positionally, returned, stored, collected), so no other owner can be ending it. Passing it as a named argument does not: a widget or animation never disposes a controller it was given. On what was read, `TextEditingController` outlives the object that made it — its listeners, and through them this object and everything it references, stay reachable, and a ticker, timer or subscription keeps calling into a disposed object. Release it where the duty is discharged: `_ctrl.dispose();` in `dispose()` before `super.dispose()`. — common/lib/src/features/stats/ui/stats_filter.dart:26

What to do

  • Each finding names the value and the span that decides who owns it — the `new` that created it, or the constructor parameter that handed it over. Confirm ownership from that span, then make the disposal match it: release what this type created, leave what it was injected with to whoever created THAT, and drop a finalizer whose type holds nothing unmanaged to release.
X19 · Unrestored process-global state10.0 / 10Exemplary○ Nothing flagged

Other · Code Health — Whether a method that temporarily changes state belonging to the whole process — the working directory, an environment variable — puts it back on EVERY path: a restore reached only when nothing throws leaks the change to the rest of the process.

Method: Roslyn syntax + semantics: method bodies that write the process working directory or an environment variable and write it back in the same body, checked for whether that restore sits in a `finally`/`catch` or only on the straight-line path. On a repository with no .NET source the same rule reads production JavaScript/TypeScript off the engine’s own token stream (test, vendored and minified paths not): `process.chdir`, `process.env.NAME =`/`["NAME"] =` and `delete process.env.NAME`, and Deno’s `Deno.chdir`/`Deno.env.set`/`Deno.env.delete`, paired per function body (a nested function or arrow is its own body, and module top-level code is none), where the last write puts back a local the body captured from the same global or deletes a variable the first write set, with at least one statement between them; a write in a `catch`/`finally` of that body silences it. Deterministic, provable per finding. Advisory.

X2 · Cancellation propagation4.0 / 10Weak✓ Tool-verified

Other · Code Health — Whether async functions that make a cancellable request accept or pass on an AbortSignal (adoption curve).

Method: Roslyn scan: every async method (excluding framework-fixed overrides/Blazor handlers) checked for CancellationToken parameter presence. Deterministic, adoption percentage. On a repository with no .NET source it reads JavaScript/TypeScript off the engine’s own token stream (test, vendored and minified paths not) with the same question: every named async function that itself makes a request an AbortSignal can cancel (global `fetch`, axios and its file-local instances, ky, ofetch) counts, and it is compliant when its parameters or body name a signal or it hands one of its own parameters to the request as options; signatures a framework fixes (JSX event handlers, route and lifecycle exports, request-first handlers, `override`, `'use server'` modules, TanStack `mutationFn`) are exempt unless they take a signal. Deterministic, adoption percentage.

  • Only 0/1 async functions that make a cancellable request (fetch, axios, ky, ofetch, got, undici, node:http) accept an AbortSignal or pass one on, so a request keeps running after whatever wanted it has given up — a page navigated away from, an unmounted component, a timed-out job. Take a `signal` (or an options object that carries one) and hand it to the request; where nothing could ever cancel the call, omitting it is a deliberate choice — judge against how the function is used.
  • `isAppiumServerReady` awaits `fetch(…)` but neither accepts an AbortSignal nor passes one on, so its caller cannot stop the request once it has started. Accept `{ signal }` and pass it through: `fetch(url, { signal })`. — REDACTED:340

What to do

  • Thread an AbortSignal through async functions that make requests, so the work stops when its caller gives up.
X21 · Side-effecting pattern guard10.0 / 10Exemplary○ Nothing flagged

Other · Code Health — Whether a `when` guard is free of side effects — a guard that increments a counter or assigns while deciding whether its arm matches applies that change during PATTERN MATCHING, on an arm that may not be selected, and skips it entirely when a short-circuit to its left answers first.

Method: Roslyn syntax: `when` guards on case labels and switch-expression arms, read for a mutation (`++`/`--`/assignment) sitting in a position the guard's own `&&`/`||`/`??`/`?:`/`?.` can skip. Deterministic, provable per finding. Advisory.

X23 · Unguarded diagnostic materialisation10.0 / 10Exemplary○ Nothing flagged

Other · Code Health — Whether the work a diagnostic log line costs is paid only when that line is wanted — C# evaluates a call's arguments BEFORE the call, so a trace/debug message joined or projected out of a collection is built in full on every pass, and then discarded by a sink the shipped configuration leaves switched off.

Method: Roslyn syntax: log calls at a diagnostic level (a `Log`-prefixed method naming Trace/Debug/Verbose, or a bare `Debug`/`Trace`/`Verbose` on a receiver named for a logger), whose argument list is read for a call whose cost scales with a sequence — a LINQ operator, a materialisation, `string.Join`, a serializer — with no enclosing level check or conditional-compilation region. On a repository with no .NET source it reads JavaScript/TypeScript off the engine’s own token stream (test, vendored and minified paths not) with the same rule: a `debug`/`trace`/`verbose` call on a receiver named for a logger, or a `log`-prefixed method naming the level, whose argument calls an array operator (`map`/`filter`/`reduce`/`sort`/…), `Array.from`, `Object.keys/values/entries`, `JSON.stringify`/`util.inspect` over anything but a literal, or an array `join` — outside any arrow or function passed as an argument, which the logger calls only when the level is on — with no enclosing `if`, `&&` or `?:` whose condition names a level, a level string, or the `NODE_ENV`/`__DEV__`/`DEV` build switch. Deterministic, provable per finding. Advisory.

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

Other · Code Health — Whether a value the caller is invited to supply is the value the type actually uses — a constructor parameter stored in a private field that nothing ever reads while the default it was given is spelled out a second time at the site that should have read it, a keyed lookup that falls back to a different setting than the one its key names while the same type falls back to the matching one for that same key, or a culture-sensitive parse given no format provider by a type that feeds its own settable culture to the same kind of parse elsewhere, or a number an entry point writes to standard output under the host's culture while the same entry point formats with the invariant culture elsewhere. Either way, every caller who supplies a value silently gets something else.

Method: Roslyn syntax: private instance fields of a non-partial type assigned in a constructor from one of its own parameters with a `??` fallback, checked for whether anything in the type body reads the field and whether that same fallback expression is spelled out again outside the constructor; and `??` fallbacks onto a member access from a lookup call carrying exactly one string literal, grouped by that key across the type and checked for a fallback member whose folded name disagrees with the key while a sibling site for the same key agrees with it. On a repository with no .NET source the first two arms read JavaScript/TypeScript off the engine’s own token stream (tests included, bundles and vendored paths not): a `#x`, `private` or `private` parameter-property instance field filled in the constructor from a parameter (or one member of one) through `??`/`||` or a parameter default, never read anywhere in the file by name, whose constructed default is spelled again in the class body; and `lookup("key") ?? s.member` grouped by key per class, or per module outside every class. The culture arm has no JavaScript counterpart: its parses take no locale. Deterministic, provable per finding. Advisory.

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

Other · Code Health — Whether a `for` loop leaves the `dict`, `set` or `deque` it is walking alone — CPython's iterators over those check that the collection has not changed size since the loop began, so a body that removes from (or empties) the very collection the loop is walking makes the next step raise `RuntimeError: dictionary changed size during iteration` and the remaining items are never seen. Whether a `for … in` loop leaves the `List`, `Map` or `Set` it is walking alone — Dart's collection iterators check that the collection has not changed since the loop began, so a body that adds to or removes from the very collection the loop is walking (or the map whose `keys`, `values` or `entries` it walks) makes the next step throw `ConcurrentModificationError` and the remaining elements are never seen. Whether a walk over a `Hash` or `Set` (`each`, `each_pair`, `map`, `for … in` and the other block walks) leaves it alone — Ruby refuses `rehash`, `replace`, `compare_by_identity` and `transform_keys!` on a Hash, and `reset`, `replace`, `compare_by_identity` and `map!` on a Set, while it is being iterated: the call raises `RuntimeError` at once and the remaining entries are never seen. Whether a `for (x in c)` or `c.forEach { … }` leaves the collection it is walking alone — a `mutableListOf`/`ArrayList`, `mutableMapOf`/`HashMap` or `mutableSetOf`/`HashSet` is a `java.util` collection on the JVM and is walked by its own fail-fast iterator, so a body that adds to or removes from the very collection the loop is walking makes the next step throw `ConcurrentModificationException` and the remaining elements are never seen.

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

X28 · Index access outside its own emptiness guard10.0 / 10Exemplary○ Nothing flagged

Other · Code Health — Whether a condition that tests a value for emptiness indexes that same value only where the test holds — an `||` written one parenthesis too far to the left leaves an index access outside the guard beside it, so the empty case the guard exists to anticipate reaches the index and throws.

Method: Roslyn syntax only, no semantic model: the OUTERMOST `&&`/`||` of every boolean condition, read for a symbol the condition tests for emptiness (`string.IsNullOrEmpty`/`IsNullOrWhiteSpace`, a `Length`/`Count` comparison against a literal, `Any()`, a `Length`/`Count` pattern, or a comparison against `""`) and ALSO indexes. Each `symbol[...]` access is placed by a boolean-reachability walk from the access up to the outermost connective: an access is COVERED when some enclosing step has it in the right operand and the left operand, under the truth value that step forces, proves the symbol non-empty — a recursion over `&&`/`||` whose true- and false-directions are asymmetric. A finding needs BOTH an uncovered access and a covered one on the same symbol in the same condition, which is the agreeing twin that separates a misplaced parenthesis from an unrelated length test. Bare index accesses with no emptiness test in the condition are neither counted nor reported; a non-identifier receiver and a lambda nested inside the condition are outside the population. Deterministic, provable per finding. Advisory.

X29 · Per-element action decided by a fixed element10.0 / 10Exemplary○ Nothing flagged

Other · Code Health — Whether a decision taken once per element is taken ABOUT that element — a test inside a counted loop that reads a fixed subscript of the very collection its guarded statement indexes by the loop variable applies element zero's answer to all of them, so the elements that differ from it are all handled wrongly, and in the same direction.

Method: Roslyn syntax only, no semantic model: every `for` statement declaring exactly ONE loop variable, and every `if` inside its body that is not under a nested loop or a lambda. A site enters the population when the `if`’s condition never mentions the loop variable while the statement it guards indexes some collection by that variable ALONE (`c[i]`; `c[i + 1]` and `c[i, j]` are outside it). A finding additionally needs the AGREEING TWIN at the same-collection grain: the condition must read THAT SAME collection at a subscript that does not move — written into the condition, or reached through a local declared BEFORE the loop, so an alias bound inside the body is not followed. Both collection expressions must be simple identifiers. On a repository with no .NET source the same rule reads JavaScript/TypeScript off the engine’s own token stream (tests included, bundles and vendored paths not): a `for (let|var|const x = …; …; …)` with one declarator and a braced body, an alias followed only when it is declared before the loop in a block that encloses it and never assigned inside the loop. Deterministic, provable per finding. Advisory.

X3 · Exception handling6.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. (×2) — ios/App/Util/JsonUtil.swift:65, ios/App/Binding/CoreBinding.swift:294
  • `except Exception` 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. — common/websocket.py:12
  • `catch (e)` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter. (×4) — common/lib/src/platform/stage/stage.dart:42, common/lib/src/features/stats/ui/stats_detail_section.dart:43, common/lib/src/features/payment/domain/attribute_converter.dart:83, …
  • An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it. (×21) — common/lib/src/platform/app/launch_context.dart:57, common/lib/src/platform/app/launch_context.dart:128, common/lib/src/features/notification/domain/event.dart: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. (×3) — common/lib/src/features/support/domain/actor.dart:409, common/lib/src/features/notification/domain/actor.dart:555, common/lib/src/app_variants/v6/widget/home/stats/privacy_pulse_section.dart:412
  • `catch (ex: Throwable)` 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. — android/app/src/main/java/model/Error.kt:58

What to do

  • Swallowed exception (caught, then discarded)
X30 · Support guard that admits what it rejects10.0 / 10Exemplary○ Nothing flagged

Other · Code Health — Whether a guard written as a NEGATED `||` says what its author meant — `!(a || b || x != k)` is `!a && !b && x == k` by De Morgan, so a bail-out that mixes capabilities the code needs with a fault it refuses turns inside out: it fires only where the capabilities are ABSENT, and lets every value the fault term names walk straight into the body that cannot handle it.

Method: Roslyn syntax only, no semantic model: every logical-not whose operand is a parenthesised `||` chain of two or more disjuncts, flattened (a left-nested `a || b || c` read once would see `(a || b)` as one disjunct). A site enters the population on that shape alone. A finding additionally needs the disjuncts to DISAGREE in polarity: at least one bare boolean read — an identifier or member access, never an invocation, which is a predicate rather than a capability flag — and at least one `x != <constant>`, the only form that negates into an exact-value pin (`== null` negates into a looser requirement and is outside the fault set). Consistently-polarised disjunctions, all-fault or all-capability, are counted and never reported; a negated `&&` is outside the population entirely. No same-receiver gate: it was measured to cost a real defect and remove no false positive. Deterministic, provable per finding. Advisory.

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

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

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

Reference — by lens

The score is the rank-weighted fold of these lenses (worst-heaviest), each including its meta-dimensions; a lens with a Critical contributor is capped at Fair (its band reads "gated by …") and is never the strongest area however high its average.

LensScoreRatingImpact
Code Health58%Adequate — gated by R1Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Architecture93%Adequate — gated by D26Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Maturity71%Adequate — gated by M2Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Readiness65%Adequate — gated by P3Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Security66%Checked 5 of 11Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Domain Modelling80%StrongStrongest area.
Performance60%AdequateAcceptable, with room to improve.
Unscored — 5 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.

  • AXH1 Runtime security headers — 11 observation(s) recorded · Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
  • AXI1 Runtime container hardening — 1 observation(s) recorded · Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
  • AXR1 Runtime accessibility (rendered) — 2 observation(s) recorded · Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
  • X10 Duplicated predicate — 9 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
  • X7 Silent fallback defaults — 4 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
Not evidenced — 4 control(s) we could not find positive evidence for

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

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

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

  • AC1 Text alternatives — Frontend below the scale floor (19 DOM element(s) < 25) — too little surface to assess accessibility.
  • AC2 Forms & labels — Frontend below the scale floor (19 DOM element(s) < 25) — too little surface to assess accessibility.
  • AC3 Page structure — Frontend below the scale floor (19 DOM element(s) < 25) — too little surface to assess accessibility.
  • AC4 Keyboard semantics — Frontend below the scale floor (19 DOM element(s) < 25) — too little surface to assess accessibility.
  • AC5 ARIA correctness — Frontend below the scale floor (19 DOM element(s) < 25) — too little surface to assess accessibility.
  • AC6 Visual & motion safety — Frontend below the scale floor (19 DOM element(s) < 25) — too little surface to assess accessibility.
  • AX2 Stateful singletons — No container singleton was found, so there is no shared instance for concurrent requests to race on. No class in this Kotlin code is a Spring, JSR-330 or CDI singleton bean. No 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 class in this Ruby code is a Rails controller, a Sinatra, Grape or Roda app, a Hanami action or a Rack app (an instance `call(env)`), so no request handler shares state 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. Dart isolates share no mutable memory, so no two requests write one object at the same instant. TypeScript/JavaScript runs each process's requests on one event loop, so no two requests write a shared object at the same instant (interleaving across an await is a different defect).
  • AX5 Architecture & structure — not assessed — architecture style/structure is computed from a project graph (projects, types, module namespaces) that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
  • AX6 Interface segregation — no exported interface declares behaviour
  • AX7 Slice cohesion — not applicable — not a vertical-slice architecture
  • AXA1 Runtime unauthenticated reachability — This run crawled public routes only — it had no logged-in session, so there is no authenticated surface to compare anonymous access against and nothing was measured. This is a statement about this run, not about your application: nothing here says access control is missing, and nothing here says it is present.
  • AXB2 Runtime readiness — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
  • 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 included — no .dart test runner
  • D16 Bus Factor — single-maintainer repository — bus factor is not applicable
  • D18 Solution Shape — D18 scores the shape of a .NET solution; this repository has no .NET solution or project files, so the dimension does not apply.
  • D21 Naming Consistency — Naming consistency is measured on C# and TypeScript only; Dart, JavaScript, Kotlin, Python, Ruby, Swift not measured.
  • D22 Internal API Consistency — API consistency is measured on C# only; the exposed Swift surface was not measured.
  • D23 Boundary Type-Coupling — No bounded-context organisation was detected either — neither a context-shaped layout, nor 2+ sibling source directories each declaring an aggregate root, nor 2+ sibling projects each declaring an entity of their own or taking another project's integration events. Declaring this codebase's bounded contexts (≥2) would let cross-boundary type coupling be assessed. Declare them in `.codehealth/config.yaml` at the repository root (create it if absent), mapping each context name to the module-path or namespace prefixes that belong to it — e.g. `architecture:` → `contexts:` → `Billing: ["src/billing", "Acme.Billing"]`, `Catalog: ["src/catalog", "Acme.Catalog"]`.
  • D25 ADR Conformance — no ADRs to check
  • D27 Navigability — D27 counts a call into the standard library or a dependency as unresolved for this repository's language (.dart), so too few call sites counted as resolved to assess navigability. Not scored: this is a gap in the analyzer, not a verdict about this repository.
  • D32 Data Compliance (PII/GDPR) — 3 file(s) were not parsed by semgrep — the PII/GDPR ruleset never ran over them
  • D37 Vulnerability-disclosure Policy — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed.
  • D40 Network Egress Confinement — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here.
  • D41 Kernel & Syscall Confinement — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here.
  • D42 Runtime Threat Enforcement — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here.
  • 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 — JavaScript/TypeScript suite
  • DM2 Strongly-typed ids — no in-repo typed-id idiom — primitive-obsession recorded as advisory DM8, DM2 not gated
  • DM3 Integration-event coupling — no integration events detected — coupling check not applicable
  • DM6 Domain ↔ infrastructure boundary — this Dart repository maps no type to a persistence framework (drift/floor/isar/objectbox/hive), so DM6's domain↔infrastructure fusion read has no population to be taken over
  • DM7 Repository granularity — no repository abstraction detected (e.g. uses a document session)
  • ED2 Event/command shape — not scored — deciding whether a command has more than one competing handler requires resolving the call graph, and this analysis resolves a call's owner only where the receiver's type is written down in the source. Reported as guidance rather than measured
  • ED2 Event/command shape — not scored — deciding whether a command has more than one competing handler requires resolving the call graph, which this analysis does not build from source alone for this language. Reported as guidance rather than measured
  • ED5 Idempotency — no mutating command handlers or message consumers detected — idempotency check not applicable
  • ES1 Event Sourcing — not scored — this repository shows none of the 3 signals this lens looks for
  • P12 CI test-gate honesty — Reported, not scored — and nothing was matched here. The coverage check applies to any stack, and the automatic-re-run check to any GitHub-Actions workflow, but the checks for excluded tests, skipped tests and sleep-based synchronisation currently recognise only some ecosystems' test-runner idioms, so on a repository built with another stack the zeros below mean 'not checked', not 'clean'.
  • P7 Outbound HTTP resilience — not applicable — no HTTP server, API framework or worker entry point was found in the Dart, JVM, JavaScript/TypeScript, Python, Ruby, Swift source, so there is no service whose uptime a failing dependency could take down
  • P8 Schema migrations — no ORM, schema-migration tool or schema auto-create was found in this repository's dependency manifests or source, so there is no database schema for this check to judge
  • P9 Domain vs controller coverage — no coverage report found on disk — produce a coverage report in a standard format (lcov — `flutter test --coverage` (or `dart test --coverage=coverage` then `dart run coverage:format_coverage --lcov`)) and commit it — a hosted scan measures a clone of the repository, so a report that exists only in a working tree, a CI runner's or your own, never reaches it; the artefact is commonly gitignored, so `git add -f` that one file (or un-ignore its path) and commit it alongside the code it measures, or wire coverage collection into CI, to enable this cross-layer check
  • PF1 Benchmark discipline — Not applicable: no benchmark suite was found. This check searched for classes extending benchmark_harness's `BenchmarkBase`, `AsyncBenchmarkBase` or `PerfBenchmarkBase` (directly or through a base of your own), `benchmark(…)` calls under the pub `benchmark` package, Flutter's `benchmarkWidgets`, `watchPerformance` or `traceAction` in a test importing flutter_test, integration_test or flutter_driver, or benchmark_harness, benchmark or web_benchmarks in a pubspec.yaml, and for a `*benchmark*` script that this repository's CI runs. Benchmarks are credited as a bonus, so their absence is neither scored nor deducted.
  • PF2 Allocation hygiene — Not scored: this check counted allocation-aware idioms (Span, pools, stackalloc) per line, which describes what kind of code a repository is rather than whether it has an allocation problem, so it was withdrawn. Nothing here is a finding about your code.
  • R11 Import Boundaries — No recognizable feature-sliced/layered src layout — boundary rules not applicable.
  • S1 Web-Security Posture — Not assessed: these web-security controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks web-security controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
  • SC1 Supply-chain hygiene — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
  • X15 Unvalidated length from an untrusted reader — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
  • X17 Uncapped recursion over a caller-supplied document — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
  • X20 Mistyped argument guard — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
  • 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
  • X24 Document value interpolated into markup unescaped — X24 reached only 14% of this repository's production lines — dart (46,747 lines), swift (9,881 lines), kotlin (8,955 lines), objectivec (3 lines) was left unread. Not scored: a score over a minority of the product would be published as the whole of it.
  • X26 Unsynchronised callback handoff — X26 reached only 27% of this repository's production lines — dart (46,747 lines), javascript (6,502 lines), typescript (2,191 lines), objectivec (3 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 — This check asks whether log calls keep a message's values apart from its text, which needs a logger that can carry them as fields. This repository's Dart was read, and it logs through none: package:logging, package:logger, talker and dart:developer take one finished message and no template arguments or fields (as log4net does in C#), so an interpolated message there loses nothing the API could have kept. Sentry's structured logs (`Sentry.logger`) would be judged.
  • X6 Hand-rolled structured-format parsing — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
  • X9 Subsumed condition operand — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.

Appendix A — Findings (grouped)

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

Critical — 57 finding(s)
D29 · Static Analysis (SAST) · REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • + 13 more in this group — see findings.md.
DM4 · Rich vs anemic domain model · Anemic domain model · ×13
  • Anemic domain model: HttpRequest common/lib/src/features/api/domain/endpoint.dart:6 — `HttpRequest` is a data-only domain entity with public mutable state and no invariant-enforcing behaviour of its own, while the repo holds the logic in a foreign service/manager/use-case — the anemic domain model. Move the behaviour onto the entity so it enforces its own invariants (or make it an immutable `@freezed` value object) rather than being driven from outside.
  • Anemic domain model: JsonCustomListPayload common/lib/src/features/customlist/domain/api.dart:67 — `JsonCustomListPayload` is a data-only domain entity with public mutable state and no invariant-enforcing behaviour of its own, while the repo holds the logic in a foreign service/manager/use-case — the anemic domain model. Move the behaviour onto the entity so it enforces its own invariants (or make it an immutable `@freezed` value object) rather than being driven from outside.
  • Anemic domain model: JsonJournalEntry common/lib/src/features/journal/domain/api.dart:22 — `JsonJournalEntry` is a data-only domain entity with public mutable state and no invariant-enforcing behaviour of its own, while the repo holds the logic in a foreign service/manager/use-case — the anemic domain model. Move the behaviour onto the entity so it enforces its own invariants (or make it an immutable `@freezed` value object) rather than being driven from outside.
  • Anemic domain model: JsonListItem common/lib/src/features/list/domain/api.dart:29 — `JsonListItem` is a data-only domain entity with public mutable state and no invariant-enforcing behaviour of its own, while the repo holds the logic in a foreign service/manager/use-case — the anemic domain model. Move the behaviour onto the entity so it enforces its own invariants (or make it an immutable `@freezed` value object) rather than being driven from outside.
  • Anemic domain model: JsonFcmNotificationPayload common/lib/src/features/notification/domain/api.dart:3 — `JsonFcmNotificationPayload` is a data-only domain entity with public mutable state and no invariant-enforcing behaviour of its own, while the repo holds the logic in a foreign service/manager/use-case — the anemic domain model. Move the behaviour onto the entity so it enforces its own invariants (or make it an immutable `@freezed` value object) rather than being driven from outside.
  • Anemic domain model: JsonAdaptyPayload common/lib/src/features/payment/domain/api.dart:3 — `JsonAdaptyPayload` is a data-only domain entity with public mutable state and no invariant-enforcing behaviour of its own, while the repo holds the logic in a foreign service/manager/use-case — the anemic domain model. Move the behaviour onto the entity so it enforces its own invariants (or make it an immutable `@freezed` value object) rather than being driven from outside.
  • Anemic domain model: JsonLease common/lib/src/features/plus/domain/lease/api.dart:24 — `JsonLease` is a data-only domain entity with public mutable state and no invariant-enforcing behaviour of its own, while the repo holds the logic in a foreign service/manager/use-case — the anemic domain model. Move the behaviour onto the entity so it enforces its own invariants (or make it an immutable `@freezed` value object) rather than being driven from outside.
  • Anemic domain model: JsonLeasePayload common/lib/src/features/plus/domain/lease/api.dart:68 — `JsonLeasePayload` is a data-only domain entity with public mutable state and no invariant-enforcing behaviour of its own, while the repo holds the logic in a foreign service/manager/use-case — the anemic domain model. Move the behaviour onto the entity so it enforces its own invariants (or make it an immutable `@freezed` value object) rather than being driven from outside.
  • Anemic domain model: JsonSupportPayloadCreateSession common/lib/src/features/support/domain/json.dart:3 — `JsonSupportPayloadCreateSession` is a data-only domain entity with public mutable state and no invariant-enforcing behaviour of its own, while the repo holds the logic in a foreign service/manager/use-case — the anemic domain model. Move the behaviour onto the entity so it enforces its own invariants (or make it an immutable `@freezed` value object) rather than being driven from outside.
  • Anemic domain model: JsonSupportSession common/lib/src/features/support/domain/json.dart:63 — `JsonSupportSession` is a data-only domain entity with public mutable state and no invariant-enforcing behaviour of its own, while the repo holds the logic in a foreign service/manager/use-case — the anemic domain model. Move the behaviour onto the entity so it enforces its own invariants (or make it an immutable `@freezed` value object) rather than being driven from outside.
  • Anemic domain model: JsonSupportPayloadMessage common/lib/src/features/support/domain/json.dart:90 — `JsonSupportPayloadMessage` is a data-only domain entity with public mutable state and no invariant-enforcing behaviour of its own, while the repo holds the logic in a foreign service/manager/use-case — the anemic domain model. Move the behaviour onto the entity so it enforces its own invariants (or make it an immutable `@freezed` value object) rather than being driven from outside.
  • Anemic domain model: JsonSupportHistoryItem common/lib/src/features/support/domain/json.dart:152 — `JsonSupportHistoryItem` is a data-only domain entity with public mutable state and no invariant-enforcing behaviour of its own, while the repo holds the logic in a foreign service/manager/use-case — the anemic domain model. Move the behaviour onto the entity so it enforces its own invariants (or make it an immutable `@freezed` value object) rather than being driven from outside.
  • Anemic domain model: JsonSupportAction common/lib/src/features/support/domain/json.dart:196 — `JsonSupportAction` is a data-only domain entity with public mutable state and no invariant-enforcing behaviour of its own, while the repo holds the logic in a foreign service/manager/use-case — the anemic domain model. Move the behaviour onto the entity so it enforces its own invariants (or make it an immutable `@freezed` value object) rather than being driven from outside.
D28 · Secrets (history) · REDACTED · ×3
  • REDACTED
  • REDACTED
  • REDACTED
D28 · Secrets (history) · High secret · ×1
  • REDACTED
D29 · Static Analysis (SAST) · REDACTED · ×1
  • REDACTED
D31 · IaC & Container Security · High IaC · ×1
  • REDACTED
Serious — 498 finding(s)
D17 · Explicit Debt · TodoComment · ×52
  • TodoComment ios/WireguardCopiedFiles/TunnelsTracker.swift:68 — // TODO: should be unknown? — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
  • TodoComment ios/NotFamily/ContentView.swift:72 — // TODO: remove his global alert thing — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
  • TodoComment ios/Family/ContentView.swift:70 — // TODO: remove his global alert thing — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
  • TodoComment ios/NotFamily/WgService.swift:245 — // TODO: paused? — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
  • TodoComment ios/App/Util/Tasker.swift:65 — // // TODO: what about major errors — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
  • TodoComment ios/App/Service/AppDelegate.swift:251 — // Handle universal links TODO: Also in SceneDelegate — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
  • TodoComment ios/App/Service/PrivateDnsService.swift:117 — // TODO: possibly check the exact serverURL here — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
  • TodoComment ios/App/Binding/CoreBinding.swift:23 — // TODO: currently if asked for secure AND backup store, we will use the — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
  • TodoComment ios/App/Binding/FamilyBinding.swift:17 — // TODO: this should be included only in Family targets but AppDelegate needs refactor — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
  • TodoComment ios/App/Binding/Vpn/NetxServiceIn.swift:92 — // TODO: pause — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
  • TodoComment ios/App/Binding/Stage/StageBinding.swift:51 — // TODO: a better place — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
  • TodoComment common/test/platform/device/device_test.dart:127 — // TODO: verify bad json input from api — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
  • TodoComment common/lib/modules.dart:89 — // TODO: All onRegister calls here have to be replaced with modules — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
  • TodoComment common/lib/modules.dart:265 — // TODO: refactor this — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
  • TodoComment common/lib/src/shared/navigation.dart:149 — // TODO: this needs rework and merging with StageStore — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
  • TodoComment common/lib/src/platform/stats/stats.dart:60 — // TODO: Ugly hack — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
  • TodoComment common/lib/src/platform/stage/stage.dart:281 — // TODO: obsolete, unused anymore — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
  • TodoComment common/lib/src/platform/stage/stage.dart:308 — // TODO: this needs to be removed — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
  • TodoComment common/lib/src/platform/perm/dnscheck.dart:179 — // TODO: implement — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
  • TodoComment common/lib/src/platform/filter/actor.dart:50 — // todo: default value at first start of new account — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
  • TodoComment common/lib/src/platform/filter/actor.dart:59 — // TODO: remove this — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
  • TodoComment common/lib/src/platform/device/device.dart:230 — // TODO: refactor — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
  • TodoComment common/lib/src/platform/core/command.dart:6 — // TODO: This should not be a dep of core — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
  • TodoComment common/lib/src/platform/core/command.dart:8 — // TODO: This should not be a dep of core — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
  • TodoComment common/lib/src/platform/app/start/start.dart:147 — // TODO: replace with new modal approach — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
  • + 27 more in this group — see findings.md.
X3 · Exception handling · Swallowed exception (empty catch) · ×21
  • Swallowed exception (empty catch) common/lib/src/platform/app/launch_context.dart:57 — An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
  • Swallowed exception (empty catch) common/lib/src/platform/app/launch_context.dart:128 — An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
  • Swallowed exception (empty catch) common/lib/src/features/notification/domain/event.dart:38 — An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
  • Swallowed exception (empty catch) common/lib/src/app_variants/family/module/schedule/platform_timezone.dart:21 — An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
  • Swallowed exception (empty catch) common/lib/src/app_variants/family/module/auth/actor.dart:35 — An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
  • Swallowed exception (empty catch) automation/shared/lib/devices.mjs:126 — An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
  • Swallowed exception (empty catch) automation/dep-validate/lib/queue.mjs:292 — An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
  • Swallowed exception (empty catch) automation/appium/wdio/src/flows/alerts.ts:98 — An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
  • Swallowed exception (empty catch) automation/appium/wdio/src/flows/alerts.ts:124 — An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
  • Swallowed exception (empty catch) automation/appium/wdio/src/flows/alerts.ts:141 — An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
  • Swallowed exception (empty catch) automation/appium/wdio/src/flows/alerts.ts:154 — An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
  • Swallowed exception (empty catch) automation/appium/wdio/src/flows/alerts.ts:163 — An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
  • Swallowed exception (empty catch) automation/appium/wdio/src/flows/modals.ts:27 — An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
  • Swallowed exception (empty catch) automation/appium/wdio/src/flows/settings.ts:187 — An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
  • Swallowed exception (empty catch) automation/appium/wdio/scripts/lib/ai-explorer-runner.mjs:955 — An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
  • Swallowed exception (empty catch) automation/appium/wdio/scripts/lib/explorer-commands.mjs:377 — An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
  • Swallowed exception (empty catch) android/app/src/six/kotlin/ui/MainApplication.kt:122 — An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
  • Swallowed exception (empty catch) android/app/src/main/java/service/ConnectivityService.kt:323 — An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
  • Swallowed exception (empty catch) android/app/src/main/java/service/FileService.kt:36 — An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
  • Swallowed exception (empty catch) android/app/src/main/java/binding/CoreBinding.kt:282 — An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
  • Swallowed exception (empty catch) android/app/src/main/java/binding/CoreBinding.kt:296 — An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
R4 · Test Coverage · No test reaches this file · ×14
  • No test reaches this file automation/dep-validate/report.mjs:1 — No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
  • No test reaches this file automation/dep-validate/lib/queue.mjs:1 — No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
  • No test reaches this file automation/appium/wdio/src/support/golden.ts:1 — No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
  • No test reaches this file automation/appium/wdio/scripts/run-wdio-android.mjs:1 — No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
  • No test reaches this file automation/appium/wdio/scripts/explore.mjs:1 — No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
  • No test reaches this file automation/device/log.mjs:1 — No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
  • No test reaches this file automation/appium/wdio/scripts/run-wdio.mjs:1 — No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
  • No test reaches this file automation/appium/wdio/scripts/setup-session.mjs:1 — No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
  • No test reaches this file automation/appium/wdio/scripts/lib/sim.mjs:1 — No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
  • No test reaches this file automation/dep-validate/queue.mjs:1 — No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
  • No test reaches this file automation/appium/wdio/scripts/ai-explore.mjs:1 — No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
  • No test reaches this file automation/appium/wdio/scripts/select-device.mjs:1 — No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
  • No test reaches this file REDACTED:1 — No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
  • No test reaches this file automation/appium/wdio/scripts/check-driver.mjs:1 — No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
D3 · God Classes · MethodTooLong · ×13
  • MethodTooLong: SettingsState.build common/lib/src/features/settings/ui/settings_section.dart:101 — MethodTooLong — build runs 231 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 131 over it, 2.31× 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: DomainDetailSectionState._getSubtitleText common/lib/src/features/stats/ui/domain_detail_section.dart:137 — MethodTooLong — _getSubtitleText runs 181 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 81 over it, 1.81× 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: DeviceSectionState.build common/lib/src/app_variants/family/widget/device/device_section.dart:103 — MethodTooLong — build runs 179 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 79 over it, 1.79× 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: QrScanSheetMacosState.build common/lib/src/app_variants/family/widget/home/qr_scan_sheet_macos.dart:94 — MethodTooLong — build runs 154 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 54 over it, 1.54× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
  • MethodTooLong: LinkDeviceSheetState.build common/lib/src/app_variants/family/widget/home/link_device_sheet.dart:119 — MethodTooLong — build runs 144 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 44 over it, 1.44× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
  • MethodTooLong: _LockScreenState.build common/lib/src/features/lock/ui/lock_screen.dart:236 — MethodTooLong — build runs 131 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 31 over it, 1.31× 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: HorizontalRadialSegmentState.build common/lib/src/features/stats/ui/horizontal_radial_segment.dart:132 — MethodTooLong — build runs 131 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 31 over it, 1.31× 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: StatsFilterState.build common/lib/src/features/stats/ui/stats_filter.dart:37 — MethodTooLong — build 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: TopDomainsState.build common/lib/src/features/stats/ui/top_domains.dart:76 — MethodTooLong — build runs 116 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 16 over it, 1.16× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
  • MethodTooLong: StatsDetailSectionState.build common/lib/src/features/stats/ui/stats_detail_section.dart:49 — MethodTooLong — build runs 115 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 15 over it, 1.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: SafariOnboardYtSheetIosState.build common/lib/src/features/safari/ui/safari_onboard_yt_sheet.dart:19 — MethodTooLong — build runs 110 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 10 over it, 1.10× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
  • MethodTooLong: DomainDetailSectionState._fetchSubdomains common/lib/src/features/stats/ui/domain_detail_section.dart:610 — MethodTooLong — _fetchSubdomains runs 110 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 10 over it, 1.10× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
  • MethodTooLong: RadialChart.build common/lib/src/app_variants/v6/widget/home/stats/radial_chart.dart:75 — MethodTooLong — build runs 106 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 6 over it, 1.06× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
D4 · Code Duplication · Duplicated block (8 lines × 2) · ×12
  • Duplicated block (8 lines × 2) common/lib/src/app_variants/family/widget/home/smart_onboard.dart:137 — common/lib/src/app_variants/family/widget/home/smart_onboard.dart:137-144 | common/lib/src/app_variants/family/widget/home/smart_onboard.dart:193-200 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
  • Duplicated block (8 lines × 2) common/lib/src/app_variants/family/widget/main_screen.dart:35 — common/lib/src/app_variants/family/widget/main_screen.dart:35-42 | common/lib/src/app_variants/v6/widget/main_screen.dart:32-39 — 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 `common/lib/src/app_variants/family/widget/main_screen.dart:35` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `common/lib/src/app_variants/family/widget/main_screen.dart:34` calls `FamilyAnimatedBg` and `common/lib/src/app_variants/v6/widget/main_screen.dart:31` does not — after which the two agree again for 4 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
  • Duplicated block (8 lines × 2) common/lib/src/app_variants/v6/widget/home/stats/radial_chart.dart:108 — common/lib/src/app_variants/v6/widget/home/stats/radial_chart.dart:108-115 | common/lib/src/app_variants/v6/widget/home/stats/radial_chart.dart:148-155 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
  • Duplicated block (8 lines × 2) common/lib/src/app_variants/family/module/stats/json.dart:89 — common/lib/src/app_variants/family/module/stats/json.dart:89-96 | common/lib/src/platform/stats/api.dart:92-99 — before extracting anything, compare `common/lib/src/app_variants/family/module/stats/json.dart` and `common/lib/src/platform/stats/api.dart` as WHOLE FILES: this scan already matched 9 separate duplicated blocks between them, totalling at least 59 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
  • Duplicated block (8 lines × 2) ios/App/Binding/CommonBinding.swift:409 — ios/App/Binding/CommonBinding.swift:409-416 | ios/App/Binding/CommonBinding.swift:420-427 — 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 `ios/App/Binding/CommonBinding.swift:409` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (8 lines × 2) ios/Family/HomeViewModel.swift:106 — ios/Family/HomeViewModel.swift:106-113 | ios/NotFamily/HomeViewModel.swift:113-120 — `ios/Family/HomeViewModel.swift` and `ios/NotFamily/HomeViewModel.swift` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 14 separate duplicated blocks between them, totalling at least 142 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own.
  • Duplicated block (8 lines × 2) ios/Family/HomeViewModel.swift:115 — ios/Family/HomeViewModel.swift:115-122 | ios/NotFamily/HomeViewModel.swift:122-129 — `ios/Family/HomeViewModel.swift` and `ios/NotFamily/HomeViewModel.swift` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 14 separate duplicated blocks between them, totalling at least 142 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own.
  • Duplicated block (8 lines × 2) ios/Family/HomeViewModel.swift:124 — ios/Family/HomeViewModel.swift:124-131 | ios/NotFamily/HomeViewModel.swift:131-138 — `ios/Family/HomeViewModel.swift` and `ios/NotFamily/HomeViewModel.swift` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 14 separate duplicated blocks between them, totalling at least 142 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own.
  • Duplicated block (8 lines × 2) ios/Family/HomeViewModel.swift:133 — ios/Family/HomeViewModel.swift:133-140 | ios/NotFamily/HomeViewModel.swift:140-147 — `ios/Family/HomeViewModel.swift` and `ios/NotFamily/HomeViewModel.swift` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 14 separate duplicated blocks between them, totalling at least 142 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own.
  • Duplicated block (8 lines × 2) ios/Family/HomeViewModel.swift:142 — ios/Family/HomeViewModel.swift:142-149 | ios/NotFamily/HomeViewModel.swift:149-156 — `ios/Family/HomeViewModel.swift` and `ios/NotFamily/HomeViewModel.swift` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 14 separate duplicated blocks between them, totalling at least 142 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own.
  • Duplicated block (8 lines × 2) ios/Family/HomeViewModel.swift:229 — ios/Family/HomeViewModel.swift:229-236 | ios/NotFamily/HomeViewModel.swift:259-266 — `ios/Family/HomeViewModel.swift` and `ios/NotFamily/HomeViewModel.swift` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 14 separate duplicated blocks between them, totalling at least 142 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own.
  • Duplicated block (8 lines × 2) ios/Family/HomeViewModel.swift:252 — ios/Family/HomeViewModel.swift:252-259 | ios/NotFamily/HomeViewModel.swift:278-285 — `ios/Family/HomeViewModel.swift` and `ios/NotFamily/HomeViewModel.swift` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 14 separate duplicated blocks between them, totalling at least 142 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `ios/Family/HomeViewModel.swift:244` calls `switchVpn` and `ios/NotFamily/HomeViewModel.swift:271` 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.
D6 · Cohesion (LCOM4) · Low cohesion · ×12
  • Low cohesion: AdaptyConfiguration (LCOM4 16) common/vendor/adapty_flutter/lib/src/models/adapty_configuration.dart:41 — AdaptyConfiguration's methods fall into 16 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 16 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
  • Low cohesion: _AdaptyUIFlowPlatformViewState (LCOM4 16) common/vendor/adapty_flutter/lib/src/platform_views/adaptyui_flow_platform_view.dart:90 — _AdaptyUIFlowPlatformViewState's methods fall into 16 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 16 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
  • Low cohesion: AdaptyUI (LCOM4 10) common/vendor/adapty_flutter/lib/src/adaptyui.dart:4 — AdaptyUI's methods fall into 10 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 10 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
  • Low cohesion: AdaptyPaymentChannel (LCOM4 9) common/lib/src/features/payment/domain/adapty.dart:10 — AdaptyPaymentChannel's methods fall into 9 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 9 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
  • Low cohesion: _AdaptyUIOnboardingPlatformViewState (LCOM4 9) common/vendor/adapty_flutter/lib/src/platform_views/adaptyui_onboarding_platform_view.dart:49 — _AdaptyUIOnboardingPlatformViewState's methods fall into 9 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 9 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
  • Low cohesion: RuntimeCoreChannel (LCOM4 6) common/lib/src/platform/core/channel.dart:35 — RuntimeCoreChannel's methods fall into 6 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 6 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: MockScaffoldingWidget (LCOM4 5) common/lib/mock/widget/mock_scaffolding.dart:15 — MockScaffoldingWidget'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: LoggerCommand (LCOM4 5) common/lib/src/platform/core/command.dart:3 — LoggerCommand'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: PrivateDnsCheck (LCOM4 5) common/lib/src/platform/perm/dnscheck.dart:16 — PrivateDnsCheck'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: _AdaptyEmbeddedPaywallSheetState (LCOM4 4) common/lib/src/features/payment/domain/paywall_sheet.dart:29 — _AdaptyEmbeddedPaywallSheetState'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.
  • Low cohesion: PrivateDnsSheetAndroidState (LCOM4 4) common/lib/src/features/private_dns/ui/private_dns_sheet_android.dart:38 — PrivateDnsSheetAndroidState'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.
  • Low cohesion: DetailRoutes (LCOM4 4) common/lib/src/shared/layout/detail_route.dart:84 — DetailRoutes'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.
AXH1 · Runtime security headers · Runtime security header not set · ×11
  • Runtime security header not set: content-security-policy — The live app's responses did not include content-security-policy (restricts the sources a page may load — mitigates XSS/injection). Observed by booting the app in-sandbox — advisory evidence for AppSec / CRA / NIS2 runtime secure-defaults. Set it at your reverse proxy or in the app.
  • Runtime security header not set: cross-origin-embedder-policy — The live app's responses did not include cross-origin-embedder-policy (recommended by the OWASP Secure Headers Project (value: require-corp)). Observed by booting the app in-sandbox — advisory evidence for AppSec / CRA / NIS2 runtime secure-defaults. Set it at your reverse proxy or in the app.
  • Runtime security header not set: cross-origin-opener-policy — The live app's responses did not include cross-origin-opener-policy (recommended by the OWASP Secure Headers Project (value: same-origin)). Observed by booting the app in-sandbox — advisory evidence for AppSec / CRA / NIS2 runtime secure-defaults. Set it at your reverse proxy or in the app.
  • Runtime security header not set: cross-origin-resource-policy — The live app's responses did not include cross-origin-resource-policy (recommended by the OWASP Secure Headers Project (value: same-origin)). Observed by booting the app in-sandbox — advisory evidence for AppSec / CRA / NIS2 runtime secure-defaults. Set it at your reverse proxy or in the app.
  • Runtime security header not set: permissions-policy — The live app's responses did not include permissions-policy (restricts powerful browser features (camera, geolocation, …)). Observed by booting the app in-sandbox — advisory evidence for AppSec / CRA / NIS2 runtime secure-defaults. Set it at your reverse proxy or in the app.
  • Runtime security header not set: referrer-policy — The live app's responses did not include referrer-policy (limits referrer leakage to third parties). Observed by booting the app in-sandbox — advisory evidence for AppSec / CRA / NIS2 runtime secure-defaults. Set it at your reverse proxy or in the app.
  • Runtime security header not set: strict-transport-security — The live app's responses did not include strict-transport-security (forces HTTPS on subsequent requests — mitigates downgrade/MITM). Observed by booting the app in-sandbox — advisory evidence for AppSec / CRA / NIS2 runtime secure-defaults. Set it at your reverse proxy or in the app.
  • Runtime security header not set: x-content-type-options — The live app's responses did not include x-content-type-options (stops MIME-sniffing (expects 'nosniff')). Observed by booting the app in-sandbox — advisory evidence for AppSec / CRA / NIS2 runtime secure-defaults. Set it at your reverse proxy or in the app.
  • Runtime security header not set: x-dns-prefetch-control — The live app's responses did not include x-dns-prefetch-control (recommended by the OWASP Secure Headers Project (value: off)). Observed by booting the app in-sandbox — advisory evidence for AppSec / CRA / NIS2 runtime secure-defaults. Set it at your reverse proxy or in the app.
  • Runtime security header not set: x-frame-options — The live app's responses did not include x-frame-options (blocks clickjacking via framing (or use CSP frame-ancestors)). Observed by booting the app in-sandbox — advisory evidence for AppSec / CRA / NIS2 runtime secure-defaults. Set it at your reverse proxy or in the app.
  • Runtime security header not set: x-permitted-cross-domain-policies — The live app's responses did not include x-permitted-cross-domain-policies (recommended by the OWASP Secure Headers Project (value: none)). Observed by booting the app in-sandbox — advisory evidence for AppSec / CRA / NIS2 runtime secure-defaults. Set it at your reverse proxy or in the app.
X3 · Exception handling · Swallowed exception (caught, then discarded) · ×11
  • Swallowed exception (caught, then discarded) ios/App/Util/JsonUtil.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) ios/App/Binding/CoreBinding.swift:294 — `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) common/websocket.py:12 — `except Exception` 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) common/lib/src/platform/stage/stage.dart:42 — `catch (e)` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter.
  • Swallowed exception (caught, then discarded) common/lib/src/features/support/domain/actor.dart:409 — `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) common/lib/src/features/stats/ui/stats_detail_section.dart:43 — `catch (e)` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter.
  • Swallowed exception (caught, then discarded) common/lib/src/features/payment/domain/attribute_converter.dart:83 — `catch (e)` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter.
  • Swallowed exception (caught, then discarded) common/lib/src/features/payment/domain/payment.dart:51 — `catch (e)` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter.
  • Swallowed exception (caught, then discarded) common/lib/src/features/notification/domain/actor.dart:555 — `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) common/lib/src/app_variants/v6/widget/home/stats/privacy_pulse_section.dart:412 — `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) android/app/src/main/java/model/Error.kt:58 — `catch (ex: Throwable)` 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.
D4 · Code Duplication · Edited copy of a member (8 corresponding lines) · ×7
  • Edited copy of a member (8 corresponding lines) common/lib/src/features/notification/domain/actor.dart:63 — common/lib/src/features/notification/domain/actor.dart:63-70 | common/lib/src/features/notification/domain/actor.dart:72-82 — These two members are one piece of code written twice and then edited apart: 8 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (8 corresponding lines) android/app/wireguard-android/ui/src/main/java/com/wireguard/android/configStore/FileConfigStore.kt:24 — android/app/wireguard-android/ui/src/main/java/com/wireguard/android/configStore/FileConfigStore.kt:24-31 | android/app/wireguard-android/ui/src/main/java/com/wireguard/android/configStore/FileConfigStore.kt:70-77 — These two members are one piece of code written twice and then edited apart: 8 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (8 corresponding lines) ios/App/Binding/CommonBinding.swift:344 — ios/App/Binding/CommonBinding.swift:344-355 | ios/NotFamily/PlusBinding.swift:151-158 — These two members are one piece of code written twice and then edited apart: 8 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (8 corresponding lines) common/lib/src/app_variants/family/module/device_v3/api.dart:29 — common/lib/src/app_variants/family/module/device_v3/api.dart:29-36 | common/lib/src/app_variants/family/module/device_v3/api.dart:61-69 — These two members are one piece of code written twice and then edited apart: 8 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (8 corresponding lines) common/lib/src/features/stats/ui/stats_filter.dart:28 — common/lib/src/features/stats/ui/stats_filter.dart:28-35 | common/lib/src/features/stats/ui/stats_filter_device.dart:26-36 — These two members are one piece of code written twice and then edited apart: 8 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (8 corresponding lines) ios/WireguardCopiedFiles/RecentTunnelsTracker.swift:36 — ios/WireguardCopiedFiles/RecentTunnelsTracker.swift:36-43 | ios/WireguardCopiedFiles/RecentTunnelsTracker.swift:45-52 — These two members are one piece of code written twice and then edited apart: 8 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (8 corresponding lines) common/lib/src/platform/core/command.dart:10 — common/lib/src/platform/core/command.dart:10-18 | common/lib/src/platform/filter/command.dart:6-13 — These two members are one piece of code written twice and then edited apart: 8 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Duplicated block (7 lines × 2) · ×7
  • Duplicated block (7 lines × 2) common/lib/src/app_variants/family/module/device_v3/json.dart:85 — common/lib/src/app_variants/family/module/device_v3/json.dart:85-91 | common/lib/src/app_variants/family/module/device_v3/json.dart:224-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 `common/lib/src/app_variants/family/module/device_v3/json.dart:85` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The `return` at the foot of the matched lines is the enclosing body's own terminal exit, not an early one: it moves with them unchanged, and each site calls the extracted unit from the position that `return` occupied — no decision has to be handed back and re-acted on.
  • Duplicated block (7 lines × 2) common/lib/src/features/stats/ui/stats_filter_device.dart:62 — common/lib/src/features/stats/ui/stats_filter_device.dart:62-68 | common/lib/src/features/stats/ui/stats_filter_device.dart:89-95 — 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 `common/lib/src/features/stats/ui/stats_filter_device.dart:62` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (7 lines × 2) common/lib/src/app_variants/family/module/stats/json.dart:24 — common/lib/src/app_variants/family/module/stats/json.dart:24-30 | common/lib/src/platform/stats/api.dart:23-29 — before extracting anything, compare `common/lib/src/app_variants/family/module/stats/json.dart` and `common/lib/src/platform/stats/api.dart` as WHOLE FILES: this scan already matched 9 separate duplicated blocks between them, totalling at least 59 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
  • Duplicated block (7 lines × 2) common/lib/src/app_variants/family/module/stats/json.dart:123 — common/lib/src/app_variants/family/module/stats/json.dart:123-129 | common/lib/src/platform/stats/api.dart:126-132 — before extracting anything, compare `common/lib/src/app_variants/family/module/stats/json.dart` and `common/lib/src/platform/stats/api.dart` as WHOLE FILES: this scan already matched 9 separate duplicated blocks between them, totalling at least 59 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
  • Duplicated block (7 lines × 2) ios/Family/BlokadaView.swift:32 — ios/Family/BlokadaView.swift:32-38 | ios/NotFamily/BlokadaView.swift:42-48 — `ios/Family/BlokadaView.swift` and `ios/NotFamily/BlokadaView.swift` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 1 separate duplicated blocks between them, totalling at least 7 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own.
  • Duplicated block (7 lines × 2) ios/Family/HomeViewModel.swift:261 — ios/Family/HomeViewModel.swift:261-267 | ios/NotFamily/HomeViewModel.swift:287-293 — `ios/Family/HomeViewModel.swift` and `ios/NotFamily/HomeViewModel.swift` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 14 separate duplicated blocks between them, totalling at least 142 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own.
  • Duplicated block (7 lines × 2) ios/Family/SplashView.swift:52 — ios/Family/SplashView.swift:52-58 | ios/NotFamily/SplashView.swift:51-57 — `ios/Family/SplashView.swift` and `ios/NotFamily/SplashView.swift` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 2 separate duplicated blocks between them, totalling at least 22 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own.
D4 · Code Duplication · Duplicated block (6 lines × 2) · ×7
  • Duplicated block (6 lines × 2) common/lib/src/app_variants/family/module/stats/json.dart:66 — common/lib/src/app_variants/family/module/stats/json.dart:66-71 | common/lib/src/platform/stats/api.dart:69-74 — before extracting anything, compare `common/lib/src/app_variants/family/module/stats/json.dart` and `common/lib/src/platform/stats/api.dart` as WHOLE FILES: this scan already matched 9 separate duplicated blocks between them, totalling at least 59 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
  • Duplicated block (6 lines × 2) common/lib/src/app_variants/family/module/stats/json.dart:82 — common/lib/src/app_variants/family/module/stats/json.dart:82-87 | common/lib/src/platform/stats/api.dart:85-90 — before extracting anything, compare `common/lib/src/app_variants/family/module/stats/json.dart` and `common/lib/src/platform/stats/api.dart` as WHOLE FILES: this scan already matched 9 separate duplicated blocks between them, totalling at least 59 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
  • Duplicated block (6 lines × 2) common/lib/src/app_variants/family/module/stats/json.dart:110 — common/lib/src/app_variants/family/module/stats/json.dart:110-115 | common/lib/src/platform/stats/api.dart:113-118 — before extracting anything, compare `common/lib/src/app_variants/family/module/stats/json.dart` and `common/lib/src/platform/stats/api.dart` as WHOLE FILES: this scan already matched 9 separate duplicated blocks between them, totalling at least 59 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
  • Duplicated block (6 lines × 2) ios/WireguardCopiedFiles/WgLoggerForApp.swift:26 — ios/WireguardCopiedFiles/WgLoggerForApp.swift:26-31 | ios/WireguardCopiedFilesExtension/WgLoggerForExtension.swift:20-25 — before extracting anything, compare `ios/WireguardCopiedFiles/WgLoggerForApp.swift` and `ios/WireguardCopiedFilesExtension/WgLoggerForExtension.swift` as WHOLE FILES: 86% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 1 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `ios/WireguardCopiedFiles/WgLoggerForApp.swift:26` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (6 lines × 2) ios/App/ServiceImpl/LoggerSaver.swift:44 — ios/App/ServiceImpl/LoggerSaver.swift:44-49 | ios/WireguardCopiedFilesExtension/NELogger.swift:87-92 — before extracting anything, compare `ios/App/ServiceImpl/LoggerSaver.swift` and `ios/WireguardCopiedFilesExtension/NELogger.swift` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 37 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
  • Duplicated block (6 lines × 2) ios/Family/HomeViewModel.swift:191 — ios/Family/HomeViewModel.swift:191-196 | ios/NotFamily/HomeViewModel.swift:221-226 — `ios/Family/HomeViewModel.swift` and `ios/NotFamily/HomeViewModel.swift` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 14 separate duplicated blocks between them, totalling at least 142 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own.
  • Duplicated block (6 lines × 2) ios/Family/HomeViewModel.swift:198 — ios/Family/HomeViewModel.swift:198-203 | ios/NotFamily/HomeViewModel.swift:228-233 — `ios/Family/HomeViewModel.swift` and `ios/NotFamily/HomeViewModel.swift` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 14 separate duplicated blocks between them, totalling at least 142 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own.
D10 · Test Quality · No assertions · ×6
  • No assertions: opens the full Activity list from Privacy Pulse automation/appium/wdio/src/specs/smoke/activity.spec.ts:95 — This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
  • No assertions: adds a blocked domain then removes it automation/appium/wdio/src/specs/smoke/exceptions-crud.spec.ts:53 — This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
  • No assertions: presents the native paywall when enabling protection automation/appium/wdio/src/specs/smoke/paywall.spec.ts:172 — This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
  • No assertions: switches between the 24h and 7d ranges automation/appium/wdio/src/specs/smoke/privacy-pulse-range.spec.ts:38 — This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
  • No assertions: opens the Exceptions and Retention sub-pages automation/appium/wdio/src/specs/smoke/settings-navigation.spec.ts:33 — This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
  • No assertions: opens each main screen from Home and returns automation/appium/wdio/src/specs/smoke/tab-navigation.spec.ts:30 — This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, 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.
D3 · God Classes · FileTooLong · ×6
  • FileTooLong: lib/ai-explorer-runner.mjs automation/appium/wdio/scripts/lib/ai-explorer-runner.mjs — FileTooLong — 1161 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 661 over it, 2.32× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
  • FileTooLong: ui/domain_detail_section.dart common/lib/src/features/stats/ui/domain_detail_section.dart — FileTooLong — 1082 significant lines (blank, comment-only and punctuation-only lines excluded), about 95% of them inside a single declaration: DomainDetailSectionState (61-1560). The bar is 500 significant lines; this is 582 over it, 2.16× 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: domain/weekly_report.dart common/lib/src/features/notification/domain/weekly_report.dart — FileTooLong — 780 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 280 over it, 1.56× 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: Assets/UiGen.swift ios/App/Assets/UiGen.swift — FileTooLong — 719 significant lines (blank, comment-only and punctuation-only lines excluded), about 98% of them inside a single declaration: L10n (12-1429). The bar is 500 significant lines; this is 219 over it, 1.44× 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: device/rule_editor_sheet.dart common/lib/src/app_variants/family/widget/device/rule_editor_sheet.dart — FileTooLong — 676 significant lines (blank, comment-only and punctuation-only lines excluded), about 94% of them inside a single declaration: _RuleEditorSheetState (70-1094). The bar is 500 significant lines; this is 176 over it, 1.35× the bar. Moving the declarations that sit BESIDE it into sibling files will not shorten this file. Extract from INSIDE that declaration instead: lift each cohesive group of its body — the parts that share the same inputs and are named together — into its own unit in a sibling file, and have the original call them.
  • FileTooLong: stats/stats.dart common/lib/src/platform/stats/stats.dart — FileTooLong — 540 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 40 over it, 1.08× 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.
D4 · Code Duplication · Edited copy of a member (9 corresponding lines) · ×6
  • Edited copy of a member (9 corresponding lines) common/lib/src/features/notification/domain/api.dart:16 — common/lib/src/features/notification/domain/api.dart:16-24 | common/lib/src/platform/device/api.dart:88-97 — 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.
  • Edited copy of a member (9 corresponding lines) common/lib/src/platform/stats/api.dart:59 — common/lib/src/platform/stats/api.dart:59-67 | common/lib/src/platform/stats/api.dart:192-201 — 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.
  • Edited copy of a member (9 corresponding lines) common/lib/src/app_variants/family/module/profile/api.dart:18 — common/lib/src/app_variants/family/module/profile/api.dart:18-26 | common/lib/src/app_variants/family/module/profile/api.dart:35-43 — 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.
  • Edited copy of a member (9 corresponding lines) ios/App/Binding/Vpn/NetxServiceIn.swift:58 — ios/App/Binding/Vpn/NetxServiceIn.swift:58-67 | ios/App/Binding/Vpn/NetxServiceIn.swift:89-97 — 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.
  • Edited copy of a member (9 corresponding lines) common/lib/src/app_variants/family/module/auth/json.dart:16 — common/lib/src/app_variants/family/module/auth/json.dart:16-25 | common/lib/src/app_variants/v6/module/attach/json.dart:19-27 — 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.
  • Edited copy of a member (9 corresponding lines) android/app/src/family/kotlin/ui/MainApplication.kt:53 — android/app/src/family/kotlin/ui/MainApplication.kt:53-61 | android/app/src/six/kotlin/ui/MainApplication.kt:82-91 — These two members are one piece of code written twice and then edited apart: 9 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Duplicated block (11 lines × 2) · ×6
  • Duplicated block (11 lines × 2) common/lib/src/app_variants/family/module/stats/actor.dart:25 — common/lib/src/app_variants/family/module/stats/actor.dart:25-35 | common/lib/src/app_variants/family/module/stats/actor.dart:49-59 — 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 `common/lib/src/app_variants/family/module/stats/actor.dart:25` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (11 lines × 2) common/lib/src/features/stats/ui/domain_detail_section.dart:632 — common/lib/src/features/stats/ui/domain_detail_section.dart:632-642 | common/lib/src/features/stats/ui/domain_detail_section.dart:673-683 — 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `common/lib/src/features/stats/ui/domain_detail_section.dart:684` calls `log`, `pair` and `common/lib/src/features/stats/ui/domain_detail_section.dart:643` 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) common/lib/src/features/stats/ui/domain_detail_section.dart:1405 — common/lib/src/features/stats/ui/domain_detail_section.dart:1405-1415 | common/lib/src/features/stats/ui/recent_activity.dart:198-208 — 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 `common/lib/src/features/stats/ui/domain_detail_section.dart:1405` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (11 lines × 2) common/lib/src/features/stats/ui/recent_activity.dart:233 — common/lib/src/features/stats/ui/recent_activity.dart:233-243 | common/lib/src/features/stats/ui/top_domains.dart:404-414 — before extracting anything, compare `common/lib/src/features/stats/ui/recent_activity.dart` and `common/lib/src/features/stats/ui/top_domains.dart` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 70 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
  • Duplicated block (11 lines × 2) android/app/src/family/kotlin/service/UncaughtExceptionService.kt:30 — android/app/src/family/kotlin/service/UncaughtExceptionService.kt:30-40 | android/app/src/six/kotlin/service/UncaughtExceptionService.kt:30-40 — before extracting anything, compare `android/app/src/family/kotlin/service/UncaughtExceptionService.kt` and `android/app/src/six/kotlin/service/UncaughtExceptionService.kt` as WHOLE FILES: 100% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 1 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
  • Duplicated block (11 lines × 2) ios/Family/HomeViewModel.swift:83 — ios/Family/HomeViewModel.swift:83-93 | ios/NotFamily/HomeViewModel.swift:87-97 — `ios/Family/HomeViewModel.swift` and `ios/NotFamily/HomeViewModel.swift` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 14 separate duplicated blocks between them, totalling at least 142 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own.
D15 · Churn × Complexity Hotspots · Hotspot · ×5
  • Hotspot: common/lib/src/features/stats/ui/top_domains.dart common/lib/src/features/stats/ui/top_domains.dart:76 — common/lib/src/features/stats/ui/top_domains.dart changed 10 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 25 in TopDomainsState.build at line 76. 2 of those changes were fix/bug commits, and the other 8 changed it for other reasons — this file is under both repair and feature pressure. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-08-14..2026-11-12, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-14 06:33:46 +01:00' --until='2026-11-12 06:33:46 +01:00' --full-history --no-merges -- common/lib/src/features/stats/ui/top_domains.dart`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
  • Hotspot: common/lib/src/features/settings/ui/settings_section.dart common/lib/src/features/settings/ui/settings_section.dart:101 — common/lib/src/features/settings/ui/settings_section.dart changed 9 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 17 in SettingsState.build at line 101. 2 of those changes were fix/bug commits, and the other 7 changed it for other reasons — this file is under both repair and feature pressure. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-08-14..2026-11-12, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-14 06:33:46 +01:00' --until='2026-11-12 06:33:46 +01:00' --full-history --no-merges -- common/lib/src/features/settings/ui/settings_section.dart`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
  • Hotspot: common/lib/src/app_variants/v6/widget/filters_section.dart common/lib/src/app_variants/v6/widget/filters_section.dart:52 — common/lib/src/app_variants/v6/widget/filters_section.dart changed 4 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 16 in V6FiltersSectionState.build at line 52. 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-14..2026-11-12, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-14 06:33:46 +01:00' --until='2026-11-12 06:33:46 +01:00' --full-history --no-merges -- common/lib/src/app_variants/v6/widget/filters_section.dart`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
  • Hotspot: common/lib/src/app_variants/v6/widget/home/stats/radial_chart.dart common/lib/src/app_variants/v6/widget/home/stats/radial_chart.dart:75 — common/lib/src/app_variants/v6/widget/home/stats/radial_chart.dart changed 3 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 16 in RadialChart.build at line 75. 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-14..2026-11-12, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-14 06:33:46 +01:00' --until='2026-11-12 06:33:46 +01:00' --full-history --no-merges -- common/lib/src/app_variants/v6/widget/home/stats/radial_chart.dart`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
  • Hotspot: android/app/src/main/java/service/NotificationService.kt android/app/src/main/java/service/NotificationService.kt:207 — android/app/src/main/java/service/NotificationService.kt changed 2 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 16 in NotificationAlarmReceiver.onReceive at line 207. 1 of those changes was a fix/bug commit, and the other 1 changed it for other reasons — this file is under both repair and feature pressure. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-08-14..2026-11-12, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-14 06:33:46 +01:00' --until='2026-11-12 06:33:46 +01:00' --full-history --no-merges -- android/app/src/main/java/service/NotificationService.kt`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
D4 · Code Duplication · Edited copy of a member (14 corresponding lines) · ×5
  • Edited copy of a member (14 corresponding lines) common/lib/src/core/persistence/value.dart:40 — common/lib/src/core/persistence/value.dart:40-54 | common/lib/src/core/persistence/value.dart:65-78 — 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.
  • Edited copy of a member (14 corresponding lines) common/lib/src/features/plus/domain/gateway/actor.dart:65 — common/lib/src/features/plus/domain/gateway/actor.dart:65-78 | common/lib/src/features/plus/domain/lease/actor.dart:117-135 — 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.
  • Edited copy of a member (14 corresponding lines) common/lib/src/platform/app/start/start.dart:166 — common/lib/src/platform/app/start/start.dart:166-179 | common/lib/src/platform/app/start/start.dart:181-195 — 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.
  • Edited copy of a member (14 corresponding lines) common/lib/src/features/payment/domain/adapty.dart:325 — common/lib/src/features/payment/domain/adapty.dart:325-338 | common/lib/src/platform/payment/channel.dart:31-44 — 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.
  • Edited copy of a member (14 corresponding lines) common/lib/src/platform/plus/channel.dart:44 — common/lib/src/platform/plus/channel.dart:44-57 | common/lib/src/platform/plus/channel.dart:59-73 — These two members are one piece of code written twice and then edited apart: 14 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copy of a member (3 corresponding lines) · ×5
  • Edited copy of a member (3 corresponding lines) ios/App/Assets/UiGen.swift:387 — ios/App/Assets/UiGen.swift:387-389 | ios/App/Assets/UiGen.swift:423-425 — These two members are one piece of code written twice and then edited apart: 3 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (3 corresponding lines) ios/App/Util/BlockaLogger.swift:55 — ios/App/Util/BlockaLogger.swift:55-57 | ios/WireguardCopiedFilesExtension/NELogger.swift:38-40 — These two members are one piece of code written twice and then edited apart: 3 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (3 corresponding lines) ios/App/Binding/CommonBinding.swift:234 — ios/App/Binding/CommonBinding.swift:234-236 | ios/WireguardCopiedFilesExtension/Env.swift:19-23 — These two members are one piece of code written twice and then edited apart: 3 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (3 corresponding lines) ios/App/Binding/UrlBinding.swift:37 — ios/App/Binding/UrlBinding.swift:37-40 | ios/NotFamily/PlusBinding.swift:210-212 — These two members are one piece of code written twice and then edited apart: 3 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (3 corresponding lines) common/lib/src/app_variants/family/module/schedule/json.dart:144 — common/lib/src/app_variants/family/module/schedule/json.dart:144-147 | common/lib/src/features/support/domain/model.dart:135-137 — 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 · Edited copy of a member (4 corresponding lines) · ×5
  • Edited copy of a member (4 corresponding lines) ios/WireguardCopiedFiles/WgLoggerForApp.swift:34 — ios/WireguardCopiedFiles/WgLoggerForApp.swift:34-37 | ios/WireguardCopiedFilesExtension/WgLoggerForExtension.swift:28-31 — These two members are one piece of code written twice and then edited apart: 4 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (4 corresponding lines) ios/WireguardCopiedFiles/WgLoggerForApp.swift:39 — ios/WireguardCopiedFiles/WgLoggerForApp.swift:39-42 | ios/WireguardCopiedFilesExtension/WgLoggerForExtension.swift:33-36 — These two members are one piece of code written twice and then edited apart: 4 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (4 corresponding lines) common/lib/src/app_variants/family/module/stats/json.dart:105 — common/lib/src/app_variants/family/module/stats/json.dart:105-108 | common/lib/src/platform/stats/api.dart:108-111 — These two members are one piece of code written twice and then edited apart: 4 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (4 corresponding lines) ios/App/Binding/CommonBinding.swift:211 — ios/App/Binding/CommonBinding.swift:211-214 | ios/NotFamily/PlusBinding.swift:137-140 — These two members are one piece of code written twice and then edited apart: 4 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (4 corresponding lines) common/lib/src/app_variants/v6/widget/filters_section.dart:180 — common/lib/src/app_variants/v6/widget/filters_section.dart:180-183 | common/lib/src/features/filter/ui/filter.dart:154-157 — 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.
D3 · God Classes · TooManyMethods · ×4
  • TooManyMethods: PaymentBinding android/app/src/six/kotlin/binding/PaymentBinding.kt:58 — 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.
  • TooManyMethods: NotificationActor common/lib/src/features/notification/domain/actor.dart:3 — TooManyMethods — 34 methods. The bar is 30 methods; this is 4 over it, 1.13× 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: AdaptyPaymentChannel common/lib/src/features/payment/domain/adapty.dart:10 — TooManyMethods — 34 methods. The bar is 30 methods; this is 4 over it, 1.13× 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: DomainDetailSectionState common/lib/src/features/stats/ui/domain_detail_section.dart:61 — TooManyMethods — 32 methods. The bar is 30 methods; this is 2 over it, 1.07× 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.
D35 · Change Coupling · Change coupling · ×4
  • Change coupling: privacy_pulse_section.dart ↔ horizontal_radial_segment.dart common/lib/src/app_variants/v6/widget/home/stats/privacy_pulse_section.dart:1 — `common/lib/src/app_variants/v6/widget/home/stats/privacy_pulse_section.dart` and `common/lib/src/features/stats/ui/horizontal_radial_segment.dart` change together 58% of the time (7 of the 12 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) with no explicit dependency — the edge is real but nothing declares it. Read the pair before acting: if one registers itself into the other through a hook or an initialiser, the missing dependency is DELIBERATE — the registration is the link, and it is meant not to be an import — and the thing to add is a comment on each side naming the other, not a merge; if they simply belong together, co-locate them; if neither holds, the coupling is hidden and worth breaking. You can check this without leaving the row: of the 7 shared commits counted here, the most recent 3 are `8c4a9eca` common: align weekly report with privacy shield; `872640a8` pulse: activity ring improvements (at that commit the files were still `common/lib/v6/widget/home/stats/privacy_pulse_section.dart` and `common/lib/common/widget/stats/horizontal_radial_segment.dart`); `10e97815` pulse: update sparkline to support 7d range (at that commit the files were still `common/lib/v6/widget/home/stats/privacy_pulse_section.dart` and `common/lib/common/widget/stats/horizontal_radial_segment.dart`) — run `git show` on any of them.
  • Change coupling: recent_activity.dart ↔ top_domains.dart common/lib/src/features/stats/ui/recent_activity.dart:1 — `common/lib/src/features/stats/ui/recent_activity.dart` and `common/lib/src/features/stats/ui/top_domains.dart` change together 54% of the time (7 of the 13 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) with no explicit dependency between them. They sit in the same directory, but in this ecosystem each file is its own module — a sibling reference still needs an import — so the missing import edge is real: the coupling runs through shared behaviour, not a declared dependency. If they duplicate structure, extract the common part into one unit; otherwise the coupling is hidden and worth breaking. You can check this without leaving the row: of the 7 shared commits counted here, the most recent 3 are `88b99cd6` fix(a11y): follow the system text size instead of clamping it (#1410); `babc3f3e` feat(stats): smooth content changes in pulse and activity (#1385); `c4118677` feat(stats): loading placeholders instead of spinners (#1384) — run `git show` on any of them.
  • Change coupling: activity_screen.dart ↔ domain_detail_section.dart common/lib/src/app_variants/v6/widget/activity_screen.dart:1 — `common/lib/src/app_variants/v6/widget/activity_screen.dart` and `common/lib/src/features/stats/ui/domain_detail_section.dart` change together 54% of the time (7 of the 13 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 7 shared commits counted here, the most recent 3 are `0039416a` exceptions: tune domain details view to not show irrelevant sections; `83cce99f` pulse: fix toplist detail view flickering (at that commit the files were still `common/lib/v6/widget/activity_screen.dart` and `common/lib/common/widget/stats/domain_detail_section.dart`); `06dfbc5a` activity: add detail view at the end of toplist breakdown domain navi… (at that commit the files were still `common/lib/v6/widget/activity_screen.dart` and `common/lib/common/widget/stats/domain_detail_section.dart`) — run `git show` on any of them.
  • Change coupling: top_domains.dart ↔ api.dart common/lib/src/features/stats/ui/top_domains.dart:1 — `common/lib/src/features/stats/ui/top_domains.dart` and `common/lib/src/platform/stats/api.dart` 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 `b46677c2` fix(stats): key toplist rows on the domain, not the company (#1446); `fe690537` v6: weekly: create the basic weekly report flow end-to-end (at that commit the files were still `common/lib/common/widget/stats/top_domains.dart` and `common/lib/platform/stats/api.dart`); `695acae3` android: activity: implement the new toplist api (at that commit the files were still `common/lib/common/widget/stats/top_domains.dart` and `common/lib/platform/stats/api.dart`) — run `git show` on any of them.
D4 · Code Duplication · Edited copy of a member (15 corresponding lines) · ×4
  • Edited copy of a member (15 corresponding lines) common/lib/src/app_variants/family/module/device_v3/json.dart:77 — common/lib/src/app_variants/family/module/device_v3/json.dart:77-91 | common/lib/src/app_variants/family/module/device_v3/json.dart:216-230 — 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) common/lib/src/platform/stats/stats.dart:82 — common/lib/src/platform/stats/stats.dart:82-96 | common/lib/src/platform/stats/stats.dart:98-112 — 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) common/lib/src/core/value.dart:97 — common/lib/src/core/value.dart:97-111 | common/lib/src/core/value.dart:207-221 — 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) common/lib/src/features/customlist/domain/actor.dart:89 — common/lib/src/features/customlist/domain/actor.dart:89-103 | common/lib/src/features/customlist/domain/actor.dart:105-120 — These two members are one piece of code written twice and then edited apart: 15 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copy of a member (6 corresponding lines) · ×4
  • Edited copy of a member (6 corresponding lines) common/lib/src/core/persistence/persistence.dart:56 — common/lib/src/core/persistence/persistence.dart:56-61 | common/lib/src/core/persistence/persistence.dart:63-69 — 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) common/lib/src/platform/filter/actor.dart:53 — common/lib/src/platform/filter/actor.dart:53-66 | common/lib/src/platform/perm/actor.dart:167-172 — 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) common/lib/src/app_variants/family/module/stats/json.dart:38 — common/lib/src/app_variants/family/module/stats/json.dart:38-43 | common/lib/src/platform/stats/api.dart:37-44 — 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) common/lib/src/features/onboard/ui/onboard_screen.dart:32 — common/lib/src/features/onboard/ui/onboard_screen.dart:32-37 | common/lib/src/features/rate/domain/actor.dart:164-169 — 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 · Duplicated block (19 lines × 2) · ×4
  • Duplicated block (19 lines × 2) common/lib/src/features/private_dns/ui/private_dns_setting_guide.dart:28 — common/lib/src/features/private_dns/ui/private_dns_setting_guide.dart:28-46 | common/lib/src/features/safari/ui/safari_setting_guide.dart:26-44 — before extracting anything, compare `common/lib/src/features/private_dns/ui/private_dns_setting_guide.dart` and `common/lib/src/features/safari/ui/safari_setting_guide.dart` as WHOLE FILES: 84% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 1 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `common/lib/src/features/private_dns/ui/private_dns_setting_guide.dart:28` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
  • Duplicated block (19 lines × 2) android/app/src/family/kotlin/service/BlocklistService.kt:25 — android/app/src/family/kotlin/service/BlocklistService.kt:25-43 | android/app/src/six/kotlin/service/BlocklistService.kt:25-43 — before extracting anything, compare `android/app/src/family/kotlin/service/BlocklistService.kt` and `android/app/src/six/kotlin/service/BlocklistService.kt` as WHOLE FILES: 100% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 1 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
  • Duplicated block (19 lines × 2) ios/App/ServiceImpl/LoggerSaver.swift:24 — ios/App/ServiceImpl/LoggerSaver.swift:24-42 | ios/WireguardCopiedFilesExtension/NELogger.swift:67-85 — before extracting anything, compare `ios/App/ServiceImpl/LoggerSaver.swift` and `ios/WireguardCopiedFilesExtension/NELogger.swift` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 37 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
  • Duplicated block (19 lines × 2) ios/Family/HomeViewModel.swift:205 — ios/Family/HomeViewModel.swift:205-223 | ios/NotFamily/HomeViewModel.swift:235-253 — `ios/Family/HomeViewModel.swift` and `ios/NotFamily/HomeViewModel.swift` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 14 separate duplicated blocks between them, totalling at least 142 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own.
D4 · Code Duplication · Duplicated block (14 lines × 2) · ×4
  • Duplicated block (14 lines × 2) common/lib/src/features/notification/domain/weekly_report.dart:784 — common/lib/src/features/notification/domain/weekly_report.dart:784-797 | common/lib/src/features/notification/domain/weekly_report.dart:799-812 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
  • Duplicated block (14 lines × 2) common/lib/src/features/stats/ui/domain_detail_section.dart:997 — common/lib/src/features/stats/ui/domain_detail_section.dart:997-1010 | common/lib/src/features/stats/ui/domain_detail_section.dart:1012-1025 — 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 `common/lib/src/features/stats/ui/domain_detail_section.dart:997` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (14 lines × 2) common/lib/src/platform/filter/actor.dart:85 — common/lib/src/platform/filter/actor.dart:85-98 | common/lib/src/platform/filter/actor.dart:106-119 — 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 `common/lib/src/platform/filter/actor.dart:85` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (14 lines × 2) common/lib/src/app_variants/v6/widget/activity_screen.dart:39 — common/lib/src/app_variants/v6/widget/activity_screen.dart:39-52 | common/lib/src/app_variants/v6/widget/privacy_pulse_screen.dart:46-59 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
D4 · Code Duplication · Duplicated block (13 lines × 2) · ×4
  • Duplicated block (13 lines × 2) common/lib/src/features/plus/ui/vpn_bypass_item_swipe.dart:47 — common/lib/src/features/plus/ui/vpn_bypass_item_swipe.dart:47-59 | common/lib/src/features/plus/ui/vpn_devices_list.dart:127-139 — 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 `common/lib/src/features/plus/ui/vpn_bypass_item_swipe.dart:47` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (13 lines × 2) common/lib/src/features/stats/ui/stats_detail_section.dart:132 — common/lib/src/features/stats/ui/stats_detail_section.dart:132-144 | common/lib/src/features/stats/ui/stats_detail_section.dart:166-178 — 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 `common/lib/src/features/stats/ui/stats_detail_section.dart:132` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (13 lines × 2) android/app/src/family/kotlin/service/Flavor.kt:21 — android/app/src/family/kotlin/service/Flavor.kt:21-33 | android/app/src/six/kotlin/service/Flavor.kt:21-33 — before extracting anything, compare `android/app/src/family/kotlin/service/Flavor.kt` and `android/app/src/six/kotlin/service/Flavor.kt` as WHOLE FILES: 89% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 1 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
  • Duplicated block (13 lines × 2) ios/App/UI/Main/AccountChangeView.swift:33 — ios/App/UI/Main/AccountChangeView.swift:33-45 | ios/App/UI/Main/ScanQrCodeView.swift:24-36 — 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 `ios/App/UI/Main/AccountChangeView.swift:33` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (5 lines × 2) · ×4
  • Duplicated block (5 lines × 2) common/lib/src/app_variants/family/module/stats/json.dart:45 — common/lib/src/app_variants/family/module/stats/json.dart:45-49 | common/lib/src/platform/stats/api.dart:46-50 — before extracting anything, compare `common/lib/src/app_variants/family/module/stats/json.dart` and `common/lib/src/platform/stats/api.dart` as WHOLE FILES: this scan already matched 9 separate duplicated blocks between them, totalling at least 59 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
  • Duplicated block (5 lines × 2) common/lib/src/app_variants/family/module/stats/json.dart:131 — common/lib/src/app_variants/family/module/stats/json.dart:131-135 | common/lib/src/platform/stats/api.dart:134-138 — before extracting anything, compare `common/lib/src/app_variants/family/module/stats/json.dart` and `common/lib/src/platform/stats/api.dart` as WHOLE FILES: this scan already matched 9 separate duplicated blocks between them, totalling at least 59 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
  • Duplicated block (5 lines × 2) common/lib/src/features/notification/domain/weekly_report.dart:866 — common/lib/src/features/notification/domain/weekly_report.dart:866-870 | common/lib/src/features/notification/domain/weekly_report.dart:895-899 — 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 `common/lib/src/features/notification/domain/weekly_report.dart:866` 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) android/app/src/main/java/binding/CoreBinding.kt:234 — android/app/src/main/java/binding/CoreBinding.kt:234-238 | android/app/src/main/java/service/StorageService.kt:77-81 — 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.
PF3 · Async & latency hygiene · Sync-over-async blocking · ×4
  • Sync-over-async blocking automation/appium/wdio/src/support/artifacts.ts:48 — `writeFileSync` in `savePageSource` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs.
  • Sync-over-async blocking automation/appium/wdio/src/support/artifacts.ts:71 — `writeFileSync` in `saveSyslog` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs.
  • Sync-over-async blocking automation/appium/wdio/src/support/golden.ts:105 — `existsSync` in `compareToGolden` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs.
  • Sync-over-async blocking automation/appium/wdio/src/support/golden.ts:115 — `readFileSync` in `compareToGolden` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs.
D15 · Churn × Complexity Hotspots · Repeated repair · ×3
  • Repeated repair: common/lib/src/shared/ui/top_bar.dart common/lib/src/shared/ui/top_bar.dart:67 — common/lib/src/shared/ui/top_bar.dart changed 8 times in last 90 days and 5 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 8 (its worst body is TopBarState._buildBar at line 67), 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(ui): the Android back button is the arrow alone (#1452)”; “fix(ios): keep the top bar bubbles off the bar's bottom edge (#1424)”; “fix(a11y): follow the system text size instead of clamping it (#1410)”; “fix(ui): drop the link underline from bar actions (#1364)”. 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-14..2026-11-12, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-14 06:33:46 +01:00' --until='2026-11-12 06:33:46 +01:00' --full-history --no-merges -- common/lib/src/shared/ui/top_bar.dart`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
  • Repeated repair: common/lib/src/features/payment/domain/adapty.dart common/lib/src/features/payment/domain/adapty.dart:168 — common/lib/src/features/payment/domain/adapty.dart 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 8 (its worst body is AdaptyPaymentChannel._ensureEmbeddedSheetMounted at line 168), 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(payment/ios): cap paywall width on wide windows again (#1321)”; “fix(payment): explain a restore that finds no active purchase (#1283)”; “fix(payment): only run checkout when the Adapty profile has active access (#1258)”. 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-14..2026-11-12, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-14 06:33:46 +01:00' --until='2026-11-12 06:33:46 +01:00' --full-history --no-merges -- common/lib/src/features/payment/domain/adapty.dart`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
  • Repeated repair: android/app/src/six/kotlin/binding/PaymentBinding.kt android/app/src/six/kotlin/binding/PaymentBinding.kt:131 — android/app/src/six/kotlin/binding/PaymentBinding.kt changed 4 times in last 90 days and 3 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 10 (its worst body is PaymentBinding.doSetCustomAttributes at line 131), 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(android): report tablet paywall dismissals to flutter (#1292)”; “fix(android): close the paywall and show a failure modal on flow errors (#1290)”; “fix(payment): only run checkout when the Adapty profile has active access (#1258)”. 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-14..2026-11-12, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-14 06:33:46 +01:00' --until='2026-11-12 06:33:46 +01:00' --full-history --no-merges -- android/app/src/six/kotlin/binding/PaymentBinding.kt`: 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.
D17 · Explicit Debt · XxxComment · ×3
  • XxxComment ios/App/Service/PrivateDnsService.swift:181 — // XXX: An ugly way to check for this error.. — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
  • XxxComment ios/App/Service/PrivateDnsService.swift:186 — // XXX: Even uglier error I don't understand that seems safe to ignore — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
  • XxxComment ios/App/Service/PrivateDnsService.swift:203 — // XXX: This might be an overkill. — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
D3 · God Classes · ClassTooLong · ×3
  • ClassTooLong: DomainDetailSectionState common/lib/src/features/stats/ui/domain_detail_section.dart:61 — ClassTooLong — 1031 significant lines (blank, comment-only and punctuation-only lines excluded), 32 methods. The bar is 400 significant lines; this is 631 over it, 2.58× 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: L10n ios/App/Assets/UiGen.swift:12 — ClassTooLong — 707 significant lines (blank, comment-only and punctuation-only lines excluded), 70 methods. The bar is 400 significant lines; this is 307 over it, 1.77× 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: _RuleEditorSheetState common/lib/src/app_variants/family/widget/device/rule_editor_sheet.dart:70 — ClassTooLong — 636 significant lines (blank, comment-only and punctuation-only lines excluded), 27 methods. The bar is 400 significant lines; this is 236 over it, 1.59× 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 (19 corresponding lines) · ×3
  • Edited copy of a member (19 corresponding lines) android/app/src/family/kotlin/binding/FamilyBinding.kt:34 — android/app/src/family/kotlin/binding/FamilyBinding.kt:34-52 | android/app/src/main/java/binding/CommonBinding.kt:171-189 — These two members are one piece of code written twice and then edited apart: 19 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (19 corresponding lines) common/lib/src/core/value.dart:131 — common/lib/src/core/value.dart:131-156 | common/lib/src/core/value.dart:241-259 — These two members are one piece of code written twice and then edited apart: 19 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (19 corresponding lines) ios/App/UI/Main/AccountChangeView.swift:33 — ios/App/UI/Main/AccountChangeView.swift:33-51 | ios/App/UI/Main/ScanQrCodeView.swift:24-42 — 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 (11 corresponding lines) · ×3
  • Edited copy of a member (11 corresponding lines) common/lib/src/core/value.dart:66 — common/lib/src/core/value.dart:66-76 | common/lib/src/core/value.dart:174-184 — These two members are one piece of code written twice and then edited apart: 11 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (11 corresponding lines) ios/App/Service/SceneDelegate.swift:183 — ios/App/Service/SceneDelegate.swift:183-193 | ios/App/Service/SceneDelegate.swift:195-209 — These two members are one piece of code written twice and then edited apart: 11 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (11 corresponding lines) common/lib/src/platform/app/app.dart:171 — common/lib/src/platform/app/app.dart:171-181 | common/lib/src/platform/app/app.dart:183-193 — These two members are one piece of code written twice and then edited apart: 11 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copies of one member (3 members, 8+ corresponding lines) · ×3
  • Edited copies of one member (3 members, 8+ corresponding lines) common/lib/src/platform/account/account.dart:155 — common/lib/src/platform/account/account.dart:155-162 | common/lib/src/platform/account/account.dart:164-174 | common/lib/src/platform/account/account.dart:205-212 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 8 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 8+ corresponding lines) ios/App/Binding/Perm/PermBinding.swift:50 — ios/App/Binding/Perm/PermBinding.swift:50-57 | ios/App/Binding/Perm/PermBinding.swift:59-66 | ios/App/Binding/Perm/PermBinding.swift:130-142 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 8 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 8+ corresponding lines) ios/App/Binding/CommandsBinding.swift:85 — ios/App/Binding/CommandsBinding.swift:85-92 | ios/App/Binding/CommandsBinding.swift:118-125 | ios/App/Binding/CommandsBinding.swift:127-134 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 8 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication · Edited copy of a member (7 corresponding lines) · ×3
  • Edited copy of a member (7 corresponding lines) common/lib/src/features/journal/domain/actor.dart:245 — common/lib/src/features/journal/domain/actor.dart:245-253 | common/lib/src/features/stats/ui/domain_detail_section.dart:100-106 — 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) common/lib/src/app_variants/family/module/auth/json.dart:27 — common/lib/src/app_variants/family/module/auth/json.dart:27-34 | common/lib/src/app_variants/v6/module/attach/json.dart:29-35 — 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) common/lib/src/shared/layout/detail_route.dart:170 — common/lib/src/shared/layout/detail_route.dart:170-176 | common/lib/src/shared/ui/top_bar.dart:350-356 — These two members are one piece of code written twice and then edited apart: 7 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Duplicated block (17–18 lines × 3) · ×3
  • Duplicated block (17–18 lines × 3) common/lib/src/app_variants/v6/widget/freemium/weekly_refresh_sheet.dart:69 — common/lib/src/app_variants/v6/widget/freemium/weekly_refresh_sheet.dart:69-86 | common/lib/src/features/safari/ui/safari_onboard_sheet.dart:34-50 | common/lib/src/features/safari/ui/safari_onboard_yt_sheet.dart:32-48 — before extracting anything, compare `common/lib/src/features/safari/ui/safari_onboard_sheet.dart` and `common/lib/src/features/safari/ui/safari_onboard_yt_sheet.dart` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 151 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `common/lib/src/app_variants/v6/widget/freemium/weekly_refresh_sheet.dart:69` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (17–18 lines × 3) common/lib/src/features/settings/ui/exceptions_section.dart:108 — common/lib/src/features/settings/ui/exceptions_section.dart:108-125 | common/lib/src/features/stats/ui/recent_activity.dart:108-124 | common/lib/src/features/stats/ui/top_domains.dart:168-184 — before extracting anything, compare `common/lib/src/features/stats/ui/recent_activity.dart` and `common/lib/src/features/stats/ui/top_domains.dart` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 70 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `common/lib/src/features/settings/ui/exceptions_section.dart:108` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (17–18 lines × 3) common/lib/src/features/settings/ui/exceptions_section.dart:133 — common/lib/src/features/settings/ui/exceptions_section.dart:133-150 | common/lib/src/features/stats/ui/recent_activity.dart:126-142 | common/lib/src/features/stats/ui/top_domains.dart:186-202 — before extracting anything, compare `common/lib/src/features/stats/ui/recent_activity.dart` and `common/lib/src/features/stats/ui/top_domains.dart` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 70 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `common/lib/src/features/settings/ui/exceptions_section.dart:133` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (16 lines × 2) · ×3
  • Duplicated block (16 lines × 2) common/lib/src/core/value.dart:113 — common/lib/src/core/value.dart:113-128 | common/lib/src/core/value.dart:223-238 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
  • Duplicated block (16 lines × 2) ios/Family/ContentView.swift:30 — ios/Family/ContentView.swift:30-45 | ios/NotFamily/ContentView.swift:30-45 — `ios/Family/ContentView.swift` and `ios/NotFamily/ContentView.swift` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 2 separate duplicated blocks between them, totalling at least 60 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own. Read the line range as the matched WINDOW rather than a finished unit: at `ios/Family/ContentView.swift:30` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `ios/NotFamily/ContentView.swift:47` calls `LocationListView` and `ios/Family/ContentView.swift:47` 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 (16 lines × 2) ios/Family/Flavor.swift:20 — ios/Family/Flavor.swift:20-35 | ios/NotFamily/Flavor.swift:20-35 — `ios/Family/Flavor.swift` and `ios/NotFamily/Flavor.swift` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 1 separate duplicated blocks between them, totalling at least 16 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own.
D4 · Code Duplication · Duplicated block (15 lines × 2) · ×3
  • Duplicated block (15 lines × 2) common/lib/src/features/plus/ui/vpn_devices_section.dart:24 — common/lib/src/features/plus/ui/vpn_devices_section.dart:24-38 | common/lib/src/features/settings/ui/retention_section.dart:53-67 — 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 `common/lib/src/features/plus/ui/vpn_devices_section.dart:24` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (15 lines × 2) ios/Family/HomeViewModel.swift:175 — ios/Family/HomeViewModel.swift:175-189 | ios/NotFamily/HomeViewModel.swift:205-219 — `ios/Family/HomeViewModel.swift` and `ios/NotFamily/HomeViewModel.swift` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 14 separate duplicated blocks between them, totalling at least 142 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
  • Duplicated block (15 lines × 2) ios/Family/SplashView.swift:34 — ios/Family/SplashView.swift:34-48 | ios/NotFamily/SplashView.swift:33-47 — `ios/Family/SplashView.swift` and `ios/NotFamily/SplashView.swift` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 2 separate duplicated blocks between them, totalling at least 22 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own. Read the line range as the matched WINDOW rather than a finished unit: at `ios/Family/SplashView.swift:34` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (10 lines × 2) · ×3
  • Duplicated block (10 lines × 2) common/lib/src/features/stats/ui/domain_detail_section.dart:263 — common/lib/src/features/stats/ui/domain_detail_section.dart:263-272 | common/lib/src/features/stats/ui/domain_detail_section.dart:316-325 — 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 `common/lib/src/features/stats/ui/domain_detail_section.dart:263` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
  • Duplicated block (10 lines × 2) common/lib/src/app_variants/v6/widget/home/stats/radial_chart.dart:164 — common/lib/src/app_variants/v6/widget/home/stats/radial_chart.dart:164-173 | common/lib/src/app_variants/v6/widget/home/stats/radial_chart.dart:181-190 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
  • Duplicated block (10 lines × 2) ios/App/Util/BlockaLogger.swift:59 — ios/App/Util/BlockaLogger.swift:59-68 | ios/WireguardCopiedFilesExtension/NELogger.swift:42-51 — 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.
D4 · Code Duplication · Duplicated block (9 lines × 2) · ×3
  • Duplicated block (9 lines × 2) common/lib/src/app_variants/family/module/stats/json.dart:14 — common/lib/src/app_variants/family/module/stats/json.dart:14-22 | common/lib/src/platform/stats/api.dart:13-21 — before extracting anything, compare `common/lib/src/app_variants/family/module/stats/json.dart` and `common/lib/src/platform/stats/api.dart` as WHOLE FILES: this scan already matched 9 separate duplicated blocks between them, totalling at least 59 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
  • Duplicated block (9 lines × 2) common/lib/src/app_variants/family/module/family/family.dart:47 — common/lib/src/app_variants/family/module/family/family.dart:47-55 | common/lib/src/app_variants/v6/module/attach/actor.dart:20-28 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
  • Duplicated block (9 lines × 2) scripts/play-rollout.rb:40 — scripts/play-rollout.rb:40-48 | scripts/verify-play-version-code.rb:36-44 — 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.
R10 · Code Duplication · Duplicated block (13 lines × 2 locations) · ×3
  • Duplicated block (13 lines × 2 locations) automation/appium/wdio/scripts/lib/ai-explorer-config.mjs:24 — automation/appium/wdio/scripts/lib/ai-explorer-config.mjs:24 · REDACTED:17 — the 2 copies sit in sibling files in one directory, so check first whether one of them (or an existing module there) already owns this behaviour and the others should call it; otherwise extract it into one module in that directory and have each site call it.
  • Duplicated block (13 lines × 2 locations) REDACTED:148 — REDACTED:148 · REDACTED:162 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
  • Duplicated block (13 lines × 2 locations) automation/appium/wdio/src/flows/home.ts:57 — automation/appium/wdio/src/flows/home.ts:57 · automation/appium/wdio/src/flows/home.ts:71 — 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.
D17 · Explicit Debt · HackComment · ×2
  • HackComment common/lib/modules.dart:247 — // Hack to be refactored — a workaround marked in source: record what it is compensating for and what would allow its removal (the upstream fix, the API it is waiting on, the invariant it restores), so the next reader can judge whether it is still needed rather than rediscovering why it is there.
  • HackComment common/lib/modules.dart:256 — // Hack to be refactored — a workaround marked in source: record what it is compensating for and what would allow its removal (the upstream fix, the API it is waiting on, the invariant it restores), so the next reader can judge whether it is still needed rather than rediscovering why it is there.
D29 · Static Analysis (SAST) · REDACTED
  • REDACTED
  • REDACTED
D3 · God Classes · FunctionTooLong · ×2
  • FunctionTooLong: ai-explorer-runner.runAiExplorer automation/appium/wdio/scripts/lib/ai-explorer-runner.mjs:1258 — FunctionTooLong — runAiExplorer runs 376 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 276 over it, 3.76× 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: explorer-commands.runExplorerCommand automation/appium/wdio/scripts/lib/explorer-commands.mjs:417 — FunctionTooLong — runExplorerCommand runs 202 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 102 over it, 2.02× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
D30 · Dependency Vulnerabilities · Medium CVE · ×2
  • REDACTED
  • REDACTED
D4 · Code Duplication · Edited copy of a member (32 corresponding lines) · ×2
  • Edited copy of a member (32 corresponding lines) ios/Family/SplashView.swift:16 — ios/Family/SplashView.swift:16-48 | ios/NotFamily/SplashView.swift:16-47 — These two members are one piece of code written twice and then edited apart: 32 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (32 corresponding lines) common/lib/src/app_variants/family/widget/main_screen.dart:26 — common/lib/src/app_variants/family/widget/main_screen.dart:26-59 | common/lib/src/app_variants/v6/widget/main_screen.dart:25-56 — These two members are one piece of code written twice and then edited apart: 32 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copy of a member (24 corresponding lines) · ×2
  • Edited copy of a member (24 corresponding lines) common/lib/src/features/journal/domain/api.dart:85 — common/lib/src/features/journal/domain/api.dart:85-109 | common/lib/src/features/journal/domain/api.dart:111-134 — 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.
  • Edited copy of a member (24 corresponding lines) common/lib/src/features/stats/ui/stats_filter_device.dart:45 — common/lib/src/features/stats/ui/stats_filter_device.dart:45-73 | common/lib/src/features/stats/ui/stats_filter_device.dart:75-98 — 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 copies of one member (3 members, 23+ corresponding lines) · ×2
  • Edited copies of one member (3 members, 23+ corresponding lines) common/lib/src/app_variants/family/widget/home/home_devices.dart:149 — common/lib/src/app_variants/family/widget/home/home_devices.dart:149-171 | common/lib/src/features/plus/ui/vpn_bypass_item_swipe.dart:36-59 | common/lib/src/features/plus/ui/vpn_devices_list.dart:116-139 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 23 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 23+ corresponding lines) common/lib/mock/widget/background.dart:17 — common/lib/mock/widget/background.dart:17-39 | common/lib/src/features/onboard/ui/background.dart:19-50 | common/lib/src/features/onboard/ui/background.dart:57-87 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 23 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 (18 corresponding lines) · ×2
  • Edited copy of a member (18 corresponding lines) common/lib/src/features/notification/domain/actor.dart:419 — common/lib/src/features/notification/domain/actor.dart:419-437 | common/lib/src/features/notification/domain/actor.dart:439-456 — 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.
  • Edited copy of a member (18 corresponding lines) common/lib/src/features/support/domain/json.dart:19 — common/lib/src/features/support/domain/json.dart:19-37 | common/lib/src/features/support/domain/json.dart:109-126 — 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 (12 corresponding lines) · ×2
  • Edited copy of a member (12 corresponding lines) ios/WireguardCopiedFiles/WgLoggerForApp.swift:20 — ios/WireguardCopiedFiles/WgLoggerForApp.swift:20-31 | ios/WireguardCopiedFilesExtension/WgLoggerForExtension.swift:14-25 — 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) common/lib/src/app_variants/family/module/schedule/json.dart:79 — common/lib/src/app_variants/family/module/schedule/json.dart:79-92 | common/lib/src/app_variants/family/module/schedule/json.dart:131-142 — 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 (5 corresponding lines) · ×2
  • Edited copy of a member (5 corresponding lines) common/lib/src/app_variants/v6/widget/filters_section.dart:174 — common/lib/src/app_variants/v6/widget/filters_section.dart:174-178 | common/lib/src/features/filter/ui/filter.dart:148-152 — 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) common/lib/src/app_variants/family/module/device_v3/actor.dart:133 — common/lib/src/app_variants/family/module/device_v3/actor.dart:133-137 | common/lib/src/app_variants/family/module/family/devices.dart:104-108 — 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.
D4 · Code Duplication · Edited copies of one member (3 members, 4+ corresponding lines) · ×2
  • Edited copies of one member (3 members, 4+ corresponding lines) common/lib/src/features/notification/domain/command.dart:17 — common/lib/src/features/notification/domain/command.dart:17-20 | common/lib/src/features/plus/domain/command.dart:15-18 | common/lib/src/platform/filter/command.dart:15-18 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 4 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 4+ corresponding lines) common/lib/src/features/notification/domain/command.dart:27 — common/lib/src/features/notification/domain/command.dart:27-30 | common/lib/src/features/plus/domain/command.dart:20-23 | common/lib/src/platform/filter/command.dart:20-23 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 4 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 · Duplicated block (18 lines × 2) · ×2
  • Duplicated block (18 lines × 2) common/lib/src/features/plus/ui/device_limit_sheet.dart:61 — common/lib/src/features/plus/ui/device_limit_sheet.dart:61-78 | common/lib/src/features/safari/ui/safari_onboard_yt_sheet.dart:125-142 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `common/lib/src/features/plus/ui/device_limit_sheet.dart:61` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `common/lib/src/features/safari/ui/safari_onboard_yt_sheet.dart:122` calls `openSafariSetup` and `common/lib/src/features/plus/ui/device_limit_sheet.dart:58` 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 (18 lines × 2) common/lib/src/features/stats/ui/domain_detail_section.dart:1169 — common/lib/src/features/stats/ui/domain_detail_section.dart:1169-1186 | common/lib/src/features/stats/ui/domain_detail_section.dart:1218-1235 — 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 `common/lib/src/features/stats/ui/domain_detail_section.dart:1169` 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 × 4) · ×2
  • Duplicated block (15 lines × 4) common/lib/src/app_variants/v6/widget/attach_sheet.dart:91 — common/lib/src/app_variants/v6/widget/attach_sheet.dart:91-105 | common/lib/src/app_variants/v6/widget/freemium/weekly_refresh_sheet.dart:71-85 | common/lib/src/features/safari/ui/safari_onboard_sheet.dart:35-49 | common/lib/src/features/safari/ui/safari_onboard_yt_sheet.dart:33-47 — before extracting anything, compare `common/lib/src/features/safari/ui/safari_onboard_sheet.dart` and `common/lib/src/features/safari/ui/safari_onboard_yt_sheet.dart` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 151 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `common/lib/src/app_variants/v6/widget/attach_sheet.dart:91` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (15 lines × 4) common/lib/src/features/private_dns/ui/private_dns_sheet_ios.dart:61 — common/lib/src/features/private_dns/ui/private_dns_sheet_ios.dart:61-75 | common/lib/src/features/private_dns/ui/private_dns_sheet_macos.dart:61-75 | common/lib/src/features/safari/ui/safari_onboard_sheet.dart:49-63 | common/lib/src/features/safari/ui/safari_onboard_yt_sheet.dart:47-61 — before extracting anything, compare `common/lib/src/features/private_dns/ui/private_dns_sheet_ios.dart` and `common/lib/src/features/private_dns/ui/private_dns_sheet_macos.dart` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 148 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `common/lib/src/features/private_dns/ui/private_dns_sheet_ios.dart:61` 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 (14–15 lines × 2) · ×2
  • Duplicated block (14–15 lines × 2) common/lib/src/core/value.dart:143 — common/lib/src/core/value.dart:143-156 | common/lib/src/core/value.dart:245-259 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `common/lib/src/core/value.dart:143` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (14–15 lines × 2) ios/App/Binding/Notification.swift:160 — ios/App/Binding/Notification.swift:160-174 | ios/App/Binding/Notification.swift:184-197 — 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 (11–12 lines × 2) · ×2
  • Duplicated block (11–12 lines × 2) common/lib/src/features/filter/domain/actor.dart:120 — common/lib/src/features/filter/domain/actor.dart:120-130 | common/lib/src/features/filter/domain/actor.dart:241-252 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `common/lib/src/features/filter/domain/actor.dart:120` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `common/lib/src/features/filter/domain/actor.dart:131` calls `log`, `i` and `common/lib/src/features/filter/domain/actor.dart:254` does not — after which the two agree again for 4 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
  • Duplicated block (11–12 lines × 2) common/lib/src/features/stats/ui/stats_filter.dart:131 — common/lib/src/features/stats/ui/stats_filter.dart:131-141 | common/lib/src/features/stats/ui/stats_filter.dart:157-168 — 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 `common/lib/src/features/stats/ui/stats_filter.dart:131` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
D4 · Code Duplication · Duplicated block (12 lines × 2) · ×2
  • Duplicated block (12 lines × 2) ios/App/Service/PrivateDnsService.swift:204 — ios/App/Service/PrivateDnsService.swift:204-215 | ios/App/Service/PrivateDnsServiceMac.swift:172-183 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `ios/App/Service/PrivateDnsService.swift:199` calls `eraseToAnyPublisher` and `ios/App/Service/PrivateDnsServiceMac.swift:168` 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 (12 lines × 2) ios/App/ServiceImpl/LoggerSaver.swift:61 — ios/App/ServiceImpl/LoggerSaver.swift:61-72 | ios/WireguardCopiedFilesExtension/NELogger.swift:103-114 — before extracting anything, compare `ios/App/ServiceImpl/LoggerSaver.swift` and `ios/WireguardCopiedFilesExtension/NELogger.swift` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 37 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `ios/App/ServiceImpl/LoggerSaver.swift:61` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
R10 · Code Duplication · Duplicated block (12 lines × 2 locations) · ×2
  • Duplicated block (12 lines × 2 locations) automation/appium/wdio/src/flows/app.ts:18 — automation/appium/wdio/src/flows/app.ts:18 · automation/appium/wdio/src/flows/app.ts:31 — 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 (12 lines × 2 locations) automation/device/lib/log.mjs:72 — automation/device/lib/log.mjs:72 · automation/device/lib/log.mjs:88 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
R10 · Code Duplication · Duplicated block (8 lines × 2 locations) · ×2
  • Duplicated block (8 lines × 2 locations) automation/device/log.mjs:29 — automation/device/log.mjs:29 · automation/device/log.mjs:53 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
  • Duplicated block (8 lines × 2 locations) ios/BlockaWebExtension/Resources/popup.js:95 — ios/BlockaWebExtension/Resources/popup.js:95 · ios/BlockaWebExtension/Resources/popup.js:133 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
R10 · Code Duplication · Duplicated block (6 lines × 2 locations) · ×2
  • Duplicated block (6 lines × 2 locations) automation/appium/wdio/scripts/lib/ai-explorer-runner.mjs:775 — automation/appium/wdio/scripts/lib/ai-explorer-runner.mjs:775 · automation/appium/wdio/scripts/lib/ai-explorer-runner.mjs:842 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
  • Duplicated block (6 lines × 2 locations) automation/appium/wdio/scripts/lib/ai-explorer-runner.mjs:930 — automation/appium/wdio/scripts/lib/ai-explorer-runner.mjs:930 · automation/appium/wdio/scripts/lib/ai-explorer-runner.mjs:937 — 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.
AXI1 · Runtime container hardening · Container process runs as root · ×1
  • Container process runs as root: wd-runtime-app — 'wd-runtime-app' (wd-runtime-app:scan) runs as uid 0 — no user was specified, or one resolving to root was. Observed on the running container, which is the only place the answer is settled: an image's own USER, a base image's inherited one and a compose override are all invisible to a REDACTED reader. Advisory evidence for CRA Annex I (2)(b).
AXR1 · Runtime accessibility (rendered) · WCAG 2.4.2 reproducibly failed in a rendered surface · ×1
  • WCAG 2.4.2 reproducibly failed in a rendered surface — axe-core rule(s) document-title failed on: html. Runtime evidence (advisory — not scored); fix and re-scan to verify it clears.
AXR1 · Runtime accessibility (rendered) · WCAG 3.1.1 reproducibly failed in a rendered surface · ×1
  • WCAG 3.1.1 reproducibly failed in a rendered surface — axe-core rule(s) html-has-lang failed on: html. Runtime evidence (advisory — not scored); fix and re-scan to verify it clears.
D1 · Cyclomatic Complexity · ai-explorer-runner.runAiExplorer (cyclomatic 63) · ×1
  • ai-explorer-runner.runAiExplorer (cyclomatic 63) automation/appium/wdio/scripts/lib/ai-explorer-runner.mjs:1258 — ai-explorer-runner.runAiExplorer has cyclomatic complexity 63 (threshold 15). Of this number, 60 points are the body's own statements and 3 belong to 2 function literals inside it that branch. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · explorer-commands.runExplorerCommand (cyclomatic 49) · ×1
  • explorer-commands.runExplorerCommand (cyclomatic 49) automation/appium/wdio/scripts/lib/explorer-commands.mjs:417 — explorer-commands.runExplorerCommand has cyclomatic complexity 49 (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 · DomainDetailSectionState._getSubtitleText (cyclomatic 47) · ×1
  • DomainDetailSectionState._getSubtitleText (cyclomatic 47) common/lib/src/features/stats/ui/domain_detail_section.dart:137 — DomainDetailSectionState._getSubtitleText has cyclomatic complexity 47 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · filterConnectedDevices (cyclomatic 29) · ×1
  • filterConnectedDevices (cyclomatic 29) automation/shared/lib/devices.mjs:71 — filterConnectedDevices has cyclomatic complexity 29 (threshold 15). Most of this is not in the body itself: 1 of the 29 points is its own statement and the rest belongs to one function literal inside it that branches (line 72). The decisions are inside the literal, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literal's work into a named function or method at the enclosing scope and have the literal call it, then reduce whichever part then reads as the largest.
D1 · Cyclomatic Complexity · FamilyActor._updatePhaseNow (cyclomatic 27) · ×1
  • FamilyActor._updatePhaseNow (cyclomatic 27) common/lib/src/app_variants/family/module/family/actor.dart:208 — FamilyActor._updatePhaseNow has cyclomatic complexity 27 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
D1 · Cyclomatic Complexity · Notification.swift.mapNotificationToUser (cyclomatic 27) · ×1
  • Notification.swift.mapNotificationToUser (cyclomatic 27) ios/App/Binding/Notification.swift:114 — Notification.swift.mapNotificationToUser has cyclomatic complexity 27 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · TopDomainsState.build (cyclomatic 25) · ×1
  • TopDomainsState.build (cyclomatic 25) common/lib/src/features/stats/ui/top_domains.dart:76 — TopDomainsState.build 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 · AppStatusStrategy.getCurrentStatus (cyclomatic 24) · ×1
  • AppStatusStrategy.getCurrentStatus (cyclomatic 24) common/lib/src/platform/app/app.dart:110 — AppStatusStrategy.getCurrentStatus has cyclomatic complexity 24 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
D1 · Cyclomatic Complexity · AppStartStoreBase.onAppStatus (cyclomatic 23) · ×1
  • AppStartStoreBase.onAppStatus (cyclomatic 23) common/lib/src/platform/app/start/start.dart:82 — AppStartStoreBase.onAppStatus 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 · ai-explorer-runner.evaluateSummary (cyclomatic 22) · ×1
  • ai-explorer-runner.evaluateSummary (cyclomatic 22) automation/appium/wdio/scripts/lib/ai-explorer-runner.mjs:633 — ai-explorer-runner.evaluateSummary 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 · ScheduleModel.validate (cyclomatic 21) · ×1
  • ScheduleModel.validate (cyclomatic 21) common/lib/src/app_variants/family/module/schedule/json.dart:155 — ScheduleModel.validate 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 · DomainDetailSectionState._maybeFetchStatsRequestsCount (cyclomatic 19) · ×1
  • DomainDetailSectionState._maybeFetchStatsRequestsCount (cyclomatic 19) common/lib/src/features/stats/ui/domain_detail_section.dart:495 — DomainDetailSectionState._maybeFetchStatsRequestsCount 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 · _NowSectionState._buildStatusRow (cyclomatic 18) · ×1
  • _NowSectionState._buildStatusRow (cyclomatic 18) common/lib/src/app_variants/family/widget/device/now_section.dart:156 — _NowSectionState._buildStatusRow has cyclomatic complexity 18 (threshold 15). To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Where every arm is uniform — the same kind of value, with no behaviour of its own — a table keyed by the case is the shorter form; wherever the arms carry different data or different behaviour, keep them as cases, because collapsing those trades an explicit, reviewable set of cases for nothing.
D1 · Cyclomatic Complexity · CustomlistActor.getRelevantRulesForDomain (cyclomatic 18) · ×1
  • CustomlistActor.getRelevantRulesForDomain (cyclomatic 18) common/lib/src/features/customlist/domain/actor.dart:239 — CustomlistActor.getRelevantRulesForDomain has cyclomatic complexity 18 (threshold 15). To reduce it, break up the iteration: give each loop body a named function, and split a multi-phase loop into one function per phase so no single body carries the whole pipeline.
D1 · Cyclomatic Complexity · JournalActor.fetch (cyclomatic 18) · ×1
  • JournalActor.fetch (cyclomatic 18) common/lib/src/features/journal/domain/actor.dart:40 — JournalActor.fetch 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 · ai-explorer-report.renderMarkdownReport (cyclomatic 18) · ×1
  • ai-explorer-report.renderMarkdownReport (cyclomatic 18) automation/appium/wdio/scripts/lib/ai-explorer-report.mjs:88 — ai-explorer-report.renderMarkdownReport has cyclomatic complexity 18 (threshold 15). Of this number, 16 points are the body's own statements and 2 belong to 2 function literals inside it that branch. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · DeviceSectionState.build (cyclomatic 17) · ×1
  • DeviceSectionState.build (cyclomatic 17) common/lib/src/app_variants/family/widget/device/device_section.dart:103 — DeviceSectionState.build 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 · SettingsState.build (cyclomatic 17) · ×1
  • SettingsState.build (cyclomatic 17) common/lib/src/features/settings/ui/settings_section.dart:101 — SettingsState.build has cyclomatic complexity 17 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
D1 · Cyclomatic Complexity · DomainDetailSectionState._fetchSubdomains (cyclomatic 17) · ×1
  • DomainDetailSectionState._fetchSubdomains (cyclomatic 17) common/lib/src/features/stats/ui/domain_detail_section.dart:610 — DomainDetailSectionState._fetchSubdomains 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 · DomainDetailSectionState._fetchRecentActivity (cyclomatic 17) · ×1
  • DomainDetailSectionState._fetchRecentActivity (cyclomatic 17) common/lib/src/features/stats/ui/domain_detail_section.dart:780 — DomainDetailSectionState._fetchRecentActivity has cyclomatic complexity 17 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
D1 · Cyclomatic Complexity · StageBinding.doShowModal (cyclomatic 17) · ×1
  • StageBinding.doShowModal (cyclomatic 17) ios/App/Binding/Stage/StageBinding.swift:82 — StageBinding.doShowModal has cyclomatic complexity 17 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
D1 · Cyclomatic Complexity · log.filterLogText (cyclomatic 17) · ×1
  • log.filterLogText (cyclomatic 17) automation/device/lib/log.mjs:154 — log.filterLogText 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 · V6FiltersSectionState.build (cyclomatic 16) · ×1
  • V6FiltersSectionState.build (cyclomatic 16) common/lib/src/app_variants/v6/widget/filters_section.dart:52 — V6FiltersSectionState.build 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 · RadialChart.build (cyclomatic 16) · ×1
  • RadialChart.build (cyclomatic 16) common/lib/src/app_variants/v6/widget/home/stats/radial_chart.dart:75 — RadialChart.build has cyclomatic complexity 16 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
D1 · Cyclomatic Complexity · NotificationAlarmReceiver.onReceive (cyclomatic 16) · ×1
  • NotificationAlarmReceiver.onReceive (cyclomatic 16) android/app/src/main/java/service/NotificationService.kt:207 — NotificationAlarmReceiver.onReceive has cyclomatic complexity 16 (threshold 15). To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Where every arm is uniform — the same kind of value, with no behaviour of its own — a table keyed by the case is the shorter form; wherever the arms carry different data or different behaviour, keep them as cases, because collapsing those trades an explicit, reviewable set of cases for nothing.
D1 · Cyclomatic Complexity · ai-explorer-runner.runMissionSurface (cyclomatic 16) · ×1
  • ai-explorer-runner.runMissionSurface (cyclomatic 16) automation/appium/wdio/scripts/lib/ai-explorer-runner.mjs:1060 — ai-explorer-runner.runMissionSurface 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 · page-source.listLabels (cyclomatic 16) · ×1
  • page-source.listLabels (cyclomatic 16) REDACTED:200 — page-source.listLabels has cyclomatic complexity 16 (threshold 15). Of this number, 10 points are the body's own statements and 6 belong to one function literal inside it that branches. To reduce it, 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 · resolveTargetDevice (cyclomatic 16) · ×1
  • resolveTargetDevice (cyclomatic 16) automation/shared/lib/devices.mjs:185 — resolveTargetDevice 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.
D2 · Cognitive Complexity · DomainDetailSectionState._getSubtitleText (cognitive 144) · ×1
  • DomainDetailSectionState._getSubtitleText (cognitive 144) common/lib/src/features/stats/ui/domain_detail_section.dart:137 — DomainDetailSectionState._getSubtitleText has cognitive complexity 144 (threshold 15). Drivers by points: if/else 59 (131 pts), boolean chains 13 (nesting depth added 72). To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
D2 · Cognitive Complexity · ai-explorer-runner.runAiExplorer (cognitive 102) · ×1
  • ai-explorer-runner.runAiExplorer (cognitive 102) automation/appium/wdio/scripts/lib/ai-explorer-runner.mjs:1258 — ai-explorer-runner.runAiExplorer has cognitive complexity 102 (threshold 15). Drivers by points: if/else 34 (66 pts), ternaries 7 (17 pts), boolean chains 12, error handling 3 (5 pts), loops 2 (nesting depth added 44). Of this number, 101 points are the body's own statements and 1 belongs to 2 function literals inside it that branch. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · DomainDetailSectionState._fetchSubdomains (cognitive 48) · ×1
  • DomainDetailSectionState._fetchSubdomains (cognitive 48) common/lib/src/features/stats/ui/domain_detail_section.dart:610 — DomainDetailSectionState._fetchSubdomains has cognitive complexity 48 (threshold 15). Drivers by points: if/else 7 (22 pts), loops 6 (21 pts), boolean chains 2, ternaries 1 (2 pts), error handling 1 (nesting depth added 31). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · TopDomainsState.build (cognitive 46) · ×1
  • TopDomainsState.build (cognitive 46) common/lib/src/features/stats/ui/top_domains.dart:76 — TopDomainsState.build has cognitive complexity 46 (threshold 15). Drivers by points: if/else 12 (23 pts), ternaries 6 (10 pts), loops 3 (7 pts), boolean chains 6 (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 · ScheduleModel.validate (cognitive 37) · ×1
  • ScheduleModel.validate (cognitive 37) common/lib/src/app_variants/family/module/schedule/json.dart:155 — ScheduleModel.validate has cognitive complexity 37 (threshold 15). Drivers by points: if/else 11 (26 pts), boolean chains 6, loops 3 (5 pts) (nesting depth added 17). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · explorer-commands.runExplorerCommand (cognitive 37) · ×1
  • explorer-commands.runExplorerCommand (cognitive 37) automation/appium/wdio/scripts/lib/explorer-commands.mjs:417 — explorer-commands.runExplorerCommand has cognitive complexity 37 (threshold 15). Drivers by points: if/else 12 (22 pts), ternaries 4 (8 pts), boolean chains 6, match/switch 1 (nesting depth added 14). 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 · AppStartStoreBase.onAppStatus (cognitive 36) · ×1
  • AppStartStoreBase.onAppStatus (cognitive 36) common/lib/src/platform/app/start/start.dart:82 — AppStartStoreBase.onAppStatus has cognitive complexity 36 (threshold 15). Drivers by points: if/else 19 (32 pts), boolean chains 4 (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 · Notification.swift.mapNotificationToUser (cognitive 36) · ×1
  • Notification.swift.mapNotificationToUser (cognitive 36) ios/App/Binding/Notification.swift:114 — Notification.swift.mapNotificationToUser has cognitive complexity 36 (threshold 15). Drivers by points: if/else 19 (24 pts), boolean chains 9, ternaries 1 (3 pts) (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · Log.log (cognitive 35) · ×1
  • Log.log (cognitive 35) common/lib/src/core/logger/logger.dart:33 — Log.log has cognitive complexity 35 (threshold 15). Drivers by points: if/else 10 (29 pts), boolean chains 4, loops 1 (2 pts) (nesting depth added 20). To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
D2 · Cognitive Complexity · JournalActor.fetch (cognitive 34) · ×1
  • JournalActor.fetch (cognitive 34) common/lib/src/features/journal/domain/actor.dart:40 — JournalActor.fetch has cognitive complexity 34 (threshold 15). Drivers by points: if/else 15 (28 pts), boolean chains 4, ternaries 1 (2 pts) (nesting depth added 14). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · FilterActor._parse (cognitive 33) · ×1
  • FilterActor._parse (cognitive 33) common/lib/src/features/filter/domain/actor.dart:171 — FilterActor._parse has cognitive complexity 33 (threshold 15). Drivers by points: if/else 10 (29 pts), loops 3 (4 pts) (nesting depth added 20). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · FilterActor._reconfigure (cognitive 30) · ×1
  • FilterActor._reconfigure (cognitive 30) common/lib/src/features/filter/domain/actor.dart:235 — FilterActor._reconfigure has cognitive complexity 30 (threshold 15). Drivers by points: if/else 7 (19 pts), loops 4 (11 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 · ToplistMovementSource._fromToplists (cognitive 30) · ×1
  • ToplistMovementSource._fromToplists (cognitive 30) common/lib/src/features/notification/domain/weekly_report.dart:601 — ToplistMovementSource._fromToplists has cognitive complexity 30 (threshold 15). Drivers by points: ternaries 8 (22 pts), if/else 3 (6 pts), loops 2 (nesting depth added 17). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · FilterActor.getConfig (cognitive 29) · ×1
  • FilterActor.getConfig (cognitive 29) common/lib/src/features/filter/domain/actor.dart:116 — FilterActor.getConfig has cognitive complexity 29 (threshold 15). Drivers by points: if/else 6 (18 pts), loops 4 (11 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 · ai-explorer-model.findJsonEnd (cognitive 29) · ×1
  • ai-explorer-model.findJsonEnd (cognitive 29) automation/appium/wdio/scripts/lib/ai-explorer-model.mjs:40 — ai-explorer-model.findJsonEnd has cognitive complexity 29 (threshold 15). Drivers by points: if/else 9 (23 pts), ternaries 1 (3 pts), boolean chains 2, loops 1 (nesting depth added 16). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · ai-explorer-report.renderMarkdownReport (cognitive 29) · ×1
  • ai-explorer-report.renderMarkdownReport (cognitive 29) automation/appium/wdio/scripts/lib/ai-explorer-report.mjs:88 — ai-explorer-report.renderMarkdownReport has cognitive complexity 29 (threshold 15). Drivers by points: ternaries 5 (12 pts), if/else 8, loops 3 (6 pts), boolean chains 3 (nesting depth added 10). Of this number, 27 points are the body's own statements and 2 belong to 2 function literals inside it that branch. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · AppStatusStrategy.getCurrentStatus (cognitive 28) · ×1
  • AppStatusStrategy.getCurrentStatus (cognitive 28) common/lib/src/platform/app/app.dart:110 — AppStatusStrategy.getCurrentStatus has cognitive complexity 28 (threshold 15). Drivers by points: if/else 11, boolean chains 9, ternaries 4 (8 pts) (nesting depth added 4). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
D2 · Cognitive Complexity · ai-explorer-runner.evaluateSummary (cognitive 28) · ×1
  • ai-explorer-runner.evaluateSummary (cognitive 28) automation/appium/wdio/scripts/lib/ai-explorer-runner.mjs:633 — ai-explorer-runner.evaluateSummary has cognitive complexity 28 (threshold 15). Drivers by points: if/else 16 (22 pts), boolean chains 5, 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 · ai-explorer-runner.runMissionSurface (cognitive 28) · ×1
  • ai-explorer-runner.runMissionSurface (cognitive 28) automation/appium/wdio/scripts/lib/ai-explorer-runner.mjs:1060 — ai-explorer-runner.runMissionSurface has cognitive complexity 28 (threshold 15). Drivers by points: if/else 7 (12 pts), ternaries 2 (7 pts), error handling 2 (5 pts), loops 2 (3 pts), boolean chains 1 (nesting depth added 14). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · FamilyActor._updatePhaseNow (cognitive 27) · ×1
  • FamilyActor._updatePhaseNow (cognitive 27) common/lib/src/app_variants/family/module/family/actor.dart:208 — FamilyActor._updatePhaseNow has cognitive complexity 27 (threshold 15). Drivers by points: if/else 15, boolean chains 12. 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 · DomainDetailSectionState._maybeFetchStatsRequestsCount (cognitive 27) · ×1
  • DomainDetailSectionState._maybeFetchStatsRequestsCount (cognitive 27) common/lib/src/features/stats/ui/domain_detail_section.dart:495 — DomainDetailSectionState._maybeFetchStatsRequestsCount has cognitive complexity 27 (threshold 15). Drivers by points: if/else 12 (16 pts), boolean chains 6, ternaries 2 (4 pts), error handling 1 (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · VpnActor.setActualStatus (cognitive 25) · ×1
  • VpnActor.setActualStatus (cognitive 25) common/lib/src/features/plus/domain/vpn/actor.dart:114 — VpnActor.setActualStatus has cognitive complexity 25 (threshold 15). Drivers by points: if/else 13 (17 pts), boolean chains 4, error handling 1 (4 pts) (nesting depth added 7). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, 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 · settings.openSettingsSection (cognitive 25) · ×1
  • settings.openSettingsSection (cognitive 25) automation/appium/wdio/src/flows/settings.ts:294 — settings.openSettingsSection has cognitive complexity 25 (threshold 15). Drivers by points: if/else 6 (14 pts), error handling 3 (6 pts), loops 2 (3 pts), boolean chains 2 (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 · V6FiltersSectionState.build (cognitive 22) · ×1
  • V6FiltersSectionState.build (cognitive 22) common/lib/src/app_variants/v6/widget/filters_section.dart:52 — V6FiltersSectionState.build has cognitive complexity 22 (threshold 15). Drivers by points: if/else 4 (7 pts), loops 4 (6 pts), boolean chains 5, ternaries 2 (4 pts) (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · alerts.acceptNotificationAlert (cognitive 22) · ×1
  • alerts.acceptNotificationAlert (cognitive 22) automation/appium/wdio/src/flows/alerts.ts:103 — alerts.acceptNotificationAlert has cognitive complexity 22 (threshold 15). Drivers by points: error handling 4 (10 pts), if/else 3 (6 pts), loops 3 (5 pts), boolean chains 1 (nesting depth added 11). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · log.filterLogText (cognitive 22) · ×1
  • log.filterLogText (cognitive 22) automation/device/lib/log.mjs:154 — log.filterLogText has cognitive complexity 22 (threshold 15). Drivers by points: if/else 6 (12 pts), loops 4, boolean chains 3, ternaries 3 (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · DeviceSectionState.build (cognitive 21) · ×1
  • DeviceSectionState.build (cognitive 21) common/lib/src/app_variants/family/widget/device/device_section.dart:103 — DeviceSectionState.build has cognitive complexity 21 (threshold 15). Drivers by points: if/else 8 (13 pts), error handling 5, ternaries 3 (nesting depth added 5). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · RecentActivityState.build (cognitive 21) · ×1
  • RecentActivityState.build (cognitive 21) common/lib/src/features/stats/ui/recent_activity.dart:46 — RecentActivityState.build has cognitive complexity 21 (threshold 15). Drivers by points: if/else 8 (15 pts), loops 1 (4 pts), boolean chains 1, ternaries 1 (nesting depth added 10). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · PlusActor.switchPlus (cognitive 20) · ×1
  • PlusActor.switchPlus (cognitive 20) common/lib/src/features/plus/domain/actor.dart:103 — PlusActor.switchPlus has cognitive complexity 20 (threshold 15). Drivers by points: error handling 3 (9 pts), if/else 2 (5 pts), loops 1 (4 pts), boolean chains 2 (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 · SettingsState.build (cognitive 20) · ×1
  • SettingsState.build (cognitive 20) common/lib/src/features/settings/ui/settings_section.dart:101 — SettingsState.build has cognitive complexity 20 (threshold 15). Drivers by points: ternaries 9, if/else 5 (7 pts), boolean chains 2, error handling 1 (2 pts) (nesting depth added 3). To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
D2 · Cognitive Complexity · DomainDetailSectionState._fetchRecentActivity (cognitive 20) · ×1
  • DomainDetailSectionState._fetchRecentActivity (cognitive 20) common/lib/src/features/stats/ui/domain_detail_section.dart:780 — DomainDetailSectionState._fetchRecentActivity has cognitive complexity 20 (threshold 15). Drivers by points: if/else 9 (10 pts), ternaries 5 (6 pts), boolean chains 3, error handling 1 (nesting depth added 2). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
D2 · Cognitive Complexity · Navigation.generateRoute (cognitive 20) · ×1
  • Navigation.generateRoute (cognitive 20) common/lib/src/shared/navigation.dart:73 — Navigation.generateRoute has cognitive complexity 20 (threshold 15). Drivers by points: if/else 11 (20 pts) (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · CustomlistActor.getRelevantRulesForDomain (cognitive 19) · ×1
  • CustomlistActor.getRelevantRulesForDomain (cognitive 19) common/lib/src/features/customlist/domain/actor.dart:239 — CustomlistActor.getRelevantRulesForDomain has cognitive complexity 19 (threshold 15). Drivers by points: loops 7 (9 pts), boolean chains 8, if/else 2 (nesting depth added 2). To reduce it, break up the iteration: give each loop body a named function, and split a multi-phase loop into one function per phase so no single body carries the whole pipeline.
D2 · Cognitive Complexity · FilterActor.getFilterContainingList (cognitive 19) · ×1
  • FilterActor.getFilterContainingList (cognitive 19) common/lib/src/features/filter/domain/actor.dart:70 — FilterActor.getFilterContainingList has cognitive complexity 19 (threshold 15). Drivers by points: if/else 7 (13 pts), boolean chains 3, loops 2 (3 pts) (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · page-source.listLabels (cognitive 19) · ×1
  • page-source.listLabels (cognitive 19) REDACTED:200 — page-source.listLabels has cognitive complexity 19 (threshold 15). Drivers by points: if/else 6 (12 pts), boolean chains 5, loops 1, ternaries 1 (nesting depth added 6). Of this number, 10 points are the body's own statements and 9 belong to one function literal inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · page-source.listVisibleElements (cognitive 19) · ×1
  • page-source.listVisibleElements (cognitive 19) REDACTED:248 — page-source.listVisibleElements has cognitive complexity 19 (threshold 15). Drivers by points: if/else 6 (13 pts), boolean chains 3, loops 2 (3 pts) (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · WeeklyReportActor._generatePick (cognitive 18) · ×1
  • WeeklyReportActor._generatePick (cognitive 18) common/lib/src/features/notification/domain/weekly_report.dart:989 — WeeklyReportActor._generatePick has cognitive complexity 18 (threshold 15). Drivers by points: if/else 7 (12 pts), error handling 1 (2 pts), ternaries 1 (2 pts), boolean chains 1, loops 1 (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · ai-explorer-runner.ensureHomeSurface (cognitive 18) · ×1
  • ai-explorer-runner.ensureHomeSurface (cognitive 18) automation/appium/wdio/scripts/lib/ai-explorer-runner.mjs:960 — ai-explorer-runner.ensureHomeSurface has cognitive complexity 18 (threshold 15). Drivers by points: ternaries 3 (7 pts), if/else 3 (5 pts), error handling 2 (4 pts), loops 2 (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 · resolveTargetDevice (cognitive 18) · ×1
  • resolveTargetDevice (cognitive 18) automation/shared/lib/devices.mjs:185 — resolveTargetDevice has cognitive complexity 18 (threshold 15). Drivers by points: if/else 8 (11 pts), other 4, boolean chains 3 (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 · SupportActor._sendMessage (cognitive 17) · ×1
  • SupportActor._sendMessage (cognitive 17) common/lib/src/features/support/domain/actor.dart:281 — SupportActor._sendMessage has cognitive complexity 17 (threshold 15). Drivers by points: if/else 7 (14 pts), error handling 2, boolean chains 1 (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · StageBinding.doShowModal (cognitive 17) · ×1
  • StageBinding.doShowModal (cognitive 17) ios/App/Binding/Stage/StageBinding.swift:82 — StageBinding.doShowModal has cognitive complexity 17 (threshold 15). Drivers by points: if/else 17. 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 · page-source.filterTreeEntries (cognitive 17) · ×1
  • page-source.filterTreeEntries (cognitive 17) REDACTED:160 — page-source.filterTreeEntries has cognitive complexity 17 (threshold 15). Drivers by points: if/else 6 (10 pts), boolean chains 4, loops 2 (3 pts) (nesting depth added 5). Of this number, 13 points are the body's own statements and 4 belong to one function literal inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · platform.scrollIntoView (cognitive 17) · ×1
  • platform.scrollIntoView (cognitive 17) automation/appium/wdio/src/support/platform.ts:146 — platform.scrollIntoView has cognitive complexity 17 (threshold 15). Drivers by points: if/else 5 (10 pts), loops 2 (3 pts), boolean chains 2, ternaries 1 (2 pts) (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · renderReport (cognitive 17) · ×1
  • renderReport (cognitive 17) automation/dep-validate/report.mjs:170 — renderReport has cognitive complexity 17 (threshold 15). Drivers by points: if/else 10 (13 pts), loops 1 (2 pts), other 2 (nesting depth added 4). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition.
D2 · Cognitive Complexity · DeviceSectionState._openRuleEditor (cognitive 16) · ×1
  • DeviceSectionState._openRuleEditor (cognitive 16) common/lib/src/app_variants/family/widget/device/device_section.dart:371 — DeviceSectionState._openRuleEditor has cognitive complexity 16 (threshold 15). Drivers by points: if/else 4 (8 pts), error handling 4, ternaries 4 (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 · Scheduler._reschedule (cognitive 16) · ×1
  • Scheduler._reschedule (cognitive 16) common/lib/src/core/scheduler.dart:188 — Scheduler._reschedule has cognitive complexity 16 (threshold 15). Drivers by points: if/else 8 (13 pts), boolean chains 3 (nesting depth added 5). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · RateActor.checkRateConditions (cognitive 16) · ×1
  • RateActor.checkRateConditions (cognitive 16) common/lib/src/features/rate/domain/actor.dart:78 — RateActor.checkRateConditions has cognitive complexity 16 (threshold 15). Drivers by points: if/else 10 (14 pts), boolean chains 2 (nesting depth added 4). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · SupportActor.sendEvent (cognitive 16) · ×1
  • SupportActor.sendEvent (cognitive 16) common/lib/src/features/support/domain/actor.dart:322 — SupportActor.sendEvent has cognitive complexity 16 (threshold 15). Drivers by points: if/else 7 (13 pts), error handling 2, 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 · PlatformPermActor._recheckDnsPerm (cognitive 16) · ×1
  • PlatformPermActor._recheckDnsPerm (cognitive 16) common/lib/src/platform/perm/actor.dart:178 — PlatformPermActor._recheckDnsPerm has cognitive complexity 16 (threshold 15). Drivers by points: if/else 7 (13 pts), ternaries 1 (2 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 · junit-summary.parseSuites (cognitive 16) · ×1
  • junit-summary.parseSuites (cognitive 16) automation/appium/wdio/scripts/junit-summary.mjs:53 — junit-summary.parseSuites has cognitive complexity 16 (threshold 15). Drivers by points: if/else 4 (7 pts), boolean chains 4, 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 · settings.toggleDnsSwitchIfNeeded (cognitive 16) · ×1
  • settings.toggleDnsSwitchIfNeeded (cognitive 16) automation/appium/wdio/src/flows/settings.ts:384 — settings.toggleDnsSwitchIfNeeded has cognitive complexity 16 (threshold 15). Drivers by points: if/else 3 (10 pts), boolean chains 3, loops 2 (3 pts) (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · main (cognitive 16) · ×1
  • main (cognitive 16) automation/device/log.mjs:13 — main has cognitive complexity 16 (threshold 15). Drivers by points: if/else 6 (10 pts), other 6 (nesting depth added 4). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · discoverAdvisories (cognitive 16) · ×1
  • discoverAdvisories (cognitive 16) automation/dep-validate/lib/queue.mjs:215 — discoverAdvisories has cognitive complexity 16 (threshold 15). Drivers by points: if/else 3 (6 pts), error handling 3 (4 pts), boolean chains 2, loops 2, other 1, ternaries 1 (nesting depth added 4). Of this number, 15 points are the body's own statements and 1 belongs to 2 function literals inside it that branch. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D29 · Static Analysis (SAST) · REDACTED · ×1
  • REDACTED
D29 · Static Analysis (SAST) · REDACTED · ×1
  • REDACTED
D29 · Static Analysis (SAST) · REDACTED · ×1
  • REDACTED
D29 · Static Analysis (SAST) · REDACTED · ×1
  • REDACTED
D29 · Static Analysis (SAST) · REDACTED · ×1
  • REDACTED
D31 · IaC & Container Security · Medium IaC · ×1
  • REDACTED
D36 · Supply-chain Provenance & Signing · REDACTED · ×1
  • REDACTED
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) common/lib/src/features/plus/ui/device_limit_sheet.dart:15 — common/lib/src/features/plus/ui/device_limit_sheet.dart:15-84 | common/lib/src/features/private_dns/ui/private_dns_sheet_ios.dart:30-165 | common/lib/src/features/private_dns/ui/private_dns_sheet_macos.dart:32-142 | common/lib/src/features/safari/ui/safari_onboard_yt_sheet.dart:19-177 — 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 (60 corresponding lines) · ×1
  • Edited copy of a member (60 corresponding lines) ios/Family/ContentView.swift:30 — ios/Family/ContentView.swift:30-89 | ios/NotFamily/ContentView.swift:30-91 — These two members are one piece of code written twice and then edited apart: 60 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copy of a member (73 corresponding lines) · ×1
  • Edited copy of a member (73 corresponding lines) common/lib/src/features/private_dns/ui/private_dns_setting_guide.dart:28 — common/lib/src/features/private_dns/ui/private_dns_setting_guide.dart:28-104 | common/lib/src/features/safari/ui/safari_setting_guide.dart:26-98 — These two members are one piece of code written twice and then edited apart: 73 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 (54 corresponding lines) · ×1
  • Edited copy of a member (54 corresponding lines) common/lib/src/features/filter/domain/actor.dart:116 — common/lib/src/features/filter/domain/actor.dart:116-169 | common/lib/src/features/filter/domain/actor.dart:235-307 — These two members are one piece of code written twice and then edited apart: 54 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, 41+ corresponding lines) · ×1
  • Edited copies of one member (3 members, 41+ corresponding lines) ios/App/Binding/CommonBinding.swift:47 — ios/App/Binding/CommonBinding.swift:47-87 | ios/App/Binding/CommonBinding.swift:89-136 | ios/App/Binding/CommonBinding.swift:138-188 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 41 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 (48 corresponding lines) · ×1
  • Edited copy of a member (48 corresponding lines) common/lib/src/features/stats/ui/domain_detail_section.dart:1134 — common/lib/src/features/stats/ui/domain_detail_section.dart:1134-1186 | common/lib/src/features/stats/ui/domain_detail_section.dart:1188-1235 — These two members are one piece of code written twice and then edited apart: 48 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copy of a member (44 corresponding lines) · ×1
  • Edited copy of a member (44 corresponding lines) android/app/src/six/kotlin/ui/AdaptyPaymentFragment.kt:60 — android/app/src/six/kotlin/ui/AdaptyPaymentFragment.kt:60-103 | android/app/src/six/kotlin/ui/AdaptyPaymentTabletDialogFragment.kt:85-128 — These two members are one piece of code written twice and then edited apart: 44 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 (46 corresponding lines) · ×1
  • Edited copy of a member (46 corresponding lines) common/lib/src/features/stats/ui/domain_detail_section.dart:1396 — common/lib/src/features/stats/ui/domain_detail_section.dart:1396-1441 | common/lib/src/features/stats/ui/recent_activity.dart:182-231 — These two members are one piece of code written twice and then edited apart: 46 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copy of a member (27 corresponding lines) · ×1
  • Edited copy of a member (27 corresponding lines) common/lib/src/app_variants/family/module/device_v3/actor.dart:212 — common/lib/src/app_variants/family/module/device_v3/actor.dart:212-245 | common/lib/src/app_variants/family/module/device_v3/actor.dart:250-276 — 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 (21 corresponding lines) · ×1
  • Edited copy of a member (21 corresponding lines) ios/App/ServiceImpl/LoggerSaver.swift:51 — ios/App/ServiceImpl/LoggerSaver.swift:51-72 | ios/WireguardCopiedFilesExtension/NELogger.swift:94-114 — These two members are one piece of code written twice and then edited apart: 21 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copy of a member (33 corresponding lines) · ×1
  • Edited copy of a member (33 corresponding lines) common/lib/src/app_variants/family/widget/home/device/home_device_header.dart:20 — common/lib/src/app_variants/family/widget/home/device/home_device_header.dart:20-52 | common/lib/src/shared/ui/minicard/header.dart:26-59 — These two members are one piece of code written twice and then edited apart: 33 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 (26 corresponding lines) · ×1
  • Edited copy of a member (26 corresponding lines) common/lib/src/app_variants/family/widget/home/big_icon.dart:175 — common/lib/src/app_variants/family/widget/home/big_icon.dart:175-200 | common/lib/src/app_variants/family/widget/home/big_icon.dart:202-227 — These two members are one piece of code written twice and then edited apart: 26 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) common/lib/src/platform/command/command.dart:67 — common/lib/src/platform/command/command.dart:67-79 | common/lib/src/platform/command/command.dart:81-93 | common/lib/src/platform/command/command.dart:95-107 — 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 (13 corresponding lines) · ×1
  • Edited copy of a member (13 corresponding lines) common/lib/src/features/plus/domain/vpn/actor.dart:86 — common/lib/src/features/plus/domain/vpn/actor.dart:86-98 | common/lib/src/features/plus/domain/vpn/actor.dart:100-112 — 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 copies of one member (4 members, 12+ corresponding lines) · ×1
  • Edited copies of one member (4 members, 12+ corresponding lines) common/lib/src/features/journal/domain/api.dart:8 — common/lib/src/features/journal/domain/api.dart:8-19 | common/lib/src/features/journal/domain/api.dart:57-68 | common/lib/src/features/plus/domain/gateway/api.dart:8-19 | common/lib/src/features/plus/domain/lease/api.dart:10-21 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 12 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 4 times and the copies will drift further apart.
D4 · Code Duplication · Edited copies of one member (3 members, 12+ corresponding lines) · ×1
  • Edited copies of one member (3 members, 12+ corresponding lines) common/lib/src/features/journal/domain/api.dart:39 — common/lib/src/features/journal/domain/api.dart:39-50 | common/lib/src/features/plus/domain/lease/api.dart:43-55 | common/lib/src/platform/device/api.dart:37-48 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 12 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication · Edited copies of one member (3 members, 14+ corresponding lines) · ×1
  • Edited copies of one member (3 members, 14+ corresponding lines) android/app/src/main/java/binding/CommonBinding.kt:103 — android/app/src/main/java/binding/CommonBinding.kt:103-116 | android/app/src/main/java/binding/CommonBinding.kt:123-136 | android/app/src/main/java/binding/CommonBinding.kt:144-159 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 14 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication · Edited copies of one member (3 members, 9+ corresponding lines) · ×1
  • Edited copies of one member (3 members, 9+ corresponding lines) common/lib/src/app_variants/family/module/device_v3/json.dart:99 — common/lib/src/app_variants/family/module/device_v3/json.dart:99-107 | common/lib/src/app_variants/family/module/profile/json.dart:55-63 | common/lib/src/features/customlist/domain/api.dart:56-64 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 9 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication · Edited copies of one member (3 members, 7+ corresponding lines) · ×1
  • Edited copies of one member (3 members, 7+ corresponding lines) ios/App/Binding/CommandsBinding.swift:94 — ios/App/Binding/CommandsBinding.swift:94-100 | ios/App/Binding/CommandsBinding.swift:102-108 | ios/App/Binding/CommandsBinding.swift:110-116 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 7 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication · Edited copies of one member (4 members, 8+ corresponding lines) · ×1
  • Edited copies of one member (4 members, 8+ corresponding lines) common/lib/src/app_variants/family/module/qrscan/qrscan.dart:16 — common/lib/src/app_variants/family/module/qrscan/qrscan.dart:16-24 | common/lib/src/features/perm/domain/perm.dart:22-30 | common/lib/src/features/plus/domain/plus.dart:59-67 | common/lib/src/features/support/domain/actor.dart:82-89 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 8 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 4 times and the copies will drift further apart.
D4 · Code Duplication · Edited copies of one member (3 members, 3+ corresponding lines) · ×1
  • Edited copies of one member (3 members, 3+ corresponding lines) ios/App/Binding/Vpn/NetxServiceIn.swift:54 — ios/App/Binding/Vpn/NetxServiceIn.swift:54-56 | ios/App/Service/PrivateDnsService.swift:50-52 | ios/App/Service/PrivateDnsServiceMac.swift:27-31 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 3 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 · Duplicated block (66 lines × 2) · ×1
  • Duplicated block (66 lines × 2) common/lib/src/features/safari/ui/safari_onboard_sheet.dart:28 — common/lib/src/features/safari/ui/safari_onboard_sheet.dart:28-93 | common/lib/src/features/safari/ui/safari_onboard_yt_sheet.dart:26-91 — before extracting anything, compare `common/lib/src/features/safari/ui/safari_onboard_sheet.dart` and `common/lib/src/features/safari/ui/safari_onboard_yt_sheet.dart` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 151 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `common/lib/src/features/safari/ui/safari_onboard_sheet.dart:28` 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 (49 lines × 2) · ×1
  • Duplicated block (49 lines × 2) common/lib/src/features/stats/ui/domain_detail_section.dart:212 — common/lib/src/features/stats/ui/domain_detail_section.dart:212-260 | common/lib/src/features/stats/ui/domain_detail_section.dart:265-313 — 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 (33–43 lines × 2) · ×1
  • Duplicated block (33–43 lines × 2) common/lib/src/features/filter/domain/actor.dart:133 — common/lib/src/features/filter/domain/actor.dart:133-165 | common/lib/src/features/filter/domain/actor.dart:252-294 — 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 `common/lib/src/features/filter/domain/actor.dart:133` 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, `common/lib/src/features/filter/domain/actor.dart:131` calls `log`, `i` and `common/lib/src/features/filter/domain/actor.dart:252` 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 (32–33 lines × 2) · ×1
  • Duplicated block (32–33 lines × 2) common/lib/src/features/private_dns/ui/private_dns_sheet_ios.dart:130 — common/lib/src/features/private_dns/ui/private_dns_sheet_ios.dart:130-162 | common/lib/src/features/private_dns/ui/private_dns_sheet_macos.dart:109-140 — before extracting anything, compare `common/lib/src/features/private_dns/ui/private_dns_sheet_ios.dart` and `common/lib/src/features/private_dns/ui/private_dns_sheet_macos.dart` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 148 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `common/lib/src/features/private_dns/ui/private_dns_sheet_ios.dart:130` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (28–30 lines × 2) · ×1
  • Duplicated block (28–30 lines × 2) common/lib/src/features/private_dns/ui/private_dns_sheet_ios.dart:50 — common/lib/src/features/private_dns/ui/private_dns_sheet_ios.dart:50-77 | common/lib/src/features/private_dns/ui/private_dns_sheet_macos.dart:48-77 — before extracting anything, compare `common/lib/src/features/private_dns/ui/private_dns_sheet_ios.dart` and `common/lib/src/features/private_dns/ui/private_dns_sheet_macos.dart` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 148 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `common/lib/src/features/private_dns/ui/private_dns_sheet_ios.dart:50` 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 (25 lines × 2) · ×1
  • Duplicated block (25 lines × 2) common/lib/src/app_variants/family/widget/home/qr_scan_sheet_macos.dart:287 — common/lib/src/app_variants/family/widget/home/qr_scan_sheet_macos.dart:287-311 | common/lib/src/features/safari/ui/safari_onboard_yt_sheet.dart:153-177 — 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 `common/lib/src/app_variants/family/widget/home/qr_scan_sheet_macos.dart:287` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (22–24 lines × 2) · ×1
  • Duplicated block (22–24 lines × 2) common/lib/src/features/stats/ui/domain_detail_section.dart:1144 — common/lib/src/features/stats/ui/domain_detail_section.dart:1144-1167 | common/lib/src/features/stats/ui/domain_detail_section.dart:1195-1216 — 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 `common/lib/src/features/stats/ui/domain_detail_section.dart:1144` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
D4 · Code Duplication · Duplicated block (23 lines × 2) · ×1
  • Duplicated block (23 lines × 2) common/lib/src/features/stats/ui/recent_activity.dart:126 — common/lib/src/features/stats/ui/recent_activity.dart:126-148 | common/lib/src/features/stats/ui/top_domains.dart:186-208 — before extracting anything, compare `common/lib/src/features/stats/ui/recent_activity.dart` and `common/lib/src/features/stats/ui/top_domains.dart` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 70 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `common/lib/src/features/stats/ui/recent_activity.dart:126` 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 (19–21 lines × 3) · ×1
  • Duplicated block (19–21 lines × 3) common/lib/src/app_variants/family/widget/home/qr_scan_sheet_macos.dart:101 — common/lib/src/app_variants/family/widget/home/qr_scan_sheet_macos.dart:101-120 | common/lib/src/features/private_dns/ui/private_dns_sheet_ios.dart:41-59 | common/lib/src/features/private_dns/ui/private_dns_sheet_macos.dart:39-59 — before extracting anything, compare `common/lib/src/app_variants/family/widget/home/qr_scan_sheet_macos.dart` and `common/lib/src/features/private_dns/ui/private_dns_sheet_ios.dart` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 53 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `common/lib/src/app_variants/family/widget/home/qr_scan_sheet_macos.dart:101` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
D4 · Code Duplication · Duplicated block (21 lines × 2) · ×1
  • Duplicated block (21 lines × 2) common/lib/src/features/safari/ui/safari_onboard_sheet.dart:95 — common/lib/src/features/safari/ui/safari_onboard_sheet.dart:95-115 | common/lib/src/features/safari/ui/safari_onboard_yt_sheet.dart:93-113 — before extracting anything, compare `common/lib/src/features/safari/ui/safari_onboard_sheet.dart` and `common/lib/src/features/safari/ui/safari_onboard_yt_sheet.dart` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 151 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `common/lib/src/features/safari/ui/safari_onboard_sheet.dart:95` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (16–19 lines × 2) · ×1
  • Duplicated block (16–19 lines × 2) common/lib/src/features/plus/ui/vpn_bypass_dialog.dart:66 — common/lib/src/features/plus/ui/vpn_bypass_dialog.dart:66-84 | common/lib/src/features/stats/ui/stats_filter.dart:47-62 — 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 `common/lib/src/features/plus/ui/vpn_bypass_dialog.dart:66` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (17 lines × 4) · ×1
  • Duplicated block (17 lines × 4) common/lib/src/features/plus/ui/device_limit_sheet.dart:59 — common/lib/src/features/plus/ui/device_limit_sheet.dart:59-75 | common/lib/src/features/private_dns/ui/private_dns_sheet_ios.dart:134-150 | common/lib/src/features/private_dns/ui/private_dns_sheet_macos.dart:113-129 | common/lib/src/features/safari/ui/safari_onboard_yt_sheet.dart:123-139 — before extracting anything, compare `common/lib/src/features/private_dns/ui/private_dns_sheet_ios.dart` and `common/lib/src/features/private_dns/ui/private_dns_sheet_macos.dart` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 148 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `common/lib/src/features/plus/ui/device_limit_sheet.dart:59` 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, `common/lib/src/features/private_dns/ui/private_dns_sheet_macos.dart:112` calls `doOpenPermSettings` and `common/lib/src/features/plus/ui/device_limit_sheet.dart:58` 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 (17 lines × 2) · ×1
  • Duplicated block (17 lines × 2) common/lib/src/app_variants/family/widget/device/now_section.dart:124 — common/lib/src/app_variants/family/widget/device/now_section.dart:124-140 | common/lib/src/app_variants/family/widget/device/schedule_section.dart:95-111 — 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 `common/lib/src/app_variants/family/widget/device/now_section.dart:124` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
D4 · Code Duplication · Duplicated block (16 lines × 5) · ×1
  • Duplicated block (16 lines × 5) common/lib/src/app_variants/family/widget/home/qr_scan_sheet_macos.dart:97 — common/lib/src/app_variants/family/widget/home/qr_scan_sheet_macos.dart:97-112 | common/lib/src/features/private_dns/ui/private_dns_sheet_ios.dart:37-52 | common/lib/src/features/private_dns/ui/private_dns_sheet_macos.dart:35-50 | common/lib/src/features/safari/ui/safari_onboard_sheet.dart:24-39 | common/lib/src/features/safari/ui/safari_onboard_yt_sheet.dart:22-37 — before extracting anything, compare `common/lib/src/app_variants/family/widget/home/qr_scan_sheet_macos.dart` and `common/lib/src/features/private_dns/ui/private_dns_sheet_ios.dart` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 53 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `common/lib/src/app_variants/family/widget/home/qr_scan_sheet_macos.dart:97` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `common/lib/src/features/safari/ui/safari_onboard_sheet.dart:21` calls `shouldShowSetupLaterOnSafariOnboard` and `common/lib/src/features/safari/ui/safari_onboard_yt_sheet.dart:20` does not — after which the two agree again for 3 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
D4 · Code Duplication · Duplicated block (16 lines × 4) · ×1
  • Duplicated block (16 lines × 4) common/lib/src/app_variants/family/widget/home/qr_scan_sheet_macos.dart:101 — common/lib/src/app_variants/family/widget/home/qr_scan_sheet_macos.dart:101-116 | common/lib/src/features/plus/ui/device_limit_sheet.dart:22-37 | common/lib/src/features/private_dns/ui/private_dns_sheet_ios.dart:41-56 | common/lib/src/features/private_dns/ui/private_dns_sheet_macos.dart:39-54 — before extracting anything, compare `common/lib/src/app_variants/family/widget/home/qr_scan_sheet_macos.dart` and `common/lib/src/features/private_dns/ui/private_dns_sheet_ios.dart` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 53 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `common/lib/src/app_variants/family/widget/home/qr_scan_sheet_macos.dart:101` 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 (13–15 lines × 2) · ×1
  • Duplicated block (13–15 lines × 2) common/lib/src/features/stats/ui/horizontal_radial_segment.dart:178 — common/lib/src/features/stats/ui/horizontal_radial_segment.dart:178-192 | common/lib/src/features/stats/ui/horizontal_radial_segment.dart:209-221 — 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 `common/lib/src/features/stats/ui/horizontal_radial_segment.dart:178` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (11–13 lines × 2) · ×1
  • Duplicated block (11–13 lines × 2) common/lib/src/features/stats/ui/domain_detail_section.dart:1281 — common/lib/src/features/stats/ui/domain_detail_section.dart:1281-1293 | common/lib/src/features/stats/ui/domain_detail_section.dart:1300-1310 — 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 `common/lib/src/features/stats/ui/domain_detail_section.dart:1281` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
D4 · Code Duplication · Duplicated block (10–11 lines × 3) · ×1
  • Duplicated block (10–11 lines × 3) common/lib/src/features/stats/ui/domain_detail_section.dart:644 — common/lib/src/features/stats/ui/domain_detail_section.dart:644-654 | common/lib/src/features/stats/ui/domain_detail_section.dart:689-698 | common/lib/src/features/stats/ui/domain_detail_section.dart:707-716 — 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 `common/lib/src/features/stats/ui/domain_detail_section.dart:644` 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, `common/lib/src/features/stats/ui/domain_detail_section.dart:684` calls `log`, `pair` and `common/lib/src/features/stats/ui/domain_detail_section.dart:642` 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 (6–9 lines × 2) · ×1
  • Duplicated block (6–9 lines × 2) common/lib/src/app_variants/v6/widget/home/power_button.dart:579 — common/lib/src/app_variants/v6/widget/home/power_button.dart:579-584 | common/lib/src/app_variants/v6/widget/home/power_button.dart:609-617 — 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 (9 lines × 3) · ×1
  • Duplicated block (9 lines × 3) common/lib/src/features/lock/ui/keypad.dart:89 — common/lib/src/features/lock/ui/keypad.dart:89-97 | common/lib/src/features/lock/ui/keypad.dart:100-108 | common/lib/src/features/lock/ui/keypad.dart:111-119 — 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 `common/lib/src/features/lock/ui/keypad.dart:89` 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 (33–34 lines × 2) · ×1
  • Duplicated block (33–34 lines × 2) android/app/src/six/kotlin/ui/AdaptyPaymentFragment.kt:70 — android/app/src/six/kotlin/ui/AdaptyPaymentFragment.kt:70-103 | android/app/src/six/kotlin/ui/AdaptyPaymentTabletDialogFragment.kt:96-128 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `android/app/src/six/kotlin/ui/AdaptyPaymentFragment.kt:70` 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 (44 lines × 2) · ×1
  • Duplicated block (44 lines × 2) ios/Family/ContentView.swift:46 — ios/Family/ContentView.swift:46-89 | ios/NotFamily/ContentView.swift:48-91 — `ios/Family/ContentView.swift` and `ios/NotFamily/ContentView.swift` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 2 separate duplicated blocks between them, totalling at least 60 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own. Read the line range as the matched WINDOW rather than a finished unit: at `ios/Family/ContentView.swift:46` 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, `ios/NotFamily/ContentView.swift:47` calls `LocationListView` and `ios/Family/ContentView.swift:45` does not — after which the two agree again for 3 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
D4 · Code Duplication · Duplicated block (24 lines × 2) · ×1
  • Duplicated block (24 lines × 2) ios/App/Binding/CommonBinding.swift:108 — ios/App/Binding/CommonBinding.swift:108-131 | ios/App/Binding/CommonBinding.swift:160-183 — 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 `ios/App/Binding/CommonBinding.swift:108` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it. Note first that the copies are not typed on the same thing: the declarations holding them bind `completion` to `@escaping (Result<String, Error>) -> Void` in one and `@escaping (Result<String, any Error>) -> Void` in another, and the duplicated lines use it. The extracted unit therefore needs a parameter type that fits BOTH — their common supertype where they have one, or a new abstraction over them where they do not — and settling that is the step that comes BEFORE the extraction above. Where the two types are deliberately unrelated, the duplication is the price of that separation and the honest resolution is to record the decision rather than to extract.
D4 · Code Duplication · Duplicated block (22 lines × 2) · ×1
  • Duplicated block (22 lines × 2) ios/Family/HomeViewModel.swift:151 — ios/Family/HomeViewModel.swift:151-172 | ios/NotFamily/HomeViewModel.swift:158-179 — `ios/Family/HomeViewModel.swift` and `ios/NotFamily/HomeViewModel.swift` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 14 separate duplicated blocks between them, totalling at least 142 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own.
D4 · Code Duplication · Duplicated block (15–16 lines × 2) · ×1
  • Duplicated block (15–16 lines × 2) ios/App/Service/PrivateDnsService.swift:126 — ios/App/Service/PrivateDnsService.swift:126-140 | ios/App/Service/PrivateDnsServiceMac.swift:46-61 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
D4 · Code Duplication · Duplicated block (13 lines × 3) · ×1
  • Duplicated block (13 lines × 3) ios/App/Binding/CommonBinding.swift:51 — ios/App/Binding/CommonBinding.swift:51-63 | ios/App/Binding/CommonBinding.swift:94-106 | ios/App/Binding/CommonBinding.swift:144-156 — 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 `ios/App/Binding/CommonBinding.swift:51` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note first that the copies are not typed on the same thing: the declarations holding them bind `completion` to `@escaping (Result<String, Error>) -> Void` in one and `@escaping (Result<String, any Error>) -> Void` in another, and the duplicated lines use it. The extracted unit therefore needs a parameter type that fits BOTH — their common supertype where they have one, or a new abstraction over them where they do not — and settling that is the step that comes BEFORE the extraction above. Where the two types are deliberately unrelated, the duplication is the price of that separation and the honest resolution is to record the decision rather than to extract.
D4 · Code Duplication · Duplicated block (11 lines × 3) · ×1
  • Duplicated block (11 lines × 3) ios/App/Binding/CommonBinding.swift:77 — ios/App/Binding/CommonBinding.swift:77-87 | ios/App/Binding/CommonBinding.swift:126-136 | ios/App/Binding/CommonBinding.swift:178-188 — 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 `ios/App/Binding/CommonBinding.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. Note first that the copies are not typed on the same thing: the declarations holding them bind `completion` to `@escaping (Result<String, Error>) -> Void` in one and `@escaping (Result<String, any Error>) -> Void` 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, `ios/App/Binding/CommonBinding.swift:124` calls `String`, `Data`, `e` and `ios/App/Binding/CommonBinding.swift:76` does not — after which the two agree again for 3 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
D4 · Code Duplication · Duplicated block (10 lines × 3) · ×1
  • Duplicated block (10 lines × 3) ios/App/Binding/CommonBinding.swift:67 — ios/App/Binding/CommonBinding.swift:67-76 | ios/App/Binding/CommonBinding.swift:114-123 | ios/App/Binding/CommonBinding.swift:166-175 — 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 `ios/App/Binding/CommonBinding.swift:67` 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 `completion` to `@escaping (Result<String, Error>) -> Void` in one and `@escaping (Result<String, any Error>) -> Void` in another, and the duplicated lines use it. The extracted unit therefore needs a parameter type that fits BOTH — their common supertype where they have one, or a new abstraction over them where they do not — and settling that is the step that comes BEFORE the extraction above. Where the two types are deliberately unrelated, the duplication is the price of that separation and the honest resolution is to record the decision rather than to extract. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `ios/App/Binding/CommonBinding.swift:124` calls `String`, `Data`, `e` and `ios/App/Binding/CommonBinding.swift:77` 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.
R1 · Type Safety · Type Safety · ×1
  • Type Safety — 29 typed · 50 plain JS — the untyped files are automation/appium/wdio/scripts/ai-explore.mjs, automation/appium/wdio/scripts/check-driver.mjs, automation/appium/wdio/scripts/explore.mjs, automation/appium/wdio/scripts/junit-summary.mjs, automation/appium/wdio/scripts/lib/ai-explorer-config.mjs, automation/appium/wdio/scripts/lib/ai-explorer-guardrails.mjs (+44 more).
R10 · Code Duplication · Duplicated block (27 lines × 2 locations) · ×1
  • Duplicated block (27 lines × 2 locations) automation/appium/wdio/scripts/lib/explorer-commands.mjs:443 — automation/appium/wdio/scripts/lib/explorer-commands.mjs:443 · automation/appium/wdio/scripts/lib/explorer-commands.mjs:470 — 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.
R10 · Code Duplication · Duplicated block (20 lines × 2 locations) · ×1
  • Duplicated block (20 lines × 2 locations) REDACTED:367 — REDACTED:367 · REDACTED:400 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
R10 · Code Duplication · Duplicated block (19 lines × 2 locations) · ×1
  • Duplicated block (19 lines × 2 locations) automation/device/lib/log.mjs:105 — automation/device/lib/log.mjs:105 · automation/device/lib/log.mjs:125 — 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.
R10 · Code Duplication · Duplicated block (16 lines × 2 locations) · ×1
  • Duplicated block (16 lines × 2 locations) automation/appium/wdio/scripts/lib/ai-explorer-runner.mjs:1493 — automation/appium/wdio/scripts/lib/ai-explorer-runner.mjs:1493 · automation/appium/wdio/scripts/lib/ai-explorer-runner.mjs:1513 — 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.
R10 · Code Duplication · Duplicated block (10 lines × 2 locations) · ×1
  • Duplicated block (10 lines × 2 locations) REDACTED:528 — REDACTED:528 · REDACTED:538 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
R10 · Code Duplication · Duplicated block (9 lines × 2 locations) · ×1
  • Duplicated block (9 lines × 2 locations) automation/appium/wdio/scripts/lib/ai-explorer-config.mjs:4 — automation/appium/wdio/scripts/lib/ai-explorer-config.mjs:4 · automation/appium/wdio/scripts/lib/ai-explorer-config.mjs:14 — 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.
R10 · Code Duplication · Duplicated block (7 lines × 3 locations) · ×1
  • Duplicated block (7 lines × 3 locations) automation/appium/wdio/src/flows/account.ts:48 — automation/appium/wdio/src/flows/account.ts:48 · automation/appium/wdio/src/flows/nav.ts:69 · automation/appium/wdio/src/flows/nav.ts:81 — the 3 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
R10 · Code Duplication · Duplicated block (7 lines × 2 locations) · ×1
  • Duplicated block (7 lines × 2 locations) ios/BlockaWebExtension/Resources/popup.js:128 — ios/BlockaWebExtension/Resources/popup.js:128 · ios/BlockaWebExtension/Resources/popup.js:156 — 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.
R2 · Cyclomatic Complexity · Complex function runAiExplorer (cyclomatic 70, cognitive 112) · ×1
  • Complex function runAiExplorer (cyclomatic 70, cognitive 112) automation/appium/wdio/scripts/lib/ai-explorer-runner.mjs:1258 — runAiExplorer has cyclomatic complexity 70 and cognitive complexity 112; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
R2 · Cyclomatic Complexity · Complex function runExplorerCommand (cyclomatic 52, cognitive 40) · ×1
  • Complex function runExplorerCommand (cyclomatic 52, cognitive 40) automation/appium/wdio/scripts/lib/explorer-commands.mjs:417 — runExplorerCommand has cyclomatic complexity 52 and cognitive complexity 40; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
R2 · Cyclomatic Complexity · Complex function (anonymous) (cyclomatic 29, cognitive 9) · ×1
  • Complex function (anonymous) (cyclomatic 29, cognitive 9) automation/shared/lib/devices.mjs:72 — (anonymous) has cyclomatic complexity 29 and cognitive complexity 9; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
R2 · Cyclomatic Complexity · Complex function evaluateSummary (cyclomatic 25, cognitive 31) · ×1
  • Complex function evaluateSummary (cyclomatic 25, cognitive 31) automation/appium/wdio/scripts/lib/ai-explorer-runner.mjs:633 — evaluateSummary has cyclomatic complexity 25 and cognitive complexity 31; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
R2 · Cyclomatic Complexity · Complex function command (cyclomatic 22, cognitive 26) · ×1
  • Complex function command (cyclomatic 22, cognitive 26) automation/appium/wdio/scripts/tests/ai-explorer-runner.test.mjs:57 — command has cyclomatic complexity 22 and cognitive complexity 26; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
R2 · Cyclomatic Complexity · Complex function renderMarkdownReport (cyclomatic 20, cognitive 28) · ×1
  • Complex function renderMarkdownReport (cyclomatic 20, cognitive 28) automation/appium/wdio/scripts/lib/ai-explorer-report.mjs:88 — renderMarkdownReport has cyclomatic complexity 20 and cognitive complexity 28; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
R2 · Cyclomatic Complexity · Complex function runMissionSurface (cyclomatic 17, cognitive 29) · ×1
  • Complex function runMissionSurface (cyclomatic 17, cognitive 29) automation/appium/wdio/scripts/lib/ai-explorer-runner.mjs:1060 — runMissionSurface has cyclomatic complexity 17 and cognitive complexity 29; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
R2 · Cyclomatic Complexity · Complex function filterLogText (cyclomatic 17, cognitive 22) · ×1
  • Complex function filterLogText (cyclomatic 17, cognitive 22) automation/device/lib/log.mjs:154 — filterLogText has cyclomatic complexity 17 and cognitive complexity 22; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
R2 · Cyclomatic Complexity · Complex function resolveTargetDevice (cyclomatic 16, cognitive 18) · ×1
  • Complex function resolveTargetDevice (cyclomatic 16, cognitive 18) automation/shared/lib/devices.mjs:185 — resolveTargetDevice has cyclomatic complexity 16 and cognitive complexity 18; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
R2 · Cyclomatic Complexity · Complex function openSettingsSection (cyclomatic 15, cognitive 26) · ×1
  • Complex function openSettingsSection (cyclomatic 15, cognitive 26) automation/appium/wdio/src/flows/settings.ts:294 — openSettingsSection has cyclomatic complexity 15 and cognitive complexity 26; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
R2 · Cyclomatic Complexity · Complex function compareToGolden (cyclomatic 15, cognitive 22) · ×1
  • Complex function compareToGolden (cyclomatic 15, cognitive 22) automation/appium/wdio/src/support/golden.ts:86 — compareToGolden has cyclomatic complexity 15 and cognitive complexity 22; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
R2 · Cyclomatic Complexity · Complex function inspectUi (cyclomatic 15, cognitive 12) · ×1
  • Complex function inspectUi (cyclomatic 15, cognitive 12) automation/appium/wdio/scripts/lib/explorer-commands.mjs:258 — inspectUi has cyclomatic complexity 15 and cognitive complexity 12; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
R2 · Cyclomatic Complexity · Complex function findJsonEnd (cyclomatic 14, cognitive 29) · ×1
  • Complex function findJsonEnd (cyclomatic 14, cognitive 29) automation/appium/wdio/scripts/lib/ai-explorer-model.mjs:40 — findJsonEnd has cyclomatic complexity 14 and cognitive complexity 29; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
R2 · Cyclomatic Complexity · Complex function renderReport (cyclomatic 14, cognitive 17) · ×1
  • Complex function renderReport (cyclomatic 14, cognitive 17) automation/dep-validate/report.mjs:170 — renderReport has cyclomatic complexity 14 and cognitive complexity 17; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
R2 · Cyclomatic Complexity · Complex function getFeaturesList (cyclomatic 14, cognitive 12) · ×1
  • Complex function getFeaturesList (cyclomatic 14, cognitive 12) ios/BlockaWebExtension/Resources/popup.js:174 — getFeaturesList has cyclomatic complexity 14 and cognitive complexity 12; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
R2 · Cyclomatic Complexity · Complex function execute (cyclomatic 13, cognitive 18) · ×1
  • Complex function execute (cyclomatic 13, cognitive 18) automation/appium/wdio/scripts/tests/explorer-commands.test.mjs:146 — execute has cyclomatic complexity 13 and cognitive complexity 18; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
R2 · Cyclomatic Complexity · Complex function parseSuites (cyclomatic 13, cognitive 17) · ×1
  • Complex function parseSuites (cyclomatic 13, cognitive 17) automation/appium/wdio/scripts/junit-summary.mjs:53 — parseSuites has cyclomatic complexity 13 and cognitive complexity 17; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
R2 · Cyclomatic Complexity · Complex function main (cyclomatic 13, cognitive 16) · ×1
  • Complex function main (cyclomatic 13, cognitive 16) automation/device/log.mjs:13 — main has cyclomatic complexity 13 and cognitive complexity 16; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
R2 · Cyclomatic Complexity · Complex function screenBodyValues (cyclomatic 13, cognitive 10) · ×1
  • Complex function screenBodyValues (cyclomatic 13, cognitive 10) automation/appium/wdio/scripts/lib/ai-explorer-runner.mjs:277 — screenBodyValues has cyclomatic complexity 13 and cognitive complexity 10; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
R3 · Large Files · automation/appium/wdio/src/flows/settings.ts · ×1
  • automation/appium/wdio/src/flows/settings.ts: 444 lines of code automation/appium/wdio/src/flows/settings.ts:1 — automation/appium/wdio/src/flows/settings.ts has 444 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R7 · Dead Code · Dead file (~176 LoC) · ×1
  • Dead file (~176 LoC) automation/appium/wdio/src/support/golden.ts — no import path from any entry point (24 application, 16 tooling, 30 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
R8 · Dependency Hygiene · Unlisted import '@wdio/types' · ×1
  • Unlisted import '@wdio/types' automation/appium/wdio/wdio.android.conf.ts:3 — Imported only as a TYPE and declared in no reachable package.json. The import is erased at compile time, so nothing is installed and no runtime resolution depends on it — but type-checking a clean clone will fail. Declare the typings it resolves through (or the package itself) in the owning package.json.
X18 · Disposal-pattern correctness · Owned disposable field is never released · ×1
  • Owned disposable field is never released common/lib/src/features/stats/ui/stats_filter.dart:26 — `StatsFilterState` carries a disposal duty — a `State`, so the framework calls its `dispose()` when it leaves the tree — and it creates `_ctrl` itself (line 26, `TextEditingController`), which makes that instance its own. Nothing in the class releases it — no `_ctrl.dispose()`, no tear-off of it, on any path — nothing elsewhere in the library releases it through another instance, and it is never handed on as a value (passed positionally, returned, stored, collected), so no other owner can be ending it. Passing it as a named argument does not: a widget or animation never disposes a controller it was given. On what was read, `TextEditingController` outlives the object that made it — its listeners, and through them this object and everything it references, stay reachable, and a ticker, timer or subscription keeps calling into a disposed object. Release it where the duty is discharged: `_ctrl.dispose();` in `dispose()` before `super.dispose()`.
X2 · Cancellation propagation · Async function without AbortSignal · ×1
  • Async function without AbortSignal: isAppiumServerReady REDACTED:340 — `isAppiumServerReady` awaits `fetch(…)` but neither accepts an AbortSignal nor passes one on, so its caller cannot stop the request once it has started. Accept `{ signal }` and pass it through: `fetch(url, { signal })`.
Minor — 34 finding(s)
X10 · Duplicated predicate · Duplicated predicate · ×9
  • Duplicated predicate common/lib/src/platform/app/start/start.dart:127 — `!_stage.route.isForeground() || !_stage.route.isMainRoute()` appears character-identically in 2 files — common/lib/src/platform/app/start/start.dart, common/lib/src/platform/perm/actor.dart. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate common/lib/src/app_variants/family/module/stats/actor.dart:169 — `action == "fallthrough" || action == "allowed"` appears character-identically in 3 files — common/lib/src/app_variants/family/module/stats/actor.dart, common/lib/src/features/notification/domain/weekly_report.dart, common/lib/src/platform/stats/stats.dart. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate common/lib/src/features/payment/domain/actor.dart:247 — `attributes == null || attributes.isEmpty` appears character-identically in 2 files — common/lib/src/features/payment/domain/actor.dart, common/lib/src/features/payment/domain/attribute_converter.dart. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate common/lib/src/app_variants/family/module/stats/actor.dart:246 — `bucket.action == "fallthrough" || bucket.action == "allowed"` appears character-identically in 3 files — common/lib/src/app_variants/family/module/stats/actor.dart, common/lib/src/platform/stats/delta_store.dart, common/lib/src/platform/stats/stats.dart. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate common/lib/src/features/stats/ui/domain_detail_section.dart:467 — `metric.tags.action == "allowed" || metric.tags.action == "fallthrough"` appears character-identically in 2 files — common/lib/src/features/stats/ui/domain_detail_section.dart, common/lib/src/platform/stats/stats.dart. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate automation/appium/wdio/src/flows/account.ts:210 — `typeof value === "string" && value.toLowerCase() === "inactive"` appears character-identically in 2 files — automation/appium/wdio/src/flows/account.ts, automation/appium/wdio/src/flows/home.ts. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate REDACTED:151 — `typeof value === "string" && value.trim().length > 0` appears character-identically in 2 files — REDACTED, automation/appium/wdio/src/flows/settings.ts. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate automation/appium/wdio/scripts/lib/ai-explorer-guardrails.mjs:41 — `value != null && typeof value === "object" && !Array.isArray(value)` appears character-identically in 2 files — automation/appium/wdio/scripts/lib/ai-explorer-guardrails.mjs, automation/appium/wdio/scripts/lib/session-protocol.mjs. 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 ios/Family/ContentView.swift:61 — `self.homeVM.showSplash || self.homeVM.hideContent` appears character-identically in 2 files — ios/Family/ContentView.swift, ios/NotFamily/ContentView.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.
X7 · Silent fallback defaults · Silent fallback default in catch · ×4
  • Silent fallback default in catch automation/shared/lib/devices.mjs:14 — `parseXcdeviceJson` swallows every exception into `return []` — a data error becomes a silent behavior change with no trail. Log the failure or let it raise. If that constant is the correct answer rather than a stand-in for a value that could not be read, say so in a comment on the handler or in the docstring, and the row stops firing.
  • Silent fallback default in catch automation/shared/lib/devices.mjs:135 — `readDeviceList` swallows every exception into `return []` — a data error becomes a silent behavior change with no trail. Log the failure or let it raise. If that constant is the correct answer rather than a stand-in for a value that could not be read, say so in a comment on the handler or in the docstring, and the row stops firing.
  • Silent fallback default in catch automation/appium/wdio/scripts/junit-summary.mjs:132 — `readSuites` swallows every exception into `return []` — a data error becomes a silent behavior change with no trail. Log the failure or let it raise. If that constant is the correct answer rather than a stand-in for a value that could not be read, say so in a comment on the handler or in the docstring, and the row stops firing.
  • Silent fallback default in catch automation/dep-validate/lib/queue.mjs:225 — `discoverAdvisories` swallows every exception into `return ""` — a data error becomes a silent behavior change with no trail. Log the failure or let it raise. If that constant is the correct answer rather than a stand-in for a value that could not be read, say so in a comment on the handler or in the docstring, and the row stops firing.
D24 · Comment Value · redundant comment · ×2
  • redundant comment ios/BlockaWebExtension/Resources/popup.js:313 — "Setup swipe navigation" repeats the code it sits on: 3 of its 3 words (setup, swipe, navigation) are already in `setupSwipeNavigation();`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
  • redundant comment ios/BlockaWebExtension/tests/ui/popup.spec.js:93 — 5 comments in this file only repeat the code they sit on (lines 93, 112, 136, 154, 177), for example "Check for black borders". Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
D20 · ADR Quality · No ADRs found · ×1
  • No ADRs found — No ADRs found. No recognised ADR directory (`docs/adr/`, `docs/decisions/`, `adr/`, `docs/rfcs/`, an `ADR0001/` folder, or their siblings) exists anywhere in this tree. What was searched, so you can tell an empty log from a search that missed one: every directory under the tree (build output, dependencies and VCS metadata excepted), for a document that is either any non-index page inside a recognised ADR directory, whatever its name and however deeply nested (`docs/adr/use-postgres.md`, `docs/adr/2024/0001-x.md`); or a file anywhere whose name is ADR-shaped (`0001-use-postgres.md`, `adr-012-caching.md`); or, when neither turned anything up, a document carrying the decision-record signature (an "Architecture Decision Record" heading, or Status / Context / Decision / Consequences as section headings). A decision log that clears none of these — unnumbered files outside any recognised directory, without those headings — is not seen by this check and this row is then wrong. If that is your case, say so rather than renaming anything; otherwise, consider recording architectural decisions in `docs/adr/`.
D26 · Project Cohesion · Projects may be oversized for their cohesion · ×1
  • Projects may be oversized for their cohesion — 3 of 7 project(s) overshoot their size bounds, lowering Project Cohesion to 1.4/10. The most over is `common` (46915 LoC, 933 module-visible types across 108 directories). Review these for cohesion — draw the boundary inside the module first (group each responsibility into its own package or directory and keep the cross-boundary members non-public), since splitting a published package moves types between packages and breaks consumers.
D28 · Secrets (history) · Rotate the exposed credentials · ×1
  • REDACTED
D31 · IaC & Container Security · Low IaC · ×1
  • REDACTED
D34 · Knowledge Freshness · Orphaned files with no living knowledge · ×1
  • Orphaned files with no living knowledge — 1 of 313 analysed file(s) have no living knowledge left — their last meaningful change has decayed away, so if one breaks, no one currently understands it (counted over production source files of roughly 2,400 bytes or more, excluding vendored, generated, example/demo and scaffolding-template trees and test files identified by path convention, largest first; 313 of the 620 production source files in this repository met that bar). None is large enough to earn a read-through of its own, so this row stands in for the per-file rows rather than raising one each — most significant first: common/lib/src/features/lock/ui/keypad.dart. Attach the read to the next change that touches one of them: have a second person review that change, and leave behind a short comment or test recording what the file is for, so the knowledge comes back at the cost of a change you were making anyway.
D34 · Knowledge Freshness · Orphaned file · ×1
  • Orphaned file common/lib/src/features/lock/ui/keypad.dart:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
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.
P3 · Security & performance tooling · No SAST · ×1
  • No SAST REDACTED:9 — No static application security testing detected. For this repository's stack, add the Dart analyzer's security lints plus `semgrep --config=auto` as a CI step. What was searched, so you can tell an absence from a miss: the 11 CI workflow file(s) in this repository, and the scanner and linter configuration checked in beside them. A scan that runs outside CI, one configured in your forge's web UI rather than in a committed file, or a tool whose name is none of those this check carries, is not seen — if that is your case the row is wrong, and saying so is more useful than adding a second scanner.
P3 · Security & performance tooling · Dependabot does not watch pip/gitsubmodule · ×1
  • Dependabot does not watch pip/gitsubmodule REDACTED:2 — `REDACTED` schedules updates, but no `package-ecosystem` entry covers `pip`, `gitsubmodule`, which this tree depends on — so those dependencies get no update pull requests and no advisory pressure, however complete the dep-scan credit looks. Add the missing entries to the `updates:` list.
P6 · Release Hygiene · Changelog looks stale/thin · ×1
  • Changelog looks stale/thin — The changelog this check read carries 0 versioned entries, against a bar of 3. Counted as either the distinct `x.y.z` versions it names (a link's target is not counted) or its version-shaped section headings (`## [1.2.0]`, `## V14.x.x`, `## Updates in 8.0.x`), whichever is the larger — so a log sectioned by minor series counts its sections, not its individual patch numbers. Entries recorded somewhere this check does not read — release notes generated at tag time from a generator config it did not recognise, or a log kept outside the repository — are not counted here, and this row is about what is re-findable in the tree rather than about how often you release.
R7 · Dead Code · Unused export 'launchApp' · ×1
  • Unused export 'launchApp' automation/appium/wdio/src/flows/app.ts:53 — Nothing imports this binding — it is safe to review for removal.
R7 · Dead Code · Unused export 'removeAppIfPresent' · ×1
  • Unused export 'removeAppIfPresent' automation/appium/wdio/src/flows/app.ts:77 — Nothing imports this binding — it is safe to review for removal.
R7 · Dead Code · Unused export 'AutomationIdKey' · ×1
  • Unused export 'AutomationIdKey' automation/appium/wdio/src/support/automationIds.ts:60 — Nothing imports this binding — it is safe to review for removal.
R7 · Dead Code · Unused module-local declaration 'dnsProfileCellSelectors' · ×1
  • Unused module-local declaration 'dnsProfileCellSelectors' automation/appium/wdio/src/flows/settings.ts:31 — This top-level declaration is not exported and its name occurs nowhere else in its module — not called, read, typed against, re-exported or named by a string. Nothing outside the module can reach a non-exported binding, so this is the whole search: remove it, or use it.
R7 · Dead Code · Unused module-local declaration 'preferredDnsProfiles' · ×1
  • Unused module-local declaration 'preferredDnsProfiles' automation/appium/wdio/src/flows/settings.ts:37 — This top-level declaration is not exported and its name occurs nowhere else in its module — not called, read, typed against, re-exported or named by a string. Nothing outside the module can reach a non-exported binding, so this is the whole search: remove it, or use it.
R7 · Dead Code · Unused module-local declaration 'swipeUp' · ×1
  • Unused module-local declaration 'swipeUp' automation/appium/wdio/src/flows/settings.ts:146 — This top-level declaration is not exported and its name occurs nowhere else in its module — not called, read, typed against, re-exported or named by a string. Nothing outside the module can reach a non-exported binding, so this is the whole search: remove it, or use it.
X2 · Cancellation propagation · Not all async functions that make a request accept an AbortSignal · ×1
  • Not all async functions that make a request accept an AbortSignal — Only 0/1 async functions that make a cancellable request (fetch, axios, ky, ofetch, got, undici, node:http) accept an AbortSignal or pass one on, so a request keeps running after whatever wanted it has given up — a page navigated away from, an unmounted component, a timed-out job. Take a `signal` (or an options object that carries one) and hand it to the request; where nothing could ever cancel the call, omitting it is a deliberate choice — judge against how the function is used.

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-5cc5e33f8bc545e2b5b3680a16aeca5d/history.json --exit-code 0 --source .4artifacts/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-5cc5e33f8bc545e2b5b3680a16aeca5d/tree.json --exit-code 0 --source .0artifacts/raw/gitleaks-tree.json
D29 · Static Analysis (SAST)semgrep—semgrep --config /opt/semgrep-rules/security-audit.yml --config /opt/semgrep-rules/owasp-top-ten.yml --config /opt/semgrep-rules/canine-sast.yml --json --quiet --timeout 10 --timeout-threshold 3 --metrics off --exclude *.arrow --exclude *.avro --exclude *.csv --exclude *.dat --exclude *.db --exclude *.feather --exclude *.geojson --exclude *.h5 --exclude *.hdf5 --exclude *.jsonl --exclude *.log --exclude *.ndjson --exclude *.npy --exclude *.npz --exclude *.orc --exclude *.parquet --exclude *.pickle --exclude *.pkl --exclude *.psv --exclude *.sqlite --exclude *.sqlite3 --exclude *.tfrecord --exclude *.tsv --exclude *.txt --exclude ios/ChannelStatic .46artifacts/raw/semgrep.json
D30 · Dependency Vulnerabilitiestrivy—trivy fs --scanners vuln --format json --quiet --severity CRITICAL,HIGH,MEDIUM,LOW --skip-dirs **/bin/** --skip-dirs **/obj/** .2artifacts/raw/trivy-fs.json
D31 · IaC & Container Securitytrivy—trivy config --format json --quiet .3artifacts/raw/trivy-config.json
D32 · Data Compliance (PII/GDPR)semgrep—semgrep: not applicable — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that. semgrep could not parse 3 file(s) — `android/app/src/main/java/service/EnvironmentService.kt`, `android/app/wireguard-android/ui/src/main/java/com/wireguard/android/databinding/ObservableSortedKeyedArrayList.kt`, `ios/App/Util/Date+Extensions.swift` — so the PII/GDPR sweep did not cover the unparsed regions of them; rows reported elsewhere in those files are real.0—
D37 · Vulnerability-disclosure Policydisclosure—disclosure: not applicable — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed.0—
D40 · Network Egress Confinementruntime-hardening—runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here.0—
D41 · Kernel & Syscall Confinementruntime-hardening—runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here.0—
D42 · Runtime Threat Enforcementruntime-hardening—runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here.0—
D43 · Malicious 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 01a1ce4f-765a-760c-ac73-b07ce5e0b807 · 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